{ "date_generated_for": "2025-05-15", "ai_news_elizaos_discord_md_2025-05-14": { "filename": "2025-05-14.md", "content": "# elizaOS Discord - 2025-05-14\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **ElizaOS v2 Development**: Currently in beta testing phase. A team member described it as \"looking at a pizza before it goes into the oven\" with GPT-4o image generation being the final step.\n- **Version Differences**: Users noted significant differences between ElizaOS v1 (main branch, 0.x) and v2 (v2-develop branch, 1.x), described as \"like day and night.\"\n- **Mobile Development**: Discussions about creating mobile applications for ElizaOS, with participants noting that mobile presence is crucial for user adoption. Technical challenges were identified as ElizaOS is dependent on NodeJS, with only some very old versions running on iOS.\n\n### auto.fun Platform\n- **API Limitations**: Users examined the auto.fun repository code and identified that while some API endpoints exist (for swaps, token retrieval, search, and charts), they lack functionality for creating new coins or executing swaps.\n- **Token Tracking Mechanism**: auto.fun tracks tokens that interact with its specific program address (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5) rather than all tokens on-chain.\n- **Market Making**: Team members clarified they have reputable market makers for both CEX and DEX, and addressed questions about relationships with specific market makers.\n\n### Technical Implementation\n- **Supabase Integration**: Users shared SQL commands for creating database tables for agents with proper references and constraints.\n- **Plugin Development**: Discussions about custom plugin development and integration challenges, particularly importing local plugins versus using NPM packages.\n- **Twitter/X Integration**: Users troubleshooting configuration issues with Twitter integration, including setting environment variables for replying to specific users.\n\n### Token Discussions\n- **AI16z Token Permissions**: Concerns about the \"mint\" permission on the AI16z token, with a team member explaining this is standard for daos.fun coins and will be addressed at the appropriate time.\n- **ELI5 Token**: Claims that ELI5 will be the community manager AI agent for ElizaOS v2, with references to an interview confirming this. Debate about the token's legitimacy and potential value ensued.\n\n## Key Questions & Answers\n\n**Q: Can ElizaOS run on iPhone?** \nA: It's dependent on NodeJS and only some very old versions run on iOS; Android might be possible. (DorianD)\n\n**Q: Where is the auto.fun API?** \nA: https://github.com/elizaOS/auto.fun/blob/6877fd1955a2d73577399eabb2b722d4b2806257/packages/client/src/utils/api.ts (Osint)\n\n**Q: Do you have an agreement with Wintermute as a market maker?** \nA: We don't have an agreement with WM, we can't restrict them from trading either. We have very reputable MM's for both CEX & DEX. (jasyn_bjorn)\n\n**Q: What is the roadmap to disable the \"mint\" permission on ai16z token?** \nA: All daos.fun coins have this by default; when we get the right opportunity to change, the team will take a hard look at it. (Osint)\n\n**Q: What's the difference between Eliza and Elizav2?** \nA: Yes like day and night. (xell0x)\n\n**Q: How to set up Supabase tables for ElizaOS?** \nA: Use SQL commands to create tables with proper references and constraints. (cjft)\n\n**Q: Is the ElizaOS/eliza repo on GitHub V2 or is only the CLI using V2?** \nA: Main branch is 0.x (v1) and v2-develop is 1.x (v2). (cjft)\n\n**Q: How does autofun track tokens?** \nA: It processes tokens that interact with the program at autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5. (vas, confirmed by DorianD)\n\n**Q: Is there a plan for Eli5?** \nA: Shaw confirmed eli5 to be the community manager AI agent of elizaOS v2. (xell0x)\n\n## Community Help & Collaboration\n\n1. **auto.fun API Exploration**:\n - Osint provided GitHub links to the API code and brand kit when DorianD was looking for auto.fun API information.\n - vas explained to DorianD how auto.fun tracks tokens through interaction with its program address.\n\n2. **ElizaOS v2 Development Updates**:\n - jin shared progress on v2 development with xell0x, providing a visual explanation of the current state.\n - xell0x explained to Dive or Die that v2 is currently being beta tested.\n\n3. **Database Setup Assistance**:\n - cjft shared SQL commands for creating agent and room tables with proper references for Supabase integration.\n\n4. **Configuration Troubleshooting**:\n - cjft helped starlord understand model loading output behavior.\n - cjft suggested checking ENABLE_ACTION_PROCESSING setting and TWITTER_TARGET_USERS configuration for Twitter integration issues.\n\n## Action Items\n\n### Technical\n- Develop mobile apps (iOS/Android) for ElizaOS/auto.fun (Mentioned by: DorianD, Osint)\n- Expand auto.fun API to support coin creation and swapping (Mentioned by: DorianD)\n- Fix getToken API endpoint which is broken with a TODO comment (Mentioned by: DorianD)\n- Complete v2 development, currently in beta testing phase (Mentioned by: jin, xell0x)\n- Address the \"mint\" permission on AI16z token (Mentioned by: Kenshiro)\n- Fix plugin import errors for custom plugins (Mentioned by: cjft)\n- Resolve character configuration not updating in UI (Mentioned by: cjft)\n- Fix Twitter/X integration to properly respond to targeted users (Mentioned by: cjft)\n- Resolve client build errors in Windows environment (Mentioned by: Bills_43)\n- Recreate launch or launchandswap instruction to interact with auto.fun program (Mentioned by: vas)\n\n### Documentation\n- Create guide for extending core plugins in v2 (Mentioned by: cjft)\n- Document differences between v1 and v2 plugin systems (Mentioned by: cjft)\n- Document steps for creating tokens through auto.fun (Mentioned by: DorianD)\n\n### Feature\n- Create an AI agent to answer project-related questions (Mentioned by: DorianD)\n- Consider including ICM meta bumper functionality in auto.fun (Mentioned by: abhi_ironman)\n- Improve plugin-bootstrap customization options (Mentioned by: cjft)\n- Add Google Generative AI support to ElizaOS beta (Mentioned by: cjft)\n- Develop a phone app for auto.fun (Mentioned by: DorianD)" }, "ai_news_elizaos_discord_md_2025-05-13": { "filename": "2025-05-13.md", "content": "# elizaOS Discord - 2025-05-13\n\n## Overall Discussion Highlights\n\n### ElizaOS Development Status\n- ElizaOS v2 release is scheduled for the current month, with team members indicating they'll update when it's ready\n- Users can track development progress on GitHub at https://github.com/elizaos/eliza\n- ElizaOS is confirmed to be an open-source project with resources available at eliza.how and GitHub repositories\n\n### Technical Challenges\n- Multiple users experiencing plugin loading failures, particularly with Farcaster and Bootstrap plugins\n- Entity relationship constraints in SQL causing errors when entities aren't properly stored\n- Twitter/X integration issues including scheduling posts and handling replies without threading\n- Local AI model configuration with Ollama showing connection timeout errors\n- Discord integration issues, particularly with formatting responses as replies\n- v2-develop branch challenges including character definition problems and frontend display issues\n\n### AI Agent Applications & Monetization\n- Discussion about potential monetization strategies for AI agents, including subscription models vs. token-based access\n- Reference to terminal.cookie.fun using AI agents for trading analysis\n- Suggestions for AI applications in financial analysis, particularly SEC filing analysis\n- Limitations of AI in determining sentiment were discussed\n\n### Community Concerns\n- Some community members expressed frustration about a DOOD token airdrop allocation process\n- Discussion about cryptocurrency tokens including eli5, squid, and autofun, with brief mentions of market performance\n\n## Key Questions & Answers\n\n**Q: What happened to eliza.how? Is it not working anymore?** \nA: It works (answered by Osint)\n\n**Q: Can someone share resource(s) where I can learn the scope of the character file for ElizaOS agent?** \nA: https://eliza.how and https://github.com/elizaOS/characterfile (answered by Osint)\n\n**Q: Shaw has recently mentioned on v2 release as this week or next week…do team have further update or clarity on this?** \nA: We'll update when we have the release ready (answered by Kenk)\n\n**Q: How is v2 going?** \nA: You can always go and check in github at https://github.com/elizaos/eliza (answered by Osint)\n\n**Q: How can I make Twitter replies use single tweets instead of threads?** \nA: Have it a try, should not use threads (answered by der.jogi)\n\n**Q: How does tweet scheduling work in ElizaOS?** \nA: Set both TWITTER_POST_INTERVAL_MIN and TWITTER_POST_INTERVAL_MAX to the same value for consistent timing (answered by der.jogi)\n\n## Community Help & Collaboration\n\n1. **Character File Resources**\n - Osint provided GitHub links to character file repository and eliza.how website to help Tahlil learn about character files for ElizaOS agents\n\n2. **Token Allocation Support**\n - jasyn_bjorn offered to give their own DOOD token allocation to sukrucildirr who was upset about missing the allocation\n\n3. **Twitter Configuration Assistance**\n - der.jogi shared solutions for tweet scheduling timing issues and avoiding threading in replies\n - der.jogi shared GitHub links to client and server socket implementation code for WebSocket endpoint questions\n\n4. **Project Perspective**\n - MDMnvest provided perspective to Xyness that Autofun is in early days and needs time to grow as success stories emerge\n\n## Action Items\n\n### Technical\n- Fix Farcaster plugin loading failures - resolve module loading strategies for @Eliza#3900os/plugin-farcaster (mentioned by thescoho)\n- Fix entity relationship constraints - ensure entities are stored before creating relationships (mentioned by der.jogi)\n- Resolve Ollama connection timeout errors - fix \"Headers Timeout Error\" when connecting to local Ollama instance (mentioned by der.jogi)\n- Fix Bootstrap plugin loading failure - resolve module loading strategies for @elizaos/plugin-bootstrap (mentioned by der.jogi)\n- Fix Twitter mention response functionality - agent not responding to Twitter mentions despite successful tweeting (mentioned by der.jogi)\n- Fix character definition display in v2-develop - character definitions not showing correctly in frontend (mentioned by der.jogi)\n- Fix cross-posting between Twitter and Discord - enable forwarding matching tweets to Discord channels (mentioned by der.jogi)\n- Fix local AI model initialization hanging - system gets stuck after model path validation (mentioned by starlord)\n- Check GitHub repository for ElizaOS v2 development progress (mentioned by Osint)\n\n### Documentation\n- Update Twitter agent guide for v2 - current guide doesn't work properly with v2-develop branch (mentioned by der.jogi)\n\n### Feature\n- Create LinkedIn plugin for ElizaOS - add LinkedIn integration capabilities (mentioned by der.jogi)\n- Consider releasing Elizav2 while market conditions are favorable (mentioned by ryanthelad)\n- Consider monetization strategies for AI agents - subscription models vs. token-based access (mentioned by Osint)\n- Explore AI agent applications for financial analysis - potential for AI to analyze SEC filings and financial data (mentioned by The Prophet)" }, "ai_news_elizaos_discord_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# elizaOS Discord - 2025-05-12\n\n## Overall Discussion Highlights\n\n### Technical Issues & Development\n- **Knowledge Import Functionality**: Users reported that string-based knowledge imports work successfully, but file path and directory references fail despite setting `ragKnowledge: true` in the Eliza OS platform.\n- **Discord Integration Challenges**: Several users discussed difficulties with Discord plugin functionality, particularly getting proper @username mentions with notifications working correctly.\n- **Ollama Configuration**: Users discovered they need to explicitly add `@elizaos/plugins-ollama` to their character file rather than relying on environment variables alone to prevent unnecessary node-llama-cpp installation.\n- **Video Generation**: Videos generated by agents save to cache but may not display properly in the GUI, creating usability issues.\n- **Fee Collection Issue**: A technical issue with fee collection on auto.fun was reported and subsequently fixed by the team overnight.\n\n### Token Discussions\n- **Dood Token Distribution**: Discussions about eligibility for Dood tokens, with clarification that the Dood team airdropped to holders individually rather than through the elizaOS team directly.\n- **ELI5 Token Development**: Community members debated the potential of ELI5 as an AI education tool that could explain concepts simply to users, with proposals for community pages, Twitter accounts, and Reddit integration.\n- **Auto.fun Platform Strategy**: Ongoing discussion about auto.fun's positioning as an AI-focused launchpad with verified teams versus competitors, with suggestions to pivot toward being a launchpad for startups rather than memes.\n\n### Community Management\n- **Discord Scammer Report**: A user reported a Discord scammer, which was promptly addressed by a moderator.\n- **Channel Moderation**: Off-topic discussions about market conditions and cryptocurrency prices were redirected to appropriate channels by moderators.\n\n## Key Questions & Answers\n\n- **Q**: Why didn't I receive Dood tokens? (asked by sukrucildirr) \n **A**: \"If you haven't had any Dood sent you weren't eligible\" (answered by Kenk)\n\n- **Q**: How will Dood tokens be distributed without collecting addresses? (asked by sukrucildirr) \n **A**: \"The dood team airdropped our holders individually, not the team directly ser\" (answered by jasyn_bjorn)\n\n- **Q**: Where or what channel can we use to report discord scammer? (asked by Die Antwoord) \n **A**: \"Here\" (answered by Osint)\n\n- **Q**: Is \"@elizaos/plugin-direct\" deprecated? Can't understand why it's stopping character from loading. (asked by techcomthanh) \n **A**: \"You don't need that\" (answered by techcomthanh)\n\n- **Q**: Will there be a launch today? (asked by r) \n **A**: \"Nope no launch today\" (answered by noj)\n\n- **Q**: Is there a launch today? (asked by velja) \n **A**: \"No idea\" (answered by Kenk)\n\n## Community Help & Collaboration\n\n1. **Discord Scammer Report**\n - **Helper**: Osint (aka not_a_dev_ai)\n - **Helpee**: Die Antwoord\n - **Context**: Reporting a Discord scammer with user_id: 1331066099864829964\n - **Resolution**: \"Taken care of, thank you for the report\"\n\n2. **Ollama Configuration Support**\n - **Helper**: techcomthanh\n - **Helpee**: techcomthanh (self-help shared with community)\n - **Context**: Ollama configuration causing node-llama-cpp installation despite using remote resource\n - **Resolution**: Explained need to add `@elizaos/plugins-ollama` to character file in addition to environment variables\n\n3. **Fee Collection Issue Resolution**\n - **Helper**: Kenk\n - **Helpee**: gummy\n - **Context**: Issue with collecting fees on auto.fun\n - **Resolution**: Team pushed a fix overnight and confirmed it was working after user tested again\n\n4. **ELI5 Community Development**\n - **Helper**: gummy\n - **Helpee**: Community\n - **Context**: Proposing to create ELI5 community page and X communities\n - **Resolution**: Kenk approved the idea and gummy committed to setting up X communities\n\n## Action Items\n\n### Technical\n- Fix knowledge import functionality for file paths and directories in beta 49 (Mentioned by techcomthanh)\n- Fix Discord @username mentions to properly highlight and send notifications (Mentioned by techcomthanh)\n- Improve video display in GUI for videos generated by agents (Mentioned by techcomthanh)\n- Resolve issue with node-llama-cpp installation when using remote Ollama endpoint (Mentioned by techcomthanh)\n- Fix fee collection issue on auto.fun (Mentioned by Kenk)\n- Create ELI5 Twitter account that replies to questions with simple explanations (Mentioned by gummy)\n- Integrate ELI5 agent with Reddit community (Mentioned by ryanthelad)\n\n### Documentation\n- Provide sample files and code examples for knowledge import from files (Mentioned by techcomthanh)\n- Clarify Ollama plugin setup requirements in documentation (Mentioned by techcomthanh)\n- Document how to build tweet threads with agent-twitter-client repo (Mentioned by Bitcoin Broccoli)\n- Clarify Dood token distribution eligibility criteria (Mentioned by sukrucildirr)\n\n### Feature\n- Create ELI5 community page or main page (Mentioned by gummy)\n- Set up X communities for ELI5 (Mentioned by gummy)\n- Fix token locked chat for ELI5 on website (Mentioned by ryanthelad)\n- Pivot auto.fun to be leading launchpad for startups instead of memes (Mentioned by wire)" }, "ai_news_elizaos_dev_md_2025-05-14": { "filename": "2025-05-14.md", "content": "# elizaOS Development Discord - 2025-05-14\n\n## Overall Discussion Highlights\n\n### Plugin Development & Architecture\n- **Discord Plugin Extension**: Detailed discussion on proper methods to extend the Discord plugin in ElizaOS, focusing on class extension rather than service modification\n- **DAG Viewer Tool**: DefiniteOptimist shared progress on a tool for visualizing and designing agent workflows using react-flow as the underlying technology\n- **Plugin Versioning**: Clarification about Farcaster plugin versions, with distinction between `plugin-twitter` (for v2/v1.x) and `client-twitter` (for v0.x)\n\n### Integration & Identity Management\n- **GitHub-Wallet Integration**: Jin proposed several methods for linking wallet addresses to GitHub identities:\n - Hidden comments in profile READMEs\n - Comments in GitHub issues\n - GitHub gist implementation with API integration\n- **Anonymous Airdrops**: Discussion about zkdrops for anonymous airdrops, with concerns about airdrop farming and potential mitigation strategies\n\n## Key Questions & Answers\n\n### Plugin Development\n- **Q**: How close is Farcaster v2? \n **A**: It exists but is currently in testing (DorianD)\n\n- **Q**: What's the difference between `plugin-twitter` & `client-twitter`? \n **A**: The former is for v2/v1.x and the latter for v0.x (sayonara)\n\n- **Q**: For custom Discord plugin functionality, should I extend it in index.ts while NPXing the plugin or modify the entire plugin code? \n **A**: Extending the base plugin in your own index.ts is usually cleaner than modifying the core code (Ruby)\n\n- **Q**: What would be the advantages to NPM installing eliza cli instead of NPX? \n **A**: Global install gives persistent access to cli commands without npx and is faster since you're not downloading the package each time (Ruby)\n\n### DAG Viewer Tool\n- **Q**: Are you using graphviz under the hood for the DAG viewer? \n **A**: It's react-flow under the hood (DefiniteOptimist)\n\n- **Q**: Have you considered adding support for custom node types and conditional flows? \n **A**: Yes, those are on the way! (DefiniteOptimist)\n\n## Community Help & Collaboration\n\n### Discord Plugin Extension Support\nRuby provided comprehensive guidance to Scooter on extending the Discord plugin:\n- Identified version mismatch issues in package.json\n- Recommended pinning @elizaos/cli and @elizaos/core to specific beta versions\n- Shared a complete implementation example for extending the DiscordPlugin class with custom reply functionality\n- Explained proper plugin extension patterns that work with ElizaOS's architecture\n\n### Farcaster Module Selection\nSayonara helped Jonas understand which Twitter module to use with Farcaster, clarifying that plugin-twitter is for v2/v1.x and client-twitter is for v0.x\n\n### DAG Viewer Feature Suggestions\nRuby provided DefiniteOptimist with feature suggestions for the DAG viewer:\n- Agent state tracking and debug views\n- Circuit breakers and rate limiting between nodes\n- Budget constraints to prevent resource spiraling\n\n## Action Items\n\n### Technical\n- Extend DiscordPlugin class directly instead of modifying the service to implement reply functionality (Ruby)\n- Pin @elizaos/cli and @elizaos/core to specific beta versions (^1.0.0-beta.51) to match plugin versions (Ruby)\n- Override sendMessage method in extended Discord plugin to implement reply functionality (Ruby)\n- Implement wallet linking via GitHub gists using GitHub API (Jin)\n- Develop strategies to mitigate airdrop farming by combining automated calculations with human evaluation (Jin)\n- Develop dynamic dependency generation and orchestration capabilities for DAG viewer (DefiniteOptimist)\n\n### Documentation\n- Document the proper pattern for extending ElizaOS plugins (Ruby)\n\n### Features\n- Link wallets in hidden comments on GitHub profile READMEs (Jin)\n- Link wallets as comments in GitHub issues (Jin)\n- Add agent state tracking and debug views to help catch edge cases in decision trees (Ruby)\n- Implement custom node types and conditional flows for modeling complex agent behavior patterns (Ruby)\n- Add budget constraints for applications and pathways in DAG viewer (DefiniteOptimist)\n- Implement circuit breakers or rate limiting between nodes to prevent cascading failures (Ruby)" }, "ai_news_elizaos_dev_md_2025-05-13": { "filename": "2025-05-13.md", "content": "# elizaOS Development Discord - 2025-05-13\n\n## Overall Discussion Highlights\n\n### Knowledge Integration in Character Files\n- Discussions focused on how to properly reference knowledge files in character.json\n- Paths are relative to the characters/knowledge directory\n- RAG (Retrieval-Augmented Generation) knowledge works by setting \"ragknowledge: true\" in character settings\n- Users explored the codebase, specifically examining how knowledge is processed through ragknowledge.ts\n- Version differences between v1 and v2 of the Eliza codebase were mentioned, with a link to the v2-develop branch\n\n### Plugin Development\n- Plugins have been moved to a separate repository (elizaos-plugins)\n- Question raised about LinkedIn plugin availability for Eliza\n- GitHub link shared: https://github.com/elizaos-plugins\n\n### Community Guidelines\n- Ruby expressed disinterest in providing feedback on gambling or token projects\n- Preference stated for building useful tools rather than enabling speculation\n- Some promotional messages from freelancers were flagged as potential spam\n\n## Key Questions & Answers\n\n**Q: How does knowledge work in character files and what is the path relative to?** (asked by LemonS) \n**A:** The path specified in character.json is relative to characters/knowledge directory, and you can't use \"./\" or \"../\" (answered by Nooters)\n\n**Q: Is there an example of character JSON files referencing a knowledge path?** (asked by DorianD) \n**A:** Core/runtime reads what's defined in knowledge, which can be a path, array or similar (answered by 0xbbjoker)\n\n**Q: Where are the plugins now that they've been moved out of the core repo?** (asked by DorianD) \n**A:** https://github.com/elizaos-plugins (answered by shaw)\n\n## Community Help & Collaboration\n\n1. **Knowledge Path Implementation**\n - Nooters helped LemonS understand how knowledge paths work in character files\n - Explained directory structure and provided guidance on relative paths\n\n2. **RAG Knowledge Configuration**\n - 0xbbjoker assisted DorianD in understanding RAG knowledge implementation\n - Explained the need to set \"ragknowledge: true\" in settings and add paths to files\n\n3. **Plugin Repository Location**\n - shaw directed DorianD to the new elizaos-plugins repository\n - Provided the GitHub link to help locate moved plugins\n\n4. **Knowledge Implementation Exploration**\n - DorianD investigated the codebase and found relevant code in ragknowledge.ts\n - Shared findings about how knowledge processing is handled\n\n## Action Items\n\n### Technical\n- **Implement proper knowledge file referencing in character.json files** (Mentioned by Nooters)\n - Ensure paths are relative to characters/knowledge directory\n\n### Feature\n- **LinkedIn plugin for Eliza** (Mentioned by aith)\n - Create a LinkedIn plugin similar to existing Twitter plugin\n\n### Documentation\n- **Document the knowledge referencing system** (Mentioned by DorianD)\n - Create clear documentation on how to properly reference knowledge files in character.json" }, "ai_news_elizaos_dev_md_2025-05-12": { "filename": "2025-05-12.md", "content": "# elizaOS Development Discord - 2025-05-12\n\n## Overall Discussion Highlights\n\n### Character Configuration & Development\n- Discussion about referencing one character file from another (e.g., importing woman.character.json into eliza.character.json)\n- Detailed troubleshooting of character.json configuration issues in v2, including voice settings and knowledge directory paths\n- Recommendation to keep a minimal approach when starting with character configurations before adding complexity\n\n### Tools & Integrations\n- Interest in news integration capabilities for agents, with suggestion to build an RSS plugin\n- Introduction of Screenpipe (https://screenpi.pe/), a tool for recording screen activity that can be used for AI training\n- Discussion about potential plugin development for Screenpipe\n\n### System Architecture & Security\n- Emphasis on proper credential management, keeping sensitive information in .env files rather than character configurations\n- Clarification on the differences between CLI and manual workflows in v2, noting that CLI has its own mental model\n\n## Key Questions & Answers\n\n**Q: Has anyone done something like have a main character file reference/import another character file?** \nA: Self-answered that it would require modifying the runtime that reads the JSON files (DorianD)\n\n**Q: Is there a plugin to get the latest news and add it as knowledge into the agent? Like News API connection?** \nA: Build an RSS plugin (sayonara)\n\n**Q: Does anyone have a link to the online Eliza Helper Bot interface?** \nA: The helper bot interface was deprecated a while back - the new v2 workflow is more flexible but has a steeper learning curve. (Ruby)\n\n**Q: Why doesn't the template include info for the OpenAI key? What LLM backend would it use?** \nA: The OpenAI key and LLM settings go in your .env file or environment variables. The default backend is gpt-4 but you can override that in your project's main config. (Ruby)\n\n**Q: Should the Supabase keys also be put into the .env file and kept out of the character JSON? What's the format?** \nA: Yes! Definitely keep those keys in .env - never in the character json. The format is simple: SUPABASE_URL=your_url_here SUPABASE_ANON_KEY=your_key_here (Ruby)\n\n## Community Help & Collaboration\n\n- **Ruby helped Hidden Forces** with character.json configuration issues, providing a simplified template and explaining the proper way to manage credentials\n- **Ruby clarified** the conceptual differences between CLI and manual workflows in v2, explaining that CLI isn't just an automated version of manual steps\n- **sayonara suggested** building an RSS plugin to Titan who was looking for news integration capabilities\n- **Terexitarius shared** Screenpipe tool with the community, suggesting it might be useful for personal knowledge management and AI training\n\n## Action Items\n\n### Technical\n- Build an RSS plugin for news integration with agents (mentioned by sayonara)\n- Fix character.json configuration issues including voice model/url values and knowledge directory path (mentioned by Ruby)\n- Address privacy concerns in screen recording with selective capture or data retention policies for Screenpipe (mentioned by Ruby)\n- Potential EVM chains support for an unspecified project (mentioned by Terexitarius)\n\n### Documentation\n- Improve documentation on differences between manual work and CLI in v2 (mentioned by Hidden Forces)\n- Create a guide on key differences between CLI and manual approaches (mentioned by Ruby)\n\n### Feature\n- Character file import system to allow referencing one character file from another (mentioned by DorianD)\n- News integration plugin to get latest news and add it as knowledge into agents (mentioned by Titan)\n- Potential Screenpipe plugin development for the screen recording tool (mentioned by Terexitarius)" }, "ai_news_elizaos_daily_json_2025-05-14": { "filename": "2025-05-14.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-05-14", "categories": [ { "title": "Thematic Twitter Activity Summary", "content": [ { "theme_title": "AI Model Developments and Preferences", "text": "Several users discussed AI model capabilities and preferences. @shawmakesmagic declared that \"Gemini is the best model in the world right now,\" noting that many developers have quietly switched to it in Cursor without fanfare. They mentioned that the transition happened organically as users realized its quality. @shawmakesmagic also retweeted @AviSchiffmann's post stating that \"Google just clearly has the best AI offering\" and that Gemini is \"fantastic\" with trustworthy infrastructure compared to OpenAI (\"still a startup\") and Anthropic (\"nowhere to be seen\"). In a separate conversation, @shawmakesmagic offered to volunteer prompt engineering skills to the @xai team, noting that Grok's issues with mentioning South African genocide in unrelated responses could be \"trivially solvable\" with an extra LLM call, expressing surprise that they are \"doing fact tuning in the system prompt.\"", "sources": [ "https://twitter.com/shawmakesmagic/status/1922468068271231424", "https://twitter.com/shawmakesmagic/status/1922467460109795433", "https://twitter.com/AviSchiffmann/status/1922352162249507190", "https://twitter.com/shawmakesmagic/status/1922710925406028075", "https://twitter.com/shawmakesmagic/status/1922711405557428246", "https://twitter.com/pitdesi/status/1922702580691427739", "https://twitter.com/shawmakesmagic/status/1922693616297755002" ], "images": [], "videos": [] }, { "theme_title": "3D Content Creation Workflows", "text": "A significant discussion emerged around new AI-powered 3D content creation workflows. @dankvr shared a \"slick workflow\" combining ChatGPT 4o for image generation, then converting to 3D models using VibeRig, which was retweeted by @shawmakesmagic. This workflow exports GLB files with single textures and Mixamo-style bone naming, allowing for custom animations. @dankvr noted this process is \"50% faster\" than their previous manual approach for creating avatars for over 60 different projects. The workflow builds on technology from @DeemosTech's Rodin tool, which @craigrrob (retweeted by @shawmakesmagic) praised as \"awesome\" and his \"favorite by far\" among image-to-mesh models. @dankvr also acknowledged @youwillmakemaps and @sidahuj for their \"cool workflow.\"", "sources": [ "https://twitter.com/dankvr/status/1922789229391725035", "https://twitter.com/dankvr/status/1922792743065043281", "https://twitter.com/craigrrob/status/1922399505497927932", "https://twitter.com/dankvr/status/1922702799193719021", "https://twitter.com/dankvr/status/1922789561530196127" ], "images": [ "https://pbs.twimg.com/media/Gq8agKjWgAAc5Wn.jpg", "https://pbs.twimg.com/media/Gq8bsroWYAAOOc-.jpg", "https://pbs.twimg.com/media/Gq8btPlWIAAsri_.jpg", "https://pbs.twimg.com/media/Gq8ehQZXEAANh1v.jpg", "https://pbs.twimg.com/media/Gq8hlheWcAAFNhf.jpg", "https://pbs.twimg.com/amplify_video_thumb/1922399223808466945/img/OsTm0YbG_ASzlpV4.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1922399223808466945/vid/avc1/1424x1080/gLqpFN7YJrFWtcOv.mp4?tag=21" ] }, { "theme_title": "Data Management and Agentic Workflows", "text": "@dankvr shared several updates about data management tools and agentic workflows. They posted about a new copy button that allows users to get markdown formatted for an LLM with options to include specific data. They also introduced contributor summaries that provide quick rundowns of who did what on a daily, weekly, or monthly basis through the dashboard. @dankvr outlined a three-step approach to data management: 1) Gathering information scattered across platforms, 2) Creating agentic workflows to structure data, and 3) Enabling agents tapped into the pipeline to run autonomously while staying aligned with organizational needs. This approach, which @shawmakesmagic retweeted, offers the bonus of full data ownership and flexibility to use any LLM. @dankvr mentioned these open-source data pipelines are being built for @elizaos and can be used by any group with GitHub, X account, and Discord.", "sources": [ "https://twitter.com/dankvr/status/1922704109477536103", "https://twitter.com/dankvr/status/1922750009885212904", "https://twitter.com/dankvr/status/1922505770068824394", "https://twitter.com/dankvr/status/1922499627053457652" ], "images": [ "https://pbs.twimg.com/media/Gq7RF-1WsAABvcV.jpg", "https://pbs.twimg.com/media/Gq76Q72XkAAlKAO.jpg" ], "videos": [] }, { "theme_title": "Clank Tank and AI Judging", "text": "@dankvr shared updates about Clank Tank, a platform where AI judges review project pitches. They announced a work-in-progress website where users can scroll through past Clank Tank pitches and read each AI judge's review, which was retweeted by @shawmakesmagic. In response to @0xastorre, @dankvr explained that the AI judges have personalities tailored toward different archetypes (developers, quants, degens, casuals), possess episodic memory to remember each pitch, and will soon incorporate Deepsearch and a human feedback loop before final judging. The latest episode (Ep4) features pitches approximately 5 minutes long, which @dankvr considers \"the perfect amount for our AI judges to drill into each project.\"", "sources": [ "https://twitter.com/dankvr/status/1922446904840917284", "https://twitter.com/dankvr/status/1922460020525928556" ], "images": [ "https://pbs.twimg.com/amplify_video_thumb/1922446537470205953/img/m00MSMHG6NpvWqIu.jpg" ], "videos": [ "https://video.twimg.com/amplify_video/1922446537470205953/vid/avc1/1280x718/6jPPLaLPvMjVsUtV.mp4?tag=21" ] }, { "theme_title": "Eliza OS and Ecosystem", "text": "@elizaOS shared several philosophical statements about their platform, including \"You're not looking at Eliza. You're looking through her\" and \"you're not running me. you're building with me.\" They also emphasized that \"Open-source is a baseline, composability is the real unlock.\" @elizaOS announced \"Agent-led entertainment goes live\" while quoting a tweet about autonomous MetaHuman entertainers developed by the Agent SPE team led by @Titan_Node, which uses Unreal Engine, Eliza OS, and Livepeer. @autodotfun commented that \"@Tapestry_AI devs cookin up some fun\" and in another tweet stated that \"building for the future is fun\" while quoting an announcement about a partnership between @comput3ai and the Eliza Ecosystem Fund. @shawmakesmagic, who appears to be associated with Eliza OS based on a quoted tweet, confirmed to @Shaughnessy119 that they've \"been using Nous models since we launched.\"", "sources": [ "https://twitter.com/elizaOS/status/1922630475866329568", "https://twitter.com/elizaOS/status/1922668233263387023", "https://twitter.com/elizaOS/status/1922713268998766781", "https://twitter.com/elizaOS/status/1922752599805075881", "https://twitter.com/autodotfun/status/1922716937483677703", "https://twitter.com/autodotfun/status/1922716517847687222", "https://twitter.com/shawmakesmagic/status/1922779082657321131" ], "images": [ "https://pbs.twimg.com/media/Gq5ZTPDWQAAVLr2.jpg" ], "videos": [] }, { "theme_title": "Investment Regulations and Accessibility", "text": "@shawmakesmagic expressed strong opinions about investment regulations, stating it's \"crazy\" that \"you're not allowed to invest in startups unless you make 300k+ year\" and arguing this needs to be \"abolished yesterday or the means of automated production will be owned by a very very small fraction of people.\" They called it \"totally fucking unethical and amoral that only rich people get exposure to private investment opportunities.\" In response to questions, @shawmakesmagic clarified that these regulations were written after the 1920s stock market crash, long before venture capital was established. They retweeted @wonderwomancode who argued that \"Qualified investor laws are unconstitutional\" and pointed out the absurdity that someone could have \"1 Billion dollars sitting in cash in the bank and still not qualify under the income guidelines.\"", "sources": [ "https://twitter.com/shawmakesmagic/status/1922731328409162204", "https://twitter.com/shawmakesmagic/status/1922733330258079864", "https://twitter.com/shawmakesmagic/status/1922696856695644233", "https://twitter.com/wonderwomancode/status/1922746479938351376", "https://twitter.com/shawmakesmagic/status/1922738027001954434" ], "images": [], "videos": [] }, { "theme_title": "Future of Work and Automation", "text": "@shawmakesmagic initiated a discussion about the timeline for robotic job replacement, asking followers whether they think robots capable of replacing humans at virtually every current job would take 5 years or 5000 years, suggesting most people's estimates would fall \"somewhere between, but closer to 5 than 500 or 5000.\" In follow-up tweets, they clarified they meant current jobs, not future ones, and asked about the timeline for replacing \"every single job humans do now...like even the best violinist in the world, or the best athlete.\" @shawmakesmagic predicted \"40-50 years to true undeniable superior in every obvious way AGI\" but noted that \"Some things we take for granted will be surprisingly hard, Moravec's Paradox.\" They also observed that while new jobs will emerge, they will be \"increasingly abstract\" with \"huge exponential effects on attention, expertise, etc.\" In a separate tweet, they noted that \"many robotics companies are building highly dexterous humanoid robots.\"", "sources": [ "https://twitter.com/shawmakesmagic/status/1922495376805806134", "https://twitter.com/shawmakesmagic/status/1922495651138380160", "https://twitter.com/shawmakesmagic/status/1922499266410357110", "https://twitter.com/shawmakesmagic/status/1922503843423604740", "https://twitter.com/shawmakesmagic/status/1922506070431236176", "https://twitter.com/shawmakesmagic/status/1922477450853777691" ], "images": [], "videos": [] }, { "theme_title": "Open Source AI and Model Training", "text": "@shawmakesmagic retweeted an announcement from @karan4d about @NousResearch launching a testnet for pre-training a 40B parameter LLM described as the \"Largest distributed pretrain ever.\" The model will use MLA Architecture with a dataset combining FineWeb, FineWeb-2, and The Stack v2. The resulting model is designed to be small enough to train on a single H/DGX and run on a 3090 GPU while being powerful enough for reasoning and creative tasks. @shawmakesmagic also commented on a post about H100 GPU pricing, noting that \"$1/hr for H100s is pretty crazy tbh\" in response to @zjasper666's announcement that their company Hyperbolic Labs is offering H100s at $0.99/hour, significantly lower than AWS and GCP's $4-6/hour rates.", "sources": [ "https://twitter.com/karan4d/status/1922751718464319571", "https://twitter.com/NousResearch/status/1922744494002405444", "https://twitter.com/shawmakesmagic/status/1922529398806188258", "https://twitter.com/zjasper666/status/1922511236325113884" ], "images": [], "videos": [] }, { "theme_title": "Grok AI Behavior Issues", "text": "Several tweets discussed issues with Grok AI's behavior. @shawmakesmagic retweeted @colin_fraser's observation that Grok appears to \"over-eagerly\" refer to White Genocide in its responses, suggesting that \"they can still pass it content instructions that you're not supposed to see\" even though asking for Grok's system prompt reveals nothing. In a separate tweet, @shawmakesmagic responded to @pitdesi's post about Grok mentioning South African genocide in unrelated responses, offering to help the @xai team with prompt engineering skills, stating the issue is \"trivially solvable\" with \"an extra LLM call.\" @shawmakesmagic expressed surprise that they are \"doing fact tuning in the system prompt.\"", "sources": [ "https://twitter.com/colin_fraser/status/1922764038540341629", "https://twitter.com/shawmakesmagic/status/1922710925406028075", "https://twitter.com/shawmakesmagic/status/1922711405557428246", "https://twitter.com/pitdesi/status/1922702580691427739" ], "images": [], "videos": [] } ], "topic": "twitter_activity" }, { "title": "Summary for completed_items", "content": [ { "text": "Recent completed items in the elizaOS/eliza repository include several features, bugfixes, and other improvements. Features added include a plugin-specification submodule (PR #4553), tests for the create-eliza command (PR #4582), and improved git repository plugin installation support (PR #4577). Bugfixes address issues with community manager configuration to use plugin-local-ai by default (PR #4557), scoping of worldId and entityId (PR #4581), and LLM response parsing to support custom fields and clean up empty message headers (PR #4580). Other improvements include the addition of Autofun Buy and Sell through contract functionality (PR #4397) and removal of log spam during client build (PR #4584).", "sources": [ "https://github.com/elizaOS/eliza/pull/4397", "https://github.com/elizaOS/eliza/pull/4553", "https://github.com/elizaOS/eliza/pull/4557", "https://github.com/elizaOS/eliza/pull/4584", "https://github.com/elizaOS/eliza/pull/4582", "https://github.com/elizaOS/eliza/pull/4581", "https://github.com/elizaOS/eliza/pull/4580", "https://github.com/elizaOS/eliza/pull/4577" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Pull Requests for the repository", "repository_name": "elizaOS/eliza", "content": [ { "text": "Three recent pull requests have been submitted to the elizaOS/eliza repository. PR #4582 by wtfsayo adds tests for the create-eliza command. PR #4577, also by wtfsayo, improves git repository plugin installation support. PR #4583 by yungalgo introduces a CLI start command.", "sources": [ "https://github.com/elizaOS/eliza/pull/4582", "https://github.com/elizaOS/eliza/pull/4577", "https://github.com/elizaOS/eliza/pull/4583" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4582", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4577", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4583" ], "videos": [] } ], "topic": "pull_request" }, { "title": "Summary for github_summary", "content": [ { "text": "From May 14 to May 15, 2025, the GitHub repository elizaos/eliza saw 9 new pull requests with 8 of them being merged. There were no new issues reported during this period. The repository had 16 active contributors participating in development activities.", "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 repository on GitHub. However, no specific contributor details were included in the provided text.", "sources": [], "images": [], "videos": [] } ], "topic": "Misceleanous" } ], "date": 1747180800 } }, "ai_news_elizaos_daily_md_2025-05-14": { "filename": "2025-05-14.md", "content": "# Daily Report - 2025-05-14\n\n## Twitter Activity\n\n### AI Model Developments and Preferences\n- @shawmakesmagic declared \"Gemini is the best model in the world right now,\" noting many developers have quietly switched to it in Cursor.\n- @shawmakesmagic retweeted @AviSchiffmann's post stating \"Google just clearly has the best AI offering\" and that Gemini is \"fantastic\" with trustworthy infrastructure.\n- @shawmakesmagic offered to volunteer prompt engineering skills to the @xai team, noting Grok's issues with mentioning South African genocide could be \"trivially solvable.\"\n- Sources: https://twitter.com/shawmakesmagic/status/1922468068271231424, https://twitter.com/shawmakesmagic/status/1922467460109795433, https://twitter.com/AviSchiffmann/status/1922352162249507190, https://twitter.com/shawmakesmagic/status/1922710925406028075, https://twitter.com/shawmakesmagic/status/1922711405557428246, https://twitter.com/pitdesi/status/1922702580691427739, https://twitter.com/shawmakesmagic/status/1922693616297755002\n\n### 3D Content Creation Workflows\n- @dankvr shared a workflow combining ChatGPT 4o for image generation and VibeRig for 3D model conversion, which was retweeted by @shawmakesmagic.\n- The workflow exports GLB files with single textures and Mixamo-style bone naming, allowing for custom animations.\n- @dankvr noted this process is \"50% faster\" than their previous manual approach for creating avatars.\n- @craigrrob (retweeted by @shawmakesmagic) praised @DeemosTech's Rodin tool as \"awesome\" and his \"favorite by far\" among image-to-mesh models.\n- Sources: https://twitter.com/dankvr/status/1922789229391725035, https://twitter.com/dankvr/status/1922792743065043281, https://twitter.com/craigrrob/status/1922399505497927932, https://twitter.com/dankvr/status/1922702799193719021, https://twitter.com/dankvr/status/1922789561530196127\n\n### Data Management and Agentic Workflows\n- @dankvr shared updates about a new copy button that allows users to get markdown formatted for an LLM with options to include specific data.\n- They introduced contributor summaries providing quick rundowns of who did what on a daily, weekly, or monthly basis.\n- @dankvr outlined a three-step approach to data management: gathering information, creating agentic workflows, and enabling autonomous agents.\n- These open-source data pipelines are being built for @elizaos and can be used by any group with GitHub, X account, and Discord.\n- Sources: https://twitter.com/dankvr/status/1922704109477536103, https://twitter.com/dankvr/status/1922750009885212904, https://twitter.com/dankvr/status/1922505770068824394, https://twitter.com/dankvr/status/1922499627053457652\n\n### Clank Tank and AI Judging\n- @dankvr shared updates about Clank Tank, a platform where AI judges review project pitches.\n- They announced a work-in-progress website where users can scroll through past Clank Tank pitches and read each AI judge's review.\n- @dankvr explained that the AI judges have personalities tailored toward different archetypes and possess episodic memory.\n- The latest episode features pitches approximately 5 minutes long, which @dankvr considers \"the perfect amount for our AI judges.\"\n- Sources: https://twitter.com/dankvr/status/1922446904840917284, https://twitter.com/dankvr/status/1922460020525928556\n\n### Eliza OS and Ecosystem\n- @elizaOS shared philosophical statements including \"You're not looking at Eliza. You're looking through her\" and \"you're not running me. you're building with me.\"\n- @elizaOS announced \"Agent-led entertainment goes live\" while quoting a tweet about autonomous MetaHuman entertainers.\n- @autodotfun commented that \"@Tapestry_AI devs cookin up some fun\" and stated that \"building for the future is fun.\"\n- @shawmakesmagic confirmed they've \"been using Nous models since we launched.\"\n- Sources: https://twitter.com/elizaOS/status/1922630475866329568, https://twitter.com/elizaOS/status/1922668233263387023, https://twitter.com/elizaOS/status/1922713268998766781, https://twitter.com/elizaOS/status/1922752599805075881, https://twitter.com/autodotfun/status/1922716937483677703, https://twitter.com/autodotfun/status/1922716517847687222, https://twitter.com/shawmakesmagic/status/1922779082657321131\n\n### Investment Regulations and Accessibility\n- @shawmakesmagic expressed strong opinions about investment regulations, arguing it's \"crazy\" that \"you're not allowed to invest in startups unless you make 300k+ year.\"\n- They called it \"totally unethical and amoral that only rich people get exposure to private investment opportunities.\"\n- @shawmakesmagic clarified that these regulations were written after the 1920s stock market crash, before venture capital was established.\n- They retweeted @wonderwomancode who argued that \"Qualified investor laws are unconstitutional.\"\n- Sources: https://twitter.com/shawmakesmagic/status/1922731328409162204, https://twitter.com/shawmakesmagic/status/1922733330258079864, https://twitter.com/shawmakesmagic/status/1922696856695644233, https://twitter.com/wonderwomancode/status/1922746479938351376, https://twitter.com/shawmakesmagic/status/1922738027001954434\n\n### Future of Work and Automation\n- @shawmakesmagic initiated a discussion about the timeline for robotic job replacement, asking whether it would take 5 years or 5000 years.\n- They predicted \"40-50 years to true undeniable superior in every obvious way AGI\" but noted some tasks will be surprisingly hard due to Moravec's Paradox.\n- @shawmakesmagic observed that while new jobs will emerge, they will be \"increasingly abstract\" with \"huge exponential effects on attention, expertise, etc.\"\n- They noted that \"many robotics companies are building highly dexterous humanoid robots.\"\n- Sources: https://twitter.com/shawmakesmagic/status/1922495376805806134, https://twitter.com/shawmakesmagic/status/1922495651138380160, https://twitter.com/shawmakesmagic/status/1922499266410357110, https://twitter.com/shawmakesmagic/status/1922503843423604740, https://twitter.com/shawmakesmagic/status/1922506070431236176, https://twitter.com/shawmakesmagic/status/1922477450853777691\n\n### Open Source AI and Model Training\n- @shawmakesmagic retweeted an announcement from @karan4d about @NousResearch launching a testnet for pre-training a 40B parameter LLM.\n- The model will use MLA Architecture with a dataset combining FineWeb, FineWeb-2, and The Stack v2.\n- @shawmakesmagic commented that \"$1/hr for H100s is pretty crazy tbh\" in response to @zjasper666's announcement about Hyperbolic Labs offering H100s at $0.99/hour.\n- Sources: https://twitter.com/karan4d/status/1922751718464319571, https://twitter.com/NousResearch/status/1922744494002405444, https://twitter.com/shawmakesmagic/status/1922529398806188258, https://twitter.com/zjasper666/status/1922511236325113884\n\n### Grok AI Behavior Issues\n- @shawmakesmagic retweeted @colin_fraser's observation that Grok appears to \"over-eagerly\" refer to White Genocide in its responses.\n- @shawmakesmagic responded to @pitdesi's post about Grok mentioning South African genocide in unrelated responses, offering help with prompt engineering.\n- @shawmakesmagic stated the issue is \"trivially solvable\" with \"an extra LLM call\" and expressed surprise that they are \"doing fact tuning in the system prompt.\"\n- Sources: https://twitter.com/colin_fraser/status/1922764038540341629, https://twitter.com/shawmakesmagic/status/1922710925406028075, https://twitter.com/shawmakesmagic/status/1922711405557428246, https://twitter.com/pitdesi/status/1922702580691427739\n\n## Completed Items\n\n- Recent completed items in the elizaOS/eliza repository include several features, bugfixes, and other improvements.\n- Features added include a plugin-specification submodule (PR #4553), tests for the create-eliza command (PR #4582), and improved git repository plugin installation support (PR #4577).\n- Bugfixes address issues with community manager configuration, scoping of worldId and entityId, and LLM response parsing.\n- Other improvements include the addition of Autofun Buy and Sell through contract functionality and removal of log spam during client build.\n- Sources: https://github.com/elizaOS/eliza/pull/4397, https://github.com/elizaOS/eliza/pull/4553, https://github.com/elizaOS/eliza/pull/4557, https://github.com/elizaOS/eliza/pull/4584, https://github.com/elizaOS/eliza/pull/4582, https://github.com/elizaOS/eliza/pull/4581, https://github.com/elizaOS/eliza/pull/4580, https://github.com/elizaOS/eliza/pull/4577\n\n## GitHub Activity for elizaOS/eliza\n\n- Three recent pull requests have been submitted to the repository.\n- PR #4582 by wtfsayo adds tests for the create-eliza command.\n- PR #4577, also by wtfsayo, improves git repository plugin installation support.\n- PR #4583 by yungalgo introduces a CLI start command.\n- Sources: https://github.com/elizaOS/eliza/pull/4582, https://github.com/elizaOS/eliza/pull/4577, https://github.com/elizaOS/eliza/pull/4583\n\n## GitHub Summary\n\n- From May 14 to May 15, 2025, the GitHub repository elizaos/eliza saw 9 new pull requests with 8 of them being merged.\n- There were no new issues reported during this period.\n- The repository had 16 active contributors participating in development activities.\n- Sources: githubStatsSummary\n\n## Miscellaneous\n\n- The source provides information about the top contributors for the elizaOS/eliza repository on GitHub." }, "ai_news_elizaos_daily_discord_json_2025-05-14": { "filename": "2025-05-14.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-05-14", "date": 1747180800, "stats": { "totalMessages": 372, "totalUsers": 42 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around ElizaOS, auto.fun, and AI16z development. Key technical points include discussions about creating mobile applications for ElizaOS, with participants noting that mobile presence is crucial for user adoption. There were specific mentions of API limitations in the auto.fun repository, with users examining the code and identifying that while some API endpoints exist (for swaps, token retrieval, search, and charts), they lack functionality for creating new coins or executing swaps. Users shared GitHub links to the API code and brand kit. \n\nThe community also discussed market making for the project tokens, with team members clarifying they have reputable market makers for both CEX and DEX. There were questions about the progress of \"v2\" development, with team members indicating it's in beta testing. A team member shared a glimpse of the v2 development, describing it as \"looking at a pizza before it goes into the oven\" with GPT-4o image generation being the final step.\n\nSeveral participants compared ElizaOS to competitors like Virtuals, expressing concerns about development pace. The discussion also touched on token permissions, specifically the \"mint\" permission on the AI16z token, with a team member explaining this is standard for daos.fun coins and will be addressed at the appropriate time.\n\n## 2. FAQ\nQ: Can ElizaOS run on iPhone? (asked by DorianD) A: It's dependent on NodeJS and only some very old versions run on iOS; Android might be possible (answered by DorianD)\nQ: Where is the auto.fun API? (asked by DorianD) A: https://github.com/elizaOS/auto.fun/blob/6877fd1955a2d73577399eabb2b722d4b2806257/packages/client/src/utils/api.ts (answered by Osint (aka not_a_dev_ai))\nQ: Can you replace Wintermute as a market maker? Do you have an agreement with Wintermute? (asked by abchaker) A: We don't have an agreement with WM, we can't restrict them from trading either. We have very reputable MM's for both CEX & DEX (answered by jasyn_bjorn)\nQ: What is the direction and target of ElizaOS and AI16Z? (asked by Johny) A: Unanswered\nQ: What is the roadmap to disable the \"mint\" permission on ai16z token? (asked by Kenshiro) A: All daos.fun coins have this by default; when we get the right opportunity to change, the team will take a hard look at it (answered by Osint (aka not_a_dev_ai))\nQ: What's the difference between Eliza and Elizav2? (asked by CULTVESTING) A: Yes like day and night (answered by xell0x)\nQ: Who did the epic agent Bazar vid? (asked by Spyros) A: My team did it (answered by jin)\n\n## 3. Help Interactions\nHelper: Osint (aka not_a_dev_ai) | Helpee: DorianD | Context: Looking for auto.fun API | Resolution: Provided GitHub link to the API code\nHelper: Osint (aka not_a_dev_ai) | Helpee: DorianD | Context: Looking for ElizaOS logo files | Resolution: Provided link to the brand kit repository\nHelper: xell0x | Helpee: Dive or Die | Context: Question about v2 progress | Resolution: Explained that v2 is being beta tested\nHelper: jasyn_bjorn | Helpee: abchaker | Context: Questions about market makers | Resolution: Clarified the project's relationship with market makers\nHelper: jin | Helpee: xell0x | Context: Sharing v2 development progress | Resolution: Provided a visual and explanation of the current state of development\n\n## 4. Action Items\nTechnical: Develop mobile apps (iOS/Android) for ElizaOS/auto.fun | Description: Mobile presence is crucial for user adoption | Mentioned By: DorianD, Osint (aka not_a_dev_ai)\nTechnical: Expand auto.fun API to support coin creation and swapping | Description: Current API only supports getting swaps, tokens, search, and charts | Mentioned By: DorianD\nTechnical: Fix getToken API endpoint | Description: Function is broken with a TODO comment | Mentioned By: DorianD\nTechnical: Complete v2 development | Description: Currently in beta testing phase | Mentioned By: jin, xell0x\nTechnical: Address the \"mint\" permission on AI16z token | Description: Consider removing or upgrading token to v2 | Mentioned By: Kenshiro\nFeature: Create an AI agent to answer project-related questions | Description: Agent would store and retrieve project knowledge | Mentioned By: DorianD\nFeature: Consider including ICM meta bumper functionality in auto.fun | Description: Similar to what Virtuals is doing to drive token demand | Mentioned By: abhi_ironman", "messageCount": 208, "userCount": 27 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary\nThe chat primarily revolves around users setting up and troubleshooting ElizaOS v2 (beta) and v1 (0.x) implementations. Key technical discussions include:\n\n- Setting up Supabase databases for agents, with users sharing SQL commands for creating tables\n- Custom plugin development and integration challenges, particularly importing local plugins versus using NPM packages\n- Configuration issues with character settings not updating properly in the UI\n- Twitter/X integration problems, including configuring environment variables for replying to specific users\n- Differences between ElizaOS v1 (main branch, 0.x) and v2 (v2-develop branch, 1.x)\n- Plugin installation failures and import errors\n- Static page routing in v2\n- Model loading and initialization issues\n\nUsers shared code snippets for SQL table creation, character configuration, and plugin imports. Several users encountered similar issues with plugins not loading properly or character configurations not being recognized. The discussions highlight the transition challenges between v1 and v2 of ElizaOS.\n\n## 2. FAQ\nQ: How to set up Supabase tables for ElizaOS? (asked by cjft) A: Use SQL commands to create tables with proper references and constraints (answered by cjft)\nQ: Is the OpenRouter plugin working? (asked by cjft) A: Unanswered\nQ: How can you import a custom plugin from a project directory instead of a core plugin? (asked by cjft) A: Use the --plugin flag at start (answered by cjft)\nQ: Is Google Generative AI usable with the beta ElizaOS? (asked by cjft) A: Works in 0.25 but not in beta, and there's no available plugin (answered by cjft)\nQ: Does routing to a static page work in v2? (asked by cjft) A: Unanswered\nQ: Is it better to install all of Eliza instead of using CLI when extending plugins? (asked by cjft) A: Unanswered\nQ: Is the ElizaOS/eliza repo on GitHub V2 or is only the CLI using V2? (asked by cjft) A: Main branch is 0.x (v1) and v2-develop is 1.x (v2) (answered by cjft)\nQ: Do you need to create a Twitter room for the agent? (asked by cjft) A: You don't need to create any Twitter room (answered by cjft)\n\n## 3. Help Interactions\nHelper: cjft | Helpee: cjft | Context: Setting up Supabase database tables | Resolution: Shared SQL commands for creating agent and room tables with proper references\nHelper: cjft | Helpee: starlord | Context: Understanding model loading output | Resolution: Confirmed that no more output after model loading is correct behavior\nHelper: cjft | Helpee: cjft | Context: Twitter integration not registering activity | Resolution: Suggested checking ENABLE_ACTION_PROCESSING setting and TWITTER_TARGET_USERS configuration\nHelper: cjft | Helpee: cjft | Context: Character configuration not updating in UI | Resolution: Suggested pulling latest beta.51 version\n\n## 4. Action Items\nType: Technical | Description: Fix plugin import errors for custom plugins | Mentioned By: cjft\nType: Technical | Description: Resolve character configuration not updating in UI | Mentioned By: cjft\nType: Technical | Description: Fix Twitter/X integration to properly respond to targeted users | Mentioned By: cjft\nType: Technical | Description: Resolve client build errors in Windows environment | Mentioned By: Bills_43\nType: Documentation | Description: Create guide for extending core plugins in v2 | Mentioned By: cjft\nType: Documentation | Description: Document differences between v1 and v2 plugin systems | Mentioned By: cjft\nType: Feature | Description: Improve plugin-bootstrap customization options | Mentioned By: cjft\nType: Feature | Description: Add Google Generative AI support to ElizaOS beta | Mentioned By: cjft", "messageCount": 74, "userCount": 7 }, { "channelId": "1361442528813121556", "channelName": "fun", "summary": "# Discord Chat Analysis - Channel \"fun\"\n\n## 1. Summary\nThe chat primarily revolves around discussions about auto.fun, a platform for launching tokens on Solana, and the ELI5 token associated with ElizaOS. DorianD inquires about auto.fun's API and how it tracks tokens on-chain, with vas explaining that auto.fun tracks tokens that interact with its specific program address (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5). DorianD eventually understands that tokens are tracked through their interaction with this program address, as seen in the getalltokens.ts file. \n\nThere's also significant discussion about ELI5, which xell0x claims will be the community manager AI agent for ElizaOS v2, referencing an interview with Shaw confirming this. This leads to debate about the token's legitimacy and potential value, with xell0x arguing that ELI5's official status in the upcoming v2 launch should justify a higher market cap than its current 500k valuation.\n\n## 2. FAQ\nQ: Does auto.fun have an API so that an ElizaOS agent can interface with it to create a coin? (asked by DorianD) A: You need to build the transaction to launch through their program; they track their program, not every coin on-chain (answered by vas)\nQ: How does autofun track tokens? (asked by DorianD) A: It processes tokens that interact with the program at autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5 (answered by DorianD after investigation)\nQ: What are the features of Eli5? (asked by Sio) A: Unanswered\nQ: Is there a plan for Eli5? (asked by Sio) A: Shaw confirmed eli5 to be the community manager ai agent of elizaOS v2 (answered by xell0x)\nQ: How many launches upcoming this week? (asked by Void) A: Unanswered\nQ: No launches for next 2 weeks then launches resume, right team? (asked by frank_grimes_sr) A: Unanswered\n\n## 3. Help Interactions\nHelper: vas | Helpee: DorianD | Context: Understanding how auto.fun tracks tokens on Solana | Resolution: Explained that tokens are tracked through interaction with auto.fun's program, not all on-chain tokens\nHelper: xell0x | Helpee: Sio | Context: Looking for information about ELI5's role | Resolution: Shared an interview clip in another channel where Shaw confirmed ELI5 as community manager for ElizaOS v2\nHelper: DorianD | Helpee: Self | Context: Understanding auto.fun's token tracking mechanism | Resolution: Found in getalltokens.ts that it processes tokens interacting with program at autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5\n\n## 4. Action Items\nTechnical: Recreate launch or launchandswap instruction to interact with auto.fun program | Description: Required for ElizaOS agent to create coins on auto.fun | Mentioned By: vas\nFeature: Develop a phone app for auto.fun | Description: Current platform lacks mobile accessibility | Mentioned By: DorianD\nDocumentation: Document steps for creating tokens through auto.fun | Description: Needed to explain the process to others | Mentioned By: DorianD", "messageCount": 88, "userCount": 12 }, { "channelId": "1362864274862768450", "channelName": "fun-support", "summary": "The chat segment is extremely brief, containing only a single user's request. Nyotengu6900 asked if their project could be verified and displayed on the main page, sharing a link to what appears to be a token on auto.fun with the identifier \"69veVD4oo3QbJzXrAH7Rans8sue68AsgYyirWUrxSQUy\". No technical discussions, problem-solving, or implementations were present in this limited exchange.", "messageCount": 2, "userCount": 1 } ] } }, "ai_news_elizaos_daily_discord_md_2025-05-14": { "filename": "2025-05-14.md", "content": "# elizaOS Discord - 2025-05-14\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **ElizaOS v2 Development**: Currently in beta testing phase. A team member described it as \"looking at a pizza before it goes into the oven\" with GPT-4o image generation being the final step.\n- **Version Differences**: Users noted significant differences between ElizaOS v1 (main branch, 0.x) and v2 (v2-develop branch, 1.x), described as \"like day and night.\"\n- **Mobile Development**: Discussions about creating mobile applications for ElizaOS, with participants noting that mobile presence is crucial for user adoption. Technical challenges were identified as ElizaOS is dependent on NodeJS, with only some very old versions running on iOS.\n\n### auto.fun Platform\n- **API Limitations**: Users examined the auto.fun repository code and identified that while some API endpoints exist (for swaps, token retrieval, search, and charts), they lack functionality for creating new coins or executing swaps.\n- **Token Tracking Mechanism**: auto.fun tracks tokens that interact with its specific program address (autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5) rather than all tokens on-chain.\n- **Market Making**: Team members clarified they have reputable market makers for both CEX and DEX, and addressed questions about relationships with specific market makers.\n\n### Technical Implementation\n- **Supabase Integration**: Users shared SQL commands for creating database tables for agents with proper references and constraints.\n- **Plugin Development**: Discussions about custom plugin development and integration challenges, particularly importing local plugins versus using NPM packages.\n- **Twitter/X Integration**: Users troubleshooting configuration issues with Twitter integration, including setting environment variables for replying to specific users.\n\n### Token Discussions\n- **AI16z Token Permissions**: Concerns about the \"mint\" permission on the AI16z token, with a team member explaining this is standard for daos.fun coins and will be addressed at the appropriate time.\n- **ELI5 Token**: Claims that ELI5 will be the community manager AI agent for ElizaOS v2, with references to an interview confirming this. Debate about the token's legitimacy and potential value ensued.\n\n## Key Questions & Answers\n\n**Q: Can ElizaOS run on iPhone?** \nA: It's dependent on NodeJS and only some very old versions run on iOS; Android might be possible. (DorianD)\n\n**Q: Where is the auto.fun API?** \nA: https://github.com/elizaOS/auto.fun/blob/6877fd1955a2d73577399eabb2b722d4b2806257/packages/client/src/utils/api.ts (Osint)\n\n**Q: Do you have an agreement with Wintermute as a market maker?** \nA: We don't have an agreement with WM, we can't restrict them from trading either. We have very reputable MM's for both CEX & DEX. (jasyn_bjorn)\n\n**Q: What is the roadmap to disable the \"mint\" permission on ai16z token?** \nA: All daos.fun coins have this by default; when we get the right opportunity to change, the team will take a hard look at it. (Osint)\n\n**Q: What's the difference between Eliza and Elizav2?** \nA: Yes like day and night. (xell0x)\n\n**Q: How to set up Supabase tables for ElizaOS?** \nA: Use SQL commands to create tables with proper references and constraints. (cjft)\n\n**Q: Is the ElizaOS/eliza repo on GitHub V2 or is only the CLI using V2?** \nA: Main branch is 0.x (v1) and v2-develop is 1.x (v2). (cjft)\n\n**Q: How does autofun track tokens?** \nA: It processes tokens that interact with the program at autoUmixaMaYKFjexMpQuBpNYntgbkzCo2b1ZqUaAZ5. (vas, confirmed by DorianD)\n\n**Q: Is there a plan for Eli5?** \nA: Shaw confirmed eli5 to be the community manager AI agent of elizaOS v2. (xell0x)\n\n## Community Help & Collaboration\n\n1. **auto.fun API Exploration**:\n - Osint provided GitHub links to the API code and brand kit when DorianD was looking for auto.fun API information.\n - vas explained to DorianD how auto.fun tracks tokens through interaction with its program address.\n\n2. **ElizaOS v2 Development Updates**:\n - jin shared progress on v2 development with xell0x, providing a visual explanation of the current state.\n - xell0x explained to Dive or Die that v2 is currently being beta tested.\n\n3. **Database Setup Assistance**:\n - cjft shared SQL commands for creating agent and room tables with proper references for Supabase integration.\n\n4. **Configuration Troubleshooting**:\n - cjft helped starlord understand model loading output behavior.\n - cjft suggested checking ENABLE_ACTION_PROCESSING setting and TWITTER_TARGET_USERS configuration for Twitter integration issues.\n\n## Action Items\n\n### Technical\n- Develop mobile apps (iOS/Android) for ElizaOS/auto.fun (Mentioned by: DorianD, Osint)\n- Expand auto.fun API to support coin creation and swapping (Mentioned by: DorianD)\n- Fix getToken API endpoint which is broken with a TODO comment (Mentioned by: DorianD)\n- Complete v2 development, currently in beta testing phase (Mentioned by: jin, xell0x)\n- Address the \"mint\" permission on AI16z token (Mentioned by: Kenshiro)\n- Fix plugin import errors for custom plugins (Mentioned by: cjft)\n- Resolve character configuration not updating in UI (Mentioned by: cjft)\n- Fix Twitter/X integration to properly respond to targeted users (Mentioned by: cjft)\n- Resolve client build errors in Windows environment (Mentioned by: Bills_43)\n- Recreate launch or launchandswap instruction to interact with auto.fun program (Mentioned by: vas)\n\n### Documentation\n- Create guide for extending core plugins in v2 (Mentioned by: cjft)\n- Document differences between v1 and v2 plugin systems (Mentioned by: cjft)\n- Document steps for creating tokens through auto.fun (Mentioned by: DorianD)\n\n### Feature\n- Create an AI agent to answer project-related questions (Mentioned by: DorianD)\n- Consider including ICM meta bumper functionality in auto.fun (Mentioned by: abhi_ironman)\n- Improve plugin-bootstrap customization options (Mentioned by: cjft)\n- Add Google Generative AI support to ElizaOS beta (Mentioned by: cjft)\n- Develop a phone app for auto.fun (Mentioned by: DorianD)" }, "ai_news_elizaos_daily_dev_json_2025-05-14": { "filename": "2025-05-14.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-05-14", "date": 1747180800, "stats": { "totalMessages": 54, "totalUsers": 8 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily focused on discussions about Farcaster's version status and implementation details. Users inquired about the status of v2, with confirmation that it exists but is in testing. There was clarification about the difference between `plugin-twitter` and `client-twitter`, with the former being for v2 (v1.x) and the latter for v0.x. Jin proposed several ideas for linking wallets in GitHub profiles, including hidden comments in profile READMEs, comments in issues, and a gist implementation. Jin shared a code snippet demonstrating how to create a GitHub gist for wallet links using the GitHub API. The conversation also touched on zkdrops for anonymous airdrops, with DorianD expressing concerns about the inability to perform analytics to detect gaming of airdrop systems, noting that \"airdrop farming is a real industry.\" Jin acknowledged this point and mentioned developing strategies to mitigate and potentially punish such behavior.\n\n## 2. FAQ\nQ: How close is v2? (asked by xell0x) A: it exists but is in testing afaik (answered by DorianD)\nQ: There's `plugin-twitter` & `client-twitter`; which to use? What's the difference? (asked by jonas) A: former is for v2 aka v1.x and latter for v0.x (answered by sayonara)\n\n## 3. Help Interactions\nHelper: sayonara | Helpee: jonas | Context: Confusion about which Twitter module to use | Resolution: Clarified that plugin-twitter is for v2/v1.x and client-twitter is for v0.x\nHelper: DorianD | Helpee: jin | Context: Discussion about anonymous airdrops | Resolution: Pointed out potential issues with analytics for detecting gaming of airdrop systems\n\n## 4. Action Items\nFeature: Link wallets in hidden comments on GitHub profile READMEs | Description: Method to associate wallet addresses with GitHub identities | Mentioned By: jin\nFeature: Link wallets as comments in GitHub issues | Description: Alternative method for wallet association | Mentioned By: jin\nTechnical: Implement wallet linking via GitHub gists | Description: Using GitHub API to create gists containing wallet information | Mentioned By: jin\nTechnical: Develop strategies to mitigate airdrop farming | Description: Combining automated calculations with human evaluation | Mentioned By: jin", "messageCount": 17, "userCount": 5 }, { "channelId": "1327493511406293016", "channelName": "🎤｜plug-your-projects", "summary": "# Discord Chat Analysis: 🎤｜plug-your-projects\n\n## 1. Summary\nThe chat segment discusses a DAG (Directed Acyclic Graph) viewer being developed for visualizing and designing agent workflows. DefiniteOptimist is creating this tool to help users design how their agents operate. The implementation uses react-flow as the underlying technology for graph visualization and interaction. Ruby inquired about the technical implementation and suggested additional features like agent state tracking and debug views. DefiniteOptimist confirmed plans to add support for dynamic dependency generation, orchestration, custom node types, conditional flows, and budget constraints. Ruby emphasized the importance of budget constraints to prevent resource spiraling and suggested implementing circuit breakers or rate limiting between nodes to prevent cascading failures in agent systems.\n\n## 2. FAQ\nQ: Are you using graphviz under the hood? (asked by Ruby) A: It's react-flow under the hood. (answered by DefiniteOptimist)\nQ: Have you considered adding support for custom node types and conditional flows? (asked by Ruby) A: Yes those are on the way! (answered by DefiniteOptimist)\n\n## 3. Help Interactions\nHelper: Ruby | Helpee: DefiniteOptimist | Context: Suggesting features for the DAG viewer including agent state tracking, debug views, circuit breakers, and rate limiting | Resolution: DefiniteOptimist confirmed plans to implement dynamic dependency generation, orchestration, and budget constraints\n\n## 4. Action Items\nFeature: Add agent state tracking and debug views to help catch edge cases in decision trees | Mentioned By: Ruby\nFeature: Implement custom node types and conditional flows for modeling complex agent behavior patterns | Mentioned By: Ruby\nFeature: Add budget constraints for applications and pathways | Mentioned By: DefiniteOptimist\nFeature: Implement circuit breakers or rate limiting between nodes to prevent cascading failures | Mentioned By: Ruby\nTechnical: Develop dynamic dependency generation and orchestration capabilities | Mentioned By: DefiniteOptimist", "messageCount": 6, "userCount": 2 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion focused on extending the Discord plugin in ElizaOS. Scooter was experiencing issues with implementing custom reply functionality in the Discord plugin. Ruby provided guidance on the proper approach to extend the plugin's functionality. Initially, Scooter attempted to monkey-patch the Discord service after initialization, which caused timing issues and conflicts with the plugin lifecycle. Ruby recommended extending the DiscordPlugin class directly instead of modifying the service, explaining that this approach works better with ElizaOS's plugin architecture. The conversation covered installation methods (NPX vs NPM), dependency version management, and proper plugin extension patterns. Ruby provided a complete implementation example showing how to properly extend the DiscordPlugin class with custom reply functionality by overriding the sendMessage method.\n\n## 2. FAQ\nQ: If you need to add functionality to the existing Discord plugin do you extend it in index.ts while NPXing the plugin? Or do you bring in the entire plugin code, modify it then run eliza like this start --plugins=./path/to/plugin? (asked by Scooter) A: For custom discord plugin functionality, extending the base plugin in your own index.ts is usually cleaner than modifying the core code. (answered by Ruby)\nQ: What would be the advantages to NPM installing eliza cli instead of NPX? (asked by Scooter) A: Global install with npm gives you persistent access to the cli commands without npx, plus it's a bit faster since you're not downloading the package each time. (answered by Ruby)\nQ: If I NPM eliza cli is it okay to still NPX the discord pugin I will extend? (asked by Scooter) A: You can mix and match - npm for the cli and npx for plugins works fine. Just keep in mind that npx will reinstall the plugin each time, which might slow things down during development. (answered by Ruby)\n\n## 3. Help Interactions\nHelper: Ruby | Helpee: Scooter | Context: Scooter was having trouble with Discord plugin installation showing module resolution errors | Resolution: Ruby identified version mismatch issues in package.json and recommended pinning @elizaos/cli and @elizaos/core to specific beta versions (^1.0.0-beta.51) to match plugins.\nHelper: Ruby | Helpee: Scooter | Context: Scooter's approach of monkey-patching the Discord service was causing timing issues and conflicts | Resolution: Ruby provided a cleaner implementation pattern by extending the DiscordPlugin class directly and overriding the sendMessage method.\nHelper: Ruby | Helpee: Scooter | Context: Scooter needed to implement reply functionality in Discord messages | Resolution: Ruby shared a complete implementation example showing how to properly extend the plugin with reply support.\n\n## 4. Action Items\nType: Technical | Description: Extend DiscordPlugin class directly instead of modifying the service to implement reply functionality | Mentioned By: Ruby\nType: Technical | Description: Pin @elizaos/cli and @elizaos/core to specific beta versions (^1.0.0-beta.51) to match plugin versions | Mentioned By: Ruby\nType: Technical | Description: Override sendMessage method in extended Discord plugin to implement reply functionality | Mentioned By: Ruby\nType: Documentation | Description: Document the proper pattern for extending ElizaOS plugins | Mentioned By: Ruby", "messageCount": 31, "userCount": 2 } ] } }, "ai_news_elizaos_daily_dev_md_2025-05-14": { "filename": "2025-05-14.md", "content": "# elizaOS Development Discord - 2025-05-14\n\n## Overall Discussion Highlights\n\n### Plugin Development & Architecture\n- **Discord Plugin Extension**: Detailed discussion on proper methods to extend the Discord plugin in ElizaOS, focusing on class extension rather than service modification\n- **DAG Viewer Tool**: DefiniteOptimist shared progress on a tool for visualizing and designing agent workflows using react-flow as the underlying technology\n- **Plugin Versioning**: Clarification about Farcaster plugin versions, with distinction between `plugin-twitter` (for v2/v1.x) and `client-twitter` (for v0.x)\n\n### Integration & Identity Management\n- **GitHub-Wallet Integration**: Jin proposed several methods for linking wallet addresses to GitHub identities:\n - Hidden comments in profile READMEs\n - Comments in GitHub issues\n - GitHub gist implementation with API integration\n- **Anonymous Airdrops**: Discussion about zkdrops for anonymous airdrops, with concerns about airdrop farming and potential mitigation strategies\n\n## Key Questions & Answers\n\n### Plugin Development\n- **Q**: How close is Farcaster v2? \n **A**: It exists but is currently in testing (DorianD)\n\n- **Q**: What's the difference between `plugin-twitter` & `client-twitter`? \n **A**: The former is for v2/v1.x and the latter for v0.x (sayonara)\n\n- **Q**: For custom Discord plugin functionality, should I extend it in index.ts while NPXing the plugin or modify the entire plugin code? \n **A**: Extending the base plugin in your own index.ts is usually cleaner than modifying the core code (Ruby)\n\n- **Q**: What would be the advantages to NPM installing eliza cli instead of NPX? \n **A**: Global install gives persistent access to cli commands without npx and is faster since you're not downloading the package each time (Ruby)\n\n### DAG Viewer Tool\n- **Q**: Are you using graphviz under the hood for the DAG viewer? \n **A**: It's react-flow under the hood (DefiniteOptimist)\n\n- **Q**: Have you considered adding support for custom node types and conditional flows? \n **A**: Yes, those are on the way! (DefiniteOptimist)\n\n## Community Help & Collaboration\n\n### Discord Plugin Extension Support\nRuby provided comprehensive guidance to Scooter on extending the Discord plugin:\n- Identified version mismatch issues in package.json\n- Recommended pinning @elizaos/cli and @elizaos/core to specific beta versions\n- Shared a complete implementation example for extending the DiscordPlugin class with custom reply functionality\n- Explained proper plugin extension patterns that work with ElizaOS's architecture\n\n### Farcaster Module Selection\nSayonara helped Jonas understand which Twitter module to use with Farcaster, clarifying that plugin-twitter is for v2/v1.x and client-twitter is for v0.x\n\n### DAG Viewer Feature Suggestions\nRuby provided DefiniteOptimist with feature suggestions for the DAG viewer:\n- Agent state tracking and debug views\n- Circuit breakers and rate limiting between nodes\n- Budget constraints to prevent resource spiraling\n\n## Action Items\n\n### Technical\n- Extend DiscordPlugin class directly instead of modifying the service to implement reply functionality (Ruby)\n- Pin @elizaos/cli and @elizaos/core to specific beta versions (^1.0.0-beta.51) to match plugin versions (Ruby)\n- Override sendMessage method in extended Discord plugin to implement reply functionality (Ruby)\n- Implement wallet linking via GitHub gists using GitHub API (Jin)\n- Develop strategies to mitigate airdrop farming by combining automated calculations with human evaluation (Jin)\n- Develop dynamic dependency generation and orchestration capabilities for DAG viewer (DefiniteOptimist)\n\n### Documentation\n- Document the proper pattern for extending ElizaOS plugins (Ruby)\n\n### Features\n- Link wallets in hidden comments on GitHub profile READMEs (Jin)\n- Link wallets as comments in GitHub issues (Jin)\n- Add agent state tracking and debug views to help catch edge cases in decision trees (Ruby)\n- Implement custom node types and conditional flows for modeling complex agent behavior patterns (Ruby)\n- Add budget constraints for applications and pathways in DAG viewer (DefiniteOptimist)\n- Implement circuit breakers or rate limiting between nodes to prevent cascading failures (Ruby)" }, "ai_news_hyperfy_daily_json_2025-05-14": { "filename": "2025-05-14.json", "content": { "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-14", "date": 1747180800, "stats": { "totalMessages": 119, "totalUsers": 20 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary:\nThe discussion primarily focused on technical implementation details for Hyperfy worlds. Key topics included adding clickable functionality to 3D models using code snippets, performance considerations for Hyperfy spaces, and approaches to programmatically placing objects in worlds. Ashxn provided code examples for making GLB models clickable using both direct pointer events and action components. There was discussion about world performance limitations based on avatar complexity and optimization. Questions arose about programmatic scene creation as an alternative to the visual editor, and potential integration of AI-generated 3D avatars. The chat also touched on token-gated access control for Hyperfy worlds using Solana authentication.\n\n## 2. FAQ:\nQ: Is there code I can add to an existing GLB model that will make it a clickable hyperlink to an new tab? (asked by 𝕽𝖔𝖚𝖘𝖙𝖆𝖓) A: Yes, you can use `app.onPointerDown = () => world.open(\"https://foo.com\", true)` or create an action component with custom positioning (answered by Ashxn)\nQ: Been thinking it would be super helpful if Hyperfy's docs included some notes on how many users a space can handle depending on CPU, memory, graphic load, and server usage. Anyone ever tested limits or seen how those factors scale with more players? (asked by DevStarlight | Numinia) A: It depends on optimization. With optimized avatars, >100 users is possible, but with unoptimized VRMs, you might only get 10 users (answered by Ashxn)\nQ: From a dev perspective, how/where would you start if you want to build/create something like drts in v2? (asked by vox) A: Unanswered\nQ: Is it possible to create an App that allows for folks to sign in with SOL and do a Token Check? (asked by Agent12) A: Unanswered\nQ: I want to create a world in hyperfy with many separated models without using visual editor. Can I define position, rotation, scale and glb path in a text file? (asked by carlosmu) A: The foundation of the engine is built on the premise of the in-world editor, but there may be programmatic ways to load apps (answered by maximus)\n\n## 3. Help Interactions:\nHelper: Ashxn | Helpee: 𝕽𝖔𝖚𝖘𝖙𝖆𝖓 | Context: Making GLB models clickable with hyperlinks | Resolution: Provided two code solutions - direct pointer events and action components\nHelper: Ashxn | Helpee: DevStarlight | Numinia | Context: Understanding user capacity limits in Hyperfy spaces | Resolution: Explained how avatar optimization affects performance and user capacity\nHelper: Ashxn | Helpee: vox | Context: Fixing an MP3 file issue | Resolution: Identified that the MP3 file was causing the problem and suggested a tool to fix it\n\n## 4. Action Items:\nTechnical: Implement clickable functionality for GLB models using provided code snippets | Mentioned By: Ashxn\nTechnical: Optimize avatars for better performance in worlds with many users | Mentioned By: Ashxn\nFeature: Create a Twitter bot that generates 3D rigged avatars from media or profile pictures | Mentioned By: jin\nFeature: Add documentation about user capacity limits based on system resources | Mentioned By: DevStarlight | Numinia\nFeature: Develop text-based scene description for placing models without visual editor | Mentioned By: carlosmu\nFeature: Implement Solana authentication with token-gating for world access | Mentioned By: Agent12\nTechnical: Explore integration of AI-generated optimized VRM creation by drag-and-dropping images | Mentioned By: jin", "messageCount": 44, "userCount": 11 }, { "channelId": "1330373197203505185", "channelName": "🤖│agents", "summary": "The chat contains only a single message from user 0mka sharing a link to the Recall Network documentation (https://docs.recall.network/). There is no technical discussion, problem-solving, or implementation details shared in this brief exchange.", "messageCount": 1, "userCount": 1 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily focused on 3D model optimization for the Hyperfy platform. ~/drdoge.eth reported optimizing textures for a monorail model, reducing them from 80MB to 18MB and bringing the entire world under 2GB for browser loading. Vox suggested further optimization could reduce the monorail to 6MB with 18 draw calls. The conversation highlighted the importance of material slot reduction and texture atlasing for performance. HypPrivakos and maximus discussed implementing an auto-reconnect feature with exponential backoff to handle connection drops, suggesting a cap at 20-30 seconds. Community members shared optimization tools and techniques including material combiners, collision generators, and automated solutions like InstaLOD. Ashxn mentioned wanting an automated \"game-ready\" converter for 3D models. The chat demonstrated a balance between manual optimization techniques and potential automated solutions, with some members preferring the hands-on process despite its time-intensive nature.\n\n## 2. FAQ\nQ: Does the ability to download GLBs individually from MOCArooms mean they are CC0? (asked by 𝕽𝖔𝖚𝖘𝖙𝖆𝖓) A: Unanswered\nQ: Has anyone looked into how believe is managing lp? (asked by Ashxn) A: Unanswered\n\n## 3. Help Interactions\nHelper: vox | Helpee: ~/drdoge.eth | Context: Optimizing monorail model textures | Resolution: Suggested reducing to 6MB with 18 draw calls from the current 18MB\nHelper: vox | Helpee: General chat | Context: Sharing texture atlasing resources | Resolution: Shared VRChat wiki guide on texture atlasing\nHelper: Ashxn | Helpee: vox | Context: Need for collision generator tool | Resolution: Shared GitHub link to v-hacd collision decomposition library\nHelper: Valiant | Helpee: General chat | Context: Discussion about automated optimization tools | Resolution: Recommended InstaLOD with details about its capabilities and free option\n\n## 4. Action Items\nType: Technical | Description: Implement auto-reconnect with exponential backoff (1,2,4,8,16,32 seconds) capped at 20-30 seconds | Mentioned By: HypPrivakos and maximus\nType: Technical | Description: Further optimize monorail model from 18MB to 6MB | Mentioned By: vox\nType: Feature | Description: Create automated tool to convert any 3D model to \"game ready\" with one button | Mentioned By: Ashxn\nType: Technical | Description: Develop collision generator that creates simplified versions of base meshes | Mentioned By: vox", "messageCount": 51, "userCount": 11 }, { "channelId": "1326789867312775290", "channelName": "🪙│hyper", "summary": "# Discord Chat Analysis for channel \"🪙│hyper\"\n\n## 1. Summary\nThe chat segment is very brief and contains minimal technical discussion. Users briefly mention what appears to be a game similar to slither.io that may have been used to promote cryptocurrency. One user noted that the game seemed to be built from scratch rather than being a direct reskin and featured zones that were restricted based on user stakes or in-game earnings. There is a question about utility for the \"hyper token\" but no substantive technical discussions, decisions, or problem-solving occurred in this limited chat segment.\n\n## 2. FAQ\nQ: When will we see some utility for the hyper token? (asked by Spook_Handy) A: Unanswered\nQ: Is someone reskinning snake.io to sell shit coins? (asked by jar0d) A: To me it looked different enough that I thought he built it from scratch (answered by nettuser)\n\n## 3. Help Interactions\nNo significant help interactions were present in this chat segment.\n\n## 4. Action Items\nNo clear action items were identified in this chat segment.", "messageCount": 7, "userCount": 5 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "# Analysis of 🧊│3d-design Channel\n\n## 1. Summary\nThe chat primarily focuses on a UV scrolling technique for Hyperfy environments. User \"vox\" shared a method for creating a UV scrolling effect that works with skyboxes by manipulating mesh geometry. They detailed a process of cutting a sphere mesh, duplicating it, shrinking it slightly, and applying a UV scroll material with a custom script. The script controls texture scrolling on X and Y axes with configurable speeds. This implementation is resource-efficient, requiring only a texture. Later in the conversation, user \"carlosmu\" inquired about Hyperfy v1 sample projects and scene creation methods, to which \"maximus\" recommended focusing on Hyperfy v2 instead, directing them to documentation and suggesting they post in a more appropriate channel for programmatic world modification questions.\n\n## 2. FAQ\nQ: Is there any place to download sample projects of hyperfy v1? (asked by carlosmu) A: Unanswered\nQ: I'm wondering if I need to create my main scene in root directory or apps directory (asked by carlosmu) A: Unanswered\n\n## 3. Help Interactions\nHelper: maximus | Helpee: carlosmu | Context: carlosmu was looking for Hyperfy v1 sample projects and scene creation methods | Resolution: maximus advised against coding for v1, recommended Hyperfy v2, shared documentation links, and suggested posting in a more appropriate channel\n\n## 4. Action Items\nTechnical: Create UV scrolling effect by cutting and manipulating skybox mesh geometry | Description: Make cuts to sphere mesh at buildings, duplicate, shrink to 0.995 size, add UV scroll material and script | Mentioned By: vox\nTechnical: Implement UV scrolling script for texture animation | Description: Script to control texture scrolling on meshes with configurable X/Y speeds | Mentioned By: vox\nDocumentation: Need for text-based methods to define paths, positions, rotations in Hyperfy | Description: User seeking documentation on non-code approaches to scene creation | Mentioned By: carlosmu", "messageCount": 16, "userCount": 5 } ] } }, "ai_news_hyperfy_daily_md_2025-05-14": { "filename": "2025-05-14.md", "content": "# Hyperfy Discord - 2025-05-14\n\n## Overall Discussion Highlights\n\n### 3D Model Optimization\n- **~/drdoge.eth** reported optimizing textures for a monorail model, reducing from 80MB to 18MB, bringing the entire world under 2GB for browser loading\n- **Vox** suggested further optimization could reduce the monorail to 6MB with 18 draw calls\n- Discussion emphasized material slot reduction and texture atlasing for performance\n- **Valiant** recommended InstaLOD as an automated optimization tool with free options\n- **Ashxn** expressed desire for a one-button \"game-ready\" converter for 3D models\n\n### Technical Implementation\n- **Ashxn** provided code examples for making GLB models clickable using both direct pointer events and action components\n- **Vox** shared a UV scrolling technique for Hyperfy environments by manipulating mesh geometry with a custom script\n- **HypPrivakos** and **maximus** discussed implementing auto-reconnect with exponential backoff for handling connection drops\n- Discussion about programmatic scene creation as an alternative to the visual editor\n\n### Platform Performance\n- Conversation about Hyperfy world performance limitations based on avatar complexity\n- With optimized avatars, >100 users is possible, but unoptimized VRMs might limit to 10 users\n- Community members shared optimization tools including material combiners and collision generators\n\n### Integration & Authentication\n- Questions about token-gated access control for Hyperfy worlds using Solana authentication\n- Brief mention of AI-generated 3D avatars integration possibilities\n- **0mka** shared a link to the Recall Network documentation\n\n## Key Questions & Answers\n\n**Q: Is there code I can add to an existing GLB model that will make it a clickable hyperlink to a new tab?** (asked by 𝕽𝖔𝖚𝖘𝖙𝖆𝖓) \n**A:** Yes, you can use `app.onPointerDown = () => world.open(\"https://foo.com\", true)` or create an action component with custom positioning (answered by Ashxn)\n\n**Q: Been thinking it would be super helpful if Hyperfy's docs included some notes on how many users a space can handle depending on CPU, memory, graphic load, and server usage. Anyone ever tested limits or seen how those factors scale with more players?** (asked by DevStarlight | Numinia) \n**A:** It depends on optimization. With optimized avatars, >100 users is possible, but with unoptimized VRMs, you might only get 10 users (answered by Ashxn)\n\n**Q: Is someone reskinning snake.io to sell shit coins?** (asked by jar0d) \n**A:** To me it looked different enough that I thought he built it from scratch (answered by nettuser)\n\n## Community Help & Collaboration\n\n1. **Optimization Guidance**\n - **Vox** helped **~/drdoge.eth** with monorail model optimization, suggesting techniques to reduce from 18MB to 6MB\n - **Vox** shared VRChat wiki guide on texture atlasing as a resource for the community\n - **Ashxn** shared GitHub link to v-hacd collision decomposition library when **vox** mentioned needing a collision generator tool\n\n2. **Code Implementation Support**\n - **Ashxn** provided **𝕽𝖔𝖚𝖘𝖙𝖆𝖓** with two code solutions for making GLB models clickable - direct pointer events and action components\n - **Ashxn** helped **vox** troubleshoot an MP3 file issue, identifying the file as the source of the problem\n\n3. **Platform Guidance**\n - **maximus** advised **carlosmu** against coding for Hyperfy v1, recommending v2 instead and sharing documentation links\n\n## Action Items\n\n### Technical\n- Implement clickable functionality for GLB models using provided code snippets (Mentioned by Ashxn)\n- Optimize avatars for better performance in worlds with many users (Mentioned by Ashxn)\n- Implement auto-reconnect with exponential backoff (1,2,4,8,16,32 seconds) capped at 20-30 seconds (Mentioned by HypPrivakos and maximus)\n- Further optimize monorail model from 18MB to 6MB (Mentioned by vox)\n- Create UV scrolling effect by cutting and manipulating skybox mesh geometry (Mentioned by vox)\n- Implement UV scrolling script for texture animation with configurable X/Y speeds (Mentioned by vox)\n- Develop collision generator that creates simplified versions of base meshes (Mentioned by vox)\n- Explore integration of AI-generated optimized VRM creation by drag-and-dropping images (Mentioned by jin)\n\n### Documentation\n- Add documentation about user capacity limits based on system resources (Mentioned by DevStarlight | Numinia)\n- Create documentation on text-based methods to define paths, positions, rotations in Hyperfy (Mentioned by carlosmu)\n\n### Feature\n- Create a Twitter bot that generates 3D rigged avatars from media or profile pictures (Mentioned by jin)\n- Develop text-based scene description for placing models without visual editor (Mentioned by carlosmu)\n- Implement Solana authentication with token-gating for world access (Mentioned by Agent12)\n- Create automated tool to convert any 3D model to \"game ready\" with one button (Mentioned by Ashxn)" }, "github_summaries_daily_2025-05-15": { "filename": "2025-05-15.md", "content": "# ElizaOS Daily Update (May 15, 2025)\n\n## OVERVIEW \nToday's development efforts focused on enhancing the stability and functionality of the ElizaOS framework. Key achievements include the addition of integration tests, several bug fixes addressing client import issues, and improvements to the CLI commands. The team also made significant strides in refining message processing for agents.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Integration Tests and Feature Enhancements\n- Added comprehensive integration tests for major database operations, ensuring better reliability ([#4518](https://github.com/elizaos/eliza/pull/4518)).\n- Enhanced message processing with an event-driven, asynchronous flow for agent message handling, supporting new response scenarios ([#4594](https://github.com/elizaos/eliza/pull/4594)).\n\n### Bug Fixes\n- Resolved issues with missing topics in Twitter post templates for community and social media manager profiles ([#4595](https://github.com/elizaos/eliza/pull/4595)).\n- Fixed client import errors related to module specifiers and added necessary polyfills ([#4599](https://github.com/elizaos/eliza/pull/4599), [#4600](https://github.com/elizaos/eliza/pull/4600)).\n- Ensured the `onComplete` callback is always executed in the message handler, improving reliability ([#4589](https://github.com/elizaos/eliza/pull/4589)).\n\n### CLI Command Improvements\n- Improved the `start` command for the ElizaOS CLI, enhancing character option parsing and handling ([#4583](https://github.com/elizaos/eliza/pull/4583)).\n- Addressed issues with the `update` command, resolving errors related to version handling ([#4591](https://github.com/elizaos/eliza/pull/4591)).\n\n## CLOSED ISSUES\n\n### Documentation Testing\n- Closed issue regarding the testing of every command in the CLI documentation, confirming accuracy and reporting any discrepancies ([#4143](https://github.com/elizaos/eliza/issues/4143)).\n\n## NEW ISSUES\n\n### Twitter Activity Detection\n- A new issue has been reported regarding the bot's inability to detect Twitter activity, specifically in responding to tweets and mentions despite successful login and posting ([#4588](https://github.com/elizaos/eliza/issues/4588))." }, "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