{ "date_generated_for": "2025-05-13", "ai_news_elizaos_discord_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# elizaOS Discord - 2025-05-12\n\n## Overall Discussion Highlights\n\n### Technical Issues & Development\n- **Knowledge Import Functionality**: Users reported that string-based knowledge imports work successfully, but file path and directory references fail despite setting `ragKnowledge: true` in the Eliza OS platform.\n- **Discord Integration Challenges**: Several users discussed difficulties with Discord plugin functionality, particularly getting proper @username mentions with notifications working correctly.\n- **Ollama Configuration**: Users discovered they need to explicitly add `@elizaos/plugins-ollama` to their character file rather than relying on environment variables alone to prevent unnecessary node-llama-cpp installation.\n- **Video Generation**: Videos generated by agents save to cache but may not display properly in the GUI, creating usability issues.\n- **Fee Collection Issue**: A technical issue with fee collection on auto.fun was reported and subsequently fixed by the team overnight.\n\n### Token Discussions\n- **Dood Token Distribution**: Discussions about eligibility for Dood tokens, with clarification that the Dood team airdropped to holders individually rather than through the elizaOS team directly.\n- **ELI5 Token Development**: Community members debated the potential of ELI5 as an AI education tool that could explain concepts simply to users, with proposals for community pages, Twitter accounts, and Reddit integration.\n- **Auto.fun Platform Strategy**: Ongoing discussion about auto.fun's positioning as an AI-focused launchpad with verified teams versus competitors, with suggestions to pivot toward being a launchpad for startups rather than memes.\n\n### Community Management\n- **Discord Scammer Report**: A user reported a Discord scammer, which was promptly addressed by a moderator.\n- **Channel Moderation**: Off-topic discussions about market conditions and cryptocurrency prices were redirected to appropriate channels by moderators.\n\n## Key Questions & Answers\n\n- **Q**: Why didn't I receive Dood tokens? (asked by sukrucildirr) \n **A**: \"If you haven't had any Dood sent you weren't eligible\" (answered by Kenk)\n\n- **Q**: How will Dood tokens be distributed without collecting addresses? (asked by sukrucildirr) \n **A**: \"The dood team airdropped our holders individually, not the team directly ser\" (answered by jasyn_bjorn)\n\n- **Q**: Where or what channel can we use to report discord scammer? (asked by Die Antwoord) \n **A**: \"Here\" (answered by Osint)\n\n- **Q**: Is \"@elizaos/plugin-direct\" deprecated? Can't understand why it's stopping character from loading. (asked by techcomthanh) \n **A**: \"You don't need that\" (answered by techcomthanh)\n\n- **Q**: Will there be a launch today? (asked by r) \n **A**: \"Nope no launch today\" (answered by noj)\n\n- **Q**: Is there a launch today? (asked by velja) \n **A**: \"No idea\" (answered by Kenk)\n\n## Community Help & Collaboration\n\n1. **Discord Scammer Report**\n - **Helper**: Osint (aka not_a_dev_ai)\n - **Helpee**: Die Antwoord\n - **Context**: Reporting a Discord scammer with user_id: 1331066099864829964\n - **Resolution**: \"Taken care of, thank you for the report\"\n\n2. **Ollama Configuration Support**\n - **Helper**: techcomthanh\n - **Helpee**: techcomthanh (self-help shared with community)\n - **Context**: Ollama configuration causing node-llama-cpp installation despite using remote resource\n - **Resolution**: Explained need to add `@elizaos/plugins-ollama` to character file in addition to environment variables\n\n3. **Fee Collection Issue Resolution**\n - **Helper**: Kenk\n - **Helpee**: gummy\n - **Context**: Issue with collecting fees on auto.fun\n - **Resolution**: Team pushed a fix overnight and confirmed it was working after user tested again\n\n4. **ELI5 Community Development**\n - **Helper**: gummy\n - **Helpee**: Community\n - **Context**: Proposing to create ELI5 community page and X communities\n - **Resolution**: Kenk approved the idea and gummy committed to setting up X communities\n\n## Action Items\n\n### Technical\n- Fix knowledge import functionality for file paths and directories in beta 49 (Mentioned by techcomthanh)\n- Fix Discord @username mentions to properly highlight and send notifications (Mentioned by techcomthanh)\n- Improve video display in GUI for videos generated by agents (Mentioned by techcomthanh)\n- Resolve issue with node-llama-cpp installation when using remote Ollama endpoint (Mentioned by techcomthanh)\n- Fix fee collection issue on auto.fun (Mentioned by Kenk)\n- Create ELI5 Twitter account that replies to questions with simple explanations (Mentioned by gummy)\n- Integrate ELI5 agent with Reddit community (Mentioned by ryanthelad)\n\n### Documentation\n- Provide sample files and code examples for knowledge import from files (Mentioned by techcomthanh)\n- Clarify Ollama plugin setup requirements in documentation (Mentioned by techcomthanh)\n- Document how to build tweet threads with agent-twitter-client repo (Mentioned by Bitcoin Broccoli)\n- Clarify Dood token distribution eligibility criteria (Mentioned by sukrucildirr)\n\n### Feature\n- Create ELI5 community page or main page (Mentioned by gummy)\n- Set up X communities for ELI5 (Mentioned by gummy)\n- Fix token locked chat for ELI5 on website (Mentioned by ryanthelad)\n- Pivot auto.fun to be leading launchpad for startups instead of memes (Mentioned by wire)" }, "ai_news_elizaos_discord_md_2025-05-11": { "filename": "2025-05-11.md", "content": "# elizaOS Discord - 2025-05-11\n\n## Overall Discussion Highlights\n\n### Development & Technical Issues\n- Several users reported issues with the Eliza agent setup, particularly around environment configuration and plugin integration\n- Problems with API connectivity in WSL2 were discussed, where Postman requests worked but backend-to-backend calls failed with 502 errors\n- Users encountered challenges with local AI models being downloaded despite environment settings to use external models\n- Plugin installation and build errors were reported, particularly with the Twitter plugin\n- Discord integration configuration problems were mentioned by multiple users\n\n### Community & Project Updates\n- The team is seeking beta testers for an unspecified project\n- Shaw mentioned challenges with collecting contributor wallet addresses for a potential airdrop\n- There's ongoing work on tooling to better collect contributor wallets in the future\n- A request for Rust developers was posted\n\n### Cryptocurrency Discussions\n- Users discussed price movements of tokens like COM and ELI5 on the auto.fun platform\n- COM reportedly reached all-time highs due to promotion by an influencer with 50,000 followers\n- Nick dask advised taking profits at the all-time high, warning about potential retracement\n- Discussion about a potential community meme launch on autofun, with wire offering to lead it with a team of artists\n- User \"gummy\" reported issues with claiming fees from dev wallet creation\n\n## Key Questions & Answers\n\n**Q: Any news about DOOD airdrop?** \nA: \"I have no idea about dood airdrop tbh\" (Osint) and \"i have no info on the airdrop though, sorry\" (shaw)\n\n**Q: How to install the new version of eliza on windows?** \nA: WSL is recommended (Deniz)\n\n**Q: How can I use LLM from OpenAI or grok instead of llama?** \nA: modelProvider is no longer used in newer versions, you need to set all required values in .env file and include the plugins in your characterfile (scooter8992)\n\n**Q: Does anyone know why COM is running?** \nA: Because a KOL (key opinion leader) with 50k followers called it. (Nick dask)\n\n**Q: Who is launching today?** \nA: It's the weekend. (Osint)\n\n## Community Help & Collaboration\n\n1. **Environment Configuration Help**\n - **Helper:** scooter8992\n - **Helpee:** pupathebig\n - **Context:** Twitter plugin not respecting TWITTER_DRY_RUN=true setting\n - **Resolution:** Suggested adding LOG_LEVEL=debug to .env and checking Discord gateway intents\n\n2. **Discord Integration Debugging**\n - **Helper:** scooter8992\n - **Helpee:** scooter8992\n - **Context:** Discord client not loading when agent starts\n - **Resolution:** Suggested adding runtime event listener code to debug Discord connection\n\n3. **Proper Configuration File Placement**\n - **Helper:** scooter8992\n - **Helpee:** scooter8992\n - **Context:** Proper .env file placement\n - **Resolution:** Clarified that .env should be in the root folder, which improved CLI output\n\n4. **Airdrop Wallet Collection Explanation**\n - **Helper:** shaw\n - **Helpee:** sukrucildirr\n - **Context:** Explaining the situation with wallet collection for airdrops\n - **Resolution:** Explained they asked for wallets last minute and are working on tooling for future wallet collection\n\n5. **Cryptocurrency Trading Advice**\n - **Helper:** Nick dask\n - **Helpee:** hxf\n - **Context:** hxf asked why COM token was running in price\n - **Resolution:** Nick explained it was due to a key opinion leader with 50k followers promoting it, and warned about potential manipulation due to 60% being held by one holder\n\n## Action Items\n\n### Technical\n- Fix Twitter plugin to properly respect TWITTER_DRY_RUN=true setting (mentioned by pupathebig)\n- Investigate 502 error when backend service calls Eliza API while Postman works (mentioned by scooter8992)\n- Fix issue with local models being downloaded despite configuration for external models (mentioned by scooter8992)\n- Fix plugin build error: \"Module '@elizaos/core-plugin-v1' has no exported member 'Plugin'\" (mentioned by pupathebig)\n- Fix issue with claiming fees from dev wallet creation (mentioned by gummy)\n- Working on tooling to collect contributor wallets (mentioned by shaw)\n\n### Documentation\n- Create guide for proper environment configuration to use external models instead of local ones (mentioned by scooter8992)\n- Document global configuration file location and purpose (mentioned by scooter8992)\n\n### Feature\n- Implement option to restrict Twitter bot to only post and reply to tagged messages (mentioned by Sthx)\n- Beta testers recruitment for an unspecified project (mentioned by Blazo101)\n- Organize a community meme launch on autofun with a team of artists (mentioned by wire)" }, "ai_news_elizaos_discord_md_2025-05-10": { "filename": "2025-05-10.md", "content": "# elizaOS Discord - 2025-05-10\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Development Status\n- **Beta Status**: ElizaOS v2 is currently in beta and in developers' hands\n- **Release Timeline**: No hard deadline set; will be shipped \"when it's ready\"\n- **New Features**: Agents can now have custom tabs for plugins\n- **MCP Integration**: Three Multi-Chain Protocol plugins are currently on the development radar\n\n### Technical Implementation Challenges\n- **Local AI Integration**: Multiple users reported configuration issues with Ollama and LM Studio in the v2 beta\n- **Plugin Architecture**: Ollama support has been moved to a dedicated plugin requiring specific environment variables\n- **Text Embedding Limitations**: Current implementation may require OpenAI despite attempts to use alternatives like Ollama or Anthropic\n\n### Governance Evolution\n- Moving away from traditional DAO structures toward a new approach with ElizaOS at its core\n- Developing \"soft governance\" concepts (non on-chain voting) as an alternative model\n- Potential to create a governance blueprint for other projects\n\n## Key Questions & Answers\n\n### ElizaOS v2 Features & Timeline\n- **Q**: When is v2 coming? \n **A**: \"Thoon\" - The beta is in developers' hands with no hard deadline, will ship when ready\n\n- **Q**: Any MCP vision for ElizaOS? \n **A**: \"There's 3 MCP plugins on my radar at the moment\"\n\n- **Q**: What is ai16z soft governance? \n **A**: Non on-chain voting and beginning of engagement around governance, rethinking traditional DAO approaches\n\n### Technical Configuration\n- **Q**: How do I configure local Ollama models in ElizaOS beta? \n **A**: You need to use the dedicated Ollama plugin with specific environment variables like OLLAMA_API_ENDPOINT, OLLAMA_SMALL_MODEL, etc.\n\n- **Q**: What's causing the \"StudioLM text generation error: fetch failed\" with LM Studio? \n **A**: Make sure the models are available in LM Studio\n\n- **Q**: How can I set up ElizaOS v2 to not respond to everything on Twitter/X and only reply when tagged? \n **A**: Changing your character name might help as it can be confusing to LLM, and adding action examples in your configuration\n\n## Community Help & Collaboration\n\n### Local AI Model Integration\n- **bob_the_spounge** helped **Void** with configuring Ollama with ElizaOS beta by providing the correct environment variable format and explaining that Ollama was moved to its own plugin\n- **bob_the_spounge** assisted **Sthx** with Twitter/X integration issues, suggesting configuration changes to avoid spam detection and bans\n\n### Development Support\n- **Patt** and **Kenk** directed **Void** to appropriate resources for launching a local Eliza agent, pointing to the #dev-support channel for technical assistance\n- **bob_the_spounge** shared troubleshooting steps for LM Studio errors, suggesting to check if models are properly available\n\n## Action Items\n\n### Technical\n- Install Ollama plugin separately with \"elizaos create\" then add plugin to character configuration (mentioned by bob_the_spounge)\n- Configure Ollama environment variables correctly (OLLAMA_API_ENDPOINT, OLLAMA_SMALL_MODEL, etc.) (mentioned by bob_the_spounge)\n- Ensure models are available in LM Studio before attempting to use them (mentioned by bob_the_spounge)\n- Implement custom tabs for plugins in agents (mentioned by shaw)\n- Develop and integrate MCP plugins (3 mentioned) (mentioned by Kenk)\n\n### Documentation\n- Document the proper way to install and configure the Ollama plugin (mentioned by bob_the_spounge)\n- Provide guidance for launching local Eliza agents (mentioned by Void)\n\n### Feature\n- Develop ElizaOS v2 with improved capabilities (mentioned by multiple users)\n- Create new governance model as alternative to traditional DAOs with ElizaOS at core (mentioned by Kenk)\n- Support text embedding with providers other than OpenAI (mentioned by bob_the_spounge)\n- Creation of a crypto-western cyberpunk story experience in Hyperfy with locations like Degen Bar, Rugpull Hill, and Rugpull County Jail (mentioned by Dr. Neuro)" }, "ai_news_elizaos_dev_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# elizaOS Development Discord - 2025-05-12\n\n## Overall Discussion Highlights\n\n### Character Configuration & Development\n- Discussion about referencing one character file from another (e.g., importing woman.character.json into eliza.character.json)\n- Detailed troubleshooting of character.json configuration issues in v2, including voice settings and knowledge directory paths\n- Recommendation to keep a minimal approach when starting with character configurations before adding complexity\n\n### Tools & Integrations\n- Interest in news integration capabilities for agents, with suggestion to build an RSS plugin\n- Introduction of Screenpipe (https://screenpi.pe/), a tool for recording screen activity that can be used for AI training\n- Discussion about potential plugin development for Screenpipe\n\n### System Architecture & Security\n- Emphasis on proper credential management, keeping sensitive information in .env files rather than character configurations\n- Clarification on the differences between CLI and manual workflows in v2, noting that CLI has its own mental model\n\n## Key Questions & Answers\n\n**Q: Has anyone done something like have a main character file reference/import another character file?** \nA: Self-answered that it would require modifying the runtime that reads the JSON files (DorianD)\n\n**Q: Is there a plugin to get the latest news and add it as knowledge into the agent? Like News API connection?** \nA: Build an RSS plugin (sayonara)\n\n**Q: Does anyone have a link to the online Eliza Helper Bot interface?** \nA: The helper bot interface was deprecated a while back - the new v2 workflow is more flexible but has a steeper learning curve. (Ruby)\n\n**Q: Why doesn't the template include info for the OpenAI key? What LLM backend would it use?** \nA: The OpenAI key and LLM settings go in your .env file or environment variables. The default backend is gpt-4 but you can override that in your project's main config. (Ruby)\n\n**Q: Should the Supabase keys also be put into the .env file and kept out of the character JSON? What's the format?** \nA: Yes! Definitely keep those keys in .env - never in the character json. The format is simple: SUPABASE_URL=your_url_here SUPABASE_ANON_KEY=your_key_here (Ruby)\n\n## Community Help & Collaboration\n\n- **Ruby helped Hidden Forces** with character.json configuration issues, providing a simplified template and explaining the proper way to manage credentials\n- **Ruby clarified** the conceptual differences between CLI and manual workflows in v2, explaining that CLI isn't just an automated version of manual steps\n- **sayonara suggested** building an RSS plugin to Titan who was looking for news integration capabilities\n- **Terexitarius shared** Screenpipe tool with the community, suggesting it might be useful for personal knowledge management and AI training\n\n## Action Items\n\n### Technical\n- Build an RSS plugin for news integration with agents (mentioned by sayonara)\n- Fix character.json configuration issues including voice model/url values and knowledge directory path (mentioned by Ruby)\n- Address privacy concerns in screen recording with selective capture or data retention policies for Screenpipe (mentioned by Ruby)\n- Potential EVM chains support for an unspecified project (mentioned by Terexitarius)\n\n### Documentation\n- Improve documentation on differences between manual work and CLI in v2 (mentioned by Hidden Forces)\n- Create a guide on key differences between CLI and manual approaches (mentioned by Ruby)\n\n### Feature\n- Character file import system to allow referencing one character file from another (mentioned by DorianD)\n- News integration plugin to get latest news and add it as knowledge into agents (mentioned by Titan)\n- Potential Screenpipe plugin development for the screen recording tool (mentioned by Terexitarius)" }, "ai_news_elizaos_dev_md_2025-05-11": { "filename": "2025-05-11.md", "content": "# elizaOS Development Discord - 2025-05-11\n\n## Overall Discussion Highlights\n\n### Project Announcements\n- User **joaointech** shared their website project called **plinkoincinerator.com** and requested community feedback.\n\n### AI Agent Development\n- Discussion about the **AI Agent Dev School v2** content by Shaw\n- Clarification that the current available video (approximately 1 hour 15 minutes) only covers CLI basics\n- Information that advanced topics like memory systems, multi-agent architectures, and custom plugins are still in development\n- Recommendation to use the **#agent-dev** channel for discussions on advanced features like memory implementations while waiting for official content\n\n## Key Questions & Answers\n\n### AI Agent Dev School Content\n**Q:** Is there only one AI Agent Dev School for v2 by Shaw? \n**A:** Yes, currently there's just one official dev school program by Shaw, though it's still in development. (answered by Ruby)\n\n**Q:** Are you referring to the new AI Agent Dev School video that's about an hour and 15 minutes long? \n**A:** Yes, the current video only covers CLI basics, with advanced topics coming soon. (answered by Ruby)\n\n## Community Help & Collaboration\n\n### Agent Development Resources\n- **Ruby** helped **ualp.** by clarifying the status of AI Agent Dev School content and suggesting alternative resources\n- Ruby recommended using the Discord's **#agent-dev** channel for discussions on memory implementations while waiting for the full curriculum\n\n## Action Items\n\n### Technical\n- **Community feedback needed:** for plinkoincinerator.com website (Mentioned by joaointech)\n\n### Documentation\n- **Advanced curriculum:** covering memory systems, multi-agent architectures, and custom plugins (Mentioned by Ruby)\n\n### Feature\n- **Release of advanced AI Agent Dev School content:** beyond CLI basics (Mentioned by Ruby)" }, "ai_news_elizaos_dev_md_2025-05-10": { "filename": "2025-05-10.md", "content": "# elizaOS Development Discord - 2025-05-10\n\n## Overall Discussion Highlights\n\n### Plugin Development Issues\n- User **lantianlaoli** reported issues with their custom plugin \"quokkaStep\" that builds on Raydium\n- The plugin is failing to recognize specific actions like \"GENERATE_RAYDIUM_CLMM_CONFIG\" and defaulting to \"CONTINUE\" action\n- The plugin previously worked with OpenRouter but is experiencing issues after switching to the Gemini model\n\n### Documentation Systems\n- **Shaw** mentioned the project has an autodoc package that generates documentation automatically in CI\n- Documentation approach includes a mix of hand-written docs and AI-generated content to fill gaps\n\n## Key Questions & Answers\nNo resolved questions were reported in today's discussions.\n\n## Community Help & Collaboration\n- **Kenk** assisted **lantianlaoli** with Eliza agent configuration issues by directing them to www.eliza.how for further assistance\n\n## Action Items\n\n### Technical\n- Investigate why custom action \"GENERATE_RAYDIUM_CLMM_CONFIG\" is being interpreted as \"CONTINUE\" after switching from OpenRouter to Gemini (Mentioned by: lantianlaoli)\n\n### Documentation\n- Check autodoc package for documentation generation (Mentioned by: Shaw)" }, "ai_news_elizaos_daily_json_2025-05-12": { "filename": "2025-05-12.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-12", "categories": [ { "title": "Summary for completed_items", "content": [ { "text": "Recent GitHub pull requests for the elizaOS/eliza repository include several bugfixes, features, and other improvements:\n\nBugfixes:\n- Fixed agent response and improved logging/tracing in bootstrap plugin (#4548)\n- Fixed bad environment resolution (#4547)\n- Removed banner display and improved help command formatting (#4546)\n- Added passthrough function to prevent LLM plugins from breaking (#4544)\n- Fixed integration test import (#4541)\n- Fixed error related to TEXT_EMBEDDING issue #4336 (#4537)\n- Fixed build for Discord plugin and service after merge conflict (#4552)\n- Updated TEE for CI (#4572)\n- Updated Telegram messageManager tests to expect MarkdownV2 (#4570)\n\nFeatures:\n- Added commit SHA to CLI cache action (#4571)\n- Added support for third-party plugin installation with tests (#4568)\n- Upgraded CLI agent command (#4560)\n\nOther improvements:\n- Made environment naming consistent for project manager agent (#4549)\n- Removed REST /ping for websocket status checks in client (#4551)\n- Reverted to regular dev command (#4566)\n- Updated to use latest v2 plugin list (#4564)\n- Enabled strict types and adjusted guards for plugin-telegram (#4559)", "sources": [ "https://github.com/elizaOS/eliza/pull/4549", "https://github.com/elizaOS/eliza/pull/4548", "https://github.com/elizaOS/eliza/pull/4547", "https://github.com/elizaOS/eliza/pull/4546", "https://github.com/elizaOS/eliza/pull/4544", "https://github.com/elizaOS/eliza/pull/4541", "https://github.com/elizaOS/eliza/pull/4537", "https://github.com/elizaOS/eliza/pull/4552", "https://github.com/elizaOS/eliza/pull/4551", "https://github.com/elizaOS/eliza/pull/4572", "https://github.com/elizaOS/eliza/pull/4571", "https://github.com/elizaOS/eliza/pull/4570", "https://github.com/elizaOS/eliza/pull/4568", "https://github.com/elizaOS/eliza/pull/4566", "https://github.com/elizaOS/eliza/pull/4564", "https://github.com/elizaOS/eliza/pull/4560", "https://github.com/elizaOS/eliza/pull/4559" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Recent pull requests in the elizaOS/eliza repository include several feature additions and bug fixes. PR #4554 by 0xbbjoker adds MySQL support to the degen feature. User yungalgo has submitted multiple PRs (#4535, #4538, and #4543) related to ELIZA290/part-2 plugins agent CLI commands. PR #4573 by Samarthsinghal28 adds a Polygon Plugin, while PR #4574 by Y4NK33420 implements Polygon Gas Oracle Integration. Bug fixes include PR #4552 by 0xbbjoker addressing build issues for plugin discord and service mess after merge conflicts, and PR #4558 by ChristopherTrimboli fixing the Create room API. Additionally, PR #4575 by HarshModi2005 addresses Issue 451.", "sources": [ "https://github.com/elizaOS/eliza/pull/4554", "https://github.com/elizaOS/eliza/pull/4538", "https://github.com/elizaOS/eliza/pull/4535", "https://github.com/elizaOS/eliza/pull/4543", "https://github.com/elizaOS/eliza/pull/4573", "https://github.com/elizaOS/eliza/pull/4575", "https://github.com/elizaOS/eliza/pull/4552", "https://github.com/elizaOS/eliza/pull/4574", "https://github.com/elizaOS/eliza/pull/4558" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4554", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4538", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4535", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4543", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4573", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4575", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4552", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4574", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4558" ], "videos": [] } ], "topic": "pull_request" }, { "title": "Issues for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Four issues have been reported in the elizaOS/eliza repository. Issue #4536 reports a module resolution problem where the system cannot find the '@elizaos/core' module or its type declarations. Issue #4562 requests publishing the package to npm. Issue #4561 reports an error from CI activity. Issue #4565 indicates a missing path issue related to 'packages/docs/i18n/readme/'.", "sources": [ "https://github.com/elizaOS/eliza/issues/4536", "https://github.com/elizaOS/eliza/issues/4562", "https://github.com/elizaOS/eliza/issues/4561", "https://github.com/elizaOS/eliza/issues/4565" ], "images": [], "videos": [] } ], "topic": "issue" }, { "title": "Summary for github_summary", "content": [ { "text": "The elizaos/eliza repository showed continued development activity over a two-day period. From May 12-13, 2025, there were 20 new pull requests with 7 merged, 1 new issue, and 11 active contributors. The following day (May 13-14, 2025), activity remained strong with 16 new pull requests (10 merged), 3 new issues, and an increased contributor count of 17 active participants.", "sources": [], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Summary for github_other", "content": [ { "text": "The sources provide information about the top contributors for the GitHub repository elizaOS/eliza. However, both sources appear to be identical and contain only the heading 'Top contributors for elizaOS/eliza' without listing any specific contributors or additional details.", "sources": [], "images": [], "videos": [] } ], "topic": "github_other" } ], "date": 1747008000 } }, "ai_news_elizaos_daily_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# Daily Report - 2025-05-12\n\n## GitHub Activity for elizaOS/eliza\n\n### Completed Items\n- **Bugfixes:**\n - Fixed agent response and improved logging/tracing in bootstrap plugin (#4548)\n - Fixed bad environment resolution (#4547)\n - Removed banner display and improved help command formatting (#4546)\n - Added passthrough function to prevent LLM plugins from breaking (#4544)\n - Fixed integration test import (#4541)\n - Fixed error related to TEXT_EMBEDDING issue #4336 (#4537)\n - Fixed build for Discord plugin and service after merge conflict (#4552)\n - Updated TEE for CI (#4572)\n - Updated Telegram messageManager tests to expect MarkdownV2 (#4570)\n- **Features:**\n - Added commit SHA to CLI cache action (#4571)\n - Added support for third-party plugin installation with tests (#4568)\n - Upgraded CLI agent command (#4560)\n- **Other improvements:**\n - Made environment naming consistent for project manager agent (#4549)\n - Removed REST /ping for websocket status checks in client (#4551)\n - Reverted to regular dev command (#4566)\n - Updated to use latest v2 plugin list (#4564)\n - Enabled strict types and adjusted guards for plugin-telegram (#4559)\n- Sources: https://github.com/elizaOS/eliza/pull/4549, https://github.com/elizaOS/eliza/pull/4548, https://github.com/elizaOS/eliza/pull/4547, https://github.com/elizaOS/eliza/pull/4546, https://github.com/elizaOS/eliza/pull/4544, https://github.com/elizaOS/eliza/pull/4541, https://github.com/elizaOS/eliza/pull/4537, https://github.com/elizaOS/eliza/pull/4552, https://github.com/elizaOS/eliza/pull/4551, https://github.com/elizaOS/eliza/pull/4572, https://github.com/elizaOS/eliza/pull/4571, https://github.com/elizaOS/eliza/pull/4570, https://github.com/elizaOS/eliza/pull/4568, https://github.com/elizaOS/eliza/pull/4566, https://github.com/elizaOS/eliza/pull/4564, https://github.com/elizaOS/eliza/pull/4560, https://github.com/elizaOS/eliza/pull/4559\n\n### Pull Requests\n- 0xbbjoker added MySQL support to the degen feature (#4554)\n- yungalgo submitted multiple PRs (#4535, #4538, #4543) related to ELIZA290/part-2 plugins agent CLI commands\n- Samarthsinghal28 added a Polygon Plugin (#4573)\n- Y4NK33420 implemented Polygon Gas Oracle Integration (#4574)\n- 0xbbjoker addressed build issues for plugin discord and service after merge conflicts (#4552)\n- ChristopherTrimboli fixed the Create room API (#4558)\n- HarshModi2005 addressed Issue 451 (#4575)\n- Sources: https://github.com/elizaOS/eliza/pull/4554, https://github.com/elizaOS/eliza/pull/4538, https://github.com/elizaOS/eliza/pull/4535, https://github.com/elizaOS/eliza/pull/4543, https://github.com/elizaOS/eliza/pull/4573, https://github.com/elizaOS/eliza/pull/4575, https://github.com/elizaOS/eliza/pull/4552, https://github.com/elizaOS/eliza/pull/4574, https://github.com/elizaOS/eliza/pull/4558\n\n### Issues\n- Module resolution problem reported where the system cannot find the '@elizaos/core' module or its type declarations (#4536)\n- Request to publish the package to npm (#4562)\n- Error reported from CI activity (#4561)\n- Missing path issue related to 'packages/docs/i18n/readme/' (#4565)\n- Sources: https://github.com/elizaOS/eliza/issues/4536, https://github.com/elizaOS/eliza/issues/4562, https://github.com/elizaOS/eliza/issues/4561, https://github.com/elizaOS/eliza/issues/4565\n\n## GitHub Summary\n- May 12-13, 2025: 20 new pull requests with 7 merged, 1 new issue, and 11 active contributors\n- May 13-14, 2025: 16 new pull requests with 10 merged, 3 new issues, and 17 active contributors\n\n## GitHub Other\n- Information about top contributors was mentioned but no specific contributors were listed" }, "ai_news_elizaos_daily_discord_json_2025-05-12": { "filename": "2025-05-12.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-12", "date": 1747008000, "stats": { "totalMessages": 224, "totalUsers": 36 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThis Discord chat segment in the \"discussion\" channel contains minimal technical content. The conversation primarily revolves around token distributions, particularly regarding \"Dood\" tokens, with some users expressing concerns about eligibility and distribution methods. There's a dispute between user sukrucildirr and team members (including Kenk) about the distribution process, with sukrucildirr claiming the team didn't properly collect addresses for distribution. Team member jasyn_bjorn clarifies that the Dood team airdropped to holders individually rather than through the team directly. The chat also includes some off-topic discussion about market conditions and cryptocurrency prices, which moderators redirect to appropriate channels. A user reports a Discord scammer, which is promptly addressed by a moderator. Overall, the chat lacks substantive technical discussions or problem-solving content.\n\n## 2. FAQ\nQ: Where or what channel can we use to report discord scammer? (asked by Die Antwoord) A: \"here\" (answered by Osint (aka not_a_dev_ai))\nQ: Why didn't I receive Dood tokens? (asked by sukrucildirr) A: \"if you haven't had any Dood sent you weren't eligible\" (answered by Kenk)\nQ: How will Dood tokens be distributed without collecting addresses? (asked by sukrucildirr) A: \"the dood team airdropped our holders individually, not the team directly ser\" (answered by jasyn_bjorn)\n\n## 3. Help Interactions\nHelper: Osint (aka not_a_dev_ai) | Helpee: Die Antwoord | Context: Reporting a Discord scammer with user_id: 1331066099864829964 | Resolution: \"taken care of, thank you for the report\"\nHelper: Osint (aka not_a_dev_ai) | Helpee: abhi_ironman | Context: Redirecting price discussion to appropriate channel | Resolution: Informed user to move discussion to #1299989396874854440\n\n## 4. Action Items\nTechnical: None identified in this chat segment\nDocumentation: Description: Clarify Dood token distribution eligibility criteria | Mentioned By: sukrucildirr\nFeature: None identified in this chat segment", "messageCount": 60, "userCount": 12 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around technical issues with the Eliza OS platform, focusing on knowledge configuration, plugins, and Discord integration. A key discussion centers on knowledge import functionality, where users report that string-based knowledge imports work successfully, but file path and directory references fail despite setting `ragKnowledge: true`. Another significant topic involves Discord plugin functionality, particularly the challenge of getting proper @username mentions with notifications working. Users also discussed video generation plugins, noting that videos save to cache but may not display properly in the GUI. There were configuration questions about Ollama integration, with users discovering they need to explicitly add the `@elizaos/plugins-ollama` to their character file rather than relying on environment variables alone. Other minor discussions included model selection, hosting recommendations, and issues with OpenAI API key validation.\n\n## 2. FAQ:\nQ: How to get agent to respond to users on discord with @username in response? (asked by techcomthanh) A: Unanswered\nQ: Are videos displayed correctly with a player or is the GUI not able to display the videos generated by the agents? (asked by techcomthanh) A: Unanswered\nQ: Is there a specific Oauth2 perm I need to enable that let's the discord plugin work as intended with respect to @username mentions? (asked by techcomthanh) A: Unanswered\nQ: What do you recommend for hosting a xAI agent? VPS or dedicated Video Card? (asked by techcomthanh) A: Unanswered\nQ: Is \"@elizaos/plugin-direct\" deprecated? Can't understand why it's stopping character from loading. (asked by techcomthanh) A: You don't need that (answered by techcomthanh)\nQ: I use nanoGPT. Is there an easy way to override OpenAI API key validation failure? (asked by techcomthanh) A: Unanswered\nQ: How does one build a thread of tweets using the agent-twitter-client repo? (asked by Bitcoin Broccoli) A: Unanswered\n\n## 3. Help Interactions:\nHelper: techcomthanh | Helpee: techcomthanh | Context: Ollama configuration causing node-llama-cpp installation despite using remote resource | Resolution: Explained need to add `@elizaos/plugins-ollama` to character file in addition to environment variables\nHelper: techcomthanh | Helpee: techcomthanh | Context: Confusion about plugin-direct causing character loading issues | Resolution: Advised that the plugin is not needed and can be deleted from characterJSON\n\n## 4. Action Items:\nTechnical: Fix knowledge import functionality for file paths and directories in beta 49 | Mentioned By: techcomthanh\nTechnical: Fix Discord @username mentions to properly highlight and send notifications | Mentioned By: techcomthanh\nTechnical: Improve video display in GUI for videos generated by agents | Mentioned By: techcomthanh\nTechnical: Resolve issue with node-llama-cpp installation when using remote Ollama endpoint | Mentioned By: techcomthanh\nDocumentation: Provide sample files and code examples for knowledge import from files | Mentioned By: techcomthanh\nDocumentation: Clarify Ollama plugin setup requirements in documentation | Mentioned By: techcomthanh\nDocumentation: Document how to build tweet threads with agent-twitter-client repo | Mentioned By: Bitcoin Broccoli", "messageCount": 41, "userCount": 4 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Analysis of \"fun\" Discord Channel\n\n## 1. Summary\nThe channel primarily discusses AI-related tokens on the auto.fun platform, with particular focus on ELI5 token. Community members debate the potential of ELI5 as an AI education tool that could explain concepts simply to users. There's discussion about creating community pages, Twitter accounts, and Reddit integration for ELI5 to increase adoption. Some users express frustration about auto.fun's performance compared to other launchpads like pump.fun and bonk.fun. A technical issue with fee collection was reported and subsequently fixed by the team. There's ongoing discussion about auto.fun's positioning as an AI-focused launchpad with verified teams versus competitors, with suggestions that it should pivot toward being a launchpad for startups rather than memes.\n\n## 2. FAQ\nQ: What is launching tomorrow on auto fun? (asked by Kicale) A: Unanswered\nQ: How do I get autofun enjoyer? (asked by Void) A: Unanswered\nQ: When xfractal and memerepublic? (asked by Remyy) A: Unanswered\nQ: Will there be a launch today? (asked by velja) A: \"No idea\" (answered by Kenk)\nQ: Is there a launch today? (asked by r) A: \"Nope no launch today\" (answered by noj)\nQ: Are we expecting a launch today? (asked by vas) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: gummy | Context: Issue with collecting fees | Resolution: Team pushed a fix overnight and confirmed it was working after user tested again\nHelper: gummy | Helpee: Community | Context: Proposing to create ELI5 community page and X communities | Resolution: Kenk approved the idea and gummy committed to setting up X communities\nHelper: ryanthelad | Helpee: Community | Context: Reported token locked chat for ELI5 not working on website | Resolution: Mentioned as a potential place to strategize, but no direct fix confirmed\n\n## 4. Action Items\nType: Technical | Description: Fix fee collection issue | Mentioned By: Kenk\nType: Technical | Description: Create ELI5 Twitter account that replies to questions with simple explanations | Mentioned By: gummy\nType: Technical | Description: Integrate ELI5 agent with Reddit community | Mentioned By: ryanthelad\nType: Feature | Description: Create ELI5 community page or main page | Mentioned By: gummy\nType: Feature | Description: Set up X communities for ELI5 | Mentioned By: gummy\nType: Feature | Description: Fix token locked chat for ELI5 on website | Mentioned By: ryanthelad\nType: Feature | Description: Pivot auto.fun to be leading launchpad for startups instead of memes | Mentioned By: wire", "messageCount": 123, "userCount": 21 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# elizaOS Discord - 2025-05-12\n\n## Overall Discussion Highlights\n\n### Technical Issues & Development\n- **Knowledge Import Functionality**: Users reported that string-based knowledge imports work successfully, but file path and directory references fail despite setting `ragKnowledge: true` in the Eliza OS platform.\n- **Discord Integration Challenges**: Several users discussed difficulties with Discord plugin functionality, particularly getting proper @username mentions with notifications working correctly.\n- **Ollama Configuration**: Users discovered they need to explicitly add `@elizaos/plugins-ollama` to their character file rather than relying on environment variables alone to prevent unnecessary node-llama-cpp installation.\n- **Video Generation**: Videos generated by agents save to cache but may not display properly in the GUI, creating usability issues.\n- **Fee Collection Issue**: A technical issue with fee collection on auto.fun was reported and subsequently fixed by the team overnight.\n\n### Token Discussions\n- **Dood Token Distribution**: Discussions about eligibility for Dood tokens, with clarification that the Dood team airdropped to holders individually rather than through the elizaOS team directly.\n- **ELI5 Token Development**: Community members debated the potential of ELI5 as an AI education tool that could explain concepts simply to users, with proposals for community pages, Twitter accounts, and Reddit integration.\n- **Auto.fun Platform Strategy**: Ongoing discussion about auto.fun's positioning as an AI-focused launchpad with verified teams versus competitors, with suggestions to pivot toward being a launchpad for startups rather than memes.\n\n### Community Management\n- **Discord Scammer Report**: A user reported a Discord scammer, which was promptly addressed by a moderator.\n- **Channel Moderation**: Off-topic discussions about market conditions and cryptocurrency prices were redirected to appropriate channels by moderators.\n\n## Key Questions & Answers\n\n- **Q**: Why didn't I receive Dood tokens? (asked by sukrucildirr) \n **A**: \"If you haven't had any Dood sent you weren't eligible\" (answered by Kenk)\n\n- **Q**: How will Dood tokens be distributed without collecting addresses? (asked by sukrucildirr) \n **A**: \"The dood team airdropped our holders individually, not the team directly ser\" (answered by jasyn_bjorn)\n\n- **Q**: Where or what channel can we use to report discord scammer? (asked by Die Antwoord) \n **A**: \"Here\" (answered by Osint)\n\n- **Q**: Is \"@elizaos/plugin-direct\" deprecated? Can't understand why it's stopping character from loading. (asked by techcomthanh) \n **A**: \"You don't need that\" (answered by techcomthanh)\n\n- **Q**: Will there be a launch today? (asked by r) \n **A**: \"Nope no launch today\" (answered by noj)\n\n- **Q**: Is there a launch today? (asked by velja) \n **A**: \"No idea\" (answered by Kenk)\n\n## Community Help & Collaboration\n\n1. **Discord Scammer Report**\n - **Helper**: Osint (aka not_a_dev_ai)\n - **Helpee**: Die Antwoord\n - **Context**: Reporting a Discord scammer with user_id: 1331066099864829964\n - **Resolution**: \"Taken care of, thank you for the report\"\n\n2. **Ollama Configuration Support**\n - **Helper**: techcomthanh\n - **Helpee**: techcomthanh (self-help shared with community)\n - **Context**: Ollama configuration causing node-llama-cpp installation despite using remote resource\n - **Resolution**: Explained need to add `@elizaos/plugins-ollama` to character file in addition to environment variables\n\n3. **Fee Collection Issue Resolution**\n - **Helper**: Kenk\n - **Helpee**: gummy\n - **Context**: Issue with collecting fees on auto.fun\n - **Resolution**: Team pushed a fix overnight and confirmed it was working after user tested again\n\n4. **ELI5 Community Development**\n - **Helper**: gummy\n - **Helpee**: Community\n - **Context**: Proposing to create ELI5 community page and X communities\n - **Resolution**: Kenk approved the idea and gummy committed to setting up X communities\n\n## Action Items\n\n### Technical\n- Fix knowledge import functionality for file paths and directories in beta 49 (Mentioned by techcomthanh)\n- Fix Discord @username mentions to properly highlight and send notifications (Mentioned by techcomthanh)\n- Improve video display in GUI for videos generated by agents (Mentioned by techcomthanh)\n- Resolve issue with node-llama-cpp installation when using remote Ollama endpoint (Mentioned by techcomthanh)\n- Fix fee collection issue on auto.fun (Mentioned by Kenk)\n- Create ELI5 Twitter account that replies to questions with simple explanations (Mentioned by gummy)\n- Integrate ELI5 agent with Reddit community (Mentioned by ryanthelad)\n\n### Documentation\n- Provide sample files and code examples for knowledge import from files (Mentioned by techcomthanh)\n- Clarify Ollama plugin setup requirements in documentation (Mentioned by techcomthanh)\n- Document how to build tweet threads with agent-twitter-client repo (Mentioned by Bitcoin Broccoli)\n- Clarify Dood token distribution eligibility criteria (Mentioned by sukrucildirr)\n\n### Feature\n- Create ELI5 community page or main page (Mentioned by gummy)\n- Set up X communities for ELI5 (Mentioned by gummy)\n- Fix token locked chat for ELI5 on website (Mentioned by ryanthelad)\n- Pivot auto.fun to be leading launchpad for startups instead of memes (Mentioned by wire)" }, "ai_news_elizaos_daily_dev_json_2025-05-12": { "filename": "2025-05-12.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-12", "date": 1747008000, "stats": { "totalMessages": 38, "totalUsers": 11 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Analysis of Discord Chat in 💬｜general\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. One user (DorianD) briefly explored the concept of referencing one character file from another (e.g., importing woman.character.json into eliza.character.json) but quickly concluded this would require modifying the runtime that processes JSON files. Another user (Titan) inquired about plugins for integrating news content as knowledge for agents, with a suggestion to build an RSS plugin. The conversation also included a question about the expected release date of v2, sharing of resource links, and an offer from a developer seeking project opportunities.\n\n## 2. FAQ\nQ: Has anyone done something like have a main character file reference/import another character file? (asked by DorianD) A: Self-answered that it would require modifying the runtime that reads the JSON files (answered by DorianD)\nQ: When is the expected official release of v2? (asked by Nooters) A: Unanswered\nQ: Is there a plugin to get the latest news and add it as knowledge into the agent? Like News API connection? (asked by Titan | Livepeer-Eliza.com) A: Build an RSS plugin (answered by sayonara)\n\n## 3. Help Interactions\nHelper: sayonara | Helpee: Titan | Livepeer-Eliza.com | Context: Looking for a plugin to integrate news content into an agent | Resolution: Suggested building an RSS plugin\n\n## 4. Action Items\nFeature: Character file import system to allow referencing one character file from another | Description: Allow eliza.character.json to import woman.character.json | Mentioned By: DorianD\nFeature: News integration plugin | Description: Create plugin to get latest news and add it as knowledge into agents | Mentioned By: Titan | Livepeer-Eliza.com\nTechnical: Build an RSS plugin | Description: Develop RSS plugin for news integration with agents | Mentioned By: sayonara", "messageCount": 11, "userCount": 7 }, { "channelId": "1327493511406293016", "channelName": "🎤｜plug-your-projects", "summary": "# Analysis of \"🎤｜plug-your-projects\" Channel\n\n## 1. Summary\nThe chat segment is very brief, containing only four messages between two users. Terexitarius mentions acquiring \"Plinc\" (likely a token) and asks about EVM chain support. Ruby declines to engage with gambling or token projects due to personal policy against speculation-enabling technologies. Terexitarius then shares a tool called Screenpipe (https://screenpi.pe/), mentioning they're training an AI on their personal data and suggesting it might be useful for others, with potential for plugin development. Ruby expresses interest in Screenpipe for personal knowledge management while raising privacy concerns about continuous recording and inquiring about selective capture, data retention policies, and AI training pipeline details.\n\n## 2. FAQ\nQ: Can you do EVM chains next? (asked by Terexitarius) A: Unanswered\nQ: Have you thought about selective capture or data retention policies? (asked by Ruby) A: Unanswered\nQ: How are you handling the AI training pipeline? (asked by Ruby) A: Unanswered\n\n## 3. Help Interactions\nHelper: Terexitarius | Helpee: Channel members | Context: Sharing a tool (Screenpipe) for recording screen activity that can be used for AI training | Resolution: Provided link to the tool and mentioned potential future plugin development\n\n## 4. Action Items\nFeature: Potential Screenpipe plugin development | Description: Creating a plugin for the Screenpipe screen recording tool | Mentioned By: Terexitarius\nTechnical: EVM chains support | Description: Adding Ethereum Virtual Machine chains support to an unspecified project | Mentioned By: Terexitarius\nTechnical: Address privacy concerns in screen recording | Description: Implementing selective capture or data retention policies for Screenpipe | Mentioned By: Ruby", "messageCount": 4, "userCount": 2 }, { "channelId": "1324098367416172665", "channelName": "📮｜feedback", "summary": "# Discord Chat Analysis for 📮｜feedback Channel\n\n## 1. Summary:\nThe conversation centers on difficulties with the v2 CLI versus manual workflow in ElizaOS. Hidden Forces expresses frustration with documentation gaps when trying to load a custom character. Ruby offers guidance, explaining that the CLI isn't just an automated version of manual steps but has its own mental model with additional capabilities. Ruby helps troubleshoot Hidden Forces' character.json configuration, identifying issues with the voice settings, knowledge directory path, and suggesting keeping sensitive credentials in the .env file rather than in the character configuration. Ruby provides a simplified template as a starting point, recommending a minimal approach before adding complexity. The discussion highlights the learning curve of v2 and the importance of proper configuration structure and credential management.\n\n## 2. FAQ:\nQ: Does anyone have a link to the online Eliza Helper Bot interface? (asked by Hidden Forces) A: The helper bot interface was deprecated a while back - the new v2 workflow is more flexible but has a steeper learning curve. (answered by Ruby)\nQ: Why doesn't the template include info for the OpenAI key? What LLM backend would it use? (asked by Hidden Forces) A: The OpenAI key and LLM settings go in your .env file or environment variables. The default backend is gpt-4 but you can override that in your project's main config. (answered by Ruby)\nQ: Should the Supabase keys also be put into the .env file and kept out of the character JSON? What's the format? (asked by Hidden Forces) A: Yes! Definitely keep those keys in .env - never in the character json. The format is simple: SUPABASE_URL=your_url_here SUPABASE_ANON_KEY=your_key_here (answered by Ruby)\n\n## 3. Help Interactions:\nHelper: Ruby | Helpee: Hidden Forces | Context: Struggling with loading a custom character in v2 | Resolution: Provided a simplified character.json template and advised keeping credentials in .env file\nHelper: Ruby | Helpee: Hidden Forces | Context: Confusion about CLI vs manual workflow differences | Resolution: Explained that CLI has its own mental model with additional capabilities beyond manual steps\n\n## 4. Action Items:\nType: Documentation | Description: Improve documentation on differences between manual work and CLI in v2 | Mentioned By: Hidden Forces\nType: Documentation | Description: Create a guide on key differences between CLI and manual approaches | Mentioned By: Ruby\nType: Technical | Description: Fix character.json configuration issues including voice model/url values and knowledge directory path | Mentioned By: Ruby", "messageCount": 23, "userCount": 3 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# elizaOS Development Discord - 2025-05-12\n\n## Overall Discussion Highlights\n\n### Character Configuration & Development\n- Discussion about referencing one character file from another (e.g., importing woman.character.json into eliza.character.json)\n- Detailed troubleshooting of character.json configuration issues in v2, including voice settings and knowledge directory paths\n- Recommendation to keep a minimal approach when starting with character configurations before adding complexity\n\n### Tools & Integrations\n- Interest in news integration capabilities for agents, with suggestion to build an RSS plugin\n- Introduction of Screenpipe (https://screenpi.pe/), a tool for recording screen activity that can be used for AI training\n- Discussion about potential plugin development for Screenpipe\n\n### System Architecture & Security\n- Emphasis on proper credential management, keeping sensitive information in .env files rather than character configurations\n- Clarification on the differences between CLI and manual workflows in v2, noting that CLI has its own mental model\n\n## Key Questions & Answers\n\n**Q: Has anyone done something like have a main character file reference/import another character file?** \nA: Self-answered that it would require modifying the runtime that reads the JSON files (DorianD)\n\n**Q: Is there a plugin to get the latest news and add it as knowledge into the agent? Like News API connection?** \nA: Build an RSS plugin (sayonara)\n\n**Q: Does anyone have a link to the online Eliza Helper Bot interface?** \nA: The helper bot interface was deprecated a while back - the new v2 workflow is more flexible but has a steeper learning curve. (Ruby)\n\n**Q: Why doesn't the template include info for the OpenAI key? What LLM backend would it use?** \nA: The OpenAI key and LLM settings go in your .env file or environment variables. The default backend is gpt-4 but you can override that in your project's main config. (Ruby)\n\n**Q: Should the Supabase keys also be put into the .env file and kept out of the character JSON? What's the format?** \nA: Yes! Definitely keep those keys in .env - never in the character json. The format is simple: SUPABASE_URL=your_url_here SUPABASE_ANON_KEY=your_key_here (Ruby)\n\n## Community Help & Collaboration\n\n- **Ruby helped Hidden Forces** with character.json configuration issues, providing a simplified template and explaining the proper way to manage credentials\n- **Ruby clarified** the conceptual differences between CLI and manual workflows in v2, explaining that CLI isn't just an automated version of manual steps\n- **sayonara suggested** building an RSS plugin to Titan who was looking for news integration capabilities\n- **Terexitarius shared** Screenpipe tool with the community, suggesting it might be useful for personal knowledge management and AI training\n\n## Action Items\n\n### Technical\n- Build an RSS plugin for news integration with agents (mentioned by sayonara)\n- Fix character.json configuration issues including voice model/url values and knowledge directory path (mentioned by Ruby)\n- Address privacy concerns in screen recording with selective capture or data retention policies for Screenpipe (mentioned by Ruby)\n- Potential EVM chains support for an unspecified project (mentioned by Terexitarius)\n\n### Documentation\n- Improve documentation on differences between manual work and CLI in v2 (mentioned by Hidden Forces)\n- Create a guide on key differences between CLI and manual approaches (mentioned by Ruby)\n\n### Feature\n- Character file import system to allow referencing one character file from another (mentioned by DorianD)\n- News integration plugin to get latest news and add it as knowledge into agents (mentioned by Titan)\n- Potential Screenpipe plugin development for the screen recording tool (mentioned by Terexitarius)" }, "ai_news_hyperfy_daily_json_2025-05-12": { "filename": "2025-05-12.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-12", "date": 1747008000, "stats": { "totalMessages": 47, "totalUsers": 20 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary\nThe chat segment covers discussions about optimizing image loading in what appears to be a virtual world platform. Users discussed file format recommendations for faster loading times, with suggestions to use compressed formats like webp under 300KB. There was mention of intentional blur effects being applied to images. One user (jin) briefly mentioned progress on building shows like \"clank tank\" in a platform called \"hyperfy\" with more real-time capabilities. A user named b0gie reported an environment variable issue in their container setup using Coolify, despite the container working properly. Another user (drdoge.eth) mentioned updating their world and converting textures to webp format for performance improvements.\n\n## 2. FAQ\nQ: Can it handle webp with frames? (asked by ᲼~/^b0gie-(.*)$/) A: Haven't tried but probably (answered by Ashxn)\n\n## 3. Help Interactions\nHelper: vox | Helpee: ~/drdoge.eth | Context: Slow loading image in virtual world | Resolution: Suggested using lower resolution images since they get blurred anyway\nHelper: Ashxn | Helpee: ~/drdoge.eth | Context: Image optimization for virtual world | Resolution: Recommended small jpg/png/webp under 300KB for faster loading, noting blur is intentional\n\n## 4. Action Items\nTechnical: Convert textures to webp format for better performance | Description: Using webp format for textures improves loading times | Mentioned By: ~/drdoge.eth\nTechnical: Investigate environment variable issue in container | Description: Container reports missing env variables despite working properly in Coolify | Mentioned By: ᲼~/^b0gie-(.*)$/", "messageCount": 18, "userCount": 5 }, { "channelId": "1330373197203505185", "channelName": "🤖│agents", "summary": "The chat segment is extremely brief, containing only two messages from the same user (0mka). The user shared a YouTube video link with a specific timestamp (2:17:51) and mentioned that \"the whole thing is worth watch\" while suggesting to start from the timestamp provided. No technical discussions, problem-solving, or implementations were shared in this limited exchange. The content appears to be a recommendation to watch a video, possibly related to AI agents given the channel name, but no specific technical details were discussed.", "messageCount": 2, "userCount": 1 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Analysis of ⚡│general Discord Channel\n\n## 1. Summary\nThis Discord chat segment from the \"⚡│general\" channel contains minimal technical discussion. The conversation consists primarily of greetings (\"gm\") between community members and brief expressions of encouragement. There is a mention of an upcoming community call that some members are excited about, with maximus noting that while people are working on projects, they might not all be ready for release before the call. No specific technical discussions, decisions, or problem-solving occurred in this segment.\n\n## 2. FAQ\nQ: I feel like this community call is going to be a BANGER (asked by MUDBONE) A: Oh man, no pressure! 😅 I think a few folks are cooking cool stuff but not sure it'll all be released before the call 🤔 (answered by maximus)\n\n## 3. Help Interactions\nNo significant help interactions were present in this chat segment.\n\n## 4. Action Items\nNo specific action items were identified in this chat segment.", "messageCount": 18, "userCount": 12 }, { "channelId": "1326789867312775290", "channelName": "🪙│hyper", "summary": "# Analysis of Discord Chat in \"🪙│hyper\" Channel\n\n## 1. Summary\nThis chat segment is very brief and contains minimal technical discussion. The conversation primarily consists of community members expressing positive sentiment about the HYPER token price performance, particularly noting that it's up while SOL is down. There are mentions of potential future developments including DAO implementation, staking, liquidity growth, and CEX listings. One user (simk) suggests focusing on growing liquidity and expanding the holder base before implementing DAO or staking features. There is also a brief mention of ai16z getting listed on crypto.com, which is viewed as positive for HYPER and projects using ai16z. Overall, this is a short segment with expressions of optimism but lacking substantial technical content or problem-solving discussions.\n\n## 2. FAQ\nQ: What should be prioritized before implementing DAO or staking? (implied from simk's comment) A: Growing liquidity and expanding holders, building narrative-driven strategies, increasing visibility and Hyperfy usage (answered by simk)\n\n## 3. Help Interactions\nNo significant help interactions were present in this chat segment.\n\n## 4. Action Items\nType: Technical | Description: Focus on growing liquidity and expanding holder base before implementing DAO or staking | Mentioned By: simk\nType: Feature | Description: Consider building more narrative-driven or exposure strategies for visibility | Mentioned By: simk\nType: Feature | Description: Explore strategic CEX listings to bring more users and stabilize price | Mentioned By: simk", "messageCount": 7, "userCount": 4 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "The chat segment is extremely brief, containing only two messages. The first message from jin at 02:09 appears to be empty or possibly contained an image or attachment that isn't visible in the transcript. At 02:27, Ashxn responded with \"lookin good,\" suggesting approval of whatever jin shared. There is no substantial technical discussion, problem-solving, or decision-making present in this limited exchange.", "messageCount": 2, "userCount": 2 } ] } }, "ai_news_hyperfy_daily_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# Hyperfy Discord - 2025-05-12\n\n## Overall Discussion Highlights\n\n### Performance Optimization\n- Several users discussed optimizing image loading in virtual worlds, with recommendations to use compressed formats like webp under 300KB\n- Intentional blur effects are being applied to images in the platform\n- Converting textures to webp format was mentioned as a performance improvement strategy\n\n### Development Progress\n- jin reported progress on building shows like \"clank tank\" in Hyperfy with more real-time capabilities\n- Some community members are working on projects that may not be ready before the upcoming community call\n\n### HYPER Token & Ecosystem\n- Community members expressed positive sentiment about HYPER token price performance (up while SOL is down)\n- Discussion about future developments including DAO implementation, staking, liquidity growth, and CEX listings\n- Suggestion to prioritize growing liquidity and expanding the holder base before implementing DAO or staking features\n- Mention of ai16z getting listed on crypto.com, viewed as positive for HYPER and projects using ai16z\n\n### Technical Issues\n- b0gie reported an environment variable issue in their container setup using Coolify, despite the container working properly\n\n## Key Questions & Answers\n\n**Q: Can Hyperfy handle webp with frames?** \nA: \"Haven't tried but probably\" (Ashxn)\n\n**Q: How to handle slow loading images in virtual worlds?** \nA: Use lower resolution images since they get blurred anyway. Recommended small jpg/png/webp under 300KB for faster loading, noting blur is intentional (vox, Ashxn)\n\n**Q: Will all projects be ready for the upcoming community call?** \nA: \"Oh man, no pressure! 😅 I think a few folks are cooking cool stuff but not sure it'll all be released before the call 🤔\" (maximus)\n\n**Q: What should be prioritized before implementing DAO or staking?** \nA: Growing liquidity and expanding holders, building narrative-driven strategies, increasing visibility and Hyperfy usage (simk)\n\n## Community Help & Collaboration\n\n1. **Image Optimization Guidance**\n - vox and Ashxn helped drdoge.eth with optimizing images for virtual worlds\n - Recommended using lower resolution images and specific file formats (jpg/png/webp under 300KB)\n - Explained that blur effects are intentional in the platform\n\n2. **Content Sharing**\n - 0mka shared a YouTube video with a specific timestamp (2:17:51), noting \"the whole thing is worth watch\"\n - jin shared something in the 3d-design channel that received positive feedback from Ashxn (\"lookin good\")\n\n## Action Items\n\n### Technical\n- Convert textures to webp format for better performance (mentioned by drdoge.eth)\n- Investigate environment variable issue in container setup with Coolify (mentioned by b0gie)\n- Focus on growing liquidity and expanding holder base before implementing DAO or staking (mentioned by simk)\n\n### Feature\n- Consider building more narrative-driven or exposure strategies for visibility (mentioned by simk)\n- Explore strategic CEX listings to bring more users and stabilize price (mentioned by simk)\n\n### Community\n- Prepare for upcoming community call where members will showcase their projects (mentioned by maximus, MUDBONE)" }, "github_summaries_daily_2025-05-13": { "filename": "2025-05-13.md", "content": "# ElizaOS Daily Update (May 13, 2025)\n\n## OVERVIEW \nToday, significant advancements were made in the ElizaOS project, focusing on enhancing the CLI functionality and supporting third-party plugin installations. Key bug fixes were implemented to improve system stability, particularly in the plugin and CI areas. The team also addressed several issues related to error handling and logging, contributing to a more robust development environment.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Feature Enhancements\n- Improved CLI functionality for the ElizaOS agent command, fixing issues with JSON output and file saving ([#4560](https://github.com/elizaos/eliza/pull/4560)).\n- Added support for third-party plugin installations, including a refactor of the plugin install code and the addition of relevant tests ([#4568](https://github.com/elizaos/eliza/pull/4568)).\n\n### Bug Fixes\n- Resolved a critical issue in the `service.ts` file due to improper merge conflict resolution, restoring several missing methods ([#4552](https://github.com/elizaos/eliza/pull/4552)).\n- Updated CI TEE configurations to enhance continuous integration processes ([#4572](https://github.com/elizaos/eliza/pull/4572)).\n- Adjusted Telegram message manager tests to expect 'MarkdownV2' for message sending ([#4570](https://github.com/elizaos/eliza/pull/4570)).\n\n## CLOSED ISSUES\n- No issues were closed today.\n\n## NEW ISSUES\n\n### Documentation and Dependency Challenges\n- Encountered a 404 error for missing documentation paths in the repository, specifically for the i18n readme ([#4565](https://github.com/elizaos/eliza/issues/4565)).\n- A request to publish to npm was raised due to peer dependency conflicts with the zod library, causing build issues in another repository ([#4562](https://github.com/elizaos/eliza/issues/4562)).\n- An error was reported from CI activity, indicating potential issues with the continuous integration setup ([#4561](https://github.com/elizaos/eliza/issues/4561))." }, "github_summaries_week_latest_2025-05-18.md": { "filename": "2025-05-18.md", "content": "# ElizaOS Weekly Update (May 18 - 24, 2025)\n\n## OVERVIEW\nThis week saw significant expansion of ElizaOS's API capabilities with new endpoints for worlds, rooms, and agent messaging. The team enhanced plugin infrastructure with registry integration and timeout handling, while fixing critical UI responsiveness issues. Major progress was made on the Polygon plugin, bringing blockchain functionality to the framework. Test reliability was improved across CLI commands and integration tests.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### API Expansion and World Management\n- Added new API endpoints for creating and managing worlds and rooms ([#4667](https://github.com/elizaos/eliza/pull/4667), [#4647](https://github.com/elizaos/eliza/pull/4647))\n- Enhanced message API with world selection capabilities, allowing messages to be associated with specific worlds ([#4637](https://github.com/elizaos/eliza/pull/4637))\n- Improved agent creation API to return agent ID in the initial response, eliminating the need for subsequent calls ([#4634](https://github.com/elizaos/eliza/pull/4634))\n\n### Plugin Infrastructure Improvements\n- Implemented registry integration for plugins with 30-second timeout protection ([#4641](https://github.com/elizaos/eliza/pull/4641), [#4678](https://github.com/elizaos/eliza/pull/4678))\n- Added channel ID filtering capability to Discord plugin ([#4665](https://github.com/elizaos/eliza/pull/4665))\n- Removed global environment variable support in favor of local environment management ([#4666](https://github.com/elizaos/eliza/pull/4666))\n- Integrated Sentry logging for core logger errors ([#4650](https://github.com/elizaos/eliza/pull/4650))\n\n### Blockchain Integration Progress\n- Made significant progress on Polygon plugin implementation, including core EVM RPC wrappers and basic read operations ([#4575](https://github.com/elizaos/eliza/pull/4575))\n- Added Polygon Gas Oracle integration for transaction fee estimation ([#4574](https://github.com/elizaos/eliza/pull/4574))\n- Started work on Jupiter Swap plugin for cryptocurrency trading functionality ([#4593](https://github.com/elizaos/eliza/pull/4593))\n\n### Bug Fixes and Test Improvements\n- Fixed UI responsiveness issue with agent start button not updating status in real-time ([#4642](https://github.com/elizaos/eliza/pull/4642))\n- Resolved issues with dynamic providers in reply actions ([#4651](https://github.com/elizaos/eliza/pull/4651), [#4670](https://github.com/elizaos/eliza/pull/4670))\n- Improved test reliability by fixing flakiness in bats tests and addressing integration test failures ([#4663](https://github.com/elizaos/eliza/pull/4663), [#4654](https://github.com/elizaos/eliza/pull/4654))\n\n## CLOSED ISSUES\n\n### Documentation and Community Improvements\n- Updated community section documentation with improved navigation flowcharts for both technical and non-technical users ([#4260](https://github.com/elizaos/eliza/issues/4260))\n- Enhanced project documentation with updated blog posts and comprehensive partner documentation ([#4586](https://github.com/elizaos/eliza/pull/4586))\n- Implemented automatic documentation deployment workflow for changes to the docs folder ([#4640](https://github.com/elizaos/eliza/pull/4640), [#4631](https://github.com/elizaos/eliza/pull/4631))\n\n### Technical Debt and Architecture Improvements\n- Addressed platform interface needs in core package for ElizaOS v2 ([#3491](https://github.com/elizaos/eliza/issues/3491))\n- Resolved agent hanging issues after core initialization with specific configurations ([#4486](https://github.com/elizaos/eliza/issues/4486))\n- Improved dependency management with request to publish to npm for better version compatibility ([#4562](https://github.com/elizaos/eliza/issues/4562))\n\n## NEW ISSUES\n\nNo new issues were reported during this period. The team focused on addressing existing issues and implementing planned features." }, "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 significant enhancements to the framework's core architecture and plugin ecosystem. The team focused on improving CLI functionality, refining agent interactions, and streamlining the plugin management system. Major strides were made in database operations, authentication mechanisms, and documentation, while several plugins were moved to standalone repositories to support the new plugin sharing system between v0.x and v1.x.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### CLI Enhancements and Command Refinements\n- Improved CLI commands with better documentation and consistent behavior across platforms ([#4646](https://github.com/elizaos/eliza/pull/4646), [#4583](https://github.com/elizaos/eliza/pull/4583))\n- Consolidated update commands for better user experience ([#4592](https://github.com/elizaos/eliza/pull/4592), [#4591](https://github.com/elizaos/eliza/pull/4591))\n- Enhanced environment variable management with better system information display ([#4610](https://github.com/elizaos/eliza/pull/4610), [#4445](https://github.com/elizaos/eliza/pull/4445))\n- Improved dev command with better character file handling ([#4618](https://github.com/elizaos/eliza/pull/4618))\n\n### Plugin System Restructuring\n- Prepared v0.x for sharing plugins with v1.x ([#4384](https://github.com/elizaos/eliza/pull/4384))\n- Added support for third-party plugin installation directly from GitHub URLs ([#4568](https://github.com/elizaos/eliza/pull/4568), [#4577](https://github.com/elizaos/eliza/pull/4577))\n- Implemented plugin specification submodule for better standardization ([#4553](https://github.com/elizaos/eliza/pull/4553))\n- Moved several plugins out of the monorepo to standalone repositories ([#4669](https://github.com/elizaos/eliza/pull/4669), [#4511](https://github.com/elizaos/eliza/pull/4511))\n\n### Database and Storage Improvements\n- Enhanced PGLite database management with per-project directories ([#4423](https://github.com/elizaos/eliza/pull/4423), [#4497](https://github.com/elizaos/eliza/pull/4497))\n- Added comprehensive integration tests for database operations ([#4518](https://github.com/elizaos/eliza/pull/4518))\n- Fixed foreign key constraint violations when deleting agents ([#4510](https://github.com/elizaos/eliza/pull/4510))\n- Improved semantic text splitting for better RAG knowledge retrieval ([#4235](https://github.com/elizaos/eliza/pull/4235))\n\n### Authentication and API Enhancements\n- Added authentication middleware and API key dialog for unauthorized access ([#4420](https://github.com/elizaos/eliza/pull/4420))\n- Created new API endpoints for rooms and worlds management ([#4647](https://github.com/elizaos/eliza/pull/4647), [#4667](https://github.com/elizaos/eliza/pull/4667))\n- Optimized agent loading for improved performance with multiple agents ([#4519](https://github.com/elizaos/eliza/pull/4519))\n- Added world selection capability in message API ([#4637](https://github.com/elizaos/eliza/pull/4637))\n\n### Model and Provider Improvements\n- Extended OpenAI plugin to support custom embedding endpoints ([#4421](https://github.com/elizaos/eliza/pull/4421))\n- Added model usage events tracking for embeddings and image descriptions ([#4438](https://github.com/elizaos/eliza/pull/4438))\n- Optimized reply functionality to use small models for faster responses ([#4416](https://github.com/elizaos/eliza/pull/4416))\n- Refactored model handling in AgentRuntime to support provider and priority ([#4507](https://github.com/elizaos/eliza/pull/4507))\n\n### Social Media Integration\n- Implemented Twitter timeline functionality ([#4429](https://github.com/elizaos/eliza/pull/4429))\n- Added comprehensive tutorial for Twitter AI agent setup ([#4425](https://github.com/elizaos/eliza/pull/4425))\n- Fixed issues with Twitter post templates ([#4595](https://github.com/elizaos/eliza/pull/4595))\n- Enhanced Discord plugin with channel ID filtering ([#4665](https://github.com/elizaos/eliza/pull/4665))\n\n### Error Handling and Logging\n- Integrated Sentry logging for core logger errors ([#4650](https://github.com/elizaos/eliza/pull/4650))\n- Fixed JSON parsing issues with nested objects ([#4198](https://github.com/elizaos/eliza/pull/4198))\n- Improved error handling in message processing ([#4508](https://github.com/elizaos/eliza/pull/4508))\n- Enhanced logging with time tracking in tests ([#4621](https://github.com/elizaos/eliza/pull/4621))\n\n### Documentation and Code Quality\n- Added comprehensive docstrings to multiple components ([#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- Updated documentation with improved CLI command instructions ([#4448](https://github.com/elizaos/eliza/pull/4448), [#4493](https://github.com/elizaos/eliza/pull/4493))\n- Implemented automated documentation deployment workflow ([#4631](https://github.com/elizaos/eliza/pull/4631))\n- Fixed broken links and improved formatting in documentation ([#4433](https://github.com/elizaos/eliza/pull/4433), [#4597](https://github.com/elizaos/eliza/pull/4597))\n\n## CLOSED ISSUES\n\n### Documentation and Tutorials\n- Fixed broken links and improved tutorial content ([#4260](https://github.com/elizaos/eliza/issues/4260), [#3880](https://github.com/elizaos/eliza/issues/3880))\n- Tested and verified CLI command documentation for accuracy ([#4143](https://github.com/elizaos/eliza/issues/4143))\n- Clarified plugin compatibility with Eliza v2 ([#4164](https://github.com/elizaos/eliza/issues/4164))\n\n### Twitter Integration Issues\n- Resolved media generation and attachment for Twitter posts ([#4241](https://github.com/elizaos/eliza/issues/4241), [#4224](https://github.com/elizaos/eliza/issues/4224))\n- Fixed formatting issues with line breaks in tweets ([#3897](https://github.com/elizaos/eliza/issues/3897))\n- Addressed Twitter space functionality problems ([#4180](https://github.com/elizaos/eliza/issues/4180))\n- Implemented solutions for Twitter interactions and reactions ([#4181](https://github.com/elizaos/eliza/issues/4181))\n\n### Platform Compatibility\n- Resolved Windows build issues ([#4094](https://github.com/elizaos/eliza/issues/4094))\n- Improved remote debugging capabilities for v2 ([#3978](https://github.com/elizaos/eliza/issues/3978))\n- Fixed CLI functionality and error handling ([#4107](https://github.com/elizaos/eliza/issues/4107), [#4159](https://github.com/elizaos/eliza/issues/4159))\n\n### Service Integration\n- Addressed Discord message persistence issues ([#3952](https://github.com/elizaos/eliza/issues/3952))\n- Fixed API key handling for Anthropic integration ([#4049](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 250 new PRs (176 merged), 15 new issues, and 66 active contributors.\",\n \"topIssues\": [\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_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\": 5\n },\n {\n \"id\": \"I_kwDOMT5cIs61QKf3\",\n \"title\": \"pglite log entry unicode escape error\",\n \"author\": \"plvo\",\n \"number\": 4457,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nWhen attempting to create a log entry with the `useModel:TEXT_LARGE` type, the operation fails due to an `unsupported Unicode escape sequence` error. This results in the log entry not being created, impacting the reliability of our tracking system.\\n\\n**To Reproduce**\\n\\nSteps to reproduce the behavior:\\n\\n1. Trigger a model usage event of type `useModel:TEXT_LARGE`.\\n2. Ensure that the payload contains a string with an invalid Unicode escape (e.g. malformed `\\\\u` sequence).\\n3. Observe the failure to log the event.\\n\\n**Expected behavior**\\n\\nThe log entry should be created successfully, or the input should be sanitized/validated to prevent the escape sequence error.\\n\\n**Screenshots**\\n\\nN/A\\n\\n**Additional context**\\n\\nHere is the error output:\\n\\n```\\n[2025-05-05 21:44:53] ERROR: Failed to create log entry:\\n type: \\\"useModel:TEXT_LARGE\\\"\\n roomId: \\\"964d1ca6-29f9-00e0-b2c6-b16caf5bbed7\\\"\\n entityId: \\\"964d1ca6-29f9-00e0-b2c6-b16caf5bbed7\\\"\\n error: \\\"unsupported Unicode escape sequence\\\"\\n\\n# ... drizzle error\\n\\n\\nerror: unsupported Unicode escape sequence\\n at ye.Ve (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-EADU5A67.js:1:17602)\\n at ye.nt (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-EADU5A67.js:1:14988)\\n at ye.parse (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-EADU5A67.js:1:13740)\\n at pe.execProtocol (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/index.js:3:239489)\\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\\n at async pe.l (file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-A7RFOIQ7.js:8:1911)\\n at async file:///workspaces/x/agent/node_modules/@electric-sql/pglite/dist/chunk-A7RFOIQ7.js:8:2407 {\\n length: 250,\\n severity: 'ERROR',\\n code: '22P05',\\n detail: '\\\\\\\\u0000 cannot be converted to text.',\\n hint: undefined,\\n position: undefined,\\n internalPosition: undefined,\\n internalQuery: undefined,\\n where: 'JSON data, line 1: ...n environnement virtuel :\\\\\\\\\\\"}}],\\\\\\\\n \\\\\\\\u0000...\\\\n' +\\n \\\"unnamed portal parameter $2 = '...'\\\",\\n schema: undefined,\\n table: undefined,\\n column: undefined,\\n dataType: undefined,\\n constraint: undefined,\\n file: 'jsonfuncs.c',\\n line: '638',\\n routine: 'json_errsave_error'\\n}\\n\\n\\n```\\n\\nThis seems to be triggered during JSON parsing or serialization, potentially from malformed input data that includes a broken escape like `\\\\u`.\\n\",\n \"createdAt\": \"2025-05-05T21:51:18Z\",\n \"closedAt\": \"2025-05-12T08:05:38Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs61qUx2\",\n \"title\": \"Agent Hangs After Core Init / REST API Bind (Anthropic + Twitter Config)\",\n \"author\": \"kunleulysses\",\n \"number\": 4486,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"Environment:\\nOS: Ubuntu 22.04.5 LTS (on VPS)\\nNode.js Version: v23.11.0 (installed via NVM)\\npnpm Version: v9.15.0\\nElizaOS Installation Method: Manual Monorepo Clone (git clone https://github.com/elizaos/eliza.git)\\nElizaOS Version: Checked out to latest tag (Likely v0.25.9 based on agent package version in logs)\\n\\nKey Packages:\\n@elizaos/agent: v0.25.9\\n@elizaos/core: Likely v0.25.9 (based on agent)\\n@elizaos/plugin-twitter: 0.25.6-alpha.1 (or version installed via @latest)\\n@elizaos/plugin-anthropic: 1.0.0-alpha.0 (or version installed via @latest)\\nHardware: VPS with 3GB RAM\\n\\nProblem Description:\\nThe ElizaOS agent process successfully initializes its core components but hangs indefinitely immediately after the Direct Client REST API binds to its port (e.g., 3000). This occurs when configured to use a custom character (flappy.character.json) located in a root characters/ directory, with the goal of using the Anthropic model provider (@elizaos/plugin-anthropic) and the Twitter client (@elizaos/plugin-twitter) with auto-interactions enabled.\\nThe logs show successful character loading, correct plugin identification (@elizaos/plugin-twitter, @elizaos/plugin-anthropic), selection of \\\"anthropic\\\" as the model provider, database connection, and REST API binding. However, the process never proceeds to the expected Twitter client initialization logs (Creating default Twitter client..., Successfully logged in., Start Hanldeling Twitter Timeline, etc.) or any Anthropic-related activity. The process does not crash or exit; it simply stalls.\\n\\nSteps to Reproduce:\\n(Based on troubleshooting sequence followed)\\nClean VPS environment.\\nInstall prerequisites: Node v23.11.0 (via NVM), pnpm v9.15.0, git, build-essential.\\nClone the main eliza monorepo: git clone https://github.com/elizaos/eliza.git && cd eliza.\\nCheck out the latest stable tag: git checkout $(git describe --tags --abbrev=0).\\nCreate and configure ~/eliza/.env with valid Twitter API credentials (Key, Secret, Access Token, Secret) and a valid Anthropic API Key. Ensure ENABLE_TWITTER_POST_GENERATION=true and ENABLE_ACTION_PROCESSING=true. Ensure conflicting AI providers (USE_LOCAL_AI, USE_OLLAMA_TEXT_MODELS, OPENAI_API_KEY, etc.) are explicitly set to false or commented out.\\nCreate a ~/eliza/characters/ directory.\\nCreate ~/eliza/characters/flappy.character.json configured with \\\"clients\\\": [\\\"twitter\\\"], \\\"plugins\\\": [\\\"@elizaos/plugin-twitter\\\", \\\"@elizaos/plugin-anthropic\\\"], \\\"modelProvider\\\": \\\"anthropic\\\", and a specific \\\"model\\\": \\\"claude-3-haiku-20240307\\\". Include Twitter interaction settings under settings.twitter.\\nCreate ~/eliza/characters/flappy.agent.json pointing to the character file.\\nInstall dependencies: pnpm install.\\nEnsure correct plugins are installed and linked to the agent package:\\npnpm remove @elizaos/plugin-local-ai (if present)\\npnpm add @elizaos/plugin-anthropic@latest -F @elizaos/agent\\npnpm add @elizaos/plugin-twitter@latest -F @elizaos/agent\\npnpm install\\nBuild the project: pnpm build.\\nStart the agent: pnpm start --characters=\\\"characters/flappy.character.json\\\".\\n\\nExpected Result:\\nThe agent starts fully, logs confirm Twitter login and timeline handling begins, and subsequent AI tasks utilize the Anthropic API via the loaded plugin. The process remains active and responsive.\\n\\nActual Result:\\nThe agent process hangs indefinitely after the SUCCESS: REST API bound to... log message. No further logs related to Twitter client initialization, AI provider interaction, or timeline handling appear. The process doesn't exit or crash.\\n\\n\\n``` Relevant Logs:\\n\\n[2025-05-08 01:16:54] SUCCESS: REST API bound to 0.0.0.0:3000. If running locally, access it at http://localhost:3000.\\n# <-- HANGS HERE -->\\n\\nLog\\nConfiguration:\\n.env (Relevant Sections):\\n# --- Twitter/X Configuration ---\\nTWITTER_USERNAME=featherweightai\\n# TWITTER_PASSWORD=********* # Masked\\n# TWITTER_EMAIL=********* # Masked\\n# TWITTER_API_KEY=********* # Masked\\n# TWITTER_API_SECRET=********* # Masked\\n# TWITTER_ACCESS_TOKEN=********* # Masked\\n# TWITTER_ACCESS_SECRET=********* # Masked\\nENABLE_TWITTER_POST_GENERATION=true\\nENABLE_ACTION_PROCESSING=true\\n\\n# --- Anthropic Configuration ---\\nANTHROPIC_API_KEY=sk-ant-...#### # <<< IMPORTANT: Make sure this is correct\\n# ANTHROPIC_API_URL=\\n\\n# --- Disabled Providers ---\\nUSE_LOCAL_AI=false\\nUSE_OLLAMA_TEXT_MODELS=false\\n# OPENAI_API_KEY=\\n# GAIA_API_KEY=\\n# ... etc other providers blank/commented ...\\nUse code [with caution](https://support.google.com/legal/answer/13505487).\\nDotenv\\ncharacters/flappy.character.json (Relevant Sections):\\n{\\n \\\"name\\\": \\\"Flappy\\\",\\n // ... Bio/Lore/Examples/Style ...\\n \\\"clients\\\": [\\n \\\"twitter\\\"\\n ],\\n \\\"plugins\\\": [\\n \\\"@elizaos/plugin-twitter\\\",\\n \\\"@elizaos/plugin-anthropic\\\"\\n ],\\n \\\"modelProvider\\\": \\\"anthropic\\\", // Lowercase\\n \\\"model\\\": \\\"claude-3-haiku-20240307\\\",\\n \\\"settings\\\": {\\n \\\"secrets\\\": {},\\n \\\"twitter\\\": {\\n \\\"enable_replies\\\": true,\\n \\\"enable_timeline_search\\\": false,\\n \\\"enable_follow_thanks\\\": true,\\n \\\"enable_auto_retweet\\\": false\\n }\\n }\\n // ...\\n}\\n\\nAdditional Context / Troubleshooting Steps Taken:\\nIssue persists even after regenerating Twitter API keys/tokens and confirming \\\"Read, Write and access Direct Messages\\\" permissions are set correctly in the Twitter Dev Portal (OAuth 1.0a).\\nIssue occurred similarly when trying to configure GAIA via Ollama settings (using plugin-local-ai, modelProvider: \\\"OLLAMA\\\"), hanging at the same point.\\nRemoving both Twitter and AI plugins allowed the agent core to start without hanging (in previous testing phases), suggesting the issue occurs during plugin/client initialization after the core runtime is up.\\nNetwork connectivity to api.anthropic.com was verified via curl from the VPS (connection succeeded, though curl syntax errors prevented full request validation).\\nVPS has 3GB RAM, eliminating the previous RAM constraint issue encountered with local models.\\nExplicitly adding the required plugins (plugin-twitter, plugin-anthropic) as dependencies to the @elizaos/agent package using pnpm add -F @elizaos/agent ... successfully resolved earlier \\\"Cannot find package\\\" errors during plugin loading.\",\n \"createdAt\": \"2025-05-08T04:30:57Z\",\n \"closedAt\": \"2025-05-20T09:40:07Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs608Bnv\",\n \"title\": \"Job: looking for a developer with Eliza framework experience\",\n \"author\": \"TheDeveloperTom\",\n \"number\": 4432,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"Really sorry for posting here. If there are developers with eliza framework exp looking for a remote job, please let me know \\n\\nthedevelopertom@gmail.com\",\n \"createdAt\": \"2025-05-02T09:56:19Z\",\n \"closedAt\": \"2025-05-11T12:44:36Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 2\n }\n ],\n \"topPRs\": [\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 \"id\": \"PR_kwDOMT5cIs6V5ow8\",\n \"title\": \"Feat/add mysql to degen\",\n \"author\": \"0xbbjoker\",\n \"number\": 4554,\n \"body\": \"\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-05-12T21:06:49Z\",\n \"mergedAt\": null,\n \"additions\": 43476,\n \"deletions\": 31880\n }\n ],\n \"codeChanges\": {\n \"additions\": 99282,\n \"deletions\": 63296,\n \"files\": 870,\n \"commitCount\": 988\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\": \"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\": \"fix: integration test import\",\n \"prNumber\": 4541,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: error associated with issue #4336, where TEXT_EMBEDDING was not…\",\n \"prNumber\": 4537,\n \"type\": \"bugfix\",\n \"body\": \"… loaded, it was caused to openai plugin not having an export for getProviderBaseURL\\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\": \"chore: back to regular dev command\",\n \"prNumber\": 4566,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: use latest v2 plugin list\",\n \"prNumber\": 4564,\n \"type\": \"tests\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: upgrades to cli agent command\",\n \"prNumber\": 4560,\n \"type\": \"feature\",\n \"body\": \"This PR is a focused attempt to improve the elizaos agent cli command. The changes are:\\r\\n\\r\\n\\r\\n**elizaos agent get** \\r\\n-j/--json wasnt working (it was saving the file instead of of displaying in console json format)\\r\\n-o/--output wasnt working\"\n },\n {\n \"title\": \"chore: enable strict types and adjust guards for plugin-telegram\",\n \"prNumber\": 4559,\n \"type\": \"other\",\n \"body\": \"\\n\\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\": \"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: hallucination in reply\",\n \"prNumber\": 4603,\n \"type\": \"bugfix\",\n \"body\": \"Agent hallucinates if we use `OBJECT_SMALL`\\r\\n\\r\\nJSON responses are made up and causes many troubles.\\r\\n\\r\\nExample issue on the scr shoot:\\r\\n\\r\\n\\\"image\\\"\\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\": \"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: 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\": \"bring back local ai test\",\n \"prNumber\": 4676,\n \"type\": \"tests\",\n \"body\": \"\"\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\": \"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