{ "date_generated_for": "2025-05-19", "ai_news_elizaos_discord_md_2025-05-18": { "filename": "2025-05-18.md", "content": "# elizaOS Discord - 2025-05-18\n\n## Overall Discussion Highlights\n\n### Eliza Version Clarification\n- **Version Naming**: What was previously called \"Eliza V2\" is now officially branded as \"Eliza 1.0.0\"\n- **Version Differences**: V1 was merely a proof of concept, while the upcoming 1.0.0 release represents the \"real\" Eliza with full capabilities\n- **Release Timeline**: Eliza 1.0.0 appears to be scheduled for release next week\n- **Documentation Concerns**: Users have requested more detailed documentation about what V2/1.0.0 will offer\n\n### Technical Development\n- **Active Development**: Shaw appears to be live coding during discussions, indicating ongoing development\n- **Twitter Integration Issues**: Multiple users reported problems with the Twitter plugin not automatically posting tweets\n- **Discord Connectivity**: Users encountered Opus-related errors when setting up Discord bots, with solutions found in GitHub issue #278\n- **Database Connectivity**: Several users experienced challenges with Supabase connectivity and adapter installation\n\n### Community & Governance\n- **Community Bots**: Discussion about integrating community-created bots like eli5 and eddy into the ecosystem\n- **THE COUNCIL**: Community members discussing tagline options for governance structure\n- **Asian Market Concerns**: Partners expressed that Asian community sentiment is negative, suggesting dedicated Asian community management\n- **Governance Mechanisms**: Council/clank tank governance structures appear to be in \"testnet\" phase without clear execution pathways\n\n### Tokenomics & Liquidity\n- **Liquidity Pools**: Discussions about a potential COM/AI16Z pool that was announced but details remain unclear\n- **Liquidity Strategy**: Debate between strengthening the existing COM/SOL pool ($328k liquidity) versus splitting liquidity across multiple pools\n- **Token Utility**: Questions raised about the bull case for holding AI16Z tokens, with responses focusing on governance participation and voting power\n\n## Key Questions & Answers\n\n**Q: Is elizaOS 1.0 same as Eliza v2?** \nA: No, they are different products (answered by Addison Casey)\n\n**Q: What's the difference between v2 and 1.0.0?** \nA: They're the same thing, just different naming conventions. \"v2\" is considered poor branding while \"1.0.0\" is better branding (answered by xell0x)\n\n**Q: How do I get my agent to automatically tweet without manual instructions?** \nA: The ENABLE_TWITTER_POST_GENERATION environment variable should be set to true, and the Twitter plugin must be in the character's plugin array (answered by 0xbisbis)\n\n**Q: How do I import a character in Eliza v2?** \nA: The command 'character' doesn't exist; refer to the documentation at https://eliza.how/docs/cli/agent (answered by starlord)\n\n**Q: What are the bull arguments for holding ai16z?** \nA: Participation in agentic governance, voting power on clank tank, influencing the council, new spartan shipping with v2, autofun/spartan/agents trading tokenomics, and being the most active open source crypto AI DAO (answered by jin)\n\n**Q: How can the team improve communication with the Asian community?** \nA: Create AI news in Chinese/Korean, establish dedicated social media accounts for Asian markets, and potentially hire someone to run ElizaOS Asia operations (answered by jin)\n\n## Community Help & Collaboration\n\n### Version Clarification\n- **Helper**: xell0x | **Helpee**: abhi_ironman \n Explained that \"eliza v2 is the upcoming eliza 1.0.0 main release\" while \"v1 was just a proof of concept\"\n\n### Liquidity Pool Strategy\n- **Helper**: osintmao9 | **Helpee**: alexius \n Explained DeFi liquidity concepts, suggesting it's better to build up one major pool (COM/SOL) before creating additional pools\n\n### Character Import Documentation\n- **Helper**: starlord | **Helpee**: 0xbisbis \n Provided link to correct documentation at https://eliza.how/docs/cli/agent explaining there's no 'character' command\n\n### Discord Plugin Troubleshooting\n- **Helper**: 0xbisbis | **Helpee**: 0xbisbis \n Found and implemented a fix from GitHub issue #278 for Discord plugin connection errors with Opus-related issues\n\n### Token Utility Explanation\n- **Helper**: jin | **Helpee**: waterisgood123 \n Provided specific utility points for AI16Z token including governance participation, voting power, and tokenomics\n\n## Action Items\n\n### Technical\n- Implement Eliza V2 (1.0.0) as the main release (Mentioned by: xell0x)\n- Fix Twitter plugin to enable automatic tweet generation without manual instructions (Mentioned by: 0xbisbis)\n- Resolve Supabase adapter installation issues (Mentioned by: 0xbisbis)\n- Implement client-twitter functionality from V1 in V2 to handle Twitter mentions (Mentioned by: 0xbisbis)\n- Create AI news content in Chinese and Korean languages (Mentioned by: jin)\n- Improve distribution of existing technical information to community (Mentioned by: Kenk)\n- Create a new channel for news (Mentioned by: jin)\n\n### Documentation\n- Create detailed documentation about what V2 will offer (Mentioned by: abhi_ironman)\n- Clarify the relationship between Eliza V1, V2, and ElizaOS (Mentioned by: abhi_ironman)\n- Create documentation on using plugins inside custom plugins (Mentioned by: starlord)\n- Provide clearer instructions for setting up Ollama with Eliza V2 (Mentioned by: Vanilla)\n- Create clear, layman-friendly explanation of ElizaOS thesis and roadmap (Mentioned by: waterisgood123)\n\n### Feature\n- Consider integrating community bots (eli5 and eddy) into the ecosystem (Mentioned by: xell0x)\n- Establish COM/AI16Z liquidity pool as announced (Mentioned by: alexius)\n- Add support for Twitter interactions beyond posting (like responding to mentions) (Mentioned by: 0xbisbis)\n- No-code agent behavior extension through plugins (Mentioned by: abhi_ironman)\n- Develop partner token allocation system for marketing campaigns on Autofun (Mentioned by: 辞尘鸽鸽)\n- Create mechanism for partners to use auto.fun LP trade fees for bounties (Mentioned by: yikesawjeez)\n- Establish dedicated ElizaOS social media accounts for Asian markets (Mentioned by: waterisgood123)\n- Hire dedicated staff to manage ElizaOS Asia operations (Mentioned by: waterisgood123)" }, "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_dev_md_2025-05-18": { "filename": "2025-05-18.md", "content": "# elizaOS Development Discord - 2025-05-18\n\n## Overall Discussion Highlights\n\n### Plugin Development & Extension\n- Discussions centered on extending existing plugins, particularly for Discord integration\n- Users experiencing issues with custom plugins being overwritten by standard ElizaCore plugins\n- Agent Joshua suggested importing plugins locally via `workspace:*` as a solution for extending existing plugins\n- Scooter shared code snippets showing how community manager agent retrieves Discord usernames from entity metadata\n\n### CI/CD & GitHub Workflows\n- Team actively addressing failing GitHub Actions workflows in the elizaOS/eliza repository\n- Debate about whether CI should run on PR or only on push to v2-dev\n- PR #4640 created and merged to fix workflow issues\n- Emphasis on testing PRs early to catch issues before they reach production\n\n### Agent Memory Management\n- Discussion about storing Discord usernames in ElizaOS agents\n- Questions about whether ElizaOS still uses components or relies on entity metadata\n- Challenges with getting agents to remember usernames through entity metadata storage alone\n\n### Future Development\n- Excitement about Codex for code review and generation\n- Plans for container support and internet access implementation\n- Exploration of UDP traffic handling for CVMs without dedicated IPs\n\n## Key Questions & Answers\n\n**Q: Shouldn't CI only try on push to v2-dev instead of PR?** \nA: PR testing catches issues early. Keep both. (answered by SpartanDev)\n\n**Q: How do I achieve the opposite and get the custom plugin to overwrite the discord plugin message handlers?** \nA: When I extend existing plugins, I pull the plugin code locally and make changes and import it via `workspace:*`. (answered by Agent Joshua)\n\n**Q: Has anyone here actually managed to extend an existing plugin?** \nA: When I extend existing plugins, I pull the plugin code locally and make changes and import it via `workspace:*`. (answered by Agent Joshua)\n\n## Community Help & Collaboration\n\n1. **Discord Plugin Extension Support**\n - Helper: Agent Joshua\n - Helpee: Scooter\n - Context: Extending existing plugins for Discord integration with custom message formatting\n - Resolution: Suggested pulling plugin code locally and importing via `workspace:*`, though the issue wasn't fully resolved\n\n2. **GitHub Actions Workflow Fix**\n - Helper: sayonara\n - Helpee: cjft\n - Context: Notifying about a failing GitHub Actions workflow\n - Resolution: cjft acknowledged the issue and committed to fixing it\n \n3. **Discord Bot Capabilities**\n - Helper: Hidden Forces\n - Helpee: Scooter\n - Context: Scooter asked about storing Discord usernames in ElizaOS\n - Resolution: Partial - Hidden Forces provided general Discord bot information and a Python code example, but didn't directly address the components question\n\n## Action Items\n\n### Technical\n- Fix failing GitHub Actions workflow (mentioned by cjft)\n- Merge PR #4640 and rerun actions (mentioned by cjft)\n- Investigate why custom Discord plugin message handlers are being overwritten by ElizaCore Discord plugin (mentioned by Scooter)\n- Investigate methods for persistent storage of Discord usernames in ElizaOS agents (mentioned by Scooter)\n- Explore workarounds for UDP traffic handling without dedicated IPs for CVMs (mentioned by Agent Joshua)\n- Clarify the `workspace:*` import method for extending plugins (mentioned by Scooter)\n\n### Documentation\n- Document how ElizaOS handles Discord user information persistence (mentioned by Scooter)\n- Clarify whether components are still used in current ElizaOS implementation (mentioned by Scooter)\n- Provide documentation on how to properly use workspace imports in package.json (mentioned by Scooter)\n\n### Feature\n- Implement deep research plugin with PRD (mentioned by sayonara)\n- Enable container support and internet access for Codex (mentioned by sayonara)" }, "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_daily_json_2025-05-18": { "filename": "2025-05-18.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-18", "categories": [ { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "The Council - AI Governance System", "text": "@dankvr introduced \"THE COUNCIL,\" a new AI governance system described as \"Consensus Oracle Units Network.\" The system features AI agents trained on organizational data (GitHub, Discord, X) representing different archetypes (users, builders, traders). @dankvr explained it provides structured feedback on proposals and daily progress, comparing it to \"infinite backrooms x jedi council x tv show.\" The project has open-source data pipelines already built, avatars created, and a 3D rendering pipeline via Playcanvas that can generate episodes in about 20 seconds. @dankvr is working on webhooks for community voting on discussion topics and plans to make it a weekly show, starting with elizaOS/ai16z and later Optimism. @shawmakesmagic retweeted this announcement and added that all data created in the elizaOS ecosystem will feed into these agents, which will be embodied in both 2D and 3D formats, with an interactive world in Hyperfy allowing real-time chat with the council. He emphasized this will \"completely reinvent what a DAO is\" with \"AI at the center, humans at the edges.\" Later, @shawmakesmagic elaborated that everything said in ElizaOS Discord, Telegram, tweets, and code feeds into AI-generated shows, stating \"We're going to reinvent what a DAO is from the inside out with data, workflows and agents.\"", "sources": [ "https://twitter.com/dankvr/status/1923913122236023094", "https://twitter.com/dankvr/status/1924225596927656146", "https://twitter.com/shawmakesmagic/status/1923918220349571216", "https://twitter.com/elizaOS/status/1923918220349571216", "https://twitter.com/dankvr/status/1924215633304051728", "https://twitter.com/shawmakesmagic/status/1924215633304051728", "https://twitter.com/dankvr/status/1924222014090310112", "https://twitter.com/shawmakesmagic/status/1924230033633399207", "https://twitter.com/dankvr/status/1920321451514618255", "https://twitter.com/shawmakesmagic/status/1924240192925544507" ], "images": [ "https://pbs.twimg.com/amplify_video_thumb/1923879375755218944/img/NV4xoq2vwdz8eGvz.jpg", "https://pbs.twimg.com/media/GrQ4Qh6XwAELkNN.jpg", "https://pbs.twimg.com/media/GrQwTiFXgAAhRFg.png", "https://pbs.twimg.com/media/GrQwUYPWAAA9-mT.jpg", "https://pbs.twimg.com/media/GrQxlggWkAAsZJ5.jpg", "https://pbs.twimg.com/media/GrQxnS8XMAAoNxO.jpg", "https://pbs.twimg.com/media/GrRFN0hWYAAHGyV.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1923879375755218944/vid/avc1/2560x1440/l_WlvjM-GNxv70OZ.mp4?tag=21" ] }, { "theme_title": "Open Source AI Tools and Development", "text": "@dankvr shared his work on open-source AI tools for community management, highlighting his Discord summarization AI prompts that provide \"daily actionable insights from your community.\" He offered help setting up the tool and mentioned potential flat fee support. @dankvr also retweeted @gdb's prediction that \"2025 is the year of agents.\" @shawmakesmagic asked his followers about open-source agent frameworks under active development besides Eliza, and later announced he's looking for a Python developer to create a Hyperfy agent starter kit with voice capabilities, world state management, action systems, and physics simulation. The goal is to enable anyone to build Hyperfy agents in Python using Langchain or raw Python for an upcoming agent PVP challenge. @shawmakesmagic clarified this would be a game to determine \"who builds the best agent in the world\" with prizes and a leaderboard. @elizaOS tweeted that \"Plugins go beyond integrations. They define how agents reason, recall, and act.\" @shawmakesmagic also mentioned that \"elizaOS 1.0 is coming out of beta soon\" and clarified there is no Eliza v2, calling such claims \"rumors and hearsay.\"", "sources": [ "https://twitter.com/dankvr/status/1924121890622202212", "https://twitter.com/dankvr/status/1917432629617369586", "https://twitter.com/dankvr/status/1924122773976141885", "https://twitter.com/gdb/status/1923541152508281329", "https://twitter.com/shawmakesmagic/status/1923926764985758019", "https://twitter.com/shawmakesmagic/status/1923944003612889354", "https://twitter.com/shawmakesmagic/status/1923950279223083427", "https://twitter.com/Web3WithMark/status/1923949795879813468", "https://twitter.com/elizaOS/status/1924172132130627720", "https://twitter.com/shawmakesmagic/status/1923942253325623417" ], "images": [], "videos": [] }, { "theme_title": "elizaOS Development and Integration", "text": "@0rdlibrary shared a post (retweeted by @shawmakesmagic) about entering dev mode with @elizaOS CLI and @hyperfy_io, noting \"The Ascii art Eliza hits diff in the terminal\" and mentioning bringing \"$Alice to life.\" @elizaOS made several cryptic posts including \"output held. no trigger needed,\" \"nothing lost in transit,\" and a sun emoji in response to a Chainlink post. @elizaOS also emphasized that \"Plugins go beyond integrations. They define how agents reason, recall, and act.\" @shawmakesmagic stated that \"The metaverse will be created by AI, full of AI stuff and populated by AI agents\" and later shared that he was doing some \"Sunday Chill Dev.\" He also clarified that \"v2 is dead. It's 1.0 now. elizaOS 1.0 is coming out of beta soon. There is no Eliza v2. Rumors and hearsay.\"", "sources": [ "https://twitter.com/0rdlibrary/status/1924197004156060066", "https://twitter.com/elizaOS/status/1924043031730442488", "https://twitter.com/elizaOS/status/1924087071892726070", "https://twitter.com/elizaOS/status/1924163550827700721", "https://twitter.com/chainlink/status/1924163073805582801", "https://twitter.com/elizaOS/status/1924172132130627720", "https://twitter.com/shawmakesmagic/status/1923937891224338936", "https://twitter.com/shawmakesmagic/status/1923942253325623417", "https://twitter.com/shawmakesmagic/status/1924186244122075440" ], "images": [ "https://pbs.twimg.com/media/GrQe7CLXEAAEWqD.jpg", "https://pbs.twimg.com/media/GrF08sOXcAAQQ3j.jpg" ], "videos": [] }, { "theme_title": "AI and DAOs Innovation", "text": "@dankvr shared his experience from \"6 years of DAOs\" and explained he's building something different for ai16z holders that's \"FUN for a project that launched on @DAOSdotFUN.\" He described features including automated news, game shows for investments/partnerships, and an AI council mimicking a board room, comparing it to \"Twitch plays DAOs.\" @dankvr referenced @VitalikButerin's post about \"humans as steering wheel and AI as the engine\" and explained how their FOSS data pipelines connect these steering wheels to existing platforms. @shawmakesmagic retweeted this and later expanded on the concept, stating that all organizational data feeds into AI-generated shows, emphasizing \"Data is the new oil\" and that they're \"going to reinvent what a DAO is from the inside out with data, workflows and agents\" as a template anyone can use.", "sources": [ "https://twitter.com/dankvr/status/1924215633304051728", "https://twitter.com/dankvr/status/1920321451514618255", "https://twitter.com/dankvr/status/1924222014090310112", "https://twitter.com/shawmakesmagic/status/1924215633304051728", "https://twitter.com/shawmakesmagic/status/1924230033633399207" ], "images": [ "https://pbs.twimg.com/media/GrQwTiFXgAAhRFg.png", "https://pbs.twimg.com/media/GrQwUYPWAAA9-mT.jpg", "https://pbs.twimg.com/media/GrQxlggWkAAsZJ5.jpg", "https://pbs.twimg.com/media/GrQxnS8XMAAoNxO.jpg" ], "videos": [] }, { "theme_title": "Miscellaneous Tech Observations", "text": "@shawmakesmagic made several observations about technology, noting \"You can hire a junior dev in a developing country for less than my cursor bill lol.\" He also commented on a post about tip.md, calling it a \"Cool idea\" for developers to receive crypto tips via markdown buttons on GitHub READMEs. @BenjaminDEKR's tweet questioning whether John Carmack cares about sleep scores was retweeted by @shawmakesmagic. @dankvr retweeted a post by @zzznah celebrating the 10th anniversary of DeepDream, an early application of neural networks for image generation. @shawmakesmagic also commented that \"The irony of the Marathon plagiarism scandal is that if they'd just used AI generated textures they never would have had any troubles.\"", "sources": [ "https://twitter.com/shawmakesmagic/status/1923900668802367650", "https://twitter.com/shawmakesmagic/status/1923959099034677630", "https://twitter.com/tipdotmd/status/1913624329692344723", "https://twitter.com/BenjaminDEKR/status/1923928631811752193", "https://twitter.com/personofswag/status/1923208772547178578", "https://twitter.com/zzznah/status/1924001981447786898", "https://twitter.com/KateVassGalerie/status/1920856648748298392", "https://twitter.com/shawmakesmagic/status/1924237568113262775" ], "images": [ "https://pbs.twimg.com/media/GrNtcEaWEAA0BgX.jpg" ], "videos": [] }, { "theme_title": "Social Media Experiments", "text": "@shawmakesmagic shared that he's trying out a service called \"superpeer.com\" which he described as \"a really cool product idea\" though he admitted he's \"Not exactly the best at responding to DMs.\" He initially joked about making \"an agent that responds to the paid DMs $$$\" but quickly clarified \"This is a joke guys 😅 They're definitely not going to let me do that after this post.\" He also made a cryptic post asking followers to \"comment below with your UUIDs that you don't want me to use\" with a reference link to all UUIDs.", "sources": [ "https://twitter.com/shawmakesmagic/status/1924162628928295232", "https://twitter.com/0xY10_/status/1924160915064181124", "https://twitter.com/shawmakesmagic/status/1924180691987959939", "https://twitter.com/shawmakesmagic/status/1924182104990212222", "https://twitter.com/shawmakesmagic/status/1924148734692376851" ], "images": [ "https://pbs.twimg.com/media/GrQRbI5W0AAcNap.jpg" ], "videos": [] } ], "topic": "twitter_activity" }, { "title": "Summary for completed_items", "content": [ { "text": "Several pull requests were recently completed in the elizaOS/eliza repository. These include addressing Issue 451 (PR #4575), updating documentation (PR #4586), and implementing a feature to return the ID of newly created agents in the API (PR #4634).", "sources": [ "https://github.com/elizaOS/eliza/pull/4575", "https://github.com/elizaOS/eliza/pull/4586", "https://github.com/elizaOS/eliza/pull/4634" ], "images": [], "videos": [] }, { "text": "CI/CD improvements were made with the implementation of an automatic documentation deployer (PR #4631) and a subsequent fix to the docs deployment workflow (PR #4640).", "sources": [ "https://github.com/elizaOS/eliza/pull/4631", "https://github.com/elizaOS/eliza/pull/4640" ], "images": [], "videos": [] }, { "text": "New features were added including a CLI command for development (PR #4618), a missing plugin failure test (PR #4643), and functionality to allow world selection in the message API (PR #4637).", "sources": [ "https://github.com/elizaOS/eliza/pull/4618", "https://github.com/elizaOS/eliza/pull/4643", "https://github.com/elizaOS/eliza/pull/4637" ], "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 #4635 by Samarthsinghal28 adds a Polygon Plugin, PR #4636 by HarshModi2005 merges an addpolygon resolution, and PR #4638 by wtfsayo introduces a deepsearch plugin (currently in draft status).", "sources": [ "https://github.com/elizaOS/eliza/pull/4635", "https://github.com/elizaOS/eliza/pull/4636", "https://github.com/elizaOS/eliza/pull/4638" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4635", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4636", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4638" ], "videos": [] } ], "topic": "pull_request" }, { "title": "Summary for github_summary", "content": [ { "text": "From May 18-19, 2025, the elizaos/eliza repository had 9 new pull requests with 8 of them merged. There were no new issues reported during this period. The repository had 13 active contributors working on it.", "sources": [ "githubStatsSummary" ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "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": 1747526400 } }, "ai_news_elizaos_daily_md_2025-05-18": { "filename": "2025-05-18.md", "content": "# Daily Report - 2025-05-18\n\n## Twitter Activity\n\n### The Council - AI Governance System\n- @dankvr introduced \"THE COUNCIL,\" a new AI governance system described as \"Consensus Oracle Units Network\"\n- The system features AI agents trained on organizational data (GitHub, Discord, X) representing different archetypes (users, builders, traders)\n- The project has open-source data pipelines already built, avatars created, and a 3D rendering pipeline via Playcanvas that can generate episodes in about 20 seconds\n- @dankvr is working on webhooks for community voting on discussion topics and plans to make it a weekly show, starting with elizaOS/ai16z and later Optimism\n- @shawmakesmagic added that all data created in the elizaOS ecosystem will feed into these agents, which will be embodied in both 2D and 3D formats\n- @shawmakesmagic emphasized this will \"completely reinvent what a DAO is\" with \"AI at the center, humans at the edges\"\n- Sources: https://twitter.com/dankvr/status/1923913122236023094, https://twitter.com/dankvr/status/1924225596927656146, https://twitter.com/shawmakesmagic/status/1923918220349571216, https://twitter.com/elizaOS/status/1923918220349571216, https://twitter.com/dankvr/status/1924215633304051728, https://twitter.com/shawmakesmagic/status/1924215633304051728, https://twitter.com/dankvr/status/1924222014090310112, https://twitter.com/shawmakesmagic/status/1924230033633399207, https://twitter.com/dankvr/status/1920321451514618255, https://twitter.com/shawmakesmagic/status/1924240192925544507\n\n### Open Source AI Tools and Development\n- @dankvr shared his work on open-source AI tools for community management, highlighting Discord summarization AI prompts\n- @dankvr offered help setting up the tool and mentioned potential flat fee support\n- @shawmakesmagic asked about open-source agent frameworks under active development besides Eliza\n- @shawmakesmagic announced he's looking for a Python developer to create a Hyperfy agent starter kit with voice capabilities\n- The goal is to enable anyone to build Hyperfy agents in Python using Langchain or raw Python for an upcoming agent PVP challenge\n- @elizaOS tweeted that \"Plugins go beyond integrations. They define how agents reason, recall, and act\"\n- @shawmakesmagic mentioned that \"elizaOS 1.0 is coming out of beta soon\"\n- Sources: https://twitter.com/dankvr/status/1924121890622202212, https://twitter.com/dankvr/status/1917432629617369586, https://twitter.com/dankvr/status/1924122773976141885, https://twitter.com/gdb/status/1923541152508281329, https://twitter.com/shawmakesmagic/status/1923926764985758019, https://twitter.com/shawmakesmagic/status/1923944003612889354, https://twitter.com/shawmakesmagic/status/1923950279223083427, https://twitter.com/Web3WithMark/status/1923949795879813468, https://twitter.com/elizaOS/status/1924172132130627720, https://twitter.com/shawmakesmagic/status/1923942253325623417\n\n### elizaOS Development and Integration\n- @0rdlibrary shared a post about entering dev mode with @elizaOS CLI and @hyperfy_io\n- @elizaOS made several posts including \"output held. no trigger needed,\" \"nothing lost in transit,\" and a sun emoji in response to a Chainlink post\n- @elizaOS emphasized that \"Plugins go beyond integrations. They define how agents reason, recall, and act\"\n- @shawmakesmagic stated that \"The metaverse will be created by AI, full of AI stuff and populated by AI agents\"\n- @shawmakesmagic shared that he was doing some \"Sunday Chill Dev\"\n- @shawmakesmagic clarified that \"v2 is dead. It's 1.0 now. elizaOS 1.0 is coming out of beta soon\"\n- Sources: https://twitter.com/0rdlibrary/status/1924197004156060066, https://twitter.com/elizaOS/status/1924043031730442488, https://twitter.com/elizaOS/status/1924087071892726070, https://twitter.com/elizaOS/status/1924163550827700721, https://twitter.com/chainlink/status/1924163073805582801, https://twitter.com/elizaOS/status/1924172132130627720, https://twitter.com/shawmakesmagic/status/1923937891224338936, https://twitter.com/shawmakesmagic/status/1923942253325623417, https://twitter.com/shawmakesmagic/status/1924186244122075440\n\n### AI and DAOs Innovation\n- @dankvr shared his experience from \"6 years of DAOs\" and explained he's building something different for ai16z holders\n- He described features including automated news, game shows for investments/partnerships, and an AI council mimicking a board room\n- @dankvr referenced @VitalikButerin's post about \"humans as steering wheel and AI as the engine\"\n- @shawmakesmagic expanded on the concept, stating that all organizational data feeds into AI-generated shows\n- @shawmakesmagic emphasized \"Data is the new oil\" and that they're \"going to reinvent what a DAO is from the inside out with data, workflows and agents\"\n- Sources: https://twitter.com/dankvr/status/1924215633304051728, https://twitter.com/dankvr/status/1920321451514618255, https://twitter.com/dankvr/status/1924222014090310112, https://twitter.com/shawmakesmagic/status/1924215633304051728, https://twitter.com/shawmakesmagic/status/1924230033633399207\n\n### Miscellaneous Tech Observations\n- @shawmakesmagic noted \"You can hire a junior dev in a developing country for less than my cursor bill lol\"\n- @shawmakesmagic commented on tip.md, calling it a \"Cool idea\" for developers to receive crypto tips via markdown buttons on GitHub READMEs\n- @BenjaminDEKR's tweet questioning whether John Carmack cares about sleep scores was retweeted by @shawmakesmagic\n- @dankvr retweeted a post by @zzznah celebrating the 10th anniversary of DeepDream\n- @shawmakesmagic commented on the Marathon plagiarism scandal, noting they could have avoided issues by using AI-generated textures\n- Sources: https://twitter.com/shawmakesmagic/status/1923900668802367650, https://twitter.com/shawmakesmagic/status/1923959099034677630, https://twitter.com/tipdotmd/status/1913624329692344723, https://twitter.com/BenjaminDEKR/status/1923928631811752193, https://twitter.com/personofswag/status/1923208772547178578, https://twitter.com/zzznah/status/1924001981447786898, https://twitter.com/KateVassGalerie/status/1920856648748298392, https://twitter.com/shawmakesmagic/status/1924237568113262775\n\n### Social Media Experiments\n- @shawmakesmagic shared that he's trying out a service called \"superpeer.com\" which he described as \"a really cool product idea\"\n- He initially joked about making \"an agent that responds to the paid DMs $$$\" but quickly clarified it was a joke\n- @shawmakesmagic made a cryptic post asking followers to \"comment below with your UUIDs that you don't want me to use\"\n- Sources: https://twitter.com/shawmakesmagic/status/1924162628928295232, https://twitter.com/0xY10_/status/1924160915064181124, https://twitter.com/shawmakesmagic/status/1924180691987959939, https://twitter.com/shawmakesmagic/status/1924182104990212222, https://twitter.com/shawmakesmagic/status/1924148734692376851\n\n## Completed Items\n- Several pull requests were completed in the elizaOS/eliza repository, including addressing Issue 451 (PR #4575), updating documentation (PR #4586), and implementing a feature to return the ID of newly created agents in the API (PR #4634)\n- CI/CD improvements were made with the implementation of an automatic documentation deployer (PR #4631) and a subsequent fix to the docs deployment workflow (PR #4640)\n- New features were added including a CLI command for development (PR #4618), a missing plugin failure test (PR #4643), and functionality to allow world selection in the message API (PR #4637)\n- Sources: https://github.com/elizaOS/eliza/pull/4575, https://github.com/elizaOS/eliza/pull/4586, https://github.com/elizaOS/eliza/pull/4634, https://github.com/elizaOS/eliza/pull/4631, https://github.com/elizaOS/eliza/pull/4640, https://github.com/elizaOS/eliza/pull/4618, https://github.com/elizaOS/eliza/pull/4643, https://github.com/elizaOS/eliza/pull/4637\n\n## GitHub Activity for elizaOS/eliza\n- Three pull requests have been submitted: PR #4635 by Samarthsinghal28 adds a Polygon Plugin, PR #4636 by HarshModi2005 merges an addpolygon resolution, and PR #4638 by wtfsayo introduces a deepsearch plugin (currently in draft status)\n- Sources: https://github.com/elizaOS/eliza/pull/4635, https://github.com/elizaOS/eliza/pull/4636, https://github.com/elizaOS/eliza/pull/4638\n\n## GitHub Summary\n- From May 18-19, 2025, the elizaos/eliza repository had 9 new pull requests with 8 of them merged\n- There were no new issues reported during this period\n- The repository had 13 active contributors working on it\n- Sources: githubStatsSummary\n\n## Misceleanous\n- The source provides information about the top contributors for the elizaOS/eliza GitHub repository" }, "ai_news_elizaos_daily_discord_json_2025-05-18": { "filename": "2025-05-18.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-18", "date": 1747526400, "stats": { "totalMessages": 371, "totalUsers": 36 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Channel \"discussion\" Analysis\n\n## 1. Summary\nThe discussion primarily revolves around Eliza's development roadmap, particularly the relationship between Eliza V1, V2, and ElizaOS. Users are seeking clarification on version differences, with xell0x explaining that V1 was a proof of concept while V2 (referred to as Eliza 1.0.0) is the upcoming main release with \"the sauce.\" There's significant discussion about liquidity pools, specifically regarding a potential COM/AI16Z pool that was announced but details remain unclear. osintmao9 shares insights on DeFi liquidity strategy, suggesting it might be better to strengthen the existing COM/SOL pool ($328k liquidity) rather than splitting liquidity across multiple pools. Community members also discuss \"THE COUNCIL\" tagline options and the potential roles of community-created bots like eli5 and eddy in the ecosystem. Shaw appears to be live coding, suggesting active development is ongoing.\n\n## 2. FAQ\nQ: Is elizaOS 1.0 same as Eliza v2? (asked by abhi_ironman) A: No (answered by !Addison Casey!)\nQ: When will our boy eli5 join the council or the org? (asked by xell0x) A: Unanswered\nQ: How is auto.fun supposed to succeed if the community cookings like eli5 and eddy don't get spotlighted? (asked by xell0x) A: Unanswered\nQ: Will there be an LP Pool for COM/AI16Z and when will this happen? (asked by alexius) A: Unanswered\nQ: Do we have detailed article/doc on what v2 going to offer? (asked by abhi_ironman) A: Unanswered\nQ: How is v2 going? (asked by xell0x) A: Unanswered\n\n## 3. Help Interactions\nHelper: xell0x | Helpee: abhi_ironman | Context: Clarifying the relationship between Eliza versions | Resolution: Explained that \"eliza v2 is the upcoming eliza 1.0.0 main release\" while \"v1 was just a proof of concept\"\nHelper: osintmao9 | Helpee: alexius | Context: Understanding liquidity pool strategy | Resolution: Explained DeFi liquidity concepts, suggesting it's better to build up one major pool (COM/SOL) before creating additional pools\nHelper: Spyros | Helpee: alexius | Context: Explaining liquidity pool approaches | Resolution: Provided perspective on benefits of 2-tiered LP pool approach for routing through auto.fun\n\n## 4. Action Items\nTechnical: Implement Eliza V2 (1.0.0) as the main release | Mentioned By: xell0x\nTechnical: Create a new channel for news | Mentioned By: jin\nFeature: Consider integrating community bots (eli5 and eddy) into the ecosystem | Mentioned By: xell0x\nFeature: Establish COM/AI16Z liquidity pool as announced | Mentioned By: alexius\nDocumentation: Create detailed documentation about what V2 will offer | Mentioned By: abhi_ironman\nDocumentation: Clarify the relationship between Eliza V1, V2, and ElizaOS | Mentioned By: abhi_ironman", "messageCount": 109, "userCount": 17 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around users trying to set up and troubleshoot Eliza agents, particularly for Twitter integration and Discord connectivity. Several users encountered issues with the Twitter plugin not automatically posting tweets, requiring manual instructions instead. There were also challenges with Ollama integration, Supabase connectivity, and Discord bot setup. Users shared environment configurations, error messages, and screenshots while seeking help. A key technical discussion involved the difference between the eliza-starter repository and the main Eliza repository regarding automatic tweet generation. Users also discussed character imports in v2, database connectivity issues, and plugin installation problems. By the end of the chat, at least one user successfully configured their agent with RAG functionality and resolved Discord connection issues related to Opus errors by following a GitHub issue solution.\n\n## 2. FAQ:\nQ: How do I get my agent to automatically tweet without manual instructions? (asked by [elizaos] <0xbisbis>) A: The ENABLE_TWITTER_POST_GENERATION environment variable should be set to true, and the Twitter plugin must be in the character's plugin array (answered by [elizaos] <0xbisbis>)\nQ: How do I import a character in Eliza v2? (asked by [elizaos] <0xbisbis>) A: The command 'character' doesn't exist; refer to the documentation at https://eliza.how/docs/cli/agent (answered by starlord)\nQ: Is it possible to use client-twitter from V1 in V2 to respond when mentioned on Twitter? (asked by [elizaos] <0xbisbis>) A: Unanswered\nQ: What's the best solution to hydrate a Twitter account to prevent it from being flagged as spam? (asked by [elizaos] <0xbisbis>) A: Unanswered\nQ: How does one use other plugins inside custom plugins? (asked by starlord) A: Unanswered\nQ: Is the Supabase adapter deprecated? (asked by [elizaos] <0xbisbis>) A: Unanswered\nQ: How do I create a world and get world ID from API perspective? (asked by [elizaos] <0xbisbis>) A: Unanswered\n\n## 3. Help Interactions:\nHelper: starlord | Helpee: [elizaos] <0xbisbis> | Context: User was trying to import a character with incorrect command syntax | Resolution: Provided link to correct documentation at https://eliza.how/docs/cli/agent explaining there's no 'character' command\nHelper: [elizaos] <0xbisbis> | Helpee: [elizaos] <0xbisbis> | Context: Discord plugin connection error with Opus-related issues | Resolution: User found and implemented a fix from GitHub issue #278\n\n## 4. Action Items:\nType: Technical | Description: Fix Twitter plugin to enable automatic tweet generation without manual instructions | Mentioned By: [elizaos] <0xbisbis>\nType: Technical | Description: Resolve Supabase adapter installation issues | Mentioned By: [elizaos] <0xbisbis>\nType: Technical | Description: Implement client-twitter functionality from V1 in V2 to handle Twitter mentions | Mentioned By: [elizaos] <0xbisbis>\nType: Documentation | Description: Create documentation on using plugins inside custom plugins | Mentioned By: starlord\nType: Documentation | Description: Provide clearer instructions for setting up Ollama with Eliza V2 | Mentioned By: Vanilla\nType: Feature | Description: Add support for Twitter interactions beyond posting (like responding to mentions) | Mentioned By: [elizaos] <0xbisbis>", "messageCount": 63, "userCount": 5 }, { "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 segment primarily discusses Eliza's upcoming release, with confusion around version naming conventions. Users clarify that what was previously referred to as \"v2\" is actually being branded as \"Eliza 1.0.0\". The discussion indicates that the current version (referred to as v1) was merely a proof of concept, while the upcoming release (1.0.0/v2) represents the \"real\" Eliza that will be more powerful and relevant to the space. There's also a brief mention of \"Autofun\" not having a successful launch, with a suggestion that it needs new features, particularly no-code agent behavior extensions through plugins. The release timeframe for Eliza 1.0.0 appears to be the following week.\n\n## 2. FAQ\nQ: Any update on this? (asked by frank_grimes_sr) A: Unanswered\nQ: What's the difference between v2 and 1.0.0? (asked by traderlv) A: They're the same thing, just different names (answered by traderlv)\nQ: Why is the branding changing? (asked by Nick dask) A: \"v2\" is horrible branding and \"1.0.0\" is much better branding (answered by xell0x)\nQ: When is the real Eliza release coming? (asked by xell0x) A: Next week it seems (answered by xell0x)\n\n## 3. Help Interactions\nHelper: xell0x | Helpee: Nick dask | Context: Confusion about Eliza version naming | Resolution: Explained that v1 was just a proof of concept, while the upcoming release (called both v2 and 1.0.0) is the \"real\" powerful Eliza release\n\n## 4. Action Items\nFeature: No-code agent behavior extension through plugins | Description: New features needed for Autofun platform from agentic perspective | Mentioned By: abhi_ironman\nTechnical: Release of Eliza 1.0.0 (previously called v2) | Description: Launch of the first full version of Eliza | Mentioned By: xell0x", "messageCount": 14, "userCount": 8 }, { "channelId": "1301363808421543988", "channelName": "🥇-partners", "summary": "# Analysis of 🥇-partners Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around community frustration with the ElizaOS project's progress, communication, and direction. Several key issues emerge:\n\n- Partners express concern about delayed product releases (V2 framework, launchpad) and lack of clear roadmap/tokenomics\n- Communication gaps between the team and community are highlighted, particularly regarding technical progress and value proposition\n- Asian market sentiment is notably negative, with users suggesting the team needs dedicated Asian community management\n- Team members (Kenk, jin) defend the project's progress, pointing to extensive documentation and ongoing development\n- Discussion of potential solutions includes improving communication channels, creating localized content for Asian markets, and implementing partner incentives\n- Technical governance mechanisms (council/clank tank) are mentioned but appear to lack clear execution pathways\n- Partners suggest implementing reward systems and campaigns to drive engagement and token utility\n\nThe conversation reveals a disconnect between the team's perception of progress and the community's understanding, with particular emphasis on the need for better outreach to Asian markets where many token holders reside.\n\n## 2. FAQ\nQ: What are the bull arguments for holding ai16z? (asked by waterisgood123) A: Participation in agentic governance, voting power on clank tank, influencing the council, new spartan shipping with v2, autofun/spartan/agents trading tokenomics, and being the most active open source crypto AI DAO (answered by jin)\nQ: What is the current state of V2 development? (asked by waterisgood123) A: V2 is in beta with dozens of builders working with it, with no complaints from those testing it (answered by Kenk)\nQ: How can the team improve communication with the Asian community? (asked by waterisgood123) A: Create AI news in Chinese/Korean, establish dedicated social media accounts for Asian markets, and potentially hire someone to run ElizaOS Asia operations (answered by jin)\nQ: Does council/clank tank actually make governance or funding decisions? (asked by yikesawjeez) A: It's currently in a \"testnet\" phase for agentic governance (answered by jin)\nQ: How can partners contribute to the ecosystem? (asked by yikesawjeez) A: Technical users can test V2 with Spartan/investment manager, which leads to ways non-technical people can participate (answered by jin)\n\n## 3. Help Interactions\nHelper: jin | Helpee: waterisgood123 | Context: Requesting bull case for holding ai16z token | Resolution: Jin provided specific utility points including governance participation, voting power, and tokenomics\nHelper: jin | Helpee: 辞尘鸽鸽 | Context: Discussing how to improve Asian community engagement | Resolution: Jin proposed creating AI news in Chinese and establishing dedicated channels\nHelper: yikesawjeez | Helpee: Multiple partners | Context: Explaining governance participation challenges | Resolution: Suggested implementing clearer execution pathways for governance decisions\nHelper: Kenk | Helpee: waterisgood123 | Context: Questions about project progress and documentation | Resolution: Directed to extensive documentation in Knowledge folder and #announcements channel\n\n## 4. Action Items\nType: Technical | Description: Create AI news content in Chinese and Korean languages | Mentioned By: jin\nType: Technical | Description: Implement V2 framework with Spartan integration | Mentioned By: jin\nType: Feature | Description: Develop partner token allocation system for marketing campaigns on Autofun | Mentioned By: 辞尘鸽鸽\nType: Feature | Description: Create mechanism for partners to use auto.fun LP trade fees for bounties | Mentioned By: yikesawjeez\nType: Documentation | Description: Create clear, layman-friendly explanation of ElizaOS thesis and roadmap | Mentioned By: waterisgood123\nType: Feature | Description: Establish dedicated ElizaOS social media accounts for Asian markets | Mentioned By: waterisgood123\nType: Technical | Description: Improve distribution of existing technical information to community | Mentioned By: Kenk\nType: Feature | Description: Hire dedicated staff to manage ElizaOS Asia operations | Mentioned By: waterisgood123", "messageCount": 184, "userCount": 10 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-18": { "filename": "2025-05-18.md", "content": "# elizaOS Discord - 2025-05-18\n\n## Overall Discussion Highlights\n\n### Eliza Version Clarification\n- **Version Naming**: What was previously called \"Eliza V2\" is now officially branded as \"Eliza 1.0.0\"\n- **Version Differences**: V1 was merely a proof of concept, while the upcoming 1.0.0 release represents the \"real\" Eliza with full capabilities\n- **Release Timeline**: Eliza 1.0.0 appears to be scheduled for release next week\n- **Documentation Concerns**: Users have requested more detailed documentation about what V2/1.0.0 will offer\n\n### Technical Development\n- **Active Development**: Shaw appears to be live coding during discussions, indicating ongoing development\n- **Twitter Integration Issues**: Multiple users reported problems with the Twitter plugin not automatically posting tweets\n- **Discord Connectivity**: Users encountered Opus-related errors when setting up Discord bots, with solutions found in GitHub issue #278\n- **Database Connectivity**: Several users experienced challenges with Supabase connectivity and adapter installation\n\n### Community & Governance\n- **Community Bots**: Discussion about integrating community-created bots like eli5 and eddy into the ecosystem\n- **THE COUNCIL**: Community members discussing tagline options for governance structure\n- **Asian Market Concerns**: Partners expressed that Asian community sentiment is negative, suggesting dedicated Asian community management\n- **Governance Mechanisms**: Council/clank tank governance structures appear to be in \"testnet\" phase without clear execution pathways\n\n### Tokenomics & Liquidity\n- **Liquidity Pools**: Discussions about a potential COM/AI16Z pool that was announced but details remain unclear\n- **Liquidity Strategy**: Debate between strengthening the existing COM/SOL pool ($328k liquidity) versus splitting liquidity across multiple pools\n- **Token Utility**: Questions raised about the bull case for holding AI16Z tokens, with responses focusing on governance participation and voting power\n\n## Key Questions & Answers\n\n**Q: Is elizaOS 1.0 same as Eliza v2?** \nA: No, they are different products (answered by Addison Casey)\n\n**Q: What's the difference between v2 and 1.0.0?** \nA: They're the same thing, just different naming conventions. \"v2\" is considered poor branding while \"1.0.0\" is better branding (answered by xell0x)\n\n**Q: How do I get my agent to automatically tweet without manual instructions?** \nA: The ENABLE_TWITTER_POST_GENERATION environment variable should be set to true, and the Twitter plugin must be in the character's plugin array (answered by 0xbisbis)\n\n**Q: How do I import a character in Eliza v2?** \nA: The command 'character' doesn't exist; refer to the documentation at https://eliza.how/docs/cli/agent (answered by starlord)\n\n**Q: What are the bull arguments for holding ai16z?** \nA: Participation in agentic governance, voting power on clank tank, influencing the council, new spartan shipping with v2, autofun/spartan/agents trading tokenomics, and being the most active open source crypto AI DAO (answered by jin)\n\n**Q: How can the team improve communication with the Asian community?** \nA: Create AI news in Chinese/Korean, establish dedicated social media accounts for Asian markets, and potentially hire someone to run ElizaOS Asia operations (answered by jin)\n\n## Community Help & Collaboration\n\n### Version Clarification\n- **Helper**: xell0x | **Helpee**: abhi_ironman \n Explained that \"eliza v2 is the upcoming eliza 1.0.0 main release\" while \"v1 was just a proof of concept\"\n\n### Liquidity Pool Strategy\n- **Helper**: osintmao9 | **Helpee**: alexius \n Explained DeFi liquidity concepts, suggesting it's better to build up one major pool (COM/SOL) before creating additional pools\n\n### Character Import Documentation\n- **Helper**: starlord | **Helpee**: 0xbisbis \n Provided link to correct documentation at https://eliza.how/docs/cli/agent explaining there's no 'character' command\n\n### Discord Plugin Troubleshooting\n- **Helper**: 0xbisbis | **Helpee**: 0xbisbis \n Found and implemented a fix from GitHub issue #278 for Discord plugin connection errors with Opus-related issues\n\n### Token Utility Explanation\n- **Helper**: jin | **Helpee**: waterisgood123 \n Provided specific utility points for AI16Z token including governance participation, voting power, and tokenomics\n\n## Action Items\n\n### Technical\n- Implement Eliza V2 (1.0.0) as the main release (Mentioned by: xell0x)\n- Fix Twitter plugin to enable automatic tweet generation without manual instructions (Mentioned by: 0xbisbis)\n- Resolve Supabase adapter installation issues (Mentioned by: 0xbisbis)\n- Implement client-twitter functionality from V1 in V2 to handle Twitter mentions (Mentioned by: 0xbisbis)\n- Create AI news content in Chinese and Korean languages (Mentioned by: jin)\n- Improve distribution of existing technical information to community (Mentioned by: Kenk)\n- Create a new channel for news (Mentioned by: jin)\n\n### Documentation\n- Create detailed documentation about what V2 will offer (Mentioned by: abhi_ironman)\n- Clarify the relationship between Eliza V1, V2, and ElizaOS (Mentioned by: abhi_ironman)\n- Create documentation on using plugins inside custom plugins (Mentioned by: starlord)\n- Provide clearer instructions for setting up Ollama with Eliza V2 (Mentioned by: Vanilla)\n- Create clear, layman-friendly explanation of ElizaOS thesis and roadmap (Mentioned by: waterisgood123)\n\n### Feature\n- Consider integrating community bots (eli5 and eddy) into the ecosystem (Mentioned by: xell0x)\n- Establish COM/AI16Z liquidity pool as announced (Mentioned by: alexius)\n- Add support for Twitter interactions beyond posting (like responding to mentions) (Mentioned by: 0xbisbis)\n- No-code agent behavior extension through plugins (Mentioned by: abhi_ironman)\n- Develop partner token allocation system for marketing campaigns on Autofun (Mentioned by: 辞尘鸽鸽)\n- Create mechanism for partners to use auto.fun LP trade fees for bounties (Mentioned by: yikesawjeez)\n- Establish dedicated ElizaOS social media accounts for Asian markets (Mentioned by: waterisgood123)\n- Hire dedicated staff to manage ElizaOS Asia operations (Mentioned by: waterisgood123)" }, "ai_news_elizaos_daily_dev_json_2025-05-18": { "filename": "2025-05-18.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-18", "date": 1747526400, "stats": { "totalMessages": 51, "totalUsers": 11 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Analysis of Discord Chat in 💬｜general\n\n## 1. Summary:\nThe chat segment contains limited technical discussion focused on agent memory management in ElizOS, particularly regarding storing Discord usernames. A user named Scooter inquired about whether ElizOS still uses components and shared code snippets showing how the community manager agent retrieves Discord usernames from entity metadata. They expressed difficulty getting agents to remember usernames through entity metadata storage alone. Another user, Hidden Forces, provided information about Discord's bot capabilities and shared a Python code example for creating support tickets via reactions, though this wasn't directly addressing Scooter's original question. The chat also contained some unrelated messages including a content writer offering services and a greeting from a new member.\n\n## 2. FAQ:\nQ: Does eliza still use components? Looking at the org agents code doesn't look like they are being used? (asked by Scooter) A: Unanswered\nQ: Can we also store discord usernames to components? (asked by Scooter) A: Unanswered\n\n## 3. Help Interactions:\nHelper: Hidden Forces | Helpee: Scooter | Context: Scooter asked about storing Discord usernames in ElizOS | Resolution: Partial - Hidden Forces provided general Discord bot information and a Python code example, but didn't directly address the components question\n\n## 4. Action Items:\nTechnical: Investigate methods for persistent storage of Discord usernames in ElizOS agents | Description: Determine whether components or entity metadata is more appropriate for username storage | Mentioned By: Scooter\nDocumentation: Document how ElizOS handles Discord user information persistence | Description: Clarify whether components are still used in current ElizOS implementation | Mentioned By: Scooter", "messageCount": 10, "userCount": 5 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion centers around extending and customizing plugins in an agent development environment, particularly focusing on Discord integration. Scooter is experiencing issues with their custom plugin that extends the Discord service, where message handlers from their custom implementation are being overwritten by the standard ElizaCore Discord plugin. They specifically want to format responses as public mentions with user IDs. Agent Joshua suggests importing plugins locally via `workspace:*` as a potential solution for extending existing plugins. The conversation also briefly touches on UDP traffic handling for CVMs (likely Conversational Virtual Machines), with Agent Joshua mentioning they're exploring workarounds for the current limitation of not having dedicated IPs for each CVM.\n\n## 2. FAQ\nQ: Does anyone know if the character profile plugin array plugins are loaded after the custom plugin in the initialization and export project section? (asked by Scooter) A: Unanswered\nQ: How do I achieve the opposite and get the custom plugin to overwrite the discord plugin message handlers? (asked by Scooter) A: When I extend existing plugins, I pull the plugin code locally and make changes and import it via `workspace:*`. (answered by Agent Joshua ₱ | TEE)\nQ: Has anyone here actually managed to extend an existing plugin? (asked by Scooter) A: When I extend existing plugins, I pull the plugin code locally and make changes and import it via `workspace:*`. (answered by Agent Joshua ₱ | TEE)\nQ: When you say import via workspace are you referring to what needs to be in the package.json? (asked by Scooter) A: Unanswered\n\n## 3. Help Interactions\nHelper: Agent Joshua ₱ | TEE | Helpee: Scooter | Context: Extending existing plugins for Discord integration with custom message formatting | Resolution: Suggested pulling plugin code locally and importing via `workspace:*`, though the issue wasn't fully resolved by the end of the conversation.\n\n## 4. Action Items\nTechnical: Investigate why custom Discord plugin message handlers are being overwritten by ElizaCore Discord plugin | Description: Debug plugin loading order and message handler registration | Mentioned By: Scooter\nTechnical: Explore workarounds for UDP traffic handling without dedicated IPs for CVMs | Description: Find alternative methods to support UDP traffic for CVMs | Mentioned By: Agent Joshua ₱ | TEE\nTechnical: Clarify the `workspace:*` import method for extending plugins | Description: Provide documentation on how to properly use workspace imports in package.json | Mentioned By: Scooter", "messageCount": 17, "userCount": 3 }, { "channelId": "1323745969115893780", "channelName": "📥｜pull-requests", "summary": "# Analysis of \"📥｜pull-requests\" Discord Channel\n\n## 1. Summary\nThe conversation revolves around GitHub Actions workflows and pull requests for the elizaOS/eliza repository. Team members are discussing CI/CD pipeline issues, particularly focusing on a failing workflow run. There's emphasis on the importance of testing PRs early to catch issues before they reach production. A key discussion point is the use of Codex for code review and generation, with excitement about future capabilities once container support and internet access are implemented. The team is actively fixing workflow failures, with cjft taking responsibility for addressing a specific failure and creating PR #4640 to resolve it. The channel shows a collaborative environment where team members notify each other about failing workflows and coordinate fixes.\n\n## 2. FAQ\nQ: Shouldn't CI only try on push to v2-dev instead of PR? (asked by sayonara) A: PR testing catches issues early. Keep both. (answered by SpartanDev)\n\n## 3. Help Interactions\nHelper: sayonara | Helpee: cjft | Context: Notifying about a failing GitHub Actions workflow | Resolution: cjft acknowledged the issue and committed to fixing it\nHelper: cjft | Helpee: Team | Context: Fixing failing GitHub Actions workflow | Resolution: Created and merged PR #4640 to fix the issue and rerun actions\n\n## 4. Action Items\nType: Technical | Description: Fix failing GitHub Actions workflow | Mentioned By: cjft\nType: Technical | Description: Merge PR #4640 and rerun actions | Mentioned By: cjft\nType: Feature | Description: Implement deep research plugin with PRD | Mentioned By: sayonara\nType: Feature | Description: Enable container support and internet access for Codex | Mentioned By: sayonara", "messageCount": 24, "userCount": 4 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-18": { "filename": "2025-05-18.md", "content": "# elizaOS Development Discord - 2025-05-18\n\n## Overall Discussion Highlights\n\n### Plugin Development & Extension\n- Discussions centered on extending existing plugins, particularly for Discord integration\n- Users experiencing issues with custom plugins being overwritten by standard ElizaCore plugins\n- Agent Joshua suggested importing plugins locally via `workspace:*` as a solution for extending existing plugins\n- Scooter shared code snippets showing how community manager agent retrieves Discord usernames from entity metadata\n\n### CI/CD & GitHub Workflows\n- Team actively addressing failing GitHub Actions workflows in the elizaOS/eliza repository\n- Debate about whether CI should run on PR or only on push to v2-dev\n- PR #4640 created and merged to fix workflow issues\n- Emphasis on testing PRs early to catch issues before they reach production\n\n### Agent Memory Management\n- Discussion about storing Discord usernames in ElizaOS agents\n- Questions about whether ElizaOS still uses components or relies on entity metadata\n- Challenges with getting agents to remember usernames through entity metadata storage alone\n\n### Future Development\n- Excitement about Codex for code review and generation\n- Plans for container support and internet access implementation\n- Exploration of UDP traffic handling for CVMs without dedicated IPs\n\n## Key Questions & Answers\n\n**Q: Shouldn't CI only try on push to v2-dev instead of PR?** \nA: PR testing catches issues early. Keep both. (answered by SpartanDev)\n\n**Q: How do I achieve the opposite and get the custom plugin to overwrite the discord plugin message handlers?** \nA: When I extend existing plugins, I pull the plugin code locally and make changes and import it via `workspace:*`. (answered by Agent Joshua)\n\n**Q: Has anyone here actually managed to extend an existing plugin?** \nA: When I extend existing plugins, I pull the plugin code locally and make changes and import it via `workspace:*`. (answered by Agent Joshua)\n\n## Community Help & Collaboration\n\n1. **Discord Plugin Extension Support**\n - Helper: Agent Joshua\n - Helpee: Scooter\n - Context: Extending existing plugins for Discord integration with custom message formatting\n - Resolution: Suggested pulling plugin code locally and importing via `workspace:*`, though the issue wasn't fully resolved\n\n2. **GitHub Actions Workflow Fix**\n - Helper: sayonara\n - Helpee: cjft\n - Context: Notifying about a failing GitHub Actions workflow\n - Resolution: cjft acknowledged the issue and committed to fixing it\n \n3. **Discord Bot Capabilities**\n - Helper: Hidden Forces\n - Helpee: Scooter\n - Context: Scooter asked about storing Discord usernames in ElizaOS\n - Resolution: Partial - Hidden Forces provided general Discord bot information and a Python code example, but didn't directly address the components question\n\n## Action Items\n\n### Technical\n- Fix failing GitHub Actions workflow (mentioned by cjft)\n- Merge PR #4640 and rerun actions (mentioned by cjft)\n- Investigate why custom Discord plugin message handlers are being overwritten by ElizaCore Discord plugin (mentioned by Scooter)\n- Investigate methods for persistent storage of Discord usernames in ElizaOS agents (mentioned by Scooter)\n- Explore workarounds for UDP traffic handling without dedicated IPs for CVMs (mentioned by Agent Joshua)\n- Clarify the `workspace:*` import method for extending plugins (mentioned by Scooter)\n\n### Documentation\n- Document how ElizaOS handles Discord user information persistence (mentioned by Scooter)\n- Clarify whether components are still used in current ElizaOS implementation (mentioned by Scooter)\n- Provide documentation on how to properly use workspace imports in package.json (mentioned by Scooter)\n\n### Feature\n- Implement deep research plugin with PRD (mentioned by sayonara)\n- Enable container support and internet access for Codex (mentioned by sayonara)" }, "ai_news_hyperfy_daily_json_2025-05-18": { "filename": "2025-05-18.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-18", "date": 1747526400, "stats": { "totalMessages": 44, "totalUsers": 11 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary:\nThe chat primarily focused on troubleshooting deployment issues and discussing player controller customization. A developer (emotionull) successfully built their project but encountered domain connection and avatar loading problems. HypPrivakos identified typos in the .env file configuration, specifically in PUBLIC_ASSETS_URL (using \"?\" instead of \"/\") and PUBLIC_API_URL (using \"http::/\" instead of \"http://\"). Later, Cybernetic-O-Cult inquired about customizing player controllers, specifically regarding physics, animation playback, and camera functionality, wondering if forking the repository was the best approach. Jin also mentioned improving a Hyperfy news aggregator and suggested downloading data from X (Twitter) to solve the issue of retrieving historical retweets.\n\n## 2. FAQ:\nQ: How can I customize the player controller for app-specific logic changes? (asked by Cybernetic-O-Cult) A: Unanswered\nQ: How can I get historical retweets for the Hyperfy news aggregator? (asked by jin) A: Download your data from X (Twitter) settings/account (answered by jin)\n\n## 3. Help Interactions:\nHelper: HypPrivakos - HyperWorld.Host | Helpee: emotionull | Context: Avatar not loading due to configuration errors | Resolution: Identified typos in .env file - PUBLIC_ASSETS_URL had \"?\" instead of \"/\" and PUBLIC_API_URL had \"http::/\" instead of \"http://\"\n\n## 4. Action Items:\nTechnical: Fix typos in .env configuration for PUBLIC_ASSETS_URL and PUBLIC_API_URL | Description: Replace \"?\" with \"/\" in assets URL and fix protocol syntax in API URL | Mentioned By: HypPrivakos - HyperWorld.Host\nTechnical: Improve Hyperfy news aggregator | Description: Enhance functionality to better handle historical retweets | Mentioned By: jin\nDocumentation: Clarify approach for customizing player controllers | Description: Document whether forking is recommended for customizing player physics, animation, and camera | Mentioned By: Cybernetic-O-Cult", "messageCount": 19, "userCount": 6 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Analysis of ⚡│general Discord Channel\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. The main technical interaction involves emotionull requesting to connect a subdomain (dev.phettaverse.games) to a specific world ID, which HypPrivakos responded to with an IP address for DNS configuration. There was also a brief discussion about a QR code not working properly, with Roustan mentioning it should be working now but might require cache clearing, and noting compatibility issues with some mobile devices. Ashxn suggested pointing to hub.hyperfy.xyz instead to ensure better mobile and VR compatibility. The rest of the conversation included MUDBONE discussing business cards for a Solana conference and sharing designs, plus some unrelated messages.\n\n## 2. FAQ\nQ: Could I possibly connect dev.phettaverse.games to world_fa8723c3-4eb8-439d-b83d-00c3eed39301? (asked by emotionull) A: Please point that subdomain to 163.5.159.11 (answered by HypPrivakos - HyperWorld.Host)\nQ: Is Roustan down? (asked by MUDBONE) A: down for what? (answered by 𝕽𝖔𝖚𝖘𝖙𝖆𝖓)\n\n## 3. Help Interactions\nHelper: HypPrivakos - HyperWorld.Host | Helpee: emotionull | Context: Connecting a subdomain to a specific world ID | Resolution: Provided IP address (163.5.159.11) for DNS configuration\nHelper: 𝕽𝖔𝖚𝖘𝖙𝖆𝖓 | Helpee: MUDBONE | Context: QR code not working | Resolution: Suggested clearing cache and noted it works only on newest iPhones and Android\nHelper: Ashxn | Helpee: MUDBONE | Context: QR code compatibility issues | Resolution: Suggested pointing to hub.hyperfy.xyz for better mobile and VR compatibility\n\n## 4. Action Items\nTechnical: Point dev.phettaverse.games subdomain to 163.5.159.11 | Description: DNS configuration for connecting to specific world | Mentioned By: HypPrivakos - HyperWorld.Host\nTechnical: Consider pointing QR code to hub.hyperfy.xyz | Description: Create a world with better mobile and VR compatibility | Mentioned By: Ashxn", "messageCount": 19, "userCount": 7 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "# Analysis of 🧊│3d-design Channel\n\n## 1. Summary\nThe chat segment contains a brief technical discussion about optimization challenges in VR development, particularly for user-generated content (UGC). Ashxn shares insights about performance bottlenecks, noting that draw calls are the primary limiting factor for Quest 3 VR applications, with a threshold of around 20 draw calls before performance degrades significantly. They emphasize that triangle counts and materials are less problematic for modern VR hardware like Quest 3, which has sufficient memory and GPU capacity, but CPU-intensive draw calls remain a critical constraint. Ashxn suggests that creators can still build impressive interactive VR spaces by focusing on optimization techniques like texture atlasing and mesh merging. The conversation concludes with b0gie suggesting that developers should approach VR content creation with optimization standards similar to PS1 or Sega Saturn era games.\n\n## 2. FAQ\nQ: How many draw calls can a VR application handle before performance issues? (asked by Ashxn) A: Around 20 draw calls before performance degrades significantly (answered by Ashxn)\nQ: What matters more for Quest 3 performance - triangle count, materials, or draw calls? (asked by Ashxn) A: Draw calls are most critical; triangle counts and materials don't matter as much as the Quest 3 has sufficient memory and GPU (answered by Ashxn)\n\n## 3. Help Interactions\nHelper: Ashxn | Helpee: Channel members | Context: Understanding VR optimization constraints for user-generated content | Resolution: Explained that draw calls are the primary bottleneck (around 20 max), while triangle counts and materials are less problematic on Quest 3\n\n## 4. Action Items\nTechnical: Implement texture atlasing and mesh merging for VR content optimization | Description: Reduce draw calls by combining textures and meshes | Mentioned By: Ashxn\nTechnical: Target maximum of 20 draw calls for VR applications | Description: Keep draw calls under this threshold to maintain performance | Mentioned By: Ashxn\nTechnical: Focus optimization on CPU-side operations rather than GPU | Description: CPU-intensive draw calls are more problematic than triangle counts or materials | Mentioned By: Ashxn", "messageCount": 6, "userCount": 2 } ] } }, "ai_news_hyperfy_daily_md_2025-05-18": { "filename": "2025-05-18.md", "content": "# Hyperfy Discord - 2025-05-18\n\n## Overall Discussion Highlights\n\n### Deployment & Configuration\n- **emotionull** successfully built their project but encountered domain connection and avatar loading problems\n- **HypPrivakos** identified typos in the `.env` file configuration:\n - `PUBLIC_ASSETS_URL` incorrectly used \"?\" instead of \"/\"\n - `PUBLIC_API_URL` incorrectly used \"http::/\" instead of \"http://\"\n- **emotionull** requested to connect `dev.phettaverse.games` to a specific world ID, and **HypPrivakos** provided an IP address (163.5.159.11) for DNS configuration\n\n### VR Development & Optimization\n- **Ashxn** shared insights about VR performance bottlenecks:\n - Draw calls are the primary limiting factor for Quest 3 (around 20 max before performance degrades)\n - Triangle counts and materials are less problematic as Quest 3 has sufficient memory and GPU capacity\n - CPU-intensive operations remain a critical constraint\n- **b0gie** suggested approaching VR content creation with optimization standards similar to PS1 or Sega Saturn era games\n- **Ashxn** recommended texture atlasing and mesh merging to optimize VR content\n\n### Player Controller Customization\n- **Cybernetic-O-Cult** inquired about customizing player controllers, specifically regarding physics, animation playback, and camera functionality\n- They questioned whether forking the repository was the best approach for implementing app-specific logic changes\n\n### Other Projects\n- **Jin** mentioned improving a Hyperfy news aggregator and suggested downloading data from X (Twitter) to solve the issue of retrieving historical retweets\n- **MUDBONE** discussed business cards for a Solana conference and shared designs\n- QR code compatibility issues were discussed, with **Ashxn** suggesting pointing to hub.hyperfy.xyz for better mobile and VR compatibility\n\n## Key Questions & Answers\n\n1. **Q**: How can I connect a subdomain to a specific world ID? \n **A**: \"Please point that subdomain to 163.5.159.11\" (answered by HypPrivakos)\n\n2. **Q**: How many draw calls can a VR application handle before performance issues? \n **A**: \"Around 20 draw calls before performance degrades significantly\" (answered by Ashxn)\n\n3. **Q**: What matters more for Quest 3 performance - triangle count, materials, or draw calls? \n **A**: \"Draw calls are most critical; triangle counts and materials don't matter as much as the Quest 3 has sufficient memory and GPU\" (answered by Ashxn)\n\n4. **Q**: How can I get historical retweets for the Hyperfy news aggregator? \n **A**: \"Download your data from X (Twitter) settings/account\" (answered by jin)\n\n## Community Help & Collaboration\n\n1. **Configuration Troubleshooting**: \n **Helper**: HypPrivakos \n **Helpee**: emotionull \n **Context**: Avatar not loading due to configuration errors \n **Resolution**: Identified typos in .env file configuration\n\n2. **Domain Configuration**: \n **Helper**: HypPrivakos \n **Helpee**: emotionull \n **Context**: Connecting a subdomain to a specific world ID \n **Resolution**: Provided IP address for DNS configuration\n\n3. **QR Code Compatibility**: \n **Helper**: Roustan & Ashxn \n **Helpee**: MUDBONE \n **Context**: QR code not working properly \n **Resolution**: Suggested clearing cache and recommended pointing to hub.hyperfy.xyz for better mobile and VR compatibility\n\n4. **VR Optimization Guidance**: \n **Helper**: Ashxn \n **Helpee**: Channel members \n **Context**: Understanding VR optimization constraints \n **Resolution**: Explained performance bottlenecks and optimization strategies\n\n## Action Items\n\n### Technical\n- Fix typos in `.env` configuration for `PUBLIC_ASSETS_URL` and `PUBLIC_API_URL` (Mentioned by HypPrivakos)\n- Point `dev.phettaverse.games` subdomain to 163.5.159.11 (Mentioned by HypPrivakos)\n- Consider pointing QR code to hub.hyperfy.xyz for better mobile and VR compatibility (Mentioned by Ashxn)\n- Implement texture atlasing and mesh merging for VR content optimization (Mentioned by Ashxn)\n- Target maximum of 20 draw calls for VR applications (Mentioned by Ashxn)\n- Focus optimization on CPU-side operations rather than GPU (Mentioned by Ashxn)\n- Improve Hyperfy news aggregator to better handle historical retweets (Mentioned by jin)\n\n### Documentation\n- Clarify approach for customizing player controllers (Mentioned by Cybernetic-O-Cult)\n- Document whether forking is recommended for customizing player physics, animation, and camera (Mentioned by Cybernetic-O-Cult)" }, "github_summaries_daily_2025-05-19": { "filename": "2025-05-19.md", "content": "# ElizaOS Daily Update (May 19, 2025)\n\n## OVERVIEW \nToday, significant progress was made in enhancing the ElizaOS framework, particularly in improving the user interface and optimizing code performance. Key features were added, including the integration of the registry and real-time updates for agent status. Additionally, several bug fixes and code refactoring efforts were implemented, contributing to overall system stability and efficiency.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Feature Enhancements\n- Integrated registry usage to streamline operations ([#4641](https://github.com/elizaos/eliza/pull/4641)).\n- Improved real-time UI updates for agent status upon starting agents, enhancing user experience ([#4642](https://github.com/elizaos/eliza/pull/4642)).\n\n### Bug Fixes\n- Fixed chokidar watch usage by adding it as a regular dependency for the CLI and ensuring proper bundling ([#4629](https://github.com/elizaos/eliza/pull/4629)).\n \n### Code Optimization\n- Optimized action formatting functions in `actions.ts`, improving code quality and performance with added input validation ([#4633](https://github.com/elizaos/eliza/pull/4633)).\n\n### Other Contributions\n- Initiated work on the Plugin-Jupiter for handling jupiter swaps within the plugin-trade and Spartan product ([#4593](https://github.com/elizaos/eliza/pull/4593)).\n- Updated ElizaOS and made adjustments to CI processes to reduce unnecessary failures ([#4648](https://github.com/elizaos/eliza/pull/4648), [#4644](https://github.com/elizaos/eliza/pull/4644)).\n\n## CLOSED ISSUES\n- No issues were closed today.\n\n## NEW ISSUES\n- No new issues were reported today." }, "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