{ "date_generated_for": "2025-05-06", "ai_news_elizaos_discord_md_2025-05-05": { "filename": "2025-05-05.md", "content": "# elizaOS Discord - 2025-05-05\n\n## Overall Discussion Highlights\n\n### ElizaOS Technical Issues & Development\n- Users troubleshooted ElizaOS installation errors, with one user resolving database adapter initialization issues by switching from WSL to Ubuntu via Microsoft Store\n- OpenAI plugin configuration issues were resolved by properly setting up API keys in .env files\n- Twitter agent functionality problems were reported where tweets stop generating after initial posts\n- Plugin development challenges included logging visibility problems and API failures\n- Discussions about building web terminals for ElizaOS and integrating custom plugins with projects\n\n### Auto.fun Platform Concerns\n- Significant trust issues emerged regarding the token verification process after the doglifeAI launch\n- The verification process was criticized for allowing a 5-minute window after launch before verification\n- Evidence suggested the doglifeAI team exploited this window for insider trading\n- Platform representative Ben acknowledged issues and proposed reducing verification time to 1 minute\n- Users reported technical issues including fake verification symbols and inability to edit token information\n- Token supply limitations were confirmed (cannot exceed 1 billion on auto.fun)\n\n### Token Requirements & Access\n- Updated token requirements were shared: 5M DEGEN or 100K AI16 for partners (previously 1M for DEGENPARTNER)\n- Brief mention of Comput3 launching on \"auto\" with limited details\n- Some users reported issues with token-gated chats giving error messages\n\n## Key Questions & Answers\n\n### ElizaOS Technical\n- **Q: How to fix \"Database adapter not initialized\" error in ElizaOS?** \n **A:** Install Ubuntu via Microsoft Store instead of using WSL, then run commands in Ubuntu CLI\n\n- **Q: How to resolve the \"No TEXT_EMBEDDING error\"?** \n **A:** Use \"elizaos start\", add the OpenAI plugin, and create a .env file with your OPENAI_API_KEY\n\n- **Q: Where is recommended to deploy a Twitter agent to avoid being banned/flagged?** \n **A:** Login with VPN close to server or grab cookies when logging in close to server and add to .env\n\n### Auto.fun Platform\n- **Q: How does the token verification process work?** \n **A:** Auto.fun arranges a timeframe with launch partners, verifies tokens after receiving confirmation of the contract address, and posts announcements within 30 seconds of verification\n\n- **Q: Why was the doglifeAI token verified at 400-500k market cap?** \n **A:** They can only verify after receiving confirmation from the launch partner, and they have a 5-minute cutoff which will be reduced to 1 minute\n\n- **Q: Why don't you launch tokens for teams instead of letting them do it?** \n **A:** It's important for partners to deploy their own tokens to decide allocation and update information\n\n- **Q: Is it possible for a token to have more than 1 billion supply if made on auto.fun?** \n **A:** No, tokens cannot exceed 1 billion supply on the platform\n\n### General Information\n- **Q: Where can I find more info about Comput3?** \n **A:** Head to #1361442528813121556 or ask in the comput3 community\n\n## Community Help & Collaboration\n\n1. **ElizaOS Installation Troubleshooting** \n User \"axs\" documented their process of resolving database adapter initialization errors by switching from WSL to Ubuntu via Microsoft Store, helping others who might encounter similar issues\n\n2. **OpenAI Plugin Configuration** \n Detailed steps were shared for resolving TEXT_EMBEDDING errors by properly configuring the OpenAI plugin with API keys\n\n3. **Twitter Agent Deployment** \n Tips were shared about using VPNs or grabbing cookies when logging in near the server location to avoid Twitter bans\n\n4. **Auto.fun Platform Improvement** \n User \"vas\" offered to compile detailed feedback in PDF format to help improve the platform's security against exploitation by launch partners\n\n5. **Token Verification Warning** \n User \"shad\" advised another user against buying the Doglife token due to suspicious launch patterns, potentially saving them from a bad investment\n\n## Action Items\n\n### Technical\n- Reduce token verification time from 5 minutes to 1 minute after launch (mentioned by Ben)\n- Implement pre-launch contract address verification by having partners share their screen before launching (mentioned by Ben)\n- Consider having auto.fun team launch tokens directly for partners to prevent insider trading (mentioned by dway)\n- Fix Twitter agent issue where tweets stop generating after initial post (mentioned by Alex)\n- Resolve plugin logging visibility in console (mentioned by axs)\n- Fix API failures in ElizaOS project (mentioned by axs)\n- Develop integration method for custom plugins with ElizaOS projects (mentioned by 🤠)\n- Build a server-side rendered terminal for ElizaOS (mentioned by axs)\n- Implement secure Twitter agent deployment strategy (mentioned by axs)\n- Fix token-gated chats that are giving error messages to users (mentioned by ryanthelad)\n- Fix website filters that aren't working properly (mentioned by Angelon)\n- Fix the ability to edit information and connect X accounts for imported CTO tokens (mentioned by nasdaq.ai)\n- Address site display issues showing outdated token information (mentioned by shad)\n- Implement better verification system to prevent fake verifications (mentioned by MDMnvest)\n- Improve anti-scam measures against fake support messages (mentioned by nasdaq.ai)\n\n### Documentation\n- Update information about token requirements for partners (5M DEGEN or 100K AI16) (mentioned by yikesawjeez)\n- Document proper ElizaOS installation process on different environments (mentioned by axs)\n- Create guide for plugin development and debugging (mentioned by axs)\n- Create clear guidelines for launch partners regarding verification timing and process (mentioned by shad)\n- Document improved vetting process for launch partners to prevent scams (mentioned by mhd)\n- Clarify token supply limitations on auto.fun (mentioned by hxf)\n- Explain how presale funds are handled for tokens (mentioned by velja)\n\n### Feature\n- Consider implementing Collabland for ELI5 token (mentioned by ryanthelad)\n- Improve plugin logging visibility (mentioned by axs)\n- Create character and pass it to plugin (mentioned by 🤠)" }, "ai_news_elizaos_discord_md_2025-05-04": { "filename": "2025-05-04.md", "content": "# elizaOS Discord - 2025-05-04\n\n## Overall Discussion Highlights\n\n### Security Incident with Token Verification\n- Multiple users reported losing money after purchasing tokens on Auto.fun that displayed verification checkmarks but were later revealed to be scams\n- Three specific token addresses were identified as exploited tokens: HgcHazC3qtetGZZBJ2wYkfkUmDZNUn5D4AmLbKG52FUN, 8jxqtVUjKJFonRzXGGeTzPBBegQAV3111EY97EV8sFUN, 78ShedfKV1iszLyRbjHVE46z5p7PRgPvQNwBTUqVRVSN\n- Kenk confirmed the team has investigated the issue, marked the contracts as scams, and isolated the verification process\n- The team requested 24 hours to implement a fix for the verification vulnerability\n- Users expressed frustration about the lack of transparency and demanded refunds for their losses\n\n### ElizaOS Development Updates\n- Shaw mentioned that \"Vibe coding\" agent feature is live on the `v2-develop` branch but with limited functionality\n- More updates to this feature expected in the coming weeks\n- A demo session was announced featuring seven different builders showcasing their projects: Steambot Willie, The Intern, ProAgentAI, Data Barista, Soulmates, Bork, and Phala + Eliza in TEE\n\n### Technical Implementation Challenges\n- Users reported difficulties with RAG Knowledge functionality, noting it pulls from OpenAI's prior knowledge rather than the provided knowledge base\n- Twitter API integration issues were discussed, with one user reporting their API account being limited after spending $400\n- Questions about execution order of provider, generateText, and evaluator handler functions in ElizaOS v0.25 were raised\n- A user reported losing access to chat rooms despite being a token holder\n\n## Key Questions & Answers\n\n**Q: Is Vibe coding getting rolled out in v2?** \nA: The agent is live on the `v2-develop` branch but with limited functionality currently, with more updates coming in the next couple weeks. (answered by shaw)\n\n**Q: What does the verified badge on Auto.fun mean?** \nA: It means \"the token is legit by one of the partners\" (answered by vas)\n\n**Q: What were the three exploited tokens with false verification?** \nA: HgcHazC3qtetGZZBJ2wYkfkUmDZNUn5D4AmLbKG52FUN, 8jxqtVUjKJFonRzXGGeTzPBBegQAV3111EY97EV8sFUN, 78ShedfKV1iszLyRbjHVE46z5p7PRgPvQNwBTUqVRVSN (answered by vas)\n\n**Q: Could we get a follow up and confirmation that the exploit is fixed?** \nA: The team is still exploring it. There's no 'exploit' as such. They have a fix and have isolated the verification process, requesting 24 hours to address the issue. (answered by Kenk)\n\n**Q: Do you think it was an inside job?** \nA: No, the team had a look, marked the contracts as scams, and determined everything was safe. (answered by Kenk)\n\n## Community Help & Collaboration\n\n- **User Access Issue**: human_nalejzpa helped Skullcross with their issue of losing roles and chat room access despite being a token holder, indicating they need to wait for someone to return from weekend vacation to fix the issue\n\n- **RAG Knowledge Resources**: rahmsc shared Discord message links to previous discussions about RAG knowledge implementation to help other users facing similar issues\n\n- **ElizaOS Versioning Clarification**: rahmsc explained to users that v2 is the new version of ElizaOS (beta.1.0.0)\n\n- **Verification Exploit Evidence**: vas and frank_grimes_sr provided evidence and token addresses of falsely verified tokens that were later unverified, helping the community understand the scope of the security incident\n\n## Action Items\n\n### Technical\n- **Fix verification system exploit** that allowed scam tokens to appear as verified | Mentioned by vas\n- **Resolve issue with token holders losing access** to roles and chat rooms | Mentioned by Skullcross\n- **Investigate why RAG Knowledge function** pulls from OpenAI's prior knowledge instead of provided knowledge base | Mentioned by rahmsc\n- **Resolve Twitter integration issues** in eliza-starter when credentials are properly configured | Mentioned by rahmsc\n- **Address execution order** of provider, generateText, and evaluator handler functions | Mentioned by 2spooky\n- **Investigate X API limitations** and potential configuration issues to prevent flagging | Mentioned by DavidRounders\n- **Fix Twitter link on CoinGecko page** for AI16Z coin that redirects to a placeholder page | Mentioned by Angelon\n- **Implement image generation functionality** for Eliza-Twitter integration | Mentioned by Tamplayz\n- **Continue development of \"Vibe coding\"** functionality | Mentioned by shaw\n\n### Documentation\n- **Create a post-mortem report** about the verification exploit incident | Mentioned by frank_grimes_sr\n- **Provide clear explanation** of what \"verified\" status means on the platform | Mentioned by gummy\n\n### Feature\n- **Implement better verification standards** that indicate legitimate projects with real utility rather than just X account connections | Mentioned by gummy\n- **Consider implementing verification** only after official Auto.fun tweet confirmation | Mentioned by Tocheee\n- **Implement refund mechanism** for users who lost funds due to verified scam tokens | Mentioned by frank_grimes_sr" }, "ai_news_elizaos_discord_md_2025-05-03": { "filename": "2025-05-03.md", "content": "# elizaOS Discord - 2025-05-03\n\n## Overall Discussion Highlights\n\n### Project Structure & Development\n- The ElizaOS ecosystem includes multiple components:\n - **AI16Z**: Focused on venture capital but \"fully AI\" with market cap fluctuating between $300-340M\n - **Auto.fun**: Recently launched open-source project for token creation/trading\n - **ElizaOS v1/Eliza v2**: AI agent framework (core codebase under development)\n - **DegenAI**: Associated with Degenspartan AI, with $4M market cap\n\n### Technical Issues\n- **Critical Codebase Problems**: TypeScript build errors in the elizaos/core package related to missing 'preconnect' property in fetch type definition\n- **Documentation Inconsistencies**: API examples no longer match actual implementation\n- **Collabland Verification Issues**: Persistent problems (48+ hours) with role verification for token holders\n- **Security Vulnerability**: Fake verified tokens appearing on Auto.fun platform, causing financial losses\n\n### Auto.fun Platform Discussions\n- **Token Economics**: Creators capture 90% of fees generated on native tokens\n- **Fee Structure**: Imported tokens likely don't generate the same fees since they use existing liquidity pools\n- **Community Vigilance**: Users actively identifying suspicious tokens, preventing potential scams\n\n## Key Questions & Answers\n\n### Project Information\n- **Q**: What is being built now? I thought ai16z was about replacing venture capital but all I see are stuff about trading bots? \n **A**: \"We are doing some VC, but it'll be fully AI. We have auto.fun, that we launched a few weeks ago. It's open source, as well. And we are working on ElizaOS v1, or Eliza v2... our AI agent/ai agent framework codebase. We also have degenai, which is degenspartan ai.\"\n\n- **Q**: Please what's this project all about ELI5? \n **A**: \"ELI5 is amazing, it has so much potential. can't wait to see ELI5 become a bot on twitter, telegram and potentially reshape education & FAQ sections on websites\"\n\n### Platform Functionality\n- **Q**: Is there a way to preset slippage on auto fun? \n **A**: \"I don't think so. I haven't seen anyone mention that, and I've been unable to do that myself.\"\n\n- **Q**: What are the fun-creator rewards? How much % of volume after migration does the dev wallet receive? \n **A**: \"Creators of the token capture 90% of the fees generated. It depends on gas fees at time of execution and LP.\"\n\n- **Q**: When importing a token, how do fees work? Will there be fees generated if volume transitions to auto.fun? \n **A**: \"I'd assume no fees are generated on imported tokens, since they already have liquidity pools that we don't control for trading.\"\n\n## Community Help & Collaboration\n\n### Security & Scam Prevention\n- **Simon** identified a suspicious token claiming to be \"comput3\" that appeared verified. **Kenk** confirmed with the team that it was fake and flagged it, preventing Simon from investing.\n\n### Technical Support\n- **yikesawjeez** assisted **Void** with role verification issues, requesting wallet address and screenshots to troubleshoot.\n- **jin** acknowledged Collabland verification issues affecting multiple users and began investigating.\n- **Osint** explained to **Ric Q** that responses from another team member would likely come on Monday due to the weekend.\n\n### Platform Usage\n- **yikesawjeez** helped **SYMBiEX** understand the fee structure for imported tokens versus native Auto.fun launches.\n- **Osint** suggested to **nasdaq.ai** to submit a report to support when they couldn't share video from auto.fun to X.\n\n## Action Items\n\n### Technical\n- **Fix Collabland role verification issues** (Mentioned by multiple users)\n- **Fix TypeScript error regarding missing 'preconnect' property** in fetch type definition (Mentioned by lantianlaoli)\n- **Implement pre-push code quality checks** to prevent broken code from being pushed to main branch (Mentioned by lantianlaoli)\n- **Investigate and fix vulnerability** allowing fake verified tokens on the platform (Mentioned by frank_grimes_sr)\n- **Implement refund process** for users affected by fake verified tokens (Mentioned by frank_grimes_sr)\n- **Improve token verification system** to address issue that allowed fake token to appear verified (Mentioned by Kenk)\n\n### Documentation\n- **Clarify the different projects under development** (AI16Z, Auto.fun, ElizaOS, DegenAI) (Mentioned by EBITDA)\n- **Update API documentation** to match current implementation (Mentioned by lantianlaoli)\n- **Clarify what \"verified\" status actually means** for tokens on the platform (Mentioned by yikesawjeez)\n- **Explain fee structure** for migrated vs. native tokens (Mentioned by SYMBiEX)\n- **Provide guidance on volume generation strategies** for tokens (Mentioned by nasdaq.ai)\n\n### Features\n- **Continue development on ElizaOS v1/Eliza v2** AI agent framework (Mentioned by Osint)\n- **Create Twitter agent for specific blockchain projects** that posts daily updates and news (Mentioned by MIR)\n- **Implement cryptocurrency market data functionality** (CMC info retrieval for price, volume, marketcap) (Mentioned by lantianlaoli)\n- **Add token swap and transfer with status feedback** (UI feedback during transactions and tx hash links) (Mentioned by lantianlaoli)\n- **Implement token deployment functionality** (Mentioned by lantianlaoli)\n- **Integrate with wallet connection** instead of private keys for improved security (Mentioned by lantianlaoli)\n- **Add ability to preset slippage on auto.fun** (Currently resets to 2% each time) (Mentioned by noj)\n- **Pin degenai on auto.fun** for better visibility (Mentioned by Void)\n- **Add social media sharing functionality** (\"share on X\" button for coins) (Mentioned by Spyros)" }, "ai_news_elizaos_dev_md_2025-05-05": { "filename": "2025-05-05.md", "content": "# elizaOS Development Discord - 2025-05-05\n\n## Overall Discussion Highlights\n\n### Agent Development & Troubleshooting\n- Users reported issues with Telegram agent setup, specifically a \"No world found for user during onboarding\" error\n- Discussion about Twitter agent deployment best practices to avoid account flagging\n- Questions about agent behavior, including a 24-hour window for agent responses\n- Concerns about API functionality, particularly the sendmessage API not working\n\n### Technical Infrastructure\n- Plugin architecture compatibility issues between Bun and Node runtimes were discussed\n- Ruby explained the goal is to standardize the plugin system for consistent functionality across environments\n- A user successfully ran a Vite application locally but needed help calling an API from Postman\n\n### Community Projects\n- Scott Milner is looking for testers for a ChatGPT-integrated app for creating canned responses\n- A user named \"lost\" submitted a PR for Indonesian translation to the elizaOS/eliza repository\n\n## Key Questions & Answers\n\n**Q: While building a telegram agent I am running into the error \"No world found for user during onboarding\" what does this mean?** \nA: \"That error usually means the world creation step failed during setup. Check that you have WORLD_ID set in your .env and that your database migrations ran successfully. Try running 'elizaos db:migrate' first, then attempt the telegram agent setup again.\" (answered by Ruby)\n\n**Q: What is the end goal for the plugin architecture? Now, depending on which elizaos (in .bun or in the nvm/node path) the plugins fail to mount.** \nA: \"The goal is to have a unified plugin system where plugins work consistently regardless of runtime. Right now there's a known issue with path resolution between bun/node environments. We're working on standardizing how plugins are discovered and mounted. For now, I'd recommend sticking to one runtime (preferably node) until we get this sorted out.\" (answered by Ruby)\n\n**Q: Where is recommended to deploy a twitter agent to not get banned/flagged? I imagine that if it's some datacenter IP, twitter blocks them, right?** \nA: \"Yeah, datacenter IPs are a red flag for twitter. Your best bet is using residential proxies or a VPN service that rotates residential IPs. I've had good luck with Bright Data's residential network, but there are cheaper options if you're just testing.\" (answered by Ruby)\n\n**Q: Can you help me with my Indonesian translation PR that's getting blocked?** \nA: \"Yes, the issue is that merges to main branch are only allowed from the develop branch, not from patch-3.\" (answered by Ruby)\n\n## Community Help & Collaboration\n\n### Telegram Agent Troubleshooting\nRuby provided detailed guidance to StarCat on resolving the \"No world found for user during onboarding\" error by suggesting database migration checks and environment variable verification.\n\n### Plugin Architecture Support\nRuby helped kandizzy understand the current limitations of the plugin system across different runtimes and recommended sticking to Node until standardization is complete.\n\n### Twitter Agent Deployment Advice\nRuby advised morlok on avoiding Twitter account flagging by using residential proxies instead of datacenter IPs, specifically recommending Bright Data's residential network.\n\n### Pull Request Workflow Assistance\nRuby guided \"lost\" through the proper GitHub workflow for submitting a translation PR:\n1. Creating a new branch from develop\n2. Transferring the Indonesian translation files\n3. Targeting the develop branch with the PR\n4. Offered both git command sequence and GitHub web UI approaches\n\n### Twitter Agent Resources\n0xbbjoker shared a Discord channel link with yoyoha regarding Twitter agent v2 implementation information.\n\n## Action Items\n\n### Technical\n- **Standardize plugin discovery and mounting across different runtimes** - Fix path resolution issues between Bun/Node environments (Mentioned by Ruby)\n- **Implement proper database migration checks during agent setup** - Prevent \"No world found\" errors by ensuring migrations complete successfully (Mentioned by Ruby)\n- **Investigate why sendmessage API doesn't work** - User reported an issue with the API (Mentioned by OpsDev)\n- **Create a new branch from develop instead of targeting main directly** - Follow proper branch workflow for contributions (Mentioned by Ruby)\n- **Transfer Indonesian translation from patch-3 to a new feature branch** - Copy README_IND.md to the proper branch (Mentioned by Ruby)\n- **Update PR to target the develop branch instead of main** - Change PR target branch to comply with repository rules (Mentioned by Ruby)\n\n### Documentation\n- **Develop proxy configuration guide for Twitter agents** - Document how to set up residential proxies to avoid account flagging (Mentioned by Ruby)\n\n### Feature\n- **Testing app for creating canned responses with ChatGPT integration** - Looking for testers for an application that helps with rephrasing and formatting text (Mentioned by Scott Milner)" }, "ai_news_elizaos_dev_md_2025-05-04": { "filename": "2025-05-04.md", "content": "# elizaOS Development Discord - 2025-05-04\n\n## Overall Discussion Highlights\n\n### Plugin Development in V2\n- Users are experiencing challenges with plugin development in elizaOS V2, particularly due to outdated documentation that doesn't align with the latest codebase\n- The community is actively sharing workarounds and solutions for plugin integration\n- Several commands were shared for creating and testing plugins:\n - `npx @elizaos/cli@beta create` - Create new projects for plugin development\n - `bun run dev` - Run development environment\n - `elizaos --help` - Access the latest command information\n\n### Upcoming Releases\n- **V2 Release Timeline**: shaw mentioned that V2 will be released in approximately two weeks\n- Improved tutorials are planned to accompany the V2 release\n- Official documentation is available at docs.eliza.how, though some sections may need updates\n\n## Key Questions & Answers\n\n**Q: How do I add plugins in version V2 and test them after development?** (asked by lantianlaoli) \n**A:** Put plugins into packages or use \"npx @elizaos/cli@beta create\" to create a project, then \"bun run dev\" in it, and add plugins by bun installing or adding to the character object in the plugins string (answered by shaw)\n\n**Q: Is there a plugin starter available?** (asked by ItzMrTobz) \n**A:** Yes, it's available at https://github.com/elizaOS/eliza/tree/v2-develop/packages/plugin-starter (answered by sayonara)\n\n## Community Help & Collaboration\n\n- **shaw** provided detailed guidance to **lantianlaoli** who was confused about the plugin development workflow in V2, offering specific commands and explaining the process for creating projects and adding plugins\n- **sayonara** helped **ItzMrTobz** by sharing the GitHub link to the official plugin starter repository\n- The community is actively sharing workarounds while waiting for documentation to be updated\n\n## Action Items\n\n### Technical\n- Update documentation to match latest code and commands (mentioned by lantianlaoli)\n- Fix incorrect plugin path syntax in test commands - missing ./ prefix (mentioned in agent-dev-school)\n\n### Documentation\n- Create comprehensive tutorial series for V2 (mentioned by shaw)\n- Update official docs.eliza.how with V2-specific information\n\n### Feature\n- Release elizaOS V2 in approximately two weeks (mentioned by shaw)\n\n---\n\n*Note: A brief acknowledgment message \"noted\" was posted by shaw in the feedback channel, but without additional context.*" }, "ai_news_elizaos_dev_md_2025-05-03": { "filename": "2025-05-03.md", "content": "# elizaOS Development Discord - 2025-05-03\n\n## Overall Discussion Highlights\n\n### Development Branches & Version Management\n- Discussion about the differences between ElizaOS version 1.0.0.Beta 41 (current stable release) and V2 (development branch)\n- V2 branch includes new features like improved plugin architecture, enhanced character system, and better multimodal support\n- Timeline for V2 stable release is estimated at \"a few months\" according to Ruby\n- Clarification that \"v2-develop\" is the recommended branch for plugin development\n\n### CLI Installation Issues\n- Multiple users experienced difficulties updating the ElizaOS CLI from beta.38 to beta.41\n- Various installation methods were attempted (npm, GitHub, local build) with mixed results\n- Persistent version conflicts observed where the system reports an older version despite successful installation of newer version\n\n### Feature Requests\n- Request for cryptocurrency-related functionality including:\n - Token price/data retrieval\n - Token swapping and transfers with status updates\n - Token deployment capabilities\n - Wallet connection integration\n\n## Key Questions & Answers\n\n**Q: What is the difference between ElizaOS version 1.0.0.Beta 41 and V2?** \nA: V2 is the development branch which will eventually become 2.0, while beta.41 is the current stable release. V2 has a new plugin architecture, improved character system, and better multimodal support. (answered by Ruby)\n\n**Q: When will V2 be available?** \nA: V2's timeline is still fluid, but we're looking at a few months for stable release. (answered by Ruby)\n\n**Q: Which codebase should I use to develop a simple text chat plugin?** \nA: Use the v2-develop branch. (answered by shaw)\n\n**Q: How can I update the ElizaOS CLI from beta.38 to beta.41?** \nA: Try running 'npm i -g @elizaos/cli@beta' to install the latest beta version directly. (answered by sayonara)\n\n## Community Help & Collaboration\n\n1. **CLI Update Troubleshooting**\n - Helper: Ruby & sayonara\n - Helpee: kandizzy\n - Context: CLI update failing with 404 error\n - Resolution: Partially successful - guided through multiple approaches including npm install, GitHub install, and building from monorepo, but version conflict persisted\n\n2. **Plugin Development Guidance**\n - Helper: shaw\n - Helpee: lantianlaoli\n - Context: User was confused about which codebase to use for developing a text chat plugin\n - Resolution: Suggested using \"v2-develop\" branch\n\n3. **Version Clarification**\n - Helper: Ruby\n - Helpee: BMK\n - Context: Confusion about ElizaOS versions\n - Resolution: Explained that V2 is the development branch with new features while Beta 41 is the stable release\n\n## Action Items\n\n### Technical\n- Fix dependency loop issues in bun link/unlink functionality (Mentioned by Ruby)\n- Resolve version reporting inconsistency between npm and elizaos CLI (Mentioned by kandizzy)\n- Develop a text chat plugin using the v2-develop branch (Mentioned by lantianlaoli)\n- Address unspecified issue in next beta release (Mentioned by sayonara)\n\n### Feature Development\n- Create functionality to retrieve token information (price, volume, marketcap) (Mentioned by OpsDev | Onyx)\n- Implement token swap and transfer functionality with status updates and transaction hash links (Mentioned by OpsDev | Onyx)\n- Add token deployment capabilities (Mentioned by OpsDev | Onyx)\n- Integrate wallet connection without private key usage (Mentioned by OpsDev | Onyx)\n\n### Documentation\n- Create clearer documentation about version differences between stable and development branches (Mentioned by BMK)" }, "ai_news_elizaos_daily_json_2025-05-05": { "filename": "2025-05-05.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-05", "categories": [ { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "AI Agent Development", "text": "User @shawmakesmagic shared updates about developing AI agents and tools. They mentioned working on an Eliza todo list agent app, sharing a screenshot of the work in progress. They also discussed a project called 'The System' that needs further development, sharing WIP code and seeking help to build full-featured agents. @shawmakesmagic noted that agents work across platforms while tools work alone, as echoed by @elizaOS who tweeted 'Tools work alone, Agents work across.' When discussing agent performance with @ScholarChris, @shawmakesmagic mentioned that AI agents are 'surprisingly good just slow' compared to humans who operate at '30+ apm,' making it difficult for smart agents to respond quickly. @autodotfun announced that @DogLifeAI (by @drpepeai) is joining their platform as an 'AI-powered healthspan companion' for dogs, stating that 'agents are for everyone, especially dogs.'", "sources": [ "https://twitter.com/shawmakesmagic/status/1919182260072558619", "https://twitter.com/shawmakesmagic/status/1919182731885621595", "https://twitter.com/shawmakesmagic/status/1919183969683124476", "https://twitter.com/elizaOS/status/1919400899094385083", "https://twitter.com/autodotfun/status/1919425975487434912", "https://twitter.com/autodotfun/status/1919425979606241465", "https://twitter.com/autodotfun/status/1919425982492033169", "https://twitter.com/autodotfun/status/1919436480000262189", "https://twitter.com/shawmakesmagic/status/1919532307100184803" ], "images": [ "https://pbs.twimg.com/media/GqJN5deaEAALdS5.jpg", "https://pbs.twimg.com/media/GqMXuFKXAAASydw.jpg" ], "videos": [] }, { "theme_title": "Metaverse and Simulation Theory", "text": "@shawmakesmagic shared thoughts on simulation theory and the metaverse. They proposed that 'the metaverse was just a benchmark for agents' and described an 'AI MMO' where the 'highest level richest agent wins.' When discussing simulation theory with @descam2_agent_1 and @xenothales, @shawmakesmagic stated 'I feel simulated' and suggested that 'this moment will be recreated infinite times in the future,' though they applied Occam's razor to suggest this is likely base reality. They described themselves as a 'Simulation engineer working on 3D multiplayer worlds and AI' and pondered if our reality might become a simulation as computers evolve over the next 50 years. In a poetic reflection, @shawmakesmagic tweeted 'We are the monkeys, We built the typewriters, We wrote the shakespeare' and later added 'Now the typewriters write the Shakespeare without us,' to which @rabb1dfly responded about 'infinite monkeys on infinite keyboards' writing 'the entire history of the universe.'", "sources": [ "https://twitter.com/shawmakesmagic/status/1919500406201397256", "https://twitter.com/shawmakesmagic/status/1919504188288983465", "https://twitter.com/shawmakesmagic/status/1919510896646181144", "https://twitter.com/shawmakesmagic/status/1919511336238907634", "https://twitter.com/shawmakesmagic/status/1919511461908578654", "https://twitter.com/shawmakesmagic/status/1919513780402131161", "https://twitter.com/shawmakesmagic/status/1919514075777925349", "https://twitter.com/shawmakesmagic/status/1919530052812734761", "https://twitter.com/rabb1dfly/status/1919504393847591104" ], "images": [], "videos": [] }, { "theme_title": "Political and Social Commentary", "text": "@shawmakesmagic shared several thoughts on political and social issues. They expressed concern about political polarization, stating 'You're either pro America or you are pro civil war' and criticizing those who foment hatred toward fellow citizens as 'Civil War-mongerers.' When discussing economic policy with @super_projects, @shawmakesmagic argued against forced wealth redistribution, suggesting it creates 'corrupt politicians' and 'perverse incentives,' ultimately making 'revolutionary politicians the new wealth class.' They expressed skepticism about UBI, noting that 'expecting our politicians to tax the people who bribed them into office is unlikely to be effective.' However, they acknowledged that 'solving these crisis could be the purpose we need' and that 'within the problem lies the solution.' In a separate exchange, @shawmakesmagic criticized someone for making the conversation too partisan, stating 'You've dragged a complex conversation down to us vs you.'", "sources": [ "https://twitter.com/shawmakesmagic/status/1919489683907604654", "https://twitter.com/shawmakesmagic/status/1919490362827276701", "https://twitter.com/shawmakesmagic/status/1919491008460407129", "https://twitter.com/shawmakesmagic/status/1919498975079514551", "https://twitter.com/shawmakesmagic/status/1919501284996219086", "https://twitter.com/shawmakesmagic/status/1919502605732216893", "https://twitter.com/shawmakesmagic/status/1919504418988232849" ], "images": [], "videos": [] }, { "theme_title": "Technology Advancements", "text": "@shawmakesmagic retweeted an announcement from @BrianRoemmele about Stanford launching FramePack, described as 'A FREE OPEN SOURCE AI THAT CAN RUN ON 6 GB LAPTOP GPU TO GENERATE MINUTE LONG 30FPS VIDEO FROM SINGLE IMAGE.' The retweet included a video demonstration of the technology. In a separate conversation with @Flowslikeosmo about technology trends, @shawmakesmagic suggested that 'fundamental technology will be defined by cycles more than metas' and noted that 'People were just chasing meta before because the tech had no substance' while 'Some of us have been coding 80 hours a week since then.'", "sources": [ "https://twitter.com/BrianRoemmele/status/1919485829996794280", "https://twitter.com/shawmakesmagic/status/1919500812490813521", "https://twitter.com/shawmakesmagic/status/1919502830165012959" ], "images": [ "https://pbs.twimg.com/amplify_video_thumb/1919485764758601728/img/ULDkxBFz2_3DVTup.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1919485764758601728/vid/avc1/978x720/upbgNdZxV7ByR75J.mp4?tag=16" ] }, { "theme_title": "Cryptocurrency and Blockchain Projects", "text": "@autodotfun shared information about $DOGLIFEAI token, explaining that it 'grants premium access to advanced diagnostics, IP ownership for stakers, and future airdrops in https://t.co/SkdAXw5W0S's ecosystem.' They emphasized that the project is a fair launch with 'grassroots support from day 1' and that 'liquidity NFTs = funding for new features.' @shawmakesmagic mentioned working on a v2 release for a project, telling @rabb1dfly and @S4mmyEth that 'things are quiet for a little longer while we prepare the v2 release.' When asked about a character named Eddy, @shawmakesmagic clarified that 'Eddy is open source, anyone can run him' and mentioned having 'too many tokens to take care of.'", "sources": [ "https://twitter.com/autodotfun/status/1919425979606241465", "https://twitter.com/autodotfun/status/1919425982492033169", "https://twitter.com/shawmakesmagic/status/1919506863395357123", "https://twitter.com/shawmakesmagic/status/1919507127301030111", "https://twitter.com/shawmakesmagic/status/1919507402044661855", "https://twitter.com/shawmakesmagic/status/1919509285123305963" ], "images": [], "videos": [] }, { "theme_title": "Personal Projects and Interests", "text": "@shawmakesmagic shared various personal interests and project details. They mentioned taking what was supposed to be a day off but instead made a hyperfy plugin. When discussing a screenshot from Solo Leveling, they mentioned working on a '1:1 interface down to the font and regimen.' @shawmakesmagic also asked followers what 'people who think gyms are gross and unappealing do,' indicating a personal interest in fitness. In response to @lynk0x sharing something gaming-related, @shawmakesmagic enthusiastically responded 'Oh my god I am, I played the shit out of this.' @dankvr shared a photo with @shawmakesmagic with the caption 'Every great founder is a workaholic who followed their passion until it became their profession,' suggesting @shawmakesmagic's dedication to their work.", "sources": [ "https://twitter.com/shawmakesmagic/status/1919185987344728477", "https://twitter.com/shawmakesmagic/status/1919186489797124381", "https://twitter.com/shawmakesmagic/status/1919302786128449770", "https://twitter.com/shawmakesmagic/status/1919495572945289378", "https://twitter.com/dankvr/status/1919399896638992780" ], "images": [ "https://pbs.twimg.com/media/GqMUCMAWMAA8i_r.jpg" ], "videos": [] } ], "topic": "twitter_activity" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Recent pull requests to the elizaOS/eliza repository include several feature additions and fixes. User monilpat submitted PR #4449 adding polygon functionality. User K1mc4n made multiple submissions related to Indonesian documentation (PRs #4451, #4452, #4453, and #4455 for README_IND.md creation and improvements). User samarth30 contributed PR #4462 for a project manager feature named 'Jimmy'. User bowtiedbluefin created PR #4466 to add a Morpheus plugin. On the bug fix side, standujar addressed a discord service unregister timeout issue in PR #4450, while ChristopherTrimboli fixed client scroll bars in PR #4465.", "sources": [ "https://github.com/elizaOS/eliza/pull/4449", "https://github.com/elizaOS/eliza/pull/4451", "https://github.com/elizaOS/eliza/pull/4452", "https://github.com/elizaOS/eliza/pull/4453", "https://github.com/elizaOS/eliza/pull/4455", "https://github.com/elizaOS/eliza/pull/4462", "https://github.com/elizaOS/eliza/pull/4466", "https://github.com/elizaOS/eliza/pull/4450", "https://github.com/elizaOS/eliza/pull/4465" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4449", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4451", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4452", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4453", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4455", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4462", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4466", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4450", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4465" ], "videos": [] } ], "topic": "pull_request" }, { "title": "Summary for completed_items", "content": [ { "text": "Recent completed items in the elizaOS/eliza repository include several bugfixes: updating a broken image path in the Thai README (PR #4433), fixing plugin installation command plugins and start functionality (PR #4456), resolving version installation issues (PR #4454), addressing Discord service unregister timeout (PR #4450), fixing client scroll bars (PR #4465), and correcting bunx/npx detection (PR #4463).", "sources": [ "https://github.com/elizaOS/eliza/pull/4433", "https://github.com/elizaOS/eliza/pull/4456", "https://github.com/elizaOS/eliza/pull/4454", "https://github.com/elizaOS/eliza/pull/4450", "https://github.com/elizaOS/eliza/pull/4465", "https://github.com/elizaOS/eliza/pull/4463" ], "images": [], "videos": [] }, { "text": "Other completed items include documentation updates to fix broken Eliza documentation links (PR #4460), a feature addition to include elizadb in .gitignore (PR #4464), and a maintenance task to remove plugin-redpill from the monorepo (PR #4428).", "sources": [ "https://github.com/elizaOS/eliza/pull/4460", "https://github.com/elizaOS/eliza/pull/4464", "https://github.com/elizaOS/eliza/pull/4428" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Summary for github_summary", "content": [ { "text": "Over a two-day period (May 5-7, 2025), the elizaos/eliza repository showed consistent development activity. The repository had 15 new pull requests (9 merged), 2 new issues, and maintained an active contributor base that grew from 9 to 11 contributors.", "sources": [ "source 1", "source 2" ], "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 #4457 reports a 'pglite log entry unicode escape error' submitted by user plvo. Issue #4461 notes that 'settings.discord.autoPost is not implemented yet in eliza v2' and was submitted by user POKENA7.", "sources": [ "https://github.com/elizaOS/eliza/issues/4457", "https://github.com/elizaOS/eliza/issues/4461" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4457", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4461" ], "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": 1746403200 } }, "ai_news_elizaos_daily_md_2025-05-05": { "filename": "2025-05-05.md", "content": "# Daily Report - 2025-05-05\n\n## Twitter Activity\n\n### AI Agent Development\n- @shawmakesmagic shared updates about developing AI agents and tools, including an Eliza todo list agent app with a screenshot of the work in progress.\n- @shawmakesmagic discussed \"The System\" project that needs further development, sharing WIP code and seeking help to build full-featured agents.\n- @shawmakesmagic and @elizaOS noted that \"agents work across platforms while tools work alone.\"\n- In a discussion with @ScholarChris, @shawmakesmagic mentioned AI agents are \"surprisingly good just slow\" compared to humans who operate at \"30+ apm.\"\n- @autodotfun announced that @DogLifeAI (by @drpepeai) is joining their platform as an \"AI-powered healthspan companion\" for dogs.\n- Sources: https://twitter.com/shawmakesmagic/status/1919182260072558619, https://twitter.com/shawmakesmagic/status/1919182731885621595, https://twitter.com/shawmakesmagic/status/1919183969683124476, https://twitter.com/elizaOS/status/1919400899094385083, https://twitter.com/autodotfun/status/1919425975487434912, https://twitter.com/autodotfun/status/1919425979606241465, https://twitter.com/autodotfun/status/1919425982492033169, https://twitter.com/autodotfun/status/1919436480000262189, https://twitter.com/shawmakesmagic/status/1919532307100184803\n\n### Metaverse and Simulation Theory\n- @shawmakesmagic proposed that \"the metaverse was just a benchmark for agents\" and described an \"AI MMO\" where the \"highest level richest agent wins.\"\n- When discussing simulation theory with @descam2_agent_1 and @xenothales, @shawmakesmagic stated \"I feel simulated\" and suggested \"this moment will be recreated infinite times in the future.\"\n- @shawmakesmagic described themselves as a \"Simulation engineer working on 3D multiplayer worlds and AI\" and pondered if our reality might become a simulation.\n- In a poetic reflection, @shawmakesmagic tweeted \"We are the monkeys, We built the typewriters, We wrote the shakespeare\" and later added \"Now the typewriters write the Shakespeare without us.\"\n- Sources: https://twitter.com/shawmakesmagic/status/1919500406201397256, https://twitter.com/shawmakesmagic/status/1919504188288983465, https://twitter.com/shawmakesmagic/status/1919510896646181144, https://twitter.com/shawmakesmagic/status/1919511336238907634, https://twitter.com/shawmakesmagic/status/1919511461908578654, https://twitter.com/shawmakesmagic/status/1919513780402131161, https://twitter.com/shawmakesmagic/status/1919514075777925349, https://twitter.com/shawmakesmagic/status/1919530052812734761, https://twitter.com/rabb1dfly/status/1919504393847591104\n\n### Political and Social Commentary\n- @shawmakesmagic expressed concern about political polarization, stating \"You're either pro America or you are pro civil war.\"\n- In a discussion with @super_projects, @shawmakesmagic argued against forced wealth redistribution, suggesting it creates \"corrupt politicians\" and \"perverse incentives.\"\n- @shawmakesmagic expressed skepticism about UBI, noting that \"expecting our politicians to tax the people who bribed them into office is unlikely to be effective.\"\n- @shawmakesmagic acknowledged that \"solving these crisis could be the purpose we need\" and that \"within the problem lies the solution.\"\n- Sources: https://twitter.com/shawmakesmagic/status/1919489683907604654, https://twitter.com/shawmakesmagic/status/1919490362827276701, https://twitter.com/shawmakesmagic/status/1919491008460407129, https://twitter.com/shawmakesmagic/status/1919498975079514551, https://twitter.com/shawmakesmagic/status/1919501284996219086, https://twitter.com/shawmakesmagic/status/1919502605732216893, https://twitter.com/shawmakesmagic/status/1919504418988232849\n\n### Technology Advancements\n- @shawmakesmagic retweeted an announcement from @BrianRoemmele about Stanford launching FramePack, described as \"A FREE OPEN SOURCE AI THAT CAN RUN ON 6 GB LAPTOP GPU TO GENERATE MINUTE LONG 30FPS VIDEO FROM SINGLE IMAGE.\"\n- In a conversation with @Flowslikeosmo about technology trends, @shawmakesmagic suggested that \"fundamental technology will be defined by cycles more than metas.\"\n- @shawmakesmagic noted that \"People were just chasing meta before because the tech had no substance\" while \"Some of us have been coding 80 hours a week since then.\"\n- Sources: https://twitter.com/BrianRoemmele/status/1919485829996794280, https://twitter.com/shawmakesmagic/status/1919500812490813521, https://twitter.com/shawmakesmagic/status/1919502830165012959\n\n### Cryptocurrency and Blockchain Projects\n- @autodotfun shared information about $DOGLIFEAI token, explaining that it \"grants premium access to advanced diagnostics, IP ownership for stakers, and future airdrops in https://t.co/SkdAXw5W0S's ecosystem.\"\n- @autodotfun emphasized that the project is a fair launch with \"grassroots support from day 1\" and that \"liquidity NFTs = funding for new features.\"\n- @shawmakesmagic mentioned working on a v2 release for a project, telling @rabb1dfly and @S4mmyEth that \"things are quiet for a little longer while we prepare the v2 release.\"\n- @shawmakesmagic clarified that \"Eddy is open source, anyone can run him\" and mentioned having \"too many tokens to take care of.\"\n- Sources: https://twitter.com/autodotfun/status/1919425979606241465, https://twitter.com/autodotfun/status/1919425982492033169, https://twitter.com/shawmakesmagic/status/1919506863395357123, https://twitter.com/shawmakesmagic/status/1919507127301030111, https://twitter.com/shawmakesmagic/status/1919507402044661855, https://twitter.com/shawmakesmagic/status/1919509285123305963\n\n### Personal Projects and Interests\n- @shawmakesmagic shared that they took what was supposed to be a day off but instead made a hyperfy plugin.\n- @shawmakesmagic mentioned working on a \"1:1 interface down to the font and regimen\" when discussing a screenshot from Solo Leveling.\n- @shawmakesmagic asked followers what \"people who think gyms are gross and unappealing do,\" indicating a personal interest in fitness.\n- @dankvr shared a photo with @shawmakesmagic with the caption \"Every great founder is a workaholic who followed their passion until it became their profession.\"\n- Sources: https://twitter.com/shawmakesmagic/status/1919185987344728477, https://twitter.com/shawmakesmagic/status/1919186489797124381, https://twitter.com/shawmakesmagic/status/1919302786128449770, https://twitter.com/shawmakesmagic/status/1919495572945289378, https://twitter.com/dankvr/status/1919399896638992780\n\n## GitHub Activity for elizaOS/eliza\n\n### Pull Requests\n- User monilpat submitted PR #4449 adding polygon functionality.\n- User K1mc4n made multiple submissions related to Indonesian documentation (PRs #4451, #4452, #4453, and #4455 for README_IND.md creation and improvements).\n- User samarth30 contributed PR #4462 for a project manager feature named 'Jimmy'.\n- User bowtiedbluefin created PR #4466 to add a Morpheus plugin.\n- User standujar addressed a discord service unregister timeout issue in PR #4450.\n- User ChristopherTrimboli fixed client scroll bars in PR #4465.\n- Sources: https://github.com/elizaOS/eliza/pull/4449, https://github.com/elizaOS/eliza/pull/4451, https://github.com/elizaOS/eliza/pull/4452, https://github.com/elizaOS/eliza/pull/4453, https://github.com/elizaOS/eliza/pull/4455, https://github.com/elizaOS/eliza/pull/4462, https://github.com/elizaOS/eliza/pull/4466, https://github.com/elizaOS/eliza/pull/4450, https://github.com/elizaOS/eliza/pull/4465\n\n### Completed Items\n- Several bugfixes were completed: updating a broken image path in the Thai README (PR #4433), fixing plugin installation command plugins and start functionality (PR #4456), resolving version installation issues (PR #4454), addressing Discord service unregister timeout (PR #4450), fixing client scroll bars (PR #4465), and correcting bunx/npx detection (PR #4463).\n- Documentation updates were completed to fix broken Eliza documentation links (PR #4460).\n- A feature was added to include elizadb in .gitignore (PR #4464).\n- A maintenance task was completed to remove plugin-redpill from the monorepo (PR #4428).\n- Sources: https://github.com/elizaOS/eliza/pull/4433, https://github.com/elizaOS/eliza/pull/4456, https://github.com/elizaOS/eliza/pull/4454, https://github.com/elizaOS/eliza/pull/4450, https://github.com/elizaOS/eliza/pull/4465, https://github.com/elizaOS/eliza/pull/4463, https://github.com/elizaOS/eliza/pull/4460, https://github.com/elizaOS/eliza/pull/4464, https://github.com/elizaOS/eliza/pull/4428\n\n### Repository Summary\n- Over a two-day period (May 5-7, 2025), the elizaos/eliza repository had 15 new pull requests (9 merged) and 2 new issues.\n- The active contributor base grew from 9 to 11 contributors.\n- Sources: source 1, source 2\n\n### Issues\n- Issue #4457 reports a 'pglite log entry unicode escape error' submitted by user plvo.\n- Issue #4461 notes that 'settings.discord.autoPost is not implemented yet in eliza v2' and was submitted by user POKENA7.\n- Sources: https://github.com/elizaOS/eliza/issues/4457, https://github.com/elizaOS/eliza/issues/4461" }, "ai_news_elizaos_daily_discord_json_2025-05-05": { "filename": "2025-05-05.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-05", "date": 1746403200, "stats": { "totalMessages": 325, "totalUsers": 36 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe chat segment shows minimal technical discussion. The conversation primarily consists of greetings and brief exchanges about tokens and access issues. There appears to be some confusion regarding a Collabland-related problem that some users are experiencing. A user named yikesawjeez clarifies that there are no Collabland issues and mentions updated token requirements: 5M DEGEN or 100K AI16 for partners (previously 1M for DEGENPARTNER). There's also a brief mention of Comput3, which will apparently launch on \"auto,\" though details are sparse. Several users express frustration about waiting for something unspecified. The chat includes some references to ELI5 and various tokens including CRIMELI5, but contains very little substantive technical content or problem-solving.\n\n## 2. FAQ\nQ: Where can I find more info about Comput3? (asked by Scanorr_) A: Head to #1361442528813121556 or ask in the comput3 community (answered by Kenk)\nQ: Can i dm a moderator with a quick question? (asked by dway) A: Unanswered\nQ: Can we get a collabland for eli5? (asked by ryanthelad) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: Scanorr_ | Context: User needed information about Comput3 | Resolution: Directed user to appropriate channel and community\nHelper: yikesawjeez | Helpee: Multiple users | Context: Confusion about Collabland issues | Resolution: Clarified there were no issues and provided updated token requirements\n\n## 4. Action Items\nDocumentation: Update information about token requirements for partners (5M DEGEN or 100K AI16) | Mentioned By: yikesawjeez\nFeature: Consider implementing Collabland for ELI5 token | Mentioned By: ryanthelad", "messageCount": 35, "userCount": 15 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily focused on troubleshooting ElizaOS installation and plugin issues. One user resolved database adapter initialization errors by switching from WSL to Ubuntu via Microsoft Store and properly configuring the OpenAI plugin with an API key. Another user encountered issues with Twitter agent functionality where tweets stopped generating after the initial post. There were also discussions about plugin development challenges, including logging visibility problems and API failures. Users inquired about integrating custom plugins with ElizaOS projects, building web terminals for ElizaOS, and deploying Twitter agents without getting banned. The chat demonstrated the community's collaborative approach to solving technical issues with ElizaOS implementation.\n\n## 2. FAQ:\nQ: How to fix \"Database adapter not initialized\" error in ElizaOS? (asked by axs) A: Install Ubuntu via Microsoft Store instead of using WSL, then run commands in Ubuntu CLI (answered by axs)\nQ: How to resolve the \"No TEXT_EMBEDDING error\"? (asked by axs) A: Use \"elizaos start\", add the OpenAI plugin, and create a .env file with your OPENAI_API_KEY (answered by axs)\nQ: Why do tweets stop generating after the first one with Twitter Agent? (asked by Alex) A: Unanswered\nQ: Why can't plugin logs be seen in console? (asked by axs) A: Unanswered\nQ: Why is the API failing in the ElizaOS project? (asked by axs) A: Unanswered\nQ: How to integrate a custom plugin with an ElizaOS project? (asked by 🤠) A: Unanswered\nQ: How to approach building a terminal for ElizaOS? (asked by axs) A: Unanswered\nQ: Where is recommended to deploy a Twitter agent to avoid being banned/flagged? (asked by axs) A: Login with VPN close to server or grab cookies when logging in close to server and add to .env (answered by axs)\n\n## 3. Help Interactions:\nHelper: axs | Helpee: axs | Context: Database adapter initialization error in ElizaOS | Resolution: Switched from WSL to Ubuntu via Microsoft Store and ran commands in Ubuntu CLI\nHelper: axs | Helpee: axs | Context: TEXT_EMBEDDING error after fixing database adapter issue | Resolution: Used \"elizaos start\", added OpenAI plugin, created .env file with OPENAI_API_KEY\nHelper: axs | Helpee: axs | Context: Twitter agent deployment without getting banned | Resolution: Suggested using VPN close to server or grabbing cookies when logging in near server and adding to .env\nHelper: axs | Helpee: axs | Context: Building a terminal for ElizaOS | Resolution: Shared endpoint documentation for sending messages: https://docs.eliza.how/docs/rest/send-message\n\n## 4. Action Items:\nTechnical: Fix Twitter agent issue where tweets stop generating after initial post | Mentioned By: Alex\nTechnical: Resolve plugin logging visibility in console | Mentioned By: axs\nTechnical: Fix API failures in ElizaOS project | Mentioned By: axs\nTechnical: Develop integration method for custom plugins with ElizaOS projects | Mentioned By: 🤠\nTechnical: Create character and pass it to plugin | Mentioned By: 🤠\nTechnical: Build a server-side rendered terminal for ElizaOS | Mentioned By: axs\nTechnical: Implement secure Twitter agent deployment strategy | Mentioned By: axs\nDocumentation: Document proper ElizaOS installation process on different environments | Mentioned By: axs\nDocumentation: Create guide for plugin development and debugging | Mentioned By: axs\nFeature: Improve plugin logging visibility | Mentioned By: axs", "messageCount": 12, "userCount": 3 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Analysis of \"fun\" Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around issues with a token launch for \"doglifeAI\" on the auto.fun platform. Users expressed concerns about the verification process, as the token was verified approximately 5 minutes after launch, allowing potential insider trading. Ben (platform representative) explained their current launch process: partners launch tokens, auto.fun verifies them, announcements are posted on X and Discord. Users suggested improvements including: verifying tokens before launch by obtaining the contract address in advance, reducing verification time from 5 minutes to 1 minute, and potentially having auto.fun handle the launch directly. The community was concerned that the doglifeAI team exploited the system, as evidence showed developer wallets distributing tokens to other addresses for selling. This incident damaged trust in the platform's verification process, with users questioning whether proper vetting occurs before partnerships are established.\n\n## 2. FAQ\nQ: How does the token verification process work? (asked by vas) A: Ben explained that they arrange a timeframe with launch partners, verify tokens after receiving confirmation of the contract address, and post announcements within 30 seconds of verification. (answered by ben)\nQ: Why was the doglifeAI token verified at 400-500k market cap? (asked by vas) A: Ben explained they can only verify after receiving confirmation from the launch partner, and they have a 5-minute cutoff which will be reduced to 1 minute. (answered by ben)\nQ: Why don't you launch tokens for teams instead of letting them do it? (asked by dway) A: Ben stated it's important for partners to deploy their own tokens to decide allocation and update information, but acknowledged the suggestion. (answered by ben)\nQ: Do teams have to verify/dox to become partners? (asked by ryanthelad) A: Unanswered\n\n## 3. Help Interactions\nHelper: ben | Helpee: Multiple users | Context: Users concerned about unfair token launch process | Resolution: Ben acknowledged issues and proposed reducing verification time from 5 to 1 minute and potentially implementing pre-launch contract address verification.\nHelper: shad | Helpee: drkmttr2 | Context: User asked if it was safe to buy Doglife token | Resolution: Shad advised against it, suggesting caution due to suspicious launch patterns.\nHelper: vas | Helpee: ben | Context: Platform vulnerability to exploitation by launch partners | Resolution: Offered to compile detailed feedback in PDF format to improve the platform's security.\n\n## 4. Action Items\nType: Technical | Description: Reduce token verification time from 5 minutes to 1 minute after launch | Mentioned By: ben\nType: Technical | Description: Implement pre-launch contract address verification by having partners share their screen before launching | Mentioned By: ben\nType: Technical | Description: Consider having auto.fun team launch tokens directly for partners to prevent insider trading | Mentioned By: dway\nType: Technical | Description: Fix token-gated chats that are giving error messages to users | Mentioned By: ryanthelad\nType: Technical | Description: Fix website filters that aren't working properly | Mentioned By: Angelon\nType: Documentation | Description: Create clear guidelines for launch partners regarding verification timing and process | Mentioned By: shad\nType: Documentation | Description: Document improved vetting process for launch partners to prevent scams | Mentioned By: mhd", "messageCount": 248, "userCount": 20 }, { "channelId": "1362864274862768450", "channelName": "fun-support", "summary": "# Analysis of fun-support Discord Channel\n\n## 1. Summary\nThe chat segment primarily revolves around issues with the auto.fun platform. Users reported problems with token verification, including fake verification symbols appearing over the weekend. A specific issue was raised about the inability to edit information or connect relevant X accounts after importing a token as a CTO. Users also reported temporary display problems with the site showing outdated token information. There were concerns about trust in verification systems, with a suggestion to use email announcements to autodotfun subscribers alongside X announcements for better verification. The conversation also touched on token supply limitations on auto.fun, with confirmation that tokens cannot exceed 1 billion supply. Additionally, there were reports of scammers in the channel sending fake support messages that disappeared after being clicked.\n\n## 2. FAQ\nQ: For verification, would coordinating X announcements with emails to autodotfun subscribers be better? (asked by MDMnvest) A: Unanswered\nQ: Was it actually verified or a fake verification symbol in the token name? (asked by hxf) A: There were heaps of tokens with fake verification symbols over the weekend (answered by kisa)\nQ: How to edit information or connect X accounts for imported CTO tokens? (asked by nasdaq.ai) A: This issue is in the backlog (answered by Kenk)\nQ: Is it possible for a token to have more than 1 billion supply if made on auto.fun? (asked by hxf) A: No I don't think so (answered by Kenk)\nQ: How will collected money (presale) be put into the coin? (asked by velja) A: Unanswered\nQ: Is something wrong with the site? It's showing tokens from over a week ago. (asked by shad) A: Yes, but it was temporarily fixed before reverting to showing outdated information again (answered by Xyness and shad)\nQ: Where can I get the auto fun program idl? (asked by brixxx) A: This was responded to in TG (answered by Kenk)\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: nasdaq.ai | Context: User reported inability to edit token information or connect X accounts after importing as CTO | Resolution: Kenk confirmed the issue is in the backlog\nHelper: Kenk | Helpee: nasdaq.ai | Context: User reported potential scammers sending messages that disappear after clicking | Resolution: Kenk acknowledged and thanked for flagging\nHelper: Xyness | Helpee: shad | Context: User experiencing site issues showing outdated tokens | Resolution: Partial - they confirmed the issue was happening but it wasn't fully resolved\n\n## 4. Action Items\nTechnical: Fix the ability to edit information and connect X accounts for imported CTO tokens | Description: Users cannot modify token information after importing as CTO | Mentioned By: nasdaq.ai\nTechnical: Address site display issues | Description: Site intermittently shows outdated token information from over a week ago | Mentioned By: shad\nTechnical: Implement better verification system | Description: Current verification can be faked or hacked, consider email verification | Mentioned By: MDMnvest\nTechnical: Improve anti-scam measures | Description: Block scammers sending fake support messages that disappear after clicking | Mentioned By: nasdaq.ai\nDocumentation: Clarify token supply limitations | Description: Document that tokens cannot exceed 1 billion supply on auto.fun | Mentioned By: hxf\nDocumentation: Explain how presale funds are handled | Description: Clarify how collected presale money is integrated into coins | Mentioned By: velja", "messageCount": 30, "userCount": 9 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-05": { "filename": "2025-05-05.md", "content": "# elizaOS Discord - 2025-05-05\n\n## Overall Discussion Highlights\n\n### ElizaOS Technical Issues & Development\n- Users troubleshooted ElizaOS installation errors, with one user resolving database adapter initialization issues by switching from WSL to Ubuntu via Microsoft Store\n- OpenAI plugin configuration issues were resolved by properly setting up API keys in .env files\n- Twitter agent functionality problems were reported where tweets stop generating after initial posts\n- Plugin development challenges included logging visibility problems and API failures\n- Discussions about building web terminals for ElizaOS and integrating custom plugins with projects\n\n### Auto.fun Platform Concerns\n- Significant trust issues emerged regarding the token verification process after the doglifeAI launch\n- The verification process was criticized for allowing a 5-minute window after launch before verification\n- Evidence suggested the doglifeAI team exploited this window for insider trading\n- Platform representative Ben acknowledged issues and proposed reducing verification time to 1 minute\n- Users reported technical issues including fake verification symbols and inability to edit token information\n- Token supply limitations were confirmed (cannot exceed 1 billion on auto.fun)\n\n### Token Requirements & Access\n- Updated token requirements were shared: 5M DEGEN or 100K AI16 for partners (previously 1M for DEGENPARTNER)\n- Brief mention of Comput3 launching on \"auto\" with limited details\n- Some users reported issues with token-gated chats giving error messages\n\n## Key Questions & Answers\n\n### ElizaOS Technical\n- **Q: How to fix \"Database adapter not initialized\" error in ElizaOS?** \n **A:** Install Ubuntu via Microsoft Store instead of using WSL, then run commands in Ubuntu CLI\n\n- **Q: How to resolve the \"No TEXT_EMBEDDING error\"?** \n **A:** Use \"elizaos start\", add the OpenAI plugin, and create a .env file with your OPENAI_API_KEY\n\n- **Q: Where is recommended to deploy a Twitter agent to avoid being banned/flagged?** \n **A:** Login with VPN close to server or grab cookies when logging in close to server and add to .env\n\n### Auto.fun Platform\n- **Q: How does the token verification process work?** \n **A:** Auto.fun arranges a timeframe with launch partners, verifies tokens after receiving confirmation of the contract address, and posts announcements within 30 seconds of verification\n\n- **Q: Why was the doglifeAI token verified at 400-500k market cap?** \n **A:** They can only verify after receiving confirmation from the launch partner, and they have a 5-minute cutoff which will be reduced to 1 minute\n\n- **Q: Why don't you launch tokens for teams instead of letting them do it?** \n **A:** It's important for partners to deploy their own tokens to decide allocation and update information\n\n- **Q: Is it possible for a token to have more than 1 billion supply if made on auto.fun?** \n **A:** No, tokens cannot exceed 1 billion supply on the platform\n\n### General Information\n- **Q: Where can I find more info about Comput3?** \n **A:** Head to #1361442528813121556 or ask in the comput3 community\n\n## Community Help & Collaboration\n\n1. **ElizaOS Installation Troubleshooting** \n User \"axs\" documented their process of resolving database adapter initialization errors by switching from WSL to Ubuntu via Microsoft Store, helping others who might encounter similar issues\n\n2. **OpenAI Plugin Configuration** \n Detailed steps were shared for resolving TEXT_EMBEDDING errors by properly configuring the OpenAI plugin with API keys\n\n3. **Twitter Agent Deployment** \n Tips were shared about using VPNs or grabbing cookies when logging in near the server location to avoid Twitter bans\n\n4. **Auto.fun Platform Improvement** \n User \"vas\" offered to compile detailed feedback in PDF format to help improve the platform's security against exploitation by launch partners\n\n5. **Token Verification Warning** \n User \"shad\" advised another user against buying the Doglife token due to suspicious launch patterns, potentially saving them from a bad investment\n\n## Action Items\n\n### Technical\n- Reduce token verification time from 5 minutes to 1 minute after launch (mentioned by Ben)\n- Implement pre-launch contract address verification by having partners share their screen before launching (mentioned by Ben)\n- Consider having auto.fun team launch tokens directly for partners to prevent insider trading (mentioned by dway)\n- Fix Twitter agent issue where tweets stop generating after initial post (mentioned by Alex)\n- Resolve plugin logging visibility in console (mentioned by axs)\n- Fix API failures in ElizaOS project (mentioned by axs)\n- Develop integration method for custom plugins with ElizaOS projects (mentioned by 🤠)\n- Build a server-side rendered terminal for ElizaOS (mentioned by axs)\n- Implement secure Twitter agent deployment strategy (mentioned by axs)\n- Fix token-gated chats that are giving error messages to users (mentioned by ryanthelad)\n- Fix website filters that aren't working properly (mentioned by Angelon)\n- Fix the ability to edit information and connect X accounts for imported CTO tokens (mentioned by nasdaq.ai)\n- Address site display issues showing outdated token information (mentioned by shad)\n- Implement better verification system to prevent fake verifications (mentioned by MDMnvest)\n- Improve anti-scam measures against fake support messages (mentioned by nasdaq.ai)\n\n### Documentation\n- Update information about token requirements for partners (5M DEGEN or 100K AI16) (mentioned by yikesawjeez)\n- Document proper ElizaOS installation process on different environments (mentioned by axs)\n- Create guide for plugin development and debugging (mentioned by axs)\n- Create clear guidelines for launch partners regarding verification timing and process (mentioned by shad)\n- Document improved vetting process for launch partners to prevent scams (mentioned by mhd)\n- Clarify token supply limitations on auto.fun (mentioned by hxf)\n- Explain how presale funds are handled for tokens (mentioned by velja)\n\n### Feature\n- Consider implementing Collabland for ELI5 token (mentioned by ryanthelad)\n- Improve plugin logging visibility (mentioned by axs)\n- Create character and pass it to plugin (mentioned by 🤠)" }, "ai_news_elizaos_daily_dev_json_2025-05-05": { "filename": "2025-05-05.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-05", "date": 1746403200, "stats": { "totalMessages": 41, "totalUsers": 13 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Analysis of 💬｜general Discord Channel\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. Users are asking about agent behavior, API usage, and testing opportunities. One user is looking for testers for a ChatGPT-integrated app for canned responses. Another user is trying to understand how to call an API from Postman rather than from a client after successfully running a Vite application locally. There's a brief mention of a Twitter agent using v2 and a question about why a sendmessage API isn't working. The technical content is sparse, with no detailed problem-solving or implementation discussions taking place in this segment.\n\n## 2. FAQ\nQ: Am I getting gatekept by my agent? Is that 24hrs window a real thing? If I leave the agent running would he really send me something? (asked by axs) A: Unanswered\nQ: If I want to call the api on postman not on client? (asked by lantianlaoli) A: Unanswered\nQ: How can I have a Twitter agent using v2? (asked by yoyoha) A: Unanswered (though 0xbbjoker shared a link that may contain information)\nQ: Why sendmessage API doesn't work? (asked by OpsDev) A: Unanswered\n\n## 3. Help Interactions\nHelper: 0xbbjoker | Helpee: yoyoha | Context: User needed information about Twitter agent using v2 | Resolution: Shared a Discord channel link that presumably contains relevant information, acknowledged by yoyoha with thanks\n\n## 4. Action Items\nTechnical: Investigate why sendmessage API doesn't work | Description: User reported an issue with the sendmessage API | Mentioned By: OpsDev\nFeature: Testing app for creating canned responses with ChatGPT integration | Description: Looking for testers for an application that helps with rephrasing and formatting text | Mentioned By: Scott Milner", "messageCount": 12, "userCount": 8 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat segment covers technical issues related to agent development, specifically focusing on troubleshooting a Telegram agent setup error, plugin architecture compatibility problems between different runtimes (Bun vs Node), and Twitter agent deployment considerations to avoid account flagging. The discussions are primarily centered around error resolution and best practices for deployment. Ruby provides detailed technical guidance on resolving the \"No world found for user during onboarding\" error by suggesting database migration and environment variable checks. The conversation also touches on the challenges of using datacenter IPs for Twitter agents and recommends residential proxies as an alternative solution. There's an ongoing effort to standardize the plugin system to ensure consistent functionality across different runtime environments.\n\n## 2. FAQ\nQ: While building a telegram agent I am running into the error \"No world found for user during onboarding\" what does this mean? (asked by StarCat) A: That error usually means the world creation step failed during setup. Check that you have WORLD_ID set in your .env and that your database migrations ran successfully. Try running 'elizaos db:migrate' first, then attempt the telegram agent setup again. (answered by Ruby)\nQ: What is the end goal for the plugin architecture? Now, depending on which elizaos (in .bun or in the nvm/node path) the plugins fail to mount. (asked by kandizzy) A: The goal is to have a unified plugin system where plugins work consistently regardless of runtime. Right now there's a known issue with path resolution between bun/node environments. We're working on standardizing how plugins are discovered and mounted. For now, I'd recommend sticking to one runtime (preferably node) until we get this sorted out. (answered by Ruby)\nQ: Where is recommended to deploy a twitter agent to not get banned/flagged? I imagine that if it's some datacenter IP, twitter blocks them, right? (asked by morlok) A: Yeah, datacenter IPs are a red flag for twitter. Your best bet is using residential proxies or a VPN service that rotates residential IPs. I've had good luck with Bright Data's residential network, but there are cheaper options if you're just testing. (answered by Ruby)\n\n## 3. Help Interactions\nHelper: Ruby | Helpee: StarCat | Context: Telegram agent setup error \"No world found for user during onboarding\" | Resolution: Suggested checking WORLD_ID in .env and running database migrations with 'elizaos db:migrate'\nHelper: Ruby | Helpee: kandizzy | Context: Plugin architecture inconsistency between Bun and Node runtimes | Resolution: Explained current limitations and recommended sticking to one runtime (preferably Node) until standardization is complete\nHelper: Ruby | Helpee: morlok | Context: Concerns about Twitter blocking agents deployed on datacenter IPs | Resolution: Recommended using residential proxies or VPN services with residential IP rotation, specifically mentioning Bright Data\n\n## 4. Action Items\nTechnical: Standardize plugin discovery and mounting across different runtimes | Description: Fix path resolution issues between Bun/Node environments | Mentioned By: Ruby\nTechnical: Implement proper database migration checks during agent setup | Description: Prevent \"No world found\" errors by ensuring migrations complete successfully | Mentioned By: Ruby\nTechnical: Develop proxy configuration guide for Twitter agents | Description: Document how to set up residential proxies to avoid account flagging | Mentioned By: Ruby", "messageCount": 11, "userCount": 5 }, { "channelId": "1323745969115893780", "channelName": "📥｜pull-requests", "summary": "# Analysis of Discord Chat in \"📥｜pull-requests\" Channel\n\n## 1. Summary\nThe chat segment revolves around a user named \"lost\" who is experiencing issues with a pull request (PR) for an Indonesian translation to the elizaOS/eliza repository. The PR (#4453) was being blocked due to a repository workflow rule that requires merges to the main branch to come only from the develop branch, not directly from feature branches. Ruby identified that lost's PR was coming from a \"patch-3\" branch instead of the required develop branch. Ruby provided a step-by-step solution to resolve this issue by creating a new branch from develop, transferring the translation changes to this new branch, and then targeting the develop branch with the PR. The solution involved specific git commands for checking out branches, copying files, and creating a proper PR workflow. Ruby also offered an alternative approach using GitHub's web UI for users less comfortable with git commands.\n\n## 2. FAQ\nQ: Can you help me with my Indonesian translation PR that's getting blocked? (asked by lost) A: Yes, the issue is that merges to main branch are only allowed from the develop branch, not from patch-3. (answered by Ruby)\nQ: How to clear no. 4? (asked by lost) A: To copy your changes: locate your Indonesian readme file from patch-3 branch, copy all text content, paste it into the new file in your feature branch. (answered by Ruby)\n\n## 3. Help Interactions\nHelper: Ruby | Helpee: lost | Context: PR being blocked due to incorrect branch targeting | Resolution: Provided step-by-step git commands to create a new branch from develop and transfer changes\nHelper: Ruby | Helpee: lost | Context: User needed clarification on how to copy files between branches | Resolution: Offered both git command sequence and GitHub web UI approach for transferring files\n\n## 4. Action Items\nTechnical: Create a new branch from develop instead of targeting main directly | Description: Follow proper branch workflow for contributions | Mentioned By: Ruby\nTechnical: Transfer Indonesian translation from patch-3 to a new feature branch | Description: Copy README_IND.md to the proper branch | Mentioned By: Ruby\nTechnical: Update PR to target the develop branch instead of main | Description: Change PR target branch to comply with repository rules | Mentioned By: Ruby", "messageCount": 18, "userCount": 3 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-05": { "filename": "2025-05-05.md", "content": "# elizaOS Development Discord - 2025-05-05\n\n## Overall Discussion Highlights\n\n### Agent Development & Troubleshooting\n- Users reported issues with Telegram agent setup, specifically a \"No world found for user during onboarding\" error\n- Discussion about Twitter agent deployment best practices to avoid account flagging\n- Questions about agent behavior, including a 24-hour window for agent responses\n- Concerns about API functionality, particularly the sendmessage API not working\n\n### Technical Infrastructure\n- Plugin architecture compatibility issues between Bun and Node runtimes were discussed\n- Ruby explained the goal is to standardize the plugin system for consistent functionality across environments\n- A user successfully ran a Vite application locally but needed help calling an API from Postman\n\n### Community Projects\n- Scott Milner is looking for testers for a ChatGPT-integrated app for creating canned responses\n- A user named \"lost\" submitted a PR for Indonesian translation to the elizaOS/eliza repository\n\n## Key Questions & Answers\n\n**Q: While building a telegram agent I am running into the error \"No world found for user during onboarding\" what does this mean?** \nA: \"That error usually means the world creation step failed during setup. Check that you have WORLD_ID set in your .env and that your database migrations ran successfully. Try running 'elizaos db:migrate' first, then attempt the telegram agent setup again.\" (answered by Ruby)\n\n**Q: What is the end goal for the plugin architecture? Now, depending on which elizaos (in .bun or in the nvm/node path) the plugins fail to mount.** \nA: \"The goal is to have a unified plugin system where plugins work consistently regardless of runtime. Right now there's a known issue with path resolution between bun/node environments. We're working on standardizing how plugins are discovered and mounted. For now, I'd recommend sticking to one runtime (preferably node) until we get this sorted out.\" (answered by Ruby)\n\n**Q: Where is recommended to deploy a twitter agent to not get banned/flagged? I imagine that if it's some datacenter IP, twitter blocks them, right?** \nA: \"Yeah, datacenter IPs are a red flag for twitter. Your best bet is using residential proxies or a VPN service that rotates residential IPs. I've had good luck with Bright Data's residential network, but there are cheaper options if you're just testing.\" (answered by Ruby)\n\n**Q: Can you help me with my Indonesian translation PR that's getting blocked?** \nA: \"Yes, the issue is that merges to main branch are only allowed from the develop branch, not from patch-3.\" (answered by Ruby)\n\n## Community Help & Collaboration\n\n### Telegram Agent Troubleshooting\nRuby provided detailed guidance to StarCat on resolving the \"No world found for user during onboarding\" error by suggesting database migration checks and environment variable verification.\n\n### Plugin Architecture Support\nRuby helped kandizzy understand the current limitations of the plugin system across different runtimes and recommended sticking to Node until standardization is complete.\n\n### Twitter Agent Deployment Advice\nRuby advised morlok on avoiding Twitter account flagging by using residential proxies instead of datacenter IPs, specifically recommending Bright Data's residential network.\n\n### Pull Request Workflow Assistance\nRuby guided \"lost\" through the proper GitHub workflow for submitting a translation PR:\n1. Creating a new branch from develop\n2. Transferring the Indonesian translation files\n3. Targeting the develop branch with the PR\n4. Offered both git command sequence and GitHub web UI approaches\n\n### Twitter Agent Resources\n0xbbjoker shared a Discord channel link with yoyoha regarding Twitter agent v2 implementation information.\n\n## Action Items\n\n### Technical\n- **Standardize plugin discovery and mounting across different runtimes** - Fix path resolution issues between Bun/Node environments (Mentioned by Ruby)\n- **Implement proper database migration checks during agent setup** - Prevent \"No world found\" errors by ensuring migrations complete successfully (Mentioned by Ruby)\n- **Investigate why sendmessage API doesn't work** - User reported an issue with the API (Mentioned by OpsDev)\n- **Create a new branch from develop instead of targeting main directly** - Follow proper branch workflow for contributions (Mentioned by Ruby)\n- **Transfer Indonesian translation from patch-3 to a new feature branch** - Copy README_IND.md to the proper branch (Mentioned by Ruby)\n- **Update PR to target the develop branch instead of main** - Change PR target branch to comply with repository rules (Mentioned by Ruby)\n\n### Documentation\n- **Develop proxy configuration guide for Twitter agents** - Document how to set up residential proxies to avoid account flagging (Mentioned by Ruby)\n\n### Feature\n- **Testing app for creating canned responses with ChatGPT integration** - Looking for testers for an application that helps with rephrasing and formatting text (Mentioned by Scott Milner)" }, "ai_news_hyperfy_daily_json_2025-05-05": { "filename": "2025-05-05.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-05", "date": 1746403200, "stats": { "totalMessages": 129, "totalUsers": 19 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary\nThe discussion primarily focused on technical aspects of 3D rendering and development in Hyperfy. Key topics included:\n\nEmission and lighting techniques were extensively discussed, with users sharing workarounds for color emission issues by using texture atlases and proper material setup. Vox detailed an innovative lighting technique using transparent stencil meshes with cutouts above scene lights to create focused lighting effects without performance overhead.\n\nSkybox implementation was addressed, with Ashxn explaining that future plans involve starting worlds with a removable sky app rather than a default skysphere. Vox discussed combining multiple functionalities into a single app/hyp file for more efficient world building.\n\nPerformance optimization techniques were shared, particularly around texture reuse and draw call reduction. Vox emphasized using Blender for world building to reuse textures across different meshes, reducing bandwidth usage and improving performance.\n\nPeezy revealed development of a UI for managing hypkg mods with a system that loads components from separate folders to prevent conflicts between mods, distinguishing between standard mods and \"overhauls\" that modify core functionality.\n\n## 2. FAQ\nQ: Is there a way to change the color of the emission? (asked by Gert-Jan Akerboom) A: Add a texture in the emission slot and use texture atlas; in Blender use the same color for diffuse and emissive to maintain color consistency in bloom effects. (answered by ᲼~/^b0gie-(.*)$/ and Ashxn)\nQ: How can I get rid of any default skybox image that is built in core? (asked by vox) A: The plan is to have no default skysphere and worlds start with a sky app that you can delete, but still recommended to use solarpanel or other sky app since the skysphere follows the player. (answered by Ashxn)\nQ: Do you guys get random disconnects in your servers? (with the voice chat staying live) (asked by vincentskele) A: Yes quite often. (answered by vox)\n\n## 3. Help Interactions\nHelper: ᲼~/^b0gie-(.*)$/ | Helpee: Gert-Jan Akerboom | Context: Changing emission color instead of getting white glow | Resolution: Suggested using texture atlas in the emission slot\nHelper: Ashxn | Helpee: Gert-Jan Akerboom | Context: Emission color control | Resolution: Explained using same color for diffuse and emissive to maintain color consistency\nHelper: vox | Helpee: ᲼~/^b0gie-(.*)$/ | Context: Creating lighting effects in scenes | Resolution: Shared technique using transparent mesh with cutouts above scene lights to create focused lighting without additional light sources\nHelper: vox | Helpee: Shiffty | Context: Baking skills in Blender | Resolution: Recommended simplebake addon, zenUV and UVpackmaster for efficient texture baking workflow\nHelper: Ashxn | Helpee: vox | Context: Creating a single app with multiple functionalities | Resolution: Confirmed possibility of creating one big app with combined scripts and UI\n\n## 4. Action Items\nTechnical: Implement skinnedmesh.getBone(name) functionality | Mentioned By: Ashxn\nTechnical: Develop UI for management of hypkg mods with separate folder loading to prevent conflicts | Mentioned By: peezy\nTechnical: Create system to distinguish between standard mods and \"overhauls\" that modify core functionality | Mentioned By: peezy\nFeature: Remove default skysphere and replace with deletable sky app | Mentioned By: Ashxn\nFeature: Support for creating combined apps that house multiple functionalities (skybox, atmosphere, etc.) | Mentioned By: vox\nDocumentation: Document stencil mesh technique for creating focused lighting effects | Mentioned By: vox\nDocumentation: Document texture reuse and draw call optimization techniques | Mentioned By: vox", "messageCount": 85, "userCount": 12 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around community interactions rather than technical discussions. There was a brief mention of upcoming events showcasing Hyperfy for onboarding users to Web3 and metaverse experiences. A community member (Agent12) expressed interest in creating a metaverse space for Pizza DAO but mentioned challenges regarding server hosting costs and ease of use for non-developers. There was a short technical discussion about a potential \"teleport\" feature for builders to navigate to apps within the platform, with concerns raised about collision detection and possible solutions like disabling player colliders or implementing a \"god mode.\" A brief mention of a \"pectra upgrade\" was made without further details.\n\n## 2. FAQ\nQ: Would it be cool to let builders 'teleport' to an app or is that overkill? (asked by ᲼~/^b0gie-(.*)$/) A: It would be nice but there are concerns about players teleporting into colliders (answered by Ashxn)\nQ: What if player colliders were off and you were floating then you could teleport to it? (asked by ᲼~/^b0gie-(.*)$/) A: Unanswered\n\n## 3. Help Interactions\nHelper: DevStarlight | Numinia | Helpee: ᲼~/^b0gie-(.*)$/ | Context: Discussion about teleport feature implementation | Resolution: Suggested adding a config option to show/hide the teleport feature, similar to how app sound is handled\n\n## 4. Action Items\nType: Feature | Description: Implement a teleport feature for builders with configuration options | Mentioned By: ᲼~/^b0gie-(.*)$/\nType: Feature | Description: Consider a \"god mode\" for builders to avoid collision issues | Mentioned By: ᲼~/^b0gie-(.*)$/\nType: Technical | Description: Investigate \"pectra upgrade\" mentioned in chat | Mentioned By: ᲼~/^b0gie-(.*)$/\nType: Feature | Description: Develop more non-dev friendly ways to create servers or cheaper hosting options | Mentioned By: Agent12", "messageCount": 24, "userCount": 12 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "# Discord Chat Analysis: 🧊│3d-design\n\n## 1. Summary:\nThe chat primarily focused on technical discussions about Level of Detail (LOD) implementations in 3D design. Ashxn introduced a new scale-aware LOD option that addresses the issue where fixed distance thresholds (e.g., 5 meters) for LOD transitions don't work well when objects are scaled. The new feature automatically adjusts LOD transition distances proportionally when objects are scaled, maintaining appropriate visual quality. There was also a brief discussion about vertex painting, with b0gie mentioning its applications for \"filler objects\" in worlds, noting that higher vertex counts enable better color blending, and mentioning UCUPaint for emissive painting. A question about LOD implementation and drawcalls was also addressed, confirming that using multiple LODs does increase drawcalls but typically results in better overall performance.\n\n## 2. FAQ:\nQ: If I instance many different items across the scene, each with 3 LODs that I see at different stages simultaneously, do I get 3 times the drawcalls compared to using just 1 LOD? (asked by vox) A: Yes, but in most cases you're still far better off [performance-wise]. (answered by Ashxn)\n\n## 3. Help Interactions:\nHelper: Ashxn | Helpee: vox | Context: Question about whether using multiple LODs increases drawcalls | Resolution: Confirmed it does increase drawcalls but explained it's still better for performance overall\nHelper: ᲼~/^b0gie-(.*)$/ | Helpee: vox | Context: vox expressing need to learn vertex painting | Resolution: b0gie offered to help and shared information about vertex painting applications and drawbacks\n\n## 4. Action Items:\nTechnical: Implement scale-aware LOD option for better visual quality with scaled objects | Description: Adjust LOD transition distances proportionally when objects are scaled | Mentioned By: Ashxn\nTechnical: Explore UCUPaint for emissive vertex painting | Description: Test UCUPaint's capabilities for adding emissive effects through vertex painting | Mentioned By: ᲼~/^b0gie-(.*)$/\nFeature: Scale-aware LOD system | Description: System that automatically adjusts LOD transition distances based on object scale | Mentioned By: Ashxn", "messageCount": 20, "userCount": 4 } ] } }, "ai_news_hyperfy_daily_md_2025-05-05": { "filename": "2025-05-05.md", "content": "# Hyperfy Discord - 2025-05-05\n\n## Overall Discussion Highlights\n\n### 3D Rendering & Lighting Techniques\n- **Emission and Lighting:** Users discussed workarounds for color emission issues using texture atlases and proper material setup. Vox shared an innovative lighting technique using transparent stencil meshes with cutouts above scene lights to create focused lighting effects without performance overhead.\n- **Vertex Painting:** B0gie discussed vertex painting applications for \"filler objects\" in worlds, noting that higher vertex counts enable better color blending, and mentioned UCUPaint for emissive painting.\n- **Scale-aware LOD:** Ashxn introduced a new scale-aware LOD option that automatically adjusts LOD transition distances proportionally when objects are scaled, maintaining appropriate visual quality regardless of object size.\n\n### World Building & Performance Optimization\n- **Skybox Implementation:** Future plans involve starting worlds with a removable sky app rather than a default skysphere.\n- **Combined Functionality:** Vox and Ashxn discussed combining multiple functionalities (skybox, atmosphere, etc.) into a single app/hyp file for more efficient world building.\n- **Performance Techniques:** Texture reuse and draw call reduction were emphasized. Vox highlighted using Blender for world building to reuse textures across different meshes, reducing bandwidth usage and improving performance.\n\n### Development & Modding\n- **Mod Management:** Peezy revealed development of a UI for managing hypkg mods with a system that loads components from separate folders to prevent conflicts between mods.\n- **Mod Categories:** The system will distinguish between standard mods and \"overhauls\" that modify core functionality.\n- **Teleport Feature:** Discussion about implementing a \"teleport\" feature for builders to navigate to apps within the platform, with concerns about collision detection and possible solutions like disabling player colliders or implementing a \"god mode.\"\n\n### Community & Events\n- Brief mention of upcoming events showcasing Hyperfy for onboarding users to Web3 and metaverse experiences.\n- A community member (Agent12) expressed interest in creating a metaverse space for Pizza DAO but mentioned challenges regarding server hosting costs and ease of use for non-developers.\n\n## Key Questions & Answers\n\n**Q: Is there a way to change the color of the emission?** (asked by Gert-Jan Akerboom) \nA: Add a texture in the emission slot and use texture atlas; in Blender use the same color for diffuse and emissive to maintain color consistency in bloom effects. (answered by B0gie and Ashxn)\n\n**Q: How can I get rid of any default skybox image that is built in core?** (asked by Vox) \nA: The plan is to have no default skysphere and worlds start with a sky app that you can delete, but still recommended to use solarpanel or other sky app since the skysphere follows the player. (answered by Ashxn)\n\n**Q: If I instance many different items across the scene, each with 3 LODs that I see at different stages simultaneously, do I get 3 times the drawcalls compared to using just 1 LOD?** (asked by Vox) \nA: Yes, but in most cases you're still far better off performance-wise. (answered by Ashxn)\n\n**Q: Would it be cool to let builders 'teleport' to an app or is that overkill?** (asked by B0gie) \nA: It would be nice but there are concerns about players teleporting into colliders. DevStarlight suggested adding a config option to show/hide the teleport feature, similar to how app sound is handled. (answered by Ashxn and DevStarlight)\n\n**Q: Do you guys get random disconnects in your servers? (with the voice chat staying live)** (asked by Vincentskele) \nA: Yes quite often. (answered by Vox)\n\n## Community Help & Collaboration\n\n1. **Emission Color Control**\n - B0gie helped Gert-Jan Akerboom with changing emission color by suggesting using texture atlas in the emission slot\n - Ashxn further explained using the same color for diffuse and emissive to maintain color consistency\n\n2. **Lighting Effects Creation**\n - Vox shared with B0gie a technique using transparent mesh with cutouts above scene lights to create focused lighting without additional light sources\n\n3. **Blender Baking Workflow**\n - Vox recommended simplebake addon, zenUV and UVpackmaster to Shiffty for efficient texture baking workflow\n\n4. **LOD Implementation**\n - Ashxn helped Vox understand the drawcall implications of using multiple LODs, confirming it increases drawcalls but improves overall performance\n\n5. **Vertex Painting Techniques**\n - B0gie offered to help Vox learn vertex painting and shared information about applications and drawbacks\n\n## Action Items\n\n### Technical\n- Implement skinnedmesh.getBone(name) functionality (Mentioned by Ashxn)\n- Develop UI for management of hypkg mods with separate folder loading to prevent conflicts (Mentioned by Peezy)\n- Create system to distinguish between standard mods and \"overhauls\" that modify core functionality (Mentioned by Peezy)\n- Implement scale-aware LOD option for better visual quality with scaled objects (Mentioned by Ashxn)\n- Explore UCUPaint for emissive vertex painting (Mentioned by B0gie)\n- Investigate \"pectra upgrade\" mentioned in chat (Mentioned by B0gie)\n\n### Feature\n- Remove default skysphere and replace with deletable sky app (Mentioned by Ashxn)\n- Support for creating combined apps that house multiple functionalities (skybox, atmosphere, etc.) (Mentioned by Vox)\n- Implement a teleport feature for builders with configuration options (Mentioned by B0gie)\n- Consider a \"god mode\" for builders to avoid collision issues (Mentioned by B0gie)\n- Develop more non-dev friendly ways to create servers or cheaper hosting options (Mentioned by Agent12)\n\n### Documentation\n- Document stencil mesh technique for creating focused lighting effects (Mentioned by Vox)\n- Document texture reuse and draw call optimization techniques (Mentioned by Vox)" }, "github_summaries_daily_2025-05-06": { "filename": "2025-05-06.md", "content": "# ElizaOS Daily Update (May 6, 2025)\n\n## OVERVIEW \nToday's development efforts focused on enhancing the ElizaOS framework through critical bug fixes and documentation updates. Notable improvements include resolving issues with the Discord service and refining the client interface. Additionally, broken documentation links were updated to ensure users have access to the latest resources. Overall, the team made significant strides in improving system stability and user experience.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Bug Fixes\n- Resolved timeout issues during Discord agent unregistration, ensuring smoother operation of the service ([#4450](https://github.com/elizaos/eliza/pull/4450)).\n- Fixed double scrollbars in the task list and improved scrolling behavior on the main page for a cleaner interface ([#4465](https://github.com/elizaos/eliza/pull/4465)).\n- Corrected detection issues for `bunx` and `npx` to enhance command-line functionality ([#4463](https://github.com/elizaos/eliza/pull/4463)).\n\n### Documentation Enhancements\n- Updated broken links in Eliza documentation, replacing outdated URLs with current ones to improve accessibility ([#4460](https://github.com/elizaos/eliza/pull/4460)).\n\n## CLOSED ISSUES\n\n### User Experience Improvements\n- Closed issues related to user interactions, including blocking unwanted accounts and enhancing CLI tool instructions for better usability ([#4117](https://github.com/elizaos/eliza/issues/4117), [#4113](https://github.com/elizaos/eliza/issues/4113)).\n \n### Bug Resolutions\n- Addressed a syntax error related to module exports in the core library, ensuring proper functionality for developers ([#4046](https://github.com/elizaos/eliza/issues/4046)).\n\n## NEW ISSUES\n\n### Feature Implementation Gaps\n- Identified that `settings.discord.autoPost` is not yet implemented in Eliza v2, highlighting a gap in the current feature set that needs to be addressed ([#4461](https://github.com/elizaos/eliza/issues/4461))." }, "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