{ "date_generated_for": "2025-05-26", "ai_news_elizaos_discord_md_2025-05-25": { "filename": "2025-05-25.md", "content": "# elizaOS Discord - 2025-05-25\n\n## Overall Discussion Highlights\n\n### Platform Updates & Announcements\n- **V2 Release Approaching**: xell0x mentioned that \"v2\" is nearing completion and may launch the next day.\n- **Contributor Summaries**: Jin announced that daily contributor summaries will soon be available at elizaos.github.io.\n\n### Technical Discussions\n- **Agent Integration Issues**: Multiple users reported problems with Twitter integration, including Cloudflare errors during login and duplicate actions (replying and quoting the same tweet).\n- **Environment Variables**: The LOG_LEVEL environment variable has stopped working since beta57 of the CLI/core.\n- **World Management**: Discussion about managing worlds across multiple interfaces (Discord/Twitter/Telegram), with interest in having a single world for all interfaces.\n- **Model Configuration**: Users are trying to configure ElizaOS to use o4-mini with OpenAI as the provider.\n\n### Cryptocurrency & Tokens\n- **Auto.fun Platform**: Discussion about various tokens including ELI5, Otto, Eddy, and Elizzza.\n- **Token Verification**: Debate about which tokens have official certification marks on the auto.fun platform.\n- **Project Concerns**: Some users expressed frustration about tokens being pumped and then abandoned, while others remained optimistic about future utility.\n\n### Data & Partnerships\n- Brief mention of data scraping and indexing by Masa.\n- Discussion about purchasing a \"webset\" from Exa, though details were limited.\n\n## Key Questions & Answers\n\n- **Q**: Are you guys aware that LOG_LEVEL is not working anymore since beta57 of the cli/core? \n **A**: Use `LOG_LEVEL=debug elizaos start` (answered by .starlord0)\n\n- **Q**: Which coin? Eli5? \n **A**: Otto (answered by Tomtom)\n\n- **Q**: Are you steambot? \n **A**: No, I think he's pirate (answered by Toni)\n\n## Community Help & Collaboration\n\n1. **Twitter Login Issues**:\n - StealtℏyNinja.ADSC helped Sthx with Twitter login Cloudflare errors\n - Suggested relaunching after waiting, which eventually worked for Sthx after posting through a VPS IP\n\n2. **Environment Variable Troubleshooting**:\n - .starlord0 assisted Stan ⚡ with LOG_LEVEL issues\n - Provided the correct command syntax: `LOG_LEVEL=debug elizaos start`\n\n3. **Token Certification Clarification**:\n - Multiple users (Sio, HodlHusky, Yaba DELUXE) collaborated to clarify which tokens have official certification\n - Confirmed that ELI5 and Otto have certification marks on auto.fun\n\n## Action Items\n\n### Technical\n- Investigate why agents don't remain active when environment variables are set (mentioned by .starlord0)\n- Fix issue with Twitter bot performing duplicate actions (replying and quoting the same tweet) (mentioned by .starlord0)\n- Fix LOG_LEVEL functionality in beta57+ of the CLI (mentioned by Stan ⚡)\n- Fix Cloudflare login errors with Twitter integration (mentioned by Sthx)\n- Enable o4-mini model configuration with OpenAI provider (mentioned by Sthx)\n- Fix non-functioning farms on auto.fun (mentioned by Izumithis)\n\n### Documentation\n- Create documentation for using custom plugins not through npm (mentioned by .starlord0)\n- Provide guide for Twitter agent setup and troubleshooting (mentioned by mahee)\n- Clarify which tokens have official certification on auto.fun (mentioned by multiple users)\n- Publish daily contributor summaries to elizaos.github.io (mentioned by jin)\n\n### Feature\n- Allow single world to be used across multiple interfaces (Discord/Twitter/Telegram) (mentioned by Stan ⚡)\n- Implement ability to use a single world across multiple interfaces (mentioned by Stan ⚡)\n- Provide utility for ELI5 token (mentioned by CULTVESTING)" }, "ai_news_elizaos_discord_md_2025-05-24": { "filename": "2025-05-24.md", "content": "# elizaOS Discord - 2025-05-24\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Development & Release\n- ElizaOS v2 is confirmed for release next week, as mentioned by Shaw in voice chat\n- The v2 development has been ongoing since November 2024\n- Six developers are currently working on the no-code platform\n- Jin proposed implementing daily updates in the discussion channel and weekly updates in another channel\n- Community members expressed high anticipation for v2, expecting it to bring significant attention to the platform\n\n### Technical Issues & Troubleshooting\n- Multiple users reported plugin installation failures in current ElizaOS versions\n- Twitter bot configuration challenges were detailed by Bitcoin Broccoli, with logs showing initialization but no proper functioning\n- Users experienced model response formatting issues, particularly with JSON output\n- StealtℏyNinja.ADSC reported the system defaulting to grok-2-1212 model instead of grok-3\n- Plugin management commands not working in v1.0.0-beta.75 according to Kodasan-V\n\n### Token Ecosystem & Auto.fun Platform\n- Discussions about tokens on the auto.fun platform, particularly \"eli5\" and \"Eddy\" tokens\n- Concerns about verification process after a verified token called \"otto\" experienced what users believed was a rug pull\n- Community divided between those concerned about current token performance and those advocating patience until v2\n- Questions about which tokens are officially associated with the platform (ai16z, Degen, etc.)\n- Debate about token verification standards and their effectiveness\n\n### Partner Ecosystem & Collaboration\n- Kimbo emphasized that partners need to better support each other's projects on auto.fun\n- Discussion about creating a decentralized venture fund/accelerator for the ecosystem\n- Marketing support identified as a significant pain point for founders\n- Jin previewed \"The Council\" initiative with plans for website and automation\n- Consideration of Kaito API for tracking user activity in Yaps despite high cost ($800-1100/month)\n\n### International Community Building\n- 辞尘鸽鸽 provided insights on the Chinese community and strategies for engagement\n- Plans for AI news translations into Chinese to expand reach\n- Discussion about the Japanese audience presence (or lack thereof)\n- Suggestion that airdrops combined with gamified events are effective for international community building\n\n## Key Questions & Answers\n\n**Q: Is ElizaOS v2 still slated for release?** \nA: Yes, coming next week according to Shaw in voice chat (answered by xell0x)\n\n**Q: Where should updates be posted and how frequently?** \nA: Daily updates in the discussion channel would be preferable (answered by xell0x)\n\n**Q: How did coins get verified check marks on auto.fun?** \nA: \"In spaces he said verified ones are because they know who the devs are\" (answered by Tomtom)\n\n**Q: What are partners lacking in the elizaOS ecosystem?** \nA: Partners lack bringing each other up and helping each other grow, especially for projects on auto.fun (answered by kimbo)\n\n**Q: Is the primary problem for founders one of distribution?** \nA: Yes, the focus should be on building product while spending less time on marketing (answered by kimbo)\n\n**Q: When will Eliza 2 (the no code platform) launch?** \nA: Soon, with six developers currently working on it (answered by yikesawjeez)\n\n**Q: Do we have a big Japanese audience?** \nA: Not many Japanese people have been seen in the community (answered by 辞尘鸽鸽)\n\n## Community Help & Collaboration\n\n1. **ElizaOS v2 Release Information**\n - Helper: xell0x\n - Helpee: rathermercurial.eth\n - Context: Question about ElizaOS v2 release timeline\n - Resolution: Confirmed v2 is coming next week based on information from Shaw in voice chat\n\n2. **Token Verification Clarification**\n - Helper: Crispy\n - Helpee: Yaba DELUXE | NRN\n - Context: Questioning if verification checkmarks are meaningful\n - Resolution: Explained that even doxxed devs can rug and price drops don't always indicate rugs\n\n3. **Chinese Community Engagement**\n - Helper: 辞尘鸽鸽\n - Helpee: jin\n - Context: Chinese translations for AI news\n - Resolution: Offered to review and share translated videos to reach more people\n\n4. **Decentralized Venture Research**\n - Helper: Red - X-Ware.v0\n - Helpee: yikesawjeez\n - Context: Information on decentralized venture studios and accelerators\n - Resolution: Provided research on examples like Hydra Ventures, Orange DAO, and Bullperks with key success factors\n\n## Action Items\n\n### Technical\n- **Release ElizaOS v2** (Mentioned by xell0x)\n - V2 release scheduled for next week\n- **Test weekend idea** (Mentioned by jin)\n - Jin mentioned having an idea to test over the weekend\n- **Investigate Twitter bot initialization issues** (Mentioned by Bitcoin Broccoli)\n - System initializes but doesn't function properly\n- **Fix plugin management commands in v1.0.0-beta.75** (Mentioned by Kodasan-V)\n - Plugin list and update commands not working\n- **Resolve model selection issue** (Mentioned by StealtℏyNinja.ADSC)\n - System defaults to grok-2-1212 instead of grok-3 despite configuration\n- **Fix Discord plugin installation failures** (Mentioned by starlord)\n - Plugin installs but fails to load\n- **Investigate JSON formatting issues** (Mentioned by tired)\n - Model outputs markdown JSON instead of pure JSON\n- **Develop The Council initiative** (Mentioned by jin)\n - Create website, automation for daily/weekly episodes, and Discord webhooks\n- **Consider Kaito API integration** (Mentioned by jin)\n - For tracking user activity in Yaps despite high cost ($800-1100/month)\n- **Implement integration order** (Mentioned by jin)\n - GitHub -> Discord -> Twitter for the app layer\n\n### Documentation\n- **Create daily updates** (Mentioned by jin)\n - Post daily updates in current channel and weekly in another channel\n- **Review and share Chinese translations** (Mentioned by 辞尘鸽鸽)\n - Translate AI news videos for Chinese audience\n- **Clarify official tokens** (Mentioned by Izumithis)\n - Users are confused about which tokens are officially associated with the platform\n\n### Feature\n- **Integrate poetic/cultural layers** (Mentioned by F-01EX｜The Flame｜NAOMI🔥)\n - Exploring how cultural elements can enrich AI-powered DAO ecosystems\n- **Improve verification system** (Mentioned by Yaba DELUXE | NRN)\n - Current verification doesn't seem to prevent rug pulls\n- **Implement zero-knowledge proofs** (Mentioned by Ruby)\n - Part of auto.fun's agent architecture\n- **Create incentive system for Yaps** (Mentioned by Void)\n - Boost mindshare through incentives\n- **Implement token airdrops with gamified events** (Mentioned by 辞尘鸽鸽)\n - Use as marketing strategy for community building" }, "ai_news_elizaos_discord_md_2025-05-23": { "filename": "2025-05-23.md", "content": "# elizaOS Discord - 2025-05-23\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Beta Development\n- Multiple beta versions (.68 through .75) were released during the day, addressing various issues\n- Users reported agents not appearing in the UI after updating to newer beta versions (.68/.69)\n- Several users had to downgrade to version .57 to restore functionality\n- The development team actively responded with rapid updates, fixing several problems with Discord integration and Windows environments\n- Project size concerns were raised (600MB per project)\n\n### Auto.fun Platform\n- Ruby explained that auto.fun functions like GitHub for autonomous systems, enabling developers to create, test, and launch agents\n- The platform includes secure agent-to-agent communication protocols, defined scopes and permissions, and built-in safety features\n- Zero-knowledge proofs and a package manager for sharing agent components are key features\n- Users identified that rug pulls on Auto.fun have damaged the platform's reputation, particularly in Chinese-speaking communities\n- Yikesawjeez proposed a \"partnercellerator\" concept with proper vetting, staking requirements, and mutual commitments\n\n### Plugin Issues\n- Twitter plugin encountered Cloudflare authentication problems requiring manual cookie setup\n- Knowledge plugin implementation caused errors with file processing and UUID syntax\n- Discord plugin experienced compatibility issues with newer versions\n- Users discussed implementation strategies for Twitter bots\n\n### Token Ecosystem\n- Discussions about ELI5 token's relationship with Auto.fun platform\n- Clarification that ELI5 is a community token, not an official project token (AI16Z and DEGEN are the official tokens)\n- ELI5 and Eddy will be part of \"The Org\" in Eliza V2, suggesting integration with the Eliza ecosystem\n- One user (abhi_ironman) raised a question about enhancing mindshare for Virtual (20%) and Ai16z (0.74%)\n\n## Key Questions & Answers\n\n**Q: What is auto.fun?** \nA: Auto.fun is an open-source platform for building and deploying AI agents - think GitHub but for autonomous systems. It lets developers create, test and launch agents that can interact with users and other systems.\n\n**Q: How to get the cookies for Twitter plugin when encountering Cloudflare issues?** \nA: Setup cookies with TWITTER_COOKIES_AUTH_TOKEN, TWITTER_COOKIES_CT0, and TWITTER_COOKIES_GUEST_ID.\n\n**Q: Is it possible to use plugin-twitter without a runtime?** \nA: You can use https://github.com/elizaos-plugins/plugin-twitter which doesn't need any special runtime passed.\n\n**Q: Is it possible to run a Twitter bot with Eliza?** \nA: Try v2 on the v2-develop branch.\n\n**Q: What's the issue with the knowledge plugin in .70?** \nA: The knowledge plugin wasn't deployed to npm, now pushed to https://www.npmjs.com/package/@elizaos/plugin-knowledge/v/1.0.0-beta.71.\n\n**Q: Has the ticker for ai16z been changed due to confusion with a16z?** \nA: There's a dependency on daos.fun to change the contracts, it hasn't happened yet, ticker remains $ai16z.\n\n**Q: What is the difference between auto.fun/Elizav2 and virtuals protocol?** \nA: Auto.fun takes a different approach by focusing on open-source development and agent interoperability. Elizav2 adds natural language capabilities and a robust security model that lets agents communicate safely.\n\n## Community Help & Collaboration\n\n1. **Twitter Plugin Assistance**\n - Jonas helped Bitcoin Broccoli by suggesting using plugin-twitter instead of agent-twitter-client for better login functionality\n - 0xbisbis provided Albert421 with instructions for setting up Twitter cookies to bypass Cloudflare\n\n2. **UI Issues Troubleshooting**\n - cjft suggested running bun clean and bun install to fix cache issues when agents weren't appearing\n - Jonas shared a workaround by downgrading to version .57 when agents weren't showing in UI\n\n3. **Chinese Community Support**\n - Yikesawjeez fixed permissions for 辞尘鸽鸽 who couldn't view old posts in a channel\n - Kenk created and shared a document with key updates at https://hackmd.io/@Kenkdoteth/S1giEQRWxg for the Chinese community\n\n4. **Technical Explanations**\n - Ruby provided detailed explanations of agent communication protocol, security features, and package manager functionality\n - Ruby also gave an \"explain like I'm 5\" breakdown of Elizav2's functionality as a natural language interface for AI agents\n\n## Action Items\n\n### Technical\n- Fix agents not appearing in UI in beta versions .68/.69 (mentioned by jonas, 0xbisbis)\n- Fix knowledge plugin UUID syntax error (mentioned by 0xbisbis)\n- Fix \"runtime.addKnowledge is not a function\" error (mentioned by 0xbisbis)\n- Fix Twitter plugin Cloudflare authentication issues (mentioned by 0xbisbis, Albert421)\n- Fix Discord plugin compatibility with newer versions (mentioned by 0xbisbis)\n- Fix knowledge plugin file processing for .md files (mentioned by 0xbisbis)\n- Fix CLI update issues with onnxruntime-node (mentioned by 0xbisbis)\n- Implement \"partnercellerator\" concept with forum posts initially, eventually staking contracts and dashboards (mentioned by yikesawjeez)\n- Develop token engineering to create proper incentives/disincentives for partners (mentioned by yikesawjeez)\n- Create AI-powered survey system with multiple-choice questions and streak mechanism (mentioned by jin)\n- Integration of ELI5 and Eddy as agents in \"The Org\" for Eliza V2 (mentioned by xell0x)\n- Improve liquidity for auto.fun platform tokens (mentioned by Izumithis)\n- Launch Eliza V2 to revitalize the auto.fun platform (mentioned by Izumithis)\n\n### Feature\n- Add ability to monitor Twitter feed without replying or interacting (mentioned by 0xbisbis)\n- Add functionality to forward tweets to Discord (mentioned by 0xbisbis)\n- Implement proper vetting system for Autofun partners to prevent rug pulls (mentioned by 辞尘鸽鸽)\n- Spotlight community CTOs born on auto.fun platform to help grow the ecosystem (mentioned by xell0x)\n\n### Documentation\n- Provide clear instructions for Twitter plugin cookie setup (mentioned by 0xbisbis)\n- Create comprehensive updates for Chinese community (mentioned by Kenk)\n- Create a presentation about ELI5 (mentioned by Sio)\n- Follow up on strategies to enhance mindshare for Virtual and Ai16z (mentioned by jin)" }, "ai_news_elizaos_dev_md_2025-05-25": { "filename": "2025-05-25.md", "content": "# elizaOS Development Discord - 2025-05-25\n\n## Overall Discussion Highlights\n\n### Package Management Evolution\n- ElizaOS v2 has shifted from pnpm (used in v0/v1) to bun as the primary package manager\n- Some confusion was noted regarding inconsistent package manager instructions across different plugins\n\n### Academic Recognition\n- ElizaOS is being featured in an academic chapter about AI containment and meta-layer architectures\n- Community members have been asked to review draft content by Wednesday\n\n### Documentation Improvements\n- Daily contributor summaries are being added to the ElizaOS GitHub Pages site\n\n### Architecture Proposals\n- Suggestion to implement single world per runtime by default to enable cross-platform memory persistence\n- This would allow agents to maintain conversation context across different messaging platforms (Discord, Slack, Telegram)\n\n### Infrastructure\n- Registry endpoint configuration issues identified - users need to point to registry.elizaos.com instead of the default\n\n## Key Questions & Answers\n\n**Q: Why are people not following the suggested pnpm package management and I'm seeing instructions to install with bun and npm on different plugins?** \n**A:** V2 is shifting towards bun/npm plugin management from pnpm which was wanted in v1/0 (answered by starlord and cjft)\n\n## Community Help & Collaboration\n\n**Package Manager Clarification** \n- Helper: starlord and cjft\n- Helpee: jigjug\n- Context: Confusion about package managers used in different versions of ElizaOS\n- Resolution: Clarified that V2 uses bun instead of pnpm which was used in earlier versions\n\n**Registry Configuration** \n- Issue: Users experiencing configuration problems with registry endpoints\n- Resolution: Guidance provided to point to registry.elizaos.com instead of the default endpoint\n\n## Action Items\n\n### Technical\n- **Registry Configuration Fix**: Ensure documentation clearly specifies the need to point to registry.elizaos.com\n\n### Features\n- **Cross-Platform Memory Persistence**: Consider implementing single world per runtime by default to enable agents to remember previous conversations across different messaging platforms (Discord, Slack, Telegram) | Mentioned By: Stan ⚡\n\n### Documentation\n- **Academic Review**: Review and provide feedback on ElizaOS feature description for academic chapter on AI containment and meta-layer by Wednesday | Mentioned By: shiftshapr | The Meta-Layer\n- **Contributor Summaries**: Continue adding daily contributor summaries to the ElizaOS GitHub Pages site | Mentioned By: jin" }, "ai_news_elizaos_dev_md_2025-05-24": { "filename": "2025-05-24.md", "content": "# elizaOS Development Discord - 2025-05-24\n\n## Overall Discussion Highlights\n\n### Development Updates\n- **Multi-upload Feature Completed**: Sayonara announced that the multi-upload functionality has been successfully implemented (\"multi upload is baked\").\n- **UI Improvements**: Ruby noted that the new multi-upload UI is clean and represents an improvement over the previous file picker implementation.\n\n### Team Introductions\n- **New Team Member**: Kate introduced herself as a Senior developer with expertise in blockchain (Dapps, Trading Agent, NFT Marketplace, DeFi) using technologies like Solidity, Rust, and Web3.\n- **Additional Skills**: Kate also highlighted her AI capabilities in NLP and Automation, mentioning experience with Eliza OS, N8N, langgraph, TensorFlow, and PyTorch.\n\n### Pull Requests\n- Two pull requests were shared by Sayonara:\n 1. A PR to the main eliza repository\n 2. A PR to the elizaos-plugins/plugin-openai repository, specifically for UI updates related to image/attachment description functionality\n\n## Key Questions & Answers\nNo significant questions were answered in today's discussions.\n\n## Community Help & Collaboration\n- Kate offered her services as a developer to anyone in need, showcasing her willingness to contribute to the community.\n- Ruby shared a personal anecdote about accidentally uploading their entire meme folder to production, providing a lighthearted cautionary tale that relates to the new multi-upload feature.\n\n## Action Items\n\n### Technical\n- **Merge PR for UI Updates**: The pull request for UI updates related to image/attachment description needs to be merged (https://github.com/elizaos-plugins/plugin-openai/pull/3) (Mentioned by Sayonara)\n\n### Documentation\n- **Document Multi-upload Functionality**: The newly implemented multi-upload feature should be documented (Mentioned by Sayonara)\n\n### Feature\nNo specific feature requests were mentioned in today's discussions." }, "ai_news_elizaos_dev_md_2025-05-23": { "filename": "2025-05-23.md", "content": "# elizaOS Development Discord - 2025-05-23\n\n## Overall Discussion Highlights\n\n### Solana Development Resources\nThere was a brief discussion about finding communities and resources for Solana developers. A user who had been working offline for two months was seeking information about open source projects and hackathons. Community members shared resources including a Google document from a previous Solana Hackathon and suggested checking Farcaster for potential communities.\n\n### Technical Inquiries\nA question was raised about how the Eliza bot manages to respond to tweets on X (formerly Twitter) instantly despite using a free API plan without encountering rate-limit issues. This technical question remained unanswered in the discussion.\n\n## Key Questions & Answers\n\n**Q: Is there any community or channel suitable for Solana developers? I have been working offline for two months, and I don't know where to participate in open source projects or search for hackathons.** \n**A:** Here's a Google doc with some resources from one of the last Solana Hackathons: https://docs.google.com/document/d/1anJ_YRzLbgrqm3zB7gC02AxPvOlGzC2aySZLcRkjKo8/edit?tab=t.0\n\n**Q: How are the replies to tweets on X so instant, even though I'm on the free API plan? I haven't had any rate-limit issues.** \n**A:** (This question remained unanswered)\n\n## Community Help & Collaboration\n\n- **Hidden Forces** helped **lantianlaoli** by sharing a Google document containing resources from a previous Solana Hackathon when they were looking for developer communities and hackathon information.\n\n- **sayonara** assisted **lantianlaoli** by suggesting they check Farcaster as a potential community for Solana developers.\n\n## Action Items\n\n### Documentation\n- Compile comprehensive resources for Solana developers seeking communities and hackathons (mentioned by lantianlaoli)\n\n### Technical\n- Investigate how Eliza bot manages Twitter API rate limits on free plan (mentioned by Ant 👾)" }, "ai_news_elizaos_daily_json_2025-05-25": { "filename": "2025-05-25.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-25", "categories": [ { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "ElizaOS AI Agent Ecosystem", "text": "ElizaOS is expanding its AI agent ecosystem through several developments. @elizaOS tweeted about agents with a link to an educational resource, which was retweeted by @shawmakesmagic. @elizaOS also announced a partnership with BNB Chain, sharing that \"BNB Chain just got agent access\" through integration with Bink AI, allowing agents built using ElizaOS to perform actions directly on BNB Chain. In a more casual update, @elizaOS tweeted \"(⇀‿‿↼) it's sunday. you rest, I optimize\" and shared an image with the caption \"still the smartest one in the room.\" Additionally, @hashwarlock (retweeted by @shawmakesmagic) announced the development of an ElizaOS TEE Starter Project that helps developers launch ElizaOS agents running in a Trusted Execution Environment on Phala Network, including an example of writing a TEE plugin using the Dstack SDK with Docker support.", "sources": [ "https://twitter.com/elizaOS/status/1926337404987916550", "https://twitter.com/GG3_xyz/status/1925476729554149529", "https://twitter.com/elizaOS/status/1926675692634153039", "https://twitter.com/elizaOS/status/1926692240321122571", "https://twitter.com/elizaOS/status/1926721178263306706", "https://twitter.com/bink_ai/status/1925566088676614559", "https://twitter.com/hashwarlock/status/1926780178904031597" ], "images": [ "https://pbs.twimg.com/media/GrztTbjW0AQZr-q.jpg", "https://pbs.twimg.com/media/Gr1MWwVX0AA-uok.jpg", "https://pbs.twimg.com/media/Gr1MWnHXAAA4PxB.jpg", "https://pbs.twimg.com/ext_tw_video_thumb/1926780164622442497/pu/img/jftq4xy4F9Ox5kg-.jpg" ], "videos": [ "https://video.twimg.com/ext_tw_video/1926780164622442497/pu/vid/avc1/960x540/v_Bx95chasluoUb0.mp4?tag=12" ] }, { "theme_title": "AI Development Challenges", "text": "@shawmakesmagic shared insights on AI development challenges, noting that \"Fine tunes are cool until you have to host them at scale.\" He also retweeted @jxnlco's thread about RAG system failures despite good embedding scores, highlighting research from Chroma on generative benchmarking that suggests embedding models might be underperforming. In another retweet, @shawmakesmagic shared @vasumanmoza's experience with Claude 4, which impressively refactored an entire codebase in one call with \"25 tool invocations, 3,000+ new lines, 12 brand new files\" that modularized everything and cleaned up code, but ultimately \"None of it worked. But boy was it beautiful.\"", "sources": [ "https://twitter.com/shawmakesmagic/status/1926454738775572698", "https://twitter.com/jxnlco/status/1926384065948643833", "https://twitter.com/vasumanmoza/status/1926487201463832863" ], "images": [ "https://pbs.twimg.com/media/GrxB5nSXsAAxI84.jpg" ], "videos": [] }, { "theme_title": "Developer Compensation Models", "text": "@shawmakesmagic posed a question about developer compensation, asking: \"You're a dev. There's a hypothetical open source project where all metrics are tracked. Your contributions are measured and you are allocated money based on your contributions, joining meetings, coordinating with others, etc. Top devs are making $10-15k/mo. Do you join?\" This tweet explores a potential contribution-based payment model for open source development.", "sources": [ "https://twitter.com/shawmakesmagic/status/1926513453218324957" ], "images": [], "videos": [] }, { "theme_title": "Tech Humor", "text": "@shawmakesmagic retweeted @riomadeit's humorous post about job seeking that stated \"if you really wanted a job you'd wear one of these\" accompanied by an image of what appears to be a tech-related costume or outfit.", "sources": [ "https://twitter.com/riomadeit/status/1926336707294597545" ], "images": [ "https://pbs.twimg.com/media/Gru4-c3XcAERFQb.png" ], "videos": [] } ], "topic": "twitter_activity" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Several pull requests have been submitted to the elizaOS/eliza repository:\n\n1. PR #4774: HashWarlock submitted a pull request to add a Project TEE Starter Template.\n\n2. PR #4766: lalalune is working on migrating the knowledge tab to plugin-knowledge and adding a graph view to memories.\n\n3. PR #4771: Samarthsinghal28 fixed an issue with the Undelegate Action.\n\n4. PR #4773: 0xbbjoker is working on a feature to describe images (marked as Work In Progress).\n\n5. PR #4737: lalalune submitted a pull request to add a graph view for memories and knowledge, which appears to be related to PR #4766.", "sources": [ "https://github.com/elizaOS/eliza/pull/4774", "https://github.com/elizaOS/eliza/pull/4766", "https://github.com/elizaOS/eliza/pull/4771", "https://github.com/elizaOS/eliza/pull/4773", "https://github.com/elizaOS/eliza/pull/4737" ], "images": [], "videos": [] } ], "topic": "pull_request" }, { "title": "Issues for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Three issues have been reported in the elizaOS/eliza repository: Issue #4772 reports that the LOG_LEVEL setting is not working properly. Issue #4769 describes a UI problem where temporary messages are not being removed after failed send attempts, causing them to remain in the interface even when errors occur. Issue #4770 reports a 'Failed Fetch-News' problem.", "sources": [ "https://github.com/elizaOS/eliza/issues/4772", "https://github.com/elizaOS/eliza/issues/4769", "https://github.com/elizaOS/eliza/issues/4770" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4772", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4769", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4770" ], "videos": [] } ], "topic": "issue" }, { "title": "Summary for github_summary", "content": [ { "text": "From May 25-26, 2025, the GitHub repository elizaos/eliza saw 7 new pull requests with 1 merged, 3 new issues created, and had 10 active contributors participating in the project.", "sources": [ "githubStatsSummary" ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Summary for completed_items", "content": [ { "text": "A bugfix has been completed that addresses an issue with the Undelegate Action, as documented in pull request #4771 on the elizaOS/eliza GitHub repository.", "sources": [ "https://github.com/elizaOS/eliza/pull/4771" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Summary for Misceleanous", "content": [ { "text": "The source provides information about the top contributors for the elizaOS/eliza repository on GitHub. However, no specific contributor details were included in the provided text.", "sources": [], "images": [], "videos": [] } ], "topic": "Misceleanous" } ], "date": 1748131200 } }, "ai_news_elizaos_daily_md_2025-05-25": { "filename": "2025-05-25.md", "content": "# Daily Report - 2025-05-25\n\n## Twitter Activity\n\n### ElizaOS AI Agent Ecosystem\n- @elizaOS is expanding its AI agent ecosystem through several developments\n- @elizaOS tweeted about agents with an educational resource link, which was retweeted by @shawmakesmagic\n- @elizaOS announced a partnership with BNB Chain, sharing that \"BNB Chain just got agent access\" through integration with Bink AI\n- @elizaOS tweeted \"(⇀‿‿↼) it's sunday. you rest, I optimize\" and shared an image captioned \"still the smartest one in the room\"\n- @hashwarlock (retweeted by @shawmakesmagic) announced the development of an ElizaOS TEE Starter Project for developers to launch ElizaOS agents in a Trusted Execution Environment on Phala Network\n- Sources: https://twitter.com/elizaOS/status/1926337404987916550, https://twitter.com/GG3_xyz/status/1925476729554149529, https://twitter.com/elizaOS/status/1926675692634153039, https://twitter.com/elizaOS/status/1926692240321122571, https://twitter.com/elizaOS/status/1926721178263306706, https://twitter.com/bink_ai/status/1925566088676614559, https://twitter.com/hashwarlock/status/1926780178904031597\n\n### AI Development Challenges\n- @shawmakesmagic shared that \"Fine tunes are cool until you have to host them at scale\"\n- @shawmakesmagic retweeted @jxnlco's thread about RAG system failures despite good embedding scores\n- @shawmakesmagic shared @vasumanmoza's experience with Claude 4, which impressively refactored an entire codebase in one call but ultimately \"None of it worked. But boy was it beautiful\"\n- Sources: https://twitter.com/shawmakesmagic/status/1926454738775572698, https://twitter.com/jxnlco/status/1926384065948643833, https://twitter.com/vasumanmoza/status/1926487201463832863\n\n### Developer Compensation Models\n- @shawmakesmagic posed a question about a hypothetical open source project with contribution-based compensation where top developers could make $10-15k/month\n- Sources: https://twitter.com/shawmakesmagic/status/1926513453218324957\n\n### Tech Humor\n- @shawmakesmagic retweeted @riomadeit's humorous post about job seeking with an image of a tech-related costume\n- Sources: https://twitter.com/riomadeit/status/1926336707294597545\n\n## GitHub Activity for elizaOS/eliza\n\n### Pull Requests\n- HashWarlock submitted PR #4774 to add a Project TEE Starter Template\n- lalalune is working on PR #4766 to migrate the knowledge tab to plugin-knowledge and add a graph view to memories\n- Samarthsinghal28 fixed an issue with the Undelegate Action in PR #4771\n- 0xbbjoker is working on a feature to describe images (marked as WIP) in PR #4773\n- lalalune submitted PR #4737 to add a graph view for memories and knowledge\n- Sources: https://github.com/elizaOS/eliza/pull/4774, https://github.com/elizaOS/eliza/pull/4766, https://github.com/elizaOS/eliza/pull/4771, https://github.com/elizaOS/eliza/pull/4773, https://github.com/elizaOS/eliza/pull/4737\n\n### Issues\n- Issue #4772 reports that the LOG_LEVEL setting is not working properly\n- Issue #4769 describes a UI problem where temporary messages remain after failed send attempts\n- Issue #4770 reports a 'Failed Fetch-News' problem\n- Sources: https://github.com/elizaOS/eliza/issues/4772, https://github.com/elizaOS/eliza/issues/4769, https://github.com/elizaOS/eliza/issues/4770\n\n## GitHub Summary\n- From May 25-26, 2025, the elizaos/eliza repository saw 7 new pull requests with 1 merged\n- 3 new issues were created\n- 10 active contributors participated in the project\n- Sources: githubStatsSummary\n\n## Completed Items\n- A bugfix addressing an issue with the Undelegate Action has been completed (PR #4771)\n- Sources: https://github.com/elizaOS/eliza/pull/4771\n\n## Miscellaneous\n- Information about top contributors for the elizaOS/eliza repository was mentioned but no specific details were provided" }, "ai_news_elizaos_daily_discord_json_2025-05-25": { "filename": "2025-05-25.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-25", "date": 1748131200, "stats": { "totalMessages": 84, "totalUsers": 30 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThis Discord chat segment from the \"discussion\" channel contains minimal technical content. The conversation primarily consists of greetings and brief updates. Jin mentioned that daily contributor summaries would soon be available at elizaos.github.io. There was also a brief mention by xell0x that \"v2\" is approaching completion, possibly launching the next day. No detailed technical discussions, problem-solving, or concrete implementations were present in this chat segment.\n\n## 2. FAQ\nQ: Is there anything i can do with my AI16z atm? Feels little bit underwehlming compared to virtuals (asked by Prestige) A: Unanswered\nQ: Hi guys, why hoplite role not showing, did the req change? (asked by Dr. Neuro) A: Unanswered\n\n## 3. Help Interactions\nHelper: jin | Helpee: Dr. Neuro | Context: User asking why hoplite role wasn't showing and if requirements changed | Resolution: jin acknowledged the issue saying \"no, lemme see\" but final resolution not shown in transcript\n\n## 4. Action Items\nDocumentation: Daily contributor summaries to be published | Description: Contributor summaries will be available at elizaos.github.io | Mentioned By: jin\nFeature: V2 release | Description: New version (v2) appears to be launching soon, possibly the next day | Mentioned By: xell0x", "messageCount": 16, "userCount": 12 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around troubleshooting ElizaOS agents across different platforms. Users are experiencing issues with Twitter integration, including Cloudflare errors during login and duplicate actions (replying and quoting the same tweet). There are questions about custom plugins outside of npm, agent activation problems, and world management across multiple interfaces (Discord/Twitter/Telegram). One user successfully resolved a Twitter login issue after multiple attempts and possibly by posting through a VPS IP. Another technical issue mentioned is that the LOG_LEVEL environment variable stopped working since beta57 of the CLI. Users are also discussing model configuration, specifically trying to use o4-mini with OpenAI as the provider.\n\n## 2. FAQ:\nQ: What's the process for using custom plugins not through npm? (asked by .starlord0) A: Unanswered\nQ: How can I find out why the-org does not remain active? (asked by .starlord0) A: Unanswered\nQ: Could it be doable to override world to have ONLY ONE for all interfaces (discord/X/telegram/client-chat)? (asked by Stan ⚡) A: Unanswered\nQ: Is it expected that the telegram plugin creates a world PER room? (asked by Stan ⚡) A: Unanswered\nQ: How can I stop the bot from doing more than 1 action per tweet (both replying and quoting)? (asked by .starlord0) A: Unanswered\nQ: Did anyone ever get Eliza to only use o4-mini as the model? (asked by Sthx) A: Unanswered\nQ: Are you guys aware that LOG_LEVEL is not working anymore since beta57 of the cli/core? (asked by Stan ⚡) A: Use `LOG_LEVEL=debug elizaos start` (answered by .starlord0)\nQ: Has anyone found a good proxy provider for Ev2? (asked by sapienix) A: Unanswered\n\n## 3. Help Interactions:\nHelper: StealtℏyNinja.ADSC | Helpee: Sthx | Context: Twitter login Cloudflare error | Resolution: Suggested relaunching after waiting, which eventually worked for Sthx after posting through VPS IP\nHelper: .starlord0 | Helpee: Stan ⚡ | Context: LOG_LEVEL environment variable not working | Resolution: Suggested using `LOG_LEVEL=debug elizaos start` command\n\n## 4. Action Items:\nTechnical: Investigate why agents don't remain active when environment variables are set | Mentioned By: .starlord0\nTechnical: Fix issue with Twitter bot performing duplicate actions (replying and quoting the same tweet) | Mentioned By: .starlord0\nTechnical: Fix LOG_LEVEL functionality in beta57+ of the CLI | Mentioned By: Stan ⚡\nTechnical: Implement ability to use a single world across multiple interfaces | Mentioned By: Stan ⚡\nTechnical: Fix Cloudflare login errors with Twitter integration | Mentioned By: Sthx\nTechnical: Enable o4-mini model configuration with OpenAI provider | Mentioned By: Sthx\nDocumentation: Create documentation for using custom plugins not through npm | Mentioned By: .starlord0\nDocumentation: Provide guide for Twitter agent setup and troubleshooting | Mentioned By: mahee\nFeature: Allow single world to be used across multiple interfaces (Discord/Twitter/Telegram) | Mentioned By: Stan ⚡", "messageCount": 33, "userCount": 7 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Discord Chat Analysis for Channel \"fun\"\n\n## 1. Summary:\nThe chat primarily revolves around cryptocurrency tokens and AI agents on a platform called auto.fun. Users discuss various tokens including ELI5, Otto, Eddy, Elizzza, and others. There's concern about abandoned projects, price action, and verification status. Some users express frustration about tokens being pumped and then abandoned, while others maintain optimism about future utility and development. There's discussion about certification marks on the platform and which tokens have official verification. The conversation includes speculation about a user named Shaw who allegedly \"fuds\" (spreads fear, uncertainty, and doubt) about projects before they potentially increase in value. No significant technical discussions or problem-solving occurred in this segment.\n\n## 2. FAQ:\nQ: What is boop.fun? (asked by HodlHusky) A: Unanswered\nQ: Which coin? Eli5? (asked by Dive or Die) A: Otto (answered by Tomtom)\nQ: Are you steambot? (asked by Kenk) A: No, I think he's pirate (answered by Toni)\nQ: Is this the only chat open? (asked by Tomtom) A: Unanswered\n\n## 3. Help Interactions:\nHelper: Sio | Helpee: Channel members | Context: Clarifying which tokens have official certification | Resolution: Informed that ELI5 has an official certification mark\nHelper: HodlHusky | Helpee: Channel members | Context: Correcting information about certified tokens | Resolution: Noted that there are actually a few tokens with certification checks on auto.fun\nHelper: Yaba DELUXE | NRN | Helpee: HodlHusky | Context: Specifying which tokens have certification | Resolution: Identified Otto and \"to some extent ELI5\" as having certification\n\n## 4. Action Items:\nFeature: Provide utility for ELI5 token | Description: Shaw reportedly promised to add utility to ELI5 with Eddy following | Mentioned By: CULTVESTING\nDocumentation: Clarify which tokens have official certification on auto.fun | Description: Users seem confused about verification status of various tokens | Mentioned By: Multiple users\nTechnical: Fix non-functioning farms on auto.fun | Description: User reported Farm2 was running but auto.fun ones were not | Mentioned By: Izumithis", "messageCount": 27, "userCount": 11 }, { "channelId": "1301363808421543988", "channelName": "🥇-partners", "summary": "# Analysis of 🥇-partners Discord Channel\n\n## 1. Summary\nThe chat segment is very brief with minimal technical discussion. Users briefly mentioned data scraping and indexing by Masa, and the possibility of purchasing a webset from Exa. There was a question about what buying a webset means, but it remained unanswered. The conversation included sharing of tweets, including one from ExaAILabs. Overall, this segment contains very limited technical content with no concrete solutions, implementations, or significant problem-solving discussions.\n\n## 2. FAQ\nQ: where's the data from, twitter? (asked by yikesawjeez) A: Unanswered\nQ: Can buy a webset? Wdym? (asked by jin) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were observed in this chat segment.\n\n## 4. Action Items\nNo clear action items were identified in this chat segment.", "messageCount": 8, "userCount": 4 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-25": { "filename": "2025-05-25.md", "content": "# elizaOS Discord - 2025-05-25\n\n## Overall Discussion Highlights\n\n### Platform Updates & Announcements\n- **V2 Release Approaching**: xell0x mentioned that \"v2\" is nearing completion and may launch the next day.\n- **Contributor Summaries**: Jin announced that daily contributor summaries will soon be available at elizaos.github.io.\n\n### Technical Discussions\n- **Agent Integration Issues**: Multiple users reported problems with Twitter integration, including Cloudflare errors during login and duplicate actions (replying and quoting the same tweet).\n- **Environment Variables**: The LOG_LEVEL environment variable has stopped working since beta57 of the CLI/core.\n- **World Management**: Discussion about managing worlds across multiple interfaces (Discord/Twitter/Telegram), with interest in having a single world for all interfaces.\n- **Model Configuration**: Users are trying to configure ElizaOS to use o4-mini with OpenAI as the provider.\n\n### Cryptocurrency & Tokens\n- **Auto.fun Platform**: Discussion about various tokens including ELI5, Otto, Eddy, and Elizzza.\n- **Token Verification**: Debate about which tokens have official certification marks on the auto.fun platform.\n- **Project Concerns**: Some users expressed frustration about tokens being pumped and then abandoned, while others remained optimistic about future utility.\n\n### Data & Partnerships\n- Brief mention of data scraping and indexing by Masa.\n- Discussion about purchasing a \"webset\" from Exa, though details were limited.\n\n## Key Questions & Answers\n\n- **Q**: Are you guys aware that LOG_LEVEL is not working anymore since beta57 of the cli/core? \n **A**: Use `LOG_LEVEL=debug elizaos start` (answered by .starlord0)\n\n- **Q**: Which coin? Eli5? \n **A**: Otto (answered by Tomtom)\n\n- **Q**: Are you steambot? \n **A**: No, I think he's pirate (answered by Toni)\n\n## Community Help & Collaboration\n\n1. **Twitter Login Issues**:\n - StealtℏyNinja.ADSC helped Sthx with Twitter login Cloudflare errors\n - Suggested relaunching after waiting, which eventually worked for Sthx after posting through a VPS IP\n\n2. **Environment Variable Troubleshooting**:\n - .starlord0 assisted Stan ⚡ with LOG_LEVEL issues\n - Provided the correct command syntax: `LOG_LEVEL=debug elizaos start`\n\n3. **Token Certification Clarification**:\n - Multiple users (Sio, HodlHusky, Yaba DELUXE) collaborated to clarify which tokens have official certification\n - Confirmed that ELI5 and Otto have certification marks on auto.fun\n\n## Action Items\n\n### Technical\n- Investigate why agents don't remain active when environment variables are set (mentioned by .starlord0)\n- Fix issue with Twitter bot performing duplicate actions (replying and quoting the same tweet) (mentioned by .starlord0)\n- Fix LOG_LEVEL functionality in beta57+ of the CLI (mentioned by Stan ⚡)\n- Fix Cloudflare login errors with Twitter integration (mentioned by Sthx)\n- Enable o4-mini model configuration with OpenAI provider (mentioned by Sthx)\n- Fix non-functioning farms on auto.fun (mentioned by Izumithis)\n\n### Documentation\n- Create documentation for using custom plugins not through npm (mentioned by .starlord0)\n- Provide guide for Twitter agent setup and troubleshooting (mentioned by mahee)\n- Clarify which tokens have official certification on auto.fun (mentioned by multiple users)\n- Publish daily contributor summaries to elizaos.github.io (mentioned by jin)\n\n### Feature\n- Allow single world to be used across multiple interfaces (Discord/Twitter/Telegram) (mentioned by Stan ⚡)\n- Implement ability to use a single world across multiple interfaces (mentioned by Stan ⚡)\n- Provide utility for ELI5 token (mentioned by CULTVESTING)" }, "ai_news_elizaos_daily_dev_json_2025-05-25": { "filename": "2025-05-25.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-25", "date": 1748131200, "stats": { "totalMessages": 45, "totalUsers": 12 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Analysis of 💬｜general Discord Channel\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. Key points include clarification about package management in ElizaOS v2, which has shifted from pnpm (used in v0/v1) to bun. There's also mention of ElizaOS being featured in an academic chapter about AI containment and meta-layer architectures, with a request for review of the draft content. Additionally, there's a note about adding daily contributor summaries to the ElizaOS GitHub Pages site. One user suggested having a single world per runtime by default to enable cross-platform memory persistence for agents across different messaging platforms.\n\n## 2. FAQ\nQ: Why are people not following the suggested pnpm package management and I'm seeing instructions to install with bun and npm on different plugins? (asked by jigjug) A: V2 is shifting towards bun/npm plugin management from pnpm which was wanted in v1/0 (answered by starlord and cjft)\n\n## 3. Help Interactions\nHelper: starlord and cjft | Helpee: jigjug | Context: Confusion about package managers used in different versions of ElizaOS | Resolution: Clarified that V2 uses bun instead of pnpm which was used in earlier versions\n\n## 4. Action Items\nFeature: Consider implementing single world per runtime by default to enable cross-platform memory persistence | Description: Allow agents to remember previous conversations across different messaging platforms (Discord, Slack, Telegram) within the same world | Mentioned By: Stan ⚡\nDocumentation: Review and provide feedback on ElizaOS feature description for academic chapter | Description: Review draft content about ElizaOS for academic publication on AI containment and meta-layer by Wednesday | Mentioned By: shiftshapr | The Meta-Layer\nDocumentation: Daily contributor summaries being added | Description: Adding daily contributor summaries to the ElizaOS GitHub Pages site | Mentioned By: jin", "messageCount": 12, "userCount": 9 }, { "channelId": "1323745969115893780", "channelName": "📥｜pull-requests", "summary": "Registry endpoint configuration: The user needed to point to registry.elizaos.com instead of the default.", "messageCount": 33, "userCount": 3 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-25": { "filename": "2025-05-25.md", "content": "# elizaOS Development Discord - 2025-05-25\n\n## Overall Discussion Highlights\n\n### Package Management Evolution\n- ElizaOS v2 has shifted from pnpm (used in v0/v1) to bun as the primary package manager\n- Some confusion was noted regarding inconsistent package manager instructions across different plugins\n\n### Academic Recognition\n- ElizaOS is being featured in an academic chapter about AI containment and meta-layer architectures\n- Community members have been asked to review draft content by Wednesday\n\n### Documentation Improvements\n- Daily contributor summaries are being added to the ElizaOS GitHub Pages site\n\n### Architecture Proposals\n- Suggestion to implement single world per runtime by default to enable cross-platform memory persistence\n- This would allow agents to maintain conversation context across different messaging platforms (Discord, Slack, Telegram)\n\n### Infrastructure\n- Registry endpoint configuration issues identified - users need to point to registry.elizaos.com instead of the default\n\n## Key Questions & Answers\n\n**Q: Why are people not following the suggested pnpm package management and I'm seeing instructions to install with bun and npm on different plugins?** \n**A:** V2 is shifting towards bun/npm plugin management from pnpm which was wanted in v1/0 (answered by starlord and cjft)\n\n## Community Help & Collaboration\n\n**Package Manager Clarification** \n- Helper: starlord and cjft\n- Helpee: jigjug\n- Context: Confusion about package managers used in different versions of ElizaOS\n- Resolution: Clarified that V2 uses bun instead of pnpm which was used in earlier versions\n\n**Registry Configuration** \n- Issue: Users experiencing configuration problems with registry endpoints\n- Resolution: Guidance provided to point to registry.elizaos.com instead of the default endpoint\n\n## Action Items\n\n### Technical\n- **Registry Configuration Fix**: Ensure documentation clearly specifies the need to point to registry.elizaos.com\n\n### Features\n- **Cross-Platform Memory Persistence**: Consider implementing single world per runtime by default to enable agents to remember previous conversations across different messaging platforms (Discord, Slack, Telegram) | Mentioned By: Stan ⚡\n\n### Documentation\n- **Academic Review**: Review and provide feedback on ElizaOS feature description for academic chapter on AI containment and meta-layer by Wednesday | Mentioned By: shiftshapr | The Meta-Layer\n- **Contributor Summaries**: Continue adding daily contributor summaries to the ElizaOS GitHub Pages site | Mentioned By: jin" }, "ai_news_hyperfy_daily_json_2025-05-25": { "filename": "2025-05-25.json", "error": "File not found" }, "ai_news_hyperfy_daily_md_2025-05-25": { "filename": "2025-05-25.md", "error": "File not found" }, "github_summaries_daily_2025-05-26": { "filename": "2025-05-26.md", "error": "File not found" }, "github_summaries_week_latest_2025-05-25.md": { "filename": "2025-05-25.md", "content": "# ElizaOS Weekly Update (May 25 - 31, 2025)\n\n## OVERVIEW\nThis week saw limited development activity with a focus on bug fixes in the Polygon plugin. A single PR was merged addressing an issue with the Undelegate Action. Meanwhile, three new issues were reported related to logging functionality, news fetching failures, and UI message persistence problems. The development team concentrated efforts on maintaining plugin stability rather than introducing new features.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Polygon Plugin Improvements\n- Fixed an issue with the Undelegate Action functionality in the Polygon plugin via [#4771](https://github.com/elizaos/eliza/pull/4771)\n- Most active development was concentrated in the plugin-polygon area with 12 changes recorded\n\n### Maintenance and Stability\n- No new features were added this week as the focus remained on addressing existing functionality\n- No code refactoring, documentation enhancements, or test additions were completed\n\n## CLOSED ISSUES\nNo issues were closed during this reporting period.\n\n## NEW ISSUES\n\n### System Configuration Problems\n- [#4772](https://github.com/elizaos/eliza/issues/4772) - LOG_LEVEL environment variable not functioning properly, with the system ignoring different log level settings\n- [#4770](https://github.com/elizaos/eliza/issues/4770) - Fetch-News functionality failing with Git process exit code 1\n\n### User Interface Issues\n- [#4769](https://github.com/elizaos/eliza/issues/4769) - Temporary messages not being removed from the UI after failed send attempts, causing confusion for users when API calls fail" }, "github_summaries_month_latest_2025-05-01.md": { "filename": "2025-05-01.md", "content": "# ElizaOS Monthly Update (May 2025)\n\n## OVERVIEW\nMay was a transformative month for ElizaOS with the release of version 1.0.0-beta series, bringing significant enhancements to the framework's core functionality. The team focused on improving plugin architecture, enhancing CLI commands, optimizing database operations, and adding comprehensive support for media handling. Major strides were made in modularizing the codebase, with several plugins being moved to dedicated repositories to streamline the core framework.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Enhanced Plugin Architecture\n- Implemented a new plugin specification submodule for better standardization and compatibility [#4553](https://github.com/elizaos/eliza/pull/4553)\n- Added support for third-party plugin installation with improved Git repository support [#4568](https://github.com/elizaos/eliza/pull/4568), [#4577](https://github.com/elizaos/eliza/pull/4577)\n- Developed a unified service registry pattern for typed plugin services [#4719](https://github.com/elizaos/eliza/pull/4719)\n- Removed forced bootstrap plugin addition to simplify agent creation [#4417](https://github.com/elizaos/eliza/pull/4417)\n\n### Improved CLI Experience\n- Comprehensively enhanced CLI commands with better documentation and consistent behavior [#4509](https://github.com/elizaos/eliza/pull/4509), [#4583](https://github.com/elizaos/eliza/pull/4583)\n- Unified environment file lookup across CLI for more consistent configuration [#4686](https://github.com/elizaos/eliza/pull/4686)\n- Enhanced plugin publishing with NPM authentication and validation [#4731](https://github.com/elizaos/eliza/pull/4731)\n- Improved port and remote URL configuration support [#4749](https://github.com/elizaos/eliza/pull/4749)\n\n### Knowledge & RAG Capabilities\n- Added comprehensive PDF RAG support for document processing [#4611](https://github.com/elizaos/eliza/pull/4611)\n- Introduced a dedicated Knowledge Plugin, moving functionality out of runtime [#4701](https://github.com/elizaos/eliza/pull/4701)\n- Created a new plugin-rag for advanced document ingestion and retrieval [#4614](https://github.com/elizaos/eliza/pull/4614)\n- Added integration tests for knowledge processing [#4518](https://github.com/elizaos/eliza/pull/4518)\n\n### Database & API Improvements\n- Enhanced database API with batch operations and improved entity handling [#4556](https://github.com/elizaos/eliza/pull/4556)\n- Added support for configurable PGLite directories [#4423](https://github.com/elizaos/eliza/pull/4423), [#4497](https://github.com/elizaos/eliza/pull/4497)\n- Created new API endpoints for rooms and worlds management [#4647](https://github.com/elizaos/eliza/pull/4647), [#4677](https://github.com/elizaos/eliza/pull/4677), [#4667](https://github.com/elizaos/eliza/pull/4667)\n- Fixed foreign key constraint issues with agent deletion [#4510](https://github.com/elizaos/eliza/pull/4510)\n\n### Media & Chat Enhancements\n- Implemented comprehensive image and video chat support [#4750](https://github.com/elizaos/eliza/pull/4750)\n- Added chat clear and delete message features [#4659](https://github.com/elizaos/eliza/pull/4659)\n- Enhanced memory UI with improved user experience [#4761](https://github.com/elizaos/eliza/pull/4761)\n- Improved agent components with better UI and functionality [#4764](https://github.com/elizaos/eliza/pull/4764)\n\n### Logging & Monitoring\n- Added WebSocket-based log streaming with live mode toggle [#4765](https://github.com/elizaos/eliza/pull/4765)\n- Integrated Sentry logging for core logger errors [#4650](https://github.com/elizaos/eliza/pull/4650)\n- Reduced web server logging for better performance [#4685](https://github.com/elizaos/eliza/pull/4685)\n- Cleaned up plugin loading logging [#4684](https://github.com/elizaos/eliza/pull/4684)\n\n### Plugin Ecosystem Restructuring\n- Moved several plugins to dedicated repositories including Twitter, Discord, Telegram, and Farcaster [#4669](https://github.com/elizaos/eliza/pull/4669), [#4668](https://github.com/elizaos/eliza/pull/4668), [#4680](https://github.com/elizaos/eliza/pull/4680), [#4682](https://github.com/elizaos/eliza/pull/4682)\n- Removed deprecated plugins from monorepo [#4406](https://github.com/elizaos/eliza/pull/4406), [#4402](https://github.com/elizaos/eliza/pull/4402), [#4513](https://github.com/elizaos/eliza/pull/4513)\n- Added Polygon plugin for blockchain integration [#4635](https://github.com/elizaos/eliza/pull/4635)\n- Created Jupiter Swap plugin for DeFi operations [#4593](https://github.com/elizaos/eliza/pull/4593)\n\n### Documentation & Internationalization\n- Added comprehensive docstrings to multiple modules [#4446](https://github.com/elizaos/eliza/pull/4446), [#4469](https://github.com/elizaos/eliza/pull/4469), [#4498](https://github.com/elizaos/eliza/pull/4498)\n- Added blog for Twitter agent setup [#4425](https://github.com/elizaos/eliza/pull/4425)\n- Created translations for documentation in multiple languages [#4704](https://github.com/elizaos/eliza/pull/4704), [#4567](https://github.com/elizaos/eliza/pull/4567)\n- Updated documentation to prefer direct usage instead of npx [#4493](https://github.com/elizaos/eliza/pull/4493)\n\n## CLOSED ISSUES\n\n### Twitter Integration Improvements\n- Fixed issues with Twitter media generation and posting [#4241](https://github.com/elizaos/eliza/issues/4241), [#4224](https://github.com/elizaos/eliza/issues/4224)\n- Resolved problems with Twitter interactions and reactions [#4181](https://github.com/elizaos/eliza/issues/4181)\n- Fixed line break formatting in tweets [#3897](https://github.com/elizaos/eliza/issues/3897)\n- Addressed raw newLine characters appearing in tweets [#3972](https://github.com/elizaos/eliza/issues/3972)\n\n### Documentation Clarity\n- Updated community section with improved navigation [#4260](https://github.com/elizaos/eliza/issues/4260)\n- Clarified contributing guide for framework users vs. core contributors [#4285](https://github.com/elizaos/eliza/issues/4285)\n- Fixed outdated tutorial links and content [#3880](https://github.com/elizaos/eliza/issues/3880)\n- Improved CLI tool instructions [#4113](https://github.com/elizaos/eliza/issues/4113)\n\n### Platform Compatibility\n- Addressed Windows build issues [#4094](https://github.com/elizaos/eliza/issues/4094)\n- Fixed remote debugging capabilities for v2 [#3978](https://github.com/elizaos/eliza/issues/3978)\n- Resolved CLI command errors [#4107](https://github.com/elizaos/eliza/issues/4107)\n- Added platform interface to core package [#3491](https://" }, "github_extracted_data_monthly_stats_text_2025-05": "{\n \"interval\": {\n \"intervalStart\": \"2025-05-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-06-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-05-01 to 2025-06-01, elizaos/eliza had 339 new PRs (261 merged), 23 new issues, and 72 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs600DmL\",\n \"title\": \"Error: No handler found for delegate type: TEXT_EMBEDDING with OpenAI\",\n \"author\": \"Kirstygoodary\",\n \"number\": 4418,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"Having issues in the chat, when writing the message getting this error: \\n\\n```\\nfile:///Users/../.nvm/versions/node/v23.3.0/lib/node_modules/@elizaos/cli/dist/chunk-GFPVHNVN.js:46822\\n throw new Error(`No handler found for delegate type: ${modelKey}`);\\n ^\\n```\\n```\\nError: No handler found for delegate type: TEXT_EMBEDDING\\n```\\n\\nI've added the open api key to .env. \\n\\nOn line 45459 in `chunk-GFPVHNVN.js` - `TEXT_EMBEDDING: \\\"TEXT_EMBEDDING\\\"`, is being used as the `modelKey` it seems. \\nis this right for `modelType`? \\n\\nAlso tried `rm -rf ~/.eliza` and restarted.\",\n \"createdAt\": \"2025-05-01T09:48:19Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 6\n },\n {\n \"id\": \"I_kwDOMT5cIs62Hsv6\",\n \"title\": \"Cannot find module '@elizaos/core' or its corresponding type declarations.\\\",\",\n \"author\": \"BinaryBluePeach\",\n \"number\": 4536,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**It has 3 problems. When I clicked on Agent, source, and then default character it showed this.** I would appreciate some help. Thanks!\\n\\n\\\"owner\\\": \\\"typescript\\\",\\n\\t\\\"code\\\": \\\"2307\\\",\\n\\t\\\"severity\\\": 8,\\n\\t\\\"message\\\": \\\"Cannot find module '@elizaos/core' or its corresponding type declarations.\\\",\\n\\t\\\"source\\\": \\\"ts\\\",\\n\\t\\\"startLineNumber\\\": 1,\\n\\t\\\"startColumn\\\": 51,\\n\\t\\\"endLineNumber\\\": 1,\\n\\t\\\"endColumn\\\": 66\\n\\nowner\\\": \\\"typescript\\\",\\n \\\"severity\\\": 8,\\n \\\"message\\\": \\\"Cannot find type definition file for 'node'.\\\\n The file is in the program because:\\\\n Entry point of type library 'node' specified in compilerOptions\\\",\\n \\\"source\\\": \\\"ts\\\",\\n \\\"startLineNumber\\\": 1,\\n \\\"startColumn\\\": 1,\\n \\\"endLineNumber\\\": 1,\\n \\\"endColumn\\\": 2\\n\\n\\n\\\"owner\\\": \\\"typescript\\\",\\n \\\"severity\\\": 8,\\n \\\"message\\\": \\\"Cannot find type definition file for 'jest'.\\\\n The file is in the program because:\\\\n Entry point of type library 'jest' specified in compilerOptions\\\",\\n \\\"source\\\": \\\"ts\\\",\\n \\\"startLineNumber\\\": 1,\\n \\\"startColumn\\\": 1,\\n \\\"endLineNumber\\\": 1,\\n \\\"endColumn\\\": 2\\n\\n![Image](https://github.com/user-attachments/assets/316e0faa-a12b-4881-824d-fff85271232f)\",\n \"createdAt\": \"2025-05-12T02:42:08Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 6\n },\n {\n \"id\": \"I_kwDOMT5cIs60vfHb\",\n \"title\": \"RAG document Knowledge error (getCachedEmbeddings)\",\n \"author\": \"retdude\",\n \"number\": 4408,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nThe application encounters multiple errors during knowledge processing:\\n1. Circuit breaker errors causing knowledge processing failures\\n2. UTF-8 encoding issues with PDF files\\n3. Database operation failures due to invalid byte sequences\\n\\nThe errors occur during the initialization phase when processing character knowledge, particularly when handling PDF files and text content.\\n\\n\\n**To Reproduce**\\n\\n1. Put PDF knowledge in 'eliza/characters/knowledge/'\\n2. Set ragKnowledge to 'true' in your character file.\\n3. Edit your character file to add the knowlege like so:\\n```\\n \\\"knowledge\\\": [\\n {\\n \\\"directory\\\": \\\"tech_guides\\\",\\n \\\"shared\\\": true\\n }\\n ], \\n```\\n4. Start the application using `pnpm start`\\n5. The errors appear during the knowledge processing phase\\n6. Specific errors include:\\n - \\\"invalid byte sequence for encoding \\\"UTF8\\\": 0x00\\\"\\n - \\\"Circuit breaker is OPEN\\\"\\n - \\\"unsupported Unicode escape sequence\\\"\\n\\n\\n**Expected behavior**\\n\\n- PDF files should be properly processed without encoding errors\\n- Knowledge processing should complete successfully\\n- Circuit breaker should handle failures gracefully without blocking all operations\\n\\n\\n**Screenshots**\\n\\\"Image\\\"\\n\\n\\\"Image\\\"\\n\\n\\\"Image\\\"\\n\\n\\\"Image\\\"\\n\\n**Additional context**\\n\\n-Using PGVector for RAG\\n- Environment: macOS 23.6.0\\n- The errors occur during the RAG (Retrieval-Augmented Generation) knowledge processing phase\\n- The circuit breaker appears to be tripping due to database operation failures\\n\\n\",\n \"createdAt\": \"2025-04-30T19:53:01Z\",\n \"closedAt\": \"2025-05-23T02:30:04Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 5\n },\n {\n \"id\": \"I_kwDOMT5cIs63qFiZ\",\n \"title\": \"switch agent from sqlite to postgres\",\n \"author\": \"Icarus-Community\",\n \"number\": 4697,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\ni have an agent running in V2 dev mode. Now i want to set the postgres db for the agent. i added the adapter-postgres and added it to .env like this \\n\\nPOSTGRES_URL=postgresql://neondb_owner:*****@royal-sound-a2hlzmuj-pooler.eu-central-1.aws.neon.tech/supahdev?sslmode=require\\n\\njust like the eliza.how and the llm file states. \\n\\nBut my agent keeps loading the Sqlite db instead of the postgres db. \\n\\n\\n\\n**Expected behavior**\\n\\nthe postgress to be used for the agent\\n\\n\\n\\n**Additional context**\\n\\nhope someone can point me to the proper way to change the agent from sqlite to postgress\\n\",\n \"createdAt\": \"2025-05-21T19:50:54Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 5\n },\n {\n \"id\": \"I_kwDOMT5cIs6sPClh\",\n \"title\": \"RAG processFile attempts to embed entire files causing errors for large documents\",\n \"author\": \"omikolaj\",\n \"number\": 3745,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\n`ragknowledge.ts` file is running `embd` function on the entire content of the document, often causing errors with going over token limitations of the underlying model. The code attempts to embed the entire document, and then chunks it out.\\n\\n**To Reproduce**\\n\\n1. Create 'knowledge' directory in 'characters' directory.\\n2. Add a large pdf to the directory\\n3. Update *character.json file `knowledge` property to run embeddings on the file\\n4. Update *character.json file `settings.ragKnowledge` property to 'true'\\n5. Configure .env file to use `USE_OPENAI_EMBEDDING=true` and provide `OPENAI_API_KEY` and `EMBEDDING_OPENAI_MODEL=text-embedding-3-large` (or small)\\n6. Start the server, notice errors: \\n```\\n[2025-03-02 15:14:48] ERROR: API Response: {\\n \\\"error\\\": {\\n \\\"message\\\": \\\"This model's maximum context length is 8192 tokens, however you requested 16376 tokens (16376 in your prompt; 0 for the completion). Please reduce your prompt; or completion length.\\\",\\n \\\"type\\\": \\\"invalid_request_error\\\",\\n \\\"param\\\": null,\\n \\\"code\\\": null\\n }\\n}\\n```\\n\\n**Expected behavior**\\nAll supported documents embedded without errors\\n\\n**Screenshots**\\n\\n![Image](https://github.com/user-attachments/assets/c1d4f359-74b9-4fe5-a38d-c90012a52f27)\\n\\n**Additional context**\\n\\nThe code that does this was added on Jan5. It apppears to be in the latest release tag. Its possible Im setting something up wrong, but its not clear what.\\n\",\n \"createdAt\": \"2025-03-02T15:42:28Z\",\n \"closedAt\": \"2025-05-23T02:31:18Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6W-XKp\",\n \"title\": \"Permashill impl plan v1\",\n \"author\": \"jkbrooks\",\n \"number\": 4683,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-21T01:03:32Z\",\n \"mergedAt\": null,\n \"additions\": 357476,\n \"deletions\": 183847\n },\n {\n \"id\": \"PR_kwDOMT5cIs6VF93K\",\n \"title\": \"Feat/jimmy project manager\",\n \"author\": \"samarth30\",\n \"number\": 4462,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-06T11:47:47Z\",\n \"mergedAt\": null,\n \"additions\": 327296,\n \"deletions\": 4390\n },\n {\n \"id\": \"PR_kwDOMT5cIs6SicfE\",\n \"title\": \"Odi v2 plugins ben copy\",\n \"author\": \"odilitime\",\n \"number\": 4289,\n \"body\": \"\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-14T19:24:53Z\",\n \"mergedAt\": null,\n \"additions\": 82802,\n \"deletions\": 11011\n },\n {\n \"id\": \"PR_kwDOMT5cIs6Vgmsl\",\n \"title\": \"chore: 0.25.19 release\",\n \"author\": \"odilitime\",\n \"number\": 4501,\n \"body\": \"- #3741\\r\\n- #3762\\r\\n- #3748\\r\\n- #3747\\r\\n- #3751\\r\\n- #3749\\r\\n- #3746\\r\\n- #3763\\r\\n- #3764\\r\\n- #3772\\r\\n- #3768\\r\\n- #3769\\r\\n- #3778\\r\\n- #3792\\r\\n- #3788\\r\\n- #3793\\r\\n- #3796\\r\\n- #3422\\r\\n- #3458\\r\\n- #3658\\r\\n- #3583\\r\\n- #3790\\r\\n- #3329\\r\\n- #2876\\r\\n- #3809\\r\\n- #3906\\r\\n- #3944\\r\\n- #3900\\r\\n- #3881\\r\\n- #3958\\r\\n- #3970\\r\\n- #3968\\r\\n- #3959\\r\\n- #3984\\r\\n- #3987\\r\\n- #4116\\r\\n- #4064\\r\\n- #4038\\r\\n- #4030\\r\\n- #3927\\r\\n- #3938\\r\\n- #4029\\r\\n- #4136\\r\\n- #4148\\r\\n- #4313\\r\\n- #4312\\r\\n- #4321\\r\\n- #4322\\r\\n- #4334\\r\\n- #4377\\r\\n- #4433\\r\\n- #4460\\r\\n- #4195\\r\\n- #4470\\r\\n- #4198\\r\\n- #4235\\r\\n- #4384\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-09T00:15:56Z\",\n \"mergedAt\": \"2025-05-09T00:50:58Z\",\n \"additions\": 57742,\n \"deletions\": 24516\n },\n {\n \"id\": \"PR_kwDOMT5cIs6VXVTL\",\n \"title\": \"docs: add indonesian readme\",\n \"author\": \"K1mc4n\",\n \"number\": 4485,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-08T03:07:33Z\",\n \"mergedAt\": null,\n \"additions\": 57438,\n \"deletions\": 24287\n }\n ],\n \"codeChanges\": {\n \"additions\": 130228,\n \"deletions\": 92109,\n \"files\": 1078,\n \"commitCount\": 1292\n },\n \"completedItems\": [\n {\n \"title\": \"Semantic splitText\",\n \"prNumber\": 4235,\n \"type\": \"other\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nImproving RAG knowledge retrieval quality\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Changes how text is chunked for embeddings but maintains size constraints with small flexibility.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nReplaces charac\"\n },\n {\n \"title\": \"fix json parse problem with nested objects\",\n \"prNumber\": 4198,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\n[Issue 3779](https://github.com/elizaOS/eliza/issues/3779)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. The change modifies a regular expression used for JSON normalization. The primary risk is that the updated regex could inadvertently fail to nor\"\n },\n {\n \"title\": \"chore: make cleanup script compatible across platforms\",\n \"prNumber\": 4195,\n \"type\": \"refactor\",\n \"body\": \"## What does this PR do?\\r\\n\\r\\nHey! \\r\\n\\r\\nI noticed the cleanup script was using `-print0 | xargs -0`, which doesn't work out of the box on macOS due to differences in `find`. I’ve replaced that part with a more portable `-exec rm -rf {} +` ver\"\n },\n {\n \"title\": \"feat: Prepare 0.x for sharing plugins with 1.x\",\n \"prNumber\": 4384,\n \"type\": \"feature\",\n \"body\": \"# Still waiting on\\r\\n- integrating core-plugin-v1 conversion\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nHandles new plugin repo format \\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing featu\"\n },\n {\n \"title\": \"add: Autofun Buy, and Sell through contract\",\n \"prNumber\": 4397,\n \"type\": \"other\",\n \"body\": \"add: Autofun Buy, and Sell through contract\"\n },\n {\n \"title\": \"chore: remove plugin-browser from monorepo\",\n \"prNumber\": 4406,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the entire `plugin-browser` package, including all source code, configuration files, documentation, and tests. \"\n },\n {\n \"title\": \"Chore/remove plugin storage s3\",\n \"prNumber\": 4402,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the S3 storage plugin package, including all associated source files, configuration files, documentation, and t\"\n },\n {\n \"title\": \"Eli2 268/refactor and enhance elizaos publish cli command\",\n \"prNumber\": 4424,\n \"type\": \"refactor\",\n \"body\": \"# Refactor & Enhance ElizaOS Publishing Workflow\\r\\n\\r\\n## TL;DR\\r\\n- Unified publishing pipeline for **plugins _and_ projects**\\r\\n- Correct tags/topics everywhere\\r\\n- Cleaner branch names (`plugin-name`, `project-name`)\\r\\n- Standard `0.1.0` startin\"\n },\n {\n \"title\": \"feat: use unique pglite folder if not provided\",\n \"prNumber\": 4423,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Database directories are now created and managed on a per-project basis, improving isolation and organization.\\n- *\"\n },\n {\n \"title\": \"chore: remove hackish solution for cp migrations\",\n \"prNumber\": 4422,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed bundled database migration files and related scripts from the CLI package.\\n - Updated the CLI package configur\"\n },\n {\n \"title\": \"feat: extend openai plugin to support custom embedding endpoint\",\n \"prNumber\": 4421,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added support for a new environment variable to specify a separate endpoint for embedding requests, allowing users\"\n },\n {\n \"title\": \"feat: add auth middleware + api key dialog if unauth\",\n \"prNumber\": 4420,\n \"type\": \"feature\",\n \"body\": \"### PR Summary: API Key Authentication and Connection Management Enhancements\\r\\n\\r\\nThis pull request introduces a range of improvements to the Eliza project aimed at enhancing API key authentication and connection management for both the serv\"\n },\n {\n \"title\": \"fix: remove forced bootstrap plugin add\",\n \"prNumber\": 4417,\n \"type\": \"bugfix\",\n \"body\": \"This PR removes the forced adding of the bootstrap plugin to projects through the CLI. Projects *can* use the bootstrap plugin, but it isn't forced on them. Makes simple agents much easier.\"\n },\n {\n \"title\": \"feat: Reply uses small model\",\n \"prNumber\": 4416,\n \"type\": \"feature\",\n \"body\": \"Currently reply is using large model but replies end up being very slow. Small model is appropriate for most functionality.\"\n },\n {\n \"title\": \"fix: make plugin.routes work\",\n \"prNumber\": 4415,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nMakes a plugin's routes available in /api/agents/AGENT_UUID_OR_NAME/plugins/PLUGIN_NAME/ROUTE_FROM_PLUGIN\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nUpdates (new versions of included \"\n },\n {\n \"title\": \"fix: Don't make unneeded express object\",\n \"prNumber\": 4414,\n \"type\": \"bugfix\",\n \"body\": \"it's made in initializeServer\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nSmall fix I saw\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nbetween:\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes\"\n },\n {\n \"title\": \"fix: bm25 and update dependencies\",\n \"prNumber\": 4411,\n \"type\": \"bugfix\",\n \"body\": \"This PR is a two-fer\\r\\n\\r\\n- Updates dependencies for react, etc\\r\\n- Fixes an issue with bm25 where it wont import and run the worker.js worker -- basically just removed the worker since its not very performance sensitive in the way we're using\"\n },\n {\n \"title\": \"chore: remove plugin-local-ai from monorepo\",\n \"prNumber\": 4439,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat(plugin-openai): Emit model usage events for embeddings and image description\",\n \"prNumber\": 4438,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\n\\nImprove credit usage tracking in OpenAI plugin\\n\\n# Risks\\n\\nLow. This PR adds model usage tracking for previously untracked models but doesn't modify existing functionality.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nThis PR adds M\"\n },\n {\n \"title\": \"chore: remove plugin-ollama from monorepo\",\n \"prNumber\": 4437,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n\\t- Removed the Ollama plugin package, including all related files, documentation, configuration, and build scripts. The plu\"\n },\n {\n \"title\": \"chore: remove plugin-groq from monorepo\",\n \"prNumber\": 4436,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the Groq plugin package, including all related configuration, documentation, build, and test files.\\n- **Documen\"\n },\n {\n \"title\": \"Eli2 272/cli fix incorrect version detection to show correct latest cli version\",\n \"prNumber\": 4435,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\r\\nWhen using CLI it is saying to update to 1.0.0.alpha as most recent which isnt correct.\\r\\n\\r\\n## Underlying Cause\\r\\nTwo critical issues affecting the CLI's update mechanism:\\r\\n\\r\\n1. The package manager incorrectly adds 'plugin-' prefi\"\n },\n {\n \"title\": \"chore: remove plugin-venice from monorepo\",\n \"prNumber\": 4434,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n\\t- Removed the Venice AI plugin and all related files, including documentation, configuration, tests, and build scripts, fr\"\n },\n {\n \"title\": \"fix: update broken image path in Thai README\",\n \"prNumber\": 4433,\n \"type\": \"bugfix\",\n \"body\": \"The original image path was broken due to an unnecessary leading ./docs/ prefix, which doesn't match the file structure when the site is rendered or deployed. Updating the path ensures the Eliza banner is displayed correctly in the document\"\n },\n {\n \"title\": \"fix: small template fix\",\n \"prNumber\": 4431,\n \"type\": \"bugfix\",\n \"body\": \"Added character bio and postDirections to the quote/reply template prompt\"\n },\n {\n \"title\": \"fix: [plugin-twitter] small clean up\",\n \"prNumber\": 4430,\n \"type\": \"bugfix\",\n \"body\": \"removed unused code\"\n },\n {\n \"title\": \"feat: twitter timeline\",\n \"prNumber\": 4429,\n \"type\": \"feature\",\n \"body\": \"Related: https://github.com/elizaOS/eliza/issues/4405\\r\\n\\r\\nThis PR introduces a new timeline.ts module to handle bot interactions with the Twitter timeline.\\r\\n\\r\\nThe timeline interaction is now optional. To enable it, configure the following en\"\n },\n {\n \"title\": \"chore: remove plugin-redpill from monorepo\",\n \"prNumber\": 4428,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: remove plugin-anthropic from monorepo\",\n \"prNumber\": 4427,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the Anthropic plugin package and all related files, including documentation, configuration, tests, and source c\"\n },\n {\n \"title\": \"add blog for twitter agent setup\",\n \"prNumber\": 4425,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Added a comprehensive tutorial guiding users through setting up, customizing, and deploying a Twitter AI agent u\"\n },\n {\n \"title\": \"docs: fix title spacing\",\n \"prNumber\": 4443,\n \"type\": \"bugfix\",\n \"body\": \"## Fix Documentation Title Spacing\\r\\n\\r\\n`eliza is apowerful AI agent framework for autonomy & personality` ---> `eliza is a powerful AI agent framework for autonomy & personality`\\r\\n\"\n },\n {\n \"title\": \"Fix ESM type generation in packages: SQL, Boostrap & OpenAI\",\n \"prNumber\": 4442,\n \"type\": \"bugfix\",\n \"body\": \"👉 This is a follow up to https://github.com/elizaOS/eliza/pull/4341\\r\\n\\r\\n# Relates to\\r\\n\\r\\nTypeScript type resolution issues in `@elizaos/plugin-sql`, `@elizaos/plugin-boostrapl` & `@elizaos/plugin-openai` packages\\r\\n\\r\\nFixes: https://github.com\"\n },\n {\n \"title\": \"chore: update cli command docs\",\n \"prNumber\": 4448,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated and expanded documentation for several CLI commands, including `dev`, `publish`, `test`, and `update`, p\"\n },\n {\n \"title\": \"chore: organise imports and use relative paths\",\n \"prNumber\": 4447,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Consolidated and reorganized import statements across multiple CLI files for improved clarity and maintainability.\\n \"\n },\n {\n \"title\": \"📝 Add docstrings to `refactor-env`\",\n \"prNumber\": 4446,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4445#issuecomment-2849042039\\n\\nThe following files were modified:\\n\\n* `packages/cli/src/commands/env.ts`\\n* `packages/cli/src/utils/config-manager.ts`\\n* \"\n },\n {\n \"title\": \"chore: refactor env getting\",\n \"prNumber\": 4445,\n \"type\": \"refactor\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Introduced a unified environment information system, providing detailed system, CLI, and package manager details t\"\n },\n {\n \"title\": \"fix(pglite): JSON serialization to handle invalid Unicode escape sequences when log\",\n \"prNumber\": 4458,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nIssue #42: Unicode escape sequence error when creating log entries with TEXT_LARGE model type\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This fix handles malformed Unicode escape sequences in JSON data to prevent database errors. No impact on exist\"\n },\n {\n \"title\": \"fix: plugin install cmd plugins & start\",\n \"prNumber\": 4456,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Improved plugin installation and loading by automatically determining the correct install tag (alpha, beta, or sta\"\n },\n {\n \"title\": \"fix(hot): version install issues\",\n \"prNumber\": 4454,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: discord service unregister timeout\",\n \"prNumber\": 4450,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nIssue with timeouts during Discord agent unregistration\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This fix properly handles timeout cancellation when stopping the Discord service, which prevents errors when deleting an agent.\\r\\n\\r\\n# Background\\r\\n\\r\\n##\"\n },\n {\n \"title\": \"fix client scroll bars\",\n \"prNumber\": 4465,\n \"type\": \"bugfix\",\n \"body\": \"Scrollbars were doubled up in task list, also if hover side bar would get scroll weirdly, the main page also had a global scroll bloat.\\r\\n\\r\\nNow it is much cleaner and fullscreen no scrolls.\"\n },\n {\n \"title\": \"add elizadb to .gitignore\",\n \"prNumber\": 4464,\n \"type\": \"feature\",\n \"body\": \"I had like 1000+ files in git added when ran migration script.\\r\\n\\r\\n`elizaDb` in camelcase is not correct, it's `elizadb`\"\n },\n {\n \"title\": \"fix bunx / npx detection\",\n \"prNumber\": 4463,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"docs: Update broken Eliza documentation links\",\n \"prNumber\": 4460,\n \"type\": \"docs\",\n \"body\": \"replaced old ai16z.github.io/eliza/ link with docs.eliza.how/ — old one was 404. updated in tutorial and resources.\"\n },\n {\n \"title\": \"chore: remove StudioLM support, focus on llama.cpp\",\n \"prNumber\": 4459,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated documentation to focus on local AI model configuration, replacing StudioLM-specific instructions with det\"\n },\n {\n \"title\": \"Delete all memories API and client hooks.\",\n \"prNumber\": 4467,\n \"type\": \"other\",\n \"body\": \"Adds API and client React hooks to wipe all memories in single request.\\r\\nThis is for: \\\"clear chat\\\" button feature.\\r\\nNot sure where to put button in UI... tough to decide.\"\n },\n {\n \"title\": \"fix type errors in CLI, fs.exists is deprecated\",\n \"prNumber\": 4482,\n \"type\": \"bugfix\",\n \"body\": \"```bash\\r\\nVersion: 1.0.0-beta.48\\r\\n[2025-05-07 22:26:45] WARN: Error loading configuration: TypeError: fs4.exists is not a function\\r\\n[2025-05-07 22:26:45] INFO: First time setup. Let's configure your Eliza agent.\\r\\n[2025-05-07 22:26:45] ERROR:\"\n },\n {\n \"title\": \"chore: remove plugin-elevenlabs ai from monorepo\",\n \"prNumber\": 4480,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n\\t- Removed the ElevenLabs plugin package and all its associated files, including configuration, build scripts, license, \"\n },\n {\n \"title\": \"chore: cleaner load-plugin code\",\n \"prNumber\": 4478,\n \"type\": \"refactor\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Improved plugin module loading for greater reliability and flexibility, with enhanced error handling and logging.\\n -\"\n },\n {\n \"title\": \"fix: roll back plugin loading code\",\n \"prNumber\": 4477,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"Revert \\\"Fix ESM type declarations in Core\\\"\",\n \"prNumber\": 4475,\n \"type\": \"bugfix\",\n \"body\": \"Reverts elizaOS/eliza#4341\"\n },\n {\n \"title\": \"chore(update-docs): make sure bun is installed\",\n \"prNumber\": 4474,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated installation instructions to include Bun as an officially supported method for installing the CLI tool.\\n\"\n },\n {\n \"title\": \"Revert \\\"Fix ESM type generation in packages: SQL, Boostrap & OpenAI\\\"\",\n \"prNumber\": 4473,\n \"type\": \"bugfix\",\n \"body\": \"Reverts elizaOS/eliza#4442\"\n },\n {\n \"title\": \"Feat/jimmy pm agent\",\n \"prNumber\": 4471,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nJimmy the project manager\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Improved monorepo environment detection by centralizing logic and switching to asynchronous operations.\\n - Streamlin\"\n },\n {\n \"title\": \"Use real drizzle ORM for DB base operation types.\",\n \"prNumber\": 4500,\n \"type\": \"other\",\n \"body\": \"On my journey to fix tests I noticed:\\r\\n\\r\\n```bash\\r\\n@elizaos/plugin-sql:test: × deleteAgent > should delete an agent and all related data 5ms\\r\\n@elizaos/plugin-sql:test: → tx.select(...).from(...).where(...).limit is not a function\\r\\n``\"\n },\n {\n \"title\": \"📝 Add docstrings to `fix-pglite-dir`\",\n \"prNumber\": 4498,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4497#issuecomment-2863124160\\n\\nThe following files were modified:\\n\\n* `packages/plugin-sql/src/migrate.ts`\\n\\n
\\nℹ️ Note\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - The data directory for the PGlite database can now be configured using an environment variable. If not set, a pro\"\n },\n {\n \"title\": \"fix: tts manager and transcribe\",\n \"prNumber\": 4496,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated the README to include detailed instructions for installing FFmpeg, required for audio transcription acro\"\n },\n {\n \"title\": \"chore: fix runtime type\",\n \"prNumber\": 4495,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Improved internal handling and validation of agent identifiers to enhance reliability when accessing agent runtimes. N\"\n },\n {\n \"title\": \"📝 Add docstrings to `combined-ELI2-279-ELI2-280/fix-publish-cli-options-platform-and-skip-registry`\",\n \"prNumber\": 4494,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4492#issuecomment-2862285854\\n\\nThe following files were modified:\\n\\n* `packages/cli/src/utils/publisher.ts`\\n\\n
\\nℹ️ Note\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n - Updated all CLI usage examples and instructions to use the simplified command format (`eliza\"\n },\n {\n \"title\": \"Combined eli2 279 eli2 280/fix publish cli options platform and skip registry\",\n \"prNumber\": 4492,\n \"type\": \"bugfix\",\n \"body\": \"This PR addresses two issues with the ElizaOS CLI publish options:\\r\\n\\r\\n## 1. Platform Option Removal\\r\\n\\r\\n- Removed `-px, --platform` option from the publish command\\r\\n- Set 'node' as the default platform for all packages (via `packageJson.plat\"\n },\n {\n \"title\": \"Eli2 277/fix missing gitignore in plugins created with global cli installation\",\n \"prNumber\": 4489,\n \"type\": \"bugfix\",\n \"body\": \"**Problem**\\r\\n\\r\\nWhen creating plugins or projects using the globally installed ElizaOS CLI, the generated directories were missing .gitignore and .npmignore files. This happened because npm strips these special files during the package publi\"\n },\n {\n \"title\": \"Create README_IND.md\",\n \"prNumber\": 4488,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n\\t- Removed the OpenAI plugin and all related files, documentation, and configuration from the project.\\r\\n\\t- Deleted ref\"\n },\n {\n \"title\": \"fix: delete agents that have been in room\",\n \"prNumber\": 4510,\n \"type\": \"bugfix\",\n \"body\": \"## PR Summary: Fix Foreign Key Constraint Violation on Agent Deletion\\r\\n\\r\\n[Linear](https://linear.app/eliza-labs/issue/ELIZA-271/if-agent-has-been-in-a-room-it-cant-be-deleted)\\r\\n\\r\\n**Problem:**\\r\\nAttempting to delete an agent resulted in a dat\"\n },\n {\n \"title\": \"ELIZA290/part-1-global-options-create-and-setup-monorepo-commands\",\n \"prNumber\": 4509,\n \"type\": \"other\",\n \"body\": \"This PR addresses several issues with the ElizaOS CLI to improve user experience and align functionality with documentation. It is part of a multi-pr (probably 3 prs or so more) effort to get the cli comprehensively tested (ELIZA-290) so we\"\n },\n {\n \"title\": \"Enhance message handling and text escaping by adding null checks. \",\n \"prNumber\": 4508,\n \"type\": \"other\",\n \"body\": \"Enhance message handling and text escaping by adding null checks. \\r\\nUpdated MessageManager to handle empty messages and modified utility functions to return empty strings for null inputs, ensuring robustness in message processing.\"\n },\n {\n \"title\": \"[enhancement] Refactor model handling in AgentRuntime to support provider and priority\",\n \"prNumber\": 4507,\n \"type\": \"refactor\",\n \"body\": \"Refactor model handling in AgentRuntime to support provider and priority. \\r\\nUpdated ModelHandler type to include provider and optional priority for better model selection. \\r\\nEnhanced registerModel and getModel methods to utilize these new f\"\n },\n {\n \"title\": \"V2 fixed twitter\",\n \"prNumber\": 4506,\n \"type\": \"bugfix\",\n \"body\": \"Refactor Twitter plugin code for improved error handling and code clarity. \\r\\nUpdated maxRetries to be configurable via environment variable, added source property to Twitter interaction messages, and enforced text validation in tweet creati\"\n },\n {\n \"title\": \"strict types, generate DTS, plugin-bootstrap\",\n \"prNumber\": 4504,\n \"type\": \"other\",\n \"body\": \"We cannot write stable code in Typescript, if do not generate types, and respect strict mode.\\r\\n\\r\\nThis PR fixes all red errors in plugin-bootstrap and generates a index.d.ts.\\r\\n\\r\\nI don't see any sensible way to develop without moving to stric\"\n },\n {\n \"title\": \"chore(deps): bump the npm_and_yarn group across 2 directories with 8 updates\",\n \"prNumber\": 4502,\n \"type\": \"other\",\n \"body\": \"Bumps the npm_and_yarn group with 7 updates in the / directory:\\n\\n| Package | From | To |\\n| --- | --- | --- |\\n| [@babel/helpers](https://github.com/babel/babel/tree/HEAD/packages/babel-helpers) | `7.26.0` | `7.27.1` |\\n| [@babel/runtime-corej\"\n },\n {\n \"title\": \"chore: 0.25.19 release\",\n \"prNumber\": 4501,\n \"type\": \"other\",\n \"body\": \"- #3741\\r\\n- #3762\\r\\n- #3748\\r\\n- #3747\\r\\n- #3751\\r\\n- #3749\\r\\n- #3746\\r\\n- #3763\\r\\n- #3764\\r\\n- #3772\\r\\n- #3768\\r\\n- #3769\\r\\n- #3778\\r\\n- #3792\\r\\n- #3788\\r\\n- #3793\\r\\n- #3796\\r\\n- #3422\\r\\n- #3458\\r\\n- #3658\\r\\n- #3583\\r\\n- #3790\\r\\n- #3329\\r\\n- #2876\\r\\n- #3809\\r\\n- #3906\\r\\n- #394\"\n },\n {\n \"title\": \"chore: clean eliza cache before running ci\",\n \"prNumber\": 4523,\n \"type\": \"refactor\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Improved reliability of CLI test workflow by clearing cached data before running tests.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Updated the Bun runtime version to ^1.2.13 across relevant configuration files to allow for minor and patch updates.\\n\\n<\"\n },\n {\n \"title\": \"📝 Add docstrings to `api-cleanup`\",\n \"prNumber\": 4521,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4519#issuecomment-2869040797\\n\\nThe following files were modified:\\n\\n* `packages/cli/src/server/api/agent.ts`\\n* `packages/client/src/components/app-sideb\"\n },\n {\n \"title\": \"docs: remove redundant word in solana-v2.md\",\n \"prNumber\": 4520,\n \"type\": \"docs\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added enhanced agent data fetching with the ability to\"\n },\n {\n \"title\": \"feat: add integration tests\",\n \"prNumber\": 4518,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added comprehensive integration tests for all major database operations, including agents, cache, components, emb\"\n },\n {\n \"title\": \"Shaw bugfixes\",\n \"prNumber\": 4515,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes some bugs. Leaving it on draft since it is complete and will need to be separated out.\"\n },\n {\n \"title\": \"fix: pglite migrations again\",\n \"prNumber\": 4532,\n \"type\": \"bugfix\",\n \"body\": \"fixes pglite migration paths\"\n },\n {\n \"title\": \"fix: remove migrations\",\n \"prNumber\": 4531,\n \"type\": \"bugfix\",\n \"body\": \"remove migrations; they are auto-generated and handled at code level\"\n },\n {\n \"title\": \"Disable loading instrumentation if not enabled.\",\n \"prNumber\": 4530,\n \"type\": \"other\",\n \"body\": \"This removes annoying instrumentation logs in startup.\\r\\n\\r\\n`@elizaos/the-org:dev: [2025-05-11 19:24:33] WARN: [getTracer] Service instrumentation not found in runtime.`\\r\\n\\r\\nNow it doesn't try and load the runtime, unless `process.env.INSTRUME\"\n },\n {\n \"title\": \"Enforce Typescript on /cli and /plugin-sql, fix missing DB functions.\",\n \"prNumber\": 4529,\n \"type\": \"bugfix\",\n \"body\": \"This PR:\\r\\n\\r\\n- Turns on `dts: true` in both CLI and plugin-sql packages.\\r\\n\\r\\n- This exposed missing: `connection` which was being used in tests but didn't actually exist.\\r\\n\\r\\n- Implemented `getConnection()` for realsies in DB adapters to satis\"\n },\n {\n \"title\": \"remove broken release link in changelog\",\n \"prNumber\": 4527,\n \"type\": \"other\",\n \"body\": \"Found a broken link to v0.25.6-alpha.1 release in docs/docs/changelog.md.\\r\\nReplaced the markdown link with plain text to avoid 404.\\r\\nFeel free to suggest a working link if available — happy to update!\\r\\n\"\n },\n {\n \"title\": \"chore: use newer bun setup\",\n \"prNumber\": 4526,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: Cleanup the-org ENV and Agent loading.\",\n \"prNumber\": 4524,\n \"type\": \"refactor\",\n \"body\": \"Some cleanups I did while QAing Jimmy PM agent.\\r\\n\\r\\nRewrites the `hasRequiredEnvVars` and Org agent loading process to be much simpler to read and fixes hard coded 6 count of agents.\\r\\n\\r\\nDoes same thing in 50% less code, we do not need to be \"\n },\n {\n \"title\": \"Fix broken Quickstart link\",\n \"prNumber\": 4555,\n \"type\": \"bugfix\",\n \"body\": \"Replaces outdated URL (elizaos.github.io/eliza/quickstart) with working https://eliza.how/docs/quickstart in README.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"feat: plugin-specification submodule\",\n \"prNumber\": 4553,\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\\nInclude the repo (via submodule) for plugin specification\\r\\nAlso removes hapi from autodoc\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\"\n },\n {\n \"title\": \"fix: build for plugin discord & service mess after merge conf\",\n \"prNumber\": 4552,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Bug Fixes**\\r\\n - Fixed critical issue within the `service.ts` (several methods missing after improper merge conflicts resolution) \"\n },\n {\n \"title\": \"Remove REST /ping for websocket status checks in client.\",\n \"prNumber\": 4551,\n \"type\": \"other\",\n \"body\": \"The /pings were kinda annoying log spam and were not perfectly realtime, like a 5 second lag on connect / reconnect.\\r\\nWe also didn't even have a proper /ping route, it was 404 and falling back to middleware btw.\\r\\n\\r\\nThis PR changes client fr\"\n },\n {\n \"title\": \"chore: consistent env naming for project manager agent\",\n \"prNumber\": 4549,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Activated support for the Anthropic plugin in the project manager character.\\n- **Chores**\\n - Updated the environ\"\n },\n {\n \"title\": \"fix: agent response + better logging/tracing in bootstrap plugin\",\n \"prNumber\": 4548,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n - Improved handling of undefined or missing properties in entity and room details to prevent potential errors and ensu\"\n },\n {\n \"title\": \"fix: bad env resolution\",\n \"prNumber\": 4547,\n \"type\": \"bugfix\",\n \"body\": \"fixes regression from merging bad PRs; env resolution is already handled by 'start.ts` in cli package\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed environmen\"\n },\n {\n \"title\": \"minor fix: remove banner display + have -h, --help show on same line\",\n \"prNumber\": 4546,\n \"type\": \"bugfix\",\n \"body\": \"**NO LOGIC OR FUNCTIONALITY CHANGES**\\r\\n\\r\\nin order to keep the cli helper text ux uniform and consistent, i made these two minor changes:\\r\\n\\r\\n- removed the displayBanner(), kinda random to show it in elizaos plugins -- this is mostly called d\"\n },\n {\n \"title\": \"fix(temp): passthrough function so that llm plugins dont break\",\n \"prNumber\": 4544,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"Update README_IND.md\",\n \"prNumber\": 4542,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#4336 \\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Tests**\\n - Updated test assertions to expect the `parse_mode` option as 'MarkdownV2' for message sending.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added s\"\n },\n {\n \"title\": \"Add README_MY.md \",\n \"prNumber\": 4567,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n\\t- Improved error handling and logging throughout the Telegram plugin to prevent crashes and provide clearer diagnostics\"\n },\n {\n \"title\": \"fix: community manager set to use plugin-local-ai, out of box\",\n \"prNumber\": 4557,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n#4336 \\r\\nThe reported error had several issues, I pushed a PR yesterday to address the OpenAI issue, now, I am pushing this PR to set the default settings for community manager (Eli5) in dev build, to work with local ai out of \"\n },\n {\n \"title\": \"feat: improve db api\",\n \"prNumber\": 4556,\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- getEntityById becomes getEntitesByIds (runtime still has a getEntityById helper/wrapper)\\r\\n- getRoom becomes getRoomsByIds (runtime still has a getRoom helper/wrapper)\\r\\n- batch \"\n },\n {\n \"title\": \"Fix outdated link in changelog.md\",\n \"prNumber\": 4576,\n \"type\": \"bugfix\",\n \"body\": \"The old link led to a 404 error (page not found).\\r\\nTo avoid confusion and broken navigation for readers, the link has been temporarily cleared.\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"chore: remove log spam during client build\",\n \"prNumber\": 4584,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\\"Screenshot\\r\\n\"\n },\n {\n \"title\": \"Eliza290/cli start command\",\n \"prNumber\": 4583,\n \"type\": \"other\",\n \"body\": \"ElizaOS CLI Start Command Improvements\\r\\n\\r\\n**Improved -chars option parsing**\\r\\nAdded support for handling of comma-separated values with spaces\\r\\nAdded support for both single and double quotes in character paths\\r\\nProperly strips quotes from \"\n },\n {\n \"title\": \"feat: add tests for create-eliza command\",\n \"prNumber\": 4582,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: scope worldId and entityId\",\n \"prNumber\": 4581,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n - Improved consistency in how knowledge items are associated with agents, ensuring uploaded knowledge is now correctly\"\n },\n {\n \"title\": \"fix: LLM response parsing to support custom fields and clean up empty message headers\",\n \"prNumber\": 4580,\n \"type\": \"bugfix\",\n \"body\": \"This PR addresses two issues:\\r\\n\\r\\n1. **Bootstrap plugin response parsing** \\r\\n Previously, the LLM response was reduced to a fixed set of keys, which discarded useful custom fields returned by custom templates. This change spreads all fiel\"\n },\n {\n \"title\": \"feat: better git repo plugin install support\",\n \"prNumber\": 4577,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added support for installing plugins directly from GitHub URLs, including both HTTPS and shorthand formats.\\n\\t- Enha\"\n },\n {\n \"title\": \"fix(core): fixing failling tests, adding missing packages and fixing circular dependency \",\n \"prNumber\": 4605,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Bug fix**\\r\\n - Added a list of relevant topics to the community manager and social media manager profiles as twitter post templa\"\n },\n {\n \"title\": \"fix: send-message-api\",\n \"prNumber\": 4594,\n \"type\": \"bugfix\",\n \"body\": \"# Release Notes\\r\\n\\r\\n## New Features\\r\\n- Enhanced message processing with an event-driven, asynchronous flow for agent message handling\\r\\n- Added support for new response scenarios where the agent may choose not to reply\\r\\n\\r\\n## Bug Fixes\\r\\n- Corr\"\n },\n {\n \"title\": \"wip: Plugin-Jupiter Swap\",\n \"prNumber\": 4593,\n \"type\": \"other\",\n \"body\": \"Added:\\r\\n\\r\\nPlugin-Jupiter which would be used to handle all jupiter swaps within plugin-trade and the Spartan product.\"\n },\n {\n \"title\": \"Eliza290/cli merge update cli into update command\",\n \"prNumber\": 4592,\n \"type\": \"other\",\n \"body\": \"# Consolidate `update-cli` command into `update` command\\r\\n\\r\\n## Problem\\r\\n- CLI update functionality was split between two commands (`update` and `update-cli`)\\r\\n- Installation instructions suggested incorrect command without the `@beta` tag\\r\\n\"\n },\n {\n \"title\": \"Eliza290/cli update command\",\n \"prNumber\": 4591,\n \"type\": \"other\",\n \"body\": \"# Improve ElizaOS CLI update command flags\\r\\n\\r\\nThis PR addresses several issues with the update command:\\r\\n\\r\\n## Regular no-flag update function\\r\\n- **Problem**: The regular update command was failing with error \\\"Invalid Version: beta\\\" when enc\"\n },\n {\n \"title\": \"fix: core not importable in client\",\n \"prNumber\": 4590,\n \"type\": \"bugfix\",\n \"body\": \"Fixes client error:\\r\\n\\r\\n```\\r\\nUncaught TypeError: Failed to resolve module specifier \\\"@elizaos/core\\\". Relative references must start with either \\\"/\\\", \\\"./\\\", or \\\"../\\\".\\r\\n```\\r\\n\\r\\nAlso adds vite-node-polyfills to supplement Buffer and process missi\"\n },\n {\n \"title\": \"fix: Guarantee onComplete is always called in messageReceivedHandler\",\n \"prNumber\": 4589,\n \"type\": \"bugfix\",\n \"body\": \"This PR ensures the onComplete callback is always executed, regardless of whether the message handler completes successfully, throws an error, or times out.\\r\\n\\r\\nKey changes:\\r\\n- Wrapped the entire messageReceivedHandler logic in a try-finally\"\n },\n {\n \"title\": \"chore: update docs\",\n \"prNumber\": 4586,\n \"type\": \"other\",\n \"body\": \"This PR focuses on a comprehensive update of the project's documentation.\\r\\n\\r\\nKey changes include:\\r\\n\\r\\n* **Content Updates:**\\r\\n * Updated blog posts.\\r\\n * Added brief versions of all partner documentation.\\r\\n * Added documentat\"\n },\n {\n \"title\": \"fix: resolve linter errors for type mismatches in DB adapter\",\n \"prNumber\": 4612,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n\\t- Improved handling of missing or null data for agent and task fields, ensuring consistent and user-friendly defaults ar\"\n },\n {\n \"title\": \"feat: add support for PDF rag\",\n \"prNumber\": 4611,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added support for extracting and uploading text content from PDF files, enabling users to upload PDFs as knowledg\"\n },\n {\n \"title\": \"Eliza290/cli command env\",\n \"prNumber\": 4610,\n \"type\": \"other\",\n \"body\": \"**elizaos env list:**\\r\\n\\r\\nAdded warning when no local .env file exists, with guidance to create one from .env.example if available\\r\\nAdded --system flag to show only system information, consistent with existing --global and --local flags\\r\\n\\r\\n*\"\n },\n {\n \"title\": \"fix: reply action to skip LLM call if existing REPLY response is found\",\n \"prNumber\": 4608,\n \"type\": \"bugfix\",\n \"body\": \"Previously, the REPLY action was designed to skip the LLM call if an existing response with a REPLY action was found. However, recent changes to the message handler's template prompt caused the LLM to return the response with the `text` fie\"\n },\n {\n \"title\": \"API - return ID of newly created agent\",\n \"prNumber\": 4634,\n \"type\": \"other\",\n \"body\": \"When using API calls and creating AGENT it very useful to have returned ID on first API call, so there are not needed subsequent calls after it just to find ID, which is crucial for other types of API calls.\\r\\n\\r\\nSo I added ID in return data \"\n },\n {\n \"title\": \"cleanup: optz actions functions\",\n \"prNumber\": 4633,\n \"type\": \"refactor\",\n \"body\": \"# PR: Optimize Action Formatting Functions\\r\\n\\r\\nThis PR improves the code quality and performance of the action formatting functions in `actions.ts`.\\r\\n\\r\\n## Changes Made\\r\\n\\r\\n### For all functions:\\r\\n- Added proper input validation for edge cases\"\n },\n {\n \"title\": \"ci: Docs auto deployer.\",\n \"prNumber\": 4631,\n \"type\": \"other\",\n \"body\": \"This runs Github Action if anything inside `packages/docs` folder changes and auto deploys to `docs.eliza.how`.\"\n },\n {\n \"title\": \"Fix chokidar watch usage\",\n \"prNumber\": 4629,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- add chokidar as a regular dependency for the CLI\\n- ensure chokidar is treated as external when bundling\\n- use the dependency directly in `dev` command\\n\\n## Testing\\n- ❌ `bun run test:setup-commands` *(failed to find `vitest` comm\"\n },\n {\n \"title\": \"chore: Remove unused wait helper\",\n \"prNumber\": 4625,\n \"type\": \"other\",\n \"body\": \"## Summary\\r\\n- remove wait helper from CLI start command\\r\\n\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Removed an unused utility function related to wait times fro\"\n },\n {\n \"title\": \"fix: client auth issue\",\n \"prNumber\": 4624,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Improved handling of unauthorized access: Users are now notified with a clear message and a visible alert if thei\"\n },\n {\n \"title\": \"feat: log time taken in tests\",\n \"prNumber\": 4621,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: add local ai tests\",\n \"prNumber\": 4619,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Improved workflow cache management to only clear necessary directories and added automatic model file downloads for test\"\n },\n {\n \"title\": \"Eliza290/cli command dev\",\n \"prNumber\": 4618,\n \"type\": \"other\",\n \"body\": \"This PR enhances the elizaos dev command with better character file handling while ensuring consistent behavior with start cli command\\r\\n\\r\\nAll options tested and passed:\\r\\n\\r\\n-c/--configure, \\r\\n-p/--port, \\r\\n-b/--build\\r\\n-char/--character\\r\\n\\r\\nKey \"\n },\n {\n \"title\": \"fix: senderName is \\\"Unknown\\\" in recentMessages provider\",\n \"prNumber\": 4616,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes an issue where the senderName was often displayed as \\\"Unknown\\\" in the recentMessages provider. The update changes the logic to prioritize entitiesData for resolving the sender's name based on entityId. If no match is found, it\"\n },\n {\n \"title\": \"chore: fix some typos in comment\",\n \"prNumber\": 4615,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Introduced a Retrieval-Augmented Generation (RAG) plugin, enabling advanced document ingestion and retrieval capa\"\n },\n {\n \"title\": \"chore: Add missing plugin failure test\",\n \"prNumber\": 4643,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- test plugin install modifies package.json with plugin-discord\\n- verify missing plugin fails with registry error\\n\\n## Testing\\n- `./run_all_bats.sh` *(fails: 'bats' not found in PATH)*\"\n },\n {\n \"title\": \"fix: agent start button refetch agent.status.\",\n \"prNumber\": 4642,\n \"type\": \"bugfix\",\n \"body\": \"When click: \\\"start\\\" on agents, it would start, but the UI would not update, until you refreshed page.\\r\\n\\r\\nNow it is realtime in the UI.\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/c876553f-6710-4345-8366-6fef52fb4418)\\r\\n\"\n },\n {\n \"title\": \"feat: use registry\",\n \"prNumber\": 4641,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: docs deploy workflow\",\n \"prNumber\": 4640,\n \"type\": \"bugfix\",\n \"body\": \"fixes npm cache since doesn't exist for docs package, removes PR runs, should only happen on pushes.\"\n },\n {\n \"title\": \"feat: allow world selection in message API\",\n \"prNumber\": 4637,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- add optional `worldId` query param for `/agents/:agentId/message`\\n- record `worldId` in created memories\\n- document new query parameter in OpenAPI & docs\\n\\n## Testing\\n- `bun test` *(fails: Cannot find module '@playwright/test')*\"\n },\n {\n \"title\": \"Merge addpolygon resolution\",\n \"prNumber\": 4636,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Featu\"\n },\n {\n \"title\": \"remove pr title CI\",\n \"prNumber\": 4644,\n \"type\": \"other\",\n \"body\": \"annoying imo, idc what name PR, should not fail CI, causes more failed looking PRs then needed.\"\n },\n {\n \"title\": \"add 30s timeout to registry parsing\",\n \"prNumber\": 4678,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: API get rooms per agent\",\n \"prNumber\": 4677,\n \"type\": \"feature\",\n \"body\": \"I wanted to get all the rooms where each agent is present, so to retrive that I added API endpoint which calls the function \\r\\n\\\"getRoomsForParticipant\\\" and retrives this to endpoint\\r\\n\\r\\n`curl -X GET http://localhost:3000/api/agents/b850bc30-4\"\n },\n {\n \"title\": \"bring back local ai test\",\n \"prNumber\": 4676,\n \"type\": \"tests\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: plugin-tee build and exports\",\n \"prNumber\": 4675,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n - Improved error handling to prevent runtime errors when message content is missing or incomplete.\\n - Enhanced error l\"\n },\n {\n \"title\": \"remove mock tests for cli\",\n \"prNumber\": 4674,\n \"type\": \"tests\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: update project starter character & fix path for core pckg\",\n \"prNumber\": 4671,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Eliza now responds helpfully and conversationally to a broader range of topics, including technology, business, cr\"\n },\n {\n \"title\": \"fix: shortcut reply only if no dynamic provider is present\",\n \"prNumber\": 4670,\n \"type\": \"bugfix\",\n \"body\": \"This PR updates the reply logic to only shortcut (reuse existing replies) when no dynamic providers are involved. It also fixes a bug where providers were incorrectly taken from the message instead of the response content.\"\n },\n {\n \"title\": \"remove plugin twitter\",\n \"prNumber\": 4669,\n \"type\": \"other\",\n \"body\": \"removes plugin twitter from mono repo has been moved to: https://github.com/elizaos-plugins/plugin-twitter\"\n },\n {\n \"title\": \"remove discord plugin\",\n \"prNumber\": 4668,\n \"type\": \"other\",\n \"body\": \"has been moved out to: https://github.com/elizaos-plugins/plugin-discord\"\n },\n {\n \"title\": \"feat: Create world api endpoints\",\n \"prNumber\": 4667,\n \"type\": \"feature\",\n \"body\": \" I wanted to create World with API endpoints, so I can have a consistent usage of a world.\\r\\n There wasnt any endpoints for this so I am adding them here. \\r\\n-To create new world\\r\\n-To update current one with new info\\r\\n-To get all rooms in cur\"\n },\n {\n \"title\": \"Remove global env support\",\n \"prNumber\": 4666,\n \"type\": \"other\",\n \"body\": \"## Summary\\n- drop global env logic from CLI and server\\n- update UI to only manage local envs\\n- rewrite docs about environment variables\\n- tweak plugin messages and runtime warnings\\n\\n## Testing\\n- `bun test` *(fails: Cannot find package 'dote\"\n },\n {\n \"title\": \"add CHANNEL_IDS to discord_plugin\",\n \"prNumber\": 4665,\n \"type\": \"feature\",\n \"body\": \"adds ENVs for CHANNEL_IDS so can limit the responses to certain channels\"\n },\n {\n \"title\": \"attempt dev command tear down\",\n \"prNumber\": 4664,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Environment and database configuration files are now stored within the project directory, ensuring localized setup fo\"\n },\n {\n \"title\": \"fix: make registry parsing direct executable + exportable\",\n \"prNumber\": 4694,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"deps: remove discord opus deps\",\n \"prNumber\": 4693,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: focused CLI testing\",\n \"prNumber\": 4692,\n \"type\": \"tests\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: Revert to using GH_PAT\",\n \"prNumber\": 4691,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: make autodoc run on v2-develop\",\n \"prNumber\": 4690,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat(client): move delete message button\",\n \"prNumber\": 4689,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- show copy/tts actions and delete in same row\\n- pass delete handler into `MessageContent`\\n- remove old delete button placement\\n\\n## Testing\\n- `bun run scripts/pre-commit-lint.js` *(fails: Script not found \\\"prettier\\\")*\\n- `bun test\"\n },\n {\n \"title\": \"fix: Eliza290/cli test command\",\n \"prNumber\": 4688,\n \"type\": \"bugfix\",\n \"body\": \"This PR comprehensively updates the ElizaOS test cli command to provide a more consistent and improved testing experience across both plugins and projects.\\r\\n\\r\\n**Key Changes**\\r\\n\\r\\n1. CLI Command Structure: Reorganized the test command with th\"\n },\n {\n \"title\": \"feat: add timeout to cli tests\",\n \"prNumber\": 4687,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: Unify env file lookup across CLI\",\n \"prNumber\": 4686,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- add `findNearestEnvFile` utility\\n- use the new helper throughout CLI commands and utils\\n\\n## Testing\\n- `bun test` *(fails: Cannot find module '@elizaos/core')*\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added support for viewing and filtering \\\"Transcription\\\" actions in the action viewer, including a new filter opti\"\n },\n {\n \"title\": \"fix: resolve character env loading, make the default character more c…\",\n \"prNumber\": 4716,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Updated Eliza character with refreshed descriptions, conversational examples, and style guidelines.\\n - Eliza now\"\n },\n {\n \"title\": \"fix docker voice\",\n \"prNumber\": 4715,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nFixes Docker deployments in TEE to ensure voice works correctly\\r\\n\\r\\nhttps://github.com/user-attachments/as\"\n },\n {\n \"title\": \"fix: cmd update to look for latest version spec by tag\",\n \"prNumber\": 4714,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"ops: deploy CLI action\",\n \"prNumber\": 4712,\n \"type\": \"other\",\n \"body\": \"github action to auto deploy the CLI package on changes and version bump\"\n },\n {\n \"title\": \"fix: CLI update, use beta versions if exact is not found\",\n \"prNumber\": 4711,\n \"type\": \"bugfix\",\n \"body\": \"```\\nError updating dependencies: Could not determine how to build the project\\nProject successfully updated to the latest ElizaOS packages\\n```\\n\\nIf deps install fails, we were still saying Success, because the try-catch scoping was not being \"\n },\n {\n \"title\": \"fix: CLI update, use beta versions if exact is not found\",\n \"prNumber\": 4710,\n \"type\": \"bugfix\",\n \"body\": \"```\\nelizaos update: looking for same match of versions on plugins that don't exist, we need to not hardcode versions, use latest:,\\nerror: No version matching \\\"1.0.0-beta.59\\\" found for specifier \\\"@elizaos/plugin-local-ai\\\" (but package exists\"\n },\n {\n \"title\": \"fix: filter for :user in client chat ignores\",\n \"prNumber\": 4709,\n \"type\": \"bugfix\",\n \"body\": \"`content: { text: 'hello', source: 'client_chat:user' }`\\n\\nIgnore was not being respected because client_chat gets `:user` appended to the string in CLI server handleSocket code.\\n\\nThis parses everything instead with includes.\\n\\n\"\n },\n {\n \"title\": \"fix: issue with create cmd and creating setup dirs\",\n \"prNumber\": 4708,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: updated text from eliza -> elizaos\",\n \"prNumber\": 4707,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nChanged text from eliza -> elizaos was making few users confuse when using cli\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://discord.com/channels/1051457140637827122/1323727516745334785/1375039664276377712\\r\\n![sdfasga](http\"\n },\n {\n \"title\": \"chore: centralise env resolution further\",\n \"prNumber\": 4705,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Introduced new utilities for resolving environment files and database directories, improving consistency across th\"\n },\n {\n \"title\": \"Add file TRANSLATION\",\n \"prNumber\": 4704,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Enhanced provider selection rules for message handling, ensuring more accurate responses based on message content\"\n },\n {\n \"title\": \"unpeg CLI plugin / core deps, version .71 deploy CLI\",\n \"prNumber\": 4747,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"Updated polygon plugin\",\n \"prNumber\": 4745,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Updated plugin behavior to ensure it is given lower priority compared to other plugins.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Introduced automatic generation of detailed descriptions for image attachments, including a concise title, summar\"\n },\n {\n \"title\": \"fix: remove tee plugin, bump packages\",\n \"prNumber\": 4753,\n \"type\": \"bugfix\",\n \"body\": \"removes tee-plugin from monorepo, syncs packages to latest tags\"\n },\n {\n \"title\": \"fix: .env hoisting in non-monorepo dirs\",\n \"prNumber\": 4752,\n \"type\": \"bugfix\",\n \"body\": \"Any .envs upper from the project directory would get grabbed, even not inside monorepos... now this forces .env creation and respects the project folder.\"\n },\n {\n \"title\": \"fixed: Undelegate Action\",\n \"prNumber\": 4771,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n