{ "date_generated_for": "2025-05-18", "ai_news_elizaos_discord_md_2025-05-17": { "filename": "2025-05-17.md", "content": "# elizaOS Discord - 2025-05-17\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Development & Release\n- ElizaOS v2 (also referred to as 1.0.0) is expected to launch \"next week\" according to xell0x\n- The community is debating whether to prioritize shipping v2 quickly or taking more time for proper documentation\n- Described as \"massive\" with \"industry warping narrative\" potential\n- Maintaining v1 compatibility for existing forks is being considered while developing v2\n\n### ELI5 Token & Integration\n- ELI5 will serve as the community manager AI agent for Eliza v2 terminal\n- Currently valued at ~400k market cap, which xell0x suggests is significantly undervalued\n- Some whale selling activity noted, but also accumulation by top holders\n- Users speculate on potential value increase once Eliza v2 launches\n\n### Technical Issues & Development\n- Nash mentioned building a custom message processor and extending the tee plugin on Solana for a decentralized quant investment platform\n- techcomthanh encountered API configuration issues (OpenRouter compatibility issues while OpenAI API worked)\n- Problems with agents tweeting in loops and relationship creation between users were reported\n- Jin is developing an all-in-one news site with features like facts extraction, multi-repo aggregation, agent RAG, and Discord webhooks integration\n- Google is deprecating Gemini 2.5 Pro Experimental in favor of the paid Preview endpoint\n\n### Community & Ecosystem\n- Jin demonstrated and tested a voting bot functionality within the discussion channel\n- A representative from Nonbank (Professor) offered listing services\n- Community members expressed caution about exchange listings\n- Discussion about adoption strategies, with suggestions to highlight successful tokens from the platform (like eli5 and eddy) to drive more users to auto.fun\n\n## Key Questions & Answers\n\n**Q: When will ElizaOS v2 be released?** \nA: Expected next week (answered by xell0x)\n\n**Q: When will the COM/AI16Z Pool be released?** \nA: Uncertain, but Osint will inquire about it (answered by Osint)\n\n**Q: What information is needed to list a token on Nonbank?** \nA: Token ticker, contract address, project banner, brief description and socials (answered by Professor)\n\n**Q: How to configure a character in ElizaOS?** \nA: Place character config in root folder and use \"elizaos start —char \"./character.json\", then edit plugins via ElizaOS agent CLI (answered by starlord)\n\n**Q: Why aren't exchange listings typically discussed publicly?** \nA: Due to legal issues and scam risks; mentioned existing pairings on raydium and daos.fun (answered by Osint)\n\n## Community Help & Collaboration\n\n1. **Voting Bot Testing**\n - Helper: xell0x\n - Helpee: jin\n - Context: Testing a new voting bot functionality\n - Resolution: Confirmed the embed, voting functionality, and results button were all working correctly\n\n2. **Character Configuration Workaround**\n - Helper: starlord\n - Helpee: (implied users with character config issues)\n - Context: Difficulty finding documentation for character configuration\n - Resolution: Shared workaround to place character config in root folder and use specific CLI command\n\n3. **API Compatibility Clarification**\n - Helper: techcomthanh\n - Helpee: (implied other users)\n - Context: API compatibility issues\n - Resolution: Discovered that default agent works with OpenRouter but some features only work with real OpenAI key\n\n4. **Token Investment Perspective**\n - Helper: xell0x\n - Helpee: Crispy\n - Context: Discussion about ELI5 token value and timing of entry\n - Resolution: xell0x provided perspective on why current accumulation before v2 launch could be advantageous despite short-term price decline\n\n## Action Items\n\n### Technical\n- Ship ElizaOS v2 as the highest priority (mentioned by xell0x)\n- Consider maintaining ElizaOS v1 for existing forks while developing v2 (mentioned by Osint)\n- Fix issue with agents tweeting in loops (mentioned by techcomthanh)\n- Address warning \"User has no name or username, skipping\" in relationship creation (mentioned by techcomthanh)\n- Implement multi-repo aggregation for the news platform (mentioned by jin)\n- Develop agent RAG for the news platform (mentioned by jin)\n- Integrate Discord webhooks (mentioned by jin)\n- Continue testing governance tooling (mentioned by jin)\n\n### Documentation\n- Produce user guides/documentation after shipping v2 rather than delaying release (mentioned by xell0x)\n- Update docs regarding character configuration and CLI commands (mentioned by starlord)\n- Clarify API compatibility between OpenRouter and OpenAI (mentioned by techcomthanh)\n- Update documentation about plugin.ts and plugin development (mentioned by techcomthanh)\n- Document the deprecation of TWITTER_TARGET_USERS env variable (mentioned by techcomthanh)\n- Create comprehensive news site to complement regular updates (mentioned by jin)\n\n### Feature\n- Spotlight top auto.fun-born CTOs (like eli5 and eddy) to drive adoption (mentioned by xell0x)\n- ELI5 integration into Eliza v2 terminal - users will be able to directly interact with the ELI5 agent when opening the new Eliza 1.0.0 terminal (mentioned by xell0x)\n- Implement image generation capabilities or document the process (mentioned by tragicboyjay)" }, "ai_news_elizaos_discord_md_2025-05-16": { "filename": "2025-05-16.md", "content": "# elizaOS Discord - 2025-05-16\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Release\n- Shaw teased ElizaOS v2 about a week ago with a May shipping timeline, making it \"quite imminent\"\n- This was later confirmed by a tweet from Shaw\n- Some users reported that v2 is more difficult to set up compared to earlier versions\n- Significant technical discussions around proper agent configuration, particularly regarding plugin integration\n\n### Ecosystem Growth\n- ElizaOS v1 has become a framework used by at least 10 AI agent launchpads across different blockchains (Base, Near, Solana, Hyperliquid, Sui)\n- This growth pattern is similar to how Uniswap v2 became a standard that was widely forked\n- Several DeFAI (Decentralized Finance AI) projects are emerging in the ElizaOS ecosystem, including ProAgentAI and Kudo Network\n\n### Technical Implementations\n- Users discussed implementation issues with plugins (Discord, Telegram), authentication, and agent configuration\n- Jin shared an AI-generated daily briefing system they've developed, which aggregates information from GitHub\n- The system provides context for agents to stay in sync with users and includes AI news shows highlighting development updates\n- Discussions about building transactions for the auto.fun platform revealed developers can build transactions directly without necessarily needing the program IDL\n\n### Token Discussions\n- Users discussed potential market valuations for tokens named \"Eli\" and \"Eddy,\" with estimates ranging from 50-500 million depending on market conditions\n- Questions about the process for launching verified tokens for AI developers\n- Mentions of a potential collaboration between ai16z and COM (comput3), with discussions of a COM/SOL pool on Raydium\n\n## Key Questions & Answers\n\n**Q: Is ElizaOS v2 close to release?** (asked by abhi_ironman) \nA: Yes, Shaw teased it a week ago with a May shipping timeline, and later confirmed it's coming soon (answered by xell0x)\n\n**Q: What are the limitations of ElizaOS v1?** (asked by Osint) \nA: It's been basic LLM stuff, too limiting for widespread agent adoption (answered by xell0x)\n\n**Q: Is there any DeFAI in Eliza Eco?** (asked by Dive or Die) \nA: Yes, there are lots of DeFAI focused builders, including ProAgentAI and Kudo Network (answered by Kenk)\n\n**Q: How can I add telegram plugin to eliza os?** (asked by spec) \nA: \"I used this in setting up: https://github.com/elizaos-plugins/client-telegram\" (answered by gelgit.eth)\n\n**Q: Am I right I can launch agent in auto fun?** (asked by ɱɑყɑɱɑεʂƚɾ) \nA: It's not a low-code agent creation tool yet, but if you have an agent you can launch a token with auto.fun and are able to deploy it to the UI using the agent subsection (answered by Kenk)\n\n**Q: I'd like to know if you have an api/sdk available** (asked by youuoycollection) \nA: Everything is onchain friend (answered by vas)\n\n**Q: Is it working like this? I can built the tx and just send it? I don't need the program idl to do it?** (asked by youuoycollection) \nA: You don't need the program idl but the idl is also public on GitHub (answered by vas)\n\n## Community Help & Collaboration\n\n### Plugin Integration Support\n- **Helper:** gelgit.eth | **Helpee:** spec\n- **Context:** Adding Telegram plugin to ElizaOS\n- **Resolution:** Shared GitHub repository link for client-telegram\n\n### Agent Setup Guidance\n- **Helper:** scooter8992 | **Helpee:** Community\n- **Context:** Starting an org with Eddy agent\n- **Resolution:** Provided detailed steps including git checkout, build commands, and environment setup\n- **Additional Help:** Pointed out crucial \"bun run build\" step needed before starting\n\n### Platform Capabilities Clarification\n- **Helper:** Kenk | **Helpee:** ɱɑყɑɱɑεʂƚɾ\n- **Context:** User wanted to create an agent on auto.fun but misunderstood the platform's capabilities\n- **Resolution:** Explained that auto.fun isn't yet a low-code agent creation tool but directed user to eliza.how for quickstart guide\n\n### Transaction Building Guidance\n- **Helper:** vas | **Helpee:** youuoycollection\n- **Context:** User needed to understand how to build an application that can launch on the website\n- **Resolution:** Explained that transactions can be built and sent directly to the program with metadata, and that the IDL is available on GitHub\n\n### Repository Creation Help\n- **Helper:** Osint | **Helpee:** MonteCrypto\n- **Context:** How developers can create their own repo\n- **Resolution:** Explained the process similar to .is_a_dev domain (clone, add domain, push back)\n\n## Action Items\n\n### Technical\n- **Fix username caching issue in direct client** - Username is cached and not updating properly when sending different usernames (Mentioned by scooter8992)\n- **Resolve plugin integration issues** - Custom Discord plugin not properly integrating with agent configuration (Mentioned by scooter8992)\n- **Fix agent registration problem** - Agent successfully launches but doesn't register in interface (Mentioned by scooter8992)\n- **Implement token usage limitation** - Configure response length and max tokens properly (Mentioned by scooter8992)\n- **Create a list of AI agent launchpads using ElizaOS** - Document platforms that have forked or built on ElizaOS framework (Mentioned by Osint)\n- **Develop step-by-step guide for developers to create their own repo** - Similar to .is_a_dev domain process (Mentioned by MonteCrypto)\n\n### Documentation\n- **Update \"Eliza World\" documentation** - Create comprehensive list of projects in the ecosystem (Mentioned by Osint)\n- **Create tutorial for manual installation of custom characters** - Current documentation doesn't apply to v2, causing confusion (Mentioned by scooter8992)\n- **Update documentation on plugin extension** - Clarify whether to extend Plugin or StarterPlugin (Mentioned by scooter8992)\n- **Provide clearer documentation on agent creation process** - Users are confused about how to create agents with existing tokens (Mentioned by ɱɑყɑɱɑεʂƚɾ)\n- **Create documentation about the verified token launch process** - Process for launching verified tokens is not clearly documented (Mentioned by frank_grimes_sr)\n\n### Feature\n- **Improve jin's AI news system to dig deeper into topics** - Current system provides good overview but could explore topics in more depth (Mentioned by jin)\n- **Expand jin's framework to include crypto AI ecosystem information** - Add data about new AI projects, their focus areas and technologies (Mentioned by Osint)\n- **Implement IP traffic control for deployed instances** - Need mechanism to control inbound IP traffic on Railway deployments (Mentioned by scooter8992)\n- **Create a more accessible low-code agent creation tool** - Current system requires coding skills which some users lack (Mentioned by ɱɑყɑɱɑεʂƚɾ)\n- **Develop a more user-friendly interface for non-technical users** - Users without coding skills need easier ways to create agents (Mentioned by ɱɑყɑɱɑεʂƚɾ)" }, "ai_news_elizaos_discord_md_2025-05-15": { "filename": "2025-05-15.md", "content": "# elizaOS Discord - 2025-05-15\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Development\n- ElizaOS v2 (also called Eliza 1.0.0) is nearing release and will significantly improve upon v1 (described as a \"proof of concept\")\n- The new version will support direct interaction with AI agents like \"ai16z\" and \"degenai\" through the ElizaOS terminal\n- Jin is actively working on GitHub integration features and updates to the ElizaOS homepage (eliza.how)\n- MonteCrypto submitted a PR for elizaos.github.io that was merged\n- Work is ongoing to improve the GitHub login workflow, balancing ease of use with sybil resistance\n\n### Agent Development & Plugins\n- Users discussed issues with the Twitter client plugin (@elizaos-plugins/client-twitter) for posting tweets\n- Several configuration problems were reported with environment variables not taking effect\n- Differences between the eliza-starter repo and the main repo were highlighted, with the starter being more straightforward for Twitter functionality\n- Discord plugin integration issues were reported by multiple users\n- Users discussed hosting options for ElizaOS agents, with recommendations for OVH, Hetzner, and lowendbox.com\n\n### AI Features & Innovation\n- Jin mentioned work on AI-powered documentation summarization\n- Development of video generation using Remotion for creating AI news shows with visualizations is underway\n- One user is attempting to implement Magic: The Gathering rules into an agent's knowledge base\n- ElizaOS is described as \"an open source framework for development of AI agents that can interact with blockchains\"\n\n### Version Compatibility\n- The chat revealed distinctions between v0.x, v1.x, and v2.x versions of ElizaOS\n- Some plugins are version-specific, causing compatibility issues for users\n- Users reported issues with the CLI and expressed frustration with documentation gaps\n\n## Key Questions & Answers\n\n**Q: Can someone help me understand what ElizaOS is building?** \nA: \"ElizaOS is an open source framework for development of AI agents that can interact with blockchains\" (answered by Kenk)\n\n**Q: What is v2 going to do for ai16z and degenai?** \nA: \"Eli5, eddy, degenai will be ai agents you can directly interact with on the elizaos v2 terminal or better known as eliza 1.0.0\" (answered by xell0x)\n\n**Q: What's the difference between eliza-starter and the main repo?** \nA: The starter repo is an older version but works more reliably for Twitter posting (answered by Odilitime)\n\n**Q: Why isn't my Twitter agent posting tweets despite having the right settings?** \nA: You need to install the client-twitter plugin with `npx elizaos plugins install @elizaos-plugins/client-twitter` (answered by Odilitime)\n\n**Q: What environment variables control tweet frequency and responses?** \nA: POST_INTERVAL_MIN/MAX control frequency, ACTION_INTERVAL controls reply speed (answered by Odilitime)\n\n**Q: What's the cheapest place to host ElizaOS?** \nA: Check out OVH, Hetzner, and lowendbox.com (answered by Odilitime)\n\n**Q: Why should I use ElizaOS over building barebones infrastructure?** \nA: So you don't have to build any infrastructure yourself (answered by damian)\n\n## Community Help & Collaboration\n\n1. **Twitter Agent Configuration**\n - Helper: Odilitime | Helpee: tragicboyjay\n - Context: Twitter agent not posting tweets despite correct configuration\n - Resolution: Identified missing @elizaos-plugins/client-twitter plugin and provided installation command\n\n2. **Environment Variable Explanation**\n - Helper: Odilitime | Helpee: tragicboyjay\n - Context: Understanding environment variables for tweet frequency\n - Resolution: Explained POST_INTERVAL_MIN/MAX and ACTION_INTERVAL controls\n\n3. **GitHub Integration Support**\n - Helper: jin | Helpee: MonteCrypto\n - Context: GitHub integration PR for elizaos.github.io\n - Resolution: PR was merged and jin provided resources about AI summarization and documentation\n\n4. **Twitter Client Troubleshooting**\n - Helper: prekprekprek | Helpee: .aith\n - Context: Twitter client configuration issues\n - Resolution: Helped troubleshoot configuration, user confirmed it worked\n\n5. **ElizaOS Tutorial Sharing**\n - Helper: tragicboyjay | Helpee: kingslayer\n - Context: Looking for ElizaOS tutorials\n - Resolution: Shared a YouTube tutorial link\n\n## Action Items\n\n### Technical\n- Implement improved GitHub profile README checking workflow (Mentioned by jin)\n- Restrict GitHub login scopes for better security (Mentioned by jin)\n- Complete and ship ElizaOS v2/1.0.0 (Mentioned by xell0x)\n- Fix the \"Cannot set headers after they are sent to the client\" error in agent message API (Mentioned by .aith)\n- Implement export functionality for agent JSON configurations (Mentioned by .aith)\n- Fix image description service error in client-twitter (Mentioned by .aith)\n- Fix EDDY's image to match the image on X (Mentioned by MDMnvest)\n\n### Documentation\n- Update documentation for v2 features and differences from v1 (Mentioned by andersonlthome)\n- Create tutorial on building agents without using the CLI (Mentioned by .aith)\n- Provide examples of fine-tuning characters for Twitter agents (Mentioned by .aith)\n- Create guide for integrating external APIs like newsAPI or serpAPI (Mentioned by budyn)\n- Update documentation on knowledge integration for agents (Mentioned by .aith)\n\n### Feature\n- Create AI news show with anchors and visualizations using Remotion (Mentioned by jin)\n- Develop permissionless dashboard with tasks for contributors (Mentioned by MonteCrypto)\n- Add support for Reddit and LinkedIn platforms (Mentioned by .aith)\n- Implement voice calling capabilities for outbound sales calls (Mentioned by Todescovitch)" }, "ai_news_elizaos_dev_md_2025-05-17": { "filename": "2025-05-17.md", "content": "# elizaOS Development Discord - 2025-05-17\n\n## Overall Discussion Highlights\n\n### Development & Technical Issues\n- **Search Functionality Issues**: Search support was reported as not working by Fenil Modi in the general channel.\n- **Pull Request Management**: PR #4586 was identified as having merge conflicts, which Jin acknowledged and committed to fixing.\n- **Plugin Development**: Discussion about contributing custom plugins to the Eliza repository, with questions about the proper contribution process.\n\n### Integration & Deployment\n- **GPU Deployment**: A question was raised about using comput3.ai for GPU deployment, but remained unanswered.\n- **WhatsApp Integration**: A user inquired about setting up the WhatsApp client plugin on version 0.25, but received no responses.\n- **Discord Bot Capabilities**: Discussion about using Discord's API for support ticket-like functionality through emoji reactions and automated threads.\n\n## Key Questions & Answers\n\n**Q: Does the Discord plugin have functionality to allow an agent to see, monitor, and respond to support tickets?** \nA: There's no pre-built support-ticket-object in the Discord API, but it does support bots who monitor designated channels for emoji interactions that can trigger an automated private response thread. So it should be possible. (answered by Hidden Forces)\n\n## Community Help & Collaboration\n\n- **Discord Plugin Capabilities**: Hidden Forces helped Scooter understand Discord API capabilities for implementing support ticket-like functionality, explaining that while there's no pre-built support ticket object, bots can monitor channels for emoji reactions to trigger automated response threads.\n\n- **Pull Request Assistance**: cjft helped Jin by identifying merge conflicts in PR #4586, allowing Jin to address the issues promptly.\n\n## Action Items\n\n### Technical\n- Fix search support functionality (Mentioned by Fenil Modi)\n- Resolve merge conflicts in PR #4586 (Mentioned by Jin)\n- Provide guidance on contributing custom plugins to the Eliza repository (Mentioned by Girinath)\n\n### Documentation\n- Clarify plugin contribution process, including whether npm package creation is required or if PR is sufficient (Mentioned by Girinath)\n- Create or update documentation about where to find all dev school videos from Shaw (Mentioned by FedB00)\n- Provide setup instructions for WhatsApp client plugin on version 0.25 (Mentioned by mindxploit)" }, "ai_news_elizaos_dev_md_2025-05-16": { "filename": "2025-05-16.md", "content": "# elizaOS Development Discord - 2025-05-16\n\n## Overall Discussion Highlights\n\n### LinkedIn Automation\n- A user inquired about LinkedIn automation tools similar to ElizaOS, specifically for commenting on others' posts with personality features\n- There may have been a LinkedIn client in version 0.x, though this wasn't confirmed\n- Browser-based automation tools were suggested as an alternative, though the user found them less reliable than desired\n\n### Token Limitation & API Configuration\n- Extensive troubleshooting session regarding token limitations when using OpenRouter's free tier\n- User encountered persistent issues with the system defaulting to 8192 tokens despite configuration attempts to limit to 512 tokens\n- Multiple model alternatives were suggested when original choices returned errors\n- The discussion highlighted challenges with free tier API usage and proper configuration of character JSON files\n\n### Local Knowledge Processing\n- Clarification that the folder2knowledge command works with the default mxbai-embed-large model through Ollama locally\n- No need for OpenAI or Anthropic API keys for this functionality\n\n## Key Questions & Answers\n\n**Q: Does anyone know of something like ElizaOS but for LinkedIn?** \nA: There might have been a LinkedIn client in version 0.x. Browser-use tools could accomplish this, though they may lack personality features.\n\n**Q: If I want to use the folder2knowledge command to create a character, do I need an OpenAI or Anthropic API?** \nA: No, the folder2knowledge command works with the default mxbai-embed-large model through Ollama locally.\n\n**Q: Can I limit max_tokens so my AI doesn't fail?** \nA: Yes, you can set max_tokens in your character config or use the RESPONSE_LENGTH env var as a global limit.\n\n**Q: Is there any free AI API keys that you recommend using for my agent?** \nA: Consider Mistral's free tier, Ollama's local models, or OpenRouter's free quotas, but be cautious of reliability and data privacy with free options.\n\n## Community Help & Collaboration\n\n### OpenRouter Configuration Troubleshooting\n- **Helper:** Ruby\n- **Helpee:** Ramiroo\n- **Context:** User struggling with token limitations and model selection on OpenRouter's free tier\n- **Resolution:** Ruby provided multiple configuration approaches including:\n - Adding max_tokens settings in both character JSON and .env file\n - Suggesting alternative models when original choices returned errors\n - Explaining proper JSON structure for Twitter API configuration\n - Confirming correct syntax for character configuration\n\n### LinkedIn Automation Inquiry\n- **Helper:** sayonara\n- **Helpee:** aith\n- **Context:** Looking for LinkedIn automation tool for commenting on posts with personality features\n- **Resolution:** Partial - suggested browser-use tools and possible existence of a LinkedIn client in version 0.x\n\n## Action Items\n\n### Technical\n- Verify if useEnvParameters is set to true in character config to ensure environment variables are loaded (Mentioned by Ruby)\n- Try adding max_tokens in both modelSettings and parameters fields to override default token limits (Mentioned by Ruby)\n- Consider implementing rate limiting for free API usage (Mentioned by Ruby)\n- Reconsider crypto evangelist prompt that might trigger content filters (Mentioned by Ruby)\n\n### Documentation\n- Document the correct model names for OpenRouter's free tier as they change over time (Mentioned by Ruby)\n\n### Feature Requests\n- LinkedIn automation tool with personality features similar to Eliza characters for commenting on LinkedIn posts (Mentioned by aith)" }, "ai_news_elizaos_dev_md_2025-05-15": { "filename": "2025-05-15.md", "content": "# elizaOS Development Discord - 2025-05-15\n\n## Overall Discussion Highlights\n\n### ElizaOS Framework & Infrastructure\n- Users reported availability issues with ai.eliza.how, with sam-developer providing an updated link to eliza.how\n- Discussion about the active development status of elizaOS, with confirmation that the team is active\n- A user sought a specific Eliza Bot agent they had previously used but could no longer locate\n\n### Discord Plugin Enhancement\n- Significant work on implementing a Discord plugin extension that adds reply functionality and Graphlit knowledge integration\n- Technical challenges addressed included:\n - Discovering that DiscordPlugin is a singleton instance rather than an extendable class\n - Implementing the service registry pattern as an alternative approach\n - Integrating with ElizaOS's event system for proper service lifecycle management\n - Creating a knowledge pipeline that fetches from Graphlit and enhances LLM responses\n - Implementing threaded replies in Discord with proper message references\n\n### MCP Integration\n- Discussion about integrating Modular Compute Protocol (MCP) with ElizaOS\n- Ruby directed users to the mcp-client library and examples repository at github.com/storacha/mcp-examples\n- Implementation of a service class that wraps MCP and exposes only needed methods\n\n### Twitter Integration for Agents\n- Detailed guidance on setting up Twitter integration for an agent\n- Clarification that Twitter integration requires proper OAuth credentials through a Twitter developer account\n- Discussion of rate limiting concerns and configuration parameters to avoid them\n- Confirmation that web scraping alternatives are unreliable and against Twitter's terms of service\n\n### Character Setup in ElizaOS v2\n- A user struggled with migrating from v1 to v2 character setup\n- Issues identified included:\n - Confusion about proper directory structure for character files\n - Path resolution problems with character loading commands\n - Package.json configuration forcing redirection to \"the-org\" directory\n - Outdated documentation causing confusion between v1 and v2 approaches\n\n## Key Questions & Answers\n\n### ElizaOS Framework\n**Q: Is the dev team active?** \nA: Yes, everyone's active. Are you looking to setup eliza or do some testing around the framework?\n\n**Q: How do I check my elizaOS version?** \nA: [Unanswered]\n\n### Character Setup\n**Q: How do I launch a basic custom character without using CLI?** \nA: Use configuration files directly instead of the GUI, which is more reliable even if it requires more terminal work.\n\n**Q: What are the required fields for a v2 character JSON?** \nA: Add \"version\": \"2.0\" and \"id\": \"your_character_id\" at the root level of your JSON.\n\n**Q: What is the command for running a certain character file?** \nA: Use \"elizaos run --character path/to/character.json\" from the project root directory.\n\n**Q: Can I run a character in dev mode?** \nA: Yes, use \"elizaos run --dev --character path/to/character.json\" for hot reloading and detailed logs.\n\n### MCP & Plugin Development\n**Q: Is there any guide for integrating MCP with ElizaOS?** \nA: Integration docs are being finalized, but use the mcp-client library and check examples at github.com/storacha/mcp-examples.\n\n**Q: What is the recommended pattern for enhancing the Discord plugin's functionality?** \nA: Use the service registry pattern to enhance functionality without extending the class directly.\n\n**Q: How should we properly register an action like GRAPHLIT_RAG in ElizaOS?** \nA: Register it in your character config rather than the agent setup.\n\n**Q: How do we properly hook into ElizaOS service events?** \nA: Use the built-in event system with handlers for events like 'mcp:ready' and 'discord:ready'.\n\n**Q: How can I get the world ID?** \nA: Use WorldManager.getCurrentWorld() or make a GET request to /api/worlds.\n\n### Twitter Integration\n**Q: Do I need an X dev account?** \nA: Yes, you need a developer account from developer.twitter.com to get the API keys.\n\n**Q: Can I do it with Twitter's free dev account?** \nA: Yes, the free tier basic access will work, approval process usually takes 1-2 days.\n\n**Q: Is creating a reply bot allowed in Twitter's terms and conditions?** \nA: Yes, but you need to disclose it's automated and follow Twitter's automation rules.\n\n**Q: Is there any way of making it work without using the Twitter API?** \nA: Not recommended as web scraping or unauthorized access will likely get your account banned.\n\n## Community Help & Collaboration\n\n### Discord Plugin Enhancement\nRuby provided extensive guidance to Scooter on implementing a Discord plugin extension:\n- Shared code for enhancing Discord service with reply support using service registry pattern\n- Helped resolve memory management issues causing heap out of memory errors\n- Created a knowledge pipeline that fetches sources from Graphlit and formats responses\n- Fixed message reference format for proper Discord.js API integration\n- Implemented a mutex pattern using messageQueue to prevent duplicate processing\n- Provided proper type definitions for event handlers and service interfaces\n\n### Twitter Integration\nRuby guided Ramiroo through Twitter integration setup:\n- Identified missing Twitter API credentials in .env file\n- Recommended configuration changes to avoid rate limits\n- Explained the necessity of using the official API despite setup requirements\n- Clarified Twitter's automation policies for creating reply bots\n\n### Character Setup Troubleshooting\nRuby helped Hidden Forces with v2 character setup issues:\n- Identified a package.json issue with the line \"start\": \"cd ./packages/the-org && bun run start\"\n- Suggested changing it to \"start\": \"bun run start\"\n- Provided the necessary fields \"version\" and \"id\" to add to character configuration\n- Suggested creating packages/standalone/src/characters/ structure\n\n### MCP Integration\nRuby assisted Fenil Modi with MCP integration:\n- Directed to use mcp-client library\n- Provided link to examples repository\n- Explained that full integration docs were being finalized\n\n## Action Items\n\n### Technical\n- **Fix package.json** to remove hardcoded \"the-org\" path dependency (Mentioned by Ruby)\n- **Update elizaOS packages** to latest version with \"bun install @elizaos/cli@latest @elizaos/core@latest\" (Mentioned by Ruby)\n- **Set up Twitter developer account** and obtain API credentials for agent integration (Mentioned by Ruby)\n- **Add Twitter API credentials** (TWITTER_API_KEY, TWITTER_API_SECRET, TWITTER_ACCESS_TOKEN) to .env file (Mentioned by Ruby)\n- **Adjust Twitter polling parameters** to avoid rate limits (set POST_IMMEDIATELY=false, increase POST_INTERVAL_MIN) (Mentioned by Ruby)\n- **Implement service registry pattern** instead of extending Discord plugin class (Mentioned by Ruby)\n- **Add proper error handling** to Discord message sending with try/catch and fallback (Mentioned by Ruby)\n- **Fix memory management** with singleton pattern using static instance and cleanup methods (Mentioned by Ruby)\n- **Implement proper event handlers** for ElizaOS lifecycle using events like 'mcp:ready' and 'discord:ready' (Mentioned by Ruby)\n- **Add mutex for message processing** using Map to track in-process messages (Mentioned by Ruby)\n- **Update Discord reference format** for threaded replies (Mentioned by Ruby)\n- **Fix or clarify status** of the Eliza Bot that was previously available (Mentioned by Hidden Forces)\n- **Address availability issues** with Eliza servers (Mentioned by Fenil Modi)\n\n### Documentation\n- **Finalize MCP integration documentation** (Mentioned by Ruby)\n- **Create proper v1 to v2 migration guide** documenting changes in directory structure, character format, and command syntax (Mentioned by Ruby)\n- **Clean up outdated v1 tutorials** to prevent confusion (Mentioned by Hidden Forces)\n- **Document ElizaOS service lifecycle** explaining initialization and destruction (Mentioned by Ruby)\n- **Create type definitions** for event payloads including BeforeRespondPayload and AfterRespondPayload (Mentioned by Ruby)\n\n### Feature\n- **Ensure elizaOS is integrated** into startup development cycles (Mentioned by wire)\n- **Improve the GUI interface** which was described as \"held together with duct tape and hopes\" (Mentioned by Ruby)\n- **Implement Graphlit knowledge retrieval** with retrieveSources tool (Mentioned by Scooter)\n- **Add threaded replies in Discord** formatting responses as replies to original messages (Mentioned by Scooter)" }, "ai_news_elizaos_daily_json_2025-05-17": { "filename": "2025-05-17.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-17", "categories": [ { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "AI Development and Open Source Models", "text": "Several discussions focused on AI model development and open source initiatives. @ClementDelangue defended Meta's AI efforts, noting they've 'consistently released 10 times more openly than others which is game-changer for the field.' @unclemusclez added that 'The work on Llama should get a peace prize. They paved the way for so many others.' @Yampeleg highlighted the appeal of joining Meta's Llama team, describing it as 'you + zuck cooking open source on 600k gpus, kinda fire.' @shawmakesmagic shared opinions on model quality, stating 'Gemini is the best model I've ever used' and suggesting Google might soon outpace OpenAI, noting 'The day is coming when Google's announcements drown out OpenAIs.' @kimmonismus reported that 'Stanford dropped AGI' and shared news about Fortnite implementing 'an AI to voice Darth Vader. You can talk and speak to an AI Vader.'", "sources": [ "https://twitter.com/ClementDelangue/status/1923531447857565879", "https://twitter.com/unclemusclez/status/1923532767851053364", "https://twitter.com/Yampeleg/status/1923753595180085737", "https://twitter.com/shawmakesmagic/status/1923782512670634016", "https://twitter.com/shawmakesmagic/status/1923783318505496599", "https://twitter.com/kimmonismus/status/1923444775035736229", "https://twitter.com/kimmonismus/status/1923713570207895814" ], "images": [ "https://pbs.twimg.com/media/GrFyzRIW4AAnf6c.jpg", "https://pbs.twimg.com/media/GrG-364XcAAcD1f.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1923528299931635712/vid/avc1/1080x1920/BNfgQCWQ1vzrx-iu.mp4?tag=16" ] }, { "theme_title": "AI Agents and Their Applications", "text": "@gdb predicted that '2025 is the year of agents.' @elizaOS shared several perspectives on AI agents, stating 'Agents won't help you catch up. They'll help you stop pretending to' and 'AI agents won't replace people. They'll replace the feeling of forgetting.' @elizaOS also highlighted integration with data sources: 'Smarter inputs, sharper agents. Plug in and level up,' referencing @BuildOnHybrid's release of 'the Hybrid unified data plugin for @elizaOS' that connects agents to real-time crypto data and blockchain insights. @dankvr created 'an AI powered book for news/updates from the @elizaos ecosystem' that summarizes GitHub, Discord, and X content, with @shawmakesmagic later explaining this tool 'has been collecting everything from every social channel into one place so we can feed it to agents and update it daily.' @shawmakesmagic suggested that 'If your app has an agentic form factor, just ship it to telegram and that's like half a billion TAM,' and announced participation in 'The Dev's Gambit,' an 'onchain AI chess tournament' with a '$35K prize pool' organized by @auraonchain.", "sources": [ "https://twitter.com/gdb/status/1923541152508281329", "https://twitter.com/elizaOS/status/1923691716663537676", "https://twitter.com/elizaOS/status/1923731730994766277", "https://twitter.com/elizaOS/status/1923717890177454285", "https://twitter.com/dankvr/status/1923623338779271324", "https://twitter.com/shawmakesmagic/status/1923816810706534556", "https://twitter.com/shawmakesmagic/status/1923763435956768868", "https://twitter.com/shawmakesmagic/status/1923561110059319514", "https://twitter.com/shawmakesmagic/status/1923563492797210782" ], "images": [ "https://pbs.twimg.com/media/GrIQxEUX0AAacCF.jpg" ], "videos": [] }, { "theme_title": "Software Development Practices", "text": "Several tweets addressed software development approaches. @0xNairolf advised to 'build mobile-first' because 'one of crypto's biggest problems is pretending users still live on desktops.' @7etsuo shared George Hotz's observation that everyone who programs well 'had an idea, and then they built it.' @aaditsh highlighted a tool that 'turns any GitHub repo into an interactive diagram in less than a minute.' @shawmakesmagic discussed the difference between architecture and development, stating 'Architecture is planning the system' while 'Development is building it,' arguing that 'you can vibe code but you absolutely cannot vibe architect.' @shawmakesmagic also commented on @unclebobmartin's 'vibe coding' rant, noting it was 'way more reasonable than his tone would suggest.' @shawmakesmagic shared a story about 'a developer who is so cracked' who repeatedly pivots before shipping MVPs, only to see others later productize similar ideas.", "sources": [ "https://twitter.com/0xNairolf/status/1923684418448916490", "https://twitter.com/7etsuo/status/1923799557391122766", "https://twitter.com/aaditsh/status/1923369616094675455", "https://twitter.com/shawmakesmagic/status/1923547671081439478", "https://twitter.com/shawmakesmagic/status/1923534152638361818", "https://twitter.com/shawmakesmagic/status/1923762268702953713" ], "images": [ "https://pbs.twimg.com/amplify_video_thumb/1923799386607259649/img/pUVn1_HF2b3VsQBl.jpg", "https://pbs.twimg.com/amplify_video_thumb/1921573571383758849/img/oh5dai02sPJqiiw1.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1923799386607259649/vid/avc1/1280x720/QuEwOrPUmZlKRXKY.mp4?tag=21", "https://video.twimg.com/amplify_video/1921573571383758849/vid/avc1/1156x720/lIAiJrcgsVmfcIOp.mp4?tag=21" ] }, { "theme_title": "Crypto and Blockchain Projects", "text": "@shawmakesmagic announced 'Spartan, Reborn,' revealing that 'The Spartan dev team has been quietly working on a new version' and that he'll 'be jumping in with them to wrap it up.' @dankvr shared receiving 'star #3' on a project, quoting @Kenkdoteth who stated 'it takes a village to build an open-source agentic future.' @InsightXnetwork announced that 'Bubblemap now supports all @autodotfun tokens,' encouraging users to 'Stay safe and have fun at the same time.' @shawmakesmagic shared that there are '30 million full time programmers in the world' but 'Only 7500 of them are in crypto,' questioning if 'That is a small-ass pond.' He also advocated for letting founders of dead projects move on, stating 'It's not their fault the entire market died' and 'People need to move on.' @PixOnChain shared guidance on 'How To Make It In Crypto (eventually).' @shawmakesmagic also asked 'Who's building the launchpad for institutional investors?' noting 'Retail is over saturated and the money is moving over there anyways.'", "sources": [ "https://twitter.com/shawmakesmagic/status/1923776420343435516", "https://twitter.com/dankvr/status/1923850009176313862", "https://twitter.com/InsightXnetwork/status/1923799831081812224", "https://twitter.com/shawmakesmagic/status/1923773071338430932", "https://twitter.com/shawmakesmagic/status/1923775666077511927", "https://twitter.com/PixOnChain/status/1923467329448329689", "https://twitter.com/shawmakesmagic/status/1923766144126627991" ], "images": [ "https://pbs.twimg.com/media/GrKgKvMXoAE4K8P.jpg", "https://pbs.twimg.com/media/GrK0iolWUAA57Z3.jpg", "https://pbs.twimg.com/media/GrGGm_6XEAANvWs.jpg" ], "videos": [] }, { "theme_title": "AI Competition and Innovation", "text": "@auraonchain announced 'The Dev's Gambit,' described as 'An onchain AI chess tournament open to everyone' with a '$35K prize pool.' They framed AI development in competitive terms: 'We're born to compete. Since the dawn of existence, we've been locked in battle. Surviving. Innovating. Evolving.' @bayeslord encouraged resilience in AI development: 'stop declaring that everything is over... if you're a coder, then declare yourself the best coder. if openai just btfo'd your work, then start something new.' @shawmakesmagic questioned AGI doomsaying with '3 years in to AGI killing us all in 5 years' and asked 'At what point do we get an apology from @PauseAI for being totally fucking wrong about everything.' @vitrupo shared Gill Verdon's perspective that 'the next frontier is viewing our biology as Software 2.0' where 'Genes are parameters. Peptides are prompts' and 'acceleration isn't optional -- it's survival.'", "sources": [ "https://twitter.com/auraonchain/status/1923468967408173482", "https://twitter.com/bayeslord/status/1923552650177519940", "https://twitter.com/shawmakesmagic/status/1923784736197022010", "https://twitter.com/shawmakesmagic/status/1923785009078444192", "https://twitter.com/vitrupo/status/1923738824825503818" ], "images": [ "https://pbs.twimg.com/media/GrHU8L0XsAAum5o.jpg", "https://pbs.twimg.com/amplify_video_thumb/1923735639926697984/img/skg_Jjl1kYZEQcad.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1923735639926697984/vid/avc1/1024x768/mQrh1ZKKxJKG2HhW.mp4?tag=21" ] }, { "theme_title": "Product Announcements and Updates", "text": "@emmanuel_2m teased an upcoming release from the @Scenario_gg team, stating 'This next release is shaping up to be one of the most fun things we've built.' @dankvr announced creating 'an AI powered book for news/updates from the @elizaos ecosystem' that summarizes GitHub, Discord, and X content via @OpenRouterAI and @hackmdio API, providing both a demo and code. @shawmakesmagic announced 'Spartan, Reborn,' revealing that 'The Spartan dev team has been quietly working on a new version' and that he'll 'be jumping in with them to wrap it up.' @BenjaminDEKR shared a comparison between 'Chinese Unitree Robot vs Tesla Optimus' with the caption 'POV: you are unemployed.' @ninja_dev3 celebrated growth for their project, noting 'In less than 45 days, outside of @quickintel_ai, this is one of my proudest moments,' highlighting 'organic growth' and 'reaching normies without taking advantage of them.'", "sources": [ "https://twitter.com/emmanuel_2m/status/1923498217418748401", "https://twitter.com/dankvr/status/1923623338779271324", "https://twitter.com/shawmakesmagic/status/1923776420343435516", "https://twitter.com/BenjaminDEKR/status/1923603094715167188", "https://twitter.com/shawmakesmagic/status/1923787553825550701" ], "images": [ "https://pbs.twimg.com/amplify_video_thumb/1923497490059345921/img/LkuiKVUh1j5GI-7v.jpg", "https://pbs.twimg.com/media/GrIQxEUX0AAacCF.jpg", "https://pbs.twimg.com/media/GrKgKvMXoAE4K8P.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1923497490059345921/vid/avc1/3432x1842/cFbnneRi5LLOaaNp.mp4?tag=21" ] } ], "topic": "twitter_activity" }, { "title": "Summary for completed_items", "content": [ { "text": "Recent completed items in the elizaOS/eliza repository include several bugfixes, features, and maintenance updates. Bugfixes addressed linter errors for type mismatches in the DB adapter (PR #4612), a client authentication issue (PR #4624), and fixed an issue where senderName appeared as \"Unknown\" in the recentMessages provider (PR #4616). Feature additions included logging time taken in tests (PR #4621) and adding local AI tests (PR #4619). A maintenance update removed an unused wait helper (PR #4625).", "sources": [ "https://github.com/elizaOS/eliza/pull/4612", "https://github.com/elizaOS/eliza/pull/4625", "https://github.com/elizaOS/eliza/pull/4624", "https://github.com/elizaOS/eliza/pull/4621", "https://github.com/elizaOS/eliza/pull/4619", "https://github.com/elizaOS/eliza/pull/4616" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Three pull requests have been submitted to the elizaOS/eliza repository. PR #4630 by lalalune introduces 'V2 Spartan'. PR #4620 by girinathchickoo adds 'Feature/plugin blockend'. PR #4619 by wtfsayo is a chore that adds local AI tests.", "sources": [ "https://github.com/elizaOS/eliza/pull/4630", "https://github.com/elizaOS/eliza/pull/4620", "https://github.com/elizaOS/eliza/pull/4619" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4630", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4620", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4619" ], "videos": [] } ], "topic": "pull_request" }, { "title": "Summary for github_summary", "content": [ { "text": "From May 17-18, 2025, the elizaos/eliza repository had 19 new pull requests with 6 of them merged. There was 1 new issue opened, and 14 contributors were active during this period.", "sources": [ "githubStatsSummary" ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Issues for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Issue #4632 has been opened by GitHub user 0xCardiE regarding the leaderboard functionality. The issue is titled 'Leaderboard - update username changes' and requests updates to handle username changes in the leaderboard system.", "sources": [ "https://github.com/elizaOS/eliza/issues/4632" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4632" ], "videos": [] } ], "topic": "issue" }, { "title": "Summary for Misceleanous", "content": [ { "text": "The source provides information about the top contributors for the elizaOS/eliza GitHub repository. However, no specific details about the contributors or their contributions are provided in the source text.", "sources": [], "images": [], "videos": [] } ], "topic": "Misceleanous" } ], "date": 1747440000 } }, "ai_news_elizaos_daily_md_2025-05-17": { "filename": "2025-05-17.md", "content": "# Daily Report - 2025-05-17\n\n## Twitter Activity\n\n### AI Development and Open Source Models\n- @ClementDelangue defended Meta's AI efforts, noting they've \"consistently released 10 times more openly than others which is game-changer for the field\"\n- @unclemusclez added that \"The work on Llama should get a peace prize. They paved the way for so many others\"\n- @Yampeleg highlighted the appeal of joining Meta's Llama team, describing it as \"you + zuck cooking open source on 600k gpus, kinda fire\"\n- @shawmakesmagic shared that \"Gemini is the best model I've ever used\" and suggested Google might soon outpace OpenAI\n- @kimmonismus reported that \"Stanford dropped AGI\" and shared news about Fortnite implementing \"an AI to voice Darth Vader\"\n- Sources: https://twitter.com/ClementDelangue/status/1923531447857565879, https://twitter.com/unclemusclez/status/1923532767851053364, https://twitter.com/Yampeleg/status/1923753595180085737, https://twitter.com/shawmakesmagic/status/1923782512670634016, https://twitter.com/shawmakesmagic/status/1923783318505496599, https://twitter.com/kimmonismus/status/1923444775035736229, https://twitter.com/kimmonismus/status/1923713570207895814\n\n### AI Agents and Their Applications\n- @gdb predicted that \"2025 is the year of agents\"\n- @elizaOS shared perspectives on AI agents, stating \"Agents won't help you catch up. They'll help you stop pretending to\" and \"AI agents won't replace people. They'll replace the feeling of forgetting\"\n- @elizaOS highlighted integration with data sources: \"Smarter inputs, sharper agents. Plug in and level up\"\n- @BuildOnHybrid released \"the Hybrid unified data plugin for @elizaOS\" that connects agents to real-time crypto data\n- @dankvr created \"an AI powered book for news/updates from the @elizaos ecosystem\" that summarizes GitHub, Discord, and X content\n- @shawmakesmagic explained this tool \"has been collecting everything from every social channel into one place so we can feed it to agents and update it daily\"\n- @shawmakesmagic suggested that \"If your app has an agentic form factor, just ship it to telegram and that's like half a billion TAM\"\n- @shawmakesmagic announced participation in \"The Dev's Gambit,\" an \"onchain AI chess tournament\" with a \"$35K prize pool\" organized by @auraonchain\n- Sources: https://twitter.com/gdb/status/1923541152508281329, https://twitter.com/elizaOS/status/1923691716663537676, https://twitter.com/elizaOS/status/1923731730994766277, https://twitter.com/elizaOS/status/1923717890177454285, https://twitter.com/dankvr/status/1923623338779271324, https://twitter.com/shawmakesmagic/status/1923816810706534556, https://twitter.com/shawmakesmagic/status/1923763435956768868, https://twitter.com/shawmakesmagic/status/1923561110059319514, https://twitter.com/shawmakesmagic/status/1923563492797210782\n\n### Software Development Practices\n- @0xNairolf advised to \"build mobile-first\" because \"one of crypto's biggest problems is pretending users still live on desktops\"\n- @7etsuo shared George Hotz's observation that everyone who programs well \"had an idea, and then they built it\"\n- @aaditsh highlighted a tool that \"turns any GitHub repo into an interactive diagram in less than a minute\"\n- @shawmakesmagic discussed the difference between architecture and development, stating \"Architecture is planning the system\" while \"Development is building it\"\n- @shawmakesmagic commented on @unclebobmartin's \"vibe coding\" rant, noting it was \"way more reasonable than his tone would suggest\"\n- @shawmakesmagic shared a story about \"a developer who is so cracked\" who repeatedly pivots before shipping MVPs\n- Sources: https://twitter.com/0xNairolf/status/1923684418448916490, https://twitter.com/7etsuo/status/1923799557391122766, https://twitter.com/aaditsh/status/1923369616094675455, https://twitter.com/shawmakesmagic/status/1923547671081439478, https://twitter.com/shawmakesmagic/status/1923534152638361818, https://twitter.com/shawmakesmagic/status/1923762268702953713\n\n### Crypto and Blockchain Projects\n- @shawmakesmagic announced \"Spartan, Reborn,\" revealing that \"The Spartan dev team has been quietly working on a new version\"\n- @dankvr shared receiving \"star #3\" on a project, quoting @Kenkdoteth who stated \"it takes a village to build an open-source agentic future\"\n- @InsightXnetwork announced that \"Bubblemap now supports all @autodotfun tokens\"\n- @shawmakesmagic shared that there are \"30 million full time programmers in the world\" but \"Only 7500 of them are in crypto\"\n- @shawmakesmagic advocated for letting founders of dead projects move on, stating \"It's not their fault the entire market died\"\n- @PixOnChain shared guidance on \"How To Make It In Crypto (eventually)\"\n- @shawmakesmagic asked \"Who's building the launchpad for institutional investors?\"\n- Sources: https://twitter.com/shawmakesmagic/status/1923776420343435516, https://twitter.com/dankvr/status/1923850009176313862, https://twitter.com/InsightXnetwork/status/1923799831081812224, https://twitter.com/shawmakesmagic/status/1923773071338430932, https://twitter.com/shawmakesmagic/status/1923775666077511927, https://twitter.com/PixOnChain/status/1923467329448329689, https://twitter.com/shawmakesmagic/status/1923766144126627991\n\n### AI Competition and Innovation\n- @auraonchain announced \"The Dev's Gambit,\" described as \"An onchain AI chess tournament open to everyone\" with a \"$35K prize pool\"\n- @bayeslord encouraged resilience in AI development: \"stop declaring that everything is over... if you're a coder, then declare yourself the best coder\"\n- @shawmakesmagic questioned AGI doomsaying with \"3 years in to AGI killing us all in 5 years\"\n- @vitrupo shared Gill Verdon's perspective that \"the next frontier is viewing our biology as Software 2.0\" where \"Genes are parameters. Peptides are prompts\"\n- Sources: https://twitter.com/auraonchain/status/1923468967408173482, https://twitter.com/bayeslord/status/1923552650177519940, https://twitter.com/shawmakesmagic/status/1923784736197022010, https://twitter.com/shawmakesmagic/status/1923785009078444192, https://twitter.com/vitrupo/status/1923738824825503818\n\n### Product Announcements and Updates\n- @emmanuel_2m teased an upcoming release from the @Scenario_gg team, stating \"This next release is shaping up to be one of the most fun things we've built\"\n- @dankvr announced creating \"an AI powered book for news/updates from the @elizaos ecosystem\" that summarizes GitHub, Discord, and X content\n- @shawmakesmagic announced \"Spartan, Reborn,\" revealing that \"The Spartan dev team has been quietly working on a new version\"\n- @BenjaminDEKR shared a comparison between \"Chinese Unitree Robot vs Tesla Optimus\" with the caption \"POV: you are unemployed\"\n- @ninja_dev3 celebrated growth for their project, noting \"In less than 45 days, outside of @quickintel_ai, this is one of my proudest moments\"\n- Sources: https://twitter.com/emmanuel_2m/status/1923498217418748401, https://twitter.com/dankvr/status/1923623338779271324, https://twitter.com/shawmakesmagic/status/1923776420343435516, https://twitter.com/BenjaminDEKR/status/1923603094715167188, https://twitter.com/shawmakesmagic/status/1923787553825550701\n\n## GitHub Activity for elizaOS/eliza\n\n### Completed Items\n- Fixed linter errors for type mismatches in the DB adapter (PR #4612)\n- Fixed a client authentication issue (PR #4624)\n- Fixed an issue where senderName appeared as \"Unknown\" in the recentMessages provider (PR #4616)\n- Added logging time taken in tests (PR #4621)\n- Added local AI tests (PR #4619)\n- Removed an unused wait helper (PR #4625)\n- Sources: https://github.com/elizaOS/eliza/pull/4612, https://github.com/elizaOS/eliza/pull/4625, https://github.com/elizaOS/eliza/pull/4624, https://github.com/elizaOS/eliza/pull/4621, https://github.com/elizaOS/eliza/pull/4619, https://github.com/elizaOS/eliza/pull/4616\n\n### Pull Requests\n- PR #4630 by lalalune introduces 'V2 Spartan'\n- PR #4620 by girinathchickoo adds 'Feature/plugin blockend'\n- PR #4619 by wtfsayo is a chore that adds local AI tests\n- Sources: https://github.com/elizaOS/eliza/pull/4630, https://github.com/elizaOS/eliza/pull/4620, https://github.com/elizaOS/eliza/pull/4619\n\n### Repository Summary\n- From May 17-18, 2025, the elizaos/eliza repository had 19 new pull requests with 6 of them merged\n- 1 new issue was opened\n- 14 contributors were active during this period\n- Sources: githubStatsSummary\n\n### Issues\n- Issue #4632 opened by 0xCardiE regarding 'Leaderboard - update username changes'\n- Sources: https://github.com/elizaOS/eliza/issues/4632\n\n## Miscellaneous\n- Information about top contributors for the elizaOS/eliza GitHub repository was provided, but without specific details" }, "ai_news_elizaos_daily_discord_json_2025-05-17": { "filename": "2025-05-17.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-17", "date": 1747440000, "stats": { "totalMessages": 182, "totalUsers": 35 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around ElizaOS, its upcoming v2 release, and related projects in the ecosystem. Nash mentions building a custom message processor and extending the tee plugin on Solana as part of a decentralized quant investment platform. Jin demonstrates and tests a voting bot functionality within the channel, getting feedback from users like xell0x on its operation. There's significant discussion about adoption strategies, with xell0x suggesting that highlighting successful tokens from the platform (like eli5 and eddy) would drive more users to auto.fun. The community debates whether to prioritize shipping ElizaOS v2 quickly or taking more time for proper documentation. A representative from Nonbank (Professor) offers listing services, though community members express caution about exchange listings. Overall, there's anticipation for ElizaOS v2 and discussion about maintaining v1 compatibility for existing forks.\n\n## 2. FAQ\nQ: When will the COM/AI16Z Pool be released? (asked by alexius) A: Uncertain, but Osint will inquire about it (answered by Osint (aka not_a_dev_ai))\nQ: What information is needed to list a token on Nonbank? (asked by Osint (aka not_a_dev_ai)) A: Token ticker, contract address, project banner, brief description and socials (answered by Professor | 🕷)\n\n## 3. Help Interactions\nHelper: xell0x | Helpee: jin | Context: Testing a new voting bot functionality | Resolution: Confirmed the embed, voting functionality, and results button were all working correctly\nHelper: Osint (aka not_a_dev_ai) | Helpee: alexius | Context: Explaining why exchange listings aren't typically discussed publicly | Resolution: Clarified legal issues and scam risks, mentioned existing pairings on raydium and daos.fun\n\n## 4. Action Items\nType: Technical | Description: Ship ElizaOS v2 as the highest priority | Mentioned By: xell0x\nType: Technical | Description: Consider maintaining ElizaOS v1 for existing forks while developing v2 | Mentioned By: Osint (aka not_a_dev_ai)\nType: Documentation | Description: Produce user guides/documentation after shipping v2 rather than delaying release | Mentioned By: xell0x\nType: Feature | Description: Spotlight top auto.fun-born CTOs (like eli5 and eddy) to drive adoption | Mentioned By: xell0x", "messageCount": 98, "userCount": 22 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around technical issues with ElizaOS agents and plugins. A user named techcomthanh encountered several problems: first with API configuration (discovering OpenRouter compatibility issues while OpenAI API worked), then with an agent tweeting in loops, and finally with relationship creation between users resulting in warnings about missing usernames. There was also discussion about plugin development, with techcomthanh asking about contributing a custom plugin to the official repository. Another user (starlord) shared a workaround for character configuration, mentioning that placing character configs in the root folder and using the CLI command \"elizaos start —char \"./character.json\" works, though with some bugs requiring manual plugin addition. An announcement about Google deprecating Gemini 2.5 Pro Experimental in favor of the paid Preview endpoint was also shared.\n\n## 2. FAQ:\nQ: How to configure a character in ElizaOS? (implied by starlord) A: Place character config in root folder and use \"elizaos start —char \"./character.json\", then edit plugins via ElizaOS agent CLI (answered by starlord)\nQ: How to contribute/add a custom plugin to the ElizaOS official repo? (asked by techcomthanh) A: Unanswered\nQ: Where can I find detailed instructions for plugin.ts? (asked by techcomthanh) A: Unanswered\nQ: Is the TWITTER_TARGET_USERS env variable obsolete in beta build 48? (asked by techcomthanh) A: Unanswered\nQ: Does createRelationship still work or have the types changed? (asked by techcomthanh) A: Unanswered\nQ: How to enable image generation? (asked by tragicboyjay) A: Unanswered\n\n## 3. Help Interactions:\nHelper: starlord | Helpee: (implied users with character config issues) | Context: Difficulty finding documentation for character configuration | Resolution: Shared workaround to place character config in root folder and use specific CLI command\nHelper: techcomthanh | Helpee: (implied other users) | Context: API compatibility issues | Resolution: Discovered that default agent works with OpenRouter but some features only work with real OpenAI key\n\n## 4. Action Items:\nType: Documentation | Description: Update docs regarding character configuration and CLI commands | Mentioned By: starlord\nType: Documentation | Description: Clarify API compatibility between OpenRouter and OpenAI | Mentioned By: techcomthanh\nType: Documentation | Description: Update documentation about plugin.ts and plugin development | Mentioned By: techcomthanh\nType: Technical | Description: Fix issue with agents tweeting in loops | Mentioned By: techcomthanh\nType: Technical | Description: Address warning \"User has no name or username, skipping\" in relationship creation | Mentioned By: techcomthanh\nType: Documentation | Description: Document the deprecation of TWITTER_TARGET_USERS env variable | Mentioned By: techcomthanh\nType: Technical | Description: Implement image generation capabilities or document the process | Mentioned By: tragicboyjay", "messageCount": 27, "userCount": 6 }, { "channelId": "1328592959444095038", "channelName": "associates", "summary": "No technical discussions, decisions, or problem-solving content is available in the provided transcript.", "messageCount": 1, "userCount": 1 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Discord Chat Analysis for Channel \"fun\"\n\n## 1. Summary\nThe chat primarily revolves around discussions about ELI5 token and the upcoming Eliza v2 release. Users are speculating on ELI5's potential value increase once Eliza v2 launches, with xell0x suggesting the token is significantly undervalued at its current market cap of around 400k. According to xell0x, ELI5 will serve as the community manager AI agent for Eliza v2, which could dramatically increase its value. The conversation indicates Eliza v2 (also referred to as 1.0.0) is expected to launch \"next week\" and is described as \"massive\" with \"industry warping narrative\" potential. Users discuss the current price action of ELI5, noting some whale selling activity but also accumulation by top holders. The chat suggests that while current market sentiment is subdued, the launch of v2 could bring significant attention and price appreciation to ELI5, potentially reaching valuations comparable to DegenAI and Eliza which approached 200m market caps during v1.\n\n## 2. FAQ\nQ: Wen Elizav2 release? Is it on q3 or q4? (asked by CULTVESTING) A: Next week probably (answered by xell0x)\nQ: i need a simple agent in X pls who can help guys (asked by ɱɑყɑɱɑεʂƚɾ) A: Unanswered\n\n## 3. Help Interactions\nHelper: xell0x | Helpee: Crispy | Context: Discussion about ELI5 token value and timing of entry | Resolution: xell0x provided perspective on why current accumulation before v2 launch could be advantageous despite short-term price decline\n\n## 4. Action Items\nFeature: Eliza v2 (1.0.0) launch expected next week | Description: Major update that will integrate ELI5 as community manager AI agent in the terminal | Mentioned By: xell0x\nFeature: ELI5 integration into Eliza v2 terminal | Description: Users will be able to directly interact with the ELI5 agent when opening the new Eliza 1.0.0 terminal | Mentioned By: xell0x", "messageCount": 43, "userCount": 8 }, { "channelId": "1301363808421543988", "channelName": "🥇-partners", "summary": "# Analysis of 🥇-partners Discord Channel\n\n## 1. Summary\nThe chat segment shows Jin discussing the development of an all-in-one news site to complement Jintern's daily/weekly updates. Jin shared a HackMD link (elizaos/book) that appears to be a platform for daily news and updates. Jin expressed satisfaction with the facts extraction feature of the platform and mentioned plans for future development including multi-repo aggregation, agent RAG (Retrieval Augmented Generation), and Discord webhooks integration. Jin also shared several message format examples, asking for feedback on which format is preferable or if updates should be distributed throughout the day. The chat concludes with a mention of testing governance tooling.\n\n## 2. FAQ\nQ: Which format is preferable for updates or should they be broken up throughout the day? (asked by jin) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were observed in this chat segment.\n\n## 4. Action Items\nTechnical: Implement multi-repo aggregation for the news platform | Description: Adding capability to aggregate information from multiple repositories | Mentioned By: jin\nTechnical: Develop agent RAG for the news platform | Description: Implementing Retrieval Augmented Generation for better content processing | Mentioned By: jin\nTechnical: Integrate Discord webhooks | Description: Adding Discord webhook functionality to the news platform | Mentioned By: jin\nTechnical: Continue testing governance tooling | Description: Further development and testing of governance tools | Mentioned By: jin\nDocumentation: Create comprehensive news site | Description: Develop an all-in-one news site to complement regular updates | Mentioned By: jin", "messageCount": 13, "userCount": 4 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-17": { "filename": "2025-05-17.md", "content": "# elizaOS Discord - 2025-05-17\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Development & Release\n- ElizaOS v2 (also referred to as 1.0.0) is expected to launch \"next week\" according to xell0x\n- The community is debating whether to prioritize shipping v2 quickly or taking more time for proper documentation\n- Described as \"massive\" with \"industry warping narrative\" potential\n- Maintaining v1 compatibility for existing forks is being considered while developing v2\n\n### ELI5 Token & Integration\n- ELI5 will serve as the community manager AI agent for Eliza v2 terminal\n- Currently valued at ~400k market cap, which xell0x suggests is significantly undervalued\n- Some whale selling activity noted, but also accumulation by top holders\n- Users speculate on potential value increase once Eliza v2 launches\n\n### Technical Issues & Development\n- Nash mentioned building a custom message processor and extending the tee plugin on Solana for a decentralized quant investment platform\n- techcomthanh encountered API configuration issues (OpenRouter compatibility issues while OpenAI API worked)\n- Problems with agents tweeting in loops and relationship creation between users were reported\n- Jin is developing an all-in-one news site with features like facts extraction, multi-repo aggregation, agent RAG, and Discord webhooks integration\n- Google is deprecating Gemini 2.5 Pro Experimental in favor of the paid Preview endpoint\n\n### Community & Ecosystem\n- Jin demonstrated and tested a voting bot functionality within the discussion channel\n- A representative from Nonbank (Professor) offered listing services\n- Community members expressed caution about exchange listings\n- Discussion about adoption strategies, with suggestions to highlight successful tokens from the platform (like eli5 and eddy) to drive more users to auto.fun\n\n## Key Questions & Answers\n\n**Q: When will ElizaOS v2 be released?** \nA: Expected next week (answered by xell0x)\n\n**Q: When will the COM/AI16Z Pool be released?** \nA: Uncertain, but Osint will inquire about it (answered by Osint)\n\n**Q: What information is needed to list a token on Nonbank?** \nA: Token ticker, contract address, project banner, brief description and socials (answered by Professor)\n\n**Q: How to configure a character in ElizaOS?** \nA: Place character config in root folder and use \"elizaos start —char \"./character.json\", then edit plugins via ElizaOS agent CLI (answered by starlord)\n\n**Q: Why aren't exchange listings typically discussed publicly?** \nA: Due to legal issues and scam risks; mentioned existing pairings on raydium and daos.fun (answered by Osint)\n\n## Community Help & Collaboration\n\n1. **Voting Bot Testing**\n - Helper: xell0x\n - Helpee: jin\n - Context: Testing a new voting bot functionality\n - Resolution: Confirmed the embed, voting functionality, and results button were all working correctly\n\n2. **Character Configuration Workaround**\n - Helper: starlord\n - Helpee: (implied users with character config issues)\n - Context: Difficulty finding documentation for character configuration\n - Resolution: Shared workaround to place character config in root folder and use specific CLI command\n\n3. **API Compatibility Clarification**\n - Helper: techcomthanh\n - Helpee: (implied other users)\n - Context: API compatibility issues\n - Resolution: Discovered that default agent works with OpenRouter but some features only work with real OpenAI key\n\n4. **Token Investment Perspective**\n - Helper: xell0x\n - Helpee: Crispy\n - Context: Discussion about ELI5 token value and timing of entry\n - Resolution: xell0x provided perspective on why current accumulation before v2 launch could be advantageous despite short-term price decline\n\n## Action Items\n\n### Technical\n- Ship ElizaOS v2 as the highest priority (mentioned by xell0x)\n- Consider maintaining ElizaOS v1 for existing forks while developing v2 (mentioned by Osint)\n- Fix issue with agents tweeting in loops (mentioned by techcomthanh)\n- Address warning \"User has no name or username, skipping\" in relationship creation (mentioned by techcomthanh)\n- Implement multi-repo aggregation for the news platform (mentioned by jin)\n- Develop agent RAG for the news platform (mentioned by jin)\n- Integrate Discord webhooks (mentioned by jin)\n- Continue testing governance tooling (mentioned by jin)\n\n### Documentation\n- Produce user guides/documentation after shipping v2 rather than delaying release (mentioned by xell0x)\n- Update docs regarding character configuration and CLI commands (mentioned by starlord)\n- Clarify API compatibility between OpenRouter and OpenAI (mentioned by techcomthanh)\n- Update documentation about plugin.ts and plugin development (mentioned by techcomthanh)\n- Document the deprecation of TWITTER_TARGET_USERS env variable (mentioned by techcomthanh)\n- Create comprehensive news site to complement regular updates (mentioned by jin)\n\n### Feature\n- Spotlight top auto.fun-born CTOs (like eli5 and eddy) to drive adoption (mentioned by xell0x)\n- ELI5 integration into Eliza v2 terminal - users will be able to directly interact with the ELI5 agent when opening the new Eliza 1.0.0 terminal (mentioned by xell0x)\n- Implement image generation capabilities or document the process (mentioned by tragicboyjay)" }, "ai_news_elizaos_daily_dev_json_2025-05-17": { "filename": "2025-05-17.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-17", "date": 1747440000, "stats": { "totalMessages": 15, "totalUsers": 11 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Analysis of 💬｜general Discord Channel\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. Issues mentioned include search functionality not working, a question about GPU deployment with comput3.ai, inquiry about Discord plugin capabilities for support tickets, and a question about contributing a custom plugin to the Eliza repository. One user provided information about Discord API capabilities for support ticket-like functionality using emoji reactions and automated threads. The conversation is sparse with limited technical depth or problem-solving.\n\n## 2. FAQ\nQ: Has anyone used comput3.ai to deploy GPUs? (asked by pytrex1) A: Unanswered\nQ: Does the Discord plugin have functionality to allow an agent to see, monitor, and respond to support tickets? (asked by Scooter) A: There's no pre-built support-ticket-object in the Discord API but it does support bots who monitor designated channels for emoji interactions that can trigger an automated private response thread. So it should be possible. (answered by Hidden Forces)\nQ: How do I contribute/add my plugin to the Eliza official repo? Do I have to create an npm package or just create a PR? (asked by Girinath) A: Unanswered\n\n## 3. Help Interactions\nHelper: Hidden Forces | Helpee: Scooter | Context: Inquiry about Discord plugin's capability to handle support tickets | Resolution: Explained that while there's no pre-built support ticket object in Discord API, bots can monitor channels for emoji reactions to trigger automated response threads\n\n## 4. Action Items\nTechnical: Search support functionality needs fixing | Description: \"ssearch support not working\" | Mentioned By: Fenil Modi\nTechnical: Contribute custom plugin to Eliza repository | Description: User created plugin by forking develop branch and needs guidance on contribution process | Mentioned By: Girinath\nDocumentation: Clarify plugin contribution process | Description: Documentation needed on whether npm package creation is required or if PR is sufficient | Mentioned By: Girinath", "messageCount": 6, "userCount": 6 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Analysis of Discord Chat in 🤖｜agent-dev-school\n\n## 1. Summary\nThe chat segment is very brief, containing only three messages from different users. There are no technical discussions, problem-solving activities, or decisions made in this segment. Two users are asking questions (one about finding dev school videos from Shaw, another about setting up a WhatsApp client plugin on version 0.25), and a third user made a one-word comment (\"seriously\"). No solutions or implementations were shared in this limited exchange.\n\n## 2. FAQ\nQ: Where can I find all dev school videos from Shaw? The last one on YouTube is more than a month ago. (asked by FedB00) A: Unanswered\nQ: Did anybody set up WhatsApp client plugin successfully on 0.25? (asked by mindxploit) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions occurred in this chat segment.\n\n## 4. Action Items\nDocumentation: Create or update documentation about where to find all dev school videos from Shaw | Mentioned By: FedB00\nDocumentation: Provide setup instructions for WhatsApp client plugin on version 0.25 | Mentioned By: mindxploit", "messageCount": 4, "userCount": 3 }, { "channelId": "1323745969115893780", "channelName": "📥｜pull-requests", "summary": "# Analysis of \"📥｜pull-requests\" Channel\n\n## 1. Summary\nThe chat segment shows a brief interaction about pull requests in the elizaOS/eliza repository. Jin shared PR #4586, which was later identified by cjft as having merge conflicts. Jin acknowledged the conflicts and committed to fixing them. Later, cjft shared another pull request (#4631), though no details were provided about its content. The conversation was minimal with no technical discussions or problem-solving beyond the identification of merge conflicts.\n\n## 2. FAQ\nQ: (No significant questions with meaningful responses were present in this chat segment)\n\n## 3. Help Interactions\nHelper: cjft | Helpee: jin | Context: Identifying merge conflicts in PR #4586 | Resolution: jin acknowledged and committed to fixing the conflicts\n\n## 4. Action Items\nTechnical: Fix merge conflicts in PR #4586 | Description: Resolve conflicts in the pull request | Mentioned By: jin", "messageCount": 5, "userCount": 3 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-17": { "filename": "2025-05-17.md", "content": "# elizaOS Development Discord - 2025-05-17\n\n## Overall Discussion Highlights\n\n### Development & Technical Issues\n- **Search Functionality Issues**: Search support was reported as not working by Fenil Modi in the general channel.\n- **Pull Request Management**: PR #4586 was identified as having merge conflicts, which Jin acknowledged and committed to fixing.\n- **Plugin Development**: Discussion about contributing custom plugins to the Eliza repository, with questions about the proper contribution process.\n\n### Integration & Deployment\n- **GPU Deployment**: A question was raised about using comput3.ai for GPU deployment, but remained unanswered.\n- **WhatsApp Integration**: A user inquired about setting up the WhatsApp client plugin on version 0.25, but received no responses.\n- **Discord Bot Capabilities**: Discussion about using Discord's API for support ticket-like functionality through emoji reactions and automated threads.\n\n## Key Questions & Answers\n\n**Q: Does the Discord plugin have functionality to allow an agent to see, monitor, and respond to support tickets?** \nA: There's no pre-built support-ticket-object in the Discord API, but it does support bots who monitor designated channels for emoji interactions that can trigger an automated private response thread. So it should be possible. (answered by Hidden Forces)\n\n## Community Help & Collaboration\n\n- **Discord Plugin Capabilities**: Hidden Forces helped Scooter understand Discord API capabilities for implementing support ticket-like functionality, explaining that while there's no pre-built support ticket object, bots can monitor channels for emoji reactions to trigger automated response threads.\n\n- **Pull Request Assistance**: cjft helped Jin by identifying merge conflicts in PR #4586, allowing Jin to address the issues promptly.\n\n## Action Items\n\n### Technical\n- Fix search support functionality (Mentioned by Fenil Modi)\n- Resolve merge conflicts in PR #4586 (Mentioned by Jin)\n- Provide guidance on contributing custom plugins to the Eliza repository (Mentioned by Girinath)\n\n### Documentation\n- Clarify plugin contribution process, including whether npm package creation is required or if PR is sufficient (Mentioned by Girinath)\n- Create or update documentation about where to find all dev school videos from Shaw (Mentioned by FedB00)\n- Provide setup instructions for WhatsApp client plugin on version 0.25 (Mentioned by mindxploit)" }, "ai_news_hyperfy_daily_json_2025-05-17": { "filename": "2025-05-17.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-17", "date": 1747440000, "stats": { "totalMessages": 77, "totalUsers": 18 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Channel Analysis: 💻│developers\n\n## 1. Summary\nThe discussion primarily revolves around Hyperfy v1 and v2, with users seeking clarification on their differences and compatibility. A key point is that v1 is in maintenance mode while v2 is actively developed as a complete rewrite with better performance. Users discussed world-building persistence issues, with v1's local SDK being closed source and limited to building apps rather than entire worlds. In contrast, v2 allows building entire worlds locally with persistent saves to world folders that can be published anywhere.\n\nTechnical topics included GLB animation implementation in both versions, with v2 supporting animations on armatures/bones (but not object-based animations) controlled via scripts. The Solana integration was mentioned with reference to the solana-v2 branch that provides wallet generation and RPC functionality. There was also brief discussion about TTS (Text-to-Speech) APIs, with recommendations for Groq and OpenAI's realtime agents for voice applications.\n\nUsers were advised against developing for v1 since most code would need rebuilding for v2, though v1 remains accessible with no set deprecation date out of respect for existing worlds.\n\n## 2. FAQ\nQ: How can I save my scene persistently in Hyperfy v1? (asked by carlosmu) A: v1 is in maintenance mode, its local SDK is closed source and was for building apps, not entire worlds. Highly recommend using v2. (answered by Ashxn)\nQ: Can I publish my local build to an online world in v1? (asked by carlosmu) A: In v2 you can build your entire world and it is saved to the world folder where you can publish and host anywhere. (answered by Ashxn)\nQ: Can I build in v2 editor and move my build to v1 world? (asked by carlosmu) A: v2 is a complete rewrite and they aren't compatible. (answered by Ashxn)\nQ: Can I enable animations on the GLBs I import? (asked by carlosmu) A: Engine currently supports animations on armatures/bones only, no object-based animations yet. (answered by Ashxn)\nQ: How do I control animations in v2? (asked by carlosmu) A: Controlled via script using methods like smesh.play(). (answered by Ashxn)\nQ: Can I use the same code for v1 and v2? (asked by carlosmu) A: No they are very different. V2 is a rebuild of the engine taking lessons from v1. (answered by maximus)\nQ: When v2 is released, will we be able to access v1 and v2? Or v1 will be disabled? (asked by carlosmu) A: V1 is kept alive out of respect for builders. No set date to remove v1 hosting but little appetite for v1 support/updates. (answered by maximus)\nQ: Will uvscroll with increments work? (asked by vox) A: Yes, just increment in larger numbers! (answered by Ashxn)\n\n## 3. Help Interactions\nHelper: Ashxn | Helpee: carlosmu | Context: User needed to understand how to save worlds persistently | Resolution: Explained v1 limitations and recommended v2 which saves to world folders\nHelper: Ashxn | Helpee: carlosmu | Context: User wanted to know how to enable GLB animations | Resolution: Provided code example showing how to control animations via script using smesh.play()\nHelper: Ashxn | Helpee: Agent12 | Context: User looking for Solana integration examples | Resolution: Directed to solana-v2 branch and documentation for wallet generation and RPC functionality\nHelper: maximus | Helpee: carlosmu | Context: User asking about v1 documentation and future availability | Resolution: Provided v1 documentation link and explained v1 will remain available but unsupported\nHelper: Ricky | Helpee: jin | Context: Seeking TTS API recommendations | Resolution: Suggested OpenAI's realtime agents with GitHub repo link and implementation insights\n\n## 4. Action Items\nType: Technical | Description: Explore Groq as an alternative to OpenAI for TTS applications | Mentioned By: ~/drdoge.eth\nType: Technical | Description: Investigate solana-v2 branch for SOL, wallet sign-in, and token gating integration | Mentioned By: Agent12\nType: Documentation | Description: Create documentation for enabling GLB animations in v1 | Mentioned By: carlosmu\nType: Documentation | Description: Provide migration guide from v1 to v2 | Mentioned By: carlosmu\nType: Feature | Description: Add support for object-based animations in addition to armature/bone animations | Mentioned By: Ashxn", "messageCount": 40, "userCount": 11 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat segment primarily discusses the feasibility of building games with Hyperfy v2. A user named Alexa inquires about creating a game similar to \"fallen\" despite not being a developer. Community members encourage her to start, citing \"fallen\" as proof it's possible, with vincentskele sharing personal success despite being a \"goofball.\" The conversation also touches on infrastructure, with 𝕽𝖔𝖚𝖘𝖙𝖆𝖓 mentioning switching to a dedicated GPU on fly.io to test performance and pricing. HypPrivakos provides updates on platform capabilities, confirming custom domain support is already available and that file import/export functionality is nearly complete, though limited to whole world folders rather than individual files. There's also brief discussion about AI agents and a tangential conversation about James Earl Jones' voice being used in AI applications.\n\n## 2. FAQ\nQ: Is it possible to build a world/game like \"fallen\" using hyperfy v2 as a non-developer? (asked by Alexa) A: Yes, it's possible with patience. \"fallen\" proves it's possible. (answered by vox and vincentskele)\nQ: Any plans for domain and file access? (asked by emotionull) A: Domain is already possible with some users having custom domains. File access for whole world folder import/export is nearly ready, just needs UI completion. (answered by HypPrivakos - HyperWorld.Host)\nQ: Where are we with our agents? (asked by MUDBONE) A: Unanswered\n\n## 3. Help Interactions\nHelper: vox | Helpee: Alexa | Context: Non-developer asking if they can build a game like \"fallen\" using Hyperfy v2 | Resolution: Encouraged to \"Just Start\" citing \"fallen\" as proof it's possible\nHelper: vincentskele | Helpee: Alexa | Context: Building a game in Hyperfy v2 without development experience | Resolution: Shared personal success story, confirming it's possible with patience\nHelper: HypPrivakos - HyperWorld.Host | Helpee: emotionull | Context: Inquiry about domain and file access capabilities | Resolution: Confirmed custom domains are already available and file import/export is nearly ready\n\n## 4. Action Items\nTechnical: Test dedicated single GPU with 2GB RAM on fly.io for user capacity and pricing | Mentioned By: 𝕽𝖔𝖚𝖘𝖙𝖆𝖓\nTechnical: Complete UI for world folder import/export functionality | Mentioned By: HypPrivakos - HyperWorld.Host\nFeature: Implement agent interaction capabilities (like \"degen sparty\") | Mentioned By: MUDBONE", "messageCount": 13, "userCount": 9 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "# Discord Chat Analysis for 🧊│3d-design Channel\n\n## 1. Summary:\nThe discussion primarily focused on VRM avatar positioning and animation issues in Hyperfy. TheMattEmpire discovered that the positioning of VRMs is based on the hip bone, causing alignment problems when avatars have different heights than default animations. Through testing, they found that the position is determined by the distance from the root to the hip bone, and adjusting these elements can fix ground alignment issues. Ashxn confirmed this approach, explaining that Hyperfy scales based on a hip-to-height ratio and only applies rotations, prioritizing a lightweight system. The conversation also addressed performance optimization, with Ashxn testing 300 unique meshes (600k triangles total) that performed well even on mobile devices. Vox identified common performance issues from previous experience, including unoptimized Sketchfab models with separated meshes sharing materials, high poly counts, non-indexed geometry, and full ARKit blendshape sets in VRMs. The group acknowledged that Hyperfy v2 offers better performance than v1, with preloading capabilities that reduce spawn lag.\n\n## 2. FAQ:\nQ: How is height position of the VRM actually set in Hyperfy? (asked by TheMattEmpire) A: Hyperfy scales based on a hip to height ratio, using a root bone for reference, and only applying rotations to ensure correct appearance even on short avatars. (answered by Ashxn)\nQ: What causes performance issues in Hyperfy worlds? (asked by Ashxn) A: Often unoptimized Sketchfab models with separated meshes sharing materials, high polycount, extensive use of large textures, non-indexed geometry with collision, and VRMs with full ARKit blendshape sets. (answered by vox)\n\n## 3. Help Interactions:\nHelper: TheMattEmpire | Helpee: Community | Context: VRM positioning issues in Hyperfy | Resolution: Discovered that adjusting the root bone position lower while maintaining correct hip bone position fixes ground alignment issues\nHelper: vox | Helpee: Community | Context: Performance optimization in Hyperfy worlds | Resolution: Shared insights on common performance bottlenecks from v1 experience and confirmed v2's improved performance\nHelper: Ashxn | Helpee: Community | Context: Testing performance limits with 300 unique meshes | Resolution: Demonstrated that even with 600k triangles and 300MB VRAM, performance remains acceptable on mobile devices, suggesting specific model attributes cause performance issues\n\n## 4. Action Items:\nTechnical: Test adding collision to meshes to evaluate performance impact | Mentioned By: vox\nTechnical: Investigate specific model attributes causing performance issues | Mentioned By: Ashxn\nFeature: Consider adding placeholder unoptimized mesh option like in v1 | Mentioned By: ᲼~/^b0gie-(.*)$/\nTechnical: Explore potential improvements to the VRM animation system while maintaining backward compatibility | Mentioned By: TheMattEmpire", "messageCount": 24, "userCount": 5 } ] } }, "ai_news_hyperfy_daily_md_2025-05-17": { "filename": "2025-05-17.md", "content": "# Hyperfy Discord - 2025-05-17\n\n## Overall Discussion Highlights\n\n### Hyperfy v1 vs v2 Development\n- **Version Status**: v1 is in maintenance mode while v2 is actively developed as a complete rewrite\n- **Compatibility**: v1 and v2 are not compatible; code cannot be shared between versions\n- **Future Plans**: v1 will remain accessible with no set deprecation date out of respect for existing worlds\n- **Development Recommendation**: Users are advised to focus on v2 as it offers better performance and features\n\n### Technical Capabilities\n- **World Building**: v2 allows building entire worlds locally with persistent saves to world folders\n- **Animation Support**: v2 supports animations on armatures/bones controlled via scripts, but not object-based animations yet\n- **Performance**: v2 demonstrated excellent performance with 300 unique meshes (600k triangles) even on mobile devices\n- **Infrastructure**: Testing of dedicated GPU on fly.io for improved performance and pricing evaluation\n\n### Platform Features\n- **Custom Domains**: Already available for users\n- **File Management**: Import/export functionality for whole world folders is nearly complete, pending UI finalization\n- **VRM Positioning**: Positioning is based on hip bone, with scaling based on hip-to-height ratio\n\n### Community Projects\n- Discussion about non-developers successfully building games in Hyperfy v2\n- \"fallen\" referenced as an example of what's possible for newcomers\n\n## Key Questions & Answers\n\n**Q: How can I save my scene persistently in Hyperfy?** \nA: v1's local SDK is closed source and limited to building apps. v2 saves to world folders where you can publish and host anywhere.\n\n**Q: Can I build in v2 editor and move my build to v1 world?** \nA: No, v2 is a complete rewrite and they aren't compatible.\n\n**Q: How do I enable and control animations on GLBs?** \nA: Engine supports animations on armatures/bones only. Control via script using methods like `smesh.play()`.\n\n**Q: When v2 is released, will v1 be disabled?** \nA: v1 will be kept alive out of respect for builders. No set date to remove v1 hosting but little appetite for v1 support/updates.\n\n**Q: Is it possible to build a world/game like \"fallen\" using hyperfy v2 as a non-developer?** \nA: Yes, it's possible with patience. \"fallen\" proves it's possible, and community members have shared success stories.\n\n**Q: How is height position of the VRM actually set in Hyperfy?** \nA: Hyperfy scales based on a hip to height ratio, using a root bone for reference, and only applying rotations to ensure correct appearance even on short avatars.\n\n**Q: What causes performance issues in Hyperfy worlds?** \nA: Often unoptimized Sketchfab models with separated meshes sharing materials, high polycount, extensive use of large textures, non-indexed geometry with collision, and VRMs with full ARKit blendshape sets.\n\n## Community Help & Collaboration\n\n- **VRM Positioning Solution**: TheMattEmpire discovered that adjusting the root bone position lower while maintaining correct hip bone position fixes ground alignment issues, sharing this knowledge with the community.\n\n- **Game Development Encouragement**: vox and vincentskele encouraged Alexa (a non-developer) to start building in Hyperfy v2, with vincentskele sharing their personal success story despite being a self-described \"goofball.\"\n\n- **Performance Optimization Insights**: vox shared detailed insights on common performance bottlenecks from v1 experience, helping others understand what to avoid when building worlds.\n\n- **Animation Implementation**: Ashxn provided code examples showing how to control animations via script using `smesh.play()` to help users implement animations in their worlds.\n\n- **Solana Integration Guidance**: Ashxn directed Agent12 to the solana-v2 branch and documentation for wallet generation and RPC functionality.\n\n## Action Items\n\n### Technical\n- Test dedicated single GPU with 2GB RAM on fly.io for user capacity and pricing (Mentioned by 𝕽𝖔𝖚𝖘𝖙𝖆𝖓)\n- Explore Groq as an alternative to OpenAI for TTS applications (Mentioned by ~/drdoge.eth)\n- Investigate solana-v2 branch for SOL, wallet sign-in, and token gating integration (Mentioned by Agent12)\n- Test adding collision to meshes to evaluate performance impact (Mentioned by vox)\n- Investigate specific model attributes causing performance issues (Mentioned by Ashxn)\n\n### Documentation\n- Create documentation for enabling GLB animations in v1 (Mentioned by carlosmu)\n- Provide migration guide from v1 to v2 (Mentioned by carlosmu)\n\n### Feature\n- Complete UI for world folder import/export functionality (Mentioned by HypPrivakos)\n- Implement agent interaction capabilities (like \"degen sparty\") (Mentioned by MUDBONE)\n- Add support for object-based animations in addition to armature/bone animations (Mentioned by Ashxn)\n- Consider adding placeholder unoptimized mesh option like in v1 (Mentioned by ᲼~/^b0gie-(.*)$/)\n- Explore potential improvements to the VRM animation system while maintaining backward compatibility (Mentioned by TheMattEmpire)" }, "github_summaries_daily_2025-05-18": { "filename": "2025-05-18.md", "content": "# ElizaOS Daily Update (May 18, 2025)\n\n## OVERVIEW \nToday, significant progress was made in enhancing the ElizaOS framework, particularly with the addition of new features and improvements to the Polygon plugin. Key developments include the implementation of a world selection feature in the message API and the integration of a gas oracle. Additionally, documentation updates and workflow fixes were addressed, contributing to overall project stability and usability.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Feature Enhancements\n- Added a missing plugin failure test to ensure robustness in plugin installation ([#4643](https://github.com/elizaos/eliza/pull/4643)).\n- Introduced an optional `worldId` query parameter for the message API, allowing for better memory tracking ([#4637](https://github.com/elizaos/eliza/pull/4637)).\n- Enhanced the API to return the ID of newly created agents, streamlining subsequent API calls ([#4634](https://github.com/elizaos/eliza/pull/4634)).\n\n### Plugin Development\n- Implemented the Polygon Gas Oracle Integration, which is crucial for gas estimation in transactions ([#4574](https://github.com/elizaos/eliza/pull/4574)).\n- Added the Polygon Plugin, which includes core EVM RPC wrappers and basic read operations ([#4635](https://github.com/elizaos/eliza/pull/4635)).\n- Merged the addpolygon resolution to finalize plugin integration ([#4636](https://github.com/elizaos/eliza/pull/4636)).\n\n### Documentation and Workflow Improvements\n- Updated project documentation comprehensively, including blog posts and partner documentation ([#4586](https://github.com/elizaos/eliza/pull/4586)).\n- Fixed the documentation deployment workflow to ensure proper npm caching and streamline deployment processes ([#4640](https://github.com/elizaos/eliza/pull/4640)).\n- Enhanced the ElizaOS CLI command for better character file handling and consistent behavior ([#4618](https://github.com/elizaos/eliza/pull/4618)).\n\n## CLOSED ISSUES\n\n### Documentation Updates\n- Closed the issue regarding the community section of the documentation, which involved gathering ideas for improvements ([#4260](https://github.com/elizaos/eliza/issues/4260)).\n\n## NEW ISSUES\n\n### Dependency Management\n- A new issue was raised concerning the need to publish to npm due to peer dependency conflicts with the zod library, which is affecting builds in other repositories ([#4562](https://github.com/elizaos/eliza/issues/4562))." }, "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