{ "date_generated_for": "2025-08-30", "ai_news_elizaos_discord_md_2025-08-29": { "filename": "2025-08-29.md", "content": "# elizaOS Discord - 2025-08-29\n\n## Overall Discussion Highlights\n\n### Legal Dispute with X (Twitter)\n- **Account Suspension & Lawsuit**: Shaw announced a lawsuit against X for suspending ElizaOS accounts and attempting to charge approximately $600,000 for Enterprise API access, which Shaw characterized as extortion.\n- **Media Coverage**: Shaw has an upcoming interview with the New York Times about the situation.\n- **Community Response**: A token called \"Ani\" was launched by community member Baoskee from DaosFun to help fund legal action against X/Elon, with reports of approximately $50k already sent to support the cause.\n- **Strategic Debate**: Jin advocated for demonstrating how ElizaOS can complement Grok rather than competing with it, emphasizing shared values in open-source AI, while Shaw defended the confrontational approach.\n- **Impersonation Concerns**: Community members warned about fake Shaw accounts on X soliciting donations.\n\n### Technical Issues & Development\n- **Package Type Definition Issues**: Core@1.5.0 had critical issues where exported types incorrectly referenced source files not included in the published package, causing compilation errors for plugins.\n- **Version Updates**: cjft worked on fixing tests and releasing versions 1.5.1 and 1.5.2 to address critical issues, particularly focusing on CLI functionality.\n- **Build Errors**: Multiple users reported build errors after updating to version 1.5.0, with import issues in the ElizaOS core that weren't fully resolved in 1.5.1.\n- **Model Configuration**: Jonas resolved a model issue by using \"gpt-4o-mini\" and reported concerns about high database egress (~1GB daily) despite minimal agent activity.\n- **Docker Deployment**: Agent Joshua shared his workflow for using flox with Eliza to generate Docker images, simplifying container deployment.\n- **Benchmarking Discussion**: Developers discussed tools for benchmarking function/action calling capabilities, referencing GLM4.5, gorilla's berkeley-function-call-leaderboard, and taubench.\n\n### Community & Ecosystem\n- **Alternative Communication Channels**: With the X account suspended, community members shared alternative channels to follow ElizaOS including Substack, YouTube, Farcaster, and LinkedIn.\n- **Token Discussions**: Users discussed cryptocurrency tokens like ELI5 and EDDY, with mentions of auto.fun platform potentially generating fee revenue for buybacks.\n- **Sonnet 4 Announcement**: Brief mention of Sonnet 4 rolling out 1 million context length capability.\n\n## Key Questions & Answers\n\n### Legal & Business\n- **Q**: What is the lawsuit against X about? \n **A**: X suspended ElizaOS accounts and attempted to charge them for API access, which Shaw characterized as extortion.\n\n- **Q**: Why did Shaw decide to sue X? \n **A**: They weren't responding to emails after initially indicating they would restore the accounts. Shaw sees it as the fastest path to account restoration.\n\n- **Q**: How is ElizaOS different from Virtuals in this situation? \n **A**: ElizaOS has a non-profit, open-source structure while Virtuals ended up paying the license fee.\n\n- **Q**: Is the $ani coin actually associated with Eliza Labs and is helping fund their legal actions? \n **A**: It's not directly associated with Eliza Labs, but baoskee from daosfun launched it and uses the fees from the token to help with the lawsuit. They have sent about $50k already.\n\n- **Q**: Is the ai16z token on solana still valid? \n **A**: Yes. CA: HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC\n\n### Technical\n- **Q**: How can I solve model issues? \n **A**: Use OPENAI_SMALL_MODEL=\"gpt-4o-mini\"\n\n- **Q**: Is it possible to create a swarm of AI Agents in Eliza for a trading bot? \n **A**: We typically just make plugins for each task.\n\n- **Q**: How is mono building if types are busted with ~12 packages depending on it? \n **A**: In the monorepo, packages reference each other, and the re-export from src is ok because src/ exists locally, but in the npm published package, only dist/ exists, not src/.\n\n- **Q**: What's the correct CA for EDDY? \n **A**: EPXCqBxGjneWdabXW4pEUA8bnKHp6a8WZNALe4uv1FUN\n\n## Community Help & Collaboration\n\n1. **Type Definition Issue Resolution**:\n Stan identified the root cause of the TypeScript compilation issue with core@1.5.0 where exports were reported as non-existent. He discovered that the build process was generating type declarations with tsc, but a custom build script was overwriting the generated .d.ts files with re-exports to src/ files, and proposed a fix in PR #5846.\n\n2. **Docker Deployment Workflow**:\n Agent Joshua shared a detailed workflow for using flox with Eliza to generate Docker images, simplifying container deployment by generating flox manifest.toml files using LLM and the flox containerize command.\n\n3. **Alternative Channels Guidance**:\n Kenk helped a new user (SP) by providing alternative channels to follow ElizaOS including Substack, YouTube, Farcaster, and LinkedIn after the X account suspension.\n\n4. **Build Error Troubleshooting**:\n Sayonara suggested trying version 1.5.1 to MRT0B13 who was experiencing build errors after updating to version 1.5.0, though this didn't fully resolve the issue.\n\n5. **Strategic Approach to X Dispute**:\n Jin proposed creating content showing how Eliza can extend Grok's abilities to demonstrate partnership potential rather than competition, offering a constructive alternative to the legal approach.\n\n## Action Items\n\n### Technical\n- **Fix type definition exports in NPM package for core module** | Resolve issue where .d.ts files reference source files that don't exist in the published package | *Mentioned by Stan*\n- **Complete test fixes for CLI functionality** | Continue fixing remaining test issues after 1.5.1 release | *Mentioned by cjft*\n- **Implement benchmarking for function/action calling** | Automate conversation testing to quickly pull stats for comparison with other models | *Mentioned by 0xbbjoker*\n- **Decide whether to fork metamcp or continue with mcp-gateway** | Evaluate the tradeoffs between the two approaches | *Mentioned by sayonara*\n- **Fix global CLI installation/update process** | Resolve issue where `bun i -g @elizaos/cli@latest` doesn't work properly | *Mentioned by Borko*\n- **Investigate high database egress (~1GB daily) with minimal agent activity** | Determine cause of excessive data traffic in nearly idle state | *Mentioned by jonas*\n- **Fix build errors with ElizaOS core imports in v1.5.0/1.5.1** | Resolve import issues that appeared after updating | *Mentioned by MRT0B13*\n- **Address SECRET_SALT configuration error** | Clarify purpose and proper setup of SECRET_SALT | *Mentioned by Trixi*\n- **Create demonstrations showing how ElizaOS can extend Grok's capabilities via OpenRouter** | *Mentioned by jin*\n- **Develop an AI debate format with fighting game UX for conflict resolution** | *Mentioned by jin*\n- **Build agent implementations for ElizaOS on Discord/Telegram/Farcaster** | *Mentioned by jin*\n- **Generate fee revenue through auto.fun platform activation** | Suggestion to activate auto.fun to generate fee revenue for buybacks | *Mentioned by lfg*\n- **Increase ELI5 token volume** | Encourage community to tweet and share ELI5 material to increase volume and value | *Mentioned by Dean*\n\n### Documentation\n- **Track ElizaOS news through alternative channels** | Follow Substack, YouTube, Farcaster, LinkedIn | *Mentioned by Kenk*\n- **Make ElizaOS news more engaging** | Cover \"spicy\" content rather than just PR updates | *Mentioned by boom*\n- **Create step-by-step instructions for setting up Eliza to tweet** | Provide clear guidance on Twitter integration | *Mentioned by David Andersson*\n- **Prepare materials for New York Times interview** | *Mentioned by shaw*\n- **Add Farcaster to plugins overview documentation** | Include Farcaster in the plugins documentation | *Mentioned by Borko*\n\n### Feature\n- **Create a UK government petition** | Get attention on the ElizaOS/X situation | *Mentioned by 3on_*\n- **Implement or document multi-agent coordination capabilities** | Enable creation of agent swarms working toward common goals | *Mentioned by Pepec01*\n- **Create short-form content for AI debate format** | *Mentioned by whobody*\n- **Implement Clank Tank for partnerships or grants funding pipeline** | *Mentioned by jin*\n- **Schedule Discord fireside chats to discuss project direction** | *Mentioned by jin*\n- **Create minimal Eliza starter that provides just core functionality** | Simplified starter template without extra components | *Mentioned by Odilitime*" }, "ai_news_elizaos_discord_md_2025-08-28": { "filename": "2025-08-28.md", "content": "# elizaOS Discord - 2025-08-28\n\n## Overall Discussion Highlights\n\n### Legal & Business Developments\n- **Major Antitrust Lawsuit**: ElizaOS has filed an antitrust lawsuit against Elon Musk's X (formerly Twitter) for allegedly suspending ElizaOS accounts and blocking sharing of ElizaOS GitHub links and website URLs\n- Community members expressed support for Shaw in this legal battle, noting that Musk has previously criticized similar censorship practices\n- Some users mentioned that Shaw had alluded to legal action as far back as June\n\n### Technical Updates & Releases\n- **Version 1.5.0 Released** with significant changes:\n - Bun build support and browser core compatibility\n - Reverted processActions to use cacheState for retrieving action results\n - Refined prompt logic for authentication\n - Added multi-step workflow execution system with configurable strategy modes\n - Custom SHA1 solution implemented for browser compatibility to maintain existing agent IDs\n- **Logging System Change**: Decision made to replace Pino with Adze for logging, offering namespaces and colored output\n- **Browser Compatibility**: Successfully made packages/client fully functional with zero polyfills\n- **LLM Performance Testing**: GPT-4o significantly outperforms Opus-3 for ElizaOS tasks (2-3 minutes vs 8-10 minutes completion time)\n\n### Cryptocurrency & Tokens\n- Active discussion about ELI5 and EDDY tokens in the ecosystem\n- EDDY described as having \"real AI utility\" within ElizaOS, functioning as an internal coding assistant\n- Some users experiencing issues with token migration/bonding not completing\n- References to \"Agent Shaw,\" an AI agent trained on ElizaOS to mimic SHAW\n\n### Plugin & Integration Discussions\n- Twitter plugin compatibility issues discussed - older versions (1.0.7/1.0.9) support user/pass/email authentication while newer versions require paid API access\n- Farcaster plugin mentioned as an alternative to Twitter\n- OpenRouter announced a 49-minute outage due to their database provider (Supabase) going down\n\n## Key Questions & Answers\n\n**Q: Is the lawsuit between ElizaOS and Twitter/X real?** \nA: Yes, it's real. (confirmed with Reuters article link)\n\n**Q: Where in the monorepo do agent details get stored when created using the UI?** \nA: In the \".eliza\" directory if you're not using an external database.\n\n**Q: How can I find the Twitter plugin that supports user/pass/email?** \nA: Newer versions use a newer API which costs. Version 1.0.7 (or possibly up to 1.0.9) is the last version supporting the old authentication method.\n\n**Q: What's the benefit of adze for logging?** \nA: It has namespaces and plugins can make their own channel.\n\n**Q: What's wrong with whisper?** \nA: It broke upstream. There was an attempt to fix it but other deadlines took priority.\n\n**Q: Are you using ollama for Local LLM?** \nA: Yes.\n\n**Q: What is EDDY's role in the ecosystem?** \nA: EDDY has real AI utility and plays an important role in \"the - org\" as an internal coding assistant similar to ChatGPT.\n\n## Community Help & Collaboration\n\n1. **Browser Compatibility Issues**:\n - cjft implemented webcrypto backwards compatibility with custom SHA1 to maintain database compatibility\n - Team successfully made packages/client fully functional with zero polyfills\n\n2. **Development Environment Fixes**:\n - cjft fixed the Vite dev server issue that sayonara reported\n - sayonara offered to fix the broken Whisper implementation for speech-to-text by next week\n\n3. **Plugin Support**:\n - jonas helped Jimmy find information about Twitter plugin versions that support user/pass/email authentication\n - Kenk shared the GitHub repository for the Farcaster plugin when Stan asked about it\n\n4. **Token Migration Issues**:\n - Odilitime acknowledged awareness of token migration/bonding issues reported by multiple users and indicated they're waiting for resolution\n\n5. **LLM Performance Testing**:\n - 0xbbjoker provided detailed comparison showing GPT-4o outperforms Opus-3 significantly, helping the team make informed decisions\n\n## Action Items\n\n### Technical\n- Replace Pino with Adze for logging (cjft)\n- Fix Whisper implementation for speech-to-text (Odilitime)\n- Fix Vite dev server (sayonara)\n- Implement custom SHA1 for browser compatibility (cjft)\n- Full QA testing on 1.5.0 release (cjft)\n- Optimize Dockerfile for CLI projects (currently large image size) (sayonara)\n- Update code to use max_completion_tokens instead of max_tokens when working with GPT-5-nano (jonas)\n- Improve redundancy and remove single points of failure in OpenRouter system (OpenRouter)\n- Fix migration/bonding issue for tokens including EB1dQHRr86w4JnvGT4nz8UCewd73jDyyRLVEg4LEtFUN (reported by multiple users)\n- Fix migration for Ani (Sagard)\n\n### Documentation\n- Write a post on tokenomics ideas for AI x VC, expanding on concepts like clank tank / $ai16z / vibe investing/trading (jin)\n\n### Feature\n- Add Farcaster webhook support to reduce neynar compute units (sayonara)\n- Implement filtering logs by agent and/or plugin (Odilitime)\n- Implement animated React library in Eliza cloud (sam-developer)\n- Create a team for Aleph hackathon to build a Base mini app with ElizaOS, Crossmint, and token launcher (Terexitarius)\n- Integrate multi-step workflow execution system with configurable strategy modes (cjft)\n- Implement browser compatibility improvements for core as mentioned in v1.5.0 release (cjft)" }, "ai_news_elizaos_discord_md_2025-08-27": { "filename": "2025-08-27.md", "content": "# elizaOS Discord - 2025-08-27\n\n## Overall Discussion Highlights\n\n### Development & Technical Updates\n- **ElizaOS Cloud Progress**: Sam shared a video update on ElizaOS cloud development and promised a Railways link for testing soon\n- **Browser Core Development**: Work continues on browser core functionality by cjft and sayonara\n- **TypeScript Declaration Issues**: Problems identified in the core package affecting plugin-solana integration\n- **Composio Plugin**: Stan's plugin was successfully added to the registry with documentation\n- **Supply Chain Security**: rs1 raised concerns about npm package security, providing detailed analysis via HackMD links\n- **Documentation Work**: yung_algorithm submitted a draft PR (#54) for documentation improvements\n\n### Integrations & Partnerships\n- **ERC-8004 Panel**: Upcoming panel discussion about Trustless Agents featuring Shaw (Eliza Labs), marcoderossi (MetaMask AI Lead), and Davide Crapis (Ethereum Foundation)\n- **Zed Editor Support**: Discussion about Zed's new agent support as an alternative to Cursor\n- **Solana Gym**: Solana Foundation launched a new environment for agent development\n- **AI Debate Format**: jin mentioned working on a format combining AI, prediction markets, and content\n\n### Twitter/X API Issues\n- **Account Suspensions**: Multiple users reported ElizaOS agent accounts being suspended on X\n- **API Limitations**: Discussion about Twitter's V1 API issues and potential alternatives\n- **Alternative Solutions**: Suggestions included switching to Telegram plugin and using third-party services like twitterapi.io\n\n### Community & Ecosystem\n- **Discord Bot Development**: Proposals to create a Discord bot for the ElizaOS ecosystem, possibly with a separate bridged server\n- **ElizaOS Projects**: fam | 0x57 offered expertise in ElizaOS, claiming to have built multiple projects with it\n- **Cryptocurrency Discussions**: Conversations about tokens related to \"daos.fun\" and various AI-themed projects on Solana blockchain\n\n## Key Questions & Answers\n\n**Q: Who is on the ERC-8004 panel about Trustless Agents?** \nA: Shaw (Eliza Labs), marcoderossi (MetaMask AI Lead), and Davide Crapis (Ethereum Foundation AI Lead)\n\n**Q: What's a good setup for development work?** \nA: R0am | tip.md suggested a maxed out Mac mini, good monitor, good chair, and maybe a standing desk\n\n**Q: What do you guys like for chairs?** \nA: R0am | tip.md mentioned using IKEA Markus at home and Herman Miller Aeron at the office\n\n**Q: Is the Composio plugin ready to add to registry?** \nA: Stan ⚡ confirmed it was ready with everything in the readme working\n\n**Q: What version are you on? 1.4.4? or 0.25.19?** \nA: Trixi confirmed using 1.4.4, while Benquik mentioned using 0.25.19 for custom plugins\n\n**Q: Is Shaw involved with the Agent Shaw token?** \nA: According to cantseemenomore, Shaw didn't say anything officially, but Baoskee sent him supply and Shaw bought more afterwards\n\n## Community Help & Collaboration\n\n1. **Twitter API Alternatives**:\n - DorianD suggested twitterapi.io as a potential alternative service after Rabbidfly's account suspension\n - DorianD also advised disputing charges for the basic account due to lack of service delivery\n\n2. **Development Support**:\n - R0am offered to collaborate with jin on Discourse data pipeline/scraper\n - Benquik helped Trixi with version information for plugin development\n\n3. **Security Awareness**:\n - rs1 provided detailed HackMD links with analysis and potential solutions for npm supply chain security issues\n\n4. **Content Sharing**:\n - Odilitime suggested using fixupx.com to view videos without leaving Discord\n - Kenk shared information about the upcoming ERC-8004 panel with links for interested participants\n\n## Action Items\n\n### Technical\n- Fix TypeScript declaration issues in core package affecting plugin-solana (Mentioned by Odilitime)\n- Review bot slots for potential Discord integration (Mentioned by jin and Odilitime)\n- Implement supply chain security scanning in CLI (Mentioned by Odilitime)\n- Test PR5825 with ecom bench using multiple providers (Mentioned by Odilitime)\n- Review and merge PR5829 (Mentioned by sayonara)\n- Review PR5828 (Mentioned by Odilitime)\n- Review and merge plugin-openrouter PR #8 (Mentioned by Stan ⚡)\n- Develop local plugin to work with existing agent (Mentioned by Trixi)\n- Switch from Twitter plugin to Telegram plugin as alternative to avoid X suspensions (Mentioned by Rabbidfly)\n- Consider twitterapi.io as Twitter API alternative (Mentioned by DorianD)\n\n### Documentation\n- Complete scenario documentation without creating merge conflicts (Mentioned by sayonara and yung_algorithm)\n- Review ERC-8004 EIP for Trustless Agents (Mentioned by Kenk)\n\n### Feature\n- Develop browser core functionality (Mentioned by cjft)\n- Finalize ElizaOS cloud implementation and share Railways link for testing (Mentioned by sam-developer)\n- Create Eliza community on X (Mentioned by GamerGenie)\n- Investigate Twitter plugin authentication changes (Mentioned by Jimmy)\n- Explore ElizaOS capabilities (Mentioned by snow)\n- Develop AI debate format where AIs can debate each other (Mentioned by jin)\n- Consider investing in Shaw AI agent token (Mentioned by cantseemenomore)" }, "ai_news_elizaos_dev_md_2025-08-29": { "filename": "2025-08-29.md", "error": "File not found" }, "ai_news_elizaos_dev_md_2025-08-28": { "filename": "2025-08-28.md", "error": "File not found" }, "ai_news_elizaos_dev_md_2025-08-27": { "filename": "2025-08-27.md", "error": "File not found" }, "ai_news_elizaos_daily_json_2025-08-29": { "filename": "2025-08-29.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-08-29", "categories": [ { "title": "GitHub Activity Summary", "content": [ { "text": "From August 29-30, 2025, the elizaOS/eliza repository showed active development with 2 new pull requests, both of which were successfully merged. There were no new issues reported during this period. The repository maintained a healthy contributor base with 8 active contributors participating in development activities." } ] }, { "title": "Pull Requests", "content": [ { "text": "PR #5845 titled 'fix: move starters build scripts locally' by @ChristopherTrimboli is merged." }, { "text": "PR #5846 titled 'fix(core): fix TypeScript declarations in npm package' by @standujar is merged." } ] }, { "title": "Issues", "content": [ { "text": "Issue #5764 titled 'v2 ↔ v3 Benchmark Suite & Evaluation' by @borisudovicic is CLOSED after being open for approximately two weeks from August 13 to August 29, 2025.", "link": "https://github.com/elizaOS/eliza/issues/5764" } ] }, { "title": "Summary for github_other", "content": [ { "text": "The repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input." } ] } ], "date": 1756425600 } }, "ai_news_elizaos_daily_md_2025-08-29": { "filename": "2025-08-29.md", "content": "# Daily Report - 2025-08-29\n\n## GitHub Activity Summary\n- From August 29-30, 2025, the elizaOS/eliza repository showed active development with 2 new pull requests, both of which were successfully merged. There were no new issues reported during this period. The repository maintained a healthy contributor base with 8 active contributors participating in development activities.\n\n## Pull Requests\n- PR #5845 titled 'fix: move starters build scripts locally' by @ChristopherTrimboli is merged.\n- PR #5846 titled 'fix(core): fix TypeScript declarations in npm package' by @standujar is merged.\n\n## Issues\n- Issue #5764 titled 'v2 ↔ v3 Benchmark Suite & Evaluation' by @borisudovicic is CLOSED after being open for approximately two weeks from August 13 to August 29, 2025. (Source: https://github.com/elizaOS/eliza/issues/5764)\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." }, "ai_news_elizaos_daily_discord_json_2025-08-29": { "filename": "2025-08-29.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-08-29", "date": 1756425600, "stats": { "totalMessages": 642, "totalUsers": 92 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around the suspension of ElizaOS's account on X (formerly Twitter) and the community's response to this situation. There is significant discussion about Elon Musk potentially targeting ElizaOS as competition to his xAI/Grok products. A token called \"Ani\" was launched by community member Baoskee from DaosFun to help fund legal action against X/Elon, with reports of approximately $50k already sent to support the cause. Community members expressed strong support for Shaw (presumably ElizaOS's founder) and discussed alternative communication channels since the X account suspension. There were concerns about impersonation accounts on X claiming to be Shaw and soliciting donations. The chat also touched on the broader implications for AI competition and censorship. No significant technical discussions or implementations were shared beyond mentions of ElizaOS being used by companies for their agents.\n\n## 2. FAQ\nQ: Is the $ani coin actually associated with Eliza Labs and is helping fund their legal actions? (asked by gptforme) A: It's not directly associated with Eliza Labs, but baoskee from daosfun launched it and uses the fees from the token to help with the lawsuit. They have sent about $50k already. (answered by 0x541nt and Rick)\nQ: Is the ai16z token on solana still valid? (asked by dr3amer◎8) A: Yes. CA: HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC (answered by Dean)\nQ: How can we reach out to Shaw? (asked by Marcelo) A: You can contact Shaw on Farcaster (answered by Cayden0207)\nQ: What are the plans team have to initiate & maintain the communication workflow? Any new/alternate accts in plan? (asked by Nomad) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: SP | Context: New user joining to follow ElizaOS news | Resolution: Provided alternative channels to follow ElizaOS including Substack, YouTube, Farcaster, and LinkedIn\nHelper: whobody | Helpee: BobbyWorld88 | Context: User unable to post in channel | Resolution: Suggested trying different text\nHelper: afidel, Spoilt, Boj/acc | Helpee: Marcelo | Context: Confusion about fake Shaw account on X soliciting donations | Resolution: Clarified which accounts were legitimate and which were parody/fake\n\n## 4. Action Items\nDocumentation: Track ElizaOS news through alternative channels (Substack, YouTube, Farcaster, LinkedIn) | Mentioned By: Kenk\nFeature: Create a UK government petition to get attention on the ElizaOS/X situation | Mentioned By: 3on_\nDocumentation: Make ElizaOS news more engaging by covering \"spicy\" content rather than just PR updates | Mentioned By: boom", "messageCount": 282, "userCount": 59 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Analysis of 💻-coders Discord Channel\n\n## 1. Summary\nThe chat segment covers several technical issues and solutions related to ElizaOS. Jonas resolved a model issue by using \"gpt-4o-mini\" and reported concerns about high database egress (~1GB daily) despite minimal agent activity. Trixi encountered a SECRET_SALT configuration error. David Andersson asked about setting up Eliza to tweet but couldn't find it in the plugin list. Pepec01 inquired about creating a swarm of AI agents for a trading bot, to which Odilitime suggested using plugins for each task. MRT0B13 reported build errors after updating to version 1.5.0, with import issues in the ElizaOS core. Sayonara recommended trying version 1.5.1 as they had reverted some changes, but MRT0B13 indicated this didn't resolve the issue. There was also an announcement about Sonnet 4 rolling out 1 million context length capability.\n\n## 2. FAQ\nQ: How can I solve model issues? (asked by jonas) A: Use OPENAI_SMALL_MODEL=\"gpt-4o-mini\" (answered by jonas)\nQ: Why is there so much database traffic (~1GB daily) with minimal agent activity? (asked by jonas) A: Unanswered\nQ: What is SECRET_SALT for? (asked by Trixi) A: Unanswered\nQ: How do I make Eliza tweet? (asked by 🏇David Andersson (James)) A: Unanswered\nQ: Is it possible to create a swarm of AI Agents in Eliza for a trading bot? (asked by Pepec01) A: We typically just make plugins for each task (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: sayonara | Helpee: MRT0B13 | Context: Build errors with ElizaOS core import issues after updating to 1.5.0 | Resolution: Suggested trying version 1.5.1 as they reverted some changes, but this didn't resolve the issue\nHelper: Odilitime | Helpee: Pepec01 | Context: Creating multiple AI agents working toward the same goal (trading bot) | Resolution: Suggested using plugins for each task instead\n\n## 4. Action Items\nTechnical: Investigate high database egress (~1GB daily) with minimal agent activity | Description: Determine cause of excessive data traffic in nearly idle state | Mentioned By: jonas\nTechnical: Fix build errors with ElizaOS core imports in v1.5.0/1.5.1 | Description: Resolve import issues that appeared after updating | Mentioned By: MRT0B13\nTechnical: Address SECRET_SALT configuration error | Description: Clarify purpose and proper setup of SECRET_SALT | Mentioned By: Trixi\nDocumentation: Create step-by-step instructions for setting up Eliza to tweet | Description: Provide clear guidance on Twitter integration | Mentioned By: 🏇David Andersson (James)\nFeature: Implement or document multi-agent coordination capabilities | Description: Enable creation of agent swarms working toward common goals | Mentioned By: Pepec01", "messageCount": 13, "userCount": 9 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Analysis of \"fun\" Discord Channel\n\n## 1. Summary\nThe chat segment shows minimal technical discussion. Users primarily discuss cryptocurrency tokens like ELI5 and EDDY (EPXCqBxGjneWdabXW4pEUA8bnKHp6a8WZNALe4uv1FUN), with mentions of auto.fun platform. There's a suggestion that auto.fun should become active to generate fee revenue for buybacks, even if not through specific tokens. One user mentions volume increases for ELI5 token and encourages community promotion. A user named Bard requests technical help but doesn't specify the issue. Overall, the conversation is mostly casual commentary about token prices, trading decisions, and brief mentions of a person named \"Shaw\" who appears to be connected to the project.\n\n## 2. FAQ\nQ: Is ELI5 still a thing? (asked by k1kkoS) A: Unanswered\nQ: Can I get some technical help regarding the platform? (asked by Bard) A: Unanswered\nQ: What's the correct CA for EDDY? (implied by MDMnvest's response) A: EPXCqBxGjneWdabXW4pEUA8bnKHp6a8WZNALe4uv1FUN (answered by MDMnvest)\n\n## 3. Help Interactions\nHelper: MDMnvest | Helpee: Unspecified user | Context: Confirming the correct contract address for EDDY token | Resolution: Provided the contract address EPXCqBxGjneWdabXW4pEUA8bnKHp6a8WZNALe4uv1FUN\n\n## 4. Action Items\nFeature: Generate fee revenue through auto.fun platform activation | Description: Suggestion to activate auto.fun to generate fee revenue for buybacks | Mentioned By: lfg\nTechnical: Increase ELI5 token volume | Description: Encourage community to tweet and share ELI5 material to increase volume and value | Mentioned By: Dean", "messageCount": 37, "userCount": 15 }, { "channelId": "1301363808421543988", "channelName": "🥇-partners", "summary": "# Discord Chat Analysis: 🥇-partners\n\n## 1. Summary\nThe chat primarily revolves around a legal dispute between ElizaOS and X (Twitter). Shaw, a key figure in ElizaOS, announced a lawsuit against X for suspending their accounts and attempting to charge them for API access, which Shaw characterized as extortion. According to the conversation, X initially engaged with ElizaOS about reinstating their accounts but then ghosted them while trying to sell them Enterprise API access for approximately $600,000. Shaw has an upcoming interview with the New York Times about the situation and believes media pressure could help resolve the issue. There's debate within the community about whether confrontational tactics or collaborative approaches would be more effective. Jin advocates for demonstrating how ElizaOS can complement Grok (X's AI) rather than competing with it, emphasizing shared values in open-source AI. The conversation also touches on potential projects like AI debate formats that could showcase ElizaOS capabilities. Shaw emphasizes that ElizaOS's non-profit, open-source structure strengthens their legal position compared to other companies like Virtuals that faced similar issues with X.\n\n## 2. FAQ\nQ: What is the lawsuit about? (asked by pragmatiko) A: X suspended ElizaOS accounts and attempted to charge them for API access, which Shaw characterized as extortion. (answered by shaw)\nQ: Why did Shaw decide to sue X? (asked by pragmatiko) A: They weren't responding to emails after initially indicating they would restore the accounts. Shaw sees it as the fastest path to account restoration. (answered by shaw)\nQ: Is this approach too confrontational? (asked by jin) A: Shaw believes standing up for himself has worked well in the past, and lawsuits have been financially beneficial. (answered by shaw)\nQ: What does X want from ElizaOS? (asked by jin) A: According to Shaw, X wanted to sell them Enterprise API access for approximately $600,000. (answered by shaw)\nQ: How is ElizaOS different from Virtuals in this situation? (asked by jin) A: ElizaOS has a non-profit, open-source structure while Virtuals ended up paying the license fee. (answered by shaw)\n\n## 3. Help Interactions\nHelper: shaw | Helpee: pragmatiko | Context: pragmatiko was confused about the lawsuit since ElizaOS is open source | Resolution: Shaw directed them to read his announcement that explained the situation.\nHelper: jin | Helpee: shaw | Context: Suggesting alternative approaches to the X conflict | Resolution: Proposed creating content showing how Eliza can extend Grok's abilities to demonstrate partnership potential rather than competition.\nHelper: jin | Helpee: community | Context: Proposing a constructive project amid the legal tension | Resolution: Suggested building a 1v1 debate format show with fighting game UX that could showcase ElizaOS capabilities.\n\n## 4. Action Items\nType: Technical | Description: Create demonstrations showing how ElizaOS can extend Grok's capabilities via OpenRouter | Mentioned By: jin\nType: Technical | Description: Develop an AI debate format with fighting game UX for conflict resolution | Mentioned By: jin\nType: Technical | Description: Build agent implementations for ElizaOS on Discord/Telegram/Farcaster | Mentioned By: jin\nType: Feature | Description: Create short-form content for AI debate format | Mentioned By: whobody\nType: Feature | Description: Implement Clank Tank for partnerships or grants funding pipeline | Mentioned By: jin\nType: Documentation | Description: Prepare materials for New York Times interview | Mentioned By: shaw\nType: Technical | Description: Schedule Discord fireside chats to discuss project direction | Mentioned By: jin", "messageCount": 195, "userCount": 14 }, { "channelId": "1377726087789940836", "channelName": "core-devs", "summary": "# Discord Chat Analysis: \"core-devs\" Channel\n\n## 1. Summary\nThe chat primarily revolves around technical discussions related to the ElizaOS project. Key technical topics include:\n\n- Package and type definition issues in the core@1.5.0 package where exported types were incorrectly referencing source files not included in the published package. Stan identified that the build process was generating type declarations with tsc, but a custom build script was overwriting the generated .d.ts files with re-exports to src/ files. This caused compilation errors for plugins using the package.\n\n- cjft worked on fixing tests and releasing version 1.5.1 and 1.5.2 to address critical issues, particularly focusing on CLI functionality to unblock users.\n\n- Agent Joshua shared his workflow for using flox with Eliza to generate Docker images, simplifying container deployment by generating flox manifest.toml files using LLM and the flox containerize command.\n\n- Discussion about benchmarking tools for function/action calling capabilities, with references to GLM4.5, gorilla's berkeley-function-call-leaderboard, and taubench for comparing model performance.\n\n- Consideration of whether to fork metamcp or continue with their own mcp-gateway implementation.\n\n## 2. FAQ\nQ: Is there an issue with the plugin registry? (asked by Kenk) A: Unanswered\nQ: How is mono building if types are busted with ~12 packages depending on it? (asked by cjft) A: In the monorepo, packages reference each other, and the re-export from src is ok because src/ exists locally, but in the npm published package, only dist/ exists, not src/ (answered by Stan)\nQ: Can we add Farcaster to the plugins overview? (asked by Borko) A: Yes 100% (answered by yung_algorithm)\nQ: Why doesn't `bun i -g @elizaos/cli@latest` work anymore? (asked by Borko) A: Unanswered\n\n## 3. Help Interactions\nHelper: Stan | Helpee: cjft | Context: TypeScript compilation issue with core@1.5.0 where exports were reported as non-existent by TS | Resolution: Stan identified the issue with .d.ts files referencing missing source files and proposed a fix in PR #5846, though it initially caused more type errors\nHelper: Agent Joshua ₱ | TEE | Helpee: Community | Context: Sharing workflow for using flox with Eliza to generate Docker images | Resolution: Detailed a process using flox activate and containerize commands to simplify container deployment\nHelper: cjft | Helpee: Community | Context: Fixing CLI issues and tests | Resolution: Released version 1.5.1 to fix start and create commands, with plans for 1.5.2 to resolve remaining type export issues\n\n## 4. Action Items\nTechnical: Fix type definition exports in NPM package for core module | Description: Resolve issue where .d.ts files reference source files that don't exist in the published package | Mentioned By: Stan\nTechnical: Complete test fixes for CLI functionality | Description: Continue fixing remaining test issues after 1.5.1 release | Mentioned By: cjft\nTechnical: Implement benchmarking for function/action calling | Description: Automate conversation testing to quickly pull stats for comparison with other models | Mentioned By: 0xbbjoker\nTechnical: Decide whether to fork metamcp or continue with mcp-gateway | Description: Evaluate the tradeoffs between the two approaches | Mentioned By: sayonara\nFeature: Create minimal Eliza starter that provides just core functionality | Description: Simplified starter template without extra components | Mentioned By: Odilitime\nTechnical: Fix global CLI installation/update process | Description: Resolve issue where `bun i -g @elizaos/cli@latest` doesn't work properly | Mentioned By: Borko\nFeature: Add Farcaster to plugins overview documentation | Description: Include Farcaster in the plugins documentation | Mentioned By: Borko", "messageCount": 115, "userCount": 15 } ] } }, "ai_news_elizaos_daily_discord_md_2025-08-29": { "filename": "2025-08-29.md", "content": "# elizaOS Discord - 2025-08-29\n\n## Overall Discussion Highlights\n\n### Legal Dispute with X (Twitter)\n- **Account Suspension & Lawsuit**: Shaw announced a lawsuit against X for suspending ElizaOS accounts and attempting to charge approximately $600,000 for Enterprise API access, which Shaw characterized as extortion.\n- **Media Coverage**: Shaw has an upcoming interview with the New York Times about the situation.\n- **Community Response**: A token called \"Ani\" was launched by community member Baoskee from DaosFun to help fund legal action against X/Elon, with reports of approximately $50k already sent to support the cause.\n- **Strategic Debate**: Jin advocated for demonstrating how ElizaOS can complement Grok rather than competing with it, emphasizing shared values in open-source AI, while Shaw defended the confrontational approach.\n- **Impersonation Concerns**: Community members warned about fake Shaw accounts on X soliciting donations.\n\n### Technical Issues & Development\n- **Package Type Definition Issues**: Core@1.5.0 had critical issues where exported types incorrectly referenced source files not included in the published package, causing compilation errors for plugins.\n- **Version Updates**: cjft worked on fixing tests and releasing versions 1.5.1 and 1.5.2 to address critical issues, particularly focusing on CLI functionality.\n- **Build Errors**: Multiple users reported build errors after updating to version 1.5.0, with import issues in the ElizaOS core that weren't fully resolved in 1.5.1.\n- **Model Configuration**: Jonas resolved a model issue by using \"gpt-4o-mini\" and reported concerns about high database egress (~1GB daily) despite minimal agent activity.\n- **Docker Deployment**: Agent Joshua shared his workflow for using flox with Eliza to generate Docker images, simplifying container deployment.\n- **Benchmarking Discussion**: Developers discussed tools for benchmarking function/action calling capabilities, referencing GLM4.5, gorilla's berkeley-function-call-leaderboard, and taubench.\n\n### Community & Ecosystem\n- **Alternative Communication Channels**: With the X account suspended, community members shared alternative channels to follow ElizaOS including Substack, YouTube, Farcaster, and LinkedIn.\n- **Token Discussions**: Users discussed cryptocurrency tokens like ELI5 and EDDY, with mentions of auto.fun platform potentially generating fee revenue for buybacks.\n- **Sonnet 4 Announcement**: Brief mention of Sonnet 4 rolling out 1 million context length capability.\n\n## Key Questions & Answers\n\n### Legal & Business\n- **Q**: What is the lawsuit against X about? \n **A**: X suspended ElizaOS accounts and attempted to charge them for API access, which Shaw characterized as extortion.\n\n- **Q**: Why did Shaw decide to sue X? \n **A**: They weren't responding to emails after initially indicating they would restore the accounts. Shaw sees it as the fastest path to account restoration.\n\n- **Q**: How is ElizaOS different from Virtuals in this situation? \n **A**: ElizaOS has a non-profit, open-source structure while Virtuals ended up paying the license fee.\n\n- **Q**: Is the $ani coin actually associated with Eliza Labs and is helping fund their legal actions? \n **A**: It's not directly associated with Eliza Labs, but baoskee from daosfun launched it and uses the fees from the token to help with the lawsuit. They have sent about $50k already.\n\n- **Q**: Is the ai16z token on solana still valid? \n **A**: Yes. CA: HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC\n\n### Technical\n- **Q**: How can I solve model issues? \n **A**: Use OPENAI_SMALL_MODEL=\"gpt-4o-mini\"\n\n- **Q**: Is it possible to create a swarm of AI Agents in Eliza for a trading bot? \n **A**: We typically just make plugins for each task.\n\n- **Q**: How is mono building if types are busted with ~12 packages depending on it? \n **A**: In the monorepo, packages reference each other, and the re-export from src is ok because src/ exists locally, but in the npm published package, only dist/ exists, not src/.\n\n- **Q**: What's the correct CA for EDDY? \n **A**: EPXCqBxGjneWdabXW4pEUA8bnKHp6a8WZNALe4uv1FUN\n\n## Community Help & Collaboration\n\n1. **Type Definition Issue Resolution**:\n Stan identified the root cause of the TypeScript compilation issue with core@1.5.0 where exports were reported as non-existent. He discovered that the build process was generating type declarations with tsc, but a custom build script was overwriting the generated .d.ts files with re-exports to src/ files, and proposed a fix in PR #5846.\n\n2. **Docker Deployment Workflow**:\n Agent Joshua shared a detailed workflow for using flox with Eliza to generate Docker images, simplifying container deployment by generating flox manifest.toml files using LLM and the flox containerize command.\n\n3. **Alternative Channels Guidance**:\n Kenk helped a new user (SP) by providing alternative channels to follow ElizaOS including Substack, YouTube, Farcaster, and LinkedIn after the X account suspension.\n\n4. **Build Error Troubleshooting**:\n Sayonara suggested trying version 1.5.1 to MRT0B13 who was experiencing build errors after updating to version 1.5.0, though this didn't fully resolve the issue.\n\n5. **Strategic Approach to X Dispute**:\n Jin proposed creating content showing how Eliza can extend Grok's abilities to demonstrate partnership potential rather than competition, offering a constructive alternative to the legal approach.\n\n## Action Items\n\n### Technical\n- **Fix type definition exports in NPM package for core module** | Resolve issue where .d.ts files reference source files that don't exist in the published package | *Mentioned by Stan*\n- **Complete test fixes for CLI functionality** | Continue fixing remaining test issues after 1.5.1 release | *Mentioned by cjft*\n- **Implement benchmarking for function/action calling** | Automate conversation testing to quickly pull stats for comparison with other models | *Mentioned by 0xbbjoker*\n- **Decide whether to fork metamcp or continue with mcp-gateway** | Evaluate the tradeoffs between the two approaches | *Mentioned by sayonara*\n- **Fix global CLI installation/update process** | Resolve issue where `bun i -g @elizaos/cli@latest` doesn't work properly | *Mentioned by Borko*\n- **Investigate high database egress (~1GB daily) with minimal agent activity** | Determine cause of excessive data traffic in nearly idle state | *Mentioned by jonas*\n- **Fix build errors with ElizaOS core imports in v1.5.0/1.5.1** | Resolve import issues that appeared after updating | *Mentioned by MRT0B13*\n- **Address SECRET_SALT configuration error** | Clarify purpose and proper setup of SECRET_SALT | *Mentioned by Trixi*\n- **Create demonstrations showing how ElizaOS can extend Grok's capabilities via OpenRouter** | *Mentioned by jin*\n- **Develop an AI debate format with fighting game UX for conflict resolution** | *Mentioned by jin*\n- **Build agent implementations for ElizaOS on Discord/Telegram/Farcaster** | *Mentioned by jin*\n- **Generate fee revenue through auto.fun platform activation** | Suggestion to activate auto.fun to generate fee revenue for buybacks | *Mentioned by lfg*\n- **Increase ELI5 token volume** | Encourage community to tweet and share ELI5 material to increase volume and value | *Mentioned by Dean*\n\n### Documentation\n- **Track ElizaOS news through alternative channels** | Follow Substack, YouTube, Farcaster, LinkedIn | *Mentioned by Kenk*\n- **Make ElizaOS news more engaging** | Cover \"spicy\" content rather than just PR updates | *Mentioned by boom*\n- **Create step-by-step instructions for setting up Eliza to tweet** | Provide clear guidance on Twitter integration | *Mentioned by David Andersson*\n- **Prepare materials for New York Times interview** | *Mentioned by shaw*\n- **Add Farcaster to plugins overview documentation** | Include Farcaster in the plugins documentation | *Mentioned by Borko*\n\n### Feature\n- **Create a UK government petition** | Get attention on the ElizaOS/X situation | *Mentioned by 3on_*\n- **Implement or document multi-agent coordination capabilities** | Enable creation of agent swarms working toward common goals | *Mentioned by Pepec01*\n- **Create short-form content for AI debate format** | *Mentioned by whobody*\n- **Implement Clank Tank for partnerships or grants funding pipeline** | *Mentioned by jin*\n- **Schedule Discord fireside chats to discuss project direction** | *Mentioned by jin*\n- **Create minimal Eliza starter that provides just core functionality** | Simplified starter template without extra components | *Mentioned by Odilitime*" }, "ai_news_elizaos_daily_dev_json_2025-08-29": { "filename": "2025-08-29.json", "error": "File not found" }, "ai_news_elizaos_daily_dev_md_2025-08-29": { "filename": "2025-08-29.md", "error": "File not found" }, "ai_news_hyperfy_daily_json_2025-08-29": { "filename": "2025-08-29.json", "error": "File not found" }, "ai_news_hyperfy_daily_md_2025-08-29": { "filename": "2025-08-29.md", "error": "File not found" }, "github_summaries_daily_2025-08-30": { "filename": "2025-08-30.md", "error": "File not found" }, "github_summaries_week_latest_2025-08-24.md": { "filename": "2025-08-24.md", "content": "# elizaos/eliza Weekly Report (Aug 24 - 30, 2025)\n\n## 🚀 Highlights\nThis week was characterized by significant foundational improvements and the launch of a major new feature initiative. The project's build system was modernized with a migration to Bun, streamlining development across all packages. Concurrently, a series of critical bug fixes enhanced the stability of the core runtime, client, and plugins. The most notable new development was the kickoff of work on dynamic prompting, which will enable sophisticated, multi-turn conversation simulations and represents a major step forward in the agent's adaptability and testing capabilities.\n\n## 🛠️ Key Developments\nWork this week focused on modernizing the build system, enhancing agent intelligence through advanced prompting, and improving overall system stability.\n\n- **Build System Modernization with Bun**\n A major effort was completed to replace the `tsup` build system with a standardized Bun-based approach ([#5807](https://github.com/elizaos/eliza/pull/5807)). This overhaul simplifies the build process and led to the creation of a new `@elizaos/utils` package to house shared build utilities, promoting code reuse and maintainability ([#5821](https://github.com/elizaos/eliza/pull/5821)).\n\n- **Advancements in Prompting and Agent Logic**\n A new feature to support dynamic, multi-turn conversations in scenarios was initiated, with a PR opened to add the core capability and its specifications ([#5824](https://github.com/elizaos/eliza/pull/5824)). To improve modularity, core multi-step templates were moved to the core layer, allowing characters to define their own template overrides ([#5822](https://github.com/elizaos/eliza/pull/5822)). Prompt logic was also refined to enforce user ID requirements for authenticated actions ([#5816](https://github.com/elizaos/eliza/pull/5816]) and to clean up template definitions ([#5817](https://github.com/elizaos/eliza/pull/5817)).\n\n- **Widespread Stability and Bug Fixes**\n A number of fixes were deployed across the ecosystem to improve stability and correctness:\n - **Core Runtime:** A regression in `processActions` was fixed to correctly use `cacheState` ([#5815](https://github.com/elizaos/eliza/pull/5815]), emitted events were updated to always include the runtime ([#5827](https://github.com/elizaos/eliza/pull/5827]), and browser build exports and type definitions were improved ([#5832](https://github.com/elizaos/eliza/pull/5832)).\n - **Client & CLI:** The `AgentLog` type was corrected in the client ([#5834](https://github.com/elizaos/eliza/pull/5834]), and the CLI was updated to lazy-load the environment to prevent confusing startup warnings ([#5829](https://github.com/elizaos/eliza/pull/5829)).\n - **Plugins:** The `GENERATE_IMAGE` handler was updated to return a proper `ActionResult` ([#5823](https://github.com/elizaos/eliza/pull/5823]), and a parameter order bug in `logger.error` was fixed ([#5833](https://github.com/elizaos/eliza/pull/5833)).\n\n## 🐛 Issues & Triage\nIssue tracking this week highlighted a focus on future capabilities, infrastructure improvements, and test reliability.\n\n- **Closed Issues:**\n A long-standing issue causing CI test failures on Windows was resolved. The fix addressed incorrect path handling in CLI agent start command tests, improving test suite reliability ([#5619](https://github.com/elizaos/eliza/issues/5619)).\n\n- **New & Active Issues:**\n The most significant new issue is the proposal for **Dynamic Prompting for Multi-Turn Conversations** ([#5819](https://github.com/elizaos/eliza/issues/5819)). This issue is highly active and includes a detailed implementation plan for enabling complex, stateful agent interactions in test scenarios.\n\n Other key proposals include:\n - **Infrastructure:** Integrating a native Venice AI provider for privacy-focused AI ([#5820](https://github.com/elizaos/eliza/issues/5820]) and analyzing options for the MCP Gateway to improve agent communication ([#5814](https://github.com/elizaos/eliza/issues/5814), [#5830](https://github.com/elizaos/eliza/issues/5830)).\n - **User Experience:** A suggestion was made to display the action called and its result directly in the chat UI for better transparency ([#5831](https://github.com/elizaos/eliza/issues/5831)).\n - **Bugs:** A problem was reported where a successfully published plugin is not visible in the PR list ([#5813](https://github.com/elizaos/eliza/issues/5813)).\n\n## 💬 Community & Collaboration\nThe week saw strong, proactive collaboration, particularly around planning for future features. The discussion on the dynamic prompting issue ([#5819](https://github.com/elizaos/eliza/issues/5819)) was noted as \"highly active,\" with a detailed implementation plan proposed almost immediately. This indicates a high level of engagement and a shared vision for the project's direction. The thoughtful refactoring during the Bun migration, which included creating a shared utilities package, further demonstrates a collaborative and forward-thinking development approach." }, "github_summaries_month_latest_2025-08-01.md": { "filename": "2025-08-01.md", "content": "# elizaos/eliza Monthly Report (August 2025)\n\n## 🚀 Highlights\nEarly August was a period of foundational refinement and preparation for future growth. Development focused heavily on improving the developer experience and overall repository hygiene by streamlining the build process, simplifying setup with automatic CLI dependency installation, and removing obsolete code and documentation. While no major features were merged, significant groundwork was laid with new feature requests for the core package and a proposal for a new sessions API, signaling a move towards enhanced modularity and capability.\n\n## 🛠️ Key Developments\nWork completed in this period centered on optimizing the development environment and cleaning up the codebase.\n\n* **Developer Experience and Build Optimization**: To streamline setup for new and existing contributors, the `@elizaos/cli` is now automatically installed as a dev dependency in non-monorepo environments ([#5702](https://github.com/elizaos/eliza/pull/5702)). The main build process was also made more efficient by removing the docs filter and cleaning up dependencies ([#5701](https://github.com/elizaos/eliza/pull/5701)).\n* **Repository and CI/CD Cleanup**: A significant effort was made to simplify the repository. This included removing outdated LangChain and Tauri details from the `README.md` ([#5700](https://github.com/elizaos/eliza/pull/5700)) and deleting three obsolete GitHub workflow files (`deploy-cli.yml`, `docs-publish.yml`, `llmstxt-generator.yml`), which cleans up the CI/CD pipeline ([#5699](https://github.com/elizaos/eliza/pull/5699)).\n\n## 🐛 Issues & Triage\nNo issues were closed during this period, but several key issues and pull requests were opened, outlining the project's near-term trajectory.\n\n* **Closed Issues:** No issues were closed during this reporting period.\n* **New & Active Issues:**\n * **Core Package Enhancements**: Two feature requests were opened for the core package: one to add an `unregisterAction` method for better runtime action management ([#5697](https://github.com/elizaos/eliza/issues/5697)) and another to define an `IStorageService` type to support new storage plugins ([#5698](https://github.com/elizaos/eliza/issues/5698)).\n * **Deployment**: A new issue was created to track the deployment of Eliza Cloud on Railway ([#5703](https://github.com/elizaos/eliza/issues/5703)).\n * **Work in Progress**: New pull requests were opened to introduce a \"sessions API\" ([#5704](https://github.com/elizaos/eliza/pull/5704)) and to fix a test component ([#5705](https://github.com/elizaos/eliza/pull/5705)), indicating ongoing feature development and maintenance.\n\n## 💬 Community & Collaboration\nDevelopment activity was steady, with a clear focus on foundational improvements. The work reflects a proactive approach to maintenance and developer ergonomics, which is crucial for a healthy open-source project. While the provided reports do not indicate high-volume discussions on any single item, the nature of the issues and pull requests suggests a coordinated effort to prepare the codebase for upcoming features and improved stability." }, "github_extracted_data_monthly_stats_text_2025-08": "{\n \"interval\": {\n \"intervalStart\": \"2025-08-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-09-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-08-01 to 2025-09-01, elizaos/eliza had 87 new PRs (73 merged), 59 new issues, and 34 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs7ELgn4\",\n \"title\": \"Calling `startAgent` from CLI command start - hangs early when `@elizaos/plugin-bootstrap` is omitted & hangs later when it is included\",\n \"author\": \"monilpat\",\n \"number\": 5719,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\n`packages/cli/src/commands/start/actions/agent-start.ts` is exported and re-used in CLI commands with \\n\\n```ts\\nimport { startAgent } from '../commands/start';\\n```\\n\\nWhen I call `startAgent` from `runtime-factory.ts` / `initializeAgent()`:\\n\\n```ts\\nconst runtime = await startAgent(\\n encryptedCharacter(character),\\n server,\\n undefined,\\n [], // <-- intentionally no bootstrap plugin\\n { isTestMode: false }\\n);\\n```\\n\\ninitialization hangs almost immediately (before plugin dependency resolution).\\n\\nIf I add `@elizaos/plugin-bootstrap` back:\\n\\n```ts\\nconst runtime = await startAgent(\\n encryptedCharacter(character),\\n server,\\n undefined,\\n ['@elizaos/plugin-bootstrap'],\\n { isTestMode: false }\\n);\\n```\\n\\ninitialization gets past early steps, loads **all** plugins, but then hangs right after the bootstrap plugin finishes loading.\\n\\n---\\n\\n**To Reproduce**\\n\\n1. Build the CLI (`cd packages/cli && bun x tsup`).\\n2. From `packages/cli` run a scenario that relies on `initializeAgent`, e.g.:\\n\\n```bash\\nbun run src/index.ts scenario run \\\\\\n src/commands/scenario/examples/e2b-test.scenario.yaml\\n```\\n\\n3. Edit `runtime-factory.ts` ➜ `initializeAgent()` and comment the bootstrap plugin in the `character.plugins` array (lines 411-415).\\n4. Re-run the same command – observe early hang.\\n5. Re-enable the bootstrap plugin and re-run – observe later hang.\\n\\n---\\n\\n**Expected behavior**\\n\\n`startAgent` should finish initializing an agent regardless of whether `@elizaos/plugin-bootstrap` is present. \\nIf the bootstrap plugin is mandatory there should be a clear validation error, not a silent hang.\\n\\n---\\n\\n**Logs / Screenshots**\\n\\n
\\n1️⃣ Hang without bootstrap plugin (early-stage)\\n\\n```\\n[2025-08-04 02:47:47] INFO: [startAgent] Step 1 – Starting agent initialization\\n[2025-08-04 02:47:47] INFO: [startAgent] Step 2 – Character ID set\\n[2025-08-04 02:47:47] INFO: [startAgent] Step 3 – Checking character secrets\\n[2025-08-04 02:47:47] INFO: [startAgent] Step 3c – Character already has secrets\\n[2025-08-04 02:47:47] INFO: [startAgent] Step 4 – Initializing plugin loading\\n[2025-08-04 02:47:47] INFO: [startAgent] Step 4a – SQL plugin loaded\\n[2025-08-04 02:47:47] INFO: [startAgent] Step 4b – Character plugins: [\\\"@elizaos/plugin-e2b\\\",\\\"@elizaos/plugin-openai\\\"]\\n... nothing further – process hangs here ...\\n```\\n
\\n\\n
\\n2️⃣ Hang with bootstrap plugin (late-stage)\\n\\n```\\n[2025-08-04 02:52:47] INFO: [loadAndPreparePlugin] Step 1 – Starting to load plugin: @elizaos/plugin-bootstrap\\n[2025-08-04 02:52:47] SUCCESS: Successfully loaded plugin '@elizaos/plugin-bootstrap' using workspace dependency\\n[2025-08-04 02:52:47] INFO: [loadAndPreparePlugin] Step 4e – Found valid plugin export\\n[2025-08-04 02:52:47] INFO: [startAgent] Step 5d – Successfully loaded plugin: bootstrap\\n... no further output – runtime hangs right after this point ...\\n```\\n
\\n\\n---\\n\\n**Additional context**\\n\\n* The call site is `packages/cli/src/scenarios/runtime-factory.ts` → `initializeAgent()`.\\n* `startAgent` is imported with \\n `import { startAgent } from '../commands/start';`\\n* Hangs occur both in **local** and **E2B** scenarios.\\n* Database migrations complete successfully; the hang happens after plugin loading.\\n* Removing *all* plugins except SQL reproduces the *early* hang; adding any plugin that has bootstrap as a dep reproduces the *late* hang.\\n* The same code path works in commit `510b8aac2e0b20cc3d176093a58143c26e838e65` (July 25 commit) but fails from `d84963ef3d5f5cccfef461350175dc1bc9b77b58` onward.\\n\\nPlease review my branch and the file for the associated changes. I review the plugin loading stack trace loadAndPreparePlugin -> loadPluginModule -> strategy.tryImport (which is where it hangs \\n\\n```\\n */\\nconst importStrategies: ImportStrategy[] = [\\n // Try local development first - this is the most important for plugin testing\\n {\\n name: 'local development plugin',\\n tryImport: async (repository: string) => {\\n const context = detectPluginContext(repository);\\n\\n if (context.isLocalDevelopment) {\\n logger.debug(`Detected local development for plugin: ${repository}`);\\n\\n // Ensure the plugin is built\\n const isBuilt = await ensurePluginBuilt(context);\\n if (!isBuilt) {\\n provideLocalPluginGuidance(repository, context);\\n return null;\\n }\\n\\n // Try to load from built output\\n if (context.localPath && existsSync(context.localPath)) {\\n logger.info(`Loading local development plugin: ${repository}`);\\n return tryImporting(context.localPath, 'local development plugin', repository);\\n }\\n\\n // This shouldn't happen if ensurePluginBuilt succeeded, but handle it gracefully\\n logger.warn(`Plugin built but output not found at expected path: ${context.localPath}`);\\n provideLocalPluginGuidance(repository, context);\\n return null;\\n }\\n\\n return null;\\n },\\n },\\n // Try workspace dependencies (for monorepo packages)\\n {\\n name: 'workspace dependency',\\n tryImport: async (repository: string) => {\\n if (repository.startsWith('@elizaos/plugin-')) {\\n // Try to find the plugin in the workspace\\n const pluginName = repository.replace('@elizaos/', '');\\n const workspacePath = path.resolve(process.cwd(), '..', pluginName, 'dist', 'index.js');\\n if (existsSync(workspacePath)) {\\n return tryImporting(workspacePath, 'workspace dependency', repository);\\n }\\n }\\n return null;\\n },\\n },\\n {\\n name: 'direct path',\\n tryImport: async (repository: string) => tryImporting(repository, 'direct path', repository),\\n },\\n {\\n name: 'local node_modules',\\n tryImport: async (repository: string) =>\\n tryImporting(resolveNodeModulesPath(repository), 'local node_modules', repository),\\n },\\n {\\n name: 'global node_modules',\\n tryImport: async (repository: string) => {\\n const globalPath = path.resolve(getGlobalNodeModulesPath(), repository);\\n if (!existsSync(path.dirname(globalPath))) {\\n logger.debug(\\n `Global node_modules directory not found at ${path.dirname(globalPath)}, skipping for ${repository}`\\n );\\n return null;\\n }\\n return tryImporting(globalPath, 'global node_modules', repository);\\n },\\n },\\n {\\n name: 'package.json entry',\\n tryImport: async (repository: string) => {\\n const packageJson = await readPackageJson(repository);\\n if (!packageJson) return null;\\n\\n const entryPoint = packageJson.module || packageJson.main || DEFAULT_ENTRY_POINT;\\n return tryImporting(\\n resolveNodeModulesPath(repository, entryPoint),\\n `package.json entry (${entryPoint})`,\\n repository\\n );\\n },\\n },\\n {\\n name: 'common dist pattern',\\n tryImport: async (repository: string) => {\\n const packageJson = await readPackageJson(repository);\\n if (packageJson?.main === DEFAULT_ENTRY_POINT) return null;\\n\\n return tryImporting(\\n resolveNodeModulesPath(repository, DEFAULT_ENTRY_POINT),\\n 'common dist pattern',\\n repository\\n );\\n },\\n },\\n];\\n``` in load-plugin.ts BRANCH in question: https://github.com/elizaOS/eliza/blob/scenarios-cli/packages/cli/src/scenarios/runtime-factory.ts\\n\\n\\nbut startAgent is in develop and is having issues when its being called. \",\n \"createdAt\": \"2025-08-05T02:45:31Z\",\n \"closedAt\": \"2025-08-14T02:44:06Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 5\n },\n {\n \"id\": \"I_kwDOMT5cIs7EwwuN\",\n \"title\": \"Eliza CLI failed to build project\",\n \"author\": \"Kemystra\",\n \"number\": 5734,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nOn project creation, ElizaOS CLI fails with the following error:\\n```\\n◇ Failed to build project\\nstdout: src/index.ts(7,25): error TS2345: Argument of type 'string' is not assignable to parameter of type 'undefined'.\\nstderr: $ tsc --noEmit && vite build && tsup\\n```\\n\\n**To Reproduce**\\n\\n- Install ElizaOS through `bun`\\n```\\nbun i -g @elizaos/cli\\n```\\n- Create new ElizaOS project\\n```\\nelizaos create abcde\\n```\\n\\n**Expected behavior**\\n\\nProject built successfully\\n\\n**Screenshots**\\n\\n\\\"Image\\\"\\n\\n**Additional context**\\n\\nElizaOS CLI version: `1.3.2`\\n\",\n \"createdAt\": \"2025-08-07T16:14:00Z\",\n \"closedAt\": \"2025-08-14T07:09:33Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs7Engk3\",\n \"title\": \"feat(scenarios): Implement conditional mocking and complex response structures\",\n \"author\": \"monilpat\",\n \"number\": 5726,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"# feat(scenarios): Implement conditional mocking and complex response structures\\n\\n## Description\\n\\nThis ticket enhances the mocking system to support conditional responses based on input parameters and complex response structures with metadata. This enables realistic testing of service interactions like GitHub API calls or EVM transactions with proper request/response matching.\\n\\n## Acceptance Criteria\\n\\n1. Mock definitions support `when` clauses for conditional responses\\n2. `when` clauses can match on method arguments, input parameters, or request context\\n3. Mock responses support complex nested structures with metadata (timestamps, IDs, etc.)\\n4. Multiple mock responses can be defined for the same service/method with different conditions\\n5. Mock system provides clear logging of which mock was triggered and why\\n6. Mock responses can include realistic error conditions and edge cases\\n7. Support for dynamic response generation based on input parameters\\n8. Mock validation ensures `when` clauses are syntactically correct\\n\\n## Technical Approach\\n\\n### 1. Enhanced Mock Schema\\n```typescript\\n// packages/cli/src/scenarios/schema.ts\\nconst MockSchema = z.object({\\n service: z.string(),\\n method: z.string(),\\n when: z.object({\\n // Match on method arguments\\n args: z.array(z.any()).optional(),\\n // Match on specific argument values\\n input: z.record(z.any()).optional(),\\n // Match on request context\\n context: z.record(z.any()).optional(),\\n // Custom matching function\\n matcher: z.string().optional(), // JavaScript expression\\n }).optional(),\\n response: z.any(), // Can be function or static value\\n // For dynamic responses\\n responseFn: z.string().optional(), // JavaScript function\\n // Error simulation\\n error: z.object({\\n code: z.string(),\\n message: z.string(),\\n }).optional(),\\n});\\n```\\n\\n### 2. Mock Engine Implementation\\n```typescript\\n// packages/cli/src/scenarios/mock-engine.ts\\nexport class MockEngine {\\n private mocks: MockDefinition[] = [];\\n\\n addMock(mock: MockDefinition) {\\n this.mocks.push(mock);\\n }\\n\\n async findMock(service: string, method: string, args: any[]): Promise {\\n const candidates = this.mocks.filter(m => \\n m.service === service && m.method === method\\n );\\n\\n for (const mock of candidates) {\\n if (await this.matchesCondition(mock, args)) {\\n this.logger.info(`Mock triggered: ${service}.${method} with condition: ${JSON.stringify(mock.when)}`);\\n return this.generateResponse(mock, args);\\n }\\n }\\n\\n return null; // No mock found\\n }\\n\\n private async matchesCondition(mock: MockDefinition, args: any[]): Promise {\\n if (!mock.when) return true; // Default mock\\n\\n // Match on arguments\\n if (mock.when.args) {\\n if (!this.deepEqual(args, mock.when.args)) return false;\\n }\\n\\n // Match on input parameters\\n if (mock.when.input) {\\n const input = this.extractInputFromArgs(args);\\n if (!this.deepEqual(input, mock.when.input)) return false;\\n }\\n\\n // Custom matcher function\\n if (mock.when.matcher) {\\n const matcherFn = new Function('args', 'input', mock.when.matcher);\\n return matcherFn(args, this.extractInputFromArgs(args));\\n }\\n\\n return true;\\n }\\n\\n private generateResponse(mock: MockDefinition, args: any[]): any {\\n if (mock.error) {\\n throw new Error(`${mock.error.code}: ${mock.error.message}`);\\n }\\n\\n if (mock.responseFn) {\\n const responseFn = new Function('args', 'input', mock.responseFn);\\n return responseFn(args, this.extractInputFromArgs(args));\\n }\\n\\n return mock.response;\\n }\\n}\\n```\\n\\n## Test Scenario\\n\\nCreate `advanced-mocking-test.scenario.yaml`:\\n```yaml\\nname: \\\"Advanced Mocking Test\\\"\\ndescription: \\\"Tests conditional mocking and complex response structures\\\"\\n\\nplugins:\\n - \\\"@elizaos/plugin-github\\\"\\n - \\\"@elizaos/plugin-evm\\\"\\n\\nenvironment:\\n type: e2b\\n\\nsetup:\\n mocks:\\n # Conditional GitHub issue search\\n - service: \\\"github-service\\\"\\n method: \\\"searchIssues\\\"\\n when:\\n input:\\n labels: \\\"bug\\\"\\n matcher: \\\"input.labels.includes('bug')\\\"\\n response:\\n - title: \\\"Critical Bug Found\\\"\\n number: 456\\n state: \\\"open\\\"\\n labels: [\\\"bug\\\", \\\"critical\\\"]\\n created_at: \\\"2024-07-15T10:00:00Z\\\"\\n\\n # Conditional GitHub issue search - different response\\n - service: \\\"github-service\\\"\\n method: \\\"searchIssues\\\"\\n when:\\n input:\\n labels: \\\"feature\\\"\\n matcher: \\\"input.labels.includes('feature')\\\"\\n response:\\n - title: \\\"New Feature Request\\\"\\n number: 789\\n state: \\\"open\\\"\\n labels: [\\\"feature\\\", \\\"enhancement\\\"]\\n created_at: \\\"2024-07-15T11:00:00Z\\\"\\n\\n # Dynamic EVM balance response\\n - service: \\\"evm-service\\\"\\n method: \\\"getBalancesForAddress\\\"\\n when:\\n args: [\\\"0x1234567890abcdef\\\"]\\n responseFn: |\\n return {\\n chain: \\\"ethereum\\\",\\n address: args[0],\\n balances: [\\n { symbol: \\\"ETH\\\", amount: \\\"1.23\\\" },\\n { symbol: \\\"USDC\\\", amount: \\\"1000.00\\\" }\\n ],\\n last_updated: new Date().toISOString()\\n }\\n\\n # Error simulation\\n - service: \\\"github-service\\\"\\n method: \\\"readFile\\\"\\n when:\\n input:\\n path: \\\"/docs/nonexistent.md\\\"\\n error:\\n code: \\\"FILE_NOT_FOUND\\\"\\n message: \\\"File does not exist\\\"\\n\\nrun:\\n - name: \\\"Test conditional GitHub search\\\"\\n input: \\\"Search for issues with bug label\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"github-service.searchIssues\\\"\\n - type: \\\"string_contains\\\"\\n value: \\\"Critical Bug Found\\\"\\n - type: \\\"llm_judge\\\"\\n prompt: \\\"Did the agent correctly search for bug issues?\\\"\\n expected: \\\"yes\\\"\\n\\n - name: \\\"Test dynamic EVM response\\\"\\n input: \\\"What's the balance for address 0x1234567890abcdef?\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"evm-service.getBalancesForAddress\\\"\\n - type: \\\"string_contains\\\"\\n value: \\\"1.23 ETH\\\"\\n - type: \\\"string_contains\\\"\\n value: \\\"1000.00 USDC\\\"\\n\\n - name: \\\"Test error handling\\\"\\n input: \\\"Read the file /docs/nonexistent.md\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"github-service.readFile\\\"\\n - type: \\\"string_contains\\\"\\n value: \\\"File does not exist\\\"\\n\\njudgment:\\n strategy: all_pass\\n```\\n\\n## Testing Strategy\\n\\n1. **Conditional Matching**: Test different responses based on input parameters\\n2. **Dynamic Responses**: Test response generation based on arguments\\n3. **Error Simulation**: Test error handling and reporting\\n4. **Complex Structures**: Test nested response objects with metadata\\n5. **Multiple Mocks**: Test multiple mocks for same service/method\\n6. **Logging**: Verify mock selection is logged clearly\\n\\n## Dependencies\\n\\n- Builds on existing mock system in scenarios\\n- Requires plugin system integration (Ticket 1)\\n- Integrates with agent interaction testing (Ticket 3) \",\n \"createdAt\": \"2025-08-07T02:49:00Z\",\n \"closedAt\": \"2025-08-12T04:21:45Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs7Eng6F\",\n \"title\": \"feat(scenarios): Implement natural language agent interaction and response validation\",\n \"author\": \"monilpat\",\n \"number\": 5727,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"# feat(scenarios): Implement natural language agent interaction and response validation\\n\\n## Description\\n\\nThis ticket enables scenarios to test agent behavior through natural language interactions rather than direct code execution. This allows testing of agent reasoning, decision-making, and response generation in realistic conversation contexts with proper evaluation of agent responses.\\n\\n## Acceptance Criteria\\n\\n1. Scenario `run` blocks support `input` field for natural language prompts to agents\\n2. Agent responses are captured and available for evaluation (text, thoughts, actions)\\n3. Evaluators can access both agent response text and execution context\\n4. Support for multi-turn conversations in scenarios\\n5. Agent responses include thought process and action decisions\\n6. Integration with existing evaluation engine for response validation\\n7. Support for conversation context across multiple steps\\n8. Agent response timing and performance metrics\\n\\n## Technical Approach\\n\\n### 1. Enhanced Run Step Schema\\n```typescript\\n// packages/cli/src/scenarios/schema.ts\\nconst RunStepSchema = z.object({\\n name: z.string().optional(),\\n // Natural language input to agent\\n input: z.string().optional(),\\n // Direct code execution (existing)\\n lang: z.string().optional(),\\n code: z.string().optional(),\\n // Agent interaction specific\\n agent_context: z.object({\\n conversation_id: z.string().optional(),\\n user_id: z.string().optional(),\\n room_id: z.string().optional(),\\n }).optional(),\\n evaluations: z.array(EvaluationSchema),\\n});\\n```\\n\\n### 2. Agent Interaction Engine\\n```typescript\\n// packages/cli/src/scenarios/agent-interaction.ts\\nexport class AgentInteractionEngine {\\n constructor(private runtime: IAgentRuntime) {}\\n\\n async interactWithAgent(input: string, context?: AgentContext): Promise {\\n // Create message for agent\\n const message: Memory = {\\n entityId: context?.user_id || 'scenario-user',\\n roomId: context?.room_id || 'scenario-room',\\n content: {\\n type: 'text',\\n text: input,\\n },\\n metadata: {\\n type: 'message',\\n conversationId: context?.conversation_id,\\n },\\n };\\n\\n // Send to agent and capture response\\n const startTime = Date.now();\\n const response = await this.runtime.processMessage(message);\\n const endTime = Date.now();\\n\\n return {\\n text: response.text,\\n thoughts: response.thoughts,\\n actions: response.actions,\\n timing: {\\n startTime,\\n endTime,\\n duration: endTime - startTime,\\n },\\n context: {\\n conversationId: context?.conversation_id,\\n messageId: message.id,\\n },\\n };\\n }\\n}\\n```\\n\\n### 3. Enhanced Execution Result\\n```typescript\\n// packages/cli/src/scenarios/providers.ts\\nexport interface ExecutionResult {\\n exitCode: number;\\n stdout: string;\\n stderr: string;\\n files: Record;\\n // New: Agent interaction results\\n agentResponse?: AgentResponse;\\n conversationHistory?: AgentResponse[];\\n}\\n```\\n\\n## Test Scenario\\n\\nCreate `agent-interaction-test.scenario.yaml`:\\n```yaml\\nname: \\\"Agent Interaction Test\\\"\\ndescription: \\\"Tests natural language interaction with agents\\\"\\n\\nplugins:\\n - \\\"@elizaos/plugin-github\\\"\\n - \\\"@elizaos/plugin-evm\\\"\\n\\nenvironment:\\n type: e2b\\n\\nsetup:\\n mocks:\\n - service: \\\"github-service\\\"\\n method: \\\"searchIssues\\\"\\n response:\\n - title: \\\"Implement Dark Mode\\\"\\n number: 123\\n state: \\\"open\\\"\\n labels: [\\\"feature\\\", \\\"ui\\\"]\\n - service: \\\"evm-service\\\"\\n method: \\\"getBalancesForAddress\\\"\\n response:\\n - chain: \\\"ethereum\\\"\\n balances:\\n - symbol: \\\"ETH\\\"\\n amount: \\\"2.5\\\"\\n\\nrun:\\n - name: \\\"Ask agent about roadmap\\\"\\n input: \\\"What new features are you planning to add?\\\"\\n agent_context:\\n conversation_id: \\\"roadmap-conversation\\\"\\n user_id: \\\"test-user\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"github-service.searchIssues\\\"\\n description: \\\"Verify agent searched for issues\\\"\\n \\n - type: \\\"string_contains\\\"\\n value: \\\"Dark Mode\\\"\\n description: \\\"Verify agent mentioned the mocked issue\\\"\\n \\n - type: \\\"llm_judge\\\"\\n prompt: \\\"Did the agent provide a helpful and coherent response about new features?\\\"\\n expected: \\\"yes\\\"\\n description: \\\"Verify agent response quality\\\"\\n\\n - name: \\\"Ask agent about wallet\\\"\\n input: \\\"What's my current wallet balance?\\\"\\n agent_context:\\n conversation_id: \\\"wallet-conversation\\\"\\n user_id: \\\"test-user\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"evm-service.getBalancesForAddress\\\"\\n description: \\\"Verify agent checked wallet balance\\\"\\n \\n - type: \\\"string_contains\\\"\\n value: \\\"2.5 ETH\\\"\\n description: \\\"Verify agent reported the correct balance\\\"\\n \\n - type: \\\"llm_judge\\\"\\n prompt: \\\"Did the agent clearly explain the wallet balance information?\\\"\\n expected: \\\"yes\\\"\\n\\n - name: \\\"Multi-turn conversation\\\"\\n input: \\\"Can you help me with both my wallet and roadmap?\\\"\\n agent_context:\\n conversation_id: \\\"multi-turn-conversation\\\"\\n user_id: \\\"test-user\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"evm-service.getBalancesForAddress\\\"\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"github-service.searchIssues\\\"\\n - type: \\\"string_contains\\\"\\n value: \\\"ETH\\\"\\n - type: \\\"string_contains\\\"\\n value: \\\"Dark Mode\\\"\\n - type: \\\"llm_judge\\\"\\n prompt: \\\"Did the agent address both wallet and roadmap questions comprehensively?\\\"\\n expected: \\\"yes\\\"\\n\\njudgment:\\n strategy: all_pass\\n```\\n\\n## Testing Strategy\\n\\n1. **Single Turn**: Test basic agent interaction and response\\n2. **Multi-turn**: Test conversation context across steps\\n3. **Action Tracking**: Verify agent uses appropriate actions\\n4. **Response Quality**: Test LLM judge evaluation of responses\\n5. **Performance**: Test response timing and metrics\\n6. **Error Handling**: Test agent behavior with invalid inputs\\n\\n## Dependencies\\n\\n- Requires plugin system integration (Ticket 1)\\n- Builds on advanced mocking system (Ticket 2)\\n- Integrates with existing evaluation engine\\n- Depends on agent runtime message processing\",\n \"createdAt\": \"2025-08-07T02:49:34Z\",\n \"closedAt\": \"2025-08-12T04:21:31Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 2\n },\n {\n \"id\": \"I_kwDOMT5cIs7EngKo\",\n \"title\": \"feat(scenarios): Implement plugin specification and dynamic loading\",\n \"author\": \"monilpat\",\n \"number\": 5725,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"# feat(scenarios): Implement plugin specification and dynamic loading\\n\\n## Description\\n\\nThis ticket implements plugin specification in scenario YAML files, allowing scenarios to declare which plugins are required for testing. This enables testing of agent behaviors that depend on specific plugins like `@elizaos/plugin-github` or `@elizaos/plugin-evm`. The system will dynamically load specified plugins during scenario execution and make their actions, providers, and services available to the agent.\\n\\n## Acceptance Criteria\\n\\n1. Scenario YAML supports a `plugins` array at the root level with string plugin names\\n2. The `initializeAgent()` function respects scenario plugin specifications and loads them via `startAgent()`\\n3. Plugin loading follows the same dependency resolution and error handling as the main CLI\\n4. Scenarios can specify both string plugin names (`@elizaos/plugin-github`) and direct plugin objects\\n5. Plugin loading errors are clearly reported with actionable guidance\\n6. Default plugins (bootstrap, sql) are automatically included unless explicitly excluded via `exclude_defaults: true`\\n7. Plugin conflicts are detected and reported during scenario validation\\n8. Plugin initialization errors don't crash the scenario but are reported in results\\n\\n## Technical Approach\\n\\n### 1. Update Scenario Schema\\n```typescript\\n// packages/cli/src/scenarios/schema.ts\\nconst ScenarioSchema = z.object({\\n name: z.string(),\\n description: z.string(),\\n plugins: z.array(z.string()).optional(), // e.g., [\\\"@elizaos/plugin-github\\\"]\\n exclude_defaults: z.boolean().optional(), // exclude bootstrap/sql\\n environment: EnvironmentSchema,\\n setup: SetupSchema.optional(),\\n run: z.array(RunStepSchema),\\n judgment: JudgmentSchema,\\n});\\n```\\n\\n### 2. Enhance Runtime Factory\\n```typescript\\n// packages/cli/src/scenarios/runtime-factory.ts\\nexport async function initializeAgent(scenario: Scenario): Promise {\\n const character: Character = {\\n name: 'scenario-runner',\\n id: stringToUuid('scenario-runner'),\\n bio: 'A minimal character for running scenarios',\\n plugins: scenario.plugins || []\\n };\\n\\n // Load default plugins unless excluded\\n if (!scenario.exclude_defaults) {\\n character.plugins.push('@elizaos/plugin-bootstrap', '@elizaos/plugin-sql');\\n }\\n\\n const runtime = await startAgent(\\n encryptedCharacter(character),\\n server,\\n undefined,\\n character.plugins,\\n { isTestMode: true }\\n );\\n\\n return runtime;\\n}\\n```\\n\\n### 3. Plugin Validation\\n```typescript\\n// packages/cli/src/scenarios/plugin-validator.ts\\nexport async function validateScenarioPlugins(scenario: Scenario): Promise {\\n const results: ValidationResult[] = [];\\n \\n for (const pluginName of scenario.plugins || []) {\\n try {\\n const plugin = await loadAndPreparePlugin(pluginName);\\n if (!plugin) {\\n results.push({\\n type: 'error',\\n message: `Plugin '${pluginName}' could not be loaded`,\\n suggestion: 'Check if plugin is installed or built correctly'\\n });\\n }\\n } catch (error) {\\n results.push({\\n type: 'error', \\n message: `Failed to validate plugin '${pluginName}': ${error.message}`,\\n suggestion: 'Verify plugin dependencies and configuration'\\n });\\n }\\n }\\n \\n return results;\\n}\\n```\\n\\n## Test Scenario\\n\\nCreate `plugin-integration-test.scenario.yaml`:\\n```yaml\\nname: \\\"Plugin Integration Test\\\"\\ndescription: \\\"Tests loading and using plugins specified in scenario YAML\\\"\\n\\nplugins:\\n - \\\"@elizaos/plugin-github\\\"\\n - \\\"@elizaos/plugin-evm\\\"\\n\\nenvironment:\\n type: e2b\\n\\nsetup:\\n mocks:\\n - service: \\\"github-service\\\"\\n method: \\\"searchIssues\\\"\\n response:\\n - title: \\\"Test Issue\\\"\\n number: 123\\n state: \\\"open\\\"\\n - service: \\\"evm-service\\\"\\n method: \\\"getBalancesForAddress\\\"\\n response:\\n - chain: \\\"ethereum\\\"\\n balances:\\n - symbol: \\\"ETH\\\"\\n amount: \\\"1.23\\\"\\n\\nrun:\\n - name: \\\"Test GitHub plugin actions\\\"\\n input: \\\"Search for issues with label 'bug'\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"github-service.searchIssues\\\"\\n description: \\\"Verify GitHub plugin action was executed\\\"\\n \\n - type: \\\"string_contains\\\"\\n value: \\\"Test Issue\\\"\\n description: \\\"Verify agent found the mocked issue\\\"\\n\\n - name: \\\"Test EVM plugin actions\\\"\\n input: \\\"What's my wallet balance?\\\"\\n evaluations:\\n - type: \\\"trajectory_contains_action\\\"\\n action: \\\"evm-service.getBalancesForAddress\\\"\\n description: \\\"Verify EVM plugin action was executed\\\"\\n \\n - type: \\\"string_contains\\\"\\n value: \\\"1.23 ETH\\\"\\n description: \\\"Verify agent reported the mocked balance\\\"\\n\\njudgment:\\n strategy: all_pass\\n```\\n\\n## Testing Strategy\\n\\n1. **Plugin Loading Test**: Verify plugins load without errors\\n2. **Action Availability Test**: Confirm agent can use plugin actions\\n3. **Error Handling Test**: Test with non-existent plugin\\n4. **Default Plugin Test**: Verify bootstrap/sql are included by default\\n5. **Exclusion Test**: Test `exclude_defaults: true` behavior\\n\\n## Dependencies\\n\\n- Fixes the `startAgent` hanging issue (#5719) to enable plugin testing\\n- Builds on existing `loadAndPreparePlugin` functionality\\n- Integrates with current scenario execution flow \",\n \"createdAt\": \"2025-08-07T02:48:08Z\",\n \"closedAt\": \"2025-08-12T04:21:13Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 2\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6bjrTf\",\n \"title\": \"Next\",\n \"author\": \"lalalune\",\n \"number\": 5242,\n \"body\": \"Roads? Where we're going, we don't need roads!\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-06-22T16:11:08Z\",\n \"mergedAt\": null,\n \"additions\": 1367486,\n \"deletions\": 69177\n },\n {\n \"id\": \"PR_kwDOMT5cIs6iAhom\",\n \"title\": \"Fix memory count and agent id errors\",\n \"author\": \"wtfsayo\",\n \"number\": 5712,\n \"body\": \"```\\n# Relates to\\n\\n\\n\\n# Risks\\n\\nLow. This PR fixes a display bug and adds error handling for invalid input, improving robustness without introducing new functionality.\\n\\n# Background\\n\\n## What does this PR do?\\n\\n* Corrects the `clearAgentMemories` command to use `result?.deletedCount` instead of `result?.deleted` to accurately display the number of cleared memories.\\n* Adds robust error handling for `asUUID(resolvedAgentId)` calls in `removeAgent`, `clearAgentMemories`, and `setAgentConfig` commands. This prevents unhandled errors when an invalid agent ID format (non-UUID) is provided.\\n\\n## What kind of change is this?\\n\\nBug fixes\\n\\n## Why are we doing this? Any context or related work?\\n\\nThe `clearAgentMemories` command was incorrectly displaying '0 memories cleared' because it expected a `deleted` property from the API response, while the API returns `deletedCount`. Additionally, the `removeAgent`, `clearAgentMemories`, and `setAgentConfig` commands lacked proper error handling for invalid UUIDs passed to `asUUID`, which could lead to unhandled exceptions.\\n\\n# Documentation changes needed?\\n\\nMy changes do not require a change to the project documentation.\\n\\n# Testing\\n\\n## Where should a reviewer start?\\n\\n`packages/cli/src/commands/agent/actions/crud.ts`\\n\\n## Detailed testing steps\\n\\n* **Verify `clearAgentMemories` count display**:\\n 1. Ensure an agent has some memories (e.g., by interacting with it).\\n 2. Run `npm run cli agent clear-memories --name ` (or by UUID/index).\\n 3. Verify the output correctly displays the number of cleared memories (e.g., \\\"Successfully cleared X memories...\\\").\\n* **Verify `asUUID` error handling**:\\n 1. Run `npm run cli agent remove --name invalid-uuid-format`.\\n 2. Verify an error message like \\\"Invalid agent ID format: invalid-uuid-format. Please provide a valid UUID, agent name, or index.\\\" is displayed.\\n 3. Repeat steps 1 and 2 for `npm run cli agent clear-memories --name invalid-uuid-format`.\\n 4. Repeat steps 1 and 2 for `npm run cli agent set --name invalid-uuid-format --config '{ \\\"name\\\": \\\"test\\\" }'`.\\n```\\n\\n---\\n\\n \\n \\n \\n \\\"Open\\n \\n\\n\\n \\n \\n \\n \\\"Open\\n \\n\\n\\n[Learn more](https://docs.cursor.com/background-agent/web-and-mobile) about Cursor Agents\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-08-04T13:43:39Z\",\n \"mergedAt\": null,\n \"additions\": 46580,\n \"deletions\": 142155\n },\n {\n \"id\": \"PR_kwDOMT5cIs6iADWo\",\n \"title\": \"Fix agent id uuid conversion in getAgent command\",\n \"author\": \"wtfsayo\",\n \"number\": 5711,\n \"body\": \"# Relates to\\n\\n\\n\\n# Risks\\n\\nLow. This PR improves error handling without changing core logic.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nThis PR enhances the `getAgent` command by adding robust error handling for UUID conversion. It wraps the `asUUID(resolvedAgentId)` call in a try-catch block, providing a more descriptive error message if the `resolvedAgentId` cannot be converted to a valid UUID.\\n\\n## What kind of change is this?\\n\\nBug fixes (non-breaking change which fixes an issue)\\nImprovements (misc. changes to existing features)\\n\\n## Why are we doing this? Any context or related work?\\n\\nThe `getAgent` command's use of `asUUID(resolvedAgentId)` could lead to runtime failures if `resolvedAgentId` (even after being resolved from a name, index, or string ID) is not a valid UUID. While `resolveAgentId` is intended to return a UUID, this change adds a safeguard against potential data inconsistencies or unexpected inputs, providing a clearer, user-friendly error message instead of a generic validation error. This improves the command's resilience.\\n\\n# Documentation changes needed?\\n\\nMy changes do not require a change to the project documentation.\\n\\n# Testing\\n\\n## Where should a reviewer start?\\n\\n`packages/cli/src/commands/agent/actions/crud.ts` at line 31.\\n\\n## Detailed testing steps\\n\\n1. **Verify existing functionality**:\\n * Create an agent: `eliza agent create --name myagent`\\n * Get the agent by name: `eliza agent get --name myagent` (should succeed)\\n * Get the agent by its UUID (copy from `eliza agent list`): `eliza agent get --id ` (should succeed)\\n * Get the agent by index: `eliza agent get --index 0` (should succeed)\\n2. **Verify new error handling**:\\n * Attempt to get an agent with a clearly invalid, non-UUID string that `resolveAgentId` might theoretically pass through (e.g., `eliza agent get --id \\\"not-a-uuid\\\"`).\\n * Verify that the command now outputs the custom error message: \\\"Invalid agent ID format: not-a-uuid. Please provide a valid UUID, agent name, or index.\\\"\\n\\n---\\n\\n \\n \\n \\n \\\"Open\\n \\n\\n\\n \\n \\n \\n \\\"Open\\n \\n\\n\\n[Learn more](https://docs.cursor.com/background-agent/web-and-mobile) about Cursor Agents\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-08-04T13:07:05Z\",\n \"mergedAt\": null,\n \"additions\": 46565,\n \"deletions\": 142158\n },\n {\n \"id\": \"PR_kwDOMT5cIs6h_-Oc\",\n \"title\": \"Fix agent config output exclusion\",\n \"author\": \"wtfsayo\",\n \"number\": 5710,\n \"body\": \"# Relates to\\n\\nN/A\\n\\n# Risks\\n\\nLow - This change only affects the output format of agent configuration and does not alter core functionality or data.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nThis PR restores the previous behavior of excluding the `enabled` field from the agent configuration when saving to a file (using `--output`) or displaying as JSON (using `--json`).\\n\\n## What kind of change is this?\\n\\nBug fixes\\n\\n## Why are we doing this? Any context or related work?\\n\\nThe `enabled` field was inadvertently included in the agent configuration output, which was a regression from the previous behavior where it was explicitly excluded. This fix ensures consistency with the expected output format.\\n\\n# Documentation changes needed?\\n\\nMy changes do not require a change to the project documentation.\\n\\n# Testing\\n\\n## Where should a reviewer start?\\n\\n`packages/cli/src/commands/agent/actions/crud.ts`\\n\\n## Detailed testing steps\\n\\n1. Run the agent command with the `--output` flag:\\n `your-cli-command agent get --output agent_config.json`\\n Verify that `agent_config.json` does *not* contain the `enabled` field.\\n2. Run the agent command with the `--json` flag:\\n `your-cli-command agent get --json`\\n Verify that the JSON output in the console does *not* contain the `enabled` field.\\n\\n---\\n\\n \\n \\n \\n \\\"Open\\n \\n\\n\\n \\n \\n \\n \\\"Open\\n \\n\\n\\n[Learn more](https://docs.cursor.com/background-agent/web-and-mobile) about Cursor Agents\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-08-04T13:00:58Z\",\n \"mergedAt\": null,\n \"additions\": 46560,\n \"deletions\": 142159\n },\n {\n \"id\": \"PR_kwDOMT5cIs6lddBz\",\n \"title\": \"merge develop\",\n \"author\": \"tcm390\",\n \"number\": 5826,\n \"body\": \"\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-08-26T17:47:19Z\",\n \"mergedAt\": null,\n \"additions\": 35368,\n \"deletions\": 49768\n }\n ],\n \"codeChanges\": {\n \"additions\": 61261,\n \"deletions\": 45596,\n \"files\": 542,\n \"commitCount\": 606\n },\n \"completedItems\": [\n {\n \"title\": \"feat: add CLI delegation debug tool\",\n \"prNumber\": 5682,\n \"type\": \"feature\",\n \"body\": \"## Overview\\n\\nThis PR adds a comprehensive debug tool for diagnosing ElizaOS CLI delegation issues. The script helps developers understand why local CLI delegation might not be working and provides automatic fixes for common problems.\\n\\n## Fe\",\n \"files\": [\n \"packages/cli/src/utils/local-cli-delegation.ts\",\n \"packages/cli/tests/unit/utils/local-cli-delegation.test.ts\",\n \"scripts/debug-cli-delegation.test.ts\",\n \"scripts/debug-cli-delegation.ts\"\n ]\n },\n {\n \"title\": \"feat: Boostrap event / logging improvement\",\n \"prNumber\": 5684,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow, won't affect most copies\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- uses proper runtime logger as almost all calls are in the context of a runtime\\r\\n- new setting: BOOTSTRAP_DEFLLMOFF - turns off LLM automatically respo\",\n \"files\": [\n \"packages/plugin-bootstrap/src/index.ts\",\n \".cursor\"\n ]\n },\n {\n \"title\": \"sessions API\",\n \"prNumber\": 5704,\n \"type\": \"other\",\n \"body\": \"# Sessions API Documentation\\r\\n\\r\\nThe Sessions API provides a simplified interface for messaging between users and agents, abstracting away the complexity of servers, channels, and participants.\\r\\n\\r\\n## Overview\\r\\n\\r\\nThe Sessions API is designed \",\n \"files\": [\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/server/src/api/messaging/__tests__/sessions.test.ts\",\n \"packages/server/src/api/messaging/index.ts\",\n \"packages/server/src/api/messaging/sessions.ts\",\n \"packages/server/src/services/message.ts\",\n \"packages/server/src/types.ts\",\n \"packages/server/src/types/sessions.ts\"\n ]\n },\n {\n \"title\": \"feat: auto-install @elizaos/cli as dev dependency for start/dev commands\",\n \"prNumber\": 5702,\n \"type\": \"feature\",\n \"body\": \"## 🚀 Feature: Auto-install @elizaos/cli as dev dependency using bun\\n\\n### Summary\\nAutomatically adds `@elizaos/cli` as a dev dependency using **bun** when running `start` or `dev` commands in non-monorepo environments. This improves the dev\",\n \"files\": [\n \"bun.lock\",\n \"packages/cli/src/commands/dev/actions/dev-server.ts\",\n \"packages/cli/src/commands/start/index.ts\",\n \"packages/cli/src/utils/__tests__/dependency-manager.integration.test.ts\",\n \"packages/cli/src/utils/__tests__/dependency-manager.test.ts\",\n \"packages/cli/src/utils/dependency-manager.ts\",\n \"packages/plugin-sql/src/__tests__/integration/memory.test.ts\"\n ]\n },\n {\n \"title\": \"feat: build optimization and markdown rendering support\",\n \"prNumber\": 5701,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR introduces build optimizations and enhanced markdown rendering capabilities:\\n\\n### Key Changes\\n- **Build Optimization**: Removed docs filter from main build process for more efficient builds\\n- **Dependency Cleanup**: Remo\",\n \"files\": [\n \"bun.lock\",\n \"llms.txt\",\n \"package.json\",\n \"packages/cli/package.json\",\n \"packages/client/package.json\",\n \"packages/core/package.json\"\n ]\n },\n {\n \"title\": \"remove un-necessary/obsolete readme details\",\n \"prNumber\": 5700,\n \"type\": \"other\",\n \"body\": \"This PR removes obsolete documentation from the README.md file:\\n\\n- Removes outdated LangChain integration reference from the core package description\\n- Removes extensive Tauri CI/CD documentation section that covered workflows, mobile backe\",\n \"files\": [\n \"README.md\"\n ]\n },\n {\n \"title\": \"chore: remove obsolete GitHub workflow files\",\n \"prNumber\": 5699,\n \"type\": \"other\",\n \"body\": \"This PR removes 3 obsolete GitHub workflow files that are no longer needed:\\n\\n- **deploy-cli.yml**: CLI deployment workflow\\n- **docs-publish.yml**: Documentation publishing workflow \\n- **llmstxt-generator.yml**: Repomix documentation genera\",\n \"files\": [\n \".github/workflows/deploy-cli.yml\",\n \".github/workflows/docs-publish.yml\",\n \".github/workflows/llmstxt-generator.yml\"\n ]\n },\n {\n \"title\": \"fix/elizaos test component\",\n \"prNumber\": 5705,\n \"type\": \"bugfix\",\n \"body\": \"# Fix: Enable `elizaos test --type component` for all project and plugin types\\r\\n\\r\\n## Overview\\r\\n\\r\\nThis PR fixes the `elizaos test --type component` command to ensure it passes for all project and plugin types generated by the CLI. Previously\",\n \"files\": [\n \"packages/cli/src/commands/test/actions/component-tests.ts\",\n \"packages/cli/src/commands/test/index.ts\",\n \"packages/cli/src/utils/testing/tsc-validator.ts\",\n \"packages/plugin-quick-starter/package.json\",\n \"packages/plugin-quick-starter/src/__tests__/plugin.test.ts\",\n \"packages/plugin-quick-starter/src/__tests__/test-utils.ts\",\n \"packages/plugin-quick-starter/src/plugin.ts\",\n \"packages/plugin-starter/package.json\",\n \"packages/plugin-starter/src/__tests__/integration.test.ts\",\n \"packages/plugin-starter/src/__tests__/plugin.test.ts\",\n \"packages/plugin-starter/src/__tests__/test-utils.ts\",\n \"packages/plugin-starter/src/plugin.ts\",\n \"packages/project-starter/src/__tests__/env.test.ts\",\n \"packages/project-starter/src/__tests__/file-structure.test.ts\",\n \"packages/project-starter/src/__tests__/integration.test.ts\",\n \"packages/project-tee-starter/__tests__/build-order.test.ts\",\n \"packages/project-tee-starter/__tests__/character.test.ts\",\n \"packages/project-tee-starter/__tests__/env.test.ts\",\n \"packages/project-tee-starter/__tests__/file-structure.test.ts\",\n \"packages/project-tee-starter/__tests__/tee-validation.test.ts\",\n \"packages/project-tee-starter/__tests__/vite-config-utils.ts\",\n \"packages/project-tee-starter/package.json\",\n \"packages/project-tee-starter/src/index.ts\",\n \"packages/project-tee-starter/src/plugin.ts\",\n \"packages/project-tee-starter/tsup.config.ts\",\n \"packages/project-starter/tsup.config.ts\"\n ]\n },\n {\n \"title\": \"sessions api client\",\n \"prNumber\": 5717,\n \"type\": \"other\",\n \"body\": \"## Add Sessions API to API Client SDK\\r\\n\\r\\n### Summary\\r\\nThis PR adds support for the new Sessions API to the `@elizaos/api-client` package. The Sessions API provides a simplified interface for managing stateful conversations between users and\",\n \"files\": [\n \"packages/api-client/README.md\",\n \"packages/api-client/docs/sessions-api.md\",\n \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n \"packages/api-client/src/client.ts\",\n \"packages/api-client/src/index.ts\",\n \"packages/api-client/src/services/sessions.ts\",\n \"packages/api-client/src/types/sessions.ts\",\n \"bun.lock\",\n \"packages/api-client/src/__tests__/base-client.test.ts\",\n \"packages/api-client/src/lib/base-client.ts\"\n ]\n },\n {\n \"title\": \"feat: Integrate API client and standardize workspace dependencies\",\n \"prNumber\": 5709,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR adds comprehensive authentication support to CLI agent commands and integrates the existing `@elizaos/api-client` package to eliminate code duplication. It also standardizes all workspace packages to use `workspace:*` de\",\n \"files\": [\n \".cursor\",\n \".github/workflows/cli-tests.yml\",\n \".gitmodules\",\n \".prettierignore\",\n \"bun.lock\",\n \"lerna.json\",\n \"package.json\",\n \"packages/api-client/package.json\",\n \"packages/api-client/src/types/agents.ts\",\n \"packages/cli/bunfig.toml\",\n \"packages/cli/package.json\",\n \"packages/cli/src/commands/agent/actions/crud.ts\",\n \"packages/cli/src/commands/agent/actions/lifecycle.ts\",\n \"packages/cli/src/commands/agent/index.ts\",\n \"packages/cli/src/commands/agent/utils/validation.ts\",\n \"packages/cli/src/commands/shared/auth-utils.ts\",\n \"packages/cli/src/commands/shared/index.ts\",\n \"packages/cli/src/utils/handle-error.ts\",\n \"packages/cli/tests/commands/agent.test.ts\",\n \"packages/cli/tests/commands/create.test.ts\",\n \"packages/cli/tests/commands/start.test.ts\",\n \"packages/cli/tests/commands/update.test.ts\",\n \"packages/cli/tests/test-timeouts.ts\",\n \"packages/docs/api-reference/openapi.yaml\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-quick-starter/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-starter/package.json\",\n \"packages/project-tee-starter/GUIDE.md\",\n \"packages/project-tee-starter/__tests__/frontend.test.ts\",\n \"packages/project-tee-starter/__tests__/routes.test.ts\",\n \"packages/project-tee-starter/__tests__/tee-validation.test.ts\",\n \"packages/project-tee-starter/index.html\",\n \"packages/project-tee-starter/package.json\",\n \"packages/project-tee-starter/postcss.config.js\",\n \"packages/project-tee-starter/scripts/install-test-deps.js\",\n \"packages/project-tee-starter/src/frontend/index.css\",\n \"packages/project-tee-starter/src/frontend/index.html\",\n \"packages/project-tee-starter/src/frontend/index.tsx\",\n \"packages/project-tee-starter/src/frontend/panels.tsx\",\n \"packages/project-tee-starter/src/frontend/utils.ts\",\n \"packages/project-tee-starter/src/plugin.ts\",\n \"packages/project-tee-starter/tailwind.config.js\",\n \"packages/project-tee-starter/tsconfig.build.json\",\n \"packages/project-tee-starter/tsconfig.json\",\n \"packages/project-tee-starter/vite.config.ts\",\n \"packages/server/package.json\",\n \"packages/server/src/api/memory/agents.ts\"\n ]\n },\n {\n \"title\": \"fix: Enable E2E testing for all starter templates\",\n \"prNumber\": 5720,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\r\\n\\r\\nFollowing PR #5075 which enabled component testing, E2E tests were missing or broken across starter templates. This prevented developers from validating full integration scenarios and created an inconsistent testing experience\",\n \"files\": [\n \"packages/cli/README.md\",\n \"packages/cli/src/commands/test/actions/component-tests.ts\",\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/src/commands/test/actions/run-all-tests.ts\",\n \"packages/cli/src/utils/test-runner.ts\",\n \"packages/plugin-quick-starter/README.md\",\n \"packages/plugin-quick-starter/src/__tests__/e2e/README.md\",\n \"packages/plugin-quick-starter/src/__tests__/e2e/plugin-quick-starter.e2e.ts\",\n \"packages/plugin-quick-starter/src/__tests__/plugin.test.ts\",\n \"packages/plugin-quick-starter/src/plugin.ts\",\n \"packages/plugin-starter/README.md\",\n \"packages/plugin-starter/src/__tests__/e2e/README.md\",\n \"packages/plugin-starter/src/__tests__/e2e/plugin-starter.e2e.ts\",\n \"packages/plugin-starter/src/plugin.ts\",\n \"packages/plugin-starter/src/tests.ts\",\n \"packages/project-starter/README.md\",\n \"packages/project-starter/src/__tests__/e2e/README.md\",\n \"packages/project-starter/src/__tests__/e2e/index.ts\",\n \"packages/project-starter/src/__tests__/e2e/natural-language.test.ts\",\n \"packages/project-starter/src/__tests__/e2e/project-starter.e2e.ts\",\n \"packages/project-starter/src/__tests__/e2e/project.test.ts\",\n \"packages/project-starter/src/__tests__/e2e/starter-plugin.test.ts\",\n \"packages/project-starter/src/index.ts\",\n \"packages/project-tee-starter/README.md\",\n \"packages/project-tee-starter/e2e/project.test.ts\",\n \"packages/project-tee-starter/e2e/starter-plugin.test.ts\",\n \"packages/project-tee-starter/src/__tests__/actions.test.ts\",\n \"packages/project-tee-starter/src/__tests__/build-order.test.ts\",\n \"packages/project-tee-starter/src/__tests__/character.test.ts\",\n \"packages/project-tee-starter/src/__tests__/config.test.ts\",\n \"packages/project-tee-starter/src/__tests__/e2e/README.md\",\n \"packages/project-tee-starter/src/__tests__/e2e/project-tee-starter.e2e.ts\",\n \"packages/project-tee-starter/src/__tests__/env.test.ts\",\n \"packages/project-tee-starter/src/__tests__/error-handling.test.ts\",\n \"packages/project-tee-starter/src/__tests__/events.test.ts\",\n \"packages/project-tee-starter/src/__tests__/file-structure.test.ts\",\n \"packages/project-tee-starter/src/__tests__/frontend.test.ts\",\n \"packages/project-tee-starter/src/__tests__/integration.test.ts\",\n \"packages/project-tee-starter/src/__tests__/models.test.ts\",\n \"packages/project-tee-starter/src/__tests__/plugin.test.ts\",\n \"packages/project-tee-starter/src/__tests__/provider.test.ts\",\n \"packages/project-tee-starter/src/__tests__/routes.test.ts\",\n \"packages/project-tee-starter/src/__tests__/tee-validation.test.ts\",\n \"packages/project-tee-starter/src/__tests__/test-utils.ts\",\n \"packages/project-tee-starter/src/__tests__/utils/core-test-utils.ts\",\n \"packages/project-tee-starter/src/__tests__/vite-config-utils.ts\",\n \"packages/project-tee-starter/src/index.ts\",\n \"packages/project-tee-starter/src/plugin.ts\",\n \"CLAUDE.md\",\n \"lerna.json\",\n \"packages/plugin-dummy-services/src/e2e/scenarios.ts\"\n ]\n },\n {\n \"title\": \"fix: support plugin-mysql\",\n \"prNumber\": 5718,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nLow, always ensures an adapter still\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nallows mysql before forcing plugin-sql\\r\\n\\r\\nI had looked at reording plugins but figured out how to make the order of my plugins to be not importan\",\n \"files\": [\n \"packages/cli/src/commands/start/actions/agent-start.ts\"\n ]\n },\n {\n \"title\": \"chore: remove unused specs from core\",\n \"prNumber\": 5724,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\n**Clean-up effort**: Remove obsolete plugin specification system from core package\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low risk** - This is a cleanup operation removing unused code:\\r\\n- No breaking changes to existing functionality\\r\\n- Only remov\",\n \"files\": [\n \".cursorrules\",\n \"CLAUDE.md\",\n \"bun.lock\",\n \"packages/core/package.json\",\n \"packages/core/src/index.ts\",\n \"packages/core/src/specs/README.md\",\n \"packages/core/src/specs/index.ts\",\n \"packages/core/src/specs/v1/__tests__/actionExample.test.ts\",\n \"packages/core/src/specs/v1/__tests__/integration.test.ts\",\n \"packages/core/src/specs/v1/__tests__/provider.test.ts\",\n \"packages/core/src/specs/v1/__tests__/state.test.ts\",\n \"packages/core/src/specs/v1/__tests__/templates.test.ts\",\n \"packages/core/src/specs/v1/__tests__/uuid.test.ts\",\n \"packages/core/src/specs/v1/actionExample.ts\",\n \"packages/core/src/specs/v1/index.ts\",\n \"packages/core/src/specs/v1/messages.ts\",\n \"packages/core/src/specs/v1/posts.ts\",\n \"packages/core/src/specs/v1/provider.ts\",\n \"packages/core/src/specs/v1/runtime.ts\",\n \"packages/core/src/specs/v1/state.ts\",\n \"packages/core/src/specs/v1/templates.ts\",\n \"packages/core/src/specs/v1/types.ts\",\n \"packages/core/src/specs/v1/uuid.ts\",\n \"packages/core/src/specs/v2/__tests__/actions.test.ts\",\n \"packages/core/src/specs/v2/__tests__/database.test.ts\",\n \"packages/core/src/specs/v2/__tests__/entities-extra.test.ts\",\n \"packages/core/src/specs/v2/__tests__/env.test.ts\",\n \"packages/core/src/specs/v2/__tests__/messages.test.ts\",\n \"packages/core/src/specs/v2/__tests__/mockCharacter.ts\",\n \"packages/core/src/specs/v2/__tests__/parsing.test.ts\",\n \"packages/core/src/specs/v2/__tests__/roles.test.ts\",\n \"packages/core/src/specs/v2/__tests__/runtime.test.ts\",\n \"packages/core/src/specs/v2/__tests__/search.test.ts\",\n \"packages/core/src/specs/v2/__tests__/settings.test.ts\",\n \"packages/core/src/specs/v2/__tests__/utils-extra.test.ts\",\n \"packages/core/src/specs/v2/__tests__/utils-prompt.test.ts\",\n \"packages/core/src/specs/v2/__tests__/uuid.test.ts\",\n \"packages/core/src/specs/v2/actions.ts\",\n \"packages/core/src/specs/v2/database.ts\",\n \"packages/core/src/specs/v2/entities.ts\",\n \"packages/core/src/specs/v2/index.ts\",\n \"packages/core/src/specs/v2/logger.ts\",\n \"packages/core/src/specs/v2/prompts.ts\",\n \"packages/core/src/specs/v2/roles.ts\",\n \"packages/core/src/specs/v2/runtime.ts\",\n \"packages/core/src/specs/v2/search.ts\",\n \"packages/core/src/specs/v2/services.ts\",\n \"packages/core/src/specs/v2/settings.ts\",\n \"packages/core/src/specs/v2/types.ts\",\n \"packages/core/src/specs/v2/types/stream-browserify.d.ts\"\n ]\n },\n {\n \"title\": \"feat(scenarios): Add comprehensive scenario testing system\",\n \"prNumber\": 5723,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- Add ElizaOS scenario testing system with YAML-based test definitions\\n- Support for both local and E2B sandboxed testing environments \\n- Comprehensive evaluation engine with action tracking and LLM judges\\n- Mock service support\",\n \"files\": [\n \"bun.lock\",\n \"package.json\",\n \"packages/cli/package.json\",\n \"packages/cli/scripts/run-all-scenarios.ts\",\n \"packages/cli/src/commands/scenario/docs/README.md\",\n \"packages/cli/src/commands/scenario/docs/analyze-past-trade.md\",\n \"packages/cli/src/commands/scenario/docs/answer-roadmap-questions.md\",\n \"packages/cli/src/commands/scenario/docs/check-evm-balance.md\",\n \"packages/cli/src/commands/scenario/docs/example_scenarios/analyze-past-trade.scenario.yaml\",\n \"packages/cli/src/commands/scenario/docs/example_scenarios/answer-roadmap-questions.scenario.yaml\",\n \"packages/cli/src/commands/scenario/docs/example_scenarios/check-evm-balance.scenario.yaml\",\n \"packages/cli/src/commands/scenario/docs/scenario-runner-spec.md\",\n \"packages/cli/src/commands/scenario/docs/scenarios.md\",\n \"packages/cli/src/commands/scenario/examples/action-tracking-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/e2b-fallback.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/e2b-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/evaluation-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/failing-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/fully-passing.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/invalid-missing-fields.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/llm-judge-failure-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/llm-judge-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/mixed-results.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/mock-e2b-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/mock-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/multi-step.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/simple-mock-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/simple-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/trajectory-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/valid.scenario.yaml\",\n \"packages/cli/src/commands/scenario/index.ts\",\n \"packages/cli/src/index.ts\",\n \"packages/cli/src/scenarios/E2BEnvironmentProvider.ts\",\n \"packages/cli/src/scenarios/EvaluationEngine.ts\",\n \"packages/cli/src/scenarios/LocalEnvironmentProvider.ts\",\n \"packages/cli/src/scenarios/MockEngine.ts\",\n \"packages/cli/src/scenarios/Reporter.ts\",\n \"packages/cli/src/scenarios/env-loader.ts\",\n \"packages/cli/src/scenarios/providers.ts\",\n \"packages/cli/src/scenarios/runtime-factory.ts\",\n \"packages/cli/src/scenarios/schema.ts\",\n \"packages/cli/src/types/elizaos-modules.d.ts\",\n \"packages/cli/src/commands/scenario/examples/advanced-mocking-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/enhanced-mock-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/plugin-parsing-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/simple-advanced-mock-test.scenario.yaml\",\n \"packages/cli/src/scenarios/plugin-parser.ts\",\n \"packages/cli/test-plugin-parsing.ts\",\n \"packages/cli/test-scenario-validation.ts\",\n \".github/workflows/ci.yaml\",\n \".github/workflows/pre-release.yml\",\n \".github/workflows/release.yaml\",\n \".github/workflows/update-news.yml\",\n \".gitignore\",\n \"lerna.json\",\n \"llms.txt\",\n \"packages/api-client/README.md\",\n \"packages/api-client/docs/sessions-api.md\",\n \"packages/api-client/package.json\",\n \"packages/api-client/src/__tests__/base-client.test.ts\",\n \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n \"packages/api-client/src/lib/base-client.ts\",\n \"packages/api-client/src/services/sessions.ts\",\n \"packages/api-client/src/types/sessions.ts\",\n \"packages/app/package.json\",\n \"packages/autodoc/package.json\",\n \"packages/cli/src/commands/create/index.ts\",\n \"packages/cli/src/commands/plugins/utils/env-vars.ts\",\n \"packages/cli/src/commands/scenario/examples/.gitignore\",\n \"packages/cli/src/commands/scenario/examples/analyze-past-trade.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/answer-roadmap-questions.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/check-evm-balance.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/natural-language-test.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/nl-smoke.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/execution-time-test.scenario.yaml\",\n \"packages/cli/.gitignore\",\n \"packages/cli/src/commands/scenario/examples/check-coinbase-balance.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/test-github-issues.scenario.yaml\",\n \"packages/cli/src/commands/scenario/src/E2BEnvironmentProvider.ts\",\n \"packages/cli/src/commands/scenario/src/EvaluationEngine.ts\",\n \"packages/cli/src/commands/scenario/src/LocalEnvironmentProvider.ts\",\n \"packages/cli/src/commands/scenario/src/MockEngine.ts\",\n \"packages/cli/src/commands/scenario/src/Reporter.ts\",\n \"packages/cli/src/commands/scenario/src/env-loader.ts\",\n \"packages/cli/src/commands/scenario/src/plugin-parser.ts\",\n \"packages/cli/src/commands/scenario/src/providers.ts\",\n \"packages/cli/src/commands/scenario/src/runtime-factory.ts\",\n \"packages/cli/src/commands/scenario/src/schema.ts\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/project-starter/src/__tests__/events.test.ts\",\n \"packages/server/package.json\",\n \"packages/cli/src/commands/scenario/docs/matrix-testing.md\",\n \"packages/cli/src/commands/scenario/examples/github-issue-analysis.matrix.yaml\",\n \"packages/cli/src/commands/scenario/src/__tests__/example-validation.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/matrix-command.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/matrix-runner.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/matrix-schema.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/parameter-override.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/validation-demo.test.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-runner.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-schema.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-types.ts\",\n \"packages/cli/src/commands/scenario/src/parameter-override.ts\",\n \"packages/server/src/index.ts\",\n \"packages/cli/src/commands/report/demo-html-report.ts\",\n \"packages/cli/src/commands/report/generate.ts\",\n \"packages/cli/src/commands/report/index.ts\",\n \"packages/cli/src/commands/report/src/__tests__/analysis-engine.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/html-template.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/integration.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/pdf-export.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/pdf-generator.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/template-integration.test.ts\",\n \"packages/cli/src/commands/report/src/analysis-engine.ts\",\n \"packages/cli/src/commands/report/src/assets/report_template.html\",\n \"packages/cli/src/commands/report/src/pdf-generator.ts\",\n \"packages/cli/src/commands/report/src/report-schema.ts\",\n \"packages/cli/src/commands/scenario/examples/debug-llm-judge.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/enhanced-demo.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/llm-judge-with-capabilities.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/simple-test.matrix.yaml\",\n \"packages/cli/src/commands/scenario/examples/trajectory-demo.scenario.yaml\",\n \"packages/cli/src/commands/scenario/src/EnhancedEvaluationEngine.ts\",\n \"packages/cli/src/commands/scenario/src/TrajectoryReconstructor.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/capabilities-evaluation.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/data-aggregator.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/deep-clone.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/e2e/centralized-data.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/enhanced-evaluation.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/evaluation-integration.test.ts\",\n \"packages/cli/src/commands/scenario/examples/test-basic.scenario.yaml\",\n \"packages/cli/src/commands/scenario/src/__tests__/LocalEnvironmentProvider.test.ts\",\n \"CLAUDE.md\"\n ]\n },\n {\n \"title\": \"allow iframes when web ui is enabled in production\",\n \"prNumber\": 5735,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\n\\r\\n- Low: Allows iframes from self if web ui is enabled in production.\\r\\n\\r\\n# Background\\r\\n\\r\\nCurrently in production, any panels exposed by plugins are blocked. This is because plugin panels are exposed using an iframe. with frame-src \",\n \"files\": [\n \"packages/server/src/index.ts\"\n ]\n },\n {\n \"title\": \"fix(cli): handle monorepo version in update command\",\n \"prNumber\": 5733,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR fixes the failing CLI test `update --check works` that was failing in CI due to version handling in monorepo context.\\n\\n## Problem\\n\\nThe test was expecting a semantic version pattern (e.g., `1.2.0`) but was receiving `work\",\n \"files\": [\n \"packages/cli/src/commands/update/utils/version-utils.ts\",\n \"packages/cli/tests/commands/update.test.ts\"\n ]\n },\n {\n \"title\": \"feat: remove automatic merge to develop from release workflow\",\n \"prNumber\": 5732,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR removes the automatic merge from main to develop that was happening at the end of the release workflow.\\n\\n## Changes\\n\\n- Removed the 'Merge main to develop' step from \\n- This step was automatically merging main into develo\",\n \"files\": [\n \".github/workflows/release.yaml\"\n ]\n },\n {\n \"title\": \"feat: replace numbered versions to workspace:*\",\n \"prNumber\": 5731,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR migrates the ElizaOS monorepo to use workspace:* version management for better dependency synchronization and consistency.\\n\\n## Changes\\n\\n- Updated all package.json files to use `workspace:*` versioning instead of hardcode\",\n \"files\": [\n \"bun.lock\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/app/src-tauri/Cargo.lock\",\n \"packages/autodoc/package.json\",\n \"packages/cli/package.json\",\n \"packages/client/package.json\",\n \"packages/config/package.json\",\n \"packages/core/package.json\",\n \"packages/create-eliza/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-quick-starter/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/package.json\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"chore: 1.4.2\",\n \"prNumber\": 5746,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \"packages/cli/package.json\"\n ]\n },\n {\n \"title\": \"chore: 1.4.1\",\n \"prNumber\": 5745,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \"bun.lock\",\n \"llms.txt\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/client/package.json\",\n \"packages/core/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-quick-starter/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/package.json\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"feat: remove obsolete llms.txt and standardize workspace dependencies\",\n \"prNumber\": 5744,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR performs repository cleanup and standardizes dependency management by:\\n- Removing the obsolete `llms.txt` file (2743 lines) \\n- Updating all internal package dependencies to use the workspace protocol\\n- Updating lockfile \",\n \"files\": [\n \"bun.lock\",\n \"llms.txt\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/client/package.json\",\n \"packages/core/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-quick-starter/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/package.json\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"chore 1.3.4\",\n \"prNumber\": 5743,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \".github/workflows/pre-release.yml\",\n \".github/workflows/release.yaml\",\n \"package.json\",\n \"packages/core/src/utils.ts\"\n ]\n },\n {\n \"title\": \"feat: migrate from npx to bunx and improve XML parser\",\n \"prNumber\": 5742,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR contains two main improvements:\\n\\n### 1. Migration from npx to bunx\\n- Updated GitHub workflows (pre-release.yml and release.yaml) to use `bunx` instead of `npx` for lerna commands\\n- Updated package.json clean script to us\",\n \"files\": [\n \".github/workflows/pre-release.yml\",\n \".github/workflows/release.yaml\",\n \"package.json\",\n \"packages/core/src/utils.ts\"\n ]\n },\n {\n \"title\": \"fix(core): replace unsafe XML fallback regex with linear scan to avoi…\",\n \"prNumber\": 5741,\n \"type\": \"bugfix\",\n \"body\": \"\",\n \"files\": [\n \".github/workflows/ci.yaml\",\n \".github/workflows/pre-release.yml\",\n \".github/workflows/update-news.yml\",\n \"packages/api-client/src/__tests__/base-client.test.ts\",\n \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n \"packages/api-client/src/lib/base-client.ts\",\n \"packages/cli/src/commands/test/actions/run-all-tests.ts\",\n \"packages/client/package.json\",\n \"packages/core/src/__tests__/utils.test.ts\",\n \"packages/core/src/utils.ts\"\n ]\n },\n {\n \"title\": \"feat: code formatting and linting improvements\",\n \"prNumber\": 5740,\n \"type\": \"feature\",\n \"body\": \"## 📝 Description\\n\\nThis PR implements comprehensive code formatting and linting improvements across the entire ElizaOS codebase to enhance code quality, consistency, and maintainability.\\n\\n## 🔧 Changes Made\\n\\n### Code Formatting & Style\\n- Ap\",\n \"files\": [\n \"bun.lock\",\n \"packages/api-client/README.md\",\n \"packages/api-client/docs/sessions-api.md\",\n \"packages/api-client/package.json\",\n \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n \"packages/api-client/src/services/sessions.ts\",\n \"packages/api-client/src/types/sessions.ts\",\n \"packages/app/package.json\",\n \"packages/autodoc/package.json\",\n \"packages/cli/package.json\",\n \"packages/cli/src/commands/create/index.ts\",\n \"packages/cli/src/commands/plugins/utils/env-vars.ts\",\n \"packages/cli/src/commands/start/actions/agent-start.ts\",\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/src/commands/update/actions/cli-update.ts\",\n \"packages/cli/src/project.ts\",\n \"packages/cli/src/utils/dependency-manager.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/src/utils/registry/index.ts\",\n \"packages/cli/src/utils/upgrade/migration-guide-loader.ts\",\n \"packages/cli/src/utils/upgrade/simple-migration-agent.ts\",\n \"packages/cli/src/utils/user-environment.ts\",\n \"packages/client/package.json\",\n \"packages/config/package.json\",\n \"packages/core/package.json\",\n \"packages/core/src/utils.ts\",\n \"packages/create-eliza/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-bootstrap/src/providers/capabilities.ts\",\n \"packages/plugin-bootstrap/src/providers/choice.ts\",\n \"packages/plugin-bootstrap/src/providers/facts.ts\",\n \"packages/plugin-bootstrap/src/providers/recentMessages.ts\",\n \"packages/plugin-bootstrap/src/providers/world.ts\",\n \"packages/plugin-bootstrap/src/services/task.ts\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-dummy-services/src/tokenData/service.ts\",\n \"packages/plugin-quick-starter/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-starter/package.json\",\n \"packages/project-starter/package.json\",\n \"packages/project-starter/src/__tests__/plugin.test.ts\",\n \"packages/project-starter/src/__tests__/provider.test.ts\",\n \"packages/project-tee-starter/package.json\",\n \"packages/server/package.json\",\n \"packages/server/src/index.ts\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"chore: 1.3.3\",\n \"prNumber\": 5739,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \".cursorrules\",\n \".github/workflows/ci.yaml\",\n \".github/workflows/pre-release.yml\",\n \".github/workflows/release.yaml\",\n \".github/workflows/update-news.yml\",\n \"CLAUDE.md\",\n \"bun.lock\",\n \"lerna.json\",\n \"packages/api-client/README.md\",\n \"packages/api-client/docs/sessions-api.md\",\n \"packages/api-client/package.json\",\n \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n \"packages/api-client/src/client.ts\",\n \"packages/api-client/src/index.ts\",\n \"packages/api-client/src/lib/base-client.ts\",\n \"packages/api-client/src/services/sessions.ts\",\n \"packages/api-client/src/types/sessions.ts\",\n \"packages/app/package.json\",\n \"packages/app/src-tauri/Cargo.lock\",\n \"packages/autodoc/package.json\",\n \"packages/cli/README.md\",\n \"packages/cli/package.json\",\n \"packages/cli/src/commands/create/index.ts\",\n \"packages/cli/src/commands/plugins/utils/env-vars.ts\",\n \"packages/cli/src/commands/start/actions/agent-start.ts\",\n \"packages/cli/src/commands/start/actions/server-start.ts\",\n \"packages/cli/src/commands/start/index.ts\",\n \"packages/cli/src/commands/start/utils/dependency-resolver.ts\",\n \"packages/cli/src/commands/test/actions/component-tests.ts\",\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/src/commands/test/actions/run-all-tests.ts\",\n \"packages/cli/src/commands/test/utils/plugin-utils.ts\",\n \"packages/cli/src/commands/update/actions/cli-update.ts\",\n \"packages/cli/src/commands/update/utils/version-utils.ts\",\n \"packages/cli/src/index.ts\",\n \"packages/cli/src/project.ts\",\n \"packages/cli/src/utils/auto-install-bun.ts\",\n \"packages/cli/src/utils/bun-exec.ts\",\n \"packages/cli/src/utils/dependency-manager.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/src/utils/handle-error.ts\",\n \"packages/cli/src/utils/install-plugin.ts\",\n \"packages/cli/src/utils/local-cli-delegation.ts\",\n \"packages/cli/src/utils/publisher.ts\",\n \"packages/cli/src/utils/registry/index.ts\",\n \"packages/cli/src/utils/test-runner.ts\",\n \"packages/cli/src/utils/testing/tsc-validator.ts\",\n \"packages/cli/src/utils/upgrade/migration-guide-loader.ts\",\n \"packages/cli/src/utils/upgrade/simple-migration-agent.ts\",\n \"packages/cli/src/utils/user-environment.ts\"\n ]\n },\n {\n \"title\": \"fix missing pino logger refactors\",\n \"prNumber\": 5737,\n \"type\": \"bugfix\",\n \"body\": \"### Summary\\r\\n- Convert logger calls across the repo to object-first structured logging to align with pino typings and fix TS/DTS errors.\\r\\n- No functional behavior changes; improves type-safety and log structure.\\r\\n\\r\\n### Why\\r\\n- Recent stricte\",\n \"files\": [\n \"bun.lock\",\n \"packages/cli/src/commands/create/index.ts\",\n \"packages/cli/src/commands/plugins/utils/env-vars.ts\",\n \"packages/cli/src/commands/start/actions/agent-start.ts\",\n \"packages/cli/src/commands/start/actions/server-start.ts\",\n \"packages/cli/src/commands/start/index.ts\",\n \"packages/cli/src/commands/start/utils/dependency-resolver.ts\",\n \"packages/cli/src/commands/test/actions/component-tests.ts\",\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/src/commands/test/utils/plugin-utils.ts\",\n \"packages/cli/src/commands/update/actions/cli-update.ts\",\n \"packages/cli/src/commands/update/utils/version-utils.ts\",\n \"packages/cli/src/index.ts\",\n \"packages/cli/src/project.ts\",\n \"packages/cli/src/utils/auto-install-bun.ts\",\n \"packages/cli/src/utils/bun-exec.ts\",\n \"packages/cli/src/utils/dependency-manager.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/src/utils/handle-error.ts\",\n \"packages/cli/src/utils/install-plugin.ts\",\n \"packages/cli/src/utils/local-cli-delegation.ts\",\n \"packages/cli/src/utils/publisher.ts\",\n \"packages/cli/src/utils/registry/index.ts\",\n \"packages/cli/src/utils/testing/tsc-validator.ts\",\n \"packages/cli/src/utils/upgrade/migration-guide-loader.ts\",\n \"packages/cli/src/utils/upgrade/simple-migration-agent.ts\",\n \"packages/cli/src/utils/user-environment.ts\",\n \"packages/core/src/utils.ts\",\n \"packages/plugin-bootstrap/src/__tests__/evaluators.test.ts\",\n \"packages/plugin-bootstrap/src/actions/choice.ts\",\n \"packages/plugin-bootstrap/src/actions/followRoom.ts\",\n \"packages/plugin-bootstrap/src/actions/muteRoom.ts\",\n \"packages/plugin-bootstrap/src/actions/roles.ts\",\n \"packages/plugin-bootstrap/src/actions/settings.ts\",\n \"packages/plugin-bootstrap/src/actions/unmuteRoom.ts\",\n \"packages/plugin-bootstrap/src/evaluators/reflection.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-bootstrap/src/providers/actionState.ts\",\n \"packages/plugin-bootstrap/src/providers/capabilities.ts\",\n \"packages/plugin-bootstrap/src/providers/choice.ts\",\n \"packages/plugin-bootstrap/src/providers/facts.ts\",\n \"packages/plugin-bootstrap/src/providers/recentMessages.ts\",\n \"packages/plugin-bootstrap/src/providers/world.ts\",\n \"packages/plugin-bootstrap/src/services/task.ts\",\n \"packages/plugin-dummy-services/src/tokenData/service.ts\",\n \"packages/plugin-quick-starter/src/plugin.ts\",\n \"packages/plugin-starter/src/plugin.ts\",\n \"packages/project-starter/src/__tests__/actions.test.ts\",\n \"packages/project-starter/src/__tests__/integration.test.ts\",\n \"packages/project-starter/src/__tests__/models.test.ts\"\n ]\n },\n {\n \"title\": \"fix: (project-starter) replace mock.module with spyOn for consistent logger testing\",\n \"prNumber\": 5748,\n \"type\": \"bugfix\",\n \"body\": \"## Description\\r\\n\\r\\nThis PR fixes failing component tests in the project-starter template by replacing `mock.module` with `spyOn` for logger mocking.\\r\\n\\r\\n## Problem\\r\\n\\r\\nThe project-starter template had 3 test files using `mock.module('@elizaos/\",\n \"files\": [\n \"packages/project-starter/src/__tests__/config.test.ts\",\n \"packages/project-starter/src/__tests__/error-handling.test.ts\",\n \"packages/project-starter/src/__tests__/events.test.ts\"\n ]\n },\n {\n \"title\": \"feat: Add character type system with JesseXBT character and improve API consistency\",\n \"prNumber\": 5756,\n \"type\": \"feature\",\n \"body\": \"# Character Type System and Jesse Pollak Character Implementation\\n\\nThis PR introduces a comprehensive character type system using Zod validation and implements a new Jesse Pollak (jesseXBT) character focused on Base ecosystem support.\\n\\n## K\",\n \"files\": [\n \"characters/jessexbt.json\",\n \"lib/core/character.ts\",\n \"lib/core/index.ts\",\n \"src/server.ts\"\n ]\n },\n {\n \"title\": \"feat: Add OpenAI-compliant tool calls visibility to chat completions\",\n \"prNumber\": 5755,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR adds support for viewing intermediate tool calls and results in the chat completions API while maintaining full OpenAI API compliance.\\n\\n## Changes\\n\\n- **OpenAI API Compliance**: Default responses remain fully compliant wi\",\n \"files\": [\n \"src/server.ts\"\n ]\n },\n {\n \"title\": \"feat: add Hono server, refactor ElizaOS agent registry\",\n \"prNumber\": 5753,\n \"type\": \"feature\",\n \"body\": \"This pull request introduces significant improvements to the agent management system and adds a new HTTP server for interacting with agents via an OpenAI-compatible API. The changes refactor how agents are stored and accessed, update relate\",\n \"files\": [\n \"bun.lock\",\n \"lib/core/elizaos.ts\",\n \"package.json\",\n \"src/index.ts\",\n \"src/server.ts\"\n ]\n },\n {\n \"title\": \"feat: add EVM plugin and tools\",\n \"prNumber\": 5752,\n \"type\": \"feature\",\n \"body\": \"This pull request introduces a new EVM (Ethereum Virtual Machine) plugin, integrating wallet and blockchain tooling into the application. It adds a modular service for managing EVM chains and clients, several tools for interacting with wall\",\n \"files\": [\n \".env.example\",\n \"plugins/plugin-evm/bun.lock\",\n \"plugins/plugin-evm/index.ts\",\n \"plugins/plugin-evm/package.json\",\n \"plugins/plugin-evm/services/index.ts\",\n \"plugins/plugin-evm/tools/getEVMChains.ts\",\n \"plugins/plugin-evm/tools/getTokenBalance.ts\",\n \"plugins/plugin-evm/tools/getWalletAddress.ts\",\n \"plugins/plugin-evm/tools/getWalletBalance.ts\",\n \"plugins/plugin-evm/tsconfig.json\",\n \"src/index.ts\"\n ]\n },\n {\n \"title\": \"chore(imports): use @/ alias and barrels; add Cursor rule\",\n \"prNumber\": 5751,\n \"type\": \"other\",\n \"body\": \"- Converted relative imports to '@/'\\n- Prefer barrels (e.g., '@/lib/core', '@/lib/db/schema')\\n- Added Cursor rule: .cursor/rules/use-atslash-alias-imports.mdc\\n- Verified build with Bun\",\n \"files\": [\n \".cursor/rules/use-atslash-alias-imports.mdc\",\n \"lib/core/elizaos.ts\",\n \"lib/db/index.ts\"\n ]\n },\n {\n \"title\": \"revert: Use relative paths for imports\",\n \"prNumber\": 5750,\n \"type\": \"other\",\n \"body\": \"## Description\\nThis PR ensures consistent use of relative paths for imports throughout the project.\\n\\n## Changes\\n- ✅ Reverted import in `src/index.ts` to use relative path `../lib/core`\\n- ✅ Removed path aliases configuration from `tsconfig.j\",\n \"files\": [\n \"src/index.ts\",\n \"tsconfig.json\"\n ]\n },\n {\n \"title\": \"fix: resolve `elizaos publish` command issues with --test and --npm flags\",\n \"prNumber\": 5763,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes two minor issues with the `elizaos publish` command:\\r\\n\\r\\n**1. Fix `elizaos publish --test` failing out of the box**\\r\\n\\r\\nWhen running `elizaos publish --test` OOTB, we get an error:\\r\\n```\\r\\n[2025-08-13 06:54:20] ERROR: Failed to up\",\n \"files\": [\n \"packages/cli/src/commands/publish/index.ts\",\n \"packages/cli/src/commands/publish/types.ts\",\n \"packages/cli/src/commands/publish/utils/metadata.ts\",\n \"packages/cli/src/utils/github.ts\"\n ]\n },\n {\n \"title\": \"chore(ci): adjust release workflow and package metadata\",\n \"prNumber\": 5775,\n \"type\": \"other\",\n \"body\": \"- Remove 'merge main to develop' step from to avoid automatic branch merges in release job.\\n- Minor metadata sync in various files and .\\n\\nBase: develop\\nHead: chore/release-workflow-tweaks\",\n \"files\": [\n \".github/workflows/release.yaml\",\n \"bun.lock\",\n \"lerna.json\",\n \"packages/api-client/package.json\",\n \"packages/cli/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/project-starter/src/__tests__/events.test.ts\",\n \"packages/server/package.json\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"fix: correct comma placement when adding entries to registry index.json\",\n \"prNumber\": 5774,\n \"type\": \"bugfix\",\n \"body\": \"## Description\\r\\n\\r\\n### Problem\\r\\nThe `elizaos publish` command incorrectly handled commas when adding new plugin entries to the registry's `index.json` file:\\r\\n- Did not add a comma to the previously last entry\\r\\n- Incorrectly added a comma to \",\n \"files\": [\n \"packages/cli/src/utils/publisher.ts\",\n \"packages/cli/tests/unit/utils/publisher.test.ts\"\n ]\n },\n {\n \"title\": \"fix: fix: phala CLI argument handling and tee starter docker build\",\n \"prNumber\": 5773,\n \"type\": \"bugfix\",\n \"body\": \"## Description\\r\\n\\r\\nThis PR fixes two minor issues preventing the tee command from working as intended:\\r\\n\\r\\n### 1. Phala CLI Wrapper Argument Handling\\r\\n\\r\\nThe ElizaOS wrapper for the Phala CLI was not correctly capturing arguments, causing comm\",\n \"files\": [\n \"packages/cli/src/commands/tee/phala-wrapper.ts\",\n \"packages/project-tee-starter/src/index.ts\",\n \"packages/cli/src/commands/tee/index.ts\",\n \"packages/cli/tests/commands/create.test.ts\",\n \"packages/cli/tests/commands/tee.test.ts\"\n ]\n },\n {\n \"title\": \"fix: bun run clean, bats-assert bad dep and polyfills\",\n \"prNumber\": 5776,\n \"type\": \"bugfix\",\n \"body\": \"This pull request updates dependencies in the project to improve compatibility and maintainability. The most important changes are grouped below by theme.\\r\\n\\r\\nDependency updates:\\r\\n\\r\\n* Upgraded the `vite-plugin-node-polyfills` package from ve\",\n \"files\": [\n \"bun.lock\",\n \"packages/cli/package.json\",\n \"packages/client/package.json\"\n ]\n },\n {\n \"title\": \"feat(bootstrap): async embedding generation via queue service\",\n \"prNumber\": 5793,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nPerformance improvement for message processing latency - embeddings were blocking runtime for 500ms+ per message\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low risk** - The change is backward compatible and includes fallback behavior. Main risks:\\r\\n- M\",\n \"files\": [\n \"packages/core/src/__tests__/runtime-embedding.test.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/types/events.ts\",\n \"packages/core/src/types/runtime.ts\",\n \"packages/plugin-bootstrap/src/__tests__/embedding-service.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/evaluators.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/test-utils.ts\",\n \"packages/plugin-bootstrap/src/evaluators/reflection.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-bootstrap/src/services/embedding.ts\",\n \"packages/plugin-quick-starter/src/__tests__/test-utils.ts\",\n \"packages/plugin-starter/src/__tests__/test-utils.ts\",\n \"packages/server/src/__tests__/test-utils/mocks.ts\",\n \"packages/test-utils/src/mocks/runtime.ts\",\n \"packages/plugin-bootstrap/src/__tests__/embedding-queue-management.test.ts\"\n ]\n },\n {\n \"title\": \"fix: resolve test failures and enhance XML parsing reliability in CI environment\",\n \"prNumber\": 5792,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\nMultiple GitHub Actions test failures were occurring across different packages, plus a critical plugin configuration bug:\\n\\n### Original Issues (https://github.com/elizaOS/eliza/actions/runs/17020769599/job/48249463787)\\n- ❌ **10 e\",\n \"files\": [\n \"bun.lock\",\n \"packages/plugin-bootstrap/src/__tests__/attachments.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/evaluators.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/services.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/test-utils.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/project-tee-starter/src/__tests__/config.test.ts\",\n \"packages/project-tee-starter/src/plugin.ts\"\n ]\n },\n {\n \"title\": \"fix: resolve entity creation SQL parameter mismatch\",\n \"prNumber\": 5791,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR fixes a critical database error that was occurring during entity creation:\\n\\n```\\n[ERROR] Error creating entity: Failed query: insert into \\\"entities\\\" values ($1, $2, default, default, default)\\nparams: [only 2 parameters pr\",\n \"files\": [\n \"packages/core/src/types/environment.ts\",\n \"packages/plugin-sql/src/base.ts\"\n ]\n },\n {\n \"title\": \"feat: Cross-Environment Logger Support.\",\n \"prNumber\": 5797,\n \"type\": \"feature\",\n \"body\": \"## Logger Module Refactoring: Cross-Platform Support & Enhanced Architecture\\r\\n\\r\\n### Overview\\r\\nThis PR introduces a comprehensive refactoring of the logger module to support both browser and Node.js environments while maintaining backward co\",\n \"files\": [\n \"packages/core/src/__tests__/logger-browser-node.test.ts\",\n \"packages/core/src/logger.ts\"\n ]\n },\n {\n \"title\": \"fix: improve TypeScript types and error logging in publisher\",\n \"prNumber\": 5796,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR improves TypeScript type safety and error logging in the publisher module by:\\n\\n### Changes Made\\n\\n1. **Type Safety Improvements**:\\n - Replaced all types with proper TypeScript types in \\n - Added interface for better\",\n \"files\": [\n \"packages/cli/src/utils/publisher.ts\",\n \"packages/cli/tests/unit/utils/publisher.test.ts\"\n ]\n },\n {\n \"title\": \"fix: code formatting improvements and dependency updates\",\n \"prNumber\": 5795,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR contains code formatting improvements and dependency updates:\\n\\n### Changes Made:\\n- **Test File Cleanup**: Removed unnecessary empty lines in `attachments.test.ts`\\n- **Logger Formatting**: Fixed line wrapping for `logger.\",\n \"files\": [\n \"bun.lock\",\n \"packages/plugin-bootstrap/src/__tests__/attachments.test.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/project-tee-starter/src/plugin.ts\"\n ]\n },\n {\n \"title\": \"chore: 1.4.3\",\n \"prNumber\": 5794,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \".github/workflows/release.yaml\",\n \"bun.lock\",\n \"lerna.json\",\n \"packages/api-client/package.json\",\n \"packages/cli/package.json\",\n \"packages/cli/src/commands/publish/index.ts\",\n \"packages/cli/src/commands/publish/types.ts\",\n \"packages/cli/src/commands/publish/utils/metadata.ts\",\n \"packages/cli/src/utils/github.ts\",\n \"packages/cli/src/utils/publisher.ts\",\n \"packages/cli/tests/unit/utils/publisher.test.ts\",\n \"packages/client/package.json\",\n \"packages/core/src/types/environment.ts\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-bootstrap/src/__tests__/attachments.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/evaluators.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/services.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/test-utils.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-sql/src/base.ts\",\n \"packages/project-starter/src/__tests__/config.test.ts\",\n \"packages/project-starter/src/__tests__/error-handling.test.ts\",\n \"packages/project-starter/src/__tests__/events.test.ts\",\n \"packages/project-tee-starter/src/__tests__/config.test.ts\",\n \"packages/project-tee-starter/src/plugin.ts\",\n \"packages/server/package.json\",\n \"packages/server/src/index.ts\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"feat: Sessions API ++\",\n \"prNumber\": 5799,\n \"type\": \"feature\",\n \"body\": \"## Enhanced Session Management with Advanced Timeout Configuration and Lifecycle Control\\r\\n\\r\\n### Overview\\r\\nThis PR significantly enhances the sessions API with comprehensive timeout management, auto-renewal capabilities, and robust error han\",\n \"files\": [\n \"packages/server/src/api/messaging/__tests__/sessions.test.ts\",\n \"packages/server/src/api/messaging/channels.ts\",\n \"packages/server/src/api/messaging/errors/SessionErrors.ts\",\n \"packages/server/src/api/messaging/sessions.ts\",\n \"packages/server/src/index.ts\",\n \"packages/server/src/types/sessions.ts\"\n ]\n },\n {\n \"title\": \"feat: getServiceLoadPromise\",\n \"prNumber\": 5801,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- add getServiceLoadPromise interface to runtime\\r\\n- fix component queries in plugin-sql (was too easy for dates to get invalid, this is a more flexible set up, allowing the inten\",\n \"files\": [\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/settings.ts\",\n \"packages/core/src/types/runtime.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-sql/src/base.ts\",\n \"packages/test-utils/src/mocks/runtime.ts\"\n ]\n },\n {\n \"title\": \"fix: metadata in sessions\",\n \"prNumber\": 5805,\n \"type\": \"bugfix\",\n \"body\": \"## Session Metadata Propagation for Plugin Actions\\n\\n### Overview\\nThis PR implements session metadata propagation throughout the ElizaOS message processing pipeline, enabling plugins and actions to access custom session metadata (like `ethAd\",\n \"files\": [\n \"packages/server/src/__tests__/message-bus.test.ts\",\n \"packages/server/src/api/messaging/__tests__/sessions.test.ts\",\n \"packages/server/src/api/messaging/sessions.ts\",\n \"packages/server/src/services/message.ts\"\n ]\n },\n {\n \"title\": \"feat: Convert packages/docs to git submodule from elizaos/docs\",\n \"prNumber\": 5803,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR converts the `packages/docs` directory from tracked files to a git submodule pointing to the external documentation repository at https://github.com/elizaos/docs.\\n\\n## Changes\\n\\n- Removed 171 documentation files that were \",\n \"files\": [\n \".gitmodules\",\n \"packages/docs\",\n \"packages/docs/.github/workflows/check-dead-links.yml\",\n \"packages/docs/.github/workflows/check-documentation-quality.yml\",\n \"packages/docs/.github/workflows/claude-code-review.yml\",\n \"packages/docs/.github/workflows/claude.yml\",\n \"packages/docs/.gitignore\",\n \"packages/docs/CLAUDE.md\",\n \"packages/docs/README.md\",\n \"packages/docs/api-reference/agents/create-a-new-agent.mdx\",\n \"packages/docs/api-reference/agents/create-a-world-for-an-agent.mdx\",\n \"packages/docs/api-reference/agents/delete-an-agent.mdx\",\n \"packages/docs/api-reference/agents/get-agent-details.mdx\",\n \"packages/docs/api-reference/agents/get-agent-panels.mdx\",\n \"packages/docs/api-reference/agents/get-all-worlds.mdx\",\n \"packages/docs/api-reference/agents/list-all-agents.mdx\",\n \"packages/docs/api-reference/agents/start-an-agent.mdx\",\n \"packages/docs/api-reference/agents/stop-an-agent.mdx\",\n \"packages/docs/api-reference/agents/update-a-world.mdx\",\n \"packages/docs/api-reference/agents/update-agent.mdx\",\n \"packages/docs/api-reference/audio/convert-conversation-to-speech.mdx\",\n \"packages/docs/api-reference/audio/generate-speech-from-text.mdx\",\n \"packages/docs/api-reference/audio/process-audio-message.mdx\",\n \"packages/docs/api-reference/audio/synthesize-speech-from-text.mdx\",\n \"packages/docs/api-reference/audio/transcribe-audio.mdx\",\n \"packages/docs/api-reference/media/upload-media-for-agent.mdx\",\n \"packages/docs/api-reference/media/upload-media-to-channel.mdx\",\n \"packages/docs/api-reference/memory/create-a-room.mdx\",\n \"packages/docs/api-reference/memory/delete-all-agent-memories.mdx\",\n \"packages/docs/api-reference/memory/delete-all-memories-for-a-room.mdx\",\n \"packages/docs/api-reference/memory/get-agent-memories.mdx\",\n \"packages/docs/api-reference/memory/get-room-memories.mdx\",\n \"packages/docs/api-reference/memory/update-a-memory.mdx\",\n \"packages/docs/api-reference/messaging/add-agent-to-channel.mdx\",\n \"packages/docs/api-reference/messaging/add-agent-to-server.mdx\",\n \"packages/docs/api-reference/messaging/create-central-channel.mdx\",\n \"packages/docs/api-reference/messaging/create-channel.mdx\",\n \"packages/docs/api-reference/messaging/create-group-channel.mdx\",\n \"packages/docs/api-reference/messaging/create-server.mdx\",\n \"packages/docs/api-reference/messaging/delete-all-channel-messages-by-user.mdx\",\n \"packages/docs/api-reference/messaging/delete-all-channel-messages.mdx\",\n \"packages/docs/api-reference/messaging/delete-channel-message.mdx\",\n \"packages/docs/api-reference/messaging/delete-channel.mdx\",\n \"packages/docs/api-reference/messaging/get-central-server-channels.mdx\",\n \"packages/docs/api-reference/messaging/get-central-servers.mdx\",\n \"packages/docs/api-reference/messaging/get-channel-details.mdx\",\n \"packages/docs/api-reference/messaging/get-channel-info.mdx\",\n \"packages/docs/api-reference/messaging/get-channel-messages.mdx\",\n \"packages/docs/api-reference/messaging/get-channel-participants.mdx\",\n \"packages/docs/api-reference/messaging/get-or-create-dm-channel.mdx\"\n ]\n },\n {\n \"title\": \"fix: plugin-sql test\",\n \"prNumber\": 5802,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nMedium, not sure this is what we want\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- make plugin-sql tests pass for me from monorepo\\r\\n- mainly createdAt have to be a date object for w/e reason now for pglite (timestamps no long\",\n \"files\": [\n \"packages/core/src/runtime.ts\",\n \"packages/plugin-sql/src/__tests__/e2e/postgres.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/base-adapter-methods.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/base-comprehensive.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/component.test.ts\",\n \"packages/plugin-sql/src/__tests__/unit/utils.test.ts\",\n \"packages/plugin-sql/src/base.ts\",\n \"packages/plugin-sql/src/utils.ts\"\n ]\n },\n {\n \"title\": \"feat: bun build, remove tsup\",\n \"prNumber\": 5807,\n \"type\": \"feature\",\n \"body\": \"This pull request introduces a new standardized Bun-based build system for ElizaOS packages, replacing the previous use of `tsup` and related tooling. It adds reusable build utilities, custom build scripts for `@elizaos/api-client` and `@el\",\n \"files\": [\n \".gitignore\",\n \"CLAUDE.md\",\n \"build-utils.ts\",\n \"bun.lock\",\n \"package.json\",\n \"packages/api-client/build.ts\",\n \"packages/api-client/package.json\",\n \"packages/api-client/src/services/messaging.ts\",\n \"packages/api-client/tsconfig.build.json\",\n \"packages/api-client/tsup.config.ts\",\n \"packages/cli/build.ts\",\n \"packages/cli/package.json\",\n \"packages/cli/src/commands/dev/utils/server-manager.ts\",\n \"packages/cli/src/commands/plugins/actions/upgrade.ts\",\n \"packages/cli/src/commands/plugins/utils/env-vars.ts\",\n \"packages/cli/src/commands/report/demo-html-report.ts\",\n \"packages/cli/src/commands/report/generate.ts\",\n \"packages/cli/src/commands/report/index.ts\",\n \"packages/cli/src/commands/report/src/__tests__/analysis-engine.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/html-template.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/integration.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/pdf-export.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/pdf-generator.test.ts\",\n \"packages/cli/src/commands/report/src/__tests__/template-integration.test.ts\",\n \"packages/cli/src/commands/report/src/analysis-engine.ts\",\n \"packages/cli/src/commands/report/src/assets/report_template.html\",\n \"packages/cli/src/commands/report/src/pdf-generator.ts\",\n \"packages/cli/src/commands/report/src/report-schema.ts\",\n \"packages/cli/src/commands/scenario/docs/README.md\",\n \"packages/cli/src/commands/scenario/docs/matrix-testing.md\",\n \"packages/cli/src/commands/scenario/docs/scenarios.md\",\n \"packages/cli/src/commands/scenario/examples/debug-llm-judge.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/enhanced-demo.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/llm-judge-with-capabilities.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/simple-test.matrix.yaml\",\n \"packages/cli/src/commands/scenario/examples/test-github-issues.scenario.yaml\",\n \"packages/cli/src/commands/scenario/examples/trajectory-demo.scenario.yaml\",\n \"packages/cli/src/commands/scenario/index.ts\",\n \"packages/cli/src/commands/scenario/src/E2BEnvironmentProvider.ts\",\n \"packages/cli/src/commands/scenario/src/EnhancedEvaluationEngine.ts\",\n \"packages/cli/src/commands/scenario/src/EvaluationEngine.ts\",\n \"packages/cli/src/commands/scenario/src/LocalEnvironmentProvider.ts\",\n \"packages/cli/src/commands/scenario/src/MockEngine.ts\",\n \"packages/cli/src/commands/scenario/src/TrajectoryReconstructor.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/LocalEnvironmentProvider.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/capabilities-evaluation.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/data-aggregator.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/e2e/centralized-data.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/enhanced-evaluation.test.ts\",\n \"packages/cli/src/commands/scenario/src/__tests__/evaluation-integration.test.ts\",\n \"packages/api-client/src/types/messaging.ts\",\n \"packages/api-client/src/types/sessions.ts\",\n \"packages/cli/src/commands/scenario/src/data-aggregator.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-orchestrator.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-runner.ts\",\n \"packages/cli/src/commands/scenario/src/parameter-override.ts\",\n \"packages/cli/src/commands/scenario/src/plugin-parser.ts\",\n \"packages/cli/src/commands/scenario/src/process-manager.ts\",\n \"packages/cli/src/commands/scenario/src/progress-tracker.ts\",\n \"packages/cli/src/commands/scenario/src/resource-monitor.ts\",\n \"packages/cli/src/commands/scenario/src/run-isolation.ts\",\n \"packages/cli/src/commands/scenario/src/runtime-factory.ts\",\n \"packages/cli/src/commands/start/actions/server-start.ts\",\n \"packages/cli/src/commands/start/index.ts\",\n \"packages/cli/src/project.ts\",\n \"packages/cli/src/scripts/copy-templates.ts\",\n \"packages/cli/src/services/env-file.service.ts\",\n \"packages/cli/src/utils/build-project.ts\",\n \"packages/cli/src/utils/bun-exec.ts\",\n \"packages/cli/src/utils/dependency-manager.ts\",\n \"packages/cli/src/utils/env-prompt.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/src/utils/github.ts\",\n \"packages/cli/src/utils/load-plugin.ts\",\n \"packages/cli/src/utils/local-cli-delegation.ts\",\n \"packages/cli/src/utils/plugin-creator.ts\",\n \"packages/cli/src/utils/registry/index.ts\",\n \"packages/cli/src/utils/spinner-utils.ts\",\n \"packages/cli/src/utils/test-runner.ts\"\n ]\n },\n {\n \"title\": \"improve summary\",\n \"prNumber\": 5818,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \"packages/plugin-action-bench/src/actions/retail/exchangeDeliveredOrderItems.ts\"\n ]\n },\n {\n \"title\": \"fix: Remove duplicate actionNames block from message handler template\",\n \"prNumber\": 5817,\n \"type\": \"bugfix\",\n \"body\": \"The actionNames block was appearing twice in the messageHandlerTemplate: once correctly inside the section and once redundantly after it. This PR removes the duplicated block after the tag to streamline the template\",\n \"files\": [\n \"packages/core/src/__tests__/prompts.test.ts\",\n \"packages/core/src/prompts.ts\"\n ]\n },\n {\n \"title\": \"Refine prompt logic to enforce user ID requirement for actions needing authentication\",\n \"prNumber\": 5816,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \"packages/plugin-bootstrap/src/index.ts\"\n ]\n },\n {\n \"title\": \"Revert processActions change: use cacheState to retrieve action result instead; minor auth prompt fix\",\n \"prNumber\": 5815,\n \"type\": \"bugfix\",\n \"body\": \"\",\n \"files\": [\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/types/runtime.ts\",\n \"packages/plugin-bootstrap/src/index.ts\"\n ]\n },\n {\n \"title\": \"Fix typo in runtime.ts comment: \\\"initalized\\\" → \\\"initialized\\\"\",\n \"prNumber\": 5812,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\nFixes a typo in the comment on line 1615 of `packages/core/src/runtime.ts`.\\r\\n\\r\\n### Changes\\r\\n- **Before:** `// not initalized or registered yet, registerPlugin is already smart enough to`\\r\\n- **After:** `// not initialized or registered y\",\n \"files\": [\n \"packages/core/src/runtime.ts\"\n ]\n },\n {\n \"title\": \"multi step\",\n \"prNumber\": 5825,\n \"type\": \"other\",\n \"body\": \"\",\n \"files\": [\n \"bun.lock\",\n \"packages/core/src/prompts.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-bootstrap/src/providers/actionState.ts\",\n \"packages/plugin-bootstrap/src/providers/providers.ts\",\n \"packages/plugin-bootstrap/src/providers/recentMessages.ts\",\n \"packages/project-starter/package.json\",\n \"packages/project-starter/src/character.ts\",\n \"packages/plugin-bootstrap/src/__tests__/multi-step.test.ts\",\n \"packages/plugin-bootstrap/src/__tests__/test-utils.ts\"\n ]\n },\n {\n \"title\": \"fix(plugin-bootstrap): return ActionResult in GENERATE_IMAGE handler\",\n \"prNumber\": 5823,\n \"type\": \"bugfix\",\n \"body\": \"This PR updates `GENERATE_IMAGE` in `@elizaos/plugin-bootstrap` to return an `ActionResult` per core `Action` contract.\\\\n\\\\n- Changes limited to `packages/plugin-bootstrap/src/actions/imageGeneration.ts`\\\\n- Excludes edits to `standalone.ts` \",\n \"files\": [\n \"packages/plugin-bootstrap/src/__tests__/actions.test.ts\",\n \"packages/plugin-bootstrap/src/actions/imageGeneration.ts\"\n ]\n },\n {\n \"title\": \"expose multi-step templates via character config and enable env-based strategy toggle\",\n \"prNumber\": 5822,\n \"type\": \"other\",\n \"body\": \"This PR introduces the following changes:\\r\\n\\r\\nMoves core templates (multiStepDecisionTemplate and multiStepSummaryTemplate) into the core layer to improve modularity.\\r\\n\\r\\nAdds character-level overrides: Characters can now define their own mul\",\n \"files\": [\n \"packages/cli/src/characters/eliza.ts\",\n \"packages/core/src/prompts.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-bootstrap/src/providers/recentMessages.ts\"\n ]\n },\n {\n \"title\": \"fix: CI test failures in core and cypress tests\",\n \"prNumber\": 5835,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR fixes failing CI tests in the core packages and cypress component tests identified in the develop branch CI runs.\\n\\n### Changes Made\\n\\n#### project-tee-starter tests\\n- Updated all references from `tsup.config.ts` to `build\",\n \"files\": [\n \".github/workflows/client-cypress-tests.yml\",\n \"bun.lock\",\n \"packages/client/cypress.config.cjs\",\n \"packages/client/cypress/e2e/01-home-page.cy.ts\",\n \"packages/client/cypress/e2e/02-chat-functionality.cy.ts\",\n \"packages/client/cypress/e2e/03-spa-routing.cy.ts\",\n \"packages/client/package.json\",\n \"packages/core/src/__tests__/settings.test.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/settings.ts\",\n \"packages/plugin-bootstrap/src/__tests__/providers.test.ts\",\n \"packages/plugin-dummy-services/src/lp/service.ts\",\n \"packages/plugin-dummy-services/src/tokenData/service.ts\",\n \"packages/plugin-dummy-services/src/wallet/__tests__/service.test.ts\",\n \"packages/plugin-dummy-services/src/wallet/service.ts\",\n \"packages/plugin-dummy-services/tsconfig.json\",\n \"packages/project-tee-starter/src/__tests__/build-order.test.ts\",\n \"packages/project-tee-starter/src/__tests__/env.test.ts\",\n \"packages/project-tee-starter/src/__tests__/file-structure.test.ts\",\n \"packages/project-tee-starter/src/index.ts\",\n \"packages/project-tee-starter/tsconfig.json\"\n ]\n },\n {\n \"title\": \"fix(client): Update AgentLog type structure and fix action viewer mapping\",\n \"prNumber\": 5834,\n \"type\": \"bugfix\",\n \"body\": \"related commit: https://github.com/elizaOS/eliza/commit/69a77180074633e53ba7dc2f9e28acf7f912238d#diff-883ced4e3fb77567f2861de8747a663ae1623fa5ed434e750885af2857d2944f\\r\\n\\r\\nissue:\\r\\n\\r\\n\\\"image\\\"` to `MultiStepActionResult` inte\",\n \"files\": [\n \"packages/core/src/prompts.ts\",\n \"packages/plugin-bootstrap/src/index.ts\"\n ]\n },\n {\n \"title\": \"fix: (cli) test command minor fixes\",\n \"prNumber\": 5840,\n \"type\": \"bugfix\",\n \"body\": \"this is a tiny pr to fix some minor issues with the cli test command and default tests that come with project-starter and project-tee-starter.\\r\\n\\r\\n1. when passing a test name with the --name flag, it was lowercasing the passed test name, but\",\n \"files\": [\n \"CLAUDE.md\",\n \"README.md\",\n \"packages/cli/README.md\",\n \"packages/cli/src/commands/test/utils/project-utils.ts\",\n \"packages/cli/tests/commands/start.test.ts\",\n \"packages/project-starter/src/__tests__/character-plugin-ordering.test.ts\",\n \"packages/project-starter/src/__tests__/character.test.ts\",\n \"packages/project-tee-starter/src/__tests__/character.test.ts\",\n \"packages/project-tee-starter/src/__tests__/error-handling.test.ts\"\n ]\n },\n {\n \"title\": \"Bump vite from 6.0.5 to 6.1.6 in /packages/client in the npm_and_yarn group across 1 directory\",\n \"prNumber\": 5838,\n \"type\": \"other\",\n \"body\": \"Bumps the npm_and_yarn group with 1 update in the /packages/client directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite).\\n\\nUpdates `vite` from 6.0.5 to 6.1.6\\n
\\nRelease notes\\n

Sourced from\",\n \"files\": [\n \"packages/client/package.json\"\n ]\n },\n {\n \"title\": \"fix(core): fix TypeScript declarations in npm package\",\n \"prNumber\": 5846,\n \"type\": \"bugfix\",\n \"body\": \"Point package.json to existing generated types instead of broken re-exports to src/\\r\\n\\r\\n # Risks\\r\\n\\r\\n **Low** - This is a build configuration fix that corrects broken TypeScript declarations without changing any runtime behavior.\\r\\n\\r\\n # Bac\",\n \"files\": [\n \"bun.lock\",\n \"packages/core/build.ts\",\n \"packages/core/package.json\"\n ]\n },\n {\n \"title\": \"fix: move starters build scripts locally\",\n \"prNumber\": 5845,\n \"type\": \"bugfix\",\n \"body\": \"## PR: Fix `elizaos create` command build failure for new projects\\r\\n\\r\\n### Problem\\r\\nThe `elizaos create` command was failing when building newly created projects with the error:\\r\\n```\\r\\nCannot find module '../../build-utils' from '/path/to/pro\",\n \"files\": [\n \"bun.lock\",\n \"packages/api-client/src/__tests__/services/messaging.test.ts\",\n \"packages/client/src/hooks/__tests__/use-character-convert.test.ts\",\n \"packages/client/src/hooks/__tests__/use-panel-width-state.test.ts\",\n \"packages/client/src/hooks/__tests__/use-sidebar-state.test.ts\",\n \"packages/client/tsconfig.json\",\n \"packages/core/src/__tests__/buffer.test.ts\",\n \"packages/core/src/__tests__/environment.test.ts\",\n \"packages/core/src/__tests__/logger-browser-node.test.ts\",\n \"packages/core/src/__tests__/settings.test.ts\",\n \"packages/core/src/logger.ts\",\n \"packages/core/src/utils/__tests__/buffer.test.ts\",\n \"packages/core/src/utils/buffer.ts\",\n \"packages/plugin-dummy-services/src/tokenData/service.ts\",\n \"packages/plugin-quick-starter/build.ts\",\n \"packages/plugin-starter/build.ts\",\n \"packages/project-starter/build.ts\",\n \"packages/project-tee-starter/build.ts\",\n \"packages/project-tee-starter/src/__tests__/env.test.ts\",\n \"packages/project-tee-starter/src/__tests__/file-structure.test.ts\"\n ]\n }\n ],\n \"topContributors\": [\n {\n \"username\": \"wtfsayo\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n \"totalScore\": 1906.008437360646,\n \"prScore\": 1856.950437360646,\n \"issueScore\": 0,\n \"reviewScore\": 46,\n \"commentScore\": 3.058,\n \"summary\": \"wtfsayo: This month, wtfsayo focused on improving the build process and developer experience for the elizaos/eliza repository. They landed a significant build optimization in PR #5701, which also added markdown rendering support and removed nearly 3,500 lines of code. Additionally, they improved the developer workflow by auto-installing the CLI via PR #5702 and removed obsolete documentation and workflow files. Their work was concentrated on feature development and refactoring, primarily modifying configuration and code files.\"\n },\n {\n \"username\": \"ChristopherTrimboli\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4\",\n \"totalScore\": 525.9388783377705,\n \"prScore\": 424.38487833777043,\n \"issueScore\": 0,\n \"reviewScore\": 99.5,\n \"commentScore\": 2.054,\n \"summary\": \"ChristopherTrimboli: Focused on developing a new sessions API, opening a significant pull request in elizaos/eliza (#5704). This work involved substantial changes, modifying 13 files with over 1500 lines of new code and tests. This effort was primarily focused on new feature development and also included one peer review.\"\n },\n {\n \"username\": \"tcm390\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/60634884?u=c6c41679b8322eaa0c81f72e0b4ed95e80f0ac16&v=4\",\n \"totalScore\": 289.9295911791509,\n \"prScore\": 270.9295911791509,\n \"issueScore\": 0,\n \"reviewScore\": 19,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"0xbbjoker\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n \"totalScore\": 245.73794912067663,\n \"prScore\": 210.13794912067664,\n \"issueScore\": 0,\n \"reviewScore\": 35,\n \"commentScore\": 0.6000000000000001,\n \"summary\": \"0xbbjoker: Focused on repository maintenance and bug fixes this month, with their most impactful contribution being a significant cleanup that removed over 12,600 lines of unused specs in `elizaos/eliza#5724`. They also addressed logger compatibility issues by merging a fix in `elizaos-plugins/plugin-knowledge#38` and supported the team with two code reviews. This activity shows a primary focus on bugfix work, with the majority of changes concentrated in test files.\"\n },\n {\n \"username\": \"yungalgo\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/113615973?u=92e0f29f7e2fbb8ce46ed13c51f692ca803de02d&v=4\",\n \"totalScore\": 210.54947294994395,\n \"prScore\": 199.49147294994395,\n \"issueScore\": 0,\n \"reviewScore\": 9,\n \"commentScore\": 2.058,\n \"summary\": \"yungalgo: Focused on improving test components this month, opening a significant pull request in elizaos/eliza (#5705) to address a fix. This work-in-progress contains substantial changes (+2097/-635 lines) across 31 files, reflecting their 19 commits on the topic. Based on their code changes, their activity shows a primary focus on tests, bugfixes, and other related work.\"\n },\n {\n \"username\": \"odilitime\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n \"totalScore\": 151.481933112422,\n \"prScore\": 110.181933112422,\n \"issueScore\": 0,\n \"reviewScore\": 40.5,\n \"commentScore\": 0.8,\n \"summary\": \"odilitime: No activity this month.\"\n },\n {\n \"username\": \"Dexploarer\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/211557447?u=21a243d61cc1f87574328ae07fc64d7d7577b53d&v=4\",\n \"totalScore\": 107.1549254966236,\n \"prScore\": 107.1549254966236,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"Dexploarer: Focused on introducing a major new AI Gateway feature to the ElizaOS ecosystem this month. This significant initiative is captured across four open pull requests, highlighted by the core implementation in `elizaos/eliza#5806` which adds universal access to over 100 AI models. The supporting work, which includes adding the plugin to the registry (`elizaos-plugins/registry#203`, `#204`), involved substantial changes across 49 files (+5464/-451 lines). Dexploarer's efforts were concentrated entirely on new feature development, modifying both application code and configuration files.\"\n },\n {\n \"username\": \"monilpat\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/15067321?v=4\",\n \"totalScore\": 75.2957738965761,\n \"prScore\": 43.5437738965761,\n \"issueScore\": 24.4,\n \"reviewScore\": 5,\n \"commentScore\": 2.352,\n \"summary\": \"monilpat: Undertook a substantial development effort this month, reflected in 28 commits and a large volume of code changes (+39k/-44k lines) that have not yet been merged. In the elizaos/eliza repository, they were active in defining new work by creating five issues, including a bug report for a build failure (#5738) and several feature proposals for agent scenarios (#5725, #5726, #5727). This activity, supported by 7 issue comments, shows a primary focus on feature development and other foundational work.\"\n },\n {\n \"username\": \"alex-nax\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82507604?u=b3af75d82f80ed83007a77c351a64bdd9e5d67de&v=4\",\n \"totalScore\": 50.88309952482126,\n \"prScore\": 50.88309952482126,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"alex-nax: This month, alex-nax focused on feature development and bug fixes within the elizaos/eliza repository, with two pull requests currently open. These changes introduce the ability to cancel a run (#5728) and fix an issue with action chaining (#5736). The underlying commits for this work modified over 1200 files, with a heavy emphasis on configuration files, tests, and documentation.\"\n },\n {\n \"username\": \"linear\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/in/20150?v=4\",\n \"totalScore\": 50,\n \"prScore\": 0,\n \"issueScore\": 50,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"linear: Focused entirely on project planning and task definition within the elizaos/eliza repository this month. They created 18 issues to scope new features like a CLI run command (#5573), outline documentation needs (#5638), and flag critical bugs and CI failures for resolution (#5714, #5715). This work was instrumental in defining the development roadmap and identifying necessary improvements across the project. Their efforts indicate a focus on the CLI, documentation, and CI processes.\"\n },\n {\n \"username\": \"standujar\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4\",\n \"totalScore\": 46.591563680037474,\n \"prScore\": 32.091563680037474,\n \"issueScore\": 0,\n \"reviewScore\": 14.5,\n \"commentScore\": 0,\n \"summary\": \"standujar: No activity this month.\"\n },\n {\n \"username\": \"shiedot\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/115964822?v=4\",\n \"totalScore\": 40.4257738965761,\n \"prScore\": 40.4257738965761,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"theSchein\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/4759807?u=1367e8e3307b02aef996d930feafa29937ccb5b9&v=4\",\n \"totalScore\": 28.623573590279975,\n \"prScore\": 28.623573590279975,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"rejected-l\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/99460023?u=977f49541583c40f4fc5f6a9f11ca6c6a78b362a&v=4\",\n \"totalScore\": 26.67920303898299,\n \"prScore\": 26.67920303898299,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"rejected-l: Focused on maintaining the project's build infrastructure this month by opening a pull request to update a core dependency (elizaos/eliza#5762). This proposed change to the checkout action modified 41 lines across 26 files. Their work touched primarily configuration files, along with associated tests and documentation.\"\n },\n {\n \"username\": \"github-advanced-security\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/in/57789?v=4\",\n \"totalScore\": 22.5,\n \"prScore\": 0,\n \"issueScore\": 0,\n \"reviewScore\": 22.5,\n \"commentScore\": 0,\n \"summary\": \"github-advanced-security: No activity this month.\"\n },\n {\n \"username\": \"borisudovicic\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31806472?u=27713fbe603baae91ef519990facbacd6c23e93d&v=4\",\n \"totalScore\": 22,\n \"prScore\": 0,\n \"issueScore\": 22,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"borisudovicic: Focused on project planning and defining new work streams within the elizaos/eliza repository. This month, their contributions consisted of creating 12 issues to scope out new features and infrastructure. This included initiating work on a rate-limited LLM endpoint (#5438), defining requirements for new agents (#5494, #5767), and outlining plans for a v2/v3 benchmark suite (#5764) and telemetry for training data (#5772).\"\n },\n {\n \"username\": \"prestoalvarez\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/140459501?u=b843478cdfec2bca070ff99ebb65f8f6a8161aba&v=4\",\n \"totalScore\": 21.419306144334055,\n \"prScore\": 21.419306144334055,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"Sergey1997\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/22988415?u=5ac6b5778c46fd3783556a946cac05ba4d7bd2aa&v=4\",\n \"totalScore\": 12.873759469228055,\n \"prScore\": 12.673759469228056,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"Sergey1997: Focused on a significant integration effort this month, reflected in the open pull request elizaos/eliza#5811. This single PR contains substantial changes across 1401 files, with five commits modifying over 200,000 lines of code (+43,633/-164,834). Their other activity included making one comment on a pull request.\"\n },\n {\n \"username\": \"mmalik-al\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/144422633?u=986f63acb4dee076448142e0a724f1c4419543d3&v=4\",\n \"totalScore\": 12.778306144334056,\n \"prScore\": 12.778306144334056,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"yohaiai\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/1732742?v=4\",\n \"totalScore\": 11.827306144334056,\n \"prScore\": 11.827306144334056,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"yohaiai: This month, yohaiai's work centered on expanding the plugin ecosystem. They opened a pull request to add a new connections plugin (elizaos-plugins/registry#196). This contribution consisted of minor configuration changes.\"\n },\n {\n \"username\": \"mandatedisrael\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32749185?u=d7ad7a2e6f7771775eda9a8a5dfbadb0390d535c&v=4\",\n \"totalScore\": 8.426879734614028,\n \"prScore\": 8.426879734614028,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"mandatedisrael: Contributed a documentation fix this month, opening a pull request to correct an error in the README.md for the elizaos/eliza repository (#5729). This contribution consisted of a single commit modifying one documentation file.\"\n },\n {\n \"username\": \"wookosh\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/120273332?u=493e01d0863a55ed139425760447079b96ef931d&v=4\",\n \"totalScore\": 8.377306144334055,\n \"prScore\": 8.377306144334055,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"wookosh: Focused on production configuration for the web UI this month. They merged PR elizaos/eliza#5735, which allows iframes when the web UI is enabled in production. This contribution was centered on the `elizaos/eliza` repository.\"\n },\n {\n \"username\": \"RolandOne\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/38446707?v=4\",\n \"totalScore\": 5.909573590279972,\n \"prScore\": 5.909573590279972,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"RolandOne: This month, RolandOne opened a pull request to add a new plugin to the registry (elizaos-plugins/registry#195), which involved a single-line addition to a configuration file.\"\n },\n {\n \"username\": \"HashWarlock\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/64296537?u=1d8228a93c06c603e08d438677b3f736d6b1ab22&v=4\",\n \"totalScore\": 5,\n \"prScore\": 0,\n \"issueScore\": 0,\n \"reviewScore\": 5,\n \"commentScore\": 0,\n \"summary\": \"HashWarlock: No activity this month.\"\n },\n {\n \"username\": \"samarth30\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/48334430?u=1fc119a6c2deb8cf60448b4c8961cb21dc69baeb&v=4\",\n \"totalScore\": 4,\n \"prScore\": 0,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"samarth30: This month, samarth30's activity was centered on deployment infrastructure. They opened an issue to address the Eliza cloud railway deployment (elizaos/eliza#5703), highlighting a focus on the operational aspects of the `elizaos/eliza` repository.\"\n },\n {\n \"username\": \"lalalune\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/18633264?u=e2e906c3712c2506ebfa98df01c2cfdc50050b30&v=4\",\n \"totalScore\": 4,\n \"prScore\": 0,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"lalalune: This month, lalalune focused on proposing new functionality for the `elizaos/eliza` repository. They opened two feature requests to enhance the core package, including adding an `IStorageService` type (elizaos/eliza#5698) and an `unregisterAction` function (elizaos/eliza#5697).\"\n },\n {\n \"username\": \"harperaa\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/1330944?v=4\",\n \"totalScore\": 4,\n \"prScore\": 0,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"harperaa: Focused on product quality this month by identifying and reporting bugs in the `elizaos/eliza` repository. They opened two issues related to Discord integration, highlighting that image generation (#5809) and direct messaging (#5810) were not working correctly.\"\n },\n {\n \"username\": \"1BDO\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/210645034?v=4\",\n \"totalScore\": 4,\n \"prScore\": 0,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"1BDO: No activity this month.\"\n },\n {\n \"username\": \"0xRabbidfly\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/93952856?v=4\",\n \"totalScore\": 4,\n \"prScore\": 0,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"0xRabbidfly: This month, 0xRabbidfly's contribution was focused on improving documentation by opening an issue in elizaos-plugins/plugin-twitter (#40) to request clarification on API tier requirements.\"\n },\n {\n \"username\": \"Kemystra\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/74447600?u=b02004f220ac249b7c1e3d847482c0f480a150d5&v=4\",\n \"totalScore\": 2.3000000000000003,\n \"prScore\": 0,\n \"issueScore\": 2.1,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"Kemystra: This month, Kemystra's activity was focused on identifying a build failure. They reported an issue where the Eliza CLI failed to build a project in elizaos/eliza (#5734).\"\n },\n {\n \"username\": \"ashuxshimra\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/105487009?u=23e8a61486d8a47efc1734ae7fdb61ccb191f349&v=4\",\n \"totalScore\": 2.2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"ashuxshimra: This month, ashuxshimra proposed the addition of a new Token Metrics Plugin by opening issue #202 in the elizaos-plugins/registry. They also made a substantial commit with over 3,000 lines of code changes across 4 files, indicating significant work in progress.\"\n },\n {\n \"username\": \"znahas\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/4540248?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"znahas: This month, znahas's contribution was focused on plugin stability. They identified and reported a potential crash in the knowledge plugin via issue elizaos-plugins/plugin-knowledge#37. This was their primary contribution, indicating a focus on the `elizaos-plugins/plugin-knowledge` repository.\"\n },\n {\n \"username\": \"madjin\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"madjin: This month, madjin's contribution was to propose new functionality by opening an issue in elizaos/elizaos.github.io (#150) to explore attestations via SAS / EAS.\"\n },\n {\n \"username\": \"jimthedj65\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/46975497?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"jimthedj65: This month, their activity was focused on identifying potential bugs. They reported a crash in the `elizaos/eliza` repository by creating issue #5706.\"\n },\n {\n \"username\": \"SavannahOz\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/227312217?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"LinuxIsCool\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31582215?u=b8eb5d3849bf877a3a0b686cf1632aca92e744ae&v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"LinuxIsCool: No activity this month.\"\n }\n ],\n \"newPRs\": 87,\n \"mergedPRs\": 73,\n \"newIssues\": 59,\n \"closedIssues\": 42,\n \"activeContributors\": 34\n}", "github_extracted_data_user_summaries_text_last_7_days_for_2025-08-30": "[\"Dexploarer_day_2025-08-24\", \"Dexploarer\", \"day\", \"2025-08-24\", \"Dexploarer: Focused on feature work, opening one PR, elizaos-plugins/registry#204, to add the Vercel AI Gateway Plugin to the Registry, and made two commits modifying two files with a primary focus on documentation and configuration.\", \"2025-08-24T23:10:01.245Z\"]\n[\"wtfsayo_day_2025-08-24\", \"wtfsayo\", \"day\", \"2025-08-24\", \"wtfsayo: Focused on code quality and collaboration, providing one approval review and four PR comments, in addition to one issue comment.\", \"2025-08-24T23:10:01.398Z\"]" }