{ "date_generated_for": "2025-05-12", "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_discord_md_2025-05-09": { "filename": "2025-05-09.md", "content": "# elizaOS Discord - 2025-05-09\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **V2 Release Teaser**: Multiple mentions of an upcoming ElizaOS V2 release with limited details shared\n- **GitHub Contribution Tracking**: Discussion about the elizaOS.github.io repository which tracks contributions and includes a leaderboard functionality\n- **Plugin Development Challenges**: Users reported difficulties importing plugins from external GitHub repositories due to hardcoded assumptions about repository locations\n- **Database Configuration Issues**: Several users encountered problems with PostgreSQL configurations and database migrations, particularly with Neon as a provider\n\n### Token Ecosystem\n- **Auto.fun Platform Concerns**: Significant user frustration about recent token launches perceived as \"rugs\" (projects that quickly lose value)\n- **ELI5 Token Discussion**: Mixed sentiment about ELI5 token, with some users highlighting its potential connection to elizaOS v2 as \"AI16z's brother\"\n- **Platform Improvements**: Team member \"ben\" acknowledged feedback about the auto.fun platform and mentioned improvements are underway\n- **Support Channel Migration**: Announcement that auto.fun support is moving from Discord to Telegram (@AutoDotFunBot) within 48 hours\n\n### Technical Issues\n- **Leaderboard Pagination**: PR (#92) created to fix pagination issues on the contribution leaderboard website\n- **Plugin Dependencies**: Users reported missing dependencies (@elizaos/plugin-tee and @elizaos/plugin-trustdb) for the Solana plugin\n- **Memory-Related Crashes**: Twitter plugin causing \"Maximum call stack size exceeded\" errors\n- **LMStudio Integration Errors**: Users experiencing problems integrating LMStudio with ElizaOS\n\n## Key Questions & Answers\n\n### ElizaOS Technical\n- **Q**: How can I connect my GitHub and SOL wallet for future airdrops? \n **A** (jin): \"We don't have a fully deployed solution for doing that yet\"\n\n- **Q**: What's the link to the leaderboard? \n **A** (jin): \"https://elizaos.github.io/\"\n\n- **Q**: Why am I not on the leaderboard? \n **A** (jin): \"Search should be top 1000 / no limit, considering that a bug\"\n\n- **Q**: When eliza agent is monitoring/responding in multiple servers do we want each server to be its own world? \n **A** (Kenk): \"In v2 it will be able to use the same memory across multiple client interfaces\"\n\n- **Q**: Is eliza.gg down? \n **A** (Kenk): \"Use Eliza.how instead\"\n\n### Token-Related\n- **Q**: How did you determine % for decentralized 60-70? \n **A** (Osint): \"That's standard, 60-70 percent for top 100 token holders\"\n\n- **Q**: Are we looking for binance spot listing through any way? \n **A** (Osint): \"That is something that we have no control of. When they decide it is in their best interest to list ai16z spot, then they'll do it\"\n\n- **Q**: What do you mean by \"based off the Reddit Eli5 community with 15M members\"? \n **A** (ryanthelad): \"Look up r/explainlikeimfive on Reddit, 23.2 Million Followers. All of them will be onboarded to Eli5\"\n\n- **Q**: Is there any advantage for us that hold 10k or more ai16z? \n **A** (!Addison Casey!): \"No info about that yet\"\n\n## Community Help & Collaboration\n\n1. **Leaderboard Visibility Issues**\n - **Helper**: jin\n - **Helpee**: MonteCrypto\n - **Context**: User couldn't find themselves on the leaderboard\n - **Resolution**: Jin provided a direct profile link and acknowledged search limitation as a bug\n\n2. **Leaderboard Pagination Fix**\n - **Helper**: MonteCrypto\n - **Helpee**: Community\n - **Context**: Pagination issues on the leaderboard website\n - **Resolution**: Created PR #92 to fix pagination and make all contributors visible\n\n3. **Plugin Import Problems**\n - **Helper**: Odilitime\n - **Helpee**: BowTiedBlueFin\n - **Context**: Issues with importing plugins from external GitHub repositories\n - **Resolution**: Acknowledged the issue with 1.x plugins and mentioned instructions would be published the following week\n\n4. **Database Migration Errors**\n - **Helper**: scooter8992 (self-help)\n - **Context**: Database migration errors with Neon PostgreSQL\n - **Resolution**: Created a new project in Neon to get a fresh database, which resolved the issue\n\n5. **ELI5 Token Information**\n - **Helper**: ryanthelad and xell0x\n - **Helpee**: Channel members\n - **Context**: Declining sentiment about ELI5 token\n - **Resolution**: Shared positive information about ELI5 being AI16z's little brother and an official character in elizaOS v2\n\n## Action Items\n\n### Technical\n1. **Fix leaderboard search functionality** - Make search include all contributors beyond top 100 (Mentioned by jin)\n2. **Add pagination to leaderboard** - Show all profiles on leaderboard instead of just top 100 (Mentioned by MonteCrypto)\n3. **Develop GitHub-SOL wallet connection solution** - For tracking contributions and future airdrops (Mentioned by jin)\n4. **Fix plugin resolution logic** - Properly handle GitHub URLs from package.json for plugins outside the elizaos-plugins organization (Mentioned by BowTiedBlueFin)\n5. **Address fs4.exists error** - Fix error in ElizaOS configuration saving (Mentioned by scooter8992)\n6. **Fix memory leak in Twitter plugin** - Resolve \"Maximum call stack size exceeded\" errors (Mentioned by scooter8992)\n7. **Resolve missing dependencies** - Fix @elizaos/plugin-tee and @elizaos/plugin-trustdb dependencies for the Solana plugin (Mentioned by scooter8992)\n8. **Improve token verification process** - Prevent misleading information about token distribution (Mentioned by frank_grimes_sr)\n9. **Make migration speed consistent** - Standardize migration speed for all coins or wait for green checkmark before migration (Mentioned by frank_grimes_sr)\n\n### Documentation\n1. **Add leaderboard link to contributing docs** - Link needs to be added to https://eliza.how/docs/contributing (Mentioned by MonteCrypto)\n2. **Update frontpage of eliza.how** - Add partners, videos, leaderboard, plugins links for better quick actions (Mentioned by jin)\n3. **Publish plugin development instructions** - Create documentation for plugin development and integration with ElizaOS (Mentioned by Odilitime)\n4. **Provide clearer token distribution information** - Improve transparency before launches (Mentioned by vas)\n5. **Create transparency around verification process** - Document how tokens get verified status (Mentioned by frank_grimes_sr)\n6. **Document support channel migration** - Users need to migrate to Telegram (@AutoDotFunBot) for support (Mentioned by Kenk)\n\n### Feature\n1. **Extend autodotfun functionality to Twitter** - Enable launching tokens from Twitter with commands (Mentioned by Osint)\n2. **Improve AI-news aggregator** - Jin discovered ways to make it 2-3x better (Mentioned by jin)\n3. **ElizaOS V2 development** - Upcoming major update teased in chat (Mentioned by Multiple users)\n4. **Implement time-based caching** - For facts/provider knowledge in state (Mentioned by scooter8992)\n5. **Support cross-interface memory** - Allow agents to use the same memory across multiple client interfaces in v2 (Mentioned by Kenk)\n6. **Allow more verified launches** - Enable more launches to apply for verified status after first round of launch partners (Mentioned by ryanthelad)" }, "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_dev_md_2025-05-09": { "filename": "2025-05-09.md", "content": "# elizaOS Development Discord - 2025-05-09\n\n## Overall Discussion Highlights\n\n### Token and Project Updates\n- Community members discussed potential token launches for projects ELI5, EDDY, and AI16Z on the auto.fun platform\n- Team members (Odilitime and funboy) clarified that no new token launches are currently planned\n- Questions about EDDY's functionality were raised but remained unanswered\n\n### Development Tools\n- Brief discussion about documentation generation methods used by the team\n- Mention of an ElizaOS WordPress plugin, though noted as not being state-of-the-art\n- A freelance developer offered services related to blockchain development, including token creation and smart contract writing\n\n## Key Questions & Answers\n\n| Question | Answer | Asked By | Answered By |\n|----------|--------|----------|------------|\n| Will token launches be paired with ELI5 or EDDY or only AI16Z? | No token launches | Sidtoshi Vision | Odilitime |\n| Does org project will it have its own coin or just update of ai16z? | No new tokens are planned afaik | Mazino | Odilitime |\n\n## Community Help & Collaboration\n\n- **Documentation Resources**: funboy shared a link to an ElizaOS WordPress plugin in response to Hummus's question about documentation generation methods\n\n## Action Items\n\n### Documentation\n- Provide clear information about the purpose and functionality of ELI5 and EDDY tokens (mentioned by Sidtoshi Vision)\n- Explain the documentation generation process used by the team (mentioned by Hummus)\n- Clarify plans regarding token launches and updates for the community (mentioned by Sidtoshi Vision, Mazino)\n\n---\n\n*Note: Today's discussions were relatively light, with minimal technical problem-solving or implementation discussions. Several questions remained unanswered, suggesting potential topics for future clarification from the team.*" }, "ai_news_elizaos_daily_json_2025-05-11": { "filename": "2025-05-11.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-11", "categories": [ { "title": "Summary for completed_items", "content": [ { "text": "Recent completed items in the elizaOS/eliza repository include several bugfixes, features, refactors, and other changes:\n\nBugfixes:\n- Fixed JSON serialization in pglite to handle invalid Unicode escape sequences in logs (PR #4458)\n- Fixed Twitter functionality in V2 (PR #4506)\n- Implemented Shaw bugfixes (PR #4515)\n- Fixed pglite migrations in two separate PRs (#4531, #4532)\n- Enforced TypeScript on /cli and /plugin-sql, fixing missing DB functions (PR #4529)\n- Fixed agent response and improved logging/tracing in bootstrap plugin (PR #4548)\n- Fixed bad environment resolution (PR #4547)\n- Removed banner display and improved help command formatting (PR #4546)\n- Added passthrough function to prevent LLM plugins from breaking (PR #4544)\n- Fixed integration test import (PR #4541)\n- Fixed error associated with issue #4336 related to TEXT_EMBEDDING (PR #4537)\n\nFeatures and Enhancements:\n- Added Jimmy PM agent functionality (PR #4471)\n- Refactored model handling in AgentRuntime to support provider and priority (PR #4507)\n\nMaintenance and Other Changes:\n- Removed plugin-solana from monorepo (PR #4513)\n- Updated npm and yarn dependencies across directories (PR #4502)\n- Cleaned eliza cache before running CI (PR #4523)\n- Disabled loading instrumentation when not enabled (PR #4530)\n- Removed broken release link in changelog (PR #4527)\n- Updated to newer Bun setup (PR #4526)\n- Cleaned up the-org ENV and Agent loading (PR #4524)\n- Implemented consistent environment naming for project manager agent (PR #4549)\n\nDocumentation:\n- Removed redundant word in solana-v2.md (PR #4520)", "sources": [ "https://github.com/elizaOS/eliza/pull/4458", "https://github.com/elizaOS/eliza/pull/4471", "https://github.com/elizaOS/eliza/pull/4513", "https://github.com/elizaOS/eliza/pull/4507", "https://github.com/elizaOS/eliza/pull/4506", "https://github.com/elizaOS/eliza/pull/4502", "https://github.com/elizaOS/eliza/pull/4523", "https://github.com/elizaOS/eliza/pull/4520", "https://github.com/elizaOS/eliza/pull/4515", "https://github.com/elizaOS/eliza/pull/4532", "https://github.com/elizaOS/eliza/pull/4531", "https://github.com/elizaOS/eliza/pull/4530", "https://github.com/elizaOS/eliza/pull/4529", "https://github.com/elizaOS/eliza/pull/4527", "https://github.com/elizaOS/eliza/pull/4526", "https://github.com/elizaOS/eliza/pull/4524", "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" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "Cryptocurrency Security and Best Practices", "text": "User @dankvr shared extensive cryptocurrency security advice in a thread, starting with a \"Crypto beginner pack\" for different investment levels. For those with $5k+, he recommends a hardware wallet, notebook and pen, spare device for crypto transactions, Google Voice, and learning OPSEC. At $15k+, he suggests adding home defense/cameras and steel seed phrase storage. For $100k+, he recommends multisig/multiple hardware wallets and a burner device when traveling. In follow-up tweets, @dankvr emphasized additional security practices including deleting unused apps, keeping software updated, being aware of various attack vectors (evil maid attacks, phishing, etc.), using strong passwords via a password manager, avoiding SMS 2FA, and maintaining privacy about crypto holdings. When asked about the spare device recommendation, @dankvr clarified it could be \"an old laptop and fresh OS on spare hard drive.\" In a separate conversation, @dankvr discussed potential wallet security issues with another user, asking about software updates and other potential vulnerabilities. @dankvr also warned about a social engineering scam by sharing a post from @thedefiedge about hackers using the compromised @Cointelegraph account to send DMs with phishing links to a typosquatted domain \"Cointetegraph\" attempting to steal X account credentials.", "sources": [ "https://twitter.com/dankvr/status/1921424072702939243", "https://twitter.com/dankvr/status/1921427867902115848", "https://twitter.com/dankvr/status/1921563852975595883", "https://twitter.com/dankvr/status/1921404375060123729", "https://twitter.com/dankvr/status/1921406106972152213", "https://twitter.com/thedefiedge/status/1921039988848030021" ], "images": [ "https://pbs.twimg.com/media/GqpDvH6XMAAPadU.jpg" ], "videos": [] }, { "theme_title": "Bitcoin as an Investment Asset", "text": "Several tweets discussed Bitcoin's role as an investment asset. User @dankvr retweeted a post from @izebel_eth stating that \"the endgame for bitcoin is as the greatest collateral asset invented\" describing it as \"gold that you can store for free, and borrow against permissionlessly.\" In a separate conversation, @shawmakesmagic asked @0xMert_ about how someone makes money with Bitcoin, specifically wondering if they just hold it without selling. User @shawmakesmagic also retweeted a post from @anothercohen with an enthusiastic \"Holy shit we are so back\" message that included what appears to be a Bitcoin-related image.", "sources": [ "https://twitter.com/izebel_eth/status/1921553179973451834", "https://twitter.com/shawmakesmagic/status/1921579874487017806", "https://twitter.com/anothercohen/status/1921258658945552790" ], "images": [ "https://pbs.twimg.com/media/Gqq4YtMaIAAcWIk.jpg", "https://pbs.twimg.com/media/GqmukYBXUAIZcTb.jpg" ], "videos": [] }, { "theme_title": "AI Agents and Development", "text": "User @shawmakesmagic shared several tweets about AI agents and development tools. He promoted \"The Org,\" a tool built on Eliza that allows users to \"Track the progress of your team, help your customers 24/7 and stay on top of your calendar without checking your phone\" with one-click agents for Discord, Telegram, Slack, or Teams that can be set up quickly. He also highlighted how Eliza can be deployed to enable users to chat with documentation in minutes, providing an example and source code to get started. Additionally, @shawmakesmagic mentioned an \"Auto Agent Dev\" and shared a link to build \"an autonomous agent to take over your computer,\" warning that \"it has full access to everything!\" He also praised a launch by commenting \"Best launch so far, these guys are crushing it\" in reference to a quoted tweet from @comput3ai about \"Gud tech.\" User @elizaOS, likely connected to the Eliza platform, tweeted \"trust me - this is the plan\" with an accompanying image, and in a separate tweet stated that \"alignment ≠ conformity.\"", "sources": [ "https://twitter.com/shawmakesmagic/status/1921657337019773332", "https://twitter.com/shawmakesmagic/status/1921662570764681485", "https://twitter.com/shawmakesmagic/status/1921663179555279029", "https://twitter.com/shawmakesmagic/status/1921638239288373352", "https://twitter.com/shawmakesmagic/status/1921603549013692696", "https://twitter.com/comput3ai/status/1921602632092676217", "https://twitter.com/elizaOS/status/1921531985283133712", "https://twitter.com/elizaOS/status/1921575522129383672" ], "images": [ "https://pbs.twimg.com/media/GqsXxI4aQAANpkx.jpg", "https://pbs.twimg.com/media/Gqsd5MjboAAnGdT.png", "https://pbs.twimg.com/media/GqhQPoPWgAA8B0u.jpg" ], "videos": [] }, { "theme_title": "Web Browsers and Technology", "text": "User @dankvr commented on web browsers in a conversation with @gakonst and @zooko, stating that \"the brave team is receptive and quick to implement ideas based on user feedback\" and suggesting that \"one day of using it and some thoughtful constructive criticism would go a long way towards making it good fast.\" He encouraged supporting \"our allies\" in this context. In another conversation, @dankvr responded to @Higgisp and @theo with the statement \"There is no second best,\" possibly in reference to browser or technology preferences.", "sources": [ "https://twitter.com/dankvr/status/1921614528342524123", "https://twitter.com/dankvr/status/1921636791901110779" ], "images": [], "videos": [] } ], "topic": "twitter_activity" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Several pull requests have been submitted to the elizaOS/eliza repository:\n\n1. PR #4512 by ChristopherTrimboli focuses on cleaning up organization agent and environment loading code.\n\n2. PR #4533 by 0xbbjoker addresses a fix for adding missing extensions for migrations.\n\n3. PR #4554, also by 0xbbjoker, adds MySQL support to the 'degen' component.\n\n4. PRs #4535, #4538, and #4543 by yungalgo are all related to the same feature implementation: 'ELIZA290/part-2-plugins-agent-cli-commands', with PR #4543 specifically labeled as 'ELIZA290/part-2-cli-plugins-agent-fresh'.", "sources": [ "https://github.com/elizaOS/eliza/pull/4512", "https://github.com/elizaOS/eliza/pull/4533", "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" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4512", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4533", "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" ], "videos": [] } ], "topic": "pull_request" }, { "title": "Summary for github_summary", "content": [ { "text": "GitHub activity for elizaos/eliza repository over two days:\n\nMay 11-12, 2025: 10 new PRs with 16 merged, 1 new issue, and 13 active contributors.\n\nMay 12-13, 2025: 20 new PRs with 7 merged, 1 new issue, and 11 active contributors.", "sources": [ "source 1 (githubStatsSummary)", "source 2 (githubStatsSummary)" ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Issues for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Two issues have been reported in the elizaOS/eliza repository. Issue #4528 by AndreaRettaroli focuses on improving Eliza in TEE oasis. Issue #4536 by BinaryBluePeach reports an error where the system cannot find the module '@elizaos/core' or its corresponding type declarations.", "sources": [ "https://github.com/elizaOS/eliza/issues/4528", "https://github.com/elizaOS/eliza/issues/4536" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4528", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4536" ], "videos": [] } ], "topic": "issue" }, { "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 the actual contributors.", "sources": [ "source 1", "source 2" ], "images": [], "videos": [] } ], "topic": "github_other" } ], "date": 1746921600 } }, "ai_news_elizaos_daily_md_2025-05-11": { "filename": "2025-05-11.md", "content": "# Daily Report - 2025-05-11\n\n## Completed Items in elizaOS/eliza Repository\n\n- **Bugfixes:**\n - Fixed JSON serialization in pglite to handle invalid Unicode escape sequences in logs (PR #4458)\n - Fixed Twitter functionality in V2 (PR #4506)\n - Implemented Shaw bugfixes (PR #4515)\n - Fixed pglite migrations in two separate PRs (#4531, #4532)\n - Enforced TypeScript on /cli and /plugin-sql, fixing missing DB functions (PR #4529)\n - Fixed agent response and improved logging/tracing in bootstrap plugin (PR #4548)\n - Fixed bad environment resolution (PR #4547)\n - Removed banner display and improved help command formatting (PR #4546)\n - Added passthrough function to prevent LLM plugins from breaking (PR #4544)\n - Fixed integration test import (PR #4541)\n - Fixed error associated with issue #4336 related to TEXT_EMBEDDING (PR #4537)\n\n- **Features and Enhancements:**\n - Added Jimmy PM agent functionality (PR #4471)\n - Refactored model handling in AgentRuntime to support provider and priority (PR #4507)\n\n- **Maintenance and Other Changes:**\n - Removed plugin-solana from monorepo (PR #4513)\n - Updated npm and yarn dependencies across directories (PR #4502)\n - Cleaned eliza cache before running CI (PR #4523)\n - Disabled loading instrumentation when not enabled (PR #4530)\n - Removed broken release link in changelog (PR #4527)\n - Updated to newer Bun setup (PR #4526)\n - Cleaned up the-org ENV and Agent loading (PR #4524)\n - Implemented consistent environment naming for project manager agent (PR #4549)\n\n- **Documentation:**\n - Removed redundant word in solana-v2.md (PR #4520)\n- Sources: https://github.com/elizaOS/eliza/pull/4458, https://github.com/elizaOS/eliza/pull/4471, https://github.com/elizaOS/eliza/pull/4513, https://github.com/elizaOS/eliza/pull/4507, https://github.com/elizaOS/eliza/pull/4506, https://github.com/elizaOS/eliza/pull/4502, https://github.com/elizaOS/eliza/pull/4523, https://github.com/elizaOS/eliza/pull/4520, https://github.com/elizaOS/eliza/pull/4515, https://github.com/elizaOS/eliza/pull/4532, https://github.com/elizaOS/eliza/pull/4531, https://github.com/elizaOS/eliza/pull/4530, https://github.com/elizaOS/eliza/pull/4529, https://github.com/elizaOS/eliza/pull/4527, https://github.com/elizaOS/eliza/pull/4526, https://github.com/elizaOS/eliza/pull/4524, 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\n\n## Twitter Activity\n\n### Cryptocurrency Security and Best Practices\n- @dankvr shared a \"Crypto beginner pack\" with tiered security recommendations based on investment levels ($5k+, $15k+, $100k+)\n- For $5k+ investments, @dankvr recommended hardware wallets, notebooks for recording information, dedicated crypto devices, Google Voice, and OPSEC education\n- For higher investment levels, @dankvr suggested adding home security measures, steel seed phrase storage, and multisig wallet setups\n- @dankvr emphasized additional security practices including deleting unused apps, keeping software updated, and using strong passwords via password managers\n- @dankvr warned about a social engineering scam where hackers used the compromised @Cointelegraph account to send phishing links via DMs\n- Sources: https://twitter.com/dankvr/status/1921424072702939243, https://twitter.com/dankvr/status/1921427867902115848, https://twitter.com/dankvr/status/1921563852975595883, https://twitter.com/dankvr/status/1921404375060123729, https://twitter.com/dankvr/status/1921406106972152213, https://twitter.com/thedefiedge/status/1921039988848030021\n\n### Bitcoin as an Investment Asset\n- @dankvr retweeted @izebel_eth's post describing Bitcoin as \"the greatest collateral asset invented\" and \"gold that you can store for free, and borrow against permissionlessly\"\n- @shawmakesmagic asked @0xMert_ about how people make money with Bitcoin, specifically about holding strategies\n- @shawmakesmagic retweeted @anothercohen's enthusiastic \"Holy shit we are so back\" message with a Bitcoin-related image\n- Sources: https://twitter.com/izebel_eth/status/1921553179973451834, https://twitter.com/shawmakesmagic/status/1921579874487017806, https://twitter.com/anothercohen/status/1921258658945552790\n\n### AI Agents and Development\n- @shawmakesmagic promoted \"The Org,\" a tool built on Eliza for tracking team progress and customer support with one-click agents for various platforms\n- @shawmakesmagic shared how Eliza can be deployed to enable users to chat with documentation in minutes\n- @shawmakesmagic mentioned an \"Auto Agent Dev\" tool that can take over a user's computer with full access\n- @shawmakesmagic praised a launch by @comput3ai about \"Gud tech\" as \"Best launch so far\"\n- @elizaOS tweeted \"trust me - this is the plan\" and in a separate tweet stated that \"alignment ≠ conformity\"\n- Sources: https://twitter.com/shawmakesmagic/status/1921657337019773332, https://twitter.com/shawmakesmagic/status/1921662570764681485, https://twitter.com/shawmakesmagic/status/1921663179555279029, https://twitter.com/shawmakesmagic/status/1921638239288373352, https://twitter.com/shawmakesmagic/status/1921603549013692696, https://twitter.com/comput3ai/status/1921602632092676217, https://twitter.com/elizaOS/status/1921531985283133712, https://twitter.com/elizaOS/status/1921575522129383672\n\n### Web Browsers and Technology\n- @dankvr commented that \"the brave team is receptive and quick to implement ideas based on user feedback\" in a conversation with @gakonst and @zooko\n- @dankvr encouraged supporting \"our allies\" in the browser context\n- @dankvr responded to @Higgisp and @theo with \"There is no second best,\" possibly referring to browser preferences\n- Sources: https://twitter.com/dankvr/status/1921614528342524123, https://twitter.com/dankvr/status/1921636791901110779\n\n## GitHub Activity for elizaOS/eliza\n\n### Pull Requests\n- PR #4512 by ChristopherTrimboli cleaned up organization agent and environment loading code\n- PR #4533 by 0xbbjoker fixed missing extensions for migrations\n- PR #4554 by 0xbbjoker added MySQL support to the 'degen' component\n- PRs #4535, #4538, and #4543 by yungalgo implemented 'ELIZA290/part-2-plugins-agent-cli-commands' functionality\n- Sources: https://github.com/elizaOS/eliza/pull/4512, https://github.com/elizaOS/eliza/pull/4533, 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\n\n### Issues\n- Issue #4528 by AndreaRettaroli focused on improving Eliza in TEE oasis\n- Issue #4536 by BinaryBluePeach reported an error where the system cannot find the module '@elizaos/core'\n- Sources: https://github.com/elizaOS/eliza/issues/4528, https://github.com/elizaOS/eliza/issues/4536\n\n### Repository Statistics\n- May 11-12, 2025: 10 new PRs with 16 merged, 1 new issue, and 13 active contributors\n- May 12-13, 2025: 20 new PRs with 7 merged, 1 new issue, and 11 active contributors\n- Sources: githubStatsSummary, githubStatsSummary" }, "ai_news_elizaos_daily_discord_json_2025-05-11": { "filename": "2025-05-11.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-11", "date": 1746921600, "stats": { "totalMessages": 143, "totalUsers": 27 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat segment shows minimal technical discussion. There is a brief mention of beta testers being sought, and a team member (shaw) discussing challenges with collecting contributor wallet addresses for a potential airdrop. Shaw mentions they're working on tooling to better collect contributor wallets in the future. There's also a request for Rust developers. Most of the conversation revolves around questions about a \"dood airdrop\" with uncertainty about its status, with shaw indicating they have limited information about it. The technical content is sparse with no concrete implementations or solutions discussed in depth.\n\n## 2. FAQ\nQ: Any news about DOOD airdrop? (asked by sukrucildirr) A: \"I have no idea about dood airdrop tbh\" (answered by Osint (aka not_a_dev_ai)) and \"i have no info on the airdrop though, sorry\" (answered by shaw)\nQ: When will you collect wallet addresses for doodle drop? (asked by sukrucildirr) A: Unanswered\n\n## 3. Help Interactions\nHelper: shaw | Helpee: sukrucildirr | Context: Explaining the situation with wallet collection for airdrops | Resolution: Partial - explained they asked for wallets last minute and are working on tooling for future wallet collection\n\n## 4. Action Items\nTechnical: Working on tooling to collect contributor wallets | Description: Development of a system to better track contributor wallet addresses for future airdrops | Mentioned By: shaw\nFeature: Beta testers recruitment | Description: Looking for new beta testers for an unspecified project | Mentioned By: Blazo101", "messageCount": 22, "userCount": 11 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around troubleshooting Eliza agent setup and plugin issues. Users encountered problems with environment configuration, model selection, and plugin integration. Key technical discussions included: (1) API connectivity issues between services in WSL2 where Postman requests worked but backend-to-backend calls failed with 502 errors; (2) Configuration challenges with local AI models being downloaded despite environment settings to use external models; (3) Plugin installation and build errors, particularly with the Twitter plugin; (4) Discord integration configuration problems; and (5) Global configuration file management. Several users shared solutions involving proper .env file placement, build commands, and plugin configuration approaches. The conversation highlights the importance of correct environment variable configuration and understanding the plugin architecture in the Eliza system.\n\n## 2. FAQ:\nQ: Why does my backend project fail to call \"http://localhost:3000/agents\" with a 502 error when Postman works? (asked by scooter8992) A: Unanswered\nQ: Why does my agent keep downloading a local model despite setting USE_LOCAL_AI=false? (asked by scooter8992) A: Unanswered\nQ: How to install the new version of eliza on windows? (asked by Zakito11) A: wsl is recommended (answered by Deniz)\nQ: Is there a simple answer to stop Twitter spam and get Elisa to only post and reply to tagged messages? (asked by Sthx) A: Unanswered\nQ: How can I use LLM from OpenAI or grok instead of llama? (asked by pupathebig) A: 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 (answered by scooter8992)\n\n## 3. Help Interactions:\nHelper: scooter8992 | Helpee: pupathebig | Context: Twitter plugin not respecting TWITTER_DRY_RUN=true setting | Resolution: Suggested adding LOG_LEVEL=debug to .env and checking Discord gateway intents\nHelper: scooter8992 | Helpee: scooter8992 | Context: Discord client not loading when agent starts | Resolution: Suggested adding runtime event listener code to debug Discord connection\nHelper: scooter8992 | Helpee: scooter8992 | Context: Proper .env file placement | Resolution: Clarified that .env should be in the root folder, which improved CLI output\n\n## 4. Action Items:\nType: Technical | Description: Fix Twitter plugin to properly respect TWITTER_DRY_RUN=true setting | Mentioned By: pupathebig\nType: Technical | Description: Investigate 502 error when backend service calls Eliza API while Postman works | Mentioned By: scooter8992\nType: Technical | Description: Fix issue with local models being downloaded despite configuration for external models | Mentioned By: scooter8992\nType: Technical | Description: Fix plugin build error: \"Module '@elizaos/core-plugin-v1' has no exported member 'Plugin'\" | Mentioned By: pupathebig\nType: Documentation | Description: Create guide for proper environment configuration to use external models instead of local ones | Mentioned By: scooter8992\nType: Documentation | Description: Document global configuration file location and purpose | Mentioned By: scooter8992\nType: Feature | Description: Implement option to restrict Twitter bot to only post and reply to tagged messages | Mentioned By: Sthx", "messageCount": 64, "userCount": 8 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Analysis of \"fun\" Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around cryptocurrency trading discussions rather than technical content. Users discuss price movements of tokens like COM and ELI5 on the auto.fun platform. There's mention of COM reaching all-time highs due to promotion by an influencer with 50,000 followers. Nick dask advises taking profits at the all-time high, warning about potential retracement. One technical issue was reported by gummy regarding claiming fees from dev wallet creation not working. There's also a brief discussion about a potential community meme launch on autofun, with wire offering to lead it with a team of artists, though xell0x indicates a project called ELI5 already exists for this purpose. Wire criticizes the existing ticker and meme approach, suggesting they could build something better, while xell0x defends ELI5 as being connected to \"ai16z\" and \"elizaOS v2.\"\n\n## 2. FAQ\nQ: Does anyone know why COM is running? (asked by hxf) A: Because a KOL (key opinion leader) with 50k followers called it. (answered by Nick dask)\nQ: Who is launching today? (asked by Remyy) A: It's the weekend. (answered by Osint (aka not_a_dev_ai))\n\n## 3. Help Interactions\nHelper: Nick dask | Helpee: hxf | Context: hxf asked why COM token was running in price | 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## 4. Action Items\nTechnical: Fix issue with claiming fees from dev wallet creation | Description: User reported that claiming fees from dev wallet creation does not work | Mentioned By: gummy\nFeature: Organize a community meme launch on autofun | Description: Create a well-planned launch with a team of artists to create something \"really cool\" | Mentioned By: wire", "messageCount": 54, "userCount": 11 }, { "channelId": "1362864274862768450", "channelName": "fun-support", "summary": "The chat segment is very brief, containing only three messages. A user named \"gummy\" reported an issue with fee collection from their deployment, where the system indicated successful claims but no fees appeared either in the interface or on-chain. Another user \"Osint\" suggested submitting a help request through the page interface. Separately, user \"Curtisdonthurtus\" reported seeing 30-40 fake images with the \"czai\" ticker appearing when sorting by \"New\" on an unspecified platform.", "messageCount": 3, "userCount": 3 } ] } }, "ai_news_elizaos_daily_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_daily_dev_json_2025-05-11": { "filename": "2025-05-11.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-11", "date": 1746921600, "stats": { "totalMessages": 8, "totalUsers": 3 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "The chat segment is very brief with only two participants. One user (joaointech) shared a website they're developing called plinkoincinerator.com and requested technical feedback. Another user (ualp.) asked about AI Agent Dev School recordings for v2, specifically inquiring about the availability of recordings beyond what they found on YouTube. No technical discussions, decisions, or problem-solving occurred in this limited exchange.", "messageCount": 3, "userCount": 2 }, { "channelId": "1327493511406293016", "channelName": "🎤｜plug-your-projects", "summary": "# Analysis of \"🎤｜plug-your-projects\" Channel\n\n## 1. Summary\nThe channel had minimal activity during the analyzed period. A user named joaointech briefly mentioned developing a website called plinkoincinerator.com and requested feedback from the community. No technical discussions, problem-solving, or implementations were shared in this short message. The post appears to be a simple project announcement seeking opinions rather than a detailed technical discussion.\n\n## 2. FAQ\nQ: No significant questions were asked in this chat segment.\n\n## 3. Help Interactions\nNo significant help interactions occurred in this chat segment.\n\n## 4. Action Items\nFeature: Community feedback needed for plinkoincinerator.com website | Description: Developer is seeking opinions on the project | Mentioned By: joaointech", "messageCount": 1, "userCount": 1 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Analysis of Discord Chat in 🤖｜agent-dev-school\n\n## 1. Summary\nThe chat segment contains a brief conversation between users ualp. and Ruby about AI Agent Dev School content for v2 by Shaw. Ruby initially states there's one comprehensive official dev school program covering everything from basic architecture to advanced memory systems and multimodal capabilities. When ualp. asks for clarification about the content, mentioning they only see a basic CLI video (about 1 hour 15 minutes long), Ruby acknowledges that the current video only covers CLI basics. Ruby clarifies that advanced topics like memory systems, multi-agent architectures, and custom plugins are still in development and coming soon. In the meantime, Ruby suggests using the Discord server, particularly the #agent-dev channel, as a resource for discussions on advanced features like memory implementations.\n\n## 2. FAQ\nQ: Is there only one AI Agent Dev School for v2 by Shaw? (asked by ualp.) A: Yes, currently there's just one official dev school program by Shaw, though it's still in development (answered by Ruby)\nQ: Are you referring to the new AI Agent Dev School video that's about an hour and 15 minutes long? (asked by ualp.) A: Yes, the current video only covers CLI basics, with advanced topics coming soon (answered by Ruby)\n\n## 3. Help Interactions\nHelper: Ruby | Helpee: ualp. | Context: ualp. seeking information about advanced agent development content | Resolution: Ruby clarified that advanced topics are still in development and suggested using Discord's #agent-dev channel for discussions on memory implementations\n\n## 4. Action Items\nDocumentation: Advanced curriculum covering memory systems, multi-agent architectures, and custom plugins | Mentioned By: Ruby\nFeature: Release of advanced AI Agent Dev School content beyond CLI basics | Mentioned By: Ruby", "messageCount": 4, "userCount": 2 } ] } }, "ai_news_elizaos_daily_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_hyperfy_daily_json_2025-05-11": { "filename": "2025-05-11.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-11", "date": 1746921600, "stats": { "totalMessages": 93, "totalUsers": 13 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily focused on post-processing effects in Hyperfy worlds and their impact on visual appearance. MetaRick raised concerns about post-processing darkening white backgrounds and video playback, particularly when aiming for pure white environments. The technical issue was identified as tone mapping in the post-processing pipeline, which affects colors regardless of material settings (lit or unlit). Ashxn explained that the AgX tone mapping was causing the effect, and when combined with sunlight, white materials were pushed into HDR range triggering bloom effects. Several solutions were explored: turning the sun intensity to 0, using emissive materials (which only partially worked), and potentially creating a hyp to disable tone mapping. The conversation also briefly touched on favicon implementation for worlds, with Ashxn mentioning plans to create a pipeline that would generate various icon sizes from a single SVG upload, enabling worlds to function more like mobile apps with proper \"add to homescreen\" support.\n\n## 2. FAQ\nQ: Is there a way to turn post processing off as world owner so it can't be turned on by user? (asked by MetaRick) A: No direct answer provided, but discussion revealed it's not currently possible.\nQ: What do you mean by \"stack\"? (asked by Ashxn) A: The post processing (stack) - Unity terminology for post-processing effects (answered by MetaRick)\nQ: Do unlit materials ignore post processing? (asked by MetaRick) A: No, they ignore light information but post-processing still affects them (answered by vox)\nQ: What's causing the white background to appear darker with post-processing on? (asked by MetaRick) A: It's the tone mapping in the post-processing pipeline using AgX (answered by Ashxn)\n\n## 3. Help Interactions\nHelper: Ashxn | Helpee: MetaRick | Context: White backgrounds appearing darker with post-processing enabled | Resolution: Identified the issue as tone mapping and explained how sunlight pushes white colors into HDR range causing bloom\nHelper: vox | Helpee: MetaRick | Context: Seeking alternative solutions for white backgrounds | Resolution: Suggested using white emissive materials with strength at 1, though it was only partially effective\nHelper: MetaRick | Helpee: MetaRick | Context: Finding a way to maintain pure white backgrounds | Resolution: Self-discovered that turning the sun intensity to 0 fixes the issue\n\n## 4. Action Items\nTechnical: Create a hyp to disable tone mapping for color-sensitive applications | Description: Allow disabling of tone mapping effects in post-processing | Mentioned By: MetaRick\nFeature: Add favicon customization to world settings | Description: Allow world creators to set custom favicons for their worlds | Mentioned By: 0mka\nTechnical: Implement a pipeline for favicon generation | Description: Create system to generate multiple icon sizes from a single SVG upload for proper mobile app integration | Mentioned By: Ashxn\nFeature: Support \"add to homescreen\" functionality for worlds | Description: Enable worlds to function like mobile apps with proper homescreen integration | Mentioned By: Ashxn", "messageCount": 69, "userCount": 10 }, { "channelId": "1330373197203505185", "channelName": "🤖│agents", "summary": "# Discord Chat Analysis for \"🤖│agents\" Channel\n\n## 1. Summary\nThe chat segment contains a brief discussion about cryptocurrency on-ramps and a new platform (likely related to Coinbase) that standardizes wallet API integration. Participants speculate about how the platform addresses on-ramp issues for converting fiat currency to cryptocurrency. They discuss potential regulatory implications, particularly around off-boarding funds, suggesting that users might be able to load funds but would need full documentation to withdraw. The conversation touches on the benefits of using cryptocurrency for online stores to save on credit card processing fees, as well as the advantages of quicker settlement times and the ability for token holders to exchange directly into other tokens without bank settlement.\n\n## 2. FAQ\nQ: How did they solve the on-ramp issue? (asked by general hyper) A: Possibly through standardizing Coinbase's wallet API and establishing partnerships rather than purely technical solutions (answered by maximus)\nQ: How might regulators treat this new platform? (asked by maximus) A: Possibly by regulating the off-boarding process, requiring full documentation to withdraw funds (answered by maximus)\nQ: What are the main benefits of this platform? (asked by general hyper) A: Quicker settlement for transaction parties and ability for token holders to exchange directly into other tokens without bank settlement (answered by maximus)\n\n## 3. Help Interactions\nHelper: maximus | Helpee: general hyper | Context: Confusion about what was meant by \"dollars/credit has to become stables\" | Resolution: maximus clarified after getting additional context about on-ramp necessity\n\n## 4. Action Items\nTechnical: Investigate how Coinbase's wallet API standardization works for potential integration | Description: Understanding the technical implementation of the new on-ramp solution | Mentioned By: general hyper\nFeature: Consider cryptocurrency payment options for online stores | Description: Implementing crypto payments to save on credit card processing fees | Mentioned By: general hyper", "messageCount": 13, "userCount": 2 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "The chat segment is extremely brief with minimal technical content. There appears to be a brief mention by HypPrivakos about having a backend ready for importing something (context not specified) and needing to finish the frontend portion. No detailed technical discussions, decisions, or problem-solving occurred in this limited exchange.", "messageCount": 6, "userCount": 4 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "Ashxn announced the addition of a new image option to the world menu and loading screens on the Chill Hyperfy platform. This update appears to reintroduce a \"v1 loader\" that was previously used and well-received by users. The announcement was met with positive feedback from community members, with no complaints mentioned about the previous version, which influenced the decision to bring it back.", "messageCount": 5, "userCount": 3 } ] } }, "ai_news_hyperfy_daily_md_2025-05-11": { "filename": "2025-05-11.md", "content": "# Hyperfy Discord - 2025-05-11\n\n## Overall Discussion Highlights\n\n### Visual Rendering & Post-Processing\n- **Post-Processing Effects Issue**: MetaRick identified that post-processing in Hyperfy worlds darkens white backgrounds and affects video playback, particularly problematic when aiming for pure white environments.\n- **Technical Root Cause**: Ashxn explained that AgX tone mapping in the post-processing pipeline affects colors regardless of material settings. When combined with sunlight, white materials are pushed into HDR range, triggering bloom effects.\n- **Workarounds Discovered**:\n - Setting sun intensity to 0 fixes the issue\n - Using emissive materials provides partial improvement\n - A potential hyp to disable tone mapping was discussed as a future solution\n\n### Platform Updates\n- **Loading Screen Enhancement**: Ashxn announced the reintroduction of the \"v1 loader\" to world menu and loading screens on Chill Hyperfy, responding to positive user feedback about the previous version.\n- **Favicon Implementation**: Discussion about adding favicon customization to world settings, with plans to create a pipeline generating various icon sizes from a single SVG upload.\n- **Mobile Integration**: Plans to enable worlds to function more like mobile apps with proper \"add to homescreen\" support.\n\n### Cryptocurrency Integration\n- **On-Ramp Solutions**: Brief discussion about a new platform (likely Coinbase-related) that standardizes wallet API integration for converting fiat currency to cryptocurrency.\n- **Regulatory Considerations**: Speculation that users might be able to load funds easily but would need full documentation to withdraw.\n- **Business Benefits**: Cryptocurrency payments for online stores could save on credit card processing fees, offer quicker settlement times, and allow token holders to exchange directly into other tokens without bank settlement.\n\n### Development Status\n- HypPrivakos mentioned having a backend ready for importing (context unspecified) and needing to finish the frontend portion.\n\n## Key Questions & Answers\n\n**Q: Is there a way to turn post processing off as world owner so it can't be turned on by user?** \nA: No direct answer provided, but discussion revealed it's not currently possible.\n\n**Q: Do unlit materials ignore post processing?** \nA: No, they ignore light information but post-processing still affects them (answered by vox)\n\n**Q: What's causing the white background to appear darker with post-processing on?** \nA: It's the tone mapping in the post-processing pipeline using AgX (answered by Ashxn)\n\n**Q: How did they solve the on-ramp issue?** \nA: Possibly through standardizing Coinbase's wallet API and establishing partnerships rather than purely technical solutions (answered by maximus)\n\n**Q: How might regulators treat this new platform?** \nA: Possibly by regulating the off-boarding process, requiring full documentation to withdraw funds (answered by maximus)\n\n## Community Help & Collaboration\n\n1. **White Background Rendering Issue**\n - **Helper**: Ashxn\n - **Helpee**: MetaRick\n - **Context**: White backgrounds appearing darker with post-processing enabled\n - **Resolution**: Identified the issue as tone mapping and explained how sunlight pushes white colors into HDR range causing bloom\n\n2. **Alternative Solutions for White Backgrounds**\n - **Helper**: vox\n - **Helpee**: MetaRick\n - **Context**: Seeking alternative solutions for white backgrounds\n - **Resolution**: Suggested using white emissive materials with strength at 1, though it was only partially effective\n\n3. **Cryptocurrency Terminology Clarification**\n - **Helper**: maximus\n - **Helpee**: general hyper\n - **Context**: Confusion about what was meant by \"dollars/credit has to become stables\"\n - **Resolution**: maximus clarified after getting additional context about on-ramp necessity\n\n## Action Items\n\n### Technical\n- Create a hyp to disable tone mapping for color-sensitive applications (Mentioned by MetaRick)\n- Implement a pipeline for favicon generation from SVG uploads (Mentioned by Ashxn)\n- Investigate how Coinbase's wallet API standardization works for potential integration (Mentioned by general hyper)\n- Complete frontend for import functionality (Mentioned by HypPrivakos)\n\n### Feature\n- Add favicon customization to world settings (Mentioned by 0mka)\n- Support \"add to homescreen\" functionality for worlds (Mentioned by Ashxn)\n- Consider cryptocurrency payment options for online stores to reduce processing fees (Mentioned by general hyper)" }, "github_summaries_daily_2025-05-12": { "filename": "2025-05-12.md", "content": "# ElizaOS Daily Update (May 12, 2025)\n\n## OVERVIEW \nToday, the ElizaOS team focused on bug fixes and minor improvements across various components of the framework. Key enhancements included better logging in the bootstrap plugin and resolution of environment issues. The team also addressed several integration and functionality errors, contributing to the overall stability of the system.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Bug Fixes\n- Improved handling of undefined properties in entity and room details to prevent errors ([#4548](https://github.com/elizaos/eliza/pull/4548)).\n- Resolved regression issues related to environment resolution in the CLI package ([#4547](https://github.com/elizaos/eliza/pull/4547)).\n- Fixed an error related to the OpenAI plugin not exporting the necessary URL for text embedding ([#4537](https://github.com/elizaos/eliza/pull/4537)).\n- Corrected integration test imports to ensure proper functionality ([#4541](https://github.com/elizaos/eliza/pull/4541)).\n- Implemented a passthrough function to prevent LLM plugins from breaking ([#4544](https://github.com/elizaos/eliza/pull/4544)).\n\n### Minor Improvements\n- Removed unnecessary banner display in CLI helper text for a more uniform user experience ([#4546](https://github.com/elizaos/eliza/pull/4546)).\n- Updated environment naming conventions for the project manager agent to enhance consistency ([#4549](https://github.com/elizaos/eliza/pull/4549)).\n\n## CLOSED ISSUES\n\n### Twitter Plugin Issues\n- Resolved the issue of Twitter interactions being fetched without implemented reactions ([#4181](https://github.com/elizaos/eliza/issues/4181)).\n- Fixed the dyld error preventing the use of Twitter spaces in the plugin ([#4180](https://github.com/elizaos/eliza/issues/4180)).\n\n### Documentation and Tutorial Fixes\n- Addressed a bug related to the tutorial on building a social AI agent, ensuring the embedded video functions correctly ([#3880](https://github.com/elizaos/eliza/issues/3880)).\n- Fixed a Unicode escape error in log entries for the `pglite` model type ([#4457](https://github.com/elizaos/eliza/issues/4457)).\n\n## NEW ISSUES\n\n### Module Resolution Challenges\n- A new issue was reported regarding the inability to find the module '@elizaos/core' or its type declarations, indicating potential problems with module resolution in the project ([#4536](https://github.com/elizaos/eliza/issues/4536))." }, "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