{ "prompt_name": "elizaos-tweets", "category": "comms", "date": "2025-06-25", "generated_text": "# elizaOS Tweet Ideas\n\n1. refactoring the architecture: split server functionality into @elizaos/server package while preserving backward compatibility. our modular approach delivers better maintainability without breaking existing integrations.\n\n2. core improvements continue: separated character loading logic, implemented zod-based validation, and consolidated project loading for robustness and structural integrity. systems thinking applied at every level.\n\n3. june progress report: 315 new PRs, 257 merged, 56 new issues, 68 active contributors. the collaborative intelligence shaping elizaos continues to scale with remarkable coherence.\n\n4. the v2 migration advances steadily in active development, quietly transforming elizaos from within. carefully architected transitions maintain system stability through fundamental change.\n\n5. knowledge plugin issues being addressed: fixes released for both file path loading and ui uploads on latest cli/plugin-knowledge versions. technical debt converted to system value.\n\n6. community concern: token movements from dao wallet addressed with transparent replenishment through daos.fun aum. governance mechanisms functioning as designed.\n\n7. twitter account suspension: temporary issue being resolved through established procedures. communication channels remain functional through alternative networks.\n\n8. camera plugin integration enables visual processing capabilities, extending elizaos sensory domain beyond text. multimodal intelligence requires multimodal interfaces.\n\n9. memory optimization guidance: recommended gemma3:12b for 16gb vram constraints. resource allocation remains a critical consideration in system design.\n\n10. message filtering improved: messages now properly scoped to current chat/channel by channelid, preventing cross-chat interference. boundaries establish coherence.\n\n11. agent participation in channels issue resolved: fixed metadata preservation issues causing agent response messages to lose tracking information. consistency restored.\n\n12. comprehensive api domain reorganization implemented: restructured routes into logical domain-based architecture for improved performance and maintainability. systems think in patterns.\n\n13. dynamic database tables now supported: implemented dynamic loading of tables and rebuilt plugin-sql for more flexible data management. adaptation embedded at the database layer.\n\n14. cascade deletion for agents implemented: proper data hygiene prevents orphaned records. coherent systems require coherent data structures.\n\n15. testing coverage significantly expanded across core, server, project-starter, and plugin-starter packages. quality emerges from verification.\n\n16. added ollama as fourth ai provider option in elizas create command. expanding the intelligence ecosystem with local model integration.\n\n17. windows compatibility enhanced: improved loading strategies and path handling for cross-platform consistency. accessibility increases adoption velocity.\n\n18. action prompt logging implemented for increased transparency into agent reasoning. system introspection facilitates human understanding.\n\n# Concise Twitter Thread\n\n1/4 june architectural milestone: server functionality now separated into @elizaos/server package while maintaining backward compatibility. this modular approach enables independent usage of server components while preserving existing cli interactions. system coherence through deliberate decoupling.\n\n2/4 core validation enhanced with zod-based character validation and safe json parsing. consolidated project loading logic eliminates duplication between cli and server. reliable systems require reliable foundations.\n\n3/4 plugin ecosystem evolution continues: dynamic loading of database tables implemented, plugin-sql rebuilt for flexible data management, and memory optimization guidance provided for resource-constrained environments.\n\n4/4 community engagement remains strong with 315 new prs (257 merged) and 68 active contributors this month. the v2 migration progresses steadily with camera plugin integration expanding sensory capabilities beyond text. intelligent systems require collaborative intelligence.\n\n# Platform-specific Posts\n\n## elizaOS Technical Audience:\nthe split of server functionality into @elizaos/server represents a significant architectural improvement for system modularity. while maintaining backward compatibility with existing cli integrations, this separation enables independent usage of server components for custom implementations. the concurrent implementation of zod-based character validation with safe json parsing further strengthens system reliability through robust schema enforcement. deliberate decoupling with coherent interfaces.\n\n## auto.fun Crypto-Native Audience:\ndao wallet token movements addressed with transparent replenishment through daos.fun aum. community quickly spotted 40m $degenai moving from treasury \u2192 personal wallet \u2192 market sells, team confirmed tokens sold to add liquidity with full replacement + excess tokens for runway preservation. ongoing buybacks continue through protocol fees. based tokenomics, anon. treasury management open on chain, just as it should be.", "source_references": [ "2025-06-25\n---\n2025-06-24.md\n---\nFile not found\n---\n2025-06-23.md\n---\n# elizaOS Discord - 2025-06-23\n\n## Overall Discussion Highlights\n\n### Project Status & Development\n- **V2 Development Progress**: V2 is live but still going through active development (wire)\n- **CLI Version 1.0.11 Testing**: Users reported successful testing with features like dynamic loading of plugins and agent creation (DorianD)\n- **Camera Plugin**: Shaw created a camera plugin for Eliza to enable visual input processing (Odilitime)\n- **Memory Requirements**: Running models requires significant VRAM - 16GB is barely sufficient, with gemma3:12b recommended for limited resources (Odilitime)\n- **Plugin Compatibility Issues**: Current plugin system described as \"a mess\" with unclear compatibility between versions (Odilitime)\n\n### Community Concerns\n- **Token Sales Controversy**: Community members questioned why tokens were being sold from what appeared to be a DAO wallet without communication (\u5154\u5154\u5927\u5bcc, \u8f9e\u5c18\u9e3d\u9e3d)\n - Team members explained tokens were sold to add to liquidity pools and would be replenished through daos.fun AUM (jasyn_bjorn)\n - \ud83d\udd25\ud83d\udd25\ud83d\udd25 confirmed replenishment was completed with excess tokens and mentioned ongoing buybacks\n- **X (Twitter) Account Suspension**: The project's X account is currently suspended, but the team is working with X to restore it (Odilitime, Kenk)\n- **Founder Activity**: Some users questioned Shaw's involvement, but others confirmed he's very active in dev channels, on GitHub, and spent the weekend coding (Kenk, DorianD)\n\n### Technical Issues\n- **Knowledge Plugin Problems**: Multiple users reported errors when uploading markdown files to the knowledge plugin (DrakeDinh)\n - 0xbbjoker mentioned releasing a fix for both file path loading and UI uploads on the latest CLI/plugin-knowledge versions\n- **Docker Container Issues**: Users encountered Docker container configuration problems, with jin suggesting a fix using `RUN SKIP_POSTINSTALL=1 bun install --no-cache`\n- **Formatting Issues**: Johannes Weniger encountered problems with newline characters in agent responses, with recommendations to use markdown formatting instead\n\n## Key Questions & Answers\n\n**Q: Why is the DAO wallet selling $degenai tokens?** (\u5154\u5154\u5927\u5bcc) \nA: To add to liquidity pools and would be replenished with buying from AUM on daos.fun (jasyn_bjorn)\n\n**Q: What's the status of the X (Twitter) account?** (vincent789.) \nA: It's currently suspended but the team is working with X to get it back (Odilitime, Kenk)\n\n**Q: What models can handle ElizaOS with limited resources?** (DorianD) \nA: gemma3:12b is doing ok with 16GB VRAM (Odilitime)\n\n**Q: Did knowledge feature work yet?** (DrakeDinh) \nA: 0xbbjoker mentioned releasing a fix for both file path loading and UI uploads on the latest CLI/plugin-knowledge versions\n\n**Q: Anyone running the docker container?** (jin) \nA: jin suggested a fix: `RUN SKIP_POSTINSTALL=1 bun install --no-cache`\n\n**Q: What's the team's plan to boost ai16z popularity?** (CULTVESTING) \nA: Get X account back, make quality products, open source them, and market heavily (Odilitime)\n\n**Q: Is Shaw active in the project?** (Skullcross) \nA: Yes, he's very active in dev channels, on GitHub, and spent the weekend coding (Kenk, DorianD)\n\n## Community Help & Collaboration\n\n1. **Docker Container Deployment**\n - **Helper**: jin\n - **Helpee**: Yasir\n - **Solution**: Suggested `RUN SKIP_POSTINSTALL=1 bun install --no-cache` fix for Docker issues\n\n2. **Agent Response Formatting**\n - **Helper**: sayonara\n - **Helpee**: Johannes Weniger\n - **Solution**: Suggested using markdown formatting in system prompt to fix newline character display issues\n\n3. **Plugin Requirements**\n - **Helper**: DrakeDinh\n - **Helpee**: DorianD\n - **Solution**: Suggested required plugins for new agent: os/plugin-bootstrap, os/plugin-sql, and os/plugin-openai\n\n4. **Memory Requirements Guidance**\n - **Helper**: Odilitime\n - **Helpee**: DorianD\n - **Solution**: Shared that 16GB VRAM is barely sufficient, recommended gemma3:12b model\n\n5. **Blockchain Issue Support**\n - **Helper**: Odilitime\n - **Helpee**: ElizaBAO\ud83c\udf1f\n - **Solution**: Sent message to autofun team and directed to appropriate channel\n\n## Action Items\n\n### Technical\n- **Fix knowledge plugin upload functionality** (DrakeDinh)\n - Users experiencing \"Unexpected end of form\" errors when uploading markdown files\n- **Get the X (Twitter) account unbanned** (Odilitime)\n - Team is working with X to restore the suspended account\n- **Improve plugin compatibility and documentation** (Odilitime)\n - Current plugin system described as \"a mess\" with unclear compatibility\n- **Complete V2 development** (wire)\n - V2 is live but still going through development\n- **Implement camera plugin functionality** (Odilitime)\n - Shaw created a camera plugin for Eliza to enable visual input\n- **Fix Docker container installation issues** (jin)\n - Implement proper postinstall skip for bun install\n- **Investigate search functionality in knowledge plugin** (Nash)\n - Search returns same results for different queries after first query\n- **Port MemoryCacheAdapter and CacheManager from v0.29** (Mihail Kirov)\n - Need compatibility with core v1.0.10\n- **Optimize memory usage for running models** (Odilitime)\n - Current models require significant VRAM to run properly\n\n### Documentation\n- **Create better documentation for OpenRouter integration** (jin)\n - Current documentation is confusing to follow\n- **Create better resources for character generation** (pditty)\n - New character gen app built but struggling to get attention\n- **Update community on regular buybacks through daos.fun fees** (\ud83d\udd25\ud83d\udd25\ud83d\udd25)\n - Create transparency around token movements that aren't publicly communicated\n\n### Feature\n- **Create AI accessory camera for makers** (DorianD)\n - Camera that connects to Eliza plugin to capture A/V data for processing\n- **Develop AI friend/advisor capabilities** (DorianD)\n - System that watches/hears everything and acts as advisor/buddy/coach\n- **Improve action trigger reliability** (T@P)\n - Make action triggers easier and more reliable for guide chatbots\n---\n2025-06-22.md\n---\n# elizaOS Discord - 2025-06-22\n\n## Overall Discussion Highlights\n\n### Treasury & Token Concerns\n- **Community Trust Issues**: Significant community concern over suspected token selling from what appears to be project-related wallets, with approximately 40 million $degenai tokens reportedly transferred from the DAO treasury to a personal wallet, followed by selling.\n- **Transaction Evidence**: Community members, particularly \u8f9e\u5c18\u9e3d\u9e3d, shared on-chain evidence showing approximately 3 million $degenai tokens being sold in a single day, causing the token to reach a new all-time low.\n- **Wallet Clarification**: Kenk noted that the wallet in question (GypeM9BqKeKGJGTnPxTf1PdVa3UC2LkiYnvvW8CJSNj2) hasn't been confirmed as a DAO wallet, though \u8f9e\u5c18\u9e3d\u9e3d pointed out it had previously interacted with the DAO wallet through a significant token transfer.\n- **Lack of Communication**: Multiple users expressed frustration about the absence of official communication regarding these transactions, amplifying trust issues within the community.\n\n### Development Updates\n- **V2 Status**: Dr. Neuro mentioned that V2 is already released but not officially announced yet.\n- **Spartan Prototype**: Void shared that the Spartan prototype is nearing completion, which could potentially bring positive market impact.\n- **ElizaOS API Documentation**: Documentation updates for ElizaOS API v1.0.10 were announced, including Socket messages.\n\n### Technical Issues\n- **CLI Version Conflicts**: Several users experienced problems with CLI versioning, often running 1.0.9 instead of the latest 1.0.11, with conflicts between npm and bun package managers.\n- **WebSocket Connection Issues**: Users reported problems with WebSocket connections and response handling after messages are sent.\n- **Model Selection Problems**: Multiple users struggled with getting OpenAI integration working instead of local models.\n- **Social Media Access**: Users noted issues accessing Shaw's Farcaster account and mentioned that Eliza's Twitter account needs restoration.\n\n### Market Discussion\n- **Token Predictions**: Some discussion about cryptocurrency tokens including ELI5, EDDY, Dot, COM, and TAPS, with CULTVESTING warning about a potential market dip while suggesting holding certain tokens.\n- **Launch Questions**: MDMnvest expressed interest in when Dot will launch.\n\n## Key Questions & Answers\n\n### Technical Support\n- **Q**: How do I get the test agent to use OpenAI instead of local models? (DorianD) \n **A**: Update to the latest version (1.0.11), edit .env file, run \"bun run build\" and \"bun run start\" (cjft)\n\n- **Q**: How can I get a response after a message is sent via WebSocket? (Furkan Nabi Sumji) \n **A**: Check implementation examples in eliza-nextjs-starter and eliza client repositories (sayonara)\n\n- **Q**: How do I get the new CLI when it shows I'm on 1.0.9 despite installing 1.0.11? (Bealers) \n **A**: Uninstall the npm version with \"npm uninstall -g @elizaos/cli\" then install with \"bun i -g @elizaos/cli\" (sayonara)\n\n- **Q**: What happened to Shaw's Farcaster account? (ghk9698) \n **A**: Working fine for logged-in users, may fail if not logged in (cjft)\n\n### General Questions\n- **Q**: What is ELI5? (Skaju) \n **A**: \"Explain Like I'm 5,\" which is about breaking down complex ideas into easy-to-understand bits (Eliza)\n\n- **Q**: What does \"bullish\" mean in the context of ELI5? (Skaju) \n **A**: When something is \"bullish,\" it means people are feeling positive about its future (Eliza)\n\n- **Q**: Any update on v2? (srikanth) \n **A**: V2 is already out, just not announced yet (Dr. Neuro)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **cjft helped DorianD**: Identified outdated version (1.0.9 vs 1.0.11) and provided git commands to update, enabling OpenAI integration instead of local models.\n- **sayonara helped Furkan Nabi Sumji**: Provided links to implementation examples in GitHub repositories to resolve WebSocket connection issues.\n- **sayonara helped Bealers**: Identified package manager conflict and provided commands to uninstall npm version and install with bun to resolve CLI version issues.\n- **shaw helped DorianD**: Suggested using \"agent\" mode with Claude Sonnet 4 and checking background agents for Cursor AI agent behavior issues.\n\n### Information Sharing\n- **human_nalejzpa helped \u8f9e\u5c18\u9e3d\u9e3d**: Shared a Solscan transaction link showing history with the DAO address, providing evidence for the community discussion about token movements.\n- **Kenk helped ghk9698**: Provided the correct link to Shaw's Farcaster account (https://farcaster.xyz/shawmakesmagic).\n- **Void helped the community**: Shared development update about the Spartan prototype nearing completion, providing some positive news amid token concerns.\n\n## Action Items\n\n### Technical\n- Officially announce V2 release with detailed explanation (Mentioned by Dr. Neuro)\n- Restore Eliza's Twitter account (Mentioned by HERF)\n- Fix WebSocket connection issues for response handling after message sent (Mentioned by Furkan Nabi Sumji)\n- Resolve CLI version detection issues when installed via different package managers (Mentioned by Bealers)\n- Investigate Twitter plugin problems (Mentioned by Sthx)\n- Fix issue with CLI reverting to local models instead of using Grok (Mentioned by Chief)\n- Finalize and release the Spartan prototype (Mentioned by Void)\n- Restore X (Twitter) pages (Mentioned by Odilitime)\n\n### Documentation\n- Provide clear communication about DAO treasury token movements (Mentioned by \u8f9e\u5c18\u9e3d\u9e3d)\n- Clarify the relationship between version numbering (1.0 vs V2) (Mentioned by \u8f9e\u5c18\u9e3d\u9e3d)\n- Provide transparency about DAO governance processes for treasury management (Mentioned by hildi)\n- ElizaOS API docs updated to v1.0.10 including Socket messages (Mentioned by cjft)\n- Provide clear explanation of token sales strategy (Mentioned by \u8f9e\u5c18\u9e3d\u9e3d)\n- Clarify wallet ownership and transaction purposes (Mentioned by human_nalejzpa)\n\n### Feature Requests\n- Launch of Dot token (Mentioned by MDMnvest)\n- Implement 24/7 marketing through private accounts similar to Virtuals (Mentioned by Rick)\n---\n2025-06-24.md\n---\nFile not found\n---\n2025-06-23.md\n---\nFile not found\n---\n2025-06-22.md\n---\nFile not found\n---\n2025-06-24.json\n---\nFile not found\n---\n2025-06-24.md\n---\nFile not found\n---\n2025-06-24.json\n---\nFile not found\n---\n2025-06-24.md\n---\nFile not found\n---\n2025-06-24.json\n---\nFile not found\n---\n2025-06-24.md\n---\nFile not found\n---\n2025-06-24.json\n---\nFile not found\n---\n2025-06-24.md\n---\nFile not found\n---\n2025-06-25.md\n---\nFile not found\n---\n2025-06-15.md\n---\n# ElizaOS Weekly Update (Jun 15 - 21, 2025)\n\n## OVERVIEW\nThis week saw significant architectural improvements to the ElizaOS framework, with a major focus on modularization through the separation of server functionality into its own package. The team also expanded AI provider options, enhanced testing coverage across multiple packages, and fixed numerous bugs affecting Windows compatibility, UI responsiveness, and character validation. Documentation received comprehensive updates to improve accuracy and consistency.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Architecture and Modularization\n- **Server Package Separation**: Split server functionality into a dedicated `@elizaos/server` package while maintaining backward compatibility with CLI integrations [#5122](https://github.com/elizaos/eliza/pull/5122)\n- **Character Validation**: Implemented Zod-based character validation with safe JSON parsing to improve robustness [#5167](https://github.com/elizaos/eliza/pull/5167)\n- **Project Loading Refactor**: Consolidated character loading logic to eliminate duplication between CLI and server [#5169](https://github.com/elizaos/eliza/pull/5169)\n- **CLI Command Consolidation**: Streamlined agent management by merging `elizaos stop` into `elizaos agent stop --all` [#5175](https://github.com/elizaos/eliza/pull/5175)\n\n### Testing and Provider Enhancements\n- **Expanded Test Coverage**: Added comprehensive tests for core, server, project-starter, and plugin-starter packages [#5125](https://github.com/elizaos/eliza/pull/5125), [#5136](https://github.com/elizaos/eliza/pull/5136)\n- **Ollama Integration**: Added Ollama as a fourth AI provider option in the `elizaos create` command [#5160](https://github.com/elizaos/eliza/pull/5160)\n- **Fixed Test Failures**: Resolved CLI test failures caused by circular dependencies and missing runtime methods [#5135](https://github.com/elizaos/eliza/pull/5135)\n\n### UI and User Experience Improvements\n- **Chat Interface Enhancements**: Added GUI chat title functionality [#5179](https://github.com/elizaos/eliza/pull/5179)\n- **Media Support**: Improved media content handling with better color contrast and formatting [#5165](https://github.com/elizaos/eliza/pull/5165)\n- **Message Filtering**: Fixed message filtering to properly scope messages to the current chat/channel [#5149](https://github.com/elizaos/eliza/pull/5149)\n- **UI Responsiveness**: Resolved issues with the GUI getting stuck in \"agent is thinking\" state [#5151](https://github.com/elizaos/eliza/pull/5151)\n\n## CLOSED ISSUES\n\n### API and Integration Issues\n- **REST API Functionality**: Fixed issues with room creation via REST API [#4955](https://github.com/elizaos/eliza/issues/4955)\n- **Endpoint Availability**: Resolved 404 errors when accessing agent rooms endpoint [#5121](https://github.com/elizaos/eliza/issues/5121)\n- **Postman Specifications**: Updated Postman specs to match current server API implementation [#5124](https://github.com/elizaos/eliza/issues/5124)\n\n### Feature Implementation and Documentation\n- **Knowledge Management**: Addressed RAG functionality implementation issues in version 1.0.6 [#5004](https://github.com/elizaos/eliza/issues/5004)\n- **Character Validation**: Implemented robust schema validation for character loading [#5166](https://github.com/elizaos/eliza/issues/5166)\n- **Project Loading Refactor**: Initiated streamlining of project loading mechanisms [#5168](https://github.com/elizaos/eliza/issues/5168)\n- **AI Provider Options**: Added Ollama as a new AI provider option [#5159](https://github.com/elizaos/eliza/issues/5159)\n\n## NEW ISSUES\n\n### Platform Compatibility and Infrastructure\n- **Windows Compatibility**: Projects fail to load properly on Windows development machines [#5155](https://github.com/elizaos/eliza/issues/5155)\n- **Windows Stability**: Server crashes after accessing localhost:3000 on Windows [#5161](https://github.com/elizaos/eliza/issues/5161)\n- **Testing Framework Standardization**: Need to migrate from mixed vitest/bun:test setup to standardized bun:test [#5185](https://github.com/elizaos/eliza/issues/5185)\n\n### Architecture and Scalability\n- **Logger Configuration**: Allow downstream projects to customize root logger configuration [#5183](https://github.com/elizaos/eliza/issues/5183)\n- **Database Migration**: Implement advisory locking for horizontal scaling in DatabaseMigrationService [#5181](https://github.com/elizaos/eliza/issues/5181)\n- **CLI Testing**: Fix issue where test command incorrectly requires monorepo root for standalone projects [#5142](https://github.com/elizaos/eliza/issues/5142)\n- **Plugin Compatibility**: Twitter plugin not running correctly with both plugin and client [#5172](https://github.com/elizaos/eliza/issues/5172)\n---\n2025-06-01.md\n---\n# ElizaOS Monthly Update (June 2025)\n\n## OVERVIEW\nJune was a transformative month for ElizaOS with significant architectural improvements and feature additions. The team focused on enhancing the framework's modularity, stability, and developer experience. Major achievements include a comprehensive API domain reorganization, improved plugin management, enhanced character validation, and significant UI/UX improvements across the platform. The CLI was also substantially refactored for better performance and usability.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### \ud83c\udfd7\ufe0f Core Architecture Improvements\n- **Plugin Specifications Integration**: Added plugin specifications to core, enabling standardized plugin functionality without breaking existing code [#4851](https://github.com/elizaos/eliza/pull/4851)\n- **Message Server Refactoring**: Completely separated the message server from agents, creating a standalone system with support for servers, channels, and participants [#4864](https://github.com/elizaos/eliza/pull/4864)\n- **Core Types Reorganization**: Split monolithic types.ts into granular, logical sections for better maintainability and searchability [#4999](https://github.com/elizaos/eliza/pull/4999), [#5020](https://github.com/elizaos/eliza/pull/5020)\n- **Server Package Separation**: Split server functionality into a separate `@elizaos/server` package while maintaining backward compatibility [#5122](https://github.com/elizaos/eliza/pull/5122)\n\n### \ud83d\udd04 Database and Data Management\n- **Dynamic Database Tables**: Implemented dynamic loading of database tables and rebuilt plugin-sql for more flexible data management [#5018](https://github.com/elizaos/eliza/pull/5018)\n- **Cascade Delete for Agents**: Added proper cascade deletion for agents to maintain database integrity and prevent orphaned records [#5171](https://github.com/elizaos/eliza/pull/5171)\n- **Memory Management Improvements**: Fixed duplicate memory issues and enhanced memory filtering by room [#5103](https://github.com/elizaos/eliza/pull/5103), [#4948](https://github.com/elizaos/eliza/pull/4948)\n\n### \ud83e\udde9 Plugin System Enhancements\n- **Plugin Loading Optimization**: Improved plugin loading strategies to resolve core dependency conflicts and enhance performance [#4949](https://github.com/elizaos/eliza/pull/4949)\n- **Plugin Environment Variables**: Added support for prompting users for environment variables during plugin installation [#4945](https://github.com/elizaos/eliza/pull/4945)\n- **Dummy Services**: Added dummy service implementations for testing and development purposes [#5030](https://github.com/elizaos/eliza/pull/5030)\n- **Plugin Template Improvements**: Fixed TypeScript declarations in plugin starter templates and standardized Git ignores [#4966](https://github.com/elizaos/eliza/pull/4966)\n\n### \ud83d\udda5\ufe0f CLI Enhancements\n- **CLI Command Reorganization**: Completely refactored CLI commands into a modular structure for better maintainability [#5036](https://github.com/elizaos/eliza/pull/5036)\n- **Improved Prompts**: Migrated CLI prompts from the legacy `prompts` library to modern `@clack/prompts` for enhanced UX [#5016](https://github.com/elizaos/eliza/pull/5016)\n- **Ollama Integration**: Added Ollama as an AI provider option in the create command [#5160](https://github.com/elizaos/eliza/pull/5160)\n- **Bun Offline Mode**: Optimized CLI project creation with Bun offline mode for faster installations [#5087](https://github.com/elizaos/eliza/pull/5087)\n\n### \ud83c\udfa8 UI/UX Improvements\n- **Chat Interface Enhancements**: Implemented animated markdown components, improved code blocks, and enhanced message styling [#5111](https://github.com/elizaos/eliza/pull/5111)\n- **Mobile Responsiveness**: Added responsive design for character forms and improved sidebar handling on mobile devices [#4866](https://github.com/elizaos/eliza/pull/4866), [#4974](https://github.com/elizaos/eliza/pull/4974)\n- **Message Retry Button**: Added a retry button for user messages in chat to easily resend previous messages [#4973](https://github.com/elizaos/eliza/pull/4973)\n- **Split Button Component**: Created a reusable split button component with dropdown functionality for grouping related actions [#5000](https://github.com/elizaos/eliza/pull/5000)\n\n### \ud83d\udd0c API and Integration\n- **API Domain Reorganization**: Completely restructured API routes into a logical domain-based structure [#5010](https://github.com/elizaos/eliza/pull/5010)\n- **Channel Management APIs**: Added API endpoints for managing agents across channels [#5113](https://github.com/elizaos/eliza/pull/5113)\n- **Postman Collection**: Added a comprehensive Postman collection with 90+ REST API endpoints for easier API testing [#5047](https://github.com/elizaos/eliza/pull/5047)\n- **Real-time Message Deletion**: Implemented real-time message deletion via SocketIO [#4968](https://github.com/elizaos/eliza/pull/4968)\n\n### \ud83e\uddea Testing and Documentation\n- **Comprehensive Tests**: Added detailed tests to core, server, project-starter, and plugin-starter packages [#5125](https://github.com/elizaos/eliza/pull/5125), [#5136](https://github.com/elizaos/eliza/pull/5136)\n- **CLI Test Migration**: Migrated CLI tests from Bats shell scripts to TypeScript using Bun test runner [#4978](https://github.com/elizaos/eliza/pull/4978)\n- **Scenario Testing**: Added scenario tests to bootstrap to verify agent responses [#4998](https://github.com/elizaos/eliza/pull/4998)\n- **AI Assistant Guidance**: Added comprehensive CLAUDE.md file to guide AI assistants working in the repository [#5158](https://github.com/elizaos/eliza/pull/5158)\n\n### \ud83d\udee0\ufe0f Developer Experience\n- **macOS Setup Guide**: Added a comprehensive macOS development setup guide [#4903](https://github.com/elizaos/eliza/pull/4903)\n- **Windows Compatibility**: Improved Windows compatibility for CLI tests and project loading [#5110](https://github.com/elizaos/eliza/pull/5110), [#5156](https://github.com/elizaos/eliza/pull/5156)\n- **Cursor Rules**: Added .cursor project rules as a submodule for consistent development experience [#5021](https://github.com/elizaos/eliza/pull/5021)\n- **Versioning Improvements**: Enhanced versioning logic to properly update version information across packages [#4983](https://github.com/elizaos/eliza/pull/4983)\n\n## CLOSED ISSUES\n\n### \ud83d\udc1b Critical Bug Fixes\n- Fixed issues with Twitter client startup [#4894](https://github.com/elizaos/eliza/issues/4894)\n- Resolved agent participation in channels problem [#4933](https://github.com/elizaos/eliza/issues/4933)\n- Fixed page refresh errors in agent chat [#4927](https://github.com/elizaos/eliza/issues/4927)\n- Addressed file upload failures in GUI [#5116](https://github.com/elizaos/eliza/issues/5116)\n\n### \ud83d\udd04 API and Integration Issues\n- Fixed empty rooms array returned by API despite agent participation [#4955](https://github.com/elizaos/eliza/issues/4955)\n- Resolved missing API endpoint for agent rooms [#4763](https://github.com/elizaos/eliza/issues/4763), [#5121](https://github.com/elizaos/eliza/issues/5121)\n- Fixed message handling issues in MessageBusService [#4972](https://github.com/eliz\n---\n{\n \"interval\": {\n \"intervalStart\": \"2025-06-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-07-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-06-01 to 2025-07-01, elizaos/eliza had 315 new PRs (257 merged), 56 new issues, and 68 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs66bOWK\",\n \"title\": \"Knowledge management (RAG) not working (implemented) in 1.0.6\",\n \"author\": \"harperaa\",\n \"number\": 5004,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nI am trying to get rag working and following docs, but that code is not implemented in 1.0.6. It appears to be commented as a placeholder in \\n \\n**To Reproduce**\\n\\nsettings: {\\n secrets: {},\\n ragKnowledge: true,\\n },\\n knowledge: [\\n {\\n directory: 'knowledge/foobar',\\n shared: true,\\n },\\n ],\\n\\n**Expected behavior**\\n\\nI expect that it would parse on startup and it was not doing that, as it used to do. So, I looked into code and found this... summary from claude....\\n\\nMissing Implementation Locations\\n\\n 1. AgentRuntime Initialization Missing Knowledge \\n Processing\\n\\n File: /packages/core/src/runtime.ts (lines 494-651)\\n - The AgentRuntime.initialize() method should process\\n character.knowledge but doesn't\\n - No call to any knowledge processing function during\\n agent startup\\n\\n 2. TODO Comment Confirms Missing Implementation\\n\\n File: /packages/core/src/specs/v1/index.ts (line 50)\\n // TODO: Implement the remaining adapters: ... - \\n knowledge / memory\\n This is a developer comment explicitly stating that\\n knowledge processing is not implemented yet.\\n\\n 3. Bootstrap Plugin Missing KNOWLEDGE Provider\\n\\n File: /packages/plugin-bootstrap/src/providers/index.ts\\n - Multiple message examples reference providers: \\n ['KNOWLEDGE'] in character files\\n - But the bootstrap plugin doesn't export any KNOWLEDGE \\n provider\\n - Provider list is incomplete - missing the knowledge\\n provider entirely\\n\\n 4. RagService Interface Exists But No Implementation\\n\\n File: /packages/core/src/runtime.ts (lines 52-61)\\n interface RagServiceDelegator extends Service {\\n getKnowledge(message: Memory, scope?: { roomId?: UUID;\\n worldId?: UUID; entityId?: UUID }):\\n Promise;\\n _internalAddKnowledge(item: KnowledgeItem, options?:\\n any, scope?: any): Promise;\\n }\\n The interface exists but no actual implementation of\\n this service.\\n\\n 5. Missing Functions\\n\\n - processCharacterKnowledge() - Referenced in docs but\\n doesn't exist anywhere\\n - No knowledge file reading/processing logic\\n - No connection between character.knowledge array and\\n embedding system\\n\\n Developer Comments Confirming This\\n\\n The codebase has explicit TODO comments indicating that\\n knowledge/memory functionality is intentionally \\n unfinished. The character examples even reference\\n a KNOWLEDGE provider that doesn't exist, suggesting\\n this was planned but never implemented.\\n\\n\",\n \"createdAt\": \"2025-06-08T00:06:14Z\",\n \"closedAt\": \"2025-06-17T18:10:11Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 14\n },\n {\n \"id\": \"I_kwDOMT5cIs66o8ku\",\n \"title\": \"Callback from plugin action not making it to end user response in chat\",\n \"author\": \"jonathanprozzi\",\n \"number\": 5017,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nIn using the `plugin-evm` transfer function we expect to see a followup message with either the success or failure of the transaction.\\n\\nIn the plugin's `transfer.ts` callback, we see the following:\\n\\nhttps://github.com/elizaos-plugins/plugin-evm/blob/6bf9c4c54b9e1a558c7fb092f071f2e374435887/src/actions/transfer.ts#L133\\n\\n```typescript\\n if (callback) {\\n callback({\\n text: `Successfully transferred ${paramOptions.amount} tokens to ${paramOptions.toAddress}\\\\nTransaction Hash: ${transferResp.hash}`,\\n content: {\\n success: true,\\n hash: transferResp.hash,\\n amount: formatEther(transferResp.value),\\n recipient: transferResp.to,\\n chain: paramOptions.fromChain,\\n },\\n });\\n }\\n... (other error logging as well)\\n```\\n\\nWe see the following in our logs (added additional debugging console.log statements):\\n\\n```bash\\nLOG:in the transfer action\\nCALLBACK IN EVM_TRANSFER_TOKENS [AsyncFunction (anonymous)]\\nin the transferResponse try block\\ntransferResponse try block completed {\\n hash: '0xd2680982067e0258612119a58497208428613debcd314d667bd758b93ea86ed8',\\n from: '0x7850f8a9825d6dadfF5621300ee11f2dED76b76b',\\n to: '0x25709998B542f1Be27D19Fa0B3A9A67302bc1b94',\\n value: 20000000000000000n,\\n data: '0x'\\n}\\n[2025-06-09 19:25:35] INFO: [Eliza] Agent generated response for message. Preparing to send back to bus.\\n[2025-06-09 19:25:35] INFO: [Eliza] MessageBusService: Sending payload to central server API endpoint (/api/messages/submit):\\n channel_id: \\\"93487822-03c0-4119-bffc-13aca04fb41f\\\"\\n server_id: \\\"00000000-0000-0000-0000-000000000000\\\"\\n author_id: \\\"b850bc30-45f8-0041-a00a-83df46d8555d\\\"\\n content: \\\"I'll help you transfer 0.02 ETH to 0x25709998B542f1Be27D19Fa0B3A9A67302bc1b94 on Sepolia. Processing the transaction now.\\\"\\n in_reply_to_message_id: \\\"18489676-ba76-4673-9a39-9f17fe686bc3\\\"\\n source_type: \\\"agent_response\\\"\\n raw_message: {\\n \\\"text\\\": \\\"I'll help you transfer 0.02 ETH to 0x25709998B542f1Be27D19Fa0B3A9A67302bc1b94 on Sepolia. Processing the transaction now.\\\",\\n \\\"thought\\\": \\\"Process ETH transfer request on Sepolia network after checking balance\\\",\\n \\\"actions\\\": [\\n \\\"REPLY\\\",\\n \\\"EVM_TRANSFER_TOKENS\\\"\\n ]\\n }\\n metadata: {\\n \\\"agent_id\\\": \\\"b850bc30-45f8-0041-a00a-83df46d8555d\\\",\\n \\\"agentName\\\": \\\"Eliza\\\",\\n \\\"channelType\\\": \\\"DM\\\",\\n \\\"isDm\\\": true\\n }\\n\\n```\\n\\nThe transfer is successful, but we only see the initial message of `\\\"text\\\": \\\"I'll help you transfer 0.02 ETH to 0x25709998B542f1Be27D19Fa0B3A9A67302bc1b94 on Sepolia. Processing the transaction now.\\\",` in the Eliza chat interface.\\n\\nWe would expect to see a followup message with the success (or failure) text from the callback in the `transfer.ts` function.\\n\\nWe also triggered an unsuccessful transaction and did not receive a followup error message which the callback suggests we should see.\\n\\n**To Reproduce**\\n\\n- Bare Eliza scaffolded as a fresh project with the `plugin-anthropic` and `plugin-evm` added:\\n\\n```bash\\n \\\"@elizaos/cli\\\": \\\"^1.0.6\\\",\\n \\\"@elizaos/core\\\": \\\"^1.0.6\\\",\\n \\\"@elizaos/plugin-anthropic\\\": \\\"^1.0.0\\\",\\n \\\"@elizaos/plugin-bootstrap\\\": \\\"^1.0.6\\\",\\n \\\"@elizaos/plugin-evm\\\": \\\"file:../plugin-evm\\\",\\n \\\"@elizaos/plugin-knowledge\\\": \\\"^1.0.1\\\",\\n \\\"@elizaos/plugin-openai\\\": \\\"^1.0.3\\\",\\n \\\"@elizaos/plugin-sql\\\": \\\"^1.0.6\\\",\\n \\\"zod\\\": \\\"3.24.2\\\"\\n```\\n\\nand the following Character config:\\n\\n```typescript\\n name: 'Eliza',\\n plugins: [\\n '@elizaos/plugin-sql',\\n ...(process.env.EVM_PRIVATE_KEY ? ['@elizaos/plugin-evm'] : []),\\n ...(process.env.ANTHROPIC_API_KEY ? ['@elizaos/plugin-anthropic'] : []),\\n ...(process.env.OPENAI_API_KEY ? ['@elizaos/plugin-openai'] : []),\\n ...(process.env.OPENAI_API_KEY ? ['@elizaos/plugin-knowledge'] : []),\\n ...(!process.env.OPENAI_API_KEY ? ['@elizaos/plugin-local-ai'] : []),\\n ...(process.env.DISCORD_API_TOKEN ? ['@elizaos/plugin-discord'] : []),\\n ...(process.env.TWITTER_USERNAME ? ['@elizaos/plugin-twitter'] : []),\\n ...(process.env.TELEGRAM_BOT_TOKEN ? ['@elizaos/plugin-telegram'] : []),\\n ...(!process.env.IGNORE_BOOTSTRAP ? ['@elizaos/plugin-bootstrap'] : []),\\n ],\\n settings: {\\n secrets: {},\\n chains: {\\n evm: ['sepolia'],\\n },\\n ANTHROPIC_API_KEY: process.env.ANTHROPIC_API_KEY,\\n ANTHROPIC_SMALL_MODEL: 'claude-3-5-sonnet-latest',\\n ANTHROPIC_LARGE_MODEL: 'claude-3-5-sonnet-latest',\\n },\\n\\n```\\nOur private key and RPC are configured and work as the transfer is successful.\\n\\n\\n**Expected behavior**\\n\\nBased on the callback in `transfer.ts` we expect to see a followup message indicating the success or failure of the transfer call.\\n\\n**Screenshots**\\n\\n![Image](https://github.com/user-attachments/assets/06dae3fa-9b2c-4e49-b660-42f2d9f9837f)\\n\\nAt this stage, the transfer succeeds but this is the last message we received.\\n\\nWe would expect that there would be a followup message after this indicating the success or the failure, including (or similar to) the text in the `transfer.ts` callback (in the `plugin-evm` plugin):\\n\\n`Successfully transferred ${paramOptions.amount} tokens to ${paramOptions.toAddress}\\\\nTransaction Hash: ${transferResp.hash}`\\n\\n**Additional context**\\n\\nWe're under the impression that this is a core callback issue and not with the `plugin-evm` itself as we're seeing similar behavior with a barebones example using the `plugin-mcp`. This is a more direct and more easily reproducible example to file.\\n\",\n \"createdAt\": \"2025-06-09T19:45:43Z\",\n \"closedAt\": \"2025-06-19T10:57:22Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 14\n },\n {\n \"id\": \"I_kwDOMT5cIs66Hl5D\",\n \"title\": \"Creating room via REST API first works but then returns empty rooms array\",\n \"author\": \"exitsimulation\",\n \"number\": 4955,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nI am creating a room for an existing agent via the Rest API which returns a success response\\n\\nPOST `/api/agents/b850bc30-45f8-0041-a00a-83df46d8555d/rooms` with \\n```\\n{\\n \\\"name\\\": \\\"TestRoom\\\",\\n \\\"worldId\\\": \\\"00000000-0000-0000-0000-000000000000\\\",\\n \\\"roomId\\\": \\\"c06bb360-e84f-49ff-b43a-75a9eb6df8f3\\\",\\n \\\"enitityId\\\": \\\"b850bc30-45f8-0041-a00a-83df46d8555d\\\"\\n}\\n```\\n\\nResponse:\\n```\\n{\\n \\\"success\\\": true,\\n \\\"data\\\": {\\n \\\"id\\\": \\\"143da10d-b1e5-00cb-b315-a64f6062d9de\\\",\\n \\\"name\\\": \\\"TestRoom\\\",\\n \\\"agentId\\\": \\\"b850bc30-45f8-0041-a00a-83df46d8555d\\\",\\n \\\"createdAt\\\": 1749153906448,\\n \\\"source\\\": \\\"client\\\",\\n \\\"type\\\": \\\"dm\\\",\\n \\\"worldId\\\": \\\"00000000-0000-0000-0000-000000000000\\\",\\n \\\"serverId\\\": \\\"server-1749153906404\\\"\\n }\\n}\\n```\\n\\nNow, the strange thing is then when I call the rooms endpoint via GET\\n`api/agents/b850bc30-45f8-0041-a00a-83df46d8555d/rooms`\\n\\nI am getting an empty array\\n\\n```\\n{\\n \\\"success\\\": true,\\n \\\"data\\\": {\\n \\\"rooms\\\": []\\n }\\n}\\n```\\n\\nAlso the ID in the success response is not the one that I supplied in the request.\\n\\nIt seems like internally the room has not been created despite the success response?\\n\\nIs this a bug in the current version? I am on 1.0.4. Any help would be appreciated!\",\n \"createdAt\": \"2025-06-05T20:24:03Z\",\n \"closedAt\": \"2025-06-18T21:24:30Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 11\n },\n {\n \"id\": \"I_kwDOMT5cIs66yPsU\",\n \"title\": \"Unable to load custom characters after upgrading to 1.0.7\",\n \"author\": \"jonathanprozzi\",\n \"number\": 5039,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"**Describe the bug**\\n\\nAfter upgrading an existing project to use `@elizaos/core` version `1.0.7`, our custom character is no longer registered as an agent. Opening the chat interface/dev environment on `localhost` only shows Eliza as an agent and not our character. This previously worked with `1.0.6`. \\n\\nI tested with a newly scaffolded project and set up a character there as well and noticed the same behavior with only Eliza being shown as an agent.\\n\\n**To Reproduce**\\n\\n- Upgrade an existing project to use `\\\"@elizaos/core\\\": \\\"^1.0.7\\\"` or start a fresh one using this version\\n- Create a new character file with character settings and load that as the agent in the `index.ts`\\n- Start the server\\n- Open `localhost` to view the chat/dev environment and check if custom character is there -- we only saw Eliza and not our agent\\n\\nCode snippets for characters:\\n\\n`herbert.ts` snippet:\\n\\n```typescript\\nexport const herbert: Character = {\\n name: 'Herbert',\\n plugins: [\\n '@elizaos/plugin-sql',\\n ...(process.env.EVM_PRIVATE_KEY ? ['@elizaos/plugin-evm'] : []),\\n ...(process.env.ANTHROPIC_API_KEY ? ['@elizaos/plugin-anthropic'] : []),\\n ...(process.env.OPENAI_API_KEY ? ['@elizaos/plugin-openai'] : []),\\n ...(process.env.OPENAI_API_KEY ? ['@elizaos/plugin-knowledge'] : []),\\n ...(!process.env.OPENAI_API_KEY ? ['@elizaos/plugin-local-ai'] : []),\\n ...(process.env.DISCORD_API_TOKEN ? ['@elizaos/plugin-discord'] : []),\\n ...(process.env.TWITTER_USERNAME ? ['@elizaos/plugin-twitter'] : []),\\n ...(process.env.TELEGRAM_BOT_TOKEN ? ['@elizaos/plugin-telegram'] : []),\\n ...(!process.env.IGNORE_BOOTSTRAP ? ['@elizaos/plugin-bootstrap'] : []),\\n ],\\n... (more settings)\\n}\\n```\\n\\n`index.ts`:\\n```typescript\\nconst herbertAgent: ProjectAgent = {\\n character: herbert,\\n init: async (runtime: IAgentRuntime) => initCharacter({ runtime }),\\n};\\nconst project: Project = {\\n agents: [herbertAgent],\\n};\\n```\\n\\n**Expected behavior**\\n\\n- Expected that Eliza would find the new character (Herbert) and register it as an agent (previous behavior in existing project)\\n- We didn't change any config in the existing project but after upgrading versions we could no longer find/interact with Herbert\\n\\n**Additional context**\\n\\n- Tested this with both a newly scaffolded project as well as in an existing project. Our existing project had our custom agent/character loading but I then upgraded to `1.0.7` and Eliza is the only registered agent. Seems to possibly be using Eliza as a fallback and ignoring our custom character files, even though they're being detected when the server starts.\\n\",\n \"createdAt\": \"2025-06-10T14:02:57Z\",\n \"closedAt\": \"2025-06-11T05:11:31Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 8\n },\n {\n \"id\": \"I_kwDOMT5cIs6z1G6x\",\n \"title\": \"Doesn't work this evm plugin -> @elizaos/plugin-evm\",\n \"author\": \"0xopsdev\",\n \"number\": 4357,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"I want to run evm ai agent with using plugin-evm\\nInside characters/degen.character.json file I set evm plugins and modelprovider as openai.\\nThen set openai key to .env file\\nI also import plugin-coingecko, but it works with fetch token price or etc.\\nBut If I want to swap tokens or transfer tokens, it doesn't work\\n\\n![Image](https://github.com/user-attachments/assets/caece970-2e01-4591-858c-1ea8842bdfd0)\",\n \"createdAt\": \"2025-04-24T12:06:52Z\",\n \"closedAt\": \"2025-06-03T21:27:46Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 7\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6bNbeZ\",\n \"title\": \"Eliza (AGI)\",\n \"author\": \"lalalune\",\n \"number\": 5194,\n \"body\": \"This PR adds everything needed to enable Eilza, a new generally capable and intelligent agent who can self-improve.\\r\\n\\r\\nThis is a mega PR that changes several things necessary to enable much more expansive capability, including action chaining. Bootstrap has been refactored to message handling. Trust, Research, Secrets, Autonomy, Autocoder, Rolodex and Todo are all in development and will be pushed shortly to enable all of this.\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-06-19T08:07:07Z\",\n \"mergedAt\": null,\n \"additions\": 135487,\n \"deletions\": 6548\n },\n {\n \"id\": \"PR_kwDOMT5cIs6aiHxq\",\n \"title\": \"feat: Split server package from CLI (continued shaw's PR)\",\n \"author\": \"wtfsayo\",\n \"number\": 5122,\n \"body\": \"## Summary\\n- Split server functionality into separate `@elizaos/server` package\\n- Maintains full backward compatibility with existing CLI integrations\\n- Enables independent usage of server components\\n- Updated all CLI imports to use the new server package\\n\\n## Test plan\\n- [x] All existing CLI tests pass\\n- [x] Server package builds and exports correctly\\n- [x] Backward compatibility maintained\\n- [x] Integration tests verify CLI + server work together\\n- [x] Type safety preserved across package boundaries\\n\\nGenerated with [Claude Code](https://claude.ai/code)\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-06-14T14:36:18Z\",\n \"mergedAt\": \"2025-06-15T19:40:08Z\",\n \"additions\": 68264,\n \"deletions\": 2875\n },\n {\n \"id\": \"PR_kwDOMT5cIs6akiPi\",\n \"title\": \"Add server, add tests\",\n \"author\": \"lalalune\",\n \"number\": 5125,\n \"body\": \"This PR adds detailed tests to core, server, project-starter and plugin-starter\\r\\n\\r\\nProject-starter and plugin-starter have had frontends added with cypress testing, to make frontend development easier and more clear\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-06-15T05:58:46Z\",\n \"mergedAt\": \"2025-06-15T07:32:19Z\",\n \"additions\": 62764,\n \"deletions\": 3574\n },\n {\n \"id\": \"PR_kwDOMT5cIs6akL6T\",\n \"title\": \"DRAFT feat: quickswap plugin \",\n \"author\": \"monilpat\",\n \"number\": 5123,\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-06-15T02:29:25Z\",\n \"mergedAt\": null,\n \"additions\": 57824,\n \"deletions\": 75\n },\n {\n \"id\": \"PR_kwDOMT5cIs6azVR3\",\n \"title\": \"chore: v1.0.10\",\n \"author\": \"ChristopherTrimboli\",\n \"number\": 5150,\n \"body\": \"\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-06-16T23:22:29Z\",\n \"mergedAt\": \"2025-06-20T03:23:56Z\",\n \"additions\": 48113,\n \"deletions\": 11390\n }\n ],\n \"codeChanges\": {\n \"additions\": 193135,\n \"deletions\": 114260,\n \"files\": 860,\n \"commitCount\": 1169\n },\n \"completedItems\": [\n {\n \"title\": \"Update README_MY.md\",\n \"prNumber\": 4840,\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# Relates to\\r\\n\\r\\nFixes #4763 \\r\\n\\r\\n\\r\\n\\r\\n# \"\n },\n {\n \"title\": \"fix: linter formatting issues\",\n \"prNumber\": 4878,\n \"type\": \"bugfix\",\n \"body\": \"Fixes linter CI check.\"\n },\n {\n \"title\": \"fix: docs readme build, agent name variable\",\n \"prNumber\": 4877,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix errors in CHANGELOG.md\",\n \"prNumber\": 4875,\n \"type\": \"bugfix\",\n \"body\": \"Hey team! Fixed error\\r\\n\\r\\nCHANGELOG.md\\r\\n`Seperated` - `Separated`\\r\\n`characteres` - `characters`\"\n },\n {\n \"title\": \"chore: Enhances core package build process\",\n \"prNumber\": 4874,\n \"type\": \"other\",\n \"body\": \"Refactors the core package's build process for improved modularity and maintainability.\\r\\n\\r\\n- Adds dedicated entry points for different API versions.\\r\\n- Updates the build configuration to use `tsup` for all build tasks.\\r\\n- Enables declaratio\"\n },\n {\n \"title\": \"fix: elizaos start for plugins\",\n \"prNumber\": 4873,\n \"type\": \"bugfix\",\n \"body\": \"fixes forceful telegram, discord plugins etc\"\n },\n {\n \"title\": \"fix: Removes plugin-specification submodule\",\n \"prNumber\": 4871,\n \"type\": \"bugfix\",\n \"body\": \"Removes the plugin-specification submodule from the repository.\\n\\nThis change simplifies the project structure by removing an unused submodule.\"\n },\n {\n \"title\": \"fix: failing CLI CI test suites\",\n \"prNumber\": 4870,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\nFix multiple failing test suites to achieve 100% test success rate. These comprehensive fixes address test expectation mismatches, improve error handling, and ensure CI pipeline stability.\\n\\n## Fixed Tests\\n\\n### 1. **test_plugins.b\"\n },\n {\n \"title\": \"chore: Optimize plugin loading to reduce startup log spam\",\n \"prNumber\": 4868,\n \"type\": \"other\",\n \"body\": \"## Summary\\r\\n- Implement smart strategy selection that checks file existence before attempting imports to find optimal path in one shot\\r\\n- Reorder import strategies to prioritize most likely successful paths (package.json entry first, then c\"\n },\n {\n \"title\": \"Update README_IND.md\",\n \"prNumber\": 4867,\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- **Refactor**\\n\\t- Streamlined and modernized the update command for improved reliability and maintainability.\\n\\t- Enhanced error handling\"\n },\n {\n \"title\": \"chore: update twitter envs\",\n \"prNumber\": 4883,\n \"type\": \"other\",\n \"body\": \"This pull request introduces changes to standardize Twitter-related environment variables and configuration settings across multiple files and documentation. The key updates include renaming variables for consistency, adding missing variabl\"\n },\n {\n \"title\": \"Update README_IND.md\",\n \"prNumber\": 4882,\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# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n - Improved validation for direct message channels to ensure only authorized participants receive messages.\\n\\n- **New Fe\"\n },\n {\n \"title\": \"fix(bootstrap): ensure action callbacks reach users and improve shouldRespond logic\",\n \"prNumber\": 4919,\n \"type\": \"bugfix\",\n \"body\": \"## Relates to\\r\\n\\r\\nResolves issue where MCP tool responses and other non-REPLY actions were generated but never sent to users.\\r\\n\\r\\n## Risks\\r\\n\\r\\n**Low** - This is a bug fix that ensures action callbacks are properly transmitted. The change is is\"\n },\n {\n \"title\": \"fix: remove duplicate @elizaos/cli dependency from root package.json\",\n \"prNumber\": 4918,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes the bun install error caused by having `@elizaos/cli` listed as both a workspace package and a root dependency.\\n\\n### Changes\\n- Removed `@elizaos/cli` from root `package.json` dependencies since it's already available as a work\"\n },\n {\n \"title\": \"fix: prevent circular dependency\",\n \"prNumber\": 4917,\n \"type\": \"bugfix\",\n \"body\": \"# Fix Circular Dependency During Plugin Testing\\r\\n\\r\\n## \ud83d\udea8 Problem\\r\\n\\r\\nWhen plugin developers run `elizaos test` from within their plugin directory, the CLI encounters a critical circular dependency issue:\\r\\n\\r\\n1. **Test Command Execution**: `el\"\n },\n {\n \"title\": \"fix: plugin route handler intercepting agent API routes\",\n \"prNumber\": 4916,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\n\\nThe plugin route handler was incorrectly trying to handle standard agent API routes, causing debug messages like:\\n\\n```\\n[2025-06-04 08:57:23] DEBUG: No valid agentId in query. Trying global match for path: /api/agents/b850bc30-45\"\n },\n {\n \"title\": \"windows compatibility\",\n \"prNumber\": 4913,\n \"type\": \"other\",\n \"body\": \"This PR enables vanilla windows to build by fixing some dependencies on bash and symlinking\"\n },\n {\n \"title\": \"fix: release ci versioning\",\n \"prNumber\": 4960,\n \"type\": \"bugfix\",\n \"body\": \"Summary of the Fix:\\r\\nThe main issue was that the CI workflow was trying to publish packages without first updating their versions to match the release tag. Here's what I changed:\\r\\n\\r\\nExtract version from tag: Remove the 'v' prefix from the g\"\n },\n {\n \"title\": \"Merge dev into main\",\n \"prNumber\": 4958,\n \"type\": \"other\",\n \"body\": \"Merge dev into main\"\n },\n {\n \"title\": \"remove faulty tests for now\",\n \"prNumber\": 4957,\n \"type\": \"tests\",\n \"body\": \"This PR just comments out failing tests, we'll need to uncomment them at some point\"\n },\n {\n \"title\": \"fix: right skip flag for plugins bats test\",\n \"prNumber\": 4956,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix(bootstrap): ensure action callbacks reach users and improve shouldRespond logic\",\n \"prNumber\": 4954,\n \"type\": \"bugfix\",\n \"body\": \"## Relates to\\r\\n\\r\\nResolves issue where MCP tool responses and other non-REPLY actions were generated but never sent to users.\\r\\n\\r\\n## Risks\\r\\n\\r\\n**Low** - This is a bug fix that ensures action callbacks are properly transmitted. The change is is\"\n },\n {\n \"title\": \"fix: release versioning in client\",\n \"prNumber\": 4952,\n \"type\": \"bugfix\",\n \"body\": \"This pull request introduces changes to the build and release process as well as enhancements to the versioning logic in the codebase. The most significant updates include modifying the `release` script in `package.json` to improve versioni\"\n },\n {\n \"title\": \"fix: optimize plugin loading strategies and resolve core dependency conflicts\",\n \"prNumber\": 4949,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\n**Low** - These changes optimize existing functionality without breaking compatibility. Plugin loading still works for all plugin types, with improved performance and cleaner logs.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n-\"\n },\n {\n \"title\": \"Fix agent memory viewer not displaying memories\",\n \"prNumber\": 4948,\n \"type\": \"bugfix\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added support for filtering agent memories by room, allowing users to view memories specific to a selected room.\\n\\n\"\n },\n {\n \"title\": \"fix: make group creation work\",\n \"prNumber\": 4946,\n \"type\": \"bugfix\",\n \"body\": \"creates group and redirects to new group chat\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Updated the `ChannelType` enum values and related string literals from l\"\n },\n {\n \"title\": \"feat: plugins add env var prompting\",\n \"prNumber\": 4945,\n \"type\": \"feature\",\n \"body\": \"\\\"Screenshot\\r\\n\\r\\nThis pull request enhances the plugin installation process in the CLI by adding support f\"\n },\n {\n \"title\": \"fix: avoid infinite effect loop by guarding currentDmChannelId reset\",\n \"prNumber\": 4944,\n \"type\": \"bugfix\",\n \"body\": \"This prevents the useEffect from retriggering itself due to setting currentDmChannelId: null while including it in the dependency array.\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/db7032e7-2e51-400c-a2d2-77d202993e32)\\r\\n\"\n },\n {\n \"title\": \"chore: auto install bun in CLI\",\n \"prNumber\": 4943,\n \"type\": \"other\",\n \"body\": \"\\\"Screenshot\\r\\n\\r\\nThis pull request introduces a new feature for the ElizaOS CLI: automatic installation of\"\n },\n {\n \"title\": \"fix errors cosmos.md\",\n \"prNumber\": 4941,\n \"type\": \"bugfix\",\n \"body\": \"Hey team! Fixed errors\\r\\n\\r\\n`Successfuly` - `Successfully` x2\"\n },\n {\n \"title\": \"chore: Migrate CLI tests from Bats to Bun TypeScript\",\n \"prNumber\": 4978,\n \"type\": \"tests\",\n \"body\": \"## Summary\\n- Migrated all CLI tests from Bats shell scripts to TypeScript using Bun test runner\\n- Removed legacy `__test_scripts__/` directory and obsolete Bats-based tests\\n- Updated GitHub workflow to use new Bun TypeScript test suite\\n- Im\"\n },\n {\n \"title\": \"fix: sidebar scroll behavior + add groups to sidebar\",\n \"prNumber\": 4977,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: update messages api docs\",\n \"prNumber\": 4976,\n \"type\": \"other\",\n \"body\": \"# What does this PR do?\\n\\nUpdates documentation for the messages API to provide complete and accurate information.\\n\\n## What kind of change is this?\\n\\nDocumentation changes\\n\\n## Documentation changes needed?\\n\\n\u2705 I have updated the documentation \"\n },\n {\n \"title\": \"chore: nuke duplicate & update docs for api\",\n \"prNumber\": 4975,\n \"type\": \"other\",\n \"body\": \"# Relates to\\n\\nCode cleanup and documentation improvements for API components.\\n\\n# Risks\\n\\n**Low** - Documentation and cleanup changes with minimal impact on functionality.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nThis PR performs two main tas\"\n },\n {\n \"title\": \"feat: \ud83c\udfa8 UI/UX Improvements: Responsive Character Form + Chat Interface Enhancements\",\n \"prNumber\": 4974,\n \"type\": \"feature\",\n \"body\": \"## \ud83c\udfa8 UI/UX Improvements: Responsive Character Form + Chat Interface Enhancements\\n\\n### \ud83d\udcdd Summary\\nThis PR introduces comprehensive responsive design improvements and UI enhancements across multiple client components, focusing on better spac\"\n },\n {\n \"title\": \"feat: Add retry button for user messages in chat\",\n \"prNumber\": 4973,\n \"type\": \"feature\",\n \"body\": \"## \ud83d\udd04 Add Retry Button for User Messages in Chat\\n\\n### \ud83d\udcdd Description\\nAdds a retry button to user messages in chat bubbles, allowing users to easily resend previous messages without manually copying and pasting text. This addresses the frust\"\n },\n {\n \"title\": \"feat: enhance UI/UX with responsive buttons, universal export system, and quick profile access\",\n \"prNumber\": 4971,\n \"type\": \"feature\",\n \"body\": \"## \ud83c\udfa8 Enhanced UI/UX: Responsive Buttons, Export Functionality & Profile Access\\n\\nThis PR significantly improves the user experience across the ElizaOS client with responsive design enhancements, comprehensive export capabilities, and stream\"\n },\n {\n \"title\": \"feat: update agent configuration on restart and move ensureAgentExist\u2026\",\n \"prNumber\": 4970,\n \"type\": \"feature\",\n \"body\": \"## What does this PR do?\\n\\nMoves `ensureAgentExists` method from plugin-sql to runtime level where it belongs. The method was incorrectly placed in plugin-sql when it should be in runtime based on its operations and purpose.\\n\\n## What kind of\"\n },\n {\n \"title\": \"fix: implement real-time message deletion via SocketIO\",\n \"prNumber\": 4968,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\n**Medium** - Changes to SocketIO event handling and API routing\\r\\n- Client-side state management modifications\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Add messageDeleted and channelCleared SocketIO events\\r\\n- Implement cli\"\n },\n {\n \"title\": \"fix: Plugin Starter Template TypeScript Declarations, Standardize Git Ignores, Update READMEs\",\n \"prNumber\": 4966,\n \"type\": \"bugfix\",\n \"body\": \"# Fix Plugin Starter Template TypeScript Declarations, Standardize Git Ignores, Update READMEs\\r\\n\\r\\n## Problem\\r\\n\\r\\n**Missing TypeScript Declaration Files in Published Plugins**\\r\\n\\r\\n- Plugins created from the `plugin-starter` template were missi\"\n },\n {\n \"title\": \"fix: clean command\",\n \"prNumber\": 4965,\n \"type\": \"bugfix\",\n \"body\": \"This pull request includes a minor update to the `clean` script in the `package.json` file. The order of operations in the script was adjusted to ensure that cleaning individual packages occurs before removing and reinstalling dependencies.\"\n },\n {\n \"title\": \"refactor: Enhance create command with TEE support and improved logic\",\n \"prNumber\": 4964,\n \"type\": \"refactor\",\n \"body\": \"**Problem**\\r\\n\\r\\nThe elizaos create command was becoming cluttered and lacked a unified structure for handling different types of project creation (projects, plugins, agents). Also I found it unintuitive to pass -tee as a flag for project to \"\n },\n {\n \"title\": \"Fix/agent cli json and error handling\",\n \"prNumber\": 4963,\n \"type\": \"bugfix\",\n \"body\": \"- tiny pr to cleanup agent command with an unecessary --json option on the agent start subcommand.\\r\\n- updated agent.md doc\\r\\n- updated cli doc to not include this option\\r\\n\\r\\nunaffected:\\r\\n\\r\\nelizaos agent get --json\\r\\nelizaos agent list --json\"\n },\n {\n \"title\": \"dependencies cleanup\",\n \"prNumber\": 4962,\n \"type\": \"refactor\",\n \"body\": \"# Dependencies Cleanup\\r\\n\\r\\n## Summary\\r\\nThis PR addresses critical dependency management issues in the monorepo that were causing build failures and CLI functionality problems.\\r\\n\\r\\n## Problem\\r\\n- Unnecessary dependencies in the monorepo were ca\"\n },\n {\n \"title\": \"fix: remove logs\",\n \"prNumber\": 4961,\n \"type\": \"bugfix\",\n \"body\": \"Removing logs.\"\n },\n {\n \"title\": \"New types 2\",\n \"prNumber\": 5001,\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\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added an optional property to test command options, \"\n },\n {\n \"title\": \"fix: prompt to order actions and action description\",\n \"prNumber\": 5094,\n \"type\": \"bugfix\",\n \"body\": \"Fixes prompt ordering for actions and improves action descriptions to ensure consistent behavior.\"\n },\n {\n \"title\": \"fix: remove reply action shortcut\",\n \"prNumber\": 5093,\n \"type\": \"bugfix\",\n \"body\": \"This code was initially implemented to handle cases where the agent's response is not a simple reply action. In such cases, the reply action checks if dynamic providers are missing, and if so, it simply calls back the response message using\"\n },\n {\n \"title\": \"Fix: Runtime Initialization and Database Adapter Handling\",\n \"prNumber\": 5092,\n \"type\": \"bugfix\",\n \"body\": \"# Fix Runtime Initialization and Database Adapter Handling\\r\\n\\r\\n## Overview\\r\\n\\r\\nThis PR addresses critical issues in the Eliza runtime's initialization process and database adapter handling, focusing on stability and proper agent ID synchroniz\"\n },\n {\n \"title\": \"fix: duplicate plugins\",\n \"prNumber\": 5091,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/5086\\r\\n\\r\\nThis issue occurs because, in the usePlugins hook, we merge agentPlugins (using the @elizaos/ prefix) with registryPlugins (using the @elizaos-plugins/ prefix). As a result, the line:\"\n },\n {\n \"title\": \"fix: envs loading on default eliza\",\n \"prNumber\": 5090,\n \"type\": \"bugfix\",\n \"body\": \"Fix for envs not loading in bun run start with default character eliza.\\nThis moves the loadEnvs function higher up since was only being called for project agents.\"\n },\n {\n \"title\": \"Add agentId to MessageBusService log output\",\n \"prNumber\": 5088,\n \"type\": \"feature\",\n \"body\": \"updates the logging in MessageBusService to include the agent's ID\"\n },\n {\n \"title\": \"feat: optimize CLI project creation with Bun offline mode\",\n \"prNumber\": 5087,\n \"type\": \"feature\",\n \"body\": \"## Summary\\nOptimizes CLI project creation performance in CI environments by leveraging Bun's offline mode to use cached packages instead of re-downloading them.\\n\\n## Changes\\n- **Add `preferOffline` option** to `runBunCommand` for faster inst\"\n },\n {\n \"title\": \"Fixes CSP (Content Security Policy) \",\n \"prNumber\": 5085,\n \"type\": \"bugfix\",\n \"body\": \"Fixes CSP (Content Security Policy) related issues in the web interface.\\n\\n**Changes:**\\n- Addresses content security policy configuration\\n- Removes accidentally committed test character file from previous commits\\n\\nThis PR is now clean and re\"\n },\n {\n \"title\": \"fix: remove default bot\",\n \"prNumber\": 5083,\n \"type\": \"bugfix\",\n \"body\": \"This PR removes the Default Message Bus Agent. However, after removing its creation, I encountered the following error:\\r\\n\\r\\n\\\"Screenshot\\r\\n\"\n },\n {\n \"title\": \"feat: Enhance chat UI with improved styling and components\",\n \"prNumber\": 5111,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- Add new animated markdown component with smooth rendering and improved user experience\\n- Implement chat container with better layout structure and responsive design\\n- Add enhanced code block component with syntax highlighting u\"\n },\n {\n \"title\": \"fix: Windows compatibility for CLI tests\",\n \"prNumber\": 5110,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- Fixes Windows test failures by replacing Unix-specific commands with cross-platform equivalents\\n- Creates .cmd files instead of bash scripts for Windows mock executables \\n- Adds proper error handling for git operations and she\"\n },\n {\n \"title\": \"fix: action text in example should not be inline with action field\",\n \"prNumber\": 5109,\n \"type\": \"bugfix\",\n \"body\": \"Small update action examples are confusing as text and action fields are inline and agent does mistake when choosing action in XML format by adding it inline with text. \\r\\n\\r\\nBad example: \\r\\n\\r\\n```\\r\\nassistant: I'll help you transfer 1 ETH to 0x\"\n },\n {\n \"title\": \"fix: card padding\",\n \"prNumber\": 5108,\n \"type\": \"bugfix\",\n \"body\": \"\\\"Screenshot\\r\\n\"\n },\n {\n \"title\": \"fix: fixed scroll behavior on home route\",\n \"prNumber\": 5107,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: create route full width\",\n \"prNumber\": 5106,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: misc ui stuff\",\n \"prNumber\": 5105,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: duplicate memory\",\n \"prNumber\": 5103,\n \"type\": \"bugfix\",\n \"body\": \"fix the issue that when the last memory is removed or a new agent is created, two memory entries appear in the dropdown:\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/3505a117-2977-4762-b735-e30ea87b2ce0)\\r\\n\"\n },\n {\n \"title\": \"chore: store central msg bus response to memory\",\n \"prNumber\": 5102,\n \"type\": \"other\",\n \"body\": \"Stores central message bus responses to memory for better message tracking and context persistence across agent communications.\"\n },\n {\n \"title\": \"feat: Log prompts for actions.\",\n \"prNumber\": 5099,\n \"type\": \"feature\",\n \"body\": \"This pull request introduces enhancements to the agent runtime and client-side components to improve tracking and display of actions, prompts, and associated metadata. Key changes include adding support for tracking prompts during runtime a\"\n },\n {\n \"title\": \"fix: load actual default character\",\n \"prNumber\": 5098,\n \"type\": \"bugfix\",\n \"body\": \"This is a follow on to my previous PR, default char ENVs were never being loaded, this also exposed wrong function import, now default eliza is truly being loaded in CLI monorepo.\"\n },\n {\n \"title\": \"feat: Split server package from CLI (continued shaw's PR)\",\n \"prNumber\": 5122,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- Split server functionality into separate `@elizaos/server` package\\n- Maintains full backward compatibility with existing CLI integrations\\n- Enables independent usage of server components\\n- Updated all CLI imports to use the new\"\n },\n {\n \"title\": \"chore: Update Postman collection with missing API endpoints\",\n \"prNumber\": 5120,\n \"type\": \"other\",\n \"body\": \"## Summary\\nUpdated the Postman collection to include all missing API endpoints discovered through comprehensive codebase analysis.\\n\\n### Changes Made:\\n- **Enhanced Agent Logs**: Added query parameters for filtering (roomId, type, count, offs\"\n },\n {\n \"title\": \"Remove link with duplicated id from sidebars\",\n \"prNumber\": 5119,\n \"type\": \"other\",\n \"body\": \"This PR fixes the Next navigation button bug in the Core Concepts - Overview section which pointed to the same page instead of Core Concepts - Actions by removing the unnecessary link section.\"\n },\n {\n \"title\": \"fix: transcription api\",\n \"prNumber\": 5118,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: file uploading\",\n \"prNumber\": 5115,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/5116\\r\\n\\r\\nThis PR resolves an issue with media file uploads in the GUI. File uploads are now working as expected.\\r\\nNote: Media processing features (e.g., transcription, image description) are n\"\n },\n {\n \"title\": \"fix: resolve CLI test failures with circular dependency and missing runtime methods\",\n \"prNumber\": 5135,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\nFixes critical test failures in CI/CD pipeline that were blocking development workflows.\\n\\n## Issues Fixed\\n- **Circular Dependency**: `parseBooleanFromText is not a function` errors in dummy services tests\\n- **Missing Runtime Meth\"\n },\n {\n \"title\": \"docs: comprehensive documentation accuracy and consistency updates\",\n \"prNumber\": 5134,\n \"type\": \"docs\",\n \"body\": \"## Summary\\nComprehensive review and update of ElizaOS documentation to ensure accuracy, consistency, and alignment with current codebase implementation.\\n\\n## Changes Made\\n\\n### \ud83d\udd27 API Router Documentation\\n- **Added descriptive comments** to A\"\n },\n {\n \"title\": \"Fix Typo in Unfollow Room Action and Variable Name in Plugin-Bootstrap\",\n \"prNumber\": 5130,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\nDescription:\\r\\nThis pull request addresses two minor issues in the codebase:\\r\\n1. Corrects a typo in the unfollowRoomAction response text from \\\"stahp followin dis room plz\\\" to \\\"stahp following dis room plz\\\" in packages/plugin-bootstrap/sr\"\n },\n {\n \"title\": \"fix bootstrap evaluator callbacks\",\n \"prNumber\": 5129,\n \"type\": \"bugfix\",\n \"body\": \"Evaluator callbacks seem unhandled.\\r\\n\\r\\nThis PR forwards the callback handler to `runtime.evaluate()` in favor of passing an empty closure\"\n },\n {\n \"title\": \"fix: agent is thinking...\",\n \"prNumber\": 5128,\n \"type\": \"bugfix\",\n \"body\": \"This pull request introduces changes to improve user input handling in a chat application, focusing on better synchronization between the server and client when input is disabled or re-enabled. The most important changes involve emitting co\"\n },\n {\n \"title\": \"Fix Typos in Plugin Documentation for Flow and MultiversX\",\n \"prNumber\": 5127,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\nDescription: \\r\\nThis pull request corrects minor typographical errors in the documentation files for the Flow and MultiversX plugins:\\r\\n\\r\\n- Fixed the spelling of \\\"Registration\\\" in the Flow plugin documentation.\\r\\n- Corrected the spelling \"\n },\n {\n \"title\": \"chore: strict cli, fix types\",\n \"prNumber\": 5126,\n \"type\": \"bugfix\",\n \"body\": \"This pull request focuses on improving error handling, updating dependencies, and making minor refactorings across the `packages/cli` codebase. The most significant changes enhance robustness by ensuring error messages are properly handled,\"\n },\n {\n \"title\": \"Add server, add tests\",\n \"prNumber\": 5125,\n \"type\": \"feature\",\n \"body\": \"This PR adds detailed tests to core, server, project-starter and plugin-starter\\r\\n\\r\\nProject-starter and plugin-starter have had frontends added with cypress testing, to make frontend development easier and more clear\"\n },\n {\n \"title\": \"fix: filter messages by current chat (channelId) & remove unnecessary\u2026\",\n \"prNumber\": 5149,\n \"type\": \"bugfix\",\n \"body\": \"Fixes message filtering to properly scope messages to the current chat/channel by channelId. Removes unnecessary code that was causing messages to appear across different chats.\\r\\n\\r\\n**What this fixes:**\\r\\n- Messages now properly filtered by c\"\n },\n {\n \"title\": \"fix: remove evaluators from messageHandler prompt\",\n \"prNumber\": 5148,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\nNone, I can open an issue if necessary and update this.\\r\\n\\r\\n# Background\\r\\nThe default `messageHandler` prompt contains an entry for the AI to choose relevant evaluators to be run after handling the processed message. At the mom\"\n },\n {\n \"title\": \"fix(autodoc): improve TypeScript parser robustness and exclude client package\",\n \"prNumber\": 5147,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\nThe autodoc workflow is experiencing TypeScript parsing errors when processing React/JSX components, causing noise in the documentation generation process. Examples from recent runs:\\n\\n```\\nError parsing TypeScript file: Unexpected\"\n },\n {\n \"title\": \"fix(ci): remove frozen-lockfile flag from autodoc workflow bun install\",\n \"prNumber\": 5146,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\nThe autodoc workflow is failing during dependency installation with the error:\\n```\\nerror: lockfile had changes, but lockfile is frozen\\nnote: try re-running without --frozen-lockfile and commit the updated lockfile\\nError: Process \"\n },\n {\n \"title\": \"fix(ci): remove npm cache from autodoc workflow Node.js setup\",\n \"prNumber\": 5145,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\nThe autodoc workflow is failing during Node.js setup with the error:\\n```\\nError: Dependencies lock file is not found in /home/runner/work/eliza/eliza. \\nSupported file patterns: package-lock.json,npm-shrinkwrap.json,yarn.lock\\n```\\n\\n\"\n },\n {\n \"title\": \"fix(ci): resolve git authentication issues in autodoc workflow\",\n \"prNumber\": 5144,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\nThe autodoc workflow is failing at the \\\"Checkout repository\\\" step with git authentication errors, as seen in [workflow run #871](https://github.com/elizaOS/eliza/actions/runs/15688882533/job/44198905695).\\n\\n**Error:**\\n```\\ncould no\"\n },\n {\n \"title\": \"fix(ci): resolve autodoc workflow dependency installation failures\",\n \"prNumber\": 5143,\n \"type\": \"bugfix\",\n \"body\": \"## Problem\\nThe autodoc workflow was failing during the \\\"Install root dependencies\\\" step with exit code 1, as seen in [workflow run #870](https://github.com/elizaOS/eliza/actions/runs/15688678497/job/44198237376).\\n\\n## Root Causes Identified\\n\"\n },\n {\n \"title\": \"fix: gui resend\",\n \"prNumber\": 5141,\n \"type\": \"bugfix\",\n \"body\": \"Currently, the resend (retry) button only works for older messages \u2014 specifically, messages that were sent before restarting the dev server. For newly sent messages, clicking the resend button doesn't do anything.\\r\\n\\r\\nThis PR fixes the issue\"\n },\n {\n \"title\": \"Move getContentTypeFromMimeType to core utils for reusability\",\n \"prNumber\": 5138,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: support all media type\",\n \"prNumber\": 5137,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: Add CLI tests, server tests, plugin-sql tests\",\n \"prNumber\": 5136,\n \"type\": \"feature\",\n \"body\": \"This PR adds a ton of coverage\\r\\n\\r\\nStill a few small spots that need work, though!\"\n },\n {\n \"title\": \"chore: update faq, quickstart, core docs\",\n \"prNumber\": 5164,\n \"type\": \"other\",\n \"body\": \"## Summary\\n\\nUpdates core documentation files including FAQ, quickstart guide, and core documentation to improve clarity and accuracy.\\n\\n## Changes\\n- Updated FAQ documentation with latest information \\n- Refreshed quickstart guide with curren\"\n },\n {\n \"title\": \"fix(docs): update ElizaOS documentation link to new official URL\",\n \"prNumber\": 5162,\n \"type\": \"bugfix\",\n \"body\": \"Replaced the outdated ElizaOS documentation link (https://elizaos.github.io/docs) with the current official documentation URL (https://eliza.how/docs/intro) in the Eliza partner page. This ensures users are directed to the latest and most a\"\n },\n {\n \"title\": \"feat: Add Ollama as AI provider option in create command\",\n \"prNumber\": 5160,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nAdds Ollama as the fourth AI provider option in the `elizaos create` command, alongside existing Local AI, OpenAI, and Anthropic options.\\n\\n## Changes Made\\n\\n### Core Implementation\\n- **Added Ollama to AI model selection** (`packa\"\n },\n {\n \"title\": \"docs: add CLAUDE.md for AI assistant guidance\",\n \"prNumber\": 5158,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- Add comprehensive CLAUDE.md file to guide AI assistants working in this repository\\n- Documents project architecture, development workflow, and critical rules\\n- Covers monorepo structure, component system, and testing requiremen\"\n },\n {\n \"title\": \"fix project loading on windows machines\",\n \"prNumber\": 5156,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n[bug loading projects on windows](https://github.com/elizaOS/eliza/issues/5155)\\r\\n\\r\\n\\nDatabase relationship management and agent cleanup functionality\\n\\n# Risks\\n\\n**Medium** - Changes database deletion behavior which could affect data integrity and related records\\n\\n# Background\\n\\n#\"\n },\n {\n \"title\": \"refactor(into-5167): consolidate character loading logic and eliminate duplication (Phase 1)\",\n \"prNumber\": 5169,\n \"type\": \"refactor\",\n \"body\": \"$(cat <<'EOF'\\n## Summary\\n\\nThis PR implements **Phase 1** of the project loading refactor outlined in issue #5168. The primary focus is eliminating the massive code duplication between CLI and server character loading logic by consolidating \"\n },\n {\n \"title\": \"feat(after-5169): implement Zod-based character validation with safe JSON parsing\",\n \"prNumber\": 5167,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n\\nThis PR implements comprehensive Zod-based character validation with safe JSON parsing to address the issues outlined in #5166.\\n\\n## Changes Made\\n\\n### \ud83d\udd27 Core Schema Implementation\\n- **New File**: `packages/core/src/schemas/chara\"\n },\n {\n \"title\": \"fix: tweak media content\",\n \"prNumber\": 5165,\n \"type\": \"bugfix\",\n \"body\": \"Fix media content color contrast, text truncation, and padding adjustments\"\n },\n {\n \"title\": \"fix: add server tests back fully fixed\",\n \"prNumber\": 5231,\n \"type\": \"feature\",\n \"body\": \"This pull request introduces several changes to the testing infrastructure and codebase for the `@elizaos/server` package. The modifications include updates to the test runner, enhancements to mocking strategies, and adjustments to test set\"\n },\n {\n \"title\": \"fix: plugin sql unit tests\",\n \"prNumber\": 5229,\n \"type\": \"bugfix\",\n \"body\": \"This pull request focuses on improving test reliability, simplifying test setups, and enhancing code clarity across multiple files in the `plugin-sql` package. Key changes include better handling of temporary directories in tests, refactori\"\n },\n {\n \"title\": \"fix: bootstrap tests, cleanup code\",\n \"prNumber\": 5227,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: remove CLI tests from integration tests\",\n \"prNumber\": 5226,\n \"type\": \"tests\",\n \"body\": \"CLI tests were running duplicate in both integration and cli workflows, not needed.\"\n },\n {\n \"title\": \"fix: remove all CI caching\",\n \"prNumber\": 5225,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: clean core\",\n \"prNumber\": 5224,\n \"type\": \"refactor\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: env settings saving\",\n \"prNumber\": 5223,\n \"type\": \"bugfix\",\n \"body\": \"Previously, changes to environment settings could not be saved.\\r\\n\\r\\nThis PR adds the save handler to persist environment variable updates.\"\n },\n {\n \"title\": \"chore: cleanup plugin-sql\",\n \"prNumber\": 5222,\n \"type\": \"refactor\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: incorrecly scoped plugin name\",\n \"prNumber\": 5220,\n \"type\": \"bugfix\",\n \"body\": \"This pull request refines the `normalizePluginName` function in `packages/cli/src/utils/registry/index.ts` by removing duplicate and incorrect namespace formats from the list of generated plugin name variations.\\r\\n\\r\\nKey change:\\r\\n\\r\\n* [`normal\"\n },\n {\n \"title\": \"fix: create option test\",\n \"prNumber\": 5219,\n \"type\": \"bugfix\",\n \"body\": \"This pull request updates the test suite for `ElizaOS Create Commands` to reflect changes in the available AI models. Specifically, it adjusts the expected number of models and removes assertions related to the `ollama` model's title and de\"\n },\n {\n \"title\": \"feat: add Google Generative AI support and refactor CLI prompts\",\n \"prNumber\": 5217,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- Added Google Generative AI (Gemini) support to the ElizaOS CLI\\n- Simplified AI model and database selection descriptions for better clarity\\n- Created a generic provider configuration prompt function to reduce code duplication\\n-\"\n },\n {\n \"title\": \"feat: lazy load test dependencies and Discord plugin in starter templates\",\n \"prNumber\": 5215,\n \"type\": \"feature\",\n \"body\": \"## Summary\\n- Removes Cypress test dependencies and Discord plugin from default installation in starter templates\\n- Adds on-demand installation when test commands are run\\n- Reduces initial project size and speeds up `elizaos create` command\\n\"\n },\n {\n \"title\": \"refactor: improve CLI config template formatting and organization\",\n \"prNumber\": 5214,\n \"type\": \"refactor\",\n \"body\": \"## Summary\\n- Simplified and reorganized .env template for better clarity\\n- Removed redundant configuration sections\\n- Improved comment formatting with consistent separators\\n- Focused on essential configuration options\\n- Removed multi-agent \"\n },\n {\n \"title\": \"feat: open documentation links in new tab\",\n \"prNumber\": 5213,\n \"type\": \"feature\",\n \"body\": \"- Update FooterLink component to detect external URLs\\r\\n- Add target='_blank' and rel='noopener noreferrer' for external links\\r\\n- Documentation link now opens in new tab for better UX\\r\\n\\r\\n