{ "prompt_name": "discord-announcement", "category": "comms", "date": "2025-07-17", "generated_text": "# \ud83d\ude80 ElizaOS Weekly Update: July 14-17, 2025\n\n**Exciting news! ElizaOS V2 has officially launched with our brand new website at elizaos.ai!**\n\n## \ud83d\udce3 Key Technical Updates:\n* Shaw conducted a live builder session demonstrating powerful ElizaOS V2 capabilities, now available on YouTube\n* Hyperfy v0.14.0 released with ambient occlusion, new scene app format, touch device joystick UI, and first-person support\n* Fixed database migration issues with custom plugins, particularly around schema handling\n* Implemented advisory locking for DatabaseMigrationService to prevent concurrency problems\n* Improved Windows compatibility for plugin loading and development\n\n## \ud83d\udcac Community Highlights:\n* Snapper re-uploaded tutorial videos with improved visibility of terminal commands\n* Community members provided extensive feedback for the new website design, suggesting reduced jargon and clearer onboarding pathways\n\n## \ud83d\udcb0 Token Updates:\n* DorianD shared comprehensive Grok-generated tokenomics upgrade ideas including decentralized compute sharing, token-gated knowledge exchange, and staking for reputation\n\n## \ud83d\udd2e Coming Next:\nWe're continuing to enhance the platform with real-time voice capabilities, working to resolve our X (Twitter) account issues, and implementing your feedback for the new website. Stay tuned for more improvements to our documentation and onboarding experience!", "source_references": [ "2025-07-17\n---\n2025-07-16.md\n---\n# elizaOS Discord - 2025-07-16\n\n## Overall Discussion Highlights\n\n### ElizaOS V2 Launch & Website\n- New website launched at elizaos.ai with positive community reception\n- Shaw conducted a live builder session demonstrating ElizaOS V2, which was streamed on YouTube\n- Community members shared tutorial videos with improved visibility of terminal commands\n- Website feedback suggested reducing jargon and creating clearer onboarding pathways\n\n### Technical Developments\n- Hyperfy v0.14.0 released with ambient occlusion, new scene app format, touch device joystick UI, camera-facing character controls, and first-person support\n- Multiple users reported issues with custom plugin development, particularly around database migrations and schema handling\n- Discussions about agent communication challenges using websockets and local plugin action recognition problems\n- OpenRouter announced upcoming deprecation of the o1-preview model\n\n### Platform Challenges\n- ElizaOS experiencing potential censorship on X (Twitter) with domain and GitHub URLs being blocked\n- Community documenting these issues as potential anti-competitive practices\n- Team attempting to schedule calls with X representatives to resolve the situation\n\n### Tokenomics & Community Building\n- DorianD shared Grok-generated tokenomics upgrade recommendations including:\n - Decentralized compute resource sharing\n - Token-gated knowledge exchange\n - Staking for reputation\n - Incentive-driven collaborative training\n - Governance mechanisms\n- Discussions about creating custom server emojis and artwork for the community\n- Suggestions to increase visibility of development efforts through live streaming\n\n## Key Questions & Answers\n\n**Q: What is ElizaOS?** \nA: It's an operating system for AI agents\n\n**Q: Did Shaw leave Eliza?** \nA: No, he hasn't left\n\n**Q: What do people think of the new site?** \nA: Multiple positive responses, with Bealers noting it \"looks badass\" and Dr. Neuro praising the color scheme\n\n**Q: When does the voice chat start?** \nA: 1 hour from now\n\n**Q: Is there a recording of the builder session?** \nA: Yes, available on YouTube\n\n**Q: How can I fix the EPERM error when creating an agent in WSL?** \nA: Try using a remote database like neon.tech or local postgres instead of PGLite\n\n**Q: How can I guarantee a provider will be called for every message?** \nA: This is what providers should do if you need to get data and add to the context\n\n**Q: Is elizaOS being suppressed on X?** \nA: The GitHub URL was banned but later unbanned; they're in talks with X but responses are slow\n\n**Q: Could Shaw reach out to people he knows at X?** \nA: They're trying to schedule a call, waiting for schedules to align\n\n## Community Help & Collaboration\n\n1. **Tutorial Video Improvements** \n Snapper re-uploaded the first two tutorial episodes with captions removed for better visibility of terminal commands\n\n2. **Builder Session Recording** \n Borko shared YouTube recording links of Shaw's demo for community members who missed the live session\n\n3. **Website Feedback** \n 3on_ shared detailed critique from ChatGPT about the new website design and messaging to help improve the site\n\n4. **Plugin Development Support** \n Sayonara provided solutions for custom plugin schema migration issues, explaining proper schema export, dependencies, and plugin structure requirements\n\n5. **Database Setup Alternatives** \n Sayonara suggested using neon.tech or local postgres as alternatives to PGLite for users experiencing WSL environment issues\n\n6. **Tokenomics Proposals** \n DorianD shared comprehensive Grok-generated tokenomics upgrade ideas to enhance the ecosystem's value proposition\n\n## Action Items\n\n### Technical\n- Improve ElizaOS website based on feedback about jargon and lack of clear onboarding pathway (Mentioned by 3on_)\n- Fix PGLite directory setup issues in WSL environments (Mentioned by sayonara)\n- Improve provider reliability for context injection (Mentioned by BhnInvestor)\n- Create GitHub issue with detailed logs for database migration problems (Mentioned by sayonara)\n- Explore implementation of decentralized compute resource sharing using tokens (Mentioned by DorianD)\n- Consider token-gated knowledge and memory exchange between nodes (Mentioned by DorianD)\n- Implement staking mechanism for reputation and service reliability (Mentioned by DorianD)\n- Develop incentive-driven collaborative training and fine-tuning protocols (Mentioned by DorianD)\n- Create governance and protocol evolution via token voting (Mentioned by DorianD)\n- Implement token-enabled secure data streaming and real-time sync (Mentioned by DorianD)\n- Develop incentive mechanism for plugin development and sharing (Mentioned by DorianD)\n- Create a watcher channel for ecosystem updates (Mentioned by Kenk)\n- Maintain clean official accounts to avoid ToS violations (Mentioned by DorianD)\n- Create ELI5 server emojis (Mentioned by AccountShark)\n\n### Documentation\n- Create more tutorial content for ElizaOS (Mentioned by Fleo-Thyphon)\n- Add agent-specific rooms for focused project feedback (Mentioned by ?????)\n- Clarify how to properly structure plugins for database migrations (Mentioned by sayonara)\n- Record Shaw's elizaOS v2 workshop session for those who couldn't attend (Mentioned by yikesawjeez)\n- Increase visibility of development work through live streaming on platforms like Time.fun (Mentioned by CRAY)\n- Document potential anti-competitive practices by X against elizaOS (Mentioned by multiple users)\n\n### Feature\n- Implement Eli5 as an AI companion (Mentioned by wire)\n- Improve Telegram channel structure with sub-channels similar to Discord (Mentioned by wire)\n- Support passing images to Anthropic models through useModel(ModelType.TEXT_LARGE) (Mentioned by Charlie)\n- Consider adding more crypto/token-focused content to presentations (Mentioned by pangolink)\n---\n2025-07-15.md\n---\n# elizaOS Discord - 2025-07-15\n\n## Overall Discussion Highlights\n\n### X Account Suspension & Platform Competition\n- ElizaOS's Twitter/X account was suspended, causing community concern about visibility and potential exchange listings\n- Speculation that the suspension is related to competition with Elon Musk's Grok AI and XAI companions\n- Reports that X is charging $50k/month for company API fees, potentially targeting AI competitors\n- Multiple ElizaOS-related accounts affected by suspensions, including Shaw's account and \"degenspartanai\"\n- Concerns about MEXC potentially delisting Eliza, though details are limited\n\n### Technical Developments\n- Twitter plugin v1.2.16 released with new discovery service, auto-posting fixes, and weighted discovery algorithm\n- Developers working on real-time voice capabilities with AI to enable humans to join interviews and panels\n- Knowledge plugin experiencing issues where agent responses aren't reaching the client side\n- Custom plugin schema migration problems identified in ElizaOS v1.2.5 with PostgreSQL and Drizzle ORM\n- Environment variable formatting issues causing Ollama integration errors (quotes causing HTTP request errors)\n\n### Website & Content Initiatives\n- New domains purchased: elizaos.news (for AI news show episodes) and jedaicouncil.com\n- elizaos.news hosting AI-generated news content\n- Plans to create shorter clips from longer content for distribution on platforms like TikTok and Farcaster\n- Community requesting features like transcript buttons and crypto news summaries\n\n### Economic & Tokenomics Discussions\n- Importance of open-source development as competitive advantage against closed systems like Grok\n- Parallels drawn to Bitcoin and Ethereum's success as open-source projects with economic coordination layers\n- Discussion about ElizaOS needing strong tokenomics to incentivize nodes running agents\n- DorianD proposed system where AI companions would interact with token contracts to access user data, creating a reputation system for AI agents\n\n## Key Questions & Answers\n\n**Q: How can I fix Ollama integration errors in ElizaOS?** \nA: Remove quotes from environment variables for model names (answered by starlord)\n\n**Q: How can I avoid using Ollama when I only want to use Google?** \nA: Remove '@elizaos/plugin-ollama' from your character file and clean/rebuild (answered by 0xbbjoker)\n\n**Q: Why isn't my agent using the JSON file loaded with the knowledge plugin?** \nA: There's an issue with plugin-knowledge where messages don't reach the client side (answered by 0xbbjoker)\n\n**Q: How does ElizaOS continue to be valuable when it's open source and faced with challengers like XAI who have deeper pockets?** \nA: DorianD suggested looking at Bitcoin and Ethereum as successful open-source models with economic coordination layers\n\n**Q: Where can I find news about ElizaOS?** \nA: At elizaos.news (answered by jin)\n\n**Q: Do you upload these videos to TikTok and Farcaster too?** \nA: Jin mentioned it's on the todo list to edit content into \"shorts\" for bite-size distribution\n\n## Community Help & Collaboration\n\n1. **Ollama Integration Troubleshooting**\n - Helper: starlord | Helpee: sayonara\n - Context: Identified that quotes in .env file for model names cause HTTP request errors\n - Resolution: Removing quotes from environment variables resolved the issue\n\n2. **Knowledge Plugin Workaround**\n - Helper: 0xbbjoker | Helpee: BhnInvestor\n - Context: Knowledge plugin not using JSON file properly\n - Resolution: Suggested using local CLI with latest develop branch as a workaround\n\n3. **Twitter Plugin Updates**\n - Helper: cjft | Helpee: Community\n - Context: Twitter plugin issues with auto-posting\n - Resolution: Released v1.2.16 with fixes and new discovery features\n\n4. **Website Improvement Suggestions**\n - Helper: jin | Helpee: Odilitime\n - Context: Request for transcript functionality on news site\n - Resolution: Jin acknowledged with \"will fix, soon as my internet is back\"\n\n5. **X Account Suspension Context**\n - Helper: emptyskull | Helpee: Multiple users\n - Context: Explaining why X account might be suspended\n - Resolution: Shared that X is asking for company API fees of $50k per month according to Shaw\n\n## Action Items\n\n### Technical\n- Fix quotes handling in environment variables for Ollama models (mentioned by starlord)\n- Fix database migration service for custom plugins (mentioned by baditu)\n- Fix knowledge plugin issue where agent responses don't reach client side (mentioned by 0xbbjoker)\n- Implement a \"read transcript\" button on elizaos.news (mentioned by Odilitime)\n- Develop real-time voice capabilities with AI for interviews and panels (mentioned by jin)\n- Create script to edit content into \"shorts\" for bite-size distribution (mentioned by jin)\n- Investigate and address the ElizaOS X account suspension (mentioned by multiple users)\n- Fix issue with Ollama being required even when not in character file (mentioned by sayonara)\n\n### Documentation\n- Update documentation for environment variable formatting standards (mentioned by starlord)\n- Clarify status of ElizaOS social media accounts (mentioned by Chae1550)\n\n### Feature\n- Improve context size handling for Ollama models (mentioned by starlord)\n- Include daily global summary of important crypto news on elizaos.news (mentioned by human_nalejzpa)\n- System for AI companions to interact with token contracts for data access (mentioned by DorianD)\n- Implement agent reputation system based on data sharing behavior (mentioned by DorianD)\n- Implement economic coordination layer for ElizaOS (mentioned by DorianD)\n- Develop strong tokenomics for ElizaOS nodes (mentioned by DorianD)\n---\n2025-07-14.md\n---\n# elizaOS Discord - 2025-07-14\n\n## Overall Discussion Highlights\n\n### Project Status & Updates\n- **Twitter/X Account Suspension**: The team is still waiting for X to execute a resolution for the suspended account. Community members expressed frustration about the delay, comparing it to other projects that recovered accounts more quickly.\n- **Stoic Beta Launch**: A new release called \"Stoic beta\" has launched, though details were limited.\n- **Token Ecosystem Clarification**: The project has two related tokens:\n - **$ai16z**: The main token behind the ElizaOS agentic framework\n - **$degenai**: Associated with Spartan, a product incubated by Eliza Labs\n\n### Technical Discussions\n- **Ollama Integration Issues**: Users encountered errors connecting to Ollama despite models being locally available, with community members suggesting endpoint configuration fixes.\n- **Agent Communication**: Discussion about enabling specialized agents to communicate with each other when one doesn't know an answer.\n- **Knowledge Plugin Problems**: Issues reported with the plugin-knowledge feature not utilizing uploaded JSON files despite being visible in the GUI.\n- **Database Errors**: Some users experienced errors when restarting the GUI after stopping with duplicate agent IDs, resolved by removing the .eliza directory.\n\n### Financial & Token Discussions\n- **Token Implementation**: Questions about the token2022 standard used by daos.fun for token creation, with mentions of potential changes when a name change happens.\n- **Autofun Incubator**: Clarified as an accelerator for agent teams looking to launch agents.\n- **Market Speculation**: Discussions about various tokens including \"JIMMY CODED\" (with 10% reportedly burned) and warnings about fake tokens like \"LUARA\".\n- **BlackRock's Interest**: Mention of BlackRock's interest in tokenization for stock, bond, and real estate trading, with focus on cybersecurity challenges of identity verification.\n\n## Key Questions & Answers\n\n### Project & Token Information\n- **Q**: What is the difference between degenai and ai16z? \n **A**: $ai16z is the token behind the elizaOS agentic framework, Spartan is a product incubated by Eliza Labs that has the ticker $degenai (answered by Kenk)\n\n- **Q**: Is the token mintable or has minting been disabled? \n **A**: It's a daos.fun token, they have mint control (answered by Odilitime)\n\n- **Q**: Do you have any security audits available? \n **A**: There's no smart contracts directly for ai16z. We do have audits on the open source project and autodotfun (answered by Odilitime)\n\n- **Q**: What is autofun incubator? \n **A**: Accelerator for agent teams looking to launch agents (answered by Kenk)\n\n### Technical Support\n- **Q**: How long does it take for Eliza to respond with the raw message when no action is executed? \n **A**: For local deployment, it depends on model weights and PC specs; no standard benchmark exists for raw message response times (answered by starlord)\n\n- **Q**: How can I update to the latest version of ElizaOS? \n **A**: Run `bun i -g @elizaos/cli` (answered by 0xbbjoker)\n\n- **Q**: Is there any update on x account? \n **A**: Resolution in sight but awaiting X to execute; we're following up and expect it will be returned (answered by Kenk)\n\n## Community Help & Collaboration\n\n### Troubleshooting Assistance\n- **sayonara** helped **starlord** with Ollama integration errors by suggesting different endpoints (http://0.0.0.0:11434) and offering live debugging via voice call; also recommended the gemma3:27b model.\n\n- **0xbbjoker** assisted **BhnInvestor** with GUI restart errors by suggesting removal of the .eliza directory in the project root to start fresh.\n\n- **Kenk** clarified for **ZzzzHodl** the difference between the project's two tokens, explaining their respective roles in the ecosystem.\n\n- **Odilitime** provided **Joseph-77** with information about token mintability and security audits, explaining the relationship with daos.fun.\n\n### Community Contributions\n- A community member created and shared a promotional video for the project.\n- Several users offered debugging assistance through voice calls for those experiencing technical difficulties.\n\n## Action Items\n\n### Technical\n- **Fix Twitter/X account suspension issue**: Team is waiting on X team to execute the resolution (Mentioned by Kenk)\n- **Fix issue with plugin-knowledge**: Address problem where the feature is not utilizing uploaded JSON files despite being visible in GUI (Mentioned by BhnInvestor)\n- **Address Ollama integration errors**: Fix error messages appearing when models are locally available (Mentioned by starlord)\n- **Implement agent-to-agent communication**: Enable one agent to pass questions to another specialized agent when it doesn't know the answer (Mentioned by ShisukeUrahara)\n- **Consider moving to a new token2022 implementation**: Move away from daos.fun implementation when name change happens (Mentioned by DorianD)\n\n### Documentation\n- **Provide documentation for degenai**: User requested links to degenai documentation (Mentioned by ZzzzHodl)\n- **Document response time benchmarks**: Provide guidance on expected response times for different deployment scenarios (Mentioned by Sabochee)\n- **Clarify official tokens/agents**: Create documentation distinguishing official tokens/agents from fake ones (Mentioned by 33coded)\n\n### Feature\n- **Consider developing Spartan as a personal trading bot**: Allow users to train Spartan through a Language Model for personalized trading (Mentioned by Dai00)\n---\n2025-07-16.md\n---\nFile not found\n---\n2025-07-15.md\n---\nFile not found\n---\n2025-07-14.md\n---\nFile not found\n---\n2025-07-16.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-07-16\n---\nGitHub Activity Summary\n---\nFrom July 16-17, 2025, the elizaOS/eliza repository showed moderate activity with 4 new issues opened. There were no new pull requests during this period. The repository maintained an active contributor base with 4 contributors participating during this timeframe.\n---\nIssues\n---\nIssue #5606 titled '.eliza directory getting hoisted' by @linear is OPEN.\n---\nhttps://github.com/elizaOS/eliza/issues/5606\n---\nIssue #5605 titled 'Unable to create project without using keys' by @linear is OPEN.\n---\nhttps://github.com/elizaOS/eliza/issues/5605\n---\nIssue #5604 titled 'Make API key setup optional in npx elizaos create' by @linear is OPEN.\n---\nhttps://github.com/elizaOS/eliza/issues/5604\n---\nIssue #5603 titled 'Unable to create dir on windows' by @linear is OPEN.\n---\nhttps://github.com/elizaOS/eliza/issues/5603\n---\nPull Requests\n---\nPR #5569 by @wtfsayo titled 'feat: implement advisory locking for DatabaseMigrationService' has an unknown state as the item_state was not provided in the input.\n---\nhttps://github.com/elizaOS/eliza/pull/5569\n---\nSummary for github_other\n---\nThe repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-07-16.md\n---\n# Daily Report - 2025-07-16\n\n## GitHub Activity Summary\n- From July 16-17, 2025, the elizaOS/eliza repository showed moderate activity with 4 new issues opened. There were no new pull requests during this period. The repository maintained an active contributor base with 4 contributors participating during this timeframe.\n\n## Issues\n- Issue #5606 titled '.eliza directory getting hoisted' by @linear is OPEN. (Source: https://github.com/elizaOS/eliza/issues/5606)\n- Issue #5605 titled 'Unable to create project without using keys' by @linear is OPEN. (Source: https://github.com/elizaOS/eliza/issues/5605)\n- Issue #5604 titled 'Make API key setup optional in npx elizaos create' by @linear is OPEN. (Source: https://github.com/elizaOS/eliza/issues/5604)\n- Issue #5603 titled 'Unable to create dir on windows' by @linear is OPEN. (Source: https://github.com/elizaOS/eliza/issues/5603)\n\n## Pull Requests\n- PR #5569 by @wtfsayo titled 'feat: implement advisory locking for DatabaseMigrationService' has an unknown state as the item_state was not provided in the input. (Source: https://github.com/elizaOS/eliza/pull/5569)\n\n## Summary for github_other\n- The repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-07-16.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-07-16\n---\n1253563209462448241\n---\ndiscussion\n---\n# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe discussion primarily focused on ElizaOS, an operating system for AI agents. Key technical highlights include the launch of a new website (elizaos.ai) and a builder session demonstrating ElizaOS V2. Shaw and team conducted a live demo that was streamed on YouTube, showing new features and capabilities. Community members shared tutorial videos with improved visibility of terminal commands. There were discussions about the project's positioning as an agentic framework utility rather than a meme project. The community expressed concerns about the suspension of the project's X (Twitter) account, which is limiting their ability to share links and updates. Some members suggested documenting these issues as potential anti-competitive practices. The community also discussed marketing strategies and the need for more visibility of development efforts, with suggestions to use platforms like Time.fun for live streaming development work.\n\n## 2. FAQ\nQ: What is ElizaOS? (asked by allmagic5x) A: It's an operating system for AI agents (answered by website content shared during discussion)\nQ: Did Shaw leave Eliza? (asked by EddyTheHead) A: No, he hasn't left (answered by Kenk)\nQ: What do people think of the new site? (asked by Kenk) A: Multiple positive responses, with Bealers noting it \"looks badass\" and Dr. Neuro praising the color scheme\nQ: Can we make Eli5 an AI companion? (asked by wire) A: Unanswered\nQ: Is the voice chat over? Or when does it start? (asked by HodlHusky) A: Starts in 1 hour (answered by Kenk)\nQ: Is there a recording? (asked by \u0627\u0644\u0634\u064a\u062e \u0623\u062f\u064a\u0628 \u0639\u0644\u064a) A: Yes, available on YouTube (answered by Borko)\nQ: What's the plan? (asked by ghk9698) A: Unanswered directly, though the builder session recording was shared\n\n## 3. Help Interactions\nHelper: Snapper | Helpee: Community | Context: Tutorial video captions blocking terminal view | Resolution: Re-uploaded first two episodes with captions removed for better visibility of terminal commands\nHelper: Borko | Helpee: Community | Context: Missed the live builder session | Resolution: Shared YouTube recording link of Shaw's demo\nHelper: Kenk | Helpee: Community | Context: Confusion about event timing | Resolution: Clarified start time and shared event link\nHelper: 3on_ | Helpee: Community | Context: Website feedback needed | Resolution: Shared detailed critique from ChatGPT about the new website design and messaging\n\n## 4. Action Items\nType: Technical | Description: Improve ElizaOS website based on feedback about jargon and lack of clear onboarding pathway | Mentioned By: 3on_\nType: Technical | Description: Create more tutorial content for ElizaOS | Mentioned By: Fleo-Thyphon\nType: Documentation | Description: Add agent-specific rooms for focused project feedback | Mentioned By: ?????\nType: Feature | Description: Implement Eli5 as an AI companion | Mentioned By: wire\nType: Technical | Description: Improve Telegram channel structure with sub-channels similar to Discord | Mentioned By: wire\nType: Documentation | Description: Increase visibility of development work through live streaming on platforms like Time.fun | Mentioned By: CRAY\nType: Technical | Description: Create a watcher channel for ecosystem updates | Mentioned By: Kenk\nType: Technical | Description: Maintain clean official accounts to avoid ToS violations that could justify bans | Mentioned By: DorianD\n---\n1300025221834739744\n---\n\ud83d\udcbb-tech-support\n---\n# Discord Chat Analysis for \ud83d\udcbb-tech-support\n\n## 1. Summary:\nThe chat primarily revolves around plugin development issues and technical troubleshooting. Several users encountered problems with custom plugins, database migrations, and integrations. Key discussions included: passing images to Anthropic models through useModel, plugin schema migration issues related to DatabaseMigrationService, agent communication challenges using websockets, local plugin action recognition problems, and database setup errors in WSL environments. There was also a question about dynamically injecting data into LLM context. The OpenRouter service announced the upcoming deprecation of the o1-preview model. Most technical issues remained unresolved, with community members suggesting workarounds or requesting more information for troubleshooting.\n\n## 2. FAQ:\nQ: Is there a way to pass images in useModel(ModelType.TEXT_LARGE) for Anthropic without creating an external API call? (asked by Charlie) A: Unanswered\nQ: How can I make one agent internally ask a question to another agent and get the response? (asked by ShisukeUrahara) A: Unanswered\nQ: Why doesn't my agent recognize actions from my local plugin? (asked by Uro\u0161 Ognjenovi\u0107) A: Better action and provider descriptions should do it (answered by sayonara)\nQ: How can I guarantee a provider will be called for every message? (asked by BhnInvestor) A: This is what provider should do, if you need to get some data and add to the context (answered by 0xbbjoker)\nQ: How do I fix the EPERM error when creating an agent in WSL? (asked by Stick) A: Try using a remote database like neon.tech or local postgres (answered by sayonara)\n\n## 3. Help Interactions:\nHelper: cjft | Helpee: AD | Context: User couldn't find the Twitter plugin | Resolution: Provided GitHub link to the plugin\nHelper: sayonara | Helpee: baditu | Context: Custom plugin schemas not being migrated | Resolution: Shared solution requiring proper schema export, dependencies, and plugin structure\nHelper: sayonara | Helpee: Stick | Context: Database setup errors in WSL | Resolution: Suggested using neon.tech or local postgres as alternative to PGLite\nHelper: 0xbbjoker | Helpee: BhnInvestor | Context: Injecting dynamic data into LLM context | Resolution: Suggested using providers for this purpose\n\n## 4. Action Items:\nTechnical: Fix PGLite directory setup issues in WSL environments | Description: Users encounter ENOENT errors when creating agents | Mentioned By: sayonara\nTechnical: Improve provider reliability for context injection | Description: Providers aren't consistently called without explicit prompting | Mentioned By: BhnInvestor\nTechnical: Create GitHub issue with detailed logs for database migration problems | Description: Multiple users experiencing migration issues with custom plugins | Mentioned By: sayonara\nDocumentation: Clarify how to properly structure plugins for database migrations | Description: Users struggle with implementing proper schema migrations | Mentioned By: sayonara\nFeature: Support passing images to Anthropic models through useModel(ModelType.TEXT_LARGE) | Description: Currently requires external API calls | Mentioned By: Charlie\n---\n1361442528813121556\n---\nfun\n---\n# Discord Chat Analysis for \"fun\" Channel\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation primarily revolves around a cryptocurrency or token called \"ELI5\" with members discussing price movements, expressing excitement about potential price increases (\"pump\"), and encouraging community engagement. One user (Gorllionskid) briefly mentions being a developer for \"HannaAI18\" who self-taught how to create an agent within \"ElizaOS\" in under 24 hours, but provides no technical details. The chat includes numerous emoji reactions, memes, and casual conversation about price predictions, with mentions of an upcoming voice chat. There are also references to community building activities like creating server emojis and artwork.\n\n## 2. FAQ\nQ: When does that voice chat start? (asked by HodlHusky) A: 1hr from now (answered by Crispy)\nQ: What mind of emoij's? (asked by Dr. Neuro) A: Unanswered\n\n## 3. Help Interactions\nHelper: Dr. Neuro | Helpee: Channel members | Context: Offering to help create artwork from gifs, images, stickers, emojis | Resolution: Offered to share how to get started, but no confirmation of assistance provided\n\n## 4. Action Items\nFeature: Create ELI5 server emojis | Description: Need custom emojis for the ELI5 community server | Mentioned By: AccountShark\nTechnical: Retweet meme via auto.fun X | Description: Request to have a meme retweeted through an automated system | Mentioned By: AccountShark\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\n# Discord Chat Analysis for \ud83e\udd47-partners Channel\n\n## 1. Summary\nThe chat primarily focused on the release of Hyperfy v0.14.0, which introduced several technical improvements including ambient occlusion, a new scene app format, touch device joystick UI, camera-facing character controls, and first-person support. There was significant discussion about potential censorship of elizaOS on X (Twitter), with members noting that both the elizaOS domain and GitHub URLs were being blocked. A workshop demonstration by Shaw about elizaOS v2 was promoted, with community members helping to spread the word. \n\nDorianD shared several tokenomics upgrade recommendations generated by Grok 4, including decentralized compute resource sharing, token-gated knowledge exchange, staking for reputation, incentive-driven collaborative training, and governance mechanisms. These proposals focused on creating value for AI agents in siloed nodes through various token-based incentive structures.\n\nThe community also discussed potential anti-competitive practices by X against elizaOS, with suggestions to document these actions for potential legal review. The chat revealed ongoing attempts to resolve the situation with X, including scheduling calls with the platform's representatives.\n\n## 2. FAQ\nQ: Is elizaOS being suppressed on X? (asked by pangolink) A: The GitHub URL was banned but later unbanned; they're in talks with X but responses are slow (answered by Odilitime)\nQ: Could Shaw reach out to people he knows at X? (asked by popeyebonchon) A: They're trying to schedule a call, waiting for schedules to align (answered by Odilitime)\nQ: Can you use a link shortener to bypass the ban? (asked by DorianD) A: Probably depends on which shortener, but it might work (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: DorianD | Helpee: Channel members | Context: Sharing Grok-generated tokenomics upgrade ideas for AI agents in siloed nodes | Resolution: Provided five detailed proposals including decentralized compute sharing, token-gated knowledge exchange, and reputation staking\nHelper: Kenk | Helpee: Channel members | Context: Promoting Shaw's elizaOS v2 workshop | Resolution: Provided information about the workshop and requested help spreading the word on X\nHelper: Odilitime | Helpee: popeyebonchon | Context: Explaining the X platform ban situation | Resolution: Clarified that GitHub URL was previously banned but later unbanned, and that they're working to resolve the situation\n\n## 4. Action Items\nType: Technical | Description: Explore implementation of decentralized compute resource sharing using $ai16z tokens | Mentioned By: DorianD\nType: Technical | Description: Consider token-gated knowledge and memory exchange between nodes | Mentioned By: DorianD\nType: Technical | Description: Implement staking mechanism for reputation and service reliability | Mentioned By: DorianD\nType: Technical | Description: Develop incentive-driven collaborative training and fine-tuning protocols | Mentioned By: DorianD\nType: Technical | Description: Create governance and protocol evolution via token voting | Mentioned By: DorianD\nType: Technical | Description: Implement token-enabled secure data streaming and real-time sync | Mentioned By: DorianD\nType: Technical | Description: Develop incentive mechanism for plugin development and sharing | Mentioned By: DorianD\nType: Documentation | Description: Record Shaw's elizaOS v2 workshop session for those who couldn't attend | Mentioned By: yikesawjeez\nType: Feature | Description: Consider adding more crypto/token-focused content to presentations for the community | Mentioned By: pangolink\n---\n1326603270893867064\n---\ntwitter-ai-news\n---\nThe provided chat transcript contains only timestamps and the username \"Captain Hook\" with no actual message content. There are 12 entries from Captain Hook at 00:00, 04:00, 08:00, 12:00, 16:00, and 20:00, with two entries at each timestamp. Since no actual messages or technical discussions are present in the transcript, there is no substantive content to summarize.\n---\n2025-07-16.md\n---\n# elizaOS Discord - 2025-07-16\n\n## Overall Discussion Highlights\n\n### ElizaOS V2 Launch & Website\n- New website launched at elizaos.ai with positive community reception\n- Shaw conducted a live builder session demonstrating ElizaOS V2, which was streamed on YouTube\n- Community members shared tutorial videos with improved visibility of terminal commands\n- Website feedback suggested reducing jargon and creating clearer onboarding pathways\n\n### Technical Developments\n- Hyperfy v0.14.0 released with ambient occlusion, new scene app format, touch device joystick UI, camera-facing character controls, and first-person support\n- Multiple users reported issues with custom plugin development, particularly around database migrations and schema handling\n- Discussions about agent communication challenges using websockets and local plugin action recognition problems\n- OpenRouter announced upcoming deprecation of the o1-preview model\n\n### Platform Challenges\n- ElizaOS experiencing potential censorship on X (Twitter) with domain and GitHub URLs being blocked\n- Community documenting these issues as potential anti-competitive practices\n- Team attempting to schedule calls with X representatives to resolve the situation\n\n### Tokenomics & Community Building\n- DorianD shared Grok-generated tokenomics upgrade recommendations including:\n - Decentralized compute resource sharing\n - Token-gated knowledge exchange\n - Staking for reputation\n - Incentive-driven collaborative training\n - Governance mechanisms\n- Discussions about creating custom server emojis and artwork for the community\n- Suggestions to increase visibility of development efforts through live streaming\n\n## Key Questions & Answers\n\n**Q: What is ElizaOS?** \nA: It's an operating system for AI agents\n\n**Q: Did Shaw leave Eliza?** \nA: No, he hasn't left\n\n**Q: What do people think of the new site?** \nA: Multiple positive responses, with Bealers noting it \"looks badass\" and Dr. Neuro praising the color scheme\n\n**Q: When does the voice chat start?** \nA: 1 hour from now\n\n**Q: Is there a recording of the builder session?** \nA: Yes, available on YouTube\n\n**Q: How can I fix the EPERM error when creating an agent in WSL?** \nA: Try using a remote database like neon.tech or local postgres instead of PGLite\n\n**Q: How can I guarantee a provider will be called for every message?** \nA: This is what providers should do if you need to get data and add to the context\n\n**Q: Is elizaOS being suppressed on X?** \nA: The GitHub URL was banned but later unbanned; they're in talks with X but responses are slow\n\n**Q: Could Shaw reach out to people he knows at X?** \nA: They're trying to schedule a call, waiting for schedules to align\n\n## Community Help & Collaboration\n\n1. **Tutorial Video Improvements** \n Snapper re-uploaded the first two tutorial episodes with captions removed for better visibility of terminal commands\n\n2. **Builder Session Recording** \n Borko shared YouTube recording links of Shaw's demo for community members who missed the live session\n\n3. **Website Feedback** \n 3on_ shared detailed critique from ChatGPT about the new website design and messaging to help improve the site\n\n4. **Plugin Development Support** \n Sayonara provided solutions for custom plugin schema migration issues, explaining proper schema export, dependencies, and plugin structure requirements\n\n5. **Database Setup Alternatives** \n Sayonara suggested using neon.tech or local postgres as alternatives to PGLite for users experiencing WSL environment issues\n\n6. **Tokenomics Proposals** \n DorianD shared comprehensive Grok-generated tokenomics upgrade ideas to enhance the ecosystem's value proposition\n\n## Action Items\n\n### Technical\n- Improve ElizaOS website based on feedback about jargon and lack of clear onboarding pathway (Mentioned by 3on_)\n- Fix PGLite directory setup issues in WSL environments (Mentioned by sayonara)\n- Improve provider reliability for context injection (Mentioned by BhnInvestor)\n- Create GitHub issue with detailed logs for database migration problems (Mentioned by sayonara)\n- Explore implementation of decentralized compute resource sharing using tokens (Mentioned by DorianD)\n- Consider token-gated knowledge and memory exchange between nodes (Mentioned by DorianD)\n- Implement staking mechanism for reputation and service reliability (Mentioned by DorianD)\n- Develop incentive-driven collaborative training and fine-tuning protocols (Mentioned by DorianD)\n- Create governance and protocol evolution via token voting (Mentioned by DorianD)\n- Implement token-enabled secure data streaming and real-time sync (Mentioned by DorianD)\n- Develop incentive mechanism for plugin development and sharing (Mentioned by DorianD)\n- Create a watcher channel for ecosystem updates (Mentioned by Kenk)\n- Maintain clean official accounts to avoid ToS violations (Mentioned by DorianD)\n- Create ELI5 server emojis (Mentioned by AccountShark)\n\n### Documentation\n- Create more tutorial content for ElizaOS (Mentioned by Fleo-Thyphon)\n- Add agent-specific rooms for focused project feedback (Mentioned by ?????)\n- Clarify how to properly structure plugins for database migrations (Mentioned by sayonara)\n- Record Shaw's elizaOS v2 workshop session for those who couldn't attend (Mentioned by yikesawjeez)\n- Increase visibility of development work through live streaming on platforms like Time.fun (Mentioned by CRAY)\n- Document potential anti-competitive practices by X against elizaOS (Mentioned by multiple users)\n\n### Feature\n- Implement Eli5 as an AI companion (Mentioned by wire)\n- Improve Telegram channel structure with sub-channels similar to Discord (Mentioned by wire)\n- Support passing images to Anthropic models through useModel(ModelType.TEXT_LARGE) (Mentioned by Charlie)\n- Consider adding more crypto/token-focused content to presentations (Mentioned by pangolink)\n---\n2025-07-16.json\n---\nFile not found\n---\n2025-07-16.md\n---\nFile not found\n---\n2025-07-16.json\n---\nFile not found\n---\n2025-07-16.md\n---\nFile not found\n---\n2025-07-17.md\n---\nFile not found\n---\n2025-07-13.md\n---\n# elizaos/eliza Weekly Report (Jul 13 - 19, 2025)\n\n## \ud83d\ude80 Highlights\nThis week was marked by significant strides in core architecture and developer experience. A major milestone was the implementation of standardized service types, a foundational step towards greater modularity and abstract plugin development. The command-line interface (CLI) received substantial upgrades to improve stability and streamline workflows, including automatic builds and graceful server shutdowns. Concurrently, planning for a new \"Scenario Runner\" feature kicked off, outlining a comprehensive framework for agent evaluation. The team also focused on enhancing testing infrastructure by fully embracing the Bun runtime and improving CI processes.\n\n## \ud83d\udee0\ufe0f Key Developments\nWork this week focused on strengthening the project's foundations, from core services to developer tooling and testing.\n\n- **Core Architecture Enhancements:** A pivotal change was the introduction of standardized service types and a `getServicesByType()` method, enabling more flexible and abstract plugin interactions ([#5565](https://github.com/elizaos/eliza/pull/5565)). This was complemented by code cleanup, such as removing a duplicate `ActionResult` interface to resolve build errors ([#5593](https://github.com/elizaos/eliza/pull/5593)).\n\n- **CLI & Developer Experience:** The developer workflow saw major improvements. The `elizaos start` command now automatically builds projects, mirroring the `dev` command's behavior ([#5504](https://github.com/elizaos/eliza/pull/5504]). The dev server now shuts down gracefully with `Cmd+C`, preventing orphaned processes ([#5562](https://github.com/elizaos/eliza/pull/5562]). For plugin developers, a new `plugin-quick-starter` template was added for creating backend-only plugins without frontend boilerplate ([#5589](https://github.com/elizaos/eliza/pull/5589]). The CLI also became more robust by handling port conflicts automatically ([#5592](https://github.com/elizaos/eliza/pull/5592]) and improving `bunx` detection ([#5599](https://github.com/elizaos/eliza/pull/5599)).\n\n- **Testing & CI Infrastructure:** The project continued its migration to Bun-native tooling. CI tests for the CLI were improved by using Bun's native process spawning, and `execa` was replaced in core tests ([#5586](https://github.com/elizaos/eliza/pull/5586), [#5556](https://github.com/elizaos/eliza/pull/5556)). Test suites were updated to reflect version 1.2.1 changes and refactored for clarity ([#5561](https://github.com/elizaos/eliza/pull/5561), [#5557](https://github.com/elizaos/eliza/pull/5557)).\n\n- **AI & Plugin Improvements:** The Claude code review workflow was enhanced to run on every PR commit with expanded permissions ([#5570](https://github.com/elizaos/eliza/pull/5570]). The integration with local models was refined, with a focus on Ollama. The legacy `llama_local` provider was officially mapped to the `@elizaos/plugin-ollama` plugin ([#5582](https://github.com/elizaos/eliza/pull/5582]), and a bug in the `installModelPlugin` logic was fixed to ensure correct resolution ([#5598](https://github.com/elizaos/eliza/pull/5598]).\n\n## \ud83d\udc1b Issues & Triage\n\n- **Closed Issues:** A significant number of bugs were resolved, enhancing stability and usability. Key closures include the long-standing task to implement service types ([#4914](https://github.com/elizaos/eliza/issues/4914]) and a fix for the dev server not terminating correctly ([#5559](https://github.com/elizaos/eliza/issues/5559]). Several issues related to plugin installation ([#4861](https://github.com/elizaos/eliza/issues/4861]), build processes ([#5555](https://github.com/elizaos/eliza/pull/5555]), and Windows-specific crashes ([#5161](https://github.com/elizaos/eliza/issues/5161), [#5499](https://github.com/elizaos/eliza/issues/5499]) were also addressed.\n\n- **New & Active Issues:** The most notable new development is the detailed planning for a **Scenario Runner**. A series of issues ([#5573](https://github.com/elizaos/eliza/issues/5573) - [#5579](https://github.com/elizaos/eliza/issues/5579)) were created to track the implementation of this new agent evaluation framework, covering everything from the CLI command to YAML parsing, sandboxed execution, and reporting. Other new issues highlight challenges with agent-to-agent communication ([#5584](https://github.com/elizaos/eliza/issues/5584]), custom plugin schema migrations ([#5588](https://github.com/elizaos/eliza/issues/5588]), and a community request for a Zapper plugin ([#5600](https://github.com/elizaos/eliza/issues/5600)). An ongoing discussion continues around Twitter API rate limits ([#38](https://github.com/elizaos/eliza/issues/38)), with users on free tiers still facing \"Too Many Requests\" errors.\n\n## \ud83d\udcac Community & Collaboration\nThe week's activity points to strong, coordinated development efforts. The systematic breakdown of the new Scenario Runner feature into a well-defined epic suggests a high degree of planning and collaboration among the core team. Community engagement is visible in the ongoing discussion around the Twitter API rate limit issue ([#38](https://github.com/elizaos/eliza/issues/38)), where users are actively providing feedback and sharing their experiences with different subscription tiers. The request for a new Zapper plugin ([#5600](https://github.com/elizaos/eliza/issues/5600)) also signals active interest from the community in expanding the project's integration capabilities.\n---\n2025-07-01.md\n---\n# elizaos/eliza Monthly Report (July 2025)\n\n## \ud83d\ude80 Highlights\nJuly was a month of significant refinement and foundational enhancement for ElizaOS. A major push was made to overhaul the Web UI, bringing components like the chat interface, agent cards, and sidebars into alignment with new Figma designs for a more polished user experience. The Command Line Interface (CLI) saw extensive stabilization, with a focus on cross-platform consistency, particularly on Windows, and a standardized user interaction model using `@clack/prompts`. Architecturally, the introduction of action chaining and standardized service types has paved the way for more complex, modular agent behaviors. Finally, the team kicked off a major new initiative: the Scenario Runner, a framework for evaluating agent performance in sandboxed environments.\n\n## \ud83d\udee0\ufe0f Key Developments\nWork this month spanned the entire stack, from core architecture and developer tooling to end-user interfaces.\n\n#### **UI/UX Overhaul and Modernization**\nA concerted effort was made to align the client application with official Figma designs, resulting in a more professional and cohesive user experience.\n- **Component Redesigns:** Key components were refactored to match design specifications, including the Agent Card ([#5344](https://github.com/elizaos/eliza/pull/5344), [#5351](https://github.com/elizaos/eliza/pull/5351)), Chat component ([#5349](https://github.com/elizaos/eliza/pull/5349)), Sidebar ([#5373](https://github.com/elizaos/eliza/pull/5373)), and DM chat headers ([#5392](https://github.com/elizaos/eliza/pull/5392)).\n- **UX Improvements:** Functionality was enhanced with an auto-resizing chat input ([#5546](https://github.com/elizaos/eliza/pull/5546]), a unified confirmation modal hook to replace native browser dialogs ([#5444](https://github.com/elizaos/eliza/pull/5444]), and improved navigation logic for creating new chats ([#5398](https://github.com/elizaos/eliza/pull/5398)).\n- **Performance & Stability:** The default avatar was optimized for faster loading ([#5350](https://github.com/elizaos/eliza/pull/5350]), and numerous UI glitches, hydration errors, and styling inconsistencies were resolved ([#5379](https://github.com/elizaos/eliza/pull/5379), [#5475](https://github.com/elizaos/eliza/pull/5475)).\n\n#### **CLI Enhancements and Stabilization**\nThe CLI received significant attention to improve usability, reliability, and consistency across platforms.\n- **Standardized Prompts:** The CLI was migrated to use `@clack/prompts` for a consistent and modern user interaction experience ([#5359](https://github.com/elizaos/eliza/pull/5359)).\n- **Command Reliability:** The `create` and `update` commands were made more robust, fixing issues with directory handling, type display, and preventing file creation outside project directories ([#5321](https://github.com/elizaos/eliza/pull/5321), [#5427](https://github.com/elizaos/eliza/pull/5427)).\n- **Cross-Platform Fixes:** Numerous bugs affecting Windows users were addressed, including plugin loading failures ([#5416](https://github.com/elizaos/eliza/pull/5416), [#5437](https://github.com/elizaos/eliza/pull/5437]) and test failures ([#5405](https://github.com/elizaos/eliza/pull/5405)).\n- **SPA Routing:** Issues with SPA routing for globally installed CLI instances were resolved, ensuring that refreshing on non-home routes works correctly ([#5479](https://github.com/elizaos/eliza/pull/5479)).\n\n#### **Core Framework and Agent Capabilities**\nFoundational work was completed to expand the core capabilities of the agent framework.\n- **Action Chaining:** A major new feature was implemented to allow sequential execution of agent actions with state management, enabling more complex, multi-step tasks ([#5436](https://github.com/elizaos/eliza/pull/5436)).\n- **Service Architecture:** The runtime was enhanced with standardized service types and a `getServicesByType()` method, providing a more modular way to build and retrieve agent capabilities ([#5565](https://github.com/elizaos/eliza/pull/5565)).\n- **New Features:** A `generateImageAction` was added to the agent pipeline ([#5446](https://github.com/elizaos/eliza/pull/5446]), and a new `forms` plugin was introduced to serve as a dependency for building forms ([#5487](https://github.com/elizaos/eliza/pull/5487)).\n\n#### **Developer Experience and Tooling**\nSeveral initiatives were completed to streamline the development and testing workflow for contributors.\n- **Automated Workflows:** The Claude-powered code review workflow was enhanced with more permissions and security checks ([#5519](https://github.com/elizaos/eliza/pull/5519), [#5570](https://github.com/elizaos/eliza/pull/5570]), and a new automated daily code quality analysis workflow was implemented ([#5532](https://github.com/elizaos/eliza/pull/5532]).\n- **Improved Tooling:** A new `@elizaos/test-utils` package was created to provide a `MockRuntime` for easier testing ([#5507](https://github.com/elizaos/eliza/pull/5507]). A unified `configs` package was added for shared linting and TypeScript configurations ([#5508](https://github.com/elizaos/eliza/pull/5508]).\n- **Plugin Development:** An AI-powered migration tool was introduced to help upgrade v0.x plugins ([#5311](https://github.com/elizaos/eliza/pull/5311]), and a new `plugin-quick-starter` template was added for backend-only plugins ([#5589](https://github.com/elizaos/eliza/pull/5589)).\n- **Dev Server:** The development server was improved to auto-build on `elizaos start` ([#5504](https://github.com/elizaos/eliza/pull/5504]) and to shut down gracefully on `Cmd+C` ([#5562](https://github.com/elizaos/eliza/pull/5562]).\n\n## \ud83d\udc1b Issues & Triage\n- **Closed Issues:** A significant number of issues were resolved, reflecting the month's focus on stabilization and refinement. Key resolutions include numerous fixes for plugin loading and CLI command failures on Windows ([#5407](https://github.com/elizaos/eliza/issues/5407), [#5499](https://github.com/elizaos/eliza/issues/5499]), correction of REST API documentation inaccuracies ([#5370](https://github.com/elizaos/eliza/issues/5370]), and the resolution of inconsistent testing behavior across the monorepo ([#5218](https://github.com/elizaos/eliza/issues/5218]). The closure of the long-standing issue to implement service types ([#4914](https://github.com/elizaos/eliza/issues/4914)) marked a major architectural milestone.\n\n- **New & Active Issues:** The most notable new work is the comprehensive plan for the **Scenario Runner**, broken down into a series of well-defined issues ([#5573](https://github.com/elizaos/eliza/issues/5573) - [#5579](https://github.com/elizaos/eliza/issues/5579]). This represents the next major feature for the project. The new automated code quality workflow began to proactively file issues related to dead code and potential security concerns ([#5542](https://github.com/elizaos/eliza/issues/5542), [#5545](https://github.com/elizaos/eliza/issues/5545)), streamlining maintenance. An ongoing discussion around Twitter API rate limits in issue [#38](https://github.com/\n---\n{\n \"interval\": {\n \"intervalStart\": \"2025-07-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-08-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-07-01 to 2025-08-01, elizaos/eliza had 222 new PRs (186 merged), 50 new issues, and 33 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs6_wA-H\",\n \"title\": \"Plugin-local-ai failing to load on Windows\",\n \"author\": \"SYMBaiEX\",\n \"number\": 5499,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\n[2025-07-09 20:16:04] WARN: Failed to load plugin module '@elizaos/plugin-local-ai' using all relevant strategies.\\n[2025-07-09 20:16:04] INFO: Plugin @elizaos/plugin-local-ai not available, installing...\\n[2025-07-09 20:16:04] WARN: Failed to load plugin module '@elizaos/plugin-local-ai' using all relevant strategies.\\n[2025-07-09 20:16:04] WARN: Plugin @elizaos/plugin-local-ai installed from npm with potential GitHub fallback but could not be loaded/verified.\\n[2025-07-09 20:16:04] WARN: Failed to load plugin module '@elizaos/plugin-local-ai' using all relevant strategies.\\n[2025-07-09 20:16:04] ERROR: Failed to load module for plugin @elizaos/plugin-local-ai.\\n[2025-07-09 20:16:04] INFO: Final plugins being loaded: @elizaos/plugin-sql, bootstrap\\n\\n**To Reproduce**\\n\\nUse Windows. Clean Install, select PGLite, Select Local AI, cd to the dir, elizaos start (or dev)\\n\\n**Expected behavior**\\n\\nplugin-local-ai should load properly\\n\\n**Screenshots**\\n\\n\\\"Image\\\"\\n\\n**Additional context**\\n\\n\",\n \"createdAt\": \"2025-07-09T20:17:29Z\",\n \"closedAt\": \"2025-07-13T16:15:29Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 4\n },\n {\n \"id\": \"I_kwDOMT5cIs67xrH_\",\n \"title\": \"@elizaos/cli test command incorrectly requires monorepo root for standalone projects\",\n \"author\": \"sicco-moonbeam\",\n \"number\": 5142,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nThe elizaos test command incorrectly assumes that E2E tests must be run from within the ElizaOS monorepo structure, even when running tests for standalone projects created with `elizaos create`. This prevents running E2E tests in standalone projects that are meant to extend ElizaOS functionality.\\n\\n\\n**To Reproduce**\\n\\n1. Create a new ElizaOS project\\n```elizaos create my-project```\\n\\n2. Run the e2e tests:\\n\\n```npm run test:e2e```\\n\\n3. Error: Could not find monorepo root. Make sure to run tests from within the Eliza project.\\n\\n**Expected behavior**\\n\\nThe elizaos test command should:\\n1. Recognize standalone projects created with elizaos create\\n2. Run E2E tests in the project's e2e/ directory\\n3. Not require the full ElizaOS monorepo structure\\n\\n**Screenshots**\\n\\nN/A\\n\\n**Additional context**\\n\\n- Error is reliably reproducible with any \\\"out-of-the-box\\\" project created with @elizaos/cli\\n\\n\",\n \"createdAt\": \"2025-06-16T15:05:03Z\",\n \"closedAt\": \"2025-07-13T16:50:31Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs68o4X0\",\n \"title\": \"server\",\n \"author\": \"furkannabisumji\",\n \"number\": 5230,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"{\\n \\\"success\\\": false,\\n \\\"error\\\": {\\n \\\"message\\\": \\\"API endpoint not found\\\",\\n \\\"code\\\": 404\\n }\\n}\\nin all endpoints including health only get agents is working \",\n \"createdAt\": \"2025-06-21T06:56:44Z\",\n \"closedAt\": \"2025-07-13T16:51:00Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs69hVkJ\",\n \"title\": \"Migrate remaining CLI input methods to use @clack/prompts for consistency\",\n \"author\": \"wtfsayo\",\n \"number\": 5295,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"# Migrate remaining CLI input methods to use @clack/prompts for consistency\\n\\n## \ud83c\udfaf Summary\\n\\nCurrently, the CLI uses a mix of input libraries (`inquirer`, Bun's global `prompt()`, and `@clack/prompts`). We should standardize on `@clack/prompts` for a consistent user experience and better styling across all CLI interactions.\\n\\n## \ud83d\udccb Current State\\n\\nMost of the CLI already uses `@clack/prompts` properly, but there are **2 main files** still using other input methods:\\n\\n### 1. `src/utils/plugin-creator.ts` - Using `inquirer` \ud83d\udce6\\n\\nThis file has multiple `inquirer.prompt()` calls that need to be migrated:\\n\\n- **Plugin specification collection** (~line 172-290):\\n - Plugin name input\\n - Plugin description input \\n - Plugin features input\\n - Component selection (checkbox)\\n - Action names input\\n - Provider names input\\n - Evaluator names input\\n - Service names input\\n\\n### 2. `scripts/generate-unit-tests.ts` - Using global `prompt()` \ud83d\udd27\\n\\n- **Test generation confirmation** (~line 165):\\n ```typescript\\n const answer = prompt('Generate tests? (y/n): ');\\n ```\\n\\n## \u2728 Benefits of Migration\\n\\n1. **Consistent UX** - All CLI interactions will have the same look and feel\\n2. **Better styling** - Clack provides superior visual design and animations\\n3. **Better error handling** - Clack has built-in cancellation handling\\n4. **Reduced dependencies** - Can remove `inquirer` from package.json\\n5. **Type safety** - Better TypeScript integration\\n\\n## \ud83d\udd27 Implementation Examples\\n\\n### For `plugin-creator.ts`:\\n\\n**Before (inquirer):**\\n```typescript\\nconst answers = await inquirer.prompt([\\n {\\n type: 'input',\\n name: 'name',\\n message: 'Plugin name (without \\\"plugin-\\\" prefix):',\\n validate: (input: string) => input.length > 0 || 'Plugin name is required'\\n }\\n]);\\n```\\n\\n**After (clack):**\\n```typescript\\nconst name = await clack.text({\\n message: 'Plugin name (without \\\"plugin-\\\" prefix):',\\n validate: (input) => input.length > 0 ? undefined : 'Plugin name is required'\\n});\\n\\nif (clack.isCancel(name)) {\\n clack.cancel('Operation cancelled.');\\n process.exit(0);\\n}\\n```\\n\\n### For `generate-unit-tests.ts`:\\n\\n**Before:**\\n```typescript\\nconst answer = prompt('Generate tests? (y/n): ');\\n```\\n\\n**After:**\\n```typescript\\nconst answer = await clack.confirm({\\n message: 'Generate tests?',\\n initialValue: true\\n});\\n\\nif (clack.isCancel(answer)) {\\n console.log('Cancelled.');\\n return;\\n}\\n```\\n\\n## \u2705 Reference Files (Already Using Clack)\\n\\nThese files are already properly implemented and serve as good examples:\\n- `src/commands/create/actions/creators.ts`\\n- `src/commands/create/index.ts`\\n- `src/commands/env/actions/edit.ts`\\n- `src/commands/publish/utils/validation.ts`\\n- `src/utils/cli-prompts.ts`\\n\\n## \u2705 Acceptance Criteria\\n\\n- [ ] Replace all `inquirer.prompt()` calls in `plugin-creator.ts` with clack equivalents\\n- [ ] Replace global `prompt()` call in `generate-unit-tests.ts` with clack\\n- [ ] Remove `inquirer` dependency from `package.json` if no longer used elsewhere\\n- [ ] Ensure all prompts handle cancellation properly (ctrl+c)\\n- [ ] Test plugin creation flow works identically to current behavior\\n- [ ] Test unit test generation script works identically to current behavior\\n- [ ] Maintain existing validation logic and error messages\\n- [ ] Update any related TypeScript types if needed\\n\\n## \ud83c\udfaf Priority\\n\\n**Medium** - This improves developer experience and code consistency but doesn't affect core functionality.\\n\\n## \ud83d\udca1 Implementation Notes\\n\\n- The `generate-unit-tests.ts` part would be a good **beginner-friendly** task\\n- The `plugin-creator.ts` part is more complex due to multiple sequential prompts\\n- Consider breaking this into two separate PRs if needed\\n- Make sure to test the checkbox selection for component types in plugin creation\\n\\n---\\n\\n**Note**: The majority of the CLI already uses clack properly - this is just cleaning up the last few stragglers to ensure complete consistency across the entire CLI experience.\",\n \"createdAt\": \"2025-06-26T16:14:01Z\",\n \"closedAt\": \"2025-07-04T07:16:46Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs6-8v4Z\",\n \"title\": \"Fails to load @elizaos/plugin-openai and @elizaos/plugin-bootstrap on Windows\",\n \"author\": \"gcbsumid\",\n \"number\": 5407,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\nOn 1.0.17, when I run `elizaos dev` on windows (powershell 7), it tries to load openai plugin (1.0.6) and bootstrap (1.0.15) but it fails to do so using all relevant strategies. It tries to install the plugin, succeeds to install, but fails to load it still.\\n\\nBecause it can't load openai and bootstrap plugin, it doesn't process any messages sent to it.\\n\\nHowever, it's able to find @elizaos/plugin-sql so I'm not sure what the difference is.\\n\\n**To Reproduce**\\nOn windows (powershell 7), create a new project and run 'elizaos dev'\\n\\n\\n**Expected behavior**\\n\\nI expect it to load the plugins so that it can handle the messages send from the chat.\\n\\n**Screenshots**\\n\\n\\\"Image\\\"\\n\\n**Additional context**\\n\\nI'm on Windows Powershell 7. WSL is installed. I don't have this issue when I run it on my Ubuntu Linux VM.\\n\\nI cloned the eliza repo and ran 'bun install', 'bun run build' and 'bun start' and it's able to load everything on Windows Powershell 7. So it seems this is only failing when I try running the elizaos commands from a project, but not from the eliza repo itself.\",\n \"createdAt\": \"2025-07-04T19:49:49Z\",\n \"closedAt\": \"2025-07-08T10:04:53Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6dzp_i\",\n \"title\": \"Feat/migrate docs to fumadocs\",\n \"author\": \"SYMBaiEX\",\n \"number\": 5435,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-07-07T18:23:11Z\",\n \"mergedAt\": null,\n \"additions\": 54767,\n \"deletions\": 1\n },\n {\n \"id\": \"PR_kwDOMT5cIs6aFGnn\",\n \"title\": \"feat: updated plugin migrator\",\n \"author\": \"samarth30\",\n \"number\": 5066,\n \"body\": \"This pull request introduces several enhancements and new features to the plugin migration system, focusing on improving test generation, repository analysis, and environment variable management. The most significant changes include the introduction of a context-aware test generation system, updates to repository analysis logic, and improvements to environment variable prompting. Additionally, configuration constants and export structure have been updated for better maintainability.\\r\\n\\r\\n### Context-Aware Test Generation\\r\\n* Added a new system for generating plugin-specific tests dynamically based on the plugin's actual structure and functionality. This replaces the old static template system, ensuring more relevant and accurate tests. (`CONTEXT_AWARE_TESTING.md`)\\r\\n\\r\\n### Repository Analysis Enhancements\\r\\n* Implemented a repository analyzer that scans a plugin's directory for key files (`README.md`, `package.json`, `index.ts/js`) and source files while respecting token limits and skipping large or binary files. (`repository-analyzer.ts`)\\r\\n\\r\\n### Environment Variable Management\\r\\n* Introduced `EnvPrompter`, a utility for interactive collection and validation of environment variables, with support for sensitive values and default descriptions. (`env-prompter.ts`)\\r\\n\\r\\n### Configuration Updates\\r\\n* Added new configuration constants for migration, including `MAX_TOKENS`, `CLAUDE_CODE_TIMEOUT`, and `MIN_DISK_SPACE_GB`, to centralize and standardize settings. (`config.ts`)\\r\\n\\r\\n### Export Structure Improvements\\r\\n* Updated the export structure in `index.ts` to include new components like `EnvPrompter`, `ContextAwareTestGenerator`, and configuration constants, ensuring better modularity and accessibility. (`index.ts`)\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-06-11T18:02:27Z\",\n \"mergedAt\": null,\n \"additions\": 46293,\n \"deletions\": 1326\n },\n {\n \"id\": \"PR_kwDOMT5cIs6eZi5-\",\n \"title\": \"Feat: Autocoder + e2b sandboxes\",\n \"author\": \"lalalune\",\n \"number\": 5520,\n \"body\": \"This PR adds a refactored autocoder plugin as well as the new github and e2b plugins.\\r\\n\\r\\nInstead of merging this in, we should verify we're happy with this and then probably push it out to its own repo (along with plugin deps).\\r\\n\\r\\nHowever, for arch design reasons, nice to do it in the monorepo and work here while we polish it.\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-07-11T00:32:15Z\",\n \"mergedAt\": null,\n \"additions\": 44135,\n \"deletions\": 0\n },\n {\n \"id\": \"PR_kwDOMT5cIs6doDDm\",\n \"title\": \"chore: 1.0.18\",\n \"author\": \"wtfsayo\",\n \"number\": 5419,\n \"body\": \"## Summary\\n- Merging latest changes from develop branch into main\\n\\n## Changes included\\n- All commits from develop branch since last merge\\n\\n\ud83e\udd16 Generated with [Claude Code](https://claude.ai/code)\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-07-06T11:19:58Z\",\n \"mergedAt\": \"2025-07-07T04:35:03Z\",\n \"additions\": 28125,\n \"deletions\": 1569\n },\n {\n \"id\": \"PR_kwDOMT5cIs6dn_9z\",\n \"title\": \"chore: 1.0.18\",\n \"author\": \"wtfsayo\",\n \"number\": 5417,\n \"body\": \"## Summary\\n\u2022 Merging latest changes from develop branch into main\\n\u2022 Includes all recent commits and updates\\n\\n## Changes\\nThis PR merges all changes from the develop branch into main.\\n\\n\ud83e\udd16 Generated with [Claude Code](https://claude.ai/code)\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-07-06T11:06:53Z\",\n \"mergedAt\": null,\n \"additions\": 27799,\n \"deletions\": 1420\n }\n ],\n \"codeChanges\": {\n \"additions\": 91892,\n \"deletions\": 50044,\n \"files\": 570,\n \"commitCount\": 864\n },\n \"completedItems\": [\n {\n \"title\": \"Feature: Add ELIZA_UI_ENABLE environment variable to toggle Web UI availability\",\n \"prNumber\": 5304,\n \"type\": \"feature\",\n \"body\": \"# Add ELIZA_UI_ENABLE environment variable to control web UI in production\\r\\n\\r\\n## Problem\\r\\n\\r\\nelizaOS currently serves the web UI to anyone who can reach the server. While there's `ELIZA_SERVER_AUTH_TOKEN` for API endpoints, the web interface\",\n \"files\": [\n \".env.example\",\n \"bun.lock\",\n \"packages/plugin-sql/package.json\",\n \"packages/server/src/__tests__/basic-functionality.test.ts\",\n \"packages/server/src/__tests__/ui-disable-feature.test.ts\",\n \"packages/server/src/index.ts\"\n ]\n },\n {\n \"title\": \"feat: plugins upgrade with claude code\",\n \"prNumber\": 5311,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **New Features**\\n * Introduced an AI-powered migration tool for upgrading ElizaOS plugins from version 0.x to 1.x, featuring a stepwi\",\n \"files\": [\n \"bun.lock\",\n \"packages/cli/package.json\",\n \"packages/cli/src/commands/plugins/actions/upgrade.ts\",\n \"packages/cli/src/commands/plugins/index.ts\",\n \"packages/cli/src/commands/plugins/types.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-0-branch.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-1-analysis.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-2-setup.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-3-build.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-4-typescript.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-5-migration.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-6-tests.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-7-final.ts\",\n \"packages/cli/src/utils/upgrade/gates/gate-8-verify.ts\",\n \"packages/cli/src/utils/upgrade/gates/index.ts\",\n \"packages/cli/src/utils/upgrade/migration-guide-loader.ts\",\n \"packages/cli/src/utils/upgrade/progress-reporter.ts\",\n \"packages/cli/src/utils/upgrade/sdk-migration-agent.ts\",\n \"packages/cli/src/utils/upgrade/simple-migration-agent.ts\",\n \"packages/cli/src/utils/upgrade/types.ts\",\n \"packages/cli/src/utils/upgrade/utils/file-tracker.ts\",\n \"packages/cli/src/utils/upgrade/utils/git-utils.ts\",\n \"packages/cli/src/utils/upgrade/utils/validation.ts\",\n \"packages/docs/docs/plugins/migration/claude-code/advanced-migration-guide.md\",\n \"packages/docs/docs/plugins/migration/claude-code/completion-requirements.md\",\n \"packages/docs/docs/plugins/migration/claude-code/integrated-migration-loop.md\",\n \"packages/docs/docs/plugins/migration/claude-code/migration-guide.md\",\n \"packages/docs/docs/plugins/migration/claude-code/prompt-and-generation-guide.md\",\n \"packages/docs/docs/plugins/migration/claude-code/state-and-providers-guide.md\",\n \"packages/docs/docs/plugins/migration/claude-code/testing-guide.md\",\n \"packages/cli/src/utils/upgrade/CLAUDE.md\",\n \"packages/cli/src/utils/upgrade/migrator.ts\",\n \"packages/cli/tsup.config.ts\"\n ]\n },\n {\n \"title\": \"chore: update agent secrets when they are empty with local vars\",\n \"prNumber\": 5329,\n \"type\": \"other\",\n \"body\": \"## Summary\\r\\n\\r\\nAdd automatic synchronization of secrets from local `.env` file for characters that don't have secrets configured.\\r\\n\\r\\n## Context\\r\\n\\r\\nWhen characters are stored in the database or loaded from files, they often lack secrets for s\",\n \"files\": [\n \"packages/cli/src/commands/start/actions/agent-start.ts\",\n \"packages/cli/src/commands/start/utils/config-utils.ts\"\n ]\n },\n {\n \"title\": \"feat: clack env prompts cli, major refactor of cli envs\",\n \"prNumber\": 5326,\n \"type\": \"feature\",\n \"body\": \"## \ud83d\udd27 CLI Environment System Improvements\\r\\n\\r\\nThis PR significantly improves the CLI environment variable system, making it more maintainable, user-friendly, and feature-rich.\\r\\n\\r\\n### \ud83c\udfaf Summary of Changes\\r\\n\\r\\n#### 1. **Enhanced Plugin Environ\",\n \"files\": [\n \"packages/cli/src/commands/env/utils/file-operations.ts\",\n \"packages/cli/src/commands/plugins/actions/install.ts\",\n \"packages/cli/src/commands/plugins/utils/env-vars.ts\",\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/src/services/env-file.service.ts\",\n \"packages/cli/src/services/index.ts\",\n \"packages/cli/src/types/index.ts\",\n \"packages/cli/src/utils/config-manager.ts\",\n \"packages/cli/src/utils/env-prompt.ts\",\n \"packages/cli/src/utils/index.ts\",\n \"packages/cli/tests/unit/commands/test/e2e-tests.test.ts\",\n \"packages/client/src/lib/info.json\",\n \"packages/cli/src/services/__tests__/env-file.service.test.ts\"\n ]\n },\n {\n \"title\": \"fix: cli create command directory display and cleanup on interruption\",\n \"prNumber\": 5321,\n \"type\": \"bugfix\",\n \"body\": \"# Fix CLI create command directory display and cleanup on interruption\\r\\n\\r\\n## Problem\\r\\n\\r\\nTwo minor bugs with the `elizaos create` command:\\r\\n\\r\\n1. **Confusing directory display**: When creating a project/plugin, the confirmation prompt showed \",\n \"files\": [\n \"packages/cli/src/commands/create/actions/creators.ts\",\n \"packages/cli/src/commands/create/actions/setup.ts\",\n \"packages/cli/src/utils/build-project.ts\",\n \"packages/cli/src/utils/helpers.ts\",\n \"packages/cli/tests/commands/create.test.ts\",\n \"packages/cli/src/commands/create/index.ts\"\n ]\n },\n {\n \"title\": \"fix: handle unwrapped server responses in BaseApiClient\",\n \"prNumber\": 5343,\n \"type\": \"bugfix\",\n \"body\": \"## Fix: Handle unwrapped server responses in BaseApiClient\\r\\n\\r\\n### Problem\\r\\n- Calls to Server routes through api-client (`/api/server/health`, `/api/server/ping`, `/api/server/status`) were failing with \\\"Unknown error\\\"\\r\\n- Manual requests to \",\n \"files\": [\n \"packages/api-client/src/lib/base-client.ts\",\n \"packages/api-client/src/__tests__/base-client.test.ts\"\n ]\n },\n {\n \"title\": \"feat(client): Restructure character form action buttons layout\",\n \"prNumber\": 5342,\n \"type\": \"feature\",\n \"body\": \"## Description\\n\\nThis PR restructures the character form action buttons to improve the user experience and visual layout.\\n\\n## Changes Made\\n\\n### Layout Improvements\\n- **Horizontal Layout**: Replaced vertical stacked buttons with horizontal la\",\n \"files\": [\n \"bun.lock\",\n \"packages/api-client/src/types/agents.ts\",\n \"packages/client/src/components/agent-creator.tsx\",\n \"packages/client/src/components/character-form.tsx\"\n ]\n },\n {\n \"title\": \"fix: simplify .env file creation to use template only\",\n \"prNumber\": 5340,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- Remove automatic merging of process.env variables into .env file\\n- Use clean template without runtime environment pollution\\n- Prevent .env file from becoming cluttered with unrelated variables\\n\\n## Problem\\nThe previous implement\",\n \"files\": [\n \"packages/cli/src/utils/get-config.ts\"\n ]\n },\n {\n \"title\": \"fix: gui version resolve\",\n \"prNumber\": 5339,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **New Features**\\n * The app sidebar now displays the server version dynamically, fetched from the server.\\n * Added a new server endp\",\n \"files\": [\n \"bun.lock\",\n \"eliza.postman.json\",\n \"lerna.json\",\n \"package.json\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/app/src-tauri/tauri.conf.json\",\n \"packages/autodoc/package.json\",\n \"packages/cli/package.json\",\n \"packages/client/.gitignore\",\n \"packages/client/package.json\",\n \"packages/client/src/components/app-sidebar.tsx\",\n \"packages/client/src/hooks/use-server-version.tsx\",\n \"packages/client/src/hooks/use-version.tsx\",\n \"packages/client/src/lib/info.json\",\n \"packages/client/vite.config.ts\",\n \"packages/core/package.json\",\n \"packages/create-eliza/package.json\",\n \"packages/docs/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-starter/package.json\",\n \"packages/project-starter/package.json\",\n \"packages/project-tee-starter/package.json\",\n \"packages/server/examples/package.json\",\n \"packages/server/package.json\",\n \"packages/server/src/api/system/__tests__/version.test.ts\",\n \"packages/server/src/api/system/index.ts\",\n \"packages/server/src/api/system/version.ts\"\n ]\n },\n {\n \"title\": \"fix: (cli) show correct type in create command messages\",\n \"prNumber\": 5337,\n \"type\": \"bugfix\",\n \"body\": \"## Description\\r\\n\\r\\nUpdates the CLI create command to display the correct type (Plugin/Agent/TEE Project) in prompts instead of always showing \\\"Project\\\".\\r\\n\\r\\n## Changes\\r\\n\\r\\n- Dynamic intro message based on `--type` flag\\r\\n- Type-specific success\",\n \"files\": [\n \"packages/cli/src/commands/create/index.ts\"\n ]\n },\n {\n \"title\": \"fix: auto-install AI model plugins on project creation\",\n \"prNumber\": 5335,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\r\\n\\r\\nWhen creating a new project with `elizaos create`, selecting an AI model (e.g., OpenAI, Claude) would:\\r\\n- \u2705 Store the API key in `.env`\\r\\n- \u2705 Report successful configuration\\r\\n- \u274c **NOT** install the corresponding plugin package\",\n \"files\": [\n \"packages/cli/src/commands/create/actions/setup.ts\"\n ]\n },\n {\n \"title\": \"feat: tweak agent card\",\n \"prNumber\": 5351,\n \"type\": \"feature\",\n \"body\": \"This PR refines the Agent Card to match the Figma design more closely.\\r\\n\\r\\nbefore:\\r\\n\\r\\n\\r\\n\\\"Screenshot\\r\\n\\r\\naf\",\n \"files\": [\n \"packages/client/src/components/agent-card.tsx\",\n \"packages/client/src/components/ui/switch.tsx\",\n \"packages/client/src/routes/home.tsx\"\n ]\n },\n {\n \"title\": \"fix: update eliza avatar\",\n \"prNumber\": 5350,\n \"type\": \"bugfix\",\n \"body\": \"Currently, we are using a large image for the default Eliza avatar, which makes the app load slowly. Since we only need a reasonable resolution for avatars, this PR:\\r\\n\\r\\nResizes the default Eliza avatar to 512x512, which is sufficient for UI\",\n \"files\": [\n \"packages/client/public/elizaos-avatar.png\",\n \"packages/client/src/components/avatar-panel.tsx\",\n \"packages/client/src/constants.ts\"\n ]\n },\n {\n \"title\": \"feat: chat refactor\",\n \"prNumber\": 5349,\n \"type\": \"feature\",\n \"body\": \"This PR refactors the Chat component, including the chat bubble and chat view, to align with the new Figma design. Please note that the group chat design is not finalized yet and will be refactored in a separate PR once the design is comple\",\n \"files\": [\n \"packages/client/src/components/ChatMessageListComponent.tsx\",\n \"packages/client/src/components/chat.tsx\",\n \"packages/client/src/components/retry-button.tsx\",\n \"packages/client/src/components/ui/button.cy.tsx\",\n \"packages/client/src/components/ui/button.tsx\",\n \"packages/client/src/components/ui/chat/chat-bubble.tsx\",\n \"packages/client/src/components/ui/chat/chat-message-list.tsx\",\n \"packages/client/src/components/ui/chat/chat-tts-button.tsx\"\n ]\n },\n {\n \"title\": \"chore: improve logs\",\n \"prNumber\": 5348,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **New Features**\\n * Added visual spinner animations to indicate progress during migrations.\\n * Introduced real-time tracking and dis\",\n \"files\": [\n \"packages/cli/src/utils/upgrade/simple-migration-agent.ts\"\n ]\n },\n {\n \"title\": \"fix(client): resolve all type issues in home.tsx for complete type safety\",\n \"prNumber\": 5346,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR fixes all TypeScript type issues in the home.tsx file to ensure complete type safety.\\n\\n## Changes\\n\\n- Use enum instead of string literals for status comparison\\n- Add proper type imports for and \\n- Add explicit type anno\",\n \"files\": [\n \"packages/client/src/components/add-agent-card.tsx\",\n \"packages/client/src/components/agent-card.tsx\",\n \"packages/client/src/routes/home.tsx\"\n ]\n },\n {\n \"title\": \"feat: update agent settings UI to match design specifications\",\n \"prNumber\": 5345,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\n- Updated dark theme colors for better contrast and visual consistency\\n- Fixed form field styling with proper border radius (4px) and increased spacing\\n- Restructured form element order to follow design pattern: label \u2192 input \u2192 \",\n \"files\": [\n \"packages/client/src/components/agent-settings.tsx\",\n \"packages/client/src/components/array-input.tsx\",\n \"packages/client/src/components/character-form.tsx\",\n \"packages/client/src/components/plugins-panel.tsx\",\n \"packages/client/src/components/secret-panel.tsx\",\n \"packages/client/src/components/ui/input.tsx\",\n \"packages/client/src/components/ui/label.cy.tsx\",\n \"packages/client/src/components/ui/label.tsx\",\n \"packages/client/src/components/ui/select.tsx\",\n \"packages/client/src/components/ui/tabs.tsx\",\n \"packages/client/src/components/ui/textarea.cy.tsx\",\n \"packages/client/src/components/ui/textarea.tsx\",\n \"packages/client/src/hooks/use-elevenlabs-voices.ts\",\n \"packages/client/src/hooks/use-server-version.tsx\",\n \"packages/client/src/index.css\",\n \"packages/client/src/routes/agent-settings.tsx\"\n ]\n },\n {\n \"title\": \"feat: redesign Agent Cards Homepage Layout\",\n \"prNumber\": 5344,\n \"type\": \"feature\",\n \"body\": \"## \ud83c\udfa8 UI Redesign: Agent Cards Homepage\\n\\nThis PR redesigns the agent cards on the client homepage to match the target design specification.\\n\\n### \ud83d\udccb Changes Made\\n\\n#### **AgentCard Component**\\n- \u2705 **Layout**: Changed from square/vertical to h\",\n \"files\": [\n \"bun.lock\",\n \"packages/client/package.json\",\n \"packages/client/src/components/add-agent-card.tsx\",\n \"packages/client/src/components/agent-card.tsx\",\n \"packages/client/src/components/ui/switch.tsx\",\n \"packages/client/src/routes/home.tsx\"\n ]\n },\n {\n \"title\": \"chore: v1.0.17\",\n \"prNumber\": 5385,\n \"type\": \"other\",\n \"body\": \"Version 1.0.17 release\",\n \"files\": [\n \".env.example\",\n \"bun.lock\",\n \"eliza.postman.json\",\n \"lerna.json\",\n \"package.json\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/app/src-tauri/tauri.conf.json\",\n \"packages/autodoc/package.json\",\n \"packages/cli/package.json\",\n \"packages/cli/src/utils/upgrade/simple-migration-agent.ts\",\n \"packages/client/cypress/e2e/01-home-page.cy.ts\",\n \"packages/client/cypress/e2e/02-chat-functionality.cy.ts\",\n \"packages/client/package.json\",\n \"packages/client/src/components/ChatMessageListComponent.tsx\",\n \"packages/client/src/components/agent-card.tsx\",\n \"packages/client/src/components/agent-creator.tsx\",\n \"packages/client/src/components/agent-settings.tsx\",\n \"packages/client/src/components/app-sidebar.tsx\",\n \"packages/client/src/components/character-form.tsx\",\n \"packages/client/src/components/chat.tsx\",\n \"packages/client/src/components/group-card.tsx\",\n \"packages/client/src/components/ui/switch.tsx\",\n \"packages/client/src/routes/home.tsx\",\n \"packages/core/package.json\",\n \"packages/create-eliza/package.json\",\n \"packages/docs/docs/rest/complete-message.api.mdx\",\n \"packages/docs/docs/rest/ingest-external-message.api.mdx\",\n \"packages/docs/docs/rest/send-message.api.mdx\",\n \"packages/docs/docs/rest/submit-message.api.mdx\",\n \"packages/docs/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-starter/package.json\",\n \"packages/project-starter/package.json\",\n \"packages/project-tee-starter/package.json\",\n \"packages/server/examples/package.json\",\n \"packages/server/package.json\",\n \"packages/server/src/api/index.ts\"\n ]\n },\n {\n \"title\": \"fix: remove duplicate express.json middleware in API router\",\n \"prNumber\": 5384,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- Removes redundant express.json middleware that was causing duplicate JSON parsing in the API router\\n- This was creating unnecessary overhead and potential conflicts in request processing\\n\\n## Test plan\\n- [x] Verify API endpoints\",\n \"files\": [\n \"packages/server/src/api/index.ts\"\n ]\n },\n {\n \"title\": \"chore: bump version to 1.0.16\",\n \"prNumber\": 5383,\n \"type\": \"other\",\n \"body\": \"This PR updates the version across all packages from 1.0.15 to 1.0.16.\",\n \"files\": [\n \"bun.lock\",\n \"eliza.postman.json\",\n \"lerna.json\",\n \"package.json\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/app/src-tauri/tauri.conf.json\",\n \"packages/autodoc/package.json\",\n \"packages/cli/package.json\",\n \"packages/client/package.json\",\n \"packages/core/package.json\",\n \"packages/create-eliza/package.json\",\n \"packages/docs/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-starter/package.json\",\n \"packages/project-starter/package.json\",\n \"packages/project-tee-starter/package.json\",\n \"packages/server/examples/package.json\",\n \"packages/server/package.json\"\n ]\n },\n {\n \"title\": \"fix: cypress test\",\n \"prNumber\": 5382,\n \"type\": \"bugfix\",\n \"body\": \"The test was failing because we removed the AddAgentCard component. This PR removes the related test checks for the add-agent-button to align with the updated UI, ensuring tests reflect the current state of the application.\",\n \"files\": [\n \"packages/client/cypress/e2e/01-home-page.cy.ts\",\n \"packages/client/cypress/e2e/02-chat-functionality.cy.ts\",\n \"packages/client/src/routes/home.tsx\"\n ]\n },\n {\n \"title\": \"fix: correct REST API documentation to match actual implementation\",\n \"prNumber\": 5380,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR fixes the REST API documentation to match the actual server implementation, addressing issue #5370 where the docs showed non-existent endpoints and incorrect request parameters.\\n\\n## Changes\\n\\n### Documentation Updates\\n- *\",\n \"files\": [\n \"bun.lock\",\n \"eliza.postman.json\",\n \"packages/docs/docs/rest/complete-message.api.mdx\",\n \"packages/docs/docs/rest/ingest-external-message.api.mdx\",\n \"packages/docs/docs/rest/send-message.api.mdx\",\n \"packages/docs/docs/rest/submit-message.api.mdx\"\n ]\n },\n {\n \"title\": \"fix: tweak padding\",\n \"prNumber\": 5379,\n \"type\": \"bugfix\",\n \"body\": \"\",\n \"files\": [\n \"packages/client/src/components/app-sidebar.tsx\"\n ]\n },\n {\n \"title\": \"fix: correct import/export icon\",\n \"prNumber\": 5378,\n \"type\": \"bugfix\",\n \"body\": \"\",\n \"files\": [\n \"packages/client/src/components/character-form.tsx\"\n ]\n },\n {\n \"title\": \"Fix import/export button order and icons in character form\",\n \"prNumber\": 5374,\n \"type\": \"bugfix\",\n \"body\": \"## Description\\n\\nThis PR fixes the reversed import/export buttons in the character form dropdown menu.\\n\\n## Changes Made\\n\\n1. **Fixed icon orientation**: \\n - Export button now uses (data flowing down from app to file)\\n - Import button now\",\n \"files\": [\n \"packages/client/src/components/character-form.tsx\"\n ]\n },\n {\n \"title\": \"feat: side bar\",\n \"prNumber\": 5373,\n \"type\": \"feature\",\n \"body\": \"This PR updates the Sidebar component to align with the new Figma design, improving structure, consistency, and visual clarity.\\r\\n\\r\\nUpdated Agent and Group list sections with consistent headers and new button placements.\\r\\n\\r\\nAdded \\\"Create New\",\n \"files\": [\n \"packages/client/src/components/app-sidebar.tsx\"\n ]\n },\n {\n \"title\": \"refactor: reorganize .env.example for better clarity\",\n \"prNumber\": 5372,\n \"type\": \"refactor\",\n \"body\": \"## Summary\\n- Reorganized .env.example file for better clarity and maintainability\\n- Grouped related configuration sections together\\n- Simplified the file structure to focus on essential configuration\\n\\n## Changes\\n- Moved server configuration\",\n \"files\": [\n \".env.example\"\n ]\n },\n {\n \"title\": \"feat: tweak ui\",\n \"prNumber\": 5371,\n \"type\": \"feature\",\n \"body\": \"This PR reduces the gap between the plus icon and the text as requested by @borisudovicic.\\r\\nIt also reduces the avatar size in group chats as requested by @wtfsayo.\",\n \"files\": [\n \"packages/client/src/components/ChatMessageListComponent.tsx\",\n \"packages/client/src/routes/home.tsx\"\n ]\n },\n {\n \"title\": \"feat: Show correct create button label based on active tab\",\n \"prNumber\": 5369,\n \"type\": \"feature\",\n \"body\": \"Update the create button on the Home page to display \u201cCreate New Agent\u201d when on the Agents tab and \u201cCreate New Group\u201d when on the Groups tab for clearer user guidance.\",\n \"files\": [\n \"packages/client/src/routes/home.tsx\"\n ]\n },\n {\n \"title\": \"feat: bun test:app base setup - issue 5367\",\n \"prNumber\": 5368,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/5367\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/5365\\r\\n\\r\\n\\n\\n# Risks\\n\\nLow. This change removes a potential runtime error and improves type safety without altering the component's intended behavior.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nThis PR re\",\n \"files\": [\n \"packages/client/src/components/ui/split-button.tsx\"\n ]\n },\n {\n \"title\": \"fix: cursor review\",\n \"prNumber\": 5393,\n \"type\": \"bugfix\",\n \"body\": \"Fixes an issue noted in [review](https://github.com/elizaOS/eliza/pull/5392#pullrequestreview-2986620046)\",\n \"files\": [\n \"packages/client/src/components/chat.tsx\",\n \"packages/client/src/components/ui/split-button.tsx\"\n ]\n },\n {\n \"title\": \"feat: dm chat header\",\n \"prNumber\": 5392,\n \"type\": \"feature\",\n \"body\": \"This PR updates the DM chat header design to align with the new Figma designs.\\r\\n\\r\\nAdditional improvements:\\r\\nFixes an issue where creating a new chat would jump to the second-latest chat instead of the newly created one.\\r\\n\\r\\nAdds a mechanism \",\n \"files\": [\n \"packages/client/src/components/chat.tsx\",\n \"packages/client/src/components/ui/dropdown-menu.tsx\",\n \"packages/client/src/components/ui/split-button.tsx\"\n ]\n },\n {\n \"title\": \"feat: update actions tab label to 'Model Calls' in agent sidebar\",\n \"prNumber\": 5391,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR updates the label for the actions tab in the agent sidebar from 'Actions' to 'Model Calls' for better clarity and user understanding.\\n\\n## Changes\\n\\n- Updated the tab label in \\n- Changed from 'Actions' to 'Model Calls' to \",\n \"files\": [\n \"packages/client/src/components/agent-sidebar.tsx\"\n ]\n },\n {\n \"title\": \"feat: improve UI avatar handling and styling consistency\",\n \"prNumber\": 5390,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR improves the UI avatar handling and styling consistency across the client components.\\n\\n## Changes Made\\n\\n- **Agent Card Component**: Added utility function for consistent avatar handling\\n- **App Sidebar Component**: \\n -\",\n \"files\": [\n \"packages/client/src/components/agent-card.tsx\",\n \"packages/client/src/components/app-sidebar.tsx\",\n \"packages/client/src/components/connection-status.tsx\"\n ]\n },\n {\n \"title\": \"chore: Update select component border radius\",\n \"prNumber\": 5389,\n \"type\": \"other\",\n \"body\": \"This PR updates the border radius of the select component from 'rounded' to 'rounded-xl' for a more modern appearance.\",\n \"files\": [\n \"packages/client/src/components/ui/select.tsx\"\n ]\n },\n {\n \"title\": \"fix: recording icon padding\",\n \"prNumber\": 5388,\n \"type\": \"bugfix\",\n \"body\": \"Issue:\\r\\nThe recording icon has no padding, causing it to appear cramped.\\r\\n\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/5c96b07f-b5e8-45f9-abb5-74c8b558c0a3)\\r\\n\\r\\nFix:\\r\\n\\r\\nAdded padding to the recording icon to improve visual balance\",\n \"files\": [\n \"packages/client/src/components/audio-recorder.tsx\"\n ]\n },\n {\n \"title\": \"fix: handle string and array types in bio for backward compatibility\",\n \"prNumber\": 5387,\n \"type\": \"bugfix\",\n \"body\": \"Previously, the bio handling logic assumed `agent.bio` was always an array, causing existing agents with string-based bios to fallback to the default description, hiding their actual bio.\\r\\n\\r\\nThis fix adds type checks to gracefully handle bo\",\n \"files\": [\n \"packages/client/src/components/agent-card.tsx\"\n ]\n },\n {\n \"title\": \"feat: issue-5410 fixing JSDoc comments\",\n \"prNumber\": 5414,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/5410\\r\\n[\\r\\n](https://github.com/eli\",\n \"files\": [\n \"packages/core/src/database.ts\",\n \"packages/core/src/specs/v1/messages.ts\",\n \"packages/core/src/specs/v2/settings.ts\"\n ]\n },\n {\n \"title\": \"ci: update GitHub Actions upload-artifact to v4\",\n \"prNumber\": 5412,\n \"type\": \"other\",\n \"body\": \"Updated workflows to use actions/upload-artifact@v4 for better reliability and performance. See release notes at https://github.com/actions/upload-artifact/releases\",\n \"files\": [\n \"packages/cli/.github/workflows/cli-comprehensive-tests.yml\",\n \"packages/client/.github/workflows/client-tests.yml\"\n ]\n },\n {\n \"title\": \"fix: Refactor DM channel creation logic to fetch live message count inste\u2026\",\n \"prNumber\": 5411,\n \"type\": \"bugfix\",\n \"body\": \"# Context\\r\\n\\r\\nPreviously, we were relying on the stale `latestChannelMessages` state to determine if a DM channel was empty when deciding to reuse or create a new DM channel. However, `latestChannelMessages` could be stale, leading to incorr\",\n \"files\": [\n \"packages/client/src/components/chat.tsx\"\n ]\n },\n {\n \"title\": \"fix: issue 5425 - removing check if sender name includes DM\",\n \"prNumber\": 5426,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/5425\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/5407\\r\\n\\r\\n\\r\\n\\n\\n# Relates to\\n\\n\\n\\n\\n# Risks\\n\\n\\n\\n# Relates to\\n\\n\\nN/A (Internal bug fix)\\n\\n# Risks\\n\\nLow. This PR fixes two bugs, making t\",\n \"files\": [\n \"packages/plugin-bootstrap/src/__tests__/ambiguity-handling.test.ts\",\n \"packages/plugin-bootstrap/src/index.ts\"\n ]\n },\n {\n \"title\": \"fix: clarifying prompt exclusivity for IGNORE\",\n \"prNumber\": 5528,\n \"type\": \"bugfix\",\n \"body\": \"Currently, the LLM sometimes outputs:\\r\\n\\r\\n```\\r\\n\\r\\n User acknowledged the code example with thanks - should close conversation politely\\r\\n REPLY,IGNORE\\r\\n \\r\\n \\n\\n# Risks\\n\\nLow. This is a targeted bug fix correcting data access, unlikely to introduce regressions.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nThis PR fixes a bug in the `acquireAdviso\",\n \"files\": [\n \"packages/plugin-sql/src/migration-service.ts\"\n ]\n },\n {\n \"title\": \"feat: enhance Claude workflows with full command access and PR commit triggers\",\n \"prNumber\": 5570,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- Enable Claude code review workflow to run on every commit to PRs (not just on open/ready)\\n- Grant full bash and GitHub CLI command access to both Claude workflows\\n- Closes #5564\\n\\n## Changes\\n1. **Claude Code Review Workflow (`cl\",\n \"files\": [\n \".github/workflows/claude-code-review.yml\",\n \".github/workflows/claude.yml\"\n ]\n },\n {\n \"title\": \"fix: suppress update notification during update command execution\",\n \"prNumber\": 5567,\n \"type\": \"bugfix\",\n \"body\": \"The update command was showing 'update available' messages during execution due to displayBanner() being called without skipUpdateCheck parameter. This fix passes true to skip the update check during update command execution.\\r\\n\\r\\nFixes #5447\",\n \"files\": [\n \"packages/cli/src/commands/update/index.ts\"\n ]\n },\n {\n \"title\": \"feat: implement service types and standardized interfaces with getServicesByType() method\",\n \"prNumber\": 5565,\n \"type\": \"feature\",\n \"body\": \"This PR implements the service types and test services system requested in issue #4914.\\r\\n\\r\\n## Key Features\\r\\n\\r\\n- **getServicesByType() method**: Returns all services of a specific type\\r\\n- **Multiple services per type**: Support for multiple \",\n \"files\": [\n \"bun.lock\",\n \"packages/core/src/__tests__/services-by-type.test.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/types/browser.ts\",\n \"packages/core/src/types/email.ts\",\n \"packages/core/src/types/index.ts\",\n \"packages/core/src/types/message.ts\",\n \"packages/core/src/types/pdf.ts\",\n \"packages/core/src/types/post.ts\",\n \"packages/core/src/types/runtime.ts\",\n \"packages/core/src/types/service.ts\",\n \"packages/core/src/types/transcription.ts\",\n \"packages/core/src/types/video.ts\",\n \"packages/core/src/types/web-search.ts\",\n \"packages/plugin-dummy-services/src/browser/service.ts\",\n \"packages/plugin-dummy-services/src/email/service.ts\",\n \"packages/plugin-dummy-services/src/index.ts\",\n \"packages/plugin-dummy-services/src/pdf/service.ts\",\n \"packages/plugin-dummy-services/src/transcription/service.ts\",\n \"packages/plugin-dummy-services/src/video/service.ts\",\n \"packages/plugin-dummy-services/src/web-search/service.ts\",\n \".github/workflows/claude-code-review.yml\",\n \".github/workflows/claude.yml\",\n \"CLAUDE.md\",\n \"packages/cli/src/commands/start/index.ts\",\n \"packages/cli/src/index.ts\",\n \"packages/cli/src/utils/user-environment.ts\",\n \"packages/cli/tests/commands/agent.test.ts\",\n \"packages/cli/tests/commands/create.test.ts\",\n \"packages/cli/tests/commands/dev.test.ts\",\n \"packages/cli/tests/commands/env.test.ts\",\n \"packages/cli/tests/commands/monorepo.test.ts\",\n \"packages/cli/tests/commands/plugins.test.ts\",\n \"packages/cli/tests/commands/publish.test.ts\",\n \"packages/cli/tests/commands/start.test.ts\",\n \"packages/cli/tests/commands/tee.test.ts\",\n \"packages/cli/tests/commands/test-utils.ts\",\n \"packages/cli/tests/commands/test.test.ts\",\n \"packages/cli/tests/commands/update.test.ts\",\n \"packages/cli/tests/integration/plugin-test-isolation.test.ts\",\n \"packages/cli/tests/integration/version-display.test.ts\",\n \"packages/cli/tests/unit/index.test.ts\",\n \"packages/cli/tests/utils/bun-test-helpers.ts\",\n \"packages/client/src/hooks/use-character-convert.ts\",\n \"packages/plugin-bootstrap/src/providers/capabilities.ts\",\n \"packages/plugin-dummy-services/src/tokenData/service.ts\",\n \"packages/plugin-dummy-services/src/wallet/service.ts\",\n \"packages/plugin-starter/scripts/install-test-deps.js\",\n \"packages/project-starter/scripts/install-test-deps.js\",\n \"packages/server/src/index.ts\",\n \"packages/cli/tests/test-timeouts.ts\"\n ]\n },\n {\n \"title\": \"fix: graceful shutdown for dev server on Cmd+C (SIGINT/SIGTERM)\",\n \"prNumber\": 5562,\n \"type\": \"bugfix\",\n \"body\": \"Fixes issue where Cmd+C on 'elizaos dev' doesn't kill server process\\r\\n\\r\\n## Changes\\r\\n- Added proper signal handling to stop dev server before process exit\\r\\n- Imported stopServer from server manager for cleanup\\r\\n- Replaced immediate process.e\",\n \"files\": [\n \"packages/cli/src/index.ts\",\n \"packages/cli/tests/unit/index.test.ts\",\n \"packages/cli/src/commands/dev/utils/server-manager.ts\"\n ]\n },\n {\n \"title\": \"fix: update CLI test expectations for version 1.2.1\",\n \"prNumber\": 5561,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- Update version check in update.test.ts from 1.2.0 to 1.2.1\\n- Handle monorepo detection in update command tests \\n- Tests now properly handle output when run from monorepo context\\n\\n## Test plan\\n- [x] Run tests locally with `bun \",\n \"files\": [\n \"CLAUDE.md\",\n \"bun.lock\",\n \"packages/app/package.json\",\n \"packages/app/src-tauri/Cargo.lock\",\n \"packages/app/src-tauri/Cargo.toml\",\n \"packages/app/src-tauri/src/lib.rs\",\n \"packages/app/src-tauri/tauri.conf.json\",\n \"packages/cli/src/commands/create/actions/creators.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/tests/commands/plugins.test.ts\",\n \"packages/cli/tests/commands/update.test.ts\",\n \"packages/cli/tests/unit/characters/character-plugin-ordering.test.ts\",\n \"packages/cli/tests/unit/utils/build-project.test.ts\",\n \"packages/core/src/__tests__/runtime.test.ts\",\n \"packages/core/src/specs/v2/__tests__/runtime.test.ts\",\n \"packages/docs/blog/plugin-ordering-guide.mdx\",\n \"packages/project-starter/src/__tests__/character-plugin-ordering.test.ts\",\n \"packages/project-starter/src/character.ts\",\n \"packages/project-tee-starter/src/character.ts\"\n ]\n },\n {\n \"title\": \"\ud83d\udcdd CodeRabbit Chat: Add verification script and refactor plugin ordering tests for clarity and robustness\",\n \"prNumber\": 5557,\n \"type\": \"feature\",\n \"body\": \"Code changes was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/5556#issuecomment-3066745260\\n\\nThe following files were modified:\\n\\n* `packages/cli/tests/unit/characters/character-plugin-ordering.test.ts`\",\n \"files\": [\n \"packages/cli/tests/unit/characters/character-plugin-ordering.test.ts\"\n ]\n },\n {\n \"title\": \"fix: core tests + replace execa + use bun runtime + replace local-ai + more\",\n \"prNumber\": 5556,\n \"type\": \"bugfix\",\n \"body\": \"This pull request introduces significant updates to streamline workflows, improve configuration management, and enhance local AI support by emphasizing the use of Ollama. Key changes include simplifying review prompts, enforcing the use of \",\n \"files\": [\n \".github/workflows/claude-code-review.yml\",\n \".github/workflows/claude.yml\",\n \"CLAUDE.md\",\n \"bun.lock\",\n \"packages/cli/package.json\",\n \"packages/cli/src/characters/eliza.ts\",\n \"packages/cli/src/commands/create/actions/creators.ts\",\n \"packages/cli/src/commands/create/actions/setup.ts\",\n \"packages/cli/src/commands/create/utils/selection.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/src/utils/registry/index.ts\",\n \"packages/cli/src/utils/user-environment.ts\",\n \"packages/cli/tests/unit/characters/README.md\",\n \"packages/cli/tests/unit/characters/character-plugin-ordering.test.ts\",\n \"packages/client/src/components/character-form.tsx\",\n \"packages/client/src/components/plugins-panel.tsx\",\n \"packages/client/src/config/voice-models.ts\",\n \"packages/client/src/hooks/use-character-convert.ts\",\n \"packages/core/src/__tests__/roles.test.ts\",\n \"packages/core/src/__tests__/runtime.test.ts\",\n \"packages/core/src/__tests__/settings.test.ts\",\n \"packages/core/src/specs/v2/__tests__/actions.test.ts\",\n \"packages/core/src/specs/v2/__tests__/runtime.test.ts\",\n \"packages/core/tsconfig.json\",\n \"packages/docs/blog/plugin-ordering-guide.mdx\",\n \"packages/docs/docs/core/knowledge.md\",\n \"packages/docs/static/llms-full.txt\",\n \"packages/project-starter/src/__tests__/character-plugin-ordering.test.ts\",\n \"packages/project-starter/src/character.ts\",\n \"packages/project-tee-starter/src/character.ts\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"chore: provider mapping\",\n \"prNumber\": 5582,\n \"type\": \"other\",\n \"body\": \"This PR maps the llama_local provider in v1 to @elizaos/plugin-ollama.\",\n \"files\": [\n \"packages/client/src/hooks/use-character-convert.ts\"\n ]\n },\n {\n \"title\": \"Fix auto-build test flag usage\",\n \"prNumber\": 5581,\n \"type\": \"bugfix\",\n \"body\": \"```\\n\\n\\n# Relates to\\n\\n\\nN/A\\n\\n# Risks\\n\\n