{ "date_generated_for": "2025-05-09", "ai_news_elizaos_discord_md_2025-05-08": { "filename": "2025-05-08.md", "content": "# elizaOS Discord - 2025-05-08\n\n## Overall Discussion Highlights\n\n### Team & Community Updates\n- **Shaw's Twitter Break**: Shaw (key team member) temporarily suspended his Twitter account, causing community concern. Jin and others reassured the community that Shaw is taking a break but still working on development.\n- **ElizaOS v2 Development**: Community members expressed interest in the upcoming ElizaOS v2, though specific details or timelines weren't provided.\n- **Token Distribution Analysis**: Discussion about AI16Z having more decentralized token distribution (69% held by top 100) compared to VIRTUAL (93% held by top 100).\n\n### Technical Discussions\n- **AI Model Configuration Issues**: Users troubleshooted ElizaOS defaulting to local AI models despite configuration settings specifying external providers like Groq. The solution involved properly setting environment variables in the .env file.\n- **Discord Plugin Error**: A database error (\"duplicate key value violates unique constraint\") was reported specifically with the Discord plugin.\n- **Twitter Agent Integration**: Several users discussed Twitter agent integration and API quota issues, with suggestions to use Heurist as a free alternative.\n\n### Auto.fun Platform Issues\n- **PrinceSCRT Token Launch Problems**: A problematic token launch called \"PrinceSCRT\" by Secret Network on the auto.fun platform resulted in accusations of a \"rug pull\" when the developer wallet sold a significant portion of tokens post-launch.\n- **Refund Policy Controversy**: The auto.fun team stated they wouldn't issue refunds for the PrinceSCRT incident as they have \"no control over what the team does post launch,\" causing community frustration.\n- **Platform Improvement Suggestions**: Users suggested implementing a subscription model for early access to partner projects and stricter verification criteria for launches.\n\n### Contributor Recognition\n- **DOOD Airdrop Eligibility**: Discussion about ElizaOS contributor eligibility for a potential DOOD airdrop, particularly regarding GitHub contributors.\n- **Wallet Collection Challenges**: Jin mentioned challenges in collecting Solana wallet addresses from contributors for rewards distribution.\n\n## Key Questions & Answers\n\n### Team & Development\n- **Q**: Why did Shaw's account get suspended? \n **A** (jin): He's taking a Twitter detox break.\n\n- **Q**: Is there any airdrop for those who hold 10k eliza or more? \n **A** (Osint): Sorry, no.\n\n- **Q**: I read that ElizaOS contributors could be eligible for DOOD airdrop? \n **A** (Osint): Contributors to codebase.\n\n- **Q**: I had a PR merged into Eliza GH, how does that link to my wallet for dood? \n **A** (jin): Send your SOL address to kenk.\n\n- **Q**: Where can you view the AUM for ai16z? \n **A** (Kenk): I think it's on DAOs.fun.\n\n### Technical Support\n- **Q**: How do I add plugin twitter to character? \n **A** (odilitime): Documentation is available at https://docs.eliza.how/blog/twitter-agent-guide.\n\n- **Q**: How do I fix ElizaOS falling back to local AI despite configuration? \n **A** (odilitime): Configure the .env file at the root with your API keys and configure characters for plugin-groq.\n\n### Auto.fun Platform\n- **Q**: Will there be a refund for the PrinceSCRT issue? \n **A** (jasyn_bjorn): We unfortunately have no control over what the team does post launch even after we vet them thoroughly beforehand. Sorry, but we won't be issuing refunds for this launch.\n\n- **Q**: When will it [token] migrate? \n **A** (eskender.eth): It's migrated.\n\n## Community Help & Collaboration\n\n1. **ElizaOS Configuration Support**:\n - odilitime helped users troubleshoot ElizaOS Docker image falling back to local AI despite configuration, suggesting proper .env file setup and character configuration for plugin-groq.\n\n2. **Twitter API Quota Solutions**:\n - odilitime and keygray_mm suggested using Heurist as a free alternative when mahee encountered Twitter API quota issues.\n\n3. **Contributor Reward Coordination**:\n - Jin instructed contributors to send their Solana addresses to kenk for potential rewards.\n - Osint offered to help collect Solana addresses and process a list to get addresses for jin.\n\n4. **Token Launch Information**:\n - Kenk shared an article link about the Doodles DOOD new Blood Fund TGE when sukrucildirr asked about the upcoming event.\n - eskender.eth explained to vas why partners don't always share contract addresses before launch, clarifying it's about control and limiting people at point of launch.\n\n## Action Items\n\n### Technical\n- Continue development of ElizaOS v2 (Mentioned by: xell0x)\n- Complete analysis of Discord contributors for rewards (Mentioned by: jin)\n- Collect Solana wallet addresses from contributors (Mentioned by: jin)\n- Fix Discord plugin issue causing \"duplicate key value violates unique constraint 'memories_pkey'\" error (Mentioned by: odilitime)\n- Test interactive 24/7 unreal engine elizaOS metahuman (Mentioned by: odilitime)\n- Update/push multistream-client and air3market-plugin for V2 (Mentioned by: odilitime)\n- Remove fake coins from the platform before real token launches (Mentioned by: velja)\n- Investigate the pscrt token situation (Mentioned by: hxf)\n- Require partners to share contract address before launching (Mentioned by: vas)\n- Implement a subscription model for early access to partner projects (Mentioned by: MDMnvest)\n- Fix bugs in the auto.fun platform as it \"needs bug fixes and to mature\" (Mentioned by: nasdaq.ai)\n- Establish stricter criteria for partner verification (Mentioned by: vas)\n\n### Documentation\n- Create Pope AI X agent (Mentioned by: groggs)\n- Create clearer instructions for configuring external AI providers like Groq (Mentioned by: odilitime)\n- Provide clearer communication about risks involved with new token launches (Mentioned by: jasyn_bjorn)\n\n### Feature\n- Feature Eli5 more prominently as mascot on auto.fun, Shaw's and elizaOS' Twitter (Mentioned by: xell0x)\n- Create crypto dev GitHub graph to plot relationships among crypto developers (Mentioned by: Osint)\n- Lock up ELI5 tokens to get early allocation to partner projects, similar to Virtual (Mentioned by: ryanthelad)" }, "ai_news_elizaos_discord_md_2025-05-07": { "filename": "2025-05-07.md", "content": "# elizaOS Discord - 2025-05-07\n\n## Overall Discussion Highlights\n\n### ElizaOS Platform & Development\n- Discussions about the upcoming ElizaOS v2 release, though no specific launch date was confirmed\n- Documentation site (eliza.how) experienced downtime, with team member jin confirming they were working on fixing it\n- Users reported \"Service instrumentation not found in runtime\" errors related to service registration\n- Installation problems were common, particularly with the Twitter client plugin\n- Local LLM integration issues with LMStudio and Ollama where agents weren't responding properly\n- A developer mentioned reverting an AI docs RAG agent due to hallucination issues\n\n### Token Economics & Auto.fun\n- Significant discussion about the relationship between ElizaOS success and AI16Z token value\n- Team members explained that auto.fun serves as a launchpad for agent teams building with ElizaOS\n- A portion of auto.fun fees are used for AI16Z token buybacks\n- Community members expressed bullish sentiment toward the ELI5 token\n\n### Major Incident: $FAN Token Launch Error\n- Team member \"ben\" announced the launch of $FAN by Sigma Music but posted an incorrect contract address\n- The error remained live for approximately 9 minutes before correction\n- Multiple users reported financial losses from purchasing the wrong token\n- Team implemented a refund process through their Telegram bot\n- By 16:25, affected users began confirming they had received refunds\n- Team outlined preventative measures for future launches, including requiring direct confirmation from partners\n\n### Doodles (DOOD) Airdrop\n- Questions arose about a Doodles (DOOD) airdrop for ElizaOS contributors\n- Team clarified that GitHub contributors to the framework are considered for the airdrop, not token holders\n- Confusion about eligibility criteria and claim process remains\n\n## Key Questions & Answers\n\n**Q: How does it benefit AI16Z if Eliza OS does well?** \nA: \"The more people deploy ElizaOS agents or agent-adjacent tokens, the more people will use auto.fun, which buys back the token.\" (answered by eskender.eth)\n\n**Q: Is it true that AI16Z holders are not eligible for the DOOD airdrop and are not considered Eliza contributors?** \nA: \"Token holders are not contributors to the framework, they are investors.\" (answered by Kenk)\n\n**Q: How will Eliza contributors be able to claim their Doodle airdrop?** \nA: \"We don't have any specifics, keep an eye on their announcement.\" (answered by Kenk)\n\n**Q: What happened with the $FAN launch?** \nA: \"The wrong CA was posted on twitter\" (answered by vas)\n\n**Q: How does that even happen?** \nA: \"We removed everyone from the process to keep it as under wraps as possible, so there was no check on the final link posted\" (answered by ben)\n\n**Q: Is there a project launching today?** \nA: \"There's a launch planned for each day but beyond that I don't have any more information\" (answered by Kenk)\n\n**Q: Why was today's launch so early?** \nA: \"It is not their choice\" (answered by who)\n\n## Community Help & Collaboration\n\n1. **ElizaOS Contribution Guidance**\n - Helper: Kenk\n - Context: User asking how to contribute to ElizaOS\n - Resolution: Kenk explained contribution can be through framework development or building plugins/agents\n\n2. **ElizaOS-AI16Z Relationship Explanation**\n - Helper: eskender.eth\n - Context: Explaining how ElizaOS success benefits AI16Z token\n - Resolution: Provided a mental model comparing it to WordPress ecosystem where network effects enable revenue opportunities\n\n3. **Installation Troubleshooting**\n - Helper: odilitime\n - Context: Error when running elizaos create with beta 45\n - Resolution: Installing bun resolved the issue\n\n4. **Node Version Compatibility**\n - Helper: odilitime\n - Context: Troubleshooting node version compatibility\n - Resolution: Identified node version v20.18.0\n\n5. **$FAN Launch Incident Response**\n - Helper: 🔥🔥🔥 and eskender.eth\n - Context: Users lost money due to incorrect contract address\n - Resolution: Instructed users to send transaction details to Telegram bot for refunds, which were processed within hours\n\n## Action Items\n\n### Technical\n- Fix the documentation site that's currently down (mentioned by jin)\n- Release ElizaOS v2 (mentioned by xell0x)\n- Fix \"Service instrumentation not found in runtime\" errors in custom service registration (mentioned by odilitime)\n- Resolve Twitter client plugin installation issues (mentioned by rferrari)\n- Fix XML parsing errors in Twitter integration (mentioned by odilitime)\n- Improve local LLM integration with LMStudio and Ollama (mentioned by odilitime)\n- Implement verification system requiring partner confirmation for all outbound URLs (mentioned by eskender.eth)\n- Process refunds to all users affected by the incorrect contract address (mentioned by 🔥🔥🔥)\n- Delete fake token listings before real launches (mentioned by velja)\n- Fix UI issue where token profile pages initially load with claim fees option before redirecting (mentioned by abhi_ironman)\n- Investigate possibility of MEV-protected bonding curves (mentioned by Kenk)\n\n### Documentation\n- Clarify the relationship between ElizaOS success and AI16Z token value (mentioned by CRAY)\n- Create documentation for implementing custom actions in agents (mentioned by odilitime)\n- Update CLI documentation (mentioned by odilitime)\n- Provide clear post-mortem of the $FAN launch incident (mentioned by eskender.eth)\n\n### Feature\n- Provide more information about agent azile.eth (mentioned by abhi_ironman)\n- Implement login page functionality for client (mentioned by odilitime)\n- Support per-user agent instances (mentioned by odilitime)\n- Add interval posting capability to Discord plugin (mentioned by odilitime)\n- Improve verification process for token launches (mentioned by multiple users)" }, "ai_news_elizaos_discord_md_2025-05-06": { "filename": "2025-05-06.md", "content": "# elizaOS Discord - 2025-05-06\n\n## Overall Discussion Highlights\n\n### ElizaOS V2 Development\n- Community members expressed high expectations for ElizaOS V2, with Osint describing it as \"💯\"\n- The beta version is available at www.eliza.how as confirmed by Kenk\n- Shaw has been teasing V2 on Twitter according to xell0x\n- Discussions focused on the platform's shift toward building vertical AI agents with actual use cases\n- Users are interested in how agent tokens will integrate with the V2 ecosystem\n\n### Auto.fun Platform Issues\n- Significant concerns about fake tokens and scams during token launches\n- The Comput3 (COM) token launch highlighted issues with the verification system\n- Users reported suspicious activity where some wallets executed multiple transactions within seconds of launch\n- Auto.fun team (ben, jasyn_bjorn) defended against accusations of insider trading\n- Migration process takes considerable time, causing user frustration\n- Verification system has been improved to reduce verification time to approximately 1 minute\n\n### Technical Challenges\n- Multiple users reported installation problems with ElizaOS CLI across different operating systems:\n - Permission errors on Ubuntu\n - Plugin loading failures on MacOS\n - Database configuration issues, particularly with SQL plugins\n- Plugin verification errors are common across different installation methods\n- Users discussed workarounds including using npx instead of global installation\n- PostgreSQL duplicate key constraints are preventing proper message storage\n- Twitter agent configuration issues were reported by several users\n\n### Community Concerns\n- Verification thresholds for token holders were changed without notice, causing frustration\n- Kenk acknowledged this communication failure, explaining it was done without proper notification\n- Some users expressed concerns about the project's direction and lack of communication\n- Comparisons between Eliza and Virtuals platforms emerged, debating their different approaches\n- Trust issues stemming from previous launches like Doglifeai were mentioned\n\n## Key Questions & Answers\n\n**Q: Is there a beta for the new Eliza OS?** \nA: \"Yeah www.eliza.how\" (Kenk)\n\n**Q: How much of a gamechanger will be elizaOS v2?** \nA: \"ElizaOS V2 is gonna be 💯\" (Osint)\n\n**Q: Are there any trading terminals that support auto.fun?** \nA: \"Solsniper\" (Osint)\n\n**Q: What bots work with Auto.fun?** \nA: \"Solsniper works pre-migration, Axiom post-migration\" (hxf)\n\n**Q: How do we know which token is real vs fake during migrations?** \nA: \"Wait for the verified badge and check the spotlight thread posted after launch\" (ben)\n\n**Q: How many ELI5 tokens are there?** \nA: \"1 billion, 700k cap currently\" (xell0x)\n\n**Q: What will Eli5 be used for?** \nA: \"elizaOS v2 AI agent\" (xell0x)\n\n**Q: Has someone been able to run Eliza with lmstudio or ollama?** \nA: \"Yes, with 1.x version by setting the right .env and telling the character which model to use\" (mtbc)\n\n**Q: Is this going to take time?** (regarding token migration) \nA: \"it takes time to migrate yes\" (Kenk)\n\n## Community Help & Collaboration\n\n- **Auto.fun Trading Tools**: hxf helped Rishu by recommending Solsniper for pre-migration and Axiom for post-migration trading, and provided Twitter links\n- **Fake Token Warnings**: Simon and Xyness actively warned users about fake tokens appearing on Auto.fun, potentially saving users from scams\n- **Installation Troubleshooting**: kandizzy helped Kgood with plugin-sql and plugin-openai installation errors by suggesting installing bun with npm install -g bun\n- **CLI Workarounds**: kandizzy shared a solution for plugins not being accessible after installation on Ubuntu by using npx elizaos start instead of elizaos start\n- **LLM Integration**: mtbc confirmed to kandizzy that Eliza works with ollama in 1.x by setting the correct .env and model configuration\n- **Auto.fun Setup**: Kenk offered to match payment for developers who could help Nicasso set up auto.fun after they offered to pay 500 for assistance\n\n## Action Items\n\n### Technical Tasks\n- Fix plugin loading issues when installing via npm global installation (kandizzy)\n- Address PostgreSQL duplicate key constraint for message storage (kandizzy)\n- Resolve Twitter agent posting functionality issues (kandizzy)\n- Fix plugin installation and verification process (kandizzy)\n- Remove fake/scam tokens from the Auto.fun platform (velja, Veki)\n- Fix slippage reset issue on Auto.fun (who)\n- Investigate stuck migration for token HhTQuq71vQTDKZJ44YwGVPSjRXQQPVUNs6zLoMDLMFUN (Rishu)\n- Implement a system with partner codes for instant token verification (Xyness)\n- Ban all names of upcoming token launches unless from agreed wallet (TMO)\n- Whitelist developer wallets before launch to prevent fake tokens (velja)\n- Fix migration process that takes too long (over an hour in some cases) (Rishu)\n- Prevent bundled transactions that allow some users to buy multiple times in seconds (Pyroman)\n- Announce CA before partner to ensure fair launch (MDMnvest)\n- Set up auto.fun for user willing to pay for assistance (Nicasso)\n- Containerize Eliza and deploy on remote server (yikesawjeez)\n\n### Documentation Needs\n- Create and pin an information post about avoiding scams on Auto.fun (yikesawjeez)\n- Create guide for running Eliza with local LLM solutions (kandizzy)\n- Provide clear examples of character configuration in v2 format (kandizzy)\n- Provide clear communication about token verification thresholds (Kenk)\n\n### Feature Requests\n- Implement proxy plugin for Twitter clients to use different IP addresses (some)\n- Support for lightweight custom plugin combinations (some)\n- Improve discoverability of verified tokens on Auto.fun (ben)\n- Add MEV protection for pre-migrate on Auto.fun (noj)\n- Give Eliza a voice on X (Twitter) to help price stabilize (nasdaq.ai)\n- Create community-only AI agents rather than generic AI agents (xell0x)\n- Develop an AI agent for auto.fun that can achieve viral growth (xell0x)\n- Create a middle-ground solution for deploying Eliza (Ouranos)\n- Integrate auto.fun AI agents with ElizaOS v2 (xell0x)\n- Boost ELI5 to revive trust in the platform (Yuyi)" }, "ai_news_elizaos_dev_md_2025-05-08": { "filename": "2025-05-08.md", "content": "# elizaOS Development Discord - 2025-05-08\n\n## Overall Discussion Highlights\n\n### Multi-Agent Architecture\n- Ruby confirmed that multiple agents can run on a single Postgres database\n- The platform handles memory isolation automatically through namespacing in the database schema\n- Each agent requires a unique name/ID in their configuration to ensure proper separation\n\n### Model Configuration\n- Detailed discussion on setting up tiered models (small, medium, large) in agent configurations\n- Example provided showing how to mix Claude and GPT models for different complexity levels:\n - 'small': 'claude-2.1'\n - 'medium': 'claude-2.1'\n - 'large': 'claude-3'\n- Clarification on adding Anthropic API keys to .env files for Claude model usage\n\n### Package Manager Compatibility\n- Users experienced module resolution issues when mixing npm and Bun\n- Problem occurred specifically when CLI was installed with npm but plugins were being installed with Bun\n- Two solutions were recommended:\n 1. Set `PACKAGE_MANAGER=npm` in the .env file\n 2. Install the CLI with Bun instead of npm using `bun install -g @elizaos/cli@beta`\n\n### Token Clarification\n- Odilitime clarified that \"EDDY\" and \"ELI5\" are characters in the code but not official tokens\n- Only `$ai16z` and `$degenai` are official tokens in the ecosystem\n\n### Community Contributions\n- User \"lost\" worked on adding an Indonesian translation (README_IND.md) to the project\n- Ruby provided detailed guidance on proper PR submission process\n- Discussion highlighted the importance of targeting the correct branch (develop vs. main)\n\n## Key Questions & Answers\n\n**Q: Is it ok to run multiple agents off the same postgres db? Does the platform handle storing all of their memories separately?** \nA: Yes, you can run multiple agents on one postgres db. The platform handles memory isolation by default - each agent gets their own namespace in the db schema. Just make sure you give each agent a unique name/id in their config.\n\n**Q: How do I setup my .env for anthropic models?** \nA: Add `ANTHROPIC_API_KEY=your_key_here` in your .env file. The platform will automatically detect and use it when you specify claude models in your agent config.\n\n**Q: How can I define small, large, etc. models to use different ones in the agent config?** \nA: In your agent's config.json, under the 'models' section, you can specify different model tiers like: 'small': 'claude-2.1', 'medium': 'claude-2.1', 'large': 'claude-3'.\n\n**Q: Why do plugins fail to load with global CLI install but work with npx?** \nA: It's a path resolution issue. When you install the CLI globally with npm, it expects plugins in the npm global path, but the project is using bun's module resolution.\n\n**Q: Is EDDY the V2 agent and ELI5 going to be \"a character\"?** \nA: They are characters in the code, yes. Are the tokens related? No. The only official tokens are $ai16z and $degenai.\n\n**Q: How can I put a Readme file for Indonesian translation in the repository?** \nA: Create a new file called README_IND.md in the root directory of your fork, paste in your translation, commit and push.\n\n**Q: Should I worry about integration-tests and GitHub Actions failures for documentation changes?** \nA: No, those failures are expected for doc changes and only relevant for code changes, not documentation updates.\n\n## Community Help & Collaboration\n\n### Multi-Agent Setup Guidance\nRuby provided comprehensive assistance to Blaze Leclairt on setting up multiple agents with a shared database, explaining memory isolation mechanisms and offering configuration examples for different model tiers.\n\n### Package Manager Troubleshooting\nRuby helped kandizzy resolve module resolution issues between npm and Bun, offering two alternative solutions to maintain consistency in the development environment.\n\n### Translation Contribution Support\nRuby guided user \"lost\" through the entire process of contributing an Indonesian translation:\n- Creating the translation file in the correct location\n- Adding proper language badges\n- Formatting links correctly\n- Targeting the correct branch for the PR\n- Understanding which build errors could be safely ignored for documentation changes\n\nSpartanDev also offered troubleshooting steps for build errors, suggesting cache clearing and clean installation approaches.\n\n### Token Clarification\nOdilitime helped Sidtoshi Vision understand the distinction between characters in the code and official tokens in the ecosystem.\n\n## Action Items\n\n### Technical\n- Use unique AGENT_ID in each agent's config when running multiple agents on a single database (Mentioned by Ruby)\n- Set PACKAGE_MANAGER=npm in .env file when CLI is installed with npm (Mentioned by Ruby)\n- Install CLI with Bun instead of npm for consistency using `bun install -g @elizaos/cli@beta` (Mentioned by Ruby)\n- Fix PR to target develop branch instead of main for contributions (Mentioned by Ruby)\n\n### Documentation\n- Add Indonesian translation README (README_IND.md) to the repository (Mentioned by lost)\n- Ensure all documentation links in README_IND.md point to the correct locations (Mentioned by Ruby)\n- Add language badge to Indonesian README (Mentioned by Ruby)\n- Update documentation regarding CLI installation with Bun as an alternative to npm (Mentioned by sayonara)" }, "ai_news_elizaos_dev_md_2025-05-07": { "filename": "2025-05-07.md", "content": "# elizaOS Development Discord - 2025-05-07\n\n## Overall Discussion Highlights\n\n### Development Issues\n- **Database Migration Errors**: User a4oya4o encountered persistent errors with missing \"_journal.json\" files and failed migrations when creating new projects. Sam-developer attempted troubleshooting by suggesting environment reset commands.\n- **High Database Usage**: Discussion about high Compute Units (CU) on Neon database, identified as likely caused by Discord world sync. Odilitime mentioned plans to rewrite it to use fewer queries.\n- **Documentation Website**: Multiple users reported that the documentation website was down.\n- **Web Client Behavior**: Questions raised about chat persistence in the web client, specifically whether chats disappearing when scrolling or starting new prompts is expected behavior.\n\n### Community Contributions\n- **New Character Additions**: New contributor kaue submitted PRs adding Alfred and Jarvis personalities to the official repository.\n- **Repository Standardization**: kaue identified lack of standardization in character files and absence of a README, offering to submit PRs to address these issues.\n- **GraphQL Adapter Development**: kaue mentioned they're building a GraphQL adapter (referencing issue #131) to simplify subgraph communications and improve agent performance compared to RPC queries.\n\n### Community Building\n- **Plugin Suggestions**: Nisita requested community input for plugin suggestions.\n- **Collaboration Opportunity**: Connection made between Thanh (founder of B.ARMY) and Nisita for potential collaboration on AI projects using ElizaOS.\n- **Upcoming Meetups**: Mentions of meetups in Hong Kong and Thailand.\n\n## Key Questions & Answers\n\n1. **Q**: Why is CU so crazy high on neon? \n **A**: Probably the discord world sync (Odilitime)\n\n2. **Q**: Can I submit a PR to standardize character files and add a README? \n **A**: Implied approval with positive feedback (Ruby)\n\n3. **Q**: Would the community be interested in more character personalities from pop culture? \n **A**: \"Those character additions sound great\" (Ruby)\n\n4. **Q**: Any feedback on the GraphQL adapter for subgraph communications? \n **A**: \"That's brilliant for optimizing subgraph queries\" with offer of \"caching strategies\" (Ruby)\n\n## Community Help & Collaboration\n\n1. **Database Troubleshooting**:\n - **Helper**: sam-developer\n - **Helpee**: a4oya4o\n - **Context**: Database migration errors when creating new projects\n - **Resolution**: Suggested removing ~/.eliza directory and running elizaos start in project folder, though issue persisted\n\n2. **Database Performance**:\n - **Helper**: Odilitime\n - **Helpee**: Scooter\n - **Context**: High CU usage on neon database\n - **Resolution**: Identified discord world sync as likely cause and mentioned plans to optimize\n\n3. **Community Connection**:\n - **Helper**: sayonara\n - **Helpee**: Thanh\n - **Context**: Connected Thanh with Nisita for dev community collaboration\n - **Resolution**: Introduction made, potential future call scheduled\n\n4. **GraphQL Development Support**:\n - **Helper**: Ruby\n - **Helpee**: kaue\n - **Context**: New contributor seeking feedback on character additions and GraphQL adapter\n - **Resolution**: Provided encouragement and offered caching strategies for the GraphQL implementation\n\n## Action Items\n\n### Technical\n- Fix database migration errors with missing meta/_journal.json file (mentioned by a4oya4o)\n- Optimize discord world sync to reduce database query load (mentioned by Odilitime)\n- Standardize character files in the repository (mentioned by kaue)\n- Complete GraphQL adapter for simplified subgraph communications (mentioned by kaue)\n- Implement caching strategies for GraphQL adapter (mentioned by Ruby)\n\n### Documentation\n- Fix documentation website that appears to be down (mentioned by Fenil Modi)\n- Add README to the characters repository (mentioned by kaue)\n\n### Feature\n- Implement chat persistence in web client (mentioned by shiftshapr)\n- Add Twitter post/reply rate limiting capability (mentioned by shiftshapr)\n- Collect community suggestions for new plugins or additions to existing ones (mentioned by Nisita)\n- Add more character personalities (Samwise, Gandalf, Dr. Watson, Sherlock Holmes, Cortana) (mentioned by kaue)\n- Add business-oriented examples using ragKnowledge (mentioned by kaue)" }, "ai_news_elizaos_dev_md_2025-05-06": { "filename": "2025-05-06.md", "content": "# elizaOS Development Discord - 2025-05-06\n\n## Overall Discussion Highlights\n\n### Plugin Architecture & Integration\n- ElizaOS is transitioning to individual repositories for plugins in version 1.x, moving away from the monorepo approach\n- The Ollama plugin is now hosted in a separate repository and requires manual addition to the index.ts file\n- Beta version includes a native Telegram plugin (available at github.com/elizaOS/eliza/tree/v2-develop/packages/plugin-telegram)\n- Users discussed implementation challenges with the Ollama plugin, including errors related to text embedding handlers\n\n### Package Management & Compatibility\n- A significant issue was identified where installing plugins with Bun while running in a Node.js environment creates module resolution conflicts\n- This highlights the importance of consistent package manager usage across the ElizaOS ecosystem\n\n### Model Support & Integrations\n- Questions were raised about Grok model support in ElizaOS Beta 1.0\n- Interest in connecting agents to Open Web UI was expressed\n- Discussion about using agent biographies/autobiographies for knowledge base enhancement\n\n## Key Questions & Answers\n\n**Q: Have anyone used telegram client with latest eliza?** \nA: Beta version includes its own Telegram plugin available at github.com/elizaOS/eliza/tree/v2-develop/packages/plugin-telegram (answered by 0xbbjoker)\n\n**Q: Has someone been able to run eliza2 with ollama?** \nA: For ollama use `plugin-ollama` instead of `plugin-local-ai` (answered by 0xbbjoker)\n\n**Q: Should I add manually in the index.ts?** \nA: These are kinda hardcoded right now so you can manually add and it will work (answered by sayonara)\n\n**Q: Does anyone know why this issue might be happening when I try starting my agent?** (regarding Discord plugin errors) \nA: The issue is caused by installing the plugin with Bun while running in a Node.js environment, creating module resolution conflicts. (answered by Ruby)\n\n## Community Help & Collaboration\n\n### Telegram Integration Support\n- 0xbbjoker helped Sarthak with using the Telegram client in the latest Eliza version\n- Provided GitHub link and configuration instructions for the built-in Telegram plugin\n\n### Ollama Integration Troubleshooting\n- 0xbbjoker advised bob_the_spounge to use plugin-ollama instead of plugin-local-ai when experiencing segmentation faults\n- sayonara guided bob_the_spounge through manually adding the Ollama plugin to index.ts\n- Provided troubleshooting steps including running build after editing and shared the correct GitHub repository link\n\n### Discord Plugin Resolution\n- Ruby helped kandizzy diagnose and fix module resolution errors with the Discord plugin\n- Identified the root cause as a package manager conflict between Bun and Node.js\n- Provided a clear solution: remove the package using Bun first and then reinstall using npm\n\n## Action Items\n\n### Technical\n- Implement proper integration of Ollama with ElizaOS using plugin-ollama from the correct repository (mentioned by sayonara)\n- Fix issue with TEXT_EMBEDDING handler for Ollama plugin (mentioned by bob_the_spounge)\n- Complete migration of plugins to individual repositories for version 1.x (mentioned by sayonara)\n- Remove Discord plugin installed with Bun using 'bun remove @elizaos/plugin-discord' and reinstall with npm (mentioned by Ruby)\n\n### Documentation\n- Create documentation for manually adding plugins to ElizaOS (mentioned by bob_the_spounge)\n- Document package manager compatibility issues and best practices (implied from Ruby's help)\n\n### Feature\n- Add support for Grok model in ElizaOS Beta (mentioned by Bernard)\n- Integrate Open Web UI as a chat interface option for agents (mentioned by LemonS)\n- Explore agent biography/autobiography approach for knowledge base enhancement (mentioned by dEXploarer)" }, "ai_news_elizaos_daily_json_2025-05-08": { "filename": "2025-05-08.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-08", "categories": [ { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "Eliza OS and Agentic AI Development", "text": "@elizaOS shared updates about their AI news show's evolution and announced an event in their Discord to discuss autonomous agentic governance. @dankvr mentioned that Shaw is taking a break from X to focus on the launch of V2. @elizaOS highlighted that their platform enables 'scripting behavior' rather than just scheduling posts, in response to a Bonsai integration. They also announced a builder demo week spotlighting agent-managed DAOs and how elizaOS is integrating into the Eliza community itself. @elizaOS emphasized their commitment to transparent, auditable, and agentic AI, particularly in government applications. @shawmakesmagic recommended Eliza v2 to @liamzebedee, mentioning its drag-and-drop RAG UI in chat and shared a link to a fully agentic RAG website with source code.", "sources": [ "https://twitter.com/dankvr/status/1920282622728536281", "https://twitter.com/elizaOS/status/1920296359451590804", "https://twitter.com/elizaOS/status/1920342076903866405", "https://twitter.com/elizaOS/status/1920474359002501358", "https://twitter.com/elizaOS/status/1920484355433992634", "https://twitter.com/elizaOS/status/1920484359284404460", "https://twitter.com/elizaOS/status/1920564611146760308", "https://twitter.com/shawmakesmagic/status/1920323797174849714", "https://twitter.com/shawmakesmagic/status/1920324483744780306" ], "images": [ "https://pbs.twimg.com/media/GqZDSBGWcAAWx4p.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1920340491255660544/vid/avc1/1280x720/rEa33_nR9zZCfm0C.mp4?tag=21" ] }, { "theme_title": "SigmaX Music Platform and Ecosystem", "text": "@autodotfun shared multiple tweets about SigmaX Music, describing it as 'the hottest music drop this year' and 'an ecosystem' rather than just an album. They quoted a tweet from @SigmaXMusic announcing app revenue sharing for musicians and fans, with 10% of app revenue going back to the community via raffles for Music NFT, Fan Pass, and $FAN holders. @elizaOS highlighted the platform's capabilities, stating 'eliza remixes, fans mint, royalties split' while noting that traditional labels are still asking for MP3s. @autodotfun also mentioned that @SigmaXMusic fans are 'minting bangers, splitting bags' and suggested the platform is 'changing the game' and 'bringing back the fun.'", "sources": [ "https://twitter.com/autodotfun/status/1920395542384763112", "https://twitter.com/autodotfun/status/1920382357376282794", "https://twitter.com/autodotfun/status/1920393800540659784", "https://twitter.com/autodotfun/status/1920394904884085157", "https://twitter.com/autodotfun/status/1920542078179700909", "https://twitter.com/elizaOS/status/1920393005682348390" ], "images": [], "videos": [] }, { "theme_title": "PrinceSCRT Token Launch", "text": "@autodotfun announced the launch of @PrinceSCRT on their platform, describing it as an AI agent from the @SecretNetwork community powered by Secret AI's secure LLM interactions. They explained that the platform uses a fair-launch protocol and Liquidity NFTs to ensure ongoing engagement and stable tokenomics. According to @autodotfun, holding $PSCRT tokens grants exclusive access to private interactions, Secret AI-driven insights, and initiatives empowering African communities. They described the token as 'privacy's not dead – it just went stealth mode' and referred to @PrinceSCRT as 'our prince of fun' and 'the talisMAN.'", "sources": [ "https://twitter.com/autodotfun/status/1920502475175408108", "https://twitter.com/autodotfun/status/1920502477947855018", "https://twitter.com/autodotfun/status/1920502479738859917", "https://twitter.com/autodotfun/status/1920513105596932459", "https://twitter.com/autodotfun/status/1920521069661762006", "https://twitter.com/autodotfun/status/1920521902231040268", "https://twitter.com/autodotfun/status/1920521906668667207", "https://twitter.com/autodotfun/status/1920542504862044243", "https://twitter.com/autodotfun/status/1920548478238757089" ], "images": [ "https://pbs.twimg.com/media/Gqb0CKrW4AAMROG.png" ], "videos": [] }, { "theme_title": "DAOs and Media Influence", "text": "@dankvr shared thoughts on how media shapes policy through public perception, calling it 'the fourth branch of government.' He noted that 'DAOs barely have a media layer right now' and indicated they're working to change that. This tweet was retweeted by @shawmakesmagic. @dankvr also mentioned that a byproduct of their tools is how they're fetching, summarizing, and saving repository issues, PRs, and comments that git itself doesn't have, suggesting that 'having full ownership of our project's data can make right of exit easier.'", "sources": [ "https://twitter.com/dankvr/status/1920268669847790067", "https://twitter.com/dankvr/status/1920321451514618255", "https://twitter.com/shawmakesmagic/status/1920321451514618255" ], "images": [ "https://pbs.twimg.com/media/GqYoS0NW0AA77aT.png", "https://pbs.twimg.com/media/GqYqK22XcAAIyXK.jpg", "https://pbs.twimg.com/media/GqZaLs1WgAE4INv.jpg", "https://pbs.twimg.com/media/GqZZvtOXQAAYUI_.jpg", "https://pbs.twimg.com/media/GqZZ3VpXAAAFBOS.jpg", "https://pbs.twimg.com/media/GqZZ5O6WIAAR_SP.jpg" ], "videos": [] }, { "theme_title": "Developer Tools and GitHub Integration", "text": "@dankvr shared information about an open-source tool they're building that's similar to GitHub's integration with ChatGPT but with key differences: it works with any AI model, allows users to own their data through import/export functionality, and runs daily on any repository via GitHub Actions.", "sources": [ "https://twitter.com/dankvr/status/1920562060951265284" ], "images": [], "videos": [] }, { "theme_title": "Cryptocurrency Perspectives", "text": "@dankvr retweeted a post from @0xMert_ discussing why crypto is important, mentioning that some people are disillusioned with the state of crypto but that the original poster has never felt that way. @shawmakesmagic retweeted a post from @BasedBeffJezos with the simple message 'Build and let build. That's e/acc.'", "sources": [ "https://twitter.com/0xMert_/status/1920251576624574951", "https://twitter.com/BasedBeffJezos/status/1920447783275728938" ], "images": [], "videos": [] } ], "topic": "twitter_activity" }, { "title": "Summary for completed_items", "content": [ { "text": "Recent completed items in the elizaOS/eliza repository include several code maintenance changes, bug fixes, and feature additions:\n\nCode Maintenance:\n- Removed StudioLM support to focus on llama.cpp (PR #4459)\n- Deleted all memories API and client hooks (PR #4467)\n- Removed plugin-elevenlabs AI from the monorepo (PR #4480)\n- Implemented real drizzle ORM for database operation types (PR #4500)\n- Enhanced message handling with null checks for text escaping (PR #4508)\n- Released version 0.25.19 (PR #4501)\n\nBug Fixes:\n- Fixed type errors in CLI and replaced deprecated fs.exists (PR #4482)\n- Fixed pglite directory issues (PR #4497)\n- Fixed runtime type (PR #4495)\n- Fixed publish CLI options for platform and skip-registry (PR #4492)\n- Resolved missing .gitignore in plugins created with global CLI installation (PR #4489)\n- Fixed TTS manager and transcribe functionality (PR #4496)\n- Fixed deletion of agents that have been in room (PR #4510)\n\nDocumentation and Features:\n- Added docstrings to fix-pglite-dir (PR #4498)\n- Added docstrings to fix-publish-cli-options-platform-and-skip-registry (PR #4494)\n- Updated documentation to prefer direct usage instead of npx (PR #4493)\n- Created README_IND.md (PR #4488)\n- Updated README.md (PR #4483)", "sources": [ "https://github.com/elizaOS/eliza/pull/4459", "https://github.com/elizaOS/eliza/pull/4467", "https://github.com/elizaOS/eliza/pull/4482", "https://github.com/elizaOS/eliza/pull/4480", "https://github.com/elizaOS/eliza/pull/4500", "https://github.com/elizaOS/eliza/pull/4498", "https://github.com/elizaOS/eliza/pull/4497", "https://github.com/elizaOS/eliza/pull/4495", "https://github.com/elizaOS/eliza/pull/4494", "https://github.com/elizaOS/eliza/pull/4493", "https://github.com/elizaOS/eliza/pull/4492", "https://github.com/elizaOS/eliza/pull/4489", "https://github.com/elizaOS/eliza/pull/4496", "https://github.com/elizaOS/eliza/pull/4488", "https://github.com/elizaOS/eliza/pull/4483", "https://github.com/elizaOS/eliza/pull/4510", "https://github.com/elizaOS/eliza/pull/4508", "https://github.com/elizaOS/eliza/pull/4501" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Recent pull requests in the elizaOS/eliza repository include:\n\n- PR #4501: A release update for version 0.25.19 submitted by odilitime\n- PR #4505: Addition of plugin specification wrappers by odilitime\n- PR #4500: Implementation of real drizzle ORM for database base operation types by ChristopherTrimboli\n- PR #4499: New feature for Eddy DevRel agent contributed by samarth30\n- PR #4496: Fix for TTS manager and transcribe functionality by 0xbbjoker\n- PR #4487 and #4485: Addition of Indonesian README documentation by K1mc4n\n- PR #4459: Removal of StudioLM support to focus on llama.cpp by 0xbbjoker", "sources": [ "https://github.com/elizaOS/eliza/pull/4501", "https://github.com/elizaOS/eliza/pull/4505", "https://github.com/elizaOS/eliza/pull/4500", "https://github.com/elizaOS/eliza/pull/4499", "https://github.com/elizaOS/eliza/pull/4496", "https://github.com/elizaOS/eliza/pull/4487", "https://github.com/elizaOS/eliza/pull/4485", "https://github.com/elizaOS/eliza/pull/4459" ], "images": [], "videos": [] } ], "topic": "pull_request" }, { "title": "Summary for github_summary", "content": [ { "text": "GitHub activity for elizaos/eliza over two days:\n\nMay 8-9, 2025: 17 new PRs (12 merged), 1 new issue, and 14 active contributors.\n\nMay 9-10, 2025: 12 new PRs (6 merged), 1 new issue, and 20 active contributors.\n\nThe repository saw an increase in active contributors from 14 to 20, while PR activity decreased from 17 to 12 new PRs.", "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 #4486 reports an agent hanging after core initialization and REST API binding when using Anthropic with Twitter configuration. Issue #4503 requests OLLAMA support for the project.", "sources": [ "https://github.com/elizaOS/eliza/issues/4486", "https://github.com/elizaOS/eliza/issues/4503" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4486", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4503" ], "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": 1746662400 } }, "ai_news_elizaos_daily_md_2025-05-08": { "filename": "2025-05-08.md", "content": "# Daily Report - 2025-05-08\n\n## Twitter Activity\n\n### Eliza OS and Agentic AI Development\n- @elizaOS shared updates about their AI news show's evolution and announced an event in their Discord to discuss autonomous agentic governance\n- @dankvr mentioned that Shaw is taking a break from X to focus on the launch of V2\n- @elizaOS highlighted that their platform enables 'scripting behavior' rather than just scheduling posts, in response to a Bonsai integration\n- @elizaOS announced a builder demo week spotlighting agent-managed DAOs and how elizaOS is integrating into the Eliza community itself\n- @elizaOS emphasized their commitment to transparent, auditable, and agentic AI, particularly in government applications\n- @shawmakesmagic recommended Eliza v2 to @liamzebedee, mentioning its drag-and-drop RAG UI in chat and shared a link to a fully agentic RAG website with source code\n- Sources: https://twitter.com/dankvr/status/1920282622728536281, https://twitter.com/elizaOS/status/1920296359451590804, https://twitter.com/elizaOS/status/1920342076903866405, https://twitter.com/elizaOS/status/1920474359002501358, https://twitter.com/elizaOS/status/1920484355433992634, https://twitter.com/elizaOS/status/1920484359284404460, https://twitter.com/elizaOS/status/1920564611146760308, https://twitter.com/shawmakesmagic/status/1920323797174849714, https://twitter.com/shawmakesmagic/status/1920324483744780306\n\n### SigmaX Music Platform and Ecosystem\n- @autodotfun shared multiple tweets about SigmaX Music, describing it as 'the hottest music drop this year' and 'an ecosystem' rather than just an album\n- @autodotfun quoted a tweet from @SigmaXMusic announcing app revenue sharing for musicians and fans, with 10% of app revenue going back to the community\n- @elizaOS highlighted the platform's capabilities, stating 'eliza remixes, fans mint, royalties split' while noting that traditional labels are still asking for MP3s\n- @autodotfun mentioned that @SigmaXMusic fans are 'minting bangers, splitting bags' and suggested the platform is 'changing the game' and 'bringing back the fun'\n- Sources: https://twitter.com/autodotfun/status/1920395542384763112, https://twitter.com/autodotfun/status/1920382357376282794, https://twitter.com/autodotfun/status/1920393800540659784, https://twitter.com/autodotfun/status/1920394904884085157, https://twitter.com/autodotfun/status/1920542078179700909, https://twitter.com/elizaOS/status/1920393005682348390\n\n### PrinceSCRT Token Launch\n- @autodotfun announced the launch of @PrinceSCRT on their platform, describing it as an AI agent from the @SecretNetwork community powered by Secret AI's secure LLM interactions\n- @autodotfun explained that the platform uses a fair-launch protocol and Liquidity NFTs to ensure ongoing engagement and stable tokenomics\n- According to @autodotfun, holding $PSCRT tokens grants exclusive access to private interactions, Secret AI-driven insights, and initiatives empowering African communities\n- @autodotfun described the token as 'privacy's not dead – it just went stealth mode' and referred to @PrinceSCRT as 'our prince of fun' and 'the talisMAN'\n- Sources: https://twitter.com/autodotfun/status/1920502475175408108, https://twitter.com/autodotfun/status/1920502477947855018, https://twitter.com/autodotfun/status/1920502479738859917, https://twitter.com/autodotfun/status/1920513105596932459, https://twitter.com/autodotfun/status/1920521069661762006, https://twitter.com/autodotfun/status/1920521902231040268, https://twitter.com/autodotfun/status/1920521906668667207, https://twitter.com/autodotfun/status/1920542504862044243, https://twitter.com/autodotfun/status/1920548478238757089\n\n### DAOs and Media Influence\n- @dankvr shared thoughts on how media shapes policy through public perception, calling it 'the fourth branch of government'\n- @dankvr noted that 'DAOs barely have a media layer right now' and indicated they're working to change that\n- @shawmakesmagic retweeted @dankvr's post about media influence\n- @dankvr mentioned that a byproduct of their tools is how they're fetching, summarizing, and saving repository issues, PRs, and comments that git itself doesn't have\n- @dankvr suggested that 'having full ownership of our project's data can make right of exit easier'\n- Sources: https://twitter.com/dankvr/status/1920268669847790067, https://twitter.com/dankvr/status/1920321451514618255, https://twitter.com/shawmakesmagic/status/1920321451514618255\n\n### Developer Tools and GitHub Integration\n- @dankvr shared information about an open-source tool they're building that's similar to GitHub's integration with ChatGPT but with key differences\n- The tool works with any AI model, allows users to own their data through import/export functionality, and runs daily on any repository via GitHub Actions\n- Sources: https://twitter.com/dankvr/status/1920562060951265284\n\n### Cryptocurrency Perspectives\n- @dankvr retweeted a post from @0xMert_ discussing why crypto is important, mentioning that some people are disillusioned with the state of crypto\n- @shawmakesmagic retweeted a post from @BasedBeffJezos with the message 'Build and let build. That's e/acc'\n- Sources: https://twitter.com/0xMert_/status/1920251576624574951, https://twitter.com/BasedBeffJezos/status/1920447783275728938\n\n## Completed Items for elizaOS/eliza\n\n- Removed StudioLM support to focus on llama.cpp (PR #4459)\n- Deleted all memories API and client hooks (PR #4467)\n- Removed plugin-elevenlabs AI from the monorepo (PR #4480)\n- Implemented real drizzle ORM for database operation types (PR #4500)\n- Enhanced message handling with null checks for text escaping (PR #4508)\n- Released version 0.25.19 (PR #4501)\n- Fixed type errors in CLI and replaced deprecated fs.exists (PR #4482)\n- Fixed pglite directory issues (PR #4497)\n- Fixed runtime type (PR #4495)\n- Fixed publish CLI options for platform and skip-registry (PR #4492)\n- Resolved missing .gitignore in plugins created with global CLI installation (PR #4489)\n- Fixed TTS manager and transcribe functionality (PR #4496)\n- Fixed deletion of agents that have been in room (PR #4510)\n- Added docstrings to fix-pglite-dir (PR #4498)\n- Added docstrings to fix-publish-cli-options-platform-and-skip-registry (PR #4494)\n- Updated documentation to prefer direct usage instead of npx (PR #4493)\n- Created README_IND.md (PR #4488)\n- Updated README.md (PR #4483)\n- Sources: https://github.com/elizaOS/eliza/pull/4459, https://github.com/elizaOS/eliza/pull/4467, https://github.com/elizaOS/eliza/pull/4482, https://github.com/elizaOS/eliza/pull/4480, https://github.com/elizaOS/eliza/pull/4500, https://github.com/elizaOS/eliza/pull/4498, https://github.com/elizaOS/eliza/pull/4497, https://github.com/elizaOS/eliza/pull/4495, https://github.com/elizaOS/eliza/pull/4494, https://github.com/elizaOS/eliza/pull/4493, https://github.com/elizaOS/eliza/pull/4492, https://github.com/elizaOS/eliza/pull/4489, https://github.com/elizaOS/eliza/pull/4496, https://github.com/elizaOS/eliza/pull/4488, https://github.com/elizaOS/eliza/pull/4483, https://github.com/elizaOS/eliza/pull/4510, https://github.com/elizaOS/eliza/pull/4508, https://github.com/elizaOS/eliza/pull/4501\n\n## Pull Requests for elizaOS/eliza\n\n- PR #4501: A release update for version 0.25.19 submitted by odilitime\n- PR #4505: Addition of plugin specification wrappers by odilitime\n- PR #4500: Implementation of real drizzle ORM for database base operation types by ChristopherTrimboli\n- PR #4499: New feature for Eddy DevRel agent contributed by samarth30\n- PR #4496: Fix for TTS manager and transcribe functionality by 0xbbjoker\n- PR #4487 and #4485: Addition of Indonesian README documentation by K1mc4n\n- PR #4459: Removal of StudioLM support to focus on llama.cpp by 0xbbjoker\n- Sources: https://github.com/elizaOS/eliza/pull/4501, https://github.com/elizaOS/eliza/pull/4505, https://github.com/elizaOS/eliza/pull/4500, https://github.com/elizaOS/eliza/pull/4499, https://github.com/elizaOS/eliza/pull/4496, https://github.com/elizaOS/eliza/pull/4487, https://github.com/elizaOS/eliza/pull/4485, https://github.com/elizaOS/eliza/pull/4459\n\n## GitHub Activity Summary\n\n- May 8-9, 2025: 17 new PRs (12 merged), 1 new issue, and 14 active contributors\n- May 9-10, 2025: 12 new PRs (6 merged), 1 new issue, and 20 active contributors\n- The repository saw an increase in active contributors from 14 to 20, while PR activity decreased from 17 to 12 new PRs\n- Sources: source 1 (githubStatsSummary), source 2 (githubStatsSummary)\n\n## Issues for elizaOS/eliza\n\n- Issue #4486 reports an agent hanging after core initialization and REST API binding when using Anthropic with Twitter configuration\n- Issue #4503 requests OLLAMA support for the project\n- Sources: https://github.com/elizaOS/eliza/issues/4486, https://github.com/elizaOS/eliza/issues/4503\n\n## GitHub Other\n\n- The sources provide information about the top contributors for the GitHub repository elizaOS/eliza\n- Sources: source 1, source 2" }, "ai_news_elizaos_daily_discord_json_2025-05-08": { "filename": "2025-05-08.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-08", "date": 1746662400, "stats": { "totalMessages": 569, "totalUsers": 66 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily revolves around Shaw (a key team member) temporarily suspending his Twitter account, causing community concern and FUD (Fear, Uncertainty, Doubt). Jin and other team members attempt to reassure the community that Shaw is taking a break and still working on development. The conversation touches on contributor recognition for the ElizaOS project, particularly regarding eligibility for a potential DOOD airdrop. There's discussion about how GitHub contributors were identified for rewards, with Jin mentioning challenges in collecting Solana wallet addresses from contributors. The chat reveals that the ElizaOS team provided contributor data to the Doodles team for their airdrop, but submission deadlines may have passed for some. Community members express interest in ElizaOS v2 development and discuss token distribution statistics, noting that AI16Z has more decentralized token distribution (69% held by top 100) compared to another token called VIRTUAL (93% held by top 100).\n\n## 2. FAQ\nQ: Why did Shaw's account get suspended? (asked by mars) A: He's taking a Twitter detox break (answered by jin)\nQ: Why doesn't he just let people know he's going on a break? (asked by waterisgood123) A: Unanswered\nQ: Is elizaOS v2 coming soon? (asked by xell0x) A: Unanswered\nQ: How's degenai going? Updates were supposed to come since February (asked by Dive or Die) A: Unanswered\nQ: Is this the discord of ai16z? (asked by Blow) A: Unanswered\nQ: Is there any airdrop for those who hold 10k eliza or more? (asked by gaona6828) A: Sorry, no (answered by Osint)\nQ: I read that ElizaOS contributors could be eligible for DOOD airdrop? (asked by gaona6828) A: Contributors to codebase (answered by Osint)\nQ: I had a PR merged into Eliza GH, how does that link to my wallet for dood? (asked by Cubs | WILL NOT DM) A: Send your SOL address to kenk (answered by jin)\nQ: Where can you view the AUM for ai16z? (asked by rap7ure) A: I think it's on DAOs.fun (answered by Kenk)\nQ: Is the hoplite role for holding 100k degenai gone? (asked by Adii) A: Yes, I believe so (answered by Osint)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Contributors | Context: Collecting Solana wallet addresses for contributor rewards | Resolution: Jin instructed contributors to send their addresses to kenk\nHelper: eskender.eth | Helpee: Deniz | Context: Confirming eligibility for DOOD airdrop | Resolution: Offered to check wallet addresses with the team\nHelper: Osint | Helpee: jin | Context: Offered to help collect Solana addresses | Resolution: Offered to process a list to get addresses for jin\nHelper: Osint | Helpee: Community | Context: Explaining Shaw's Twitter absence | Resolution: Clarified that Shaw is taking a break and still coding\nHelper: Kenk | Helpee: rap7ure | Context: Finding AI16Z AUM information | Resolution: Directed user to DAOs.fun\n\n## 4. Action Items\nTechnical: ElizaOS v2 development | Description: Continue development of the next version | Mentioned By: xell0x\nTechnical: Discord contributor analysis | Description: Complete analysis of Discord contributors for rewards | Mentioned By: jin\nTechnical: Collect Solana wallet addresses | Description: Gather addresses from contributors for rewards | Mentioned By: jin\nDocumentation: Create Pope AI X agent | Description: Develop an AI agent for the new Pope announcement | Mentioned By: groggs\nFeature: Feature Eli5 more prominently | Description: Use Eli5 as mascot on auto.fun, Shaw's and elizaOS' Twitter | Mentioned By: xell0x\nFeature: Create crypto dev GitHub graph | Description: Tool to plot relationships and influence among crypto developers | Mentioned By: Osint", "messageCount": 206, "userCount": 34 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around ElizaOS development and troubleshooting. Users discussed Twitter agent integration, Docker image building issues, and configuration problems with local AI models. A key technical issue involved ElizaOS defaulting to local AI models despite configuration settings specifying external providers like Groq. The solution involved properly setting environment variables in the .env file at the root folder and configuring characters for specific plugins. There was also discussion about a database error (\"duplicate key value violates unique constraint\") occurring specifically with the Discord plugin. Other topics included Vercel's MCP server support for Next.js, Twitter plugin integration, and model selection for agents.\n\n## 2. FAQ:\nQ: Does anyone know which version of Eliza is currently working best? (asked by keygray_mm) A: Unanswered\nQ: How do I add plugin twitter to character? (asked by keygray_mm) A: Documentation is available at https://docs.eliza.how/blog/twitter-agent-guide (answered by odilitime)\nQ: Why am I getting \"duplicate key value violates unique constraint 'memories_pkey'\" error while interacting in Discord? (asked by odilitime) A: It appears to be a Discord plugin-specific issue that resolves temporarily after using the Eliza web interface (answered by odilitime)\nQ: How do I fix ElizaOS falling back to local AI despite configuration? (asked by odilitime) A: Configure the .env file at the root with your API keys and configure characters for plugin-groq (answered by odilitime)\n\n## 3. Help Interactions:\nHelper: odilitime | Helpee: odilitime | Context: ElizaOS Docker image falling back to local AI despite configuration | Resolution: Suggested configuring characters for plugin-groq and setting up .env file with API keys at the root folder\nHelper: odilitime | Helpee: mahee | Context: Twitter AI agent API quota issues | Resolution: Suggested using Heurist as a free alternative\nHelper: keygray_mm | Helpee: mahee | Context: Twitter API quota exceeded error | Resolution: Suggested using Heurist as it's free\n\n## 4. Action Items:\nType: Technical | Description: Fix Discord plugin issue causing \"duplicate key value violates unique constraint 'memories_pkey'\" error | Mentioned By: odilitime\nType: Technical | Description: Test interactive 24/7 unreal engine elizaOS metahuman | Mentioned By: odilitime\nType: Technical | Description: Update/push multistream-client and air3market-plugin for V2 | Mentioned By: odilitime\nType: Documentation | Description: Create clearer instructions for configuring external AI providers like Groq | Mentioned By: odilitime", "messageCount": 34, "userCount": 7 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Analysis of Discord Chat in \"fun\" Channel\n\n## 1. Summary\nThe chat primarily revolves around a problematic token launch called \"PrinceSCRT\" by Secret Network on the auto.fun platform. Users reported that shortly after launch, the developer wallet sold a significant portion of tokens, causing the price to crash from a peak of approximately $800k to around $60-80k market cap. This triggered accusations of a \"rug pull\" and demands for refunds. The auto.fun team, represented by jasyn_bjorn, stated they wouldn't issue refunds as they have \"no control over what the team does post launch.\" This incident follows other problematic launches mentioned by users, including issues with \"doglifeai\" and a mistaken token verification the previous day (which did result in refunds). Throughout the controversy, some users continued to promote ELI5 token as a safer alternative. The chat also briefly touched on potential improvements to the platform, including a subscription model for early access to partner projects.\n\n## 2. FAQ\nQ: So will the refund be automatic? We just have to wait? (asked by Kudo Ω) A: ya. will be sorted in < 24hrs (answered by jasyn_bjorn)\nQ: Do I just need to wait after submitting information to the bot (asked by Kudo Ω) A: ya. will be sorted in < 24hrs (answered by jasyn_bjorn)\nQ: can you tell me why i should invest into eli5? (asked by shad) A: Unanswered\nQ: when will it migrate (asked by vas) A: its migrated (answered by eskender.eth)\nQ: will there be a refund? (asked by mhd) A: we unfortunately have no control over what the team does post launch even after we vet them thoroughly beforehand. sorry, but we wont be issuing refunds for this launch. (answered by jasyn_bjorn)\n\n## 3. Help Interactions\nHelper: jasyn_bjorn | Helpee: Kudo Ω | Context: User asking about refund process | Resolution: Confirmed refund would be processed within 24 hours\nHelper: eskender.eth | Helpee: vas | Context: Explaining why partners don't always share contract addresses before launch | Resolution: Clarified it's about control and limiting people at point of launch\nHelper: ryanthelad | Helpee: Multiple users | Context: Providing information about Secret Network still holding supply | Resolution: Attempted to reassure users during price crash\n\n## 4. Action Items\nType: Technical | Description: Partners should be required to share contract address before launching to prevent wrong addresses | Mentioned By: vas\nType: Technical | Description: Implement a subscription model allowing OG members early investment in partner projects with allocation limits and locks | Mentioned By: MDMnvest\nType: Technical | Description: Fix bugs in the platform as it \"needs bug fixes and to mature\" | Mentioned By: nasdaq.ai\nType: Technical | Description: Establish stricter criteria for partner verification to prevent problematic launches | Mentioned By: vas\nType: Feature | Description: Lock up ELI5 tokens to get early allocation to partner projects, similar to Virtual | Mentioned By: ryanthelad\nType: Documentation | Description: Clearer communication about risks involved with new token launches | Mentioned By: jasyn_bjorn", "messageCount": 315, "userCount": 28 }, { "channelId": "1362864274862768450", "channelName": "fun-support", "summary": "# Analysis of \"fun-support\" Discord Channel\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation primarily revolves around an upcoming token generation event (TGE) for a project called \"Doodles\" (DOOD), with users seeking information about token distribution amounts. A user named Kenk shared a link to an article about the Doodles new Blood Fund TGE. Additionally, there was a concern raised about fake coins existing on a platform before the official token launch, with a suggestion to remove them to prevent confusion. Finally, a user complained about losing money in a project called \"pscrt\" that was allegedly promoted by \"auto fun\" and then abandoned by the developer.\n\n## 2. FAQ\nQ: Any news about tomorrow's event? (asked by sukrucildirr) A: Kenk shared an article link about Doodles DOOD new Blood Fund TGE (answered by Kenk)\nQ: Will we get 200k per contribution? (asked by sukrucildirr) A: I have no insight into how they're distributing (answered by Kenk)\nQ: Can you give me a hint about the distribution? (asked by sukrucildirr) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: sukrucildirr | Context: User seeking information about upcoming token event | Resolution: Shared an article link about the Doodles DOOD new Blood Fund TGE\nHelper: velja | Helpee: Community | Context: Fake coins existing on site before real token launch | Resolution: Suggested removing fake coins to prevent confusion when the real one launches\n\n## 4. Action Items\nTechnical: Remove fake coins from the platform before the real token launches | Description: Prevent confusion and mistakes by ensuring only the legitimate token is listed | Mentioned By: velja\nTechnical: Investigate the pscrt token situation | Description: Look into claims that a developer abandoned the pscrt project after promotion by \"auto fun\" | Mentioned By: hxf", "messageCount": 14, "userCount": 4 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-08": { "filename": "2025-05-08.md", "content": "# elizaOS Discord - 2025-05-08\n\n## Overall Discussion Highlights\n\n### Team & Community Updates\n- **Shaw's Twitter Break**: Shaw (key team member) temporarily suspended his Twitter account, causing community concern. Jin and others reassured the community that Shaw is taking a break but still working on development.\n- **ElizaOS v2 Development**: Community members expressed interest in the upcoming ElizaOS v2, though specific details or timelines weren't provided.\n- **Token Distribution Analysis**: Discussion about AI16Z having more decentralized token distribution (69% held by top 100) compared to VIRTUAL (93% held by top 100).\n\n### Technical Discussions\n- **AI Model Configuration Issues**: Users troubleshooted ElizaOS defaulting to local AI models despite configuration settings specifying external providers like Groq. The solution involved properly setting environment variables in the .env file.\n- **Discord Plugin Error**: A database error (\"duplicate key value violates unique constraint\") was reported specifically with the Discord plugin.\n- **Twitter Agent Integration**: Several users discussed Twitter agent integration and API quota issues, with suggestions to use Heurist as a free alternative.\n\n### Auto.fun Platform Issues\n- **PrinceSCRT Token Launch Problems**: A problematic token launch called \"PrinceSCRT\" by Secret Network on the auto.fun platform resulted in accusations of a \"rug pull\" when the developer wallet sold a significant portion of tokens post-launch.\n- **Refund Policy Controversy**: The auto.fun team stated they wouldn't issue refunds for the PrinceSCRT incident as they have \"no control over what the team does post launch,\" causing community frustration.\n- **Platform Improvement Suggestions**: Users suggested implementing a subscription model for early access to partner projects and stricter verification criteria for launches.\n\n### Contributor Recognition\n- **DOOD Airdrop Eligibility**: Discussion about ElizaOS contributor eligibility for a potential DOOD airdrop, particularly regarding GitHub contributors.\n- **Wallet Collection Challenges**: Jin mentioned challenges in collecting Solana wallet addresses from contributors for rewards distribution.\n\n## Key Questions & Answers\n\n### Team & Development\n- **Q**: Why did Shaw's account get suspended? \n **A** (jin): He's taking a Twitter detox break.\n\n- **Q**: Is there any airdrop for those who hold 10k eliza or more? \n **A** (Osint): Sorry, no.\n\n- **Q**: I read that ElizaOS contributors could be eligible for DOOD airdrop? \n **A** (Osint): Contributors to codebase.\n\n- **Q**: I had a PR merged into Eliza GH, how does that link to my wallet for dood? \n **A** (jin): Send your SOL address to kenk.\n\n- **Q**: Where can you view the AUM for ai16z? \n **A** (Kenk): I think it's on DAOs.fun.\n\n### Technical Support\n- **Q**: How do I add plugin twitter to character? \n **A** (odilitime): Documentation is available at https://docs.eliza.how/blog/twitter-agent-guide.\n\n- **Q**: How do I fix ElizaOS falling back to local AI despite configuration? \n **A** (odilitime): Configure the .env file at the root with your API keys and configure characters for plugin-groq.\n\n### Auto.fun Platform\n- **Q**: Will there be a refund for the PrinceSCRT issue? \n **A** (jasyn_bjorn): We unfortunately have no control over what the team does post launch even after we vet them thoroughly beforehand. Sorry, but we won't be issuing refunds for this launch.\n\n- **Q**: When will it [token] migrate? \n **A** (eskender.eth): It's migrated.\n\n## Community Help & Collaboration\n\n1. **ElizaOS Configuration Support**:\n - odilitime helped users troubleshoot ElizaOS Docker image falling back to local AI despite configuration, suggesting proper .env file setup and character configuration for plugin-groq.\n\n2. **Twitter API Quota Solutions**:\n - odilitime and keygray_mm suggested using Heurist as a free alternative when mahee encountered Twitter API quota issues.\n\n3. **Contributor Reward Coordination**:\n - Jin instructed contributors to send their Solana addresses to kenk for potential rewards.\n - Osint offered to help collect Solana addresses and process a list to get addresses for jin.\n\n4. **Token Launch Information**:\n - Kenk shared an article link about the Doodles DOOD new Blood Fund TGE when sukrucildirr asked about the upcoming event.\n - eskender.eth explained to vas why partners don't always share contract addresses before launch, clarifying it's about control and limiting people at point of launch.\n\n## Action Items\n\n### Technical\n- Continue development of ElizaOS v2 (Mentioned by: xell0x)\n- Complete analysis of Discord contributors for rewards (Mentioned by: jin)\n- Collect Solana wallet addresses from contributors (Mentioned by: jin)\n- Fix Discord plugin issue causing \"duplicate key value violates unique constraint 'memories_pkey'\" error (Mentioned by: odilitime)\n- Test interactive 24/7 unreal engine elizaOS metahuman (Mentioned by: odilitime)\n- Update/push multistream-client and air3market-plugin for V2 (Mentioned by: odilitime)\n- Remove fake coins from the platform before real token launches (Mentioned by: velja)\n- Investigate the pscrt token situation (Mentioned by: hxf)\n- Require partners to share contract address before launching (Mentioned by: vas)\n- Implement a subscription model for early access to partner projects (Mentioned by: MDMnvest)\n- Fix bugs in the auto.fun platform as it \"needs bug fixes and to mature\" (Mentioned by: nasdaq.ai)\n- Establish stricter criteria for partner verification (Mentioned by: vas)\n\n### Documentation\n- Create Pope AI X agent (Mentioned by: groggs)\n- Create clearer instructions for configuring external AI providers like Groq (Mentioned by: odilitime)\n- Provide clearer communication about risks involved with new token launches (Mentioned by: jasyn_bjorn)\n\n### Feature\n- Feature Eli5 more prominently as mascot on auto.fun, Shaw's and elizaOS' Twitter (Mentioned by: xell0x)\n- Create crypto dev GitHub graph to plot relationships among crypto developers (Mentioned by: Osint)\n- Lock up ELI5 tokens to get early allocation to partner projects, similar to Virtual (Mentioned by: ryanthelad)" }, "ai_news_elizaos_daily_dev_json_2025-05-08": { "filename": "2025-05-08.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-08", "date": 1746662400, "stats": { "totalMessages": 95, "totalUsers": 15 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Analysis of 💬｜general Discord Channel\n\n## 1. Summary\nThe chat segment is very brief and contains minimal technical discussion. There are no substantive technical conversations, problem-solving, or implementations shared. The messages primarily consist of greetings, link sharing, and a developer offering services. One user (Sidtoshi Vision) asks about tokens called \"EDDY\" and \"ELI5,\" to which another user (Odilitime) clarifies that these are characters in the code but not official tokens, stating that only \"$ai16z\" and \"$degenai\" are official tokens.\n\n## 2. FAQ\nQ: Is EDDY the V2 agent and ELI5 going to be \"a character\"? (asked by Sidtoshi Vision) A: They are characters in the code, yes. Are the tokens related? No. The only official tokens are $ai16z and $degenai (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: Sidtoshi Vision | Context: Confusion about tokens called EDDY and ELI5 | Resolution: Clarified that these are characters in the code but not official tokens, stating only $ai16z and $degenai are official\n\n## 4. Action Items\nNo specific action items were identified in this chat segment.", "messageCount": 10, "userCount": 6 }, { "channelId": "1327493511406293016", "channelName": "🎤｜plug-your-projects", "summary": "The chat segment is extremely brief, containing only two messages. Kenk shared a link to a Twitter/X post from \"heurist_ai\", and sayonara responded with a brief positive comment about the project, mentioning Kenk directly. There is no technical discussion, problem-solving, or implementation details in this exchange. The conversation appears to be a simple project sharing with minimal engagement.", "messageCount": 2, "userCount": 2 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Discord Chat Analysis for 🤖｜agent-dev-school\n\n## 1. Summary:\nThe chat primarily focused on technical discussions around multi-agent setups, database configurations, and package manager compatibility issues. Ruby provided guidance on running multiple agents with a single Postgres database, explaining that the platform handles memory isolation by default through namespacing in the database schema. The conversation also covered model configuration for agents, specifically how to set up different tiers (small, medium, large) using a mix of Claude and GPT models. A significant portion of the discussion addressed package manager conflicts between npm and Bun, with users experiencing module resolution issues when the CLI was installed with npm but plugins were being installed with Bun. The recommended solution was to maintain consistency by either setting PACKAGE_MANAGER=npm in the .env file or installing the CLI with Bun instead of npm.\n\n## 2. FAQ:\nQ: Is it ok to run multiple agents off the same postgres db? Does the platform handle storing all of their memories separately? (asked by Blaze Leclairt) A: Yes, you can run multiple agents on one postgres db. The platform handles memory isolation by default - each agent gets their own namespace in the db schema. Just make sure you give each agent a unique name/id in their config. (answered by Ruby)\nQ: How do I setup my .env for anthropic models? (asked by Blaze Leclairt) A: Add ANTHROPIC_API_KEY=your_key_here in your .env file. The platform will automatically detect and use it when you specify claude models in your agent config. (answered by Ruby)\nQ: How can I define small, large, etc. models to use different ones in the agent config? (asked by Blaze Leclairt) A: In your agent's config.json, under the 'models' section, you can specify different model tiers like: 'small': 'claude-2.1', 'medium': 'claude-2.1', 'large': 'claude-3'. (answered by Ruby)\nQ: Why do plugins fail to load with global CLI install but work with npx? (asked by kandizzy) A: It's a path resolution issue. When you install the CLI globally with npm, it expects plugins in the npm global path, but the project is using bun's module resolution. (answered by Ruby)\nQ: How can I install the CLI with Bun instead of npm? (asked by kandizzy) A: Run 'bun install -g @elizaos/cli@beta' to install the CLI globally with Bun. (answered by Ruby)\n\n## 3. Help Interactions:\nHelper: Ruby | Helpee: Blaze Leclairt | Context: Running multiple agents with a single Postgres database | Resolution: Confirmed it's possible with automatic memory isolation through namespacing, recommending unique agent IDs in config\nHelper: Ruby | Helpee: Blaze Leclairt | Context: Setting up Anthropic models in agent configuration | Resolution: Provided a sample config.json with mixed models (claude-2.1, claude-3, gpt-4-turbo) for different complexity tiers\nHelper: Ruby | Helpee: kandizzy | Context: Module resolution issues between npm-installed CLI and Bun-installed plugins | Resolution: Suggested setting PACKAGE_MANAGER=npm in .env or using Bun for CLI installation to maintain consistency\n\n## 4. Action Items:\nTechnical: Use unique AGENT_ID in each agent's config when running multiple agents on a single database | Description: Ensures proper memory isolation between agents | Mentioned By: Ruby\nTechnical: Set PACKAGE_MANAGER=npm in .env file when CLI is installed with npm | Description: Prevents module resolution conflicts between npm and Bun | Mentioned By: Ruby\nTechnical: Install CLI with Bun instead of npm for consistency | Description: Run 'bun install -g @elizaos/cli@beta' to avoid package manager conflicts | Mentioned By: Ruby\nDocumentation: Update documentation regarding CLI installation with Bun | Description: Add instructions for installing CLI with Bun as an alternative to npm | Mentioned By: sayonara", "messageCount": 27, "userCount": 5 }, { "channelId": "1323745969115893780", "channelName": "📥｜pull-requests", "summary": "# Discord Chat Analysis: 📥｜pull-requests\n\n## 1. Summary:\nThe chat primarily revolves around helping a user named \"lost\" contribute an Indonesian translation (README_IND.md) to the Eliza project. Ruby (likely a bot) provided detailed guidance throughout the process. Initially, \"lost\" encountered build errors when attempting to make the contribution, but Ruby clarified that these errors could be ignored for documentation changes. Ruby walked \"lost\" through several steps: creating the translation file, adding a language badge, ensuring links were correctly formatted, placing the file in the root directory, and targeting the correct branch (develop instead of main) for the pull request. SpartanDev briefly suggested troubleshooting steps for the build error. Despite GitHub Actions showing failures, Ruby reassured \"lost\" that these were expected for documentation changes and wouldn't affect the PR. The conversation concluded with Ruby confirming that everything was properly set up for maintainer review.\n\n## 2. FAQ:\nQ: How can I put a Readme file for Indonesian translation in the repository? (asked by lost) A: Create a new file called README_IND.md in the root directory of your fork, paste in your translation, commit and push. (answered by Ruby)\nQ: How do I add a language badge to the README? (asked by lost) A: Add this line at the top of your README_IND.md: [![id](https://img.shields.io/badge/lang-Indonesian-red.svg)](README_IND.md) (answered by Ruby)\nQ: In which folder should I save the README_IND.md file? (asked by lost) A: It should go in the root directory - same level as the main README.md, alongside other language readmes like README_ES.md and README_FR.md. (answered by Ruby)\nQ: How do I fix the \"Merge requests to main branch are only allowed from dev branch\" error? (asked by lost) A: Target the develop branch instead of main by editing the PR and changing the 'base' dropdown from main to develop. (answered by Ruby)\nQ: Should I worry about integration-tests and GitHub Actions failures? (asked by lost) A: No, those failures are expected for doc changes and only relevant for code changes, not documentation updates. (answered by Ruby)\n\n## 3. Help Interactions:\nHelper: Ruby | Helpee: lost | Context: User encountered build errors when trying to contribute Indonesian translation | Resolution: Explained that build errors can be ignored for documentation changes and provided step-by-step guidance\nHelper: Ruby | Helpee: lost | Context: User needed to add a language badge to README | Resolution: Provided exact markdown code for adding an Indonesian language badge\nHelper: Ruby | Helpee: lost | Context: User's PR was targeting main branch instead of develop | Resolution: Explained how to edit the PR to target the correct branch\nHelper: Ruby | Helpee: lost | Context: User was unsure where to place the README_IND.md file | Resolution: Clarified that it should be in the root directory alongside other language readmes\nHelper: SpartanDev | Helpee: lost | Context: User encountered pnpm build errors | Resolution: Suggested clearing cache, deleting node_modules, and running clean install\n\n## 4. Action Items:\nTechnical: None\nDocumentation: Add Indonesian translation README (README_IND.md) to the repository | Mentioned By: lost\nDocumentation: Ensure all documentation links in README_IND.md point to the correct locations | Mentioned By: Ruby\nDocumentation: Add language badge to Indonesian README | Mentioned By: Ruby\nTechnical: Fix PR to target develop branch instead of main | Mentioned By: Ruby", "messageCount": 56, "userCount": 5 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-08": { "filename": "2025-05-08.md", "content": "# elizaOS Development Discord - 2025-05-08\n\n## Overall Discussion Highlights\n\n### Multi-Agent Architecture\n- Ruby confirmed that multiple agents can run on a single Postgres database\n- The platform handles memory isolation automatically through namespacing in the database schema\n- Each agent requires a unique name/ID in their configuration to ensure proper separation\n\n### Model Configuration\n- Detailed discussion on setting up tiered models (small, medium, large) in agent configurations\n- Example provided showing how to mix Claude and GPT models for different complexity levels:\n - 'small': 'claude-2.1'\n - 'medium': 'claude-2.1'\n - 'large': 'claude-3'\n- Clarification on adding Anthropic API keys to .env files for Claude model usage\n\n### Package Manager Compatibility\n- Users experienced module resolution issues when mixing npm and Bun\n- Problem occurred specifically when CLI was installed with npm but plugins were being installed with Bun\n- Two solutions were recommended:\n 1. Set `PACKAGE_MANAGER=npm` in the .env file\n 2. Install the CLI with Bun instead of npm using `bun install -g @elizaos/cli@beta`\n\n### Token Clarification\n- Odilitime clarified that \"EDDY\" and \"ELI5\" are characters in the code but not official tokens\n- Only `$ai16z` and `$degenai` are official tokens in the ecosystem\n\n### Community Contributions\n- User \"lost\" worked on adding an Indonesian translation (README_IND.md) to the project\n- Ruby provided detailed guidance on proper PR submission process\n- Discussion highlighted the importance of targeting the correct branch (develop vs. main)\n\n## Key Questions & Answers\n\n**Q: Is it ok to run multiple agents off the same postgres db? Does the platform handle storing all of their memories separately?** \nA: Yes, you can run multiple agents on one postgres db. The platform handles memory isolation by default - each agent gets their own namespace in the db schema. Just make sure you give each agent a unique name/id in their config.\n\n**Q: How do I setup my .env for anthropic models?** \nA: Add `ANTHROPIC_API_KEY=your_key_here` in your .env file. The platform will automatically detect and use it when you specify claude models in your agent config.\n\n**Q: How can I define small, large, etc. models to use different ones in the agent config?** \nA: In your agent's config.json, under the 'models' section, you can specify different model tiers like: 'small': 'claude-2.1', 'medium': 'claude-2.1', 'large': 'claude-3'.\n\n**Q: Why do plugins fail to load with global CLI install but work with npx?** \nA: It's a path resolution issue. When you install the CLI globally with npm, it expects plugins in the npm global path, but the project is using bun's module resolution.\n\n**Q: Is EDDY the V2 agent and ELI5 going to be \"a character\"?** \nA: They are characters in the code, yes. Are the tokens related? No. The only official tokens are $ai16z and $degenai.\n\n**Q: How can I put a Readme file for Indonesian translation in the repository?** \nA: Create a new file called README_IND.md in the root directory of your fork, paste in your translation, commit and push.\n\n**Q: Should I worry about integration-tests and GitHub Actions failures for documentation changes?** \nA: No, those failures are expected for doc changes and only relevant for code changes, not documentation updates.\n\n## Community Help & Collaboration\n\n### Multi-Agent Setup Guidance\nRuby provided comprehensive assistance to Blaze Leclairt on setting up multiple agents with a shared database, explaining memory isolation mechanisms and offering configuration examples for different model tiers.\n\n### Package Manager Troubleshooting\nRuby helped kandizzy resolve module resolution issues between npm and Bun, offering two alternative solutions to maintain consistency in the development environment.\n\n### Translation Contribution Support\nRuby guided user \"lost\" through the entire process of contributing an Indonesian translation:\n- Creating the translation file in the correct location\n- Adding proper language badges\n- Formatting links correctly\n- Targeting the correct branch for the PR\n- Understanding which build errors could be safely ignored for documentation changes\n\nSpartanDev also offered troubleshooting steps for build errors, suggesting cache clearing and clean installation approaches.\n\n### Token Clarification\nOdilitime helped Sidtoshi Vision understand the distinction between characters in the code and official tokens in the ecosystem.\n\n## Action Items\n\n### Technical\n- Use unique AGENT_ID in each agent's config when running multiple agents on a single database (Mentioned by Ruby)\n- Set PACKAGE_MANAGER=npm in .env file when CLI is installed with npm (Mentioned by Ruby)\n- Install CLI with Bun instead of npm for consistency using `bun install -g @elizaos/cli@beta` (Mentioned by Ruby)\n- Fix PR to target develop branch instead of main for contributions (Mentioned by Ruby)\n\n### Documentation\n- Add Indonesian translation README (README_IND.md) to the repository (Mentioned by lost)\n- Ensure all documentation links in README_IND.md point to the correct locations (Mentioned by Ruby)\n- Add language badge to Indonesian README (Mentioned by Ruby)\n- Update documentation regarding CLI installation with Bun as an alternative to npm (Mentioned by sayonara)" }, "ai_news_hyperfy_daily_json_2025-05-08": { "filename": "2025-05-08.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-08", "date": 1746662400, "stats": { "totalMessages": 49, "totalUsers": 20 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. There was a brief exchange about finding the updated Hyperfy quickstart documentation link, which was promptly provided. Another discussion touched on exporting VRM models with blendshapes in Blender, specifically addressing the limitation of the VRM plugin only allowing blendshapes to be applied to one mesh at a time. A user questioned whether this was accurate, noting that avatars often use separate opaque and transparent meshes. Finally, a user named Valiant briefly mentioned making progress toward an upcoming \"race day\" without specific technical details.\n\n## 2. FAQ\nQ: What's the new Hyperfy quickstart installation link? (asked by emotionull) A: https://docs.hyperfy.xyz/welcome/quickstart/ (answered by maximus)\nQ: Has anyone been successful in exporting generated VRMs with blendshapes through Blender? (asked by lucii.io) A: Partially answered by Ashxn who believed Blender VRM supported blendshapes on more than one mesh\nQ: Is it possible to edit the script to accommodate more than one mesh? (asked by lucii.io) A: Unanswered\n\n## 3. Help Interactions\nHelper: maximus | Helpee: emotionull | Context: User needed the updated Hyperfy quickstart documentation link | Resolution: Provided the correct URL\nHelper: Ashxn | Helpee: lucii.io | Context: User was having issues with Blender VRM plugin only allowing blendshapes on one mesh at a time | Resolution: Partial help by suggesting the plugin should support multiple meshes, citing common avatar setups\n\n## 4. Action Items\nTechnical: Investigate editing the VRM plugin script to support blendshapes on multiple meshes | Description: Current limitation in Blender VRM plugin prevents applying blendshapes to more than one mesh at a time | Mentioned By: lucii.io", "messageCount": 7, "userCount": 5 }, { "channelId": "1330373197203505185", "channelName": "🤖│agents", "summary": "The chat segment is extremely brief, consisting of only two messages. Maximus shared a link to a Coinbase Developer Platform page about \"x402\" with an expression of surprise (\"Holy moly\"). Ashxn responded with a one-word acknowledgment (\"crazy\"). There is no substantive technical discussion, problem-solving, or implementation details in this exchange.", "messageCount": 2, "userCount": 2 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Analysis of Discord Chat in \"⚡│general\" Channel\n\n## 1. Summary\nThe chat segment is extremely brief and contains no substantive technical discussions, decisions, or problem-solving. The conversation consists only of a service proposal from Martin P2B representing P2B exchange, a greeting from BallisticBanana, a one-word message \"wen\" from johan, and another greeting from Ashxn. There is also a GIF shared by a user with an unusual username. No technical content, solutions, or implementations were discussed in this brief exchange.\n\n## 2. FAQ\nNo significant questions with meaningful responses were present in the chat.\n\n## 3. Help Interactions\nNo significant help interactions occurred in this chat segment.\n\n## 4. Action Items\nNo clear action items were identified in this chat segment.", "messageCount": 5, "userCount": 5 }, { "channelId": "1326789867312775290", "channelName": "🪙│hyper", "summary": "# Discord Chat Analysis for \"🪙│hyper\" Channel\n\n## 1. Summary\nThis chat segment contains no substantive technical discussions, decisions, or problem-solving. The conversation primarily consists of brief comments about token purchases, price speculation, and exchange listings. Users mention buying more HYPER tokens, express concern about price drops, and discuss potential exchange listings. There is a mention of AI16Z being listed on crypto.com, with speculation that HYPER might follow. No technical implementations, solutions, or concrete development discussions appear in this transcript.\n\n## 2. FAQ\nQ: When will Hyperfy be listed on major CEX? (asked by simk) A: Unanswered\nQ: Why dumping? (asked by Spook_Handy) A: Unanswered\nQ: Can we focus a bit more on the token price? (asked by cloudAI) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were present in this chat segment.\n\n## 4. Action Items\nNo clear action items were identified in this chat segment.", "messageCount": 15, "userCount": 10 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "# Analysis of 🧊│3d-design Channel\n\n## 1. Summary:\nThe conversation revolves around Hyperfy's transition from v1 to v2 platform. A user (carlosmu) inquires about creating a new world in Hyperfy v1, but learns that v1 world NFTs are no longer available as the platform is transitioning to v2. Ashxn explains that while v1 is in maintenance mode and still functional, no major updates are planned. For v2, users have several options: self-hosting the open-source v2 world engine, using a hosting service like hyperworld.host, building locally, or using play.hyperfy.xyz where everyone has build permissions. The documentation has moved from hyperfy.how to docs.hyperfy.xyz, and a roadmap for v2 is coming soon.\n\n## 2. FAQ:\nQ: Can I create a new world/land in Hyperfy v1? (asked by carlosmu) A: The v1 world NFTs are no longer available as Hyperfy is transitioning to a new v2 engine and platform. (answered by Ashxn)\nQ: Can I buy a world in opensea? (asked by carlosmu) A: Yes, but the v1 platform is in maintenance mode with no more major updates, though it still works. (answered by Ashxn)\nQ: Is there any chance to try the v2 builder? (asked by carlosmu) A: Yes, the v2 world engine is open source and can be self-hosted or used via a hosting service like hyperworld.host. (answered by Ashxn)\nQ: Can we build locally? (asked by carlosmu) A: Absolutely. (answered by Ashxn)\nQ: Is this the right link for v2 docs? (asked by carlosmu) A: The docs moved to https://docs.hyperfy.xyz. (answered by Ashxn)\nQ: Is play.hyperfy.xyz v1 or v2 infrastructure? (asked by carlosmu) A: v2. (answered by Ashxn)\nQ: Is there a roadmap for the release of v2? (asked by carlosmu) A: Roadmap coming soon! (answered by Ashxn)\n\n## 3. Help Interactions:\nHelper: Ashxn | Helpee: carlosmu | Context: User wanted to create a new world in Hyperfy but was unaware of v1 to v2 transition | Resolution: Explained current status and provided multiple alternatives for building in v2\nHelper: Ashxn | Helpee: carlosmu | Context: User needed updated documentation links | Resolution: Provided correct link to v2 documentation (docs.hyperfy.xyz) and mentioned play.hyperfy.xyz as a building option\n\n## 4. Action Items:\nTechnical: Check out self-hosting options for v2 world engine | Description: For developers who want to start building in v2 | Mentioned By: Ashxn\nTechnical: Explore building in play.hyperfy.xyz | Description: Alternative to self-hosting where everyone has build permissions | Mentioned By: Ashxn\nDocumentation: Review updated v2 documentation at docs.hyperfy.xyz | Description: New location for Hyperfy documentation | Mentioned By: Ashxn\nFeature: Watch for upcoming v2 roadmap | Description: Roadmap for v2 release is coming soon | Mentioned By: Ashxn", "messageCount": 20, "userCount": 3 } ] } }, "ai_news_hyperfy_daily_md_2025-05-08": { "filename": "2025-05-08.md", "content": "# Hyperfy Discord - 2025-05-08\n\n## Overall Discussion Highlights\n\n### Platform Transition (v1 to v2)\n- Hyperfy is transitioning from v1 to v2 platform\n- v1 world NFTs are no longer available for purchase\n- v1 platform remains functional but in maintenance mode with no major updates planned\n- v2 world engine is open source and can be self-hosted\n- play.hyperfy.xyz runs on v2 infrastructure and allows everyone to build\n- A roadmap for v2 is coming soon\n\n### Development Topics\n- Brief discussion about VRM model exports with blendshapes in Blender\n- Current limitation in Blender VRM plugin only allows blendshapes on one mesh at a time\n- User Valiant mentioned making progress toward an upcoming \"race day\" (no details provided)\n- Maximus shared a link about Coinbase Developer Platform's \"x402\"\n\n### Token Discussion\n- Users discussed HYPER token purchases and price speculation\n- Mentions of potential exchange listings\n- Reference to AI16Z being listed on crypto.com with speculation HYPER might follow\n\n## Key Questions & Answers\n\n### Platform & Documentation\n- **Q**: Can I create a new world/land in Hyperfy v1? \n **A**: The v1 world NFTs are no longer available as Hyperfy is transitioning to v2.\n\n- **Q**: Can I buy a world in opensea? \n **A**: Yes, but the v1 platform is in maintenance mode with no more major updates, though it still works.\n\n- **Q**: Is there any chance to try the v2 builder? \n **A**: Yes, the v2 world engine is open source and can be self-hosted or used via a hosting service like hyperworld.host.\n\n- **Q**: What's the new Hyperfy quickstart installation link? \n **A**: https://docs.hyperfy.xyz/welcome/quickstart/\n\n- **Q**: Is play.hyperfy.xyz v1 or v2 infrastructure? \n **A**: v2.\n\n### Technical Questions\n- **Q**: Has anyone been successful in exporting generated VRMs with blendshapes through Blender? \n **A**: Partially answered - Ashxn believed Blender VRM supported blendshapes on more than one mesh.\n\n## Community Help & Collaboration\n\n- **Maximus helped emotionull** by providing the updated Hyperfy quickstart documentation link.\n\n- **Ashxn helped carlosmu** by explaining the v1 to v2 transition and providing multiple alternatives for building in v2, including self-hosting options, using hyperworld.host, building locally, or using play.hyperfy.xyz.\n\n- **Ashxn assisted lucii.io** with VRM export issues by suggesting the Blender VRM plugin should support multiple meshes, citing common avatar setups with separate opaque and transparent meshes.\n\n## Action Items\n\n### Technical\n- **Investigate editing the VRM plugin script** to support blendshapes on multiple meshes (mentioned by lucii.io)\n- **Check out self-hosting options for v2 world engine** for developers who want to start building in v2 (mentioned by Ashxn)\n- **Explore building in play.hyperfy.xyz** as an alternative to self-hosting where everyone has build permissions (mentioned by Ashxn)\n\n### Documentation\n- **Review updated v2 documentation** at docs.hyperfy.xyz, which is the new location for Hyperfy documentation (mentioned by Ashxn)\n\n### Feature\n- **Watch for upcoming v2 roadmap** which is coming soon (mentioned by Ashxn)" }, "github_summaries_daily_2025-05-09": { "filename": "2025-05-09.md", "content": "# ElizaOS Daily Update (May 9, 2025)\n\n## OVERVIEW \nToday's development efforts focused on enhancing the robustness of the ElizaOS framework, particularly in message handling and agent management. Key bug fixes were implemented to improve functionality, alongside documentation updates to assist users in setting up necessary tools. Overall, the team made significant strides in addressing existing issues and refining the user experience.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Bug Fixes and Enhancements\n- Fixed issues with the TTS manager and transcription processes, ensuring smoother audio handling ([#4496](https://github.com/elizaos/eliza/pull/4496)).\n- Resolved foreign key constraint violations when deleting agents that have been in a room ([#4510](https://github.com/elizaos/eliza/pull/4510)).\n- Enhanced message handling by adding null checks to prevent errors with empty messages ([#4508](https://github.com/elizaos/eliza/pull/4508)).\n\n### Documentation Updates\n- Updated the main README to include detailed installation instructions for FFmpeg, crucial for audio transcription ([#4496](https://github.com/elizaos/eliza/pull/4496)).\n- Created a new README file for Indian users to improve accessibility ([#4488](https://github.com/elizaos/eliza/pull/4488)).\n- Made additional updates to the README for testing purposes ([#4483](https://github.com/elizaos/eliza/pull/4483)).\n\n## CLOSED ISSUES\n\n### Resolved User Feedback\n- Closed an issue regarding line breaks being treated as spaces, following user feedback from a tweet ([#3897](https://github.com/elizaos/eliza/issues/3897)).\n\n## NEW ISSUES\n\n### Feature Requests\n- A new request for adding OLLAMA support has been raised, indicating a need for integration with this tool ([#4503](https://github.com/elizaos/eliza/issues/4503))." }, "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