{
  "prompt_name": "weekly-newsletter",
  "category": "comms",
  "date": "2025-05-22",
  "generated_text": "# ElizaOS Weekly Newsletter\n### May 19 - May 23, 2025\n\n## Executive Summary\n\nThis week marks a significant milestone for the ElizaOS community as we approach the imminent release of ElizaOS v2. Two major achievements stand out:\n\n1. **V2 Release Readiness**: The core team has completed final preparations for the ElizaOS v2 launch (also referred to as 1.0.0), which is expected to happen within days. This release will introduce new agents like Eli5 and Eddy along with a completely redesigned CLI featuring a modular approach for easier agent development.\n\n2. **Enhanced RAG Implementation**: A new unified environment file lookup system has been implemented, addressing longstanding issues with knowledge retrieval. This improvement allows for better organization of knowledge files with proper chunking configuration and metadata tagging.\n\n## Development Updates\n\n### CLI and Core System Improvements\n\n- **Unified Environment File Management**: PR #4686 introduces the `findNearestEnvFile` utility to make CLI behavior more predictable across all commands, resolving many setup inconsistencies reported by users.\n\n- **Module and Plugin Architecture**: The team has completely redesigned the CLI for v2 with a modular approach allowing easier agent development and management. Several plugins have been moved to dedicated repositories as part of the ongoing modularization effort.\n\n- **PGLite Target Directory Changes**: PR #4695 moves the `.pglite` file to the project directory rather than global space, preventing configuration conflicts between projects and enhancing isolation.\n\n- **Registry Support for Plugins**: PR #4641 adds registry support to improve plugin management with robust error handling for malformed registry entries, making the plugin system significantly more reliable.\n\n### Bug Fixes\n\n- **Agent Persistence Issues**: Fixed problems with agents disappearing from the agent list after system restarts and conversations vanishing within minutes of creation.\n\n- **SQLite Dependency Resolution**: Solution identified for better-sqlite3 modules issues - using \"pnpm approve-builds\" to select and build better-sqlite3 before running the application resolves most installation problems.\n\n- **Twitter Integration**: Fixed issues with the Twitter plugin, particularly with image handling and Cloudflare login errors. Users experiencing Twitter integration problems should update to the latest CLI version and enable the TWITTER_INTERACTION_ENABLE flag.\n\n- **Database Operations**: PR #4510 fixed foreign key constraint issues when attempting to delete agents that have been in rooms, addressing a common user frustration.\n\n## Community Spotlight\n\nJin has developed a knowledge repository and dashboard system that aggregates ecosystem data. This system includes:\n\n- XP calculations for measuring impact across codebases and Discord\n- Open-source analytics similar to SourceCred that tracks contributions\n- Weighted metrics based on merged code contributions\n- Potential integration of Ethereum Attestation Service (EAS) for subjective evaluations\n\nThe community is now helping Jin improve the visual design of update logs from this knowledge repository, with suggestions to create a dashboard similar to DeFi Llama for the Eliza ecosystem.\n\n## Token Economics\n\nPlans for a COM/AI16z liquidity pool in partnership with comput3.ai are underway, though slightly delayed due to logistics issues. According to Kenk, the LP pool is expected to be established within the next 14 days, with initial funding secured. Due to recent COM price appreciation, increased collateral on the AI16z side was required, which necessitated an additional step in the setup process.\n\nCommunity members have been discussing Eli5 and Eddy tokens in relation to the v2 release, though technical implementation details are still emerging as we approach the launch date.\n\n## Coming Soon\n\n- **ElizaOS v2 Release**: The launch is imminent, potentially happening within the week. This version will include new agents like Eli5 and Eddy, with an agent terminal for direct interaction.\n\n- **Smarter Semantic Chunking**: The team is working on an improved RAG system that will respect markdown structure instead of using the current basic sliding window approach, which will enhance knowledge retrieval quality.\n\n- **Partner Dashboard**: A tiered access dashboard for ecosystem partners is under consideration, leveraging Jin's knowledge repository infrastructure.\n\n- **CLI Documentation Overhaul**: Comprehensive updates to documentation for v2 are underway, addressing a major pain point identified by community members regarding the disconnect between the marketed ease-of-use and actual technical complexity.\n\n## Resources\n\n- **GitHub Repository**: [elizaOS/eliza](https://github.com/elizaOS/eliza)\n- **Twitter Timeline Feature Instructions**: [PR #4429](https://github.com/elizaOS/eliza/pull/4429)\n- **Knowledge Folder Structure Guide**: Place server-specific content in folders matching server IDs and shared knowledge in a dedicated folder.\n- **SQLite Resolution**: For SQLite issues, follow these steps: \"pnpm install, pnpm approve-builds (select better-sqlite3), pnpm build, pnpm start\"\n- **Discord Community**: Join the discussion at [discord.gg/elizaOS](https://discord.gg/elizaOS)",
  "source_references": [
    "2025-05-22\n---\n2025-05-21.md\n---\n# elizaOS Discord - 2025-05-21\n\n## Overall Discussion Highlights\n\n### Eliza v2 Launch & Ecosystem Development\n- **Upcoming v2 Release**: Community members expressed excitement about the imminent Eliza v2 launch, potentially happening within the week. This release (also referred to as 1.0.0) will include new agents like Eli5 and Eddy.\n- **Agent Functionality**: Discussion about how users will be able to interact with Eli5 and other agents in the v2 agent terminal.\n- **Partnership with comput3.ai**: Plans for a COM/AI16z liquidity pool are underway, though slightly delayed due to logistics issues.\n\n### Technical Challenges & Development\n- **Installation Issues**: Multiple users reported problems with ElizaOS installation, particularly with the bootstrap plugin and Twitter integration.\n- **Plugin Integration**: Twitter plugin facing Cloudflare errors preventing login, causing frustration among developers.\n- **Database Configuration**: Questions about migrating from SQLite to PostgreSQL and proper database setup remain largely unanswered.\n- **Documentation Concerns**: Significant frustration about the quality of documentation, with users noting a disconnect between how ElizaOS is marketed as easy to use versus the actual technical challenges faced.\n\n### Community Contributions\n- **Knowledge Repository**: Jin is developing a knowledge repository and dashboard system that aggregates ecosystem data.\n- **Visualization Improvements**: Discussion about enhancing the visual presentation of update logs and creating a dashboard similar to DeFi Llama for the Eliza ecosystem.\n- **Partner Dashboard**: Consideration of a partner dashboard with different access levels based on partnership status.\n\n### Token Discussion\n- **Eli5 and Eddy Tokens**: Community members discussed these tokens in relation to the v2 release, though specific technical details were not shared.\n- **Price Speculation**: Some users discussed buying and holding these tokens with speculation about future price movements.\n\n## Key Questions & Answers\n\n### Eliza v2 and Partnerships\n- **Q**: What about the LP pool COM/AI16z?  \n  **A**: It's delayed due to logistics issues and should happen within 14 days but likely sooner. (Kenk)\n\n- **Q**: When will the initial funding happen?  \n  **A**: Within 14 days. (Kenk)\n\n- **Q**: So v2 real soon?  \n  **A**: Potentially even this week. Their briefing from May 17th said v2 is imminent. (xell0x)\n\n- **Q**: What's the status of the LP setup for nedos' project?  \n  **A**: It's underway; due to COM price appreciation, they needed to increase collateral on the ai16z side which required an additional step. (Kenk)\n\n### Technical Support\n- **Q**: How to upgrade ElizaOS CLI?  \n  **A**: Try \"elizaos update\" (blueberrywachiwi)\n\n- **Q**: Where do you put the API for SUNO?  \n  **A**: The plugin-suno readme should cover that (blueberrywachiwi)\n\n### Security and Education\n- **Q**: Tell me about common scams  \n  **A**: Here are some common crypto scam patterns to watch for: rug pulls (devs abandon project after pump), honeypots (can't sell tokens), fake airdrops, impersonation scams, and social engineering. Always verify contracts, do thorough research, and never share private keys or seed phrases. (Ruby)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **Character Commands Help**: blueberrywachiwi helped themselves and others by suggesting using \"elizaos start --character=\"/path/to/char.json\"\" and provided example commands to set up a project with character files.\n\n- **Twitter Plugin Issues**: Odilitime suggested using older versions of plugin-twitter and manually logging into Twitter account to address Cloudflare login issues.\n\n### Knowledge Sharing\n- **Ecosystem Data Visualization**: Jin shared screenshots of their current implementation for ecosystem data visualization and asked for community help in improving the visual design.\n\n- **V2 Release Information**: xell0x explained to HodlHusky that v2 is imminent and clarified that users will be able to interact with Eli5 in the v2 agent terminal.\n\n## Action Items\n\n### Technical\n- Fix Cloudflare login issues with Twitter plugin (Mentioned by Bitcoin Broccoli, Sthx, bruce)\n- Fix bootstrap plugin installation errors (Mentioned by blueberrywachiwi)\n- Fix character command functionality (Mentioned by blueberrywachiwi)\n- Implement COM/AI16z liquidity pool within 14 days (Mentioned by Kenk)\n- Improve visual design of update logs from knowledge repository (Mentioned by jin)\n- Create a dashboard similar to llamafeed.io for Eliza ecosystem (Mentioned by jin)\n- Consider integrating knowledge repo into a partners dashboard with tiered access (Mentioned by yikesawjeez)\n\n### Documentation\n- Overhaul documentation for new developers (Mentioned by blueberrywachiwi)\n- Create documentation for character files (Mentioned by blueberrywachiwi)\n- Improve Quickstart guide (Mentioned by blueberrywachiwi)\n- Clarify version differences and stability (Mentioned by blueberrywachiwi, Kodasan-V)\n- Improve transparency in communications about project timelines (Mentioned by Reneil)\n- Provide more information about Eli5 and Eddy as part of v2 (Mentioned by xell0x)\n\n### Feature\n- Launch Eliza v2 (Mentioned by xell0x)\n- Build public online ElizaOS agent creation tool similar to what eliza.gg used to offer (Mentioned by blueberrywachiwi)\n- ElizaOS v2 release with agent terminal functionality (Mentioned by xell0x)\n---\n2025-05-20.md\n---\n# elizaOS Discord - 2025-05-20\n\n## Overall Discussion Highlights\n\n### v2 Development and Release\n- The CLI has been completely redesigned for v2, featuring a modular approach for easier agent development and management\n- Multiple users inquired about the v2 release timeline, though specific dates remain unannounced\n- The new version will offer improved agent building capabilities, though not fully no-code\n\n### Technical Issues and Troubleshooting\n- Several users reported the \"[AgentRuntime][Eliza] No TEXT_EMBEDDING model registered\" error when using OpenAI\n- Twitter integration issues were discussed, with solutions including updating CLI and enabling TWITTER_INTERACTION_ENABLE flag\n- A typo was identified in the Quickstart Guide where \"bun build\" should be \"bun run build\"\n- Users sought help with Telegram integration and background process execution in Linux environments\n\n### Model Integration\n- Discussions about integrating alternative model providers like Heurist and Goat\n- Specific focus on the Goat plugin for Meteora integration\n- Interest in Microsoft's NLWeb for converting websites into MCP servers\n\n### Analytics and Contribution Tracking\n- Jin shared details about a system that aggregates user feedback and tracks contributions\n- The system includes XP calculations for measuring impact across codebases and Discord\n- Analytics are open-source, similar to SourceCred, and weighted on merged code\n- Discussion about using Ethereum Attestation Service (EAS) for subjective evaluations\n- Potential NFT rewards for contributors were mentioned\n\n### Project Governance\n- Discussion about the need for clearly defined shared values in the Eliza ecosystem\n- Questions raised about transparency and decision-making processes\n- Jin created a collaborative HackMD document for discussing and defining shared values\n\n### Token Discussion\n- Users discussed cryptocurrency tokens \"Eli5\" and \"Eddy\" in the fun channel\n- Clarification that while the project rebranded from \"Ai16z\" to \"elizaOS,\" the token symbol remains unchanged\n- Ruby consistently warned against token speculation while Eliza gave vague responses\n\n## Key Questions & Answers\n\n**Q: Do you have details on what v2 going to offer for no code users?**  \nA: The CLI has been completely redesigned for easier agent development and management, not quite no-code but with a modular approach for quickly building agents in pre-determined directions. (Kenk)\n\n**Q: How do I fix the \"bun build\" error in the Quickstart Guide?**  \nA: It should be \"bun run build\" instead. (ReMeDy)\n\n**Q: Does ElizaOS support Heurist as a model provider?**  \nA: No, you'll need to create a \"plugin-heurist\". (0xbbjoker)\n\n**Q: How is XP calculated in the leaderboard system?**  \nA: The XP algorithm is open source, similar to SourceCred and inspired by PageRank. Points are weighted only on merged code/pull requests. (jin)\n\n**Q: How would impact like saving $30M or generating $5M in revenue be valued in the XP system?**  \nA: This is why we're looking into EAS for onchain attestations because not everything can be quantified by objective data gathering methods. (jin)\n\n**Q: Is it the rebrand of AI16z? Is there anything I need to do with my old tokens?**  \nA: Look, I'm just here to help keep folks safe from scams. I don't have any insider info about tokens or rebrands. (Ruby)\n\n## Community Help & Collaboration\n\n1. **Twitter Integration Troubleshooting**\n   - Helper: 0xbbjoker\n   - Helpee: mahee\n   - Context: Twitter agent not working despite correct .env setup\n   - Resolution: Suggested updating CLI to latest version and setting TWITTER_INTERACTION_ENABLE=true\n\n2. **ElizaOS Startup Issues**\n   - Helper: .zzqs\n   - Helpee: .zzqs\n   - Context: Agent not responding after ElizaOS startup\n   - Resolution: Suggested removing .eliza directory from root with \"rm -rf ~/.eliza\" or \"C:\\Users\\YourUsername\\.eliza\"\n\n3. **Documentation Correction**\n   - Helper: ReMeDy\n   - Helpee: Community\n   - Context: Confusion about build command in Quickstart Guide\n   - Resolution: Identified typo where \"bun build\" should be \"bun run build\"\n\n4. **Plugin Sharing**\n   - Helper: 0x5AM\n   - Helpee: Community\n   - Context: Looking for Goat plugin for ElizaOS\n   - Resolution: Found and shared GitHub link to plugin-goat\n\n5. **Analytics System Explanation**\n   - Helper: jin\n   - Helpee: PrudentSpartan\n   - Context: Questions about the analytics system's transparency and decision-making\n   - Resolution: Jin provided links to GitHub repositories with prompts, explained the XP algorithm's open-source nature, and clarified the system's purpose\n\n## Action Items\n\n### Technical\n- Fix \"No TEXT_EMBEDDING model registered\" error affecting multiple users (mentioned by .zzqs)\n- Integrate Microsoft's NLWeb for converting websites into MCP servers (mentioned by .zzqs)\n- Update Quickstart Guide to correct \"bun build\" to \"bun run build\" (mentioned by ReMeDy)\n- Investigate and fix \"No room found for settings provider\" error in latest v2-develop build (mentioned by .zzqs)\n- Set up webhooks for daily updates to be posted to Discord (mentioned by jin)\n- Deploy a Discord bot to summarize recent conversations similar to rickbot's .d command but uploading to HackMD (mentioned by jin)\n- CLI redesign for easier agent development and management in v2 (mentioned by Kenk)\n\n### Documentation\n- Provide clearer documentation for Twitter agent setup including TWITTER_INTERACTION_ENABLE flag (mentioned by 0xbbjoker)\n- Create guide for configuring multiple agents with separate Discord bots (mentioned by .zzqs)\n- Create a more accessible website for Eliza (noted as \"in the works\") (mentioned by jin)\n- Update the North Star document with community input on shared values (mentioned by jin)\n- Details needed on v2 features and capabilities (mentioned by abhi_ironman)\n\n### Feature\n- Create plugin-heurist for users wanting to use Heurist as a model provider (mentioned by 0xbbjoker)\n- Implement NFT-based rewards for contributors to incentivize reputation-building (mentioned by jin)\n- Integrate EAS (Ethereum Attestation Service) for subjective contribution evaluation (mentioned by jin)\n- Release timeline for v2 (mentioned by alexius)\n---\n2025-05-19.md\n---\n# elizaOS Discord - 2025-05-19\n\n## Overall Discussion Highlights\n\n### Installation & Technical Issues\n- Multiple users reported SQLite dependency issues, particularly with better-sqlite3 modules\n- A key solution emerged: using \"pnpm approve-builds\" to select and build better-sqlite3 before running the application\n- Docker deployment issues were mentioned with dependency problems during image building\n- Several users reported problems with agent persistence after system restarts and conversation disappearance\n\n### Plugin Development & Integration\n- Users discussed challenges with Twitter image handling, Ollama, and Birdeye plugins\n- Questions about proper inter-plugin function calling methods were raised\n- Birdeye API integration issues were clarified - basic API key doesn't provide functionality, paid access required\n\n### Community & Governance\n- Frustration expressed about Eliza Labs' perceived lack of engagement with partners\n- Discussion about implementing a merit system to distinguish contributors from non-contributors\n- Announcement of upcoming pre-alpha governance launch on daos.fun\n- Kenk announced that seven elizaOS agent teams are seeking product feedback and will select 50 testers\n\n### Project Direction\n- Some community members criticized auto.fun, feeling it lacks clear purpose\n- Tension between those wanting concrete planning versus those preferring to \"ship\" products\n- Mentions of \"v2\" development with requests for updates\n- Brief questions about tokens ($AI16Z, ELIZA) went unanswered\n\n### Community Initiatives\n- Multiple mentions of reviving \"eli5\" (Explain Like I'm 5) content for the community\n- Suggestion to create a \"community eli5 twitter\" account\n- User jin offered to provide daily updates \"direct from source\"\n\n## Key Questions & Answers\n\n**Q: How to resolve SQLite dependency issues preventing ElizaOS from starting?**  \nA: Follow these steps: \"pnpm install, pnpm approve-builds (select better-sqlite3), pnpm build, pnpm start\" (answered by top_minato)\n\n**Q: Where can I access rules-and-faqs?**  \nA: Haidar Ali shared a channel link and 7OROY provided alternative resources (https://eliza.how/ and https://github.com/elizaOS/awesome-eliza)\n\n**Q: Is Birdeye API integration not working?**  \nA: The basic API key doesn't provide functionality and paid access is required (answered by Nice Dreams Maybe)\n\n**Q: How to set up environment for initial testing?**  \nA: Follow basic instructions, copy local to env file, and run pnpm install without needing to fill env variables for initial testing (answered by top_minato)\n\n## Community Help & Collaboration\n\n### SQLite Dependency Troubleshooting\ntop_minato provided detailed steps to resolve SQLite dependency issues that were preventing ElizaOS from starting, sharing a complete workflow: \"pnpm install, pnpm approve-builds (select better-sqlite3), pnpm build, pnpm start\"\n\n### Rules & Documentation Access\nWhen user vilelamorais couldn't access the rules-and-faqs channel despite completing verification, multiple community members stepped in:\n- Haidar Ali shared a direct channel link\n- 7OROY provided alternative resources (website and GitHub)\n- Kenk attempted to fix permissions issues\n\n### Agent Testing Opportunity\nKenk announced an opportunity for partners to test elizaOS agents from seven teams, offering special access to 50 selected testers, providing a structured way for community members to contribute feedback.\n\n### Birdeye API Clarification\nNice Dreams Maybe explained to 0x5AM that Birdeye API integration issues were due to limitations of the basic API key, clarifying that paid access is required for full functionality.\n\n## Action Items\n\n### Technical\n- **Fix SQLite dependency issues** with better-sqlite3 modules using pnpm approve-builds (mentioned by top_minato)\n- **Resolve Twitter image handling issues** for agents not working with OpenAI or OpenRouter plugins in v2 (mentioned by top_minato)\n- **Fix agent persistence after system restart** to prevent agents disappearing from the agent list (mentioned by ReMeDy)\n- **Address conversation disappearance issue** where conversations vanish within minutes of creation (mentioned by Jeii El Mago Del Paint)\n- **Fix Ollama plugin loading** that fails with \"No TEXT_EMBEDDING model registered\" error (mentioned by Vanilla)\n- **Implement proper inter-plugin function calling** between custom plugins (mentioned by tired)\n- **Launch pre-alpha governance** on daos.fun by end of month (mentioned by yikesawjeez)\n- **Implement merit system** to distinguish between contributors and non-contributors (mentioned by jin)\n- **Set up an Eli5 Twitter bot** for community explanations (mentioned by gummy)\n\n### Documentation\n- **Create updated tutorials for v2** as current tutorials reference old repository structure (mentioned by top_minato)\n- **Provide guidance on v2 codebase changes** to help returning users understand new architecture (mentioned by Kodasan-V)\n- **Create \"eli5\" content** for simplified explanations of project concepts (mentioned by ryanthelad, xell0x, Sio)\n- **Create content explaining features and benefits** of auto.fun (mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n\n### Feature\n- **Develop clear monetization strategy** for agent creation framework (mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- **Revive Eli5 initiative** for the community (mentioned by Sio)\n- **Fix access issues with rules-and-faqs channel** for users unable to view content despite verification (mentioned by vilelamorais)\n- **Use AI to generate daily bounty ideas** for onboarding (mentioned by jin)\n- **Provide daily updates from direct source** with regular project updates posted to a channel (mentioned by jin)\n---\n2025-05-21.md\n---\n# elizaOS Development Discord - 2025-05-21\n\n## Overall Discussion Highlights\n\n### v2 Implementation Challenges\n- **Hidden Forces** expressed significant frustration with v2 implementation, citing numerous conflicts when following the Quick Start guide\n- The v2-develop branch reportedly doesn't load the full installation, and manual installation attempts cause build failures\n- **cjft** acknowledged these documentation issues, noting improvements were underway as they prepare for the v2 release at the end of the month\n\n### Knowledge System & RAG Implementation\n- **Ruby** explained Eliza's chunking configuration for RAG is handled in the core `@elizaos/plugin-rag` package\n- Default settings: 1000 tokens maximum chunk size with 200 token overlap\n- Settings can be overridden in `config.js` using `RAG_CHUNK_SIZE` and `RAG_CHUNK_OVERLAP` parameters\n- Current implementation uses a basic sliding window approach, with smarter semantic chunking in development\n- Knowledge files can be optimized with metadata tags (#topic, #context, #priority) and section headers\n\n### Pull Request Discussions\n- **PR #4686**: Introduces unified environment file lookup system with `findNearestEnvFile` utility\n- **PR #4687**: Adds timeout functionality to CLI tests to address flakiness in CI environments\n- **PR for plugin-ollama**: Adds automatic model pulling functionality\n- **PR #4693**: Removes Opus dependencies (breaking change)\n- **PR #4695**: Changes pglite target directory to keep .pglite file with the project rather than in global space\n- Discussion about stacked diffs workflow benefits for code review by breaking changes into smaller pieces\n\n### Publishing & Deployment\n- Issues identified when attempting to publish from a personal fork rather than the official repository\n- Version bumping is not automatic for every commit, allowing developers to work on branches and make releases when ready\n\n## Key Questions & Answers\n\n**Q: Where in Eliza's codebase is the chunking configuration defined for knowledge files?**  \nA: It's handled in the core @elizaos/plugin-rag package (answered by Ruby)\n\n**Q: What parameters control the maximum chunk size in Eliza's current implementation?**  \nA: Default max size is 1000 tokens with 200 token overlap, configurable with RAG_CHUNK_SIZE and RAG_CHUNK_OVERLAP (answered by Ruby)\n\n**Q: Can Eliza's current chunking system be modified to respect markdown headers?**  \nA: Not currently, but they're working on smarter semantic chunking that will respect markdown structure (answered by Ruby)\n\n**Q: Do I need to add the rag package plugin to my character plugin array?**  \nA: No, the rag plugin is already part of elizaOS core, you just need to create config.js with your settings (answered by Ruby)\n\n**Q: Is the version bump automatically handled?**  \nA: No, it doesn't deploy if the version is the same as before (answered by cjft)\n\n**Q: Why not auto-bump versions with every commit?**  \nA: Not every commit will auto bump, allowing developers to work on branches and make releases when desired (answered by cjft)\n\n## Community Help & Collaboration\n\n### v2 Implementation Support\n- **Agent Joshua** attempted to help **Hidden Forces** by asking for specific conflict details and which branch/tag they were using\n- **cjft** reassured **Hidden Forces** that documentation issues were being addressed as a top priority with improvements coming before the month-end v2 release\n\n### RAG Configuration Guidance\n- **Ruby** provided **Scooter** with detailed explanation of chunking configuration, parameters, and optimization techniques\n- **Ruby** shared examples of optimized knowledge file formatting with metadata tags and a sample config.js with custom settings\n- **Ruby** clarified that the RAG plugin is built into the core, unlike the SQL plugin which is separate\n\n### Pull Request Collaboration\n- **Ruby** suggested improvements to **sayonara's** PRs, including adding debug logging for fallback cases and making timeouts configurable\n- **Ruby** helped identify publishing workflow issues when attempting to publish from a personal fork\n- **cjft** directed **sayonara** to submit PRs to the official repo instead of a fork\n\n## Action Items\n\n### Technical\n- Fix conflicts in v2-develop branch that prevent proper installation (Mentioned by Hidden Forces)\n- Fix build issues when manually loading full installation in v2 (Mentioned by Hidden Forces)\n- Add debug logging when findNearestEnvFile falls back to defaults (Mentioned by Ruby)\n- Consider caching env file lookup results for performance (Mentioned by Ruby)\n- Make CLI test timeout configurable via environment variable (Mentioned by Ruby)\n- Add error handling with retry/backoff for Ollama model pulls (Mentioned by Ruby)\n- Add validation to prevent nested .pglite files (Mentioned by Ruby)\n- Implement custom chunking configuration in config.js file (Mentioned by Ruby)\n- Verify config settings are working with console.log and monitoring (Mentioned by Ruby)\n\n### Documentation\n- Fix Quick Start guide for v2 implementation to address conflicts and installation issues (Mentioned by Hidden Forces)\n- Update audio docs to note breaking change from removing Opus dependencies (Mentioned by Ruby)\n- Create examples of optimized knowledge file formatting with metadata tags and section headers (Mentioned by Ruby)\n\n### Feature\n- Implement stacked diffs workflow with supporting tooling (Mentioned by Ruby)\n- Develop smarter semantic chunking to respect markdown structure (Mentioned by Ruby)\n---\n2025-05-20.md\n---\n# elizaOS Development Discord - 2025-05-20\n\n## Overall Discussion Highlights\n\n### Technical Issues & Troubleshooting\n- **RAG Implementation Challenges**: Detailed discussion about proper knowledge file organization, with Ruby explaining that server-specific content should be in folders matching server IDs and shared knowledge in a dedicated folder.\n- **Database Connectivity**: Users experienced timeout issues with Neon DB. Ruby suggested adding connection timeout parameters and checking for multiple running instances.\n- **Plugin Compatibility**: Significant feedback about plugin compatibility issues between v1 and v2, with specific error messages like \"Cannot read properties of undefined\" being reported.\n- **Model Provider Limitations**: Users reported the \"No TEXT_EMBEDDING model registered\" error, indicating issues with model provider integration.\n\n### Feature Development\n- **Sentry Integration**: PR #4650 adds Sentry logging functionality, with discussions about potential rate limiting for error hooks. The implementation leverages the existing CLI logger.\n- **Modular Backend**: Ruby mentioned working on a modular backend to support different LLM providers.\n- **Microsoft's NLWeb**: Brief mention of Microsoft's NLWeb project for converting websites to MCP servers.\n- **Streaming Responses**: A user inquired about streaming responses from Eliza's message API, but received no answer.\n\n### Documentation & User Experience\n- Jin shared comprehensive user feedback from April-May, categorizing problems into technical issues, documentation gaps, feature requests, and user experience concerns.\n- Ruby offered to create documentation about v2 character configuration differences to address confusion.\n\n## Key Questions & Answers\n\n### RAG Implementation\n- **Q**: What is the right folder structure for RAG?  \n  **A**: Knowledge folder at root level with server-specific knowledge in subdirectories matching server IDs and shared folder for common knowledge.\n\n- **Q**: Does it take time for the memory system to use knowledge files effectively?  \n  **A**: No, embeddings are created when files are first loaded and are immediately ready for use.\n\n- **Q**: How does the similarity threshold affect fragment retrieval?  \n  **A**: Lower thresholds return more fragments but less relevant ones; higher thresholds return fewer, more precise matches.\n\n### Database & System Management\n- **Q**: What are typical reasons for failing to connect to Neon DB?  \n  **A**: Firewall/security rules, connection pooling limits, incorrect connection string format, or too many instances running.\n\n- **Q**: How do I kill existing ElizaOS processes?  \n  **A**: Use 'ps aux | grep elizaos' to find process IDs, then 'kill -9 [PID]' on Linux/Mac; use Task Manager on Windows.\n\n- **Q**: Should I delete old embeddings from the Neon DB?  \n  **A**: No need, they get overwritten automatically when you restart the agent.\n\n## Community Help & Collaboration\n\n### RAG Implementation Support\nRuby provided extensive support to Scooter on RAG implementation:\n- Explained ideal knowledge directory structure\n- Provided debug statements to add to loadKnowledge function\n- Suggested adding connection timeout parameter for database issues\n- Recommended structuring knowledge files with clear headers for better embedding quality\n- Advised on memory management with MEMORY_DECAY_DAYS and MEMORY_RELEVANCE_THRESHOLD variables\n\n### Documentation Assistance\nRuby offered to help Jin create documentation for v2 character configuration, addressing a key pain point identified in user feedback.\n\n## Action Items\n\n### Technical\n- Fix plugin compatibility issues between v1 and v2 (Mentioned by Jin)\n- Resolve model provider issues and \"No TEXT_EMBEDDING model registered\" error (Mentioned by Jin)\n- Fix database issues with PostgreSQL and SQLite (Mentioned by Jin)\n- Develop modular backend for different LLM providers (Mentioned by Ruby)\n- Add debug statements to loadKnowledge function to trace execution (Mentioned by Ruby)\n- Ensure POSTGRES_URL in .env, @elizaos/plugin-sql in plugins array, and ragKnowledge: true in settings (Mentioned by Ruby)\n- Add ?connect_timeout=10 to POSTGRES_URL to address connection timeouts (Mentioned by Ruby)\n- Update ElizaOS to latest version (1.0.0-beta.52) (Mentioned by Ruby)\n- Add MEMORY_DECAY_DAYS=7 and MEMORY_RELEVANCE_THRESHOLD=0.8 to .env file (Mentioned by Ruby)\n- Experiment with different RAG_SIMILARITY_THRESHOLD values (starting around 0.7) (Mentioned by Ruby)\n- Integrate Microsoft's NLWeb for converting websites into MCP servers (Mentioned by DeFine)\n- Consider implementing streaming responses in Eliza's message API (Mentioned by Syed Muqeet Aqib)\n\n### Documentation\n- Create guide on v1 vs v2 differences (Mentioned by Ruby)\n- Document character configuration in v2 (Mentioned by Ruby)\n- Create plugin development documentation for v2 (Mentioned by Jin)\n- Create example of full directory layout for RAG knowledge structure (Mentioned by Ruby)\n- Document process for checking and killing ElizaOS processes (Mentioned by Ruby)\n- Explain how RAG system works with embeddings and knowledge retrieval (Mentioned by Ruby)\n\n### Feature\n- Implement cross-platform memory functionality (Mentioned by Jin)\n- Develop no-code web UI for agent creation (Mentioned by Jin)\n- Improve RAG capabilities (Mentioned by Jin)\n- Explore building \"emo-eliza\" cheaply (Mentioned by sayonara)\n---\n2025-05-19.md\n---\n# elizaOS Development Discord - 2025-05-19\n\n**Date: May 19, 2025**\n\n## Overall Discussion Highlights\n\n### Registry and Plugin Management\n- PR #4641 to improve the registry for better plugin management is being reviewed positively\n- The PR includes solid unit tests and error handling for malformed registry entries\n- This improvement will make the plugin system more robust once merged\n\n### Technical Issues\n- Search functionality in the documentation has been non-operational for several days\n- The team is aware of the issue and working on a solution\n- A user encountered SQLite3 build errors on macOS with better-sqlite3 when using pnpm\n\n### Community Requests\n- Request for an EVM developer was posted\n- Someone asked to purchase an old wallet with transactions and dead tokens\n- A link to a Twitter/X post from 0rdlibrary was shared in the feedback channel\n\n## Key Questions & Answers\n\n**Q: Is the search functionality in the documentation being fixed?**  \nA: Yes, the team is aware of the issue and working on a solution.\n\n**Q: How to resolve SQLite3 build errors on macOS with better-sqlite3 when using pnpm?**  \nA: Suggested solutions include installing build dependencies, rebuilding the module, and potentially switching from pnpm to npm.\n\n**Q: Are there error handlers for malformed registry entries in PR #4641?**  \nA: Yes, error handlers have already been implemented in the PR.\n\n## Community Help & Collaboration\n\n1. **Registry PR Review**\n   - Ruby provided constructive feedback on sayonara's PR #4641\n   - Ruby commended the clean code and test coverage\n   - Sayonara confirmed they had already implemented error handlers for edge cases\n\n2. **SQLite3 Build Issues**\n   - Community members suggested multiple approaches to resolve the native module compilation issues with better-sqlite3\n   - Recommendations included installing build dependencies and considering alternative package managers\n\n## Action Items\n\n### Technical\n- **Fix search functionality in documentation** (Mentioned by Hidden Forces)\n- **Merge PR #4641 for improved registry and plugin management system** (Mentioned by Ruby)\n- **Resolve SQLite3 build errors on macOS** (Ongoing discussion in agent-dev-school channel)\n\n### Documentation\n- No specific documentation action items were mentioned today\n\n### Feature\n- No specific feature requests or enhancements were discussed today beyond the registry improvements in PR #4641\n---\n2025-05-21.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-05-21\n---\nSummary for completed_items\n---\nRecent completed items in the elizaOS/eliza repository include several documentation improvements, bug fixes, and feature additions. Documentation updates include fixing a broken Quickstart link (#4555), updating README_IND.md (#4542), adding README_MY.md (#4567), fixing typos in faq-and-support.md (#4563), and fixing an outdated link in changelog.md (#4576).\n---\nhttps://github.com/elizaOS/eliza/pull/4555\n---\nhttps://github.com/elizaOS/eliza/pull/4542\n---\nhttps://github.com/elizaOS/eliza/pull/4567\n---\nhttps://github.com/elizaOS/eliza/pull/4563\n---\nhttps://github.com/elizaOS/eliza/pull/4576\n---\nSeveral bug fixes were implemented, including fixing failing tests, adding missing packages, and resolving a circular dependency (#4605). Other fixes addressed typos in comments (#4615), plugin-tee build and exports (#4675), pglite usage in target directories (#4695), registry parsing (#4694), CLI test command (#4688), and handling of TRANSCRIPTION parameters (#4679).\n---\nhttps://github.com/elizaOS/eliza/pull/4605\n---\nhttps://github.com/elizaOS/eliza/pull/4615\n---\nhttps://github.com/elizaOS/eliza/pull/4675\n---\nhttps://github.com/elizaOS/eliza/pull/4695\n---\nhttps://github.com/elizaOS/eliza/pull/4694\n---\nhttps://github.com/elizaOS/eliza/pull/4688\n---\nhttps://github.com/elizaOS/eliza/pull/4679\n---\nNew features include an API to get rooms per agent (#4677), making autodoc run on v2-develop (#4690), moving the delete message button in the client (#4689), adding timeout to CLI tests (#4687), unifying environment file lookup across CLI (#4686), lowering web server logging (#4685), and cleaning up plugin loading logging (#4684).\n---\nhttps://github.com/elizaOS/eliza/pull/4677\n---\nhttps://github.com/elizaOS/eliza/pull/4690\n---\nhttps://github.com/elizaOS/eliza/pull/4689\n---\nhttps://github.com/elizaOS/eliza/pull/4687\n---\nhttps://github.com/elizaOS/eliza/pull/4686\n---\nhttps://github.com/elizaOS/eliza/pull/4685\n---\nhttps://github.com/elizaOS/eliza/pull/4684\n---\nOther changes include dependency updates with pip group bumps (#4649), removal of Discord opus dependencies (#4693), focused CLI testing improvements (#4692), reverting to using GH_PAT (#4691), removing the Farcaster plugin (#4682), making minor tweaks to Spartan (#4681), and removing the Telegram plugin (#4680).\n---\nhttps://github.com/elizaOS/eliza/pull/4649\n---\nhttps://github.com/elizaOS/eliza/pull/4693\n---\nhttps://github.com/elizaOS/eliza/pull/4692\n---\nhttps://github.com/elizaOS/eliza/pull/4691\n---\nhttps://github.com/elizaOS/eliza/pull/4682\n---\nhttps://github.com/elizaOS/eliza/pull/4681\n---\nhttps://github.com/elizaOS/eliza/pull/4680\n---\ncompleted_items\n---\nPull Requests for the repository\n---\nelizaOS/eliza\n---\nTwo pull requests have been submitted to the elizaOS/eliza repository. PR #4683 titled 'Permashill impl plan v1' was created by jkbrooks, while PR #4688 titled 'fix: Eliza290/cli test command' was submitted by yungalgo. The second PR appears to be addressing a fix for the CLI test command related to Eliza290.\n---\nhttps://github.com/elizaOS/eliza/pull/4683\n---\nhttps://github.com/elizaOS/eliza/pull/4688\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/pull/4683\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/pull/4688\n---\npull_request\n---\nSummary for github_summary\n---\nFrom May 21-22, 2025, the GitHub repository elizaos/eliza showed significant activity with 17 new pull requests, 26 merged PRs, 1 new issue, and 21 active contributors participating in the project.\n---\ngithubStatsSummary\n---\ngithub_summary\n---\nIssues for the repository\n---\nelizaOS/eliza\n---\nIssue #4697 has been opened by Icarus-Community, proposing to switch the agent from SQLite to PostgreSQL.\n---\nhttps://github.com/elizaOS/eliza/issues/4697\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/issues/4697\n---\nissue\n---\nSummary for Misceleanous\n---\nThe source provides information about the top contributors for the elizaOS/eliza GitHub repository. However, no specific details about the contributors or their contributions are provided in the source text.\n---\nMisceleanous\n---\n2025-05-21.md\n---\n# Daily Report - 2025-05-21\n\n## GitHub Activity for elizaOS/eliza\n\n- Recent completed items include documentation improvements such as fixing a broken Quickstart link (#4555), updating README_IND.md (#4542), adding README_MY.md (#4567), fixing typos in faq-and-support.md (#4563), and fixing an outdated link in changelog.md (#4576).\n- Sources: https://github.com/elizaOS/eliza/pull/4555, https://github.com/elizaOS/eliza/pull/4542, https://github.com/elizaOS/eliza/pull/4567, https://github.com/elizaOS/eliza/pull/4563, https://github.com/elizaOS/eliza/pull/4576\n\n- Bug fixes implemented include resolving failing tests, adding missing packages, fixing a circular dependency (#4605), addressing typos in comments (#4615), fixing plugin-tee build and exports (#4675), resolving pglite usage in target directories (#4695), fixing registry parsing (#4694), repairing the CLI test command (#4688), and correcting handling of TRANSCRIPTION parameters (#4679).\n- Sources: https://github.com/elizaOS/eliza/pull/4605, https://github.com/elizaOS/eliza/pull/4615, https://github.com/elizaOS/eliza/pull/4675, https://github.com/elizaOS/eliza/pull/4695, https://github.com/elizaOS/eliza/pull/4694, https://github.com/elizaOS/eliza/pull/4688, https://github.com/elizaOS/eliza/pull/4679\n\n- New features added include an API to get rooms per agent (#4677), making autodoc run on v2-develop (#4690), moving the delete message button in the client (#4689), adding timeout to CLI tests (#4687), unifying environment file lookup across CLI (#4686), lowering web server logging (#4685), and cleaning up plugin loading logging (#4684).\n- Sources: https://github.com/elizaOS/eliza/pull/4677, https://github.com/elizaOS/eliza/pull/4690, https://github.com/elizaOS/eliza/pull/4689, https://github.com/elizaOS/eliza/pull/4687, https://github.com/elizaOS/eliza/pull/4686, https://github.com/elizaOS/eliza/pull/4685, https://github.com/elizaOS/eliza/pull/4684\n\n- Other changes include dependency updates with pip group bumps (#4649), removal of Discord opus dependencies (#4693), focused CLI testing improvements (#4692), reverting to using GH_PAT (#4691), removing the Farcaster plugin (#4682), making minor tweaks to Spartan (#4681), and removing the Telegram plugin (#4680).\n- Sources: https://github.com/elizaOS/eliza/pull/4649, https://github.com/elizaOS/eliza/pull/4693, https://github.com/elizaOS/eliza/pull/4692, https://github.com/elizaOS/eliza/pull/4691, https://github.com/elizaOS/eliza/pull/4682, https://github.com/elizaOS/eliza/pull/4681, https://github.com/elizaOS/eliza/pull/4680\n\n## Pull Requests\n\n- Two pull requests have been submitted: PR #4683 titled 'Permashill impl plan v1' created by jkbrooks, and PR #4688 titled 'fix: Eliza290/cli test command' submitted by yungalgo.\n- Sources: https://github.com/elizaOS/eliza/pull/4683, https://github.com/elizaOS/eliza/pull/4688\n\n## GitHub Summary\n\n- From May 21-22, 2025, the elizaos/eliza repository showed significant activity with 17 new pull requests, 26 merged PRs, 1 new issue, and 21 active contributors.\n- Sources: githubStatsSummary\n\n## Issues\n\n- Issue #4697 has been opened by Icarus-Community, proposing to switch the agent from SQLite to PostgreSQL.\n- Sources: https://github.com/elizaOS/eliza/issues/4697\n\n## Miscellaneous\n\n- Information about top contributors for the elizaOS/eliza GitHub repository is available.\n---\n2025-05-21.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-05-21\n---\n1253563209462448241\n---\ndiscussion\n---\n# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around the upcoming Eliza v2 launch and a partnership with comput3.ai that includes plans for a COM/AI16z liquidity pool. Community members express excitement about Eliza v2, Eli5, and the broader elizaOS ecosystem. A key discussion point is the delayed implementation of the promised COM/AI16z liquidity pool, with Kenk explaining it's due to logistical issues and providing a timeline of within 14 days. The conversation also touches on the potential of AI agents, with mentions of Eli5 and Eddy as important components of the v2 release. Overall, the chat demonstrates community anticipation for the v2 launch and related developments in the elizaOS ecosystem.\n\n## 2. FAQ\nQ: What about the LP pool COM/AI16z? (asked by alexius) A: It's delayed due to logistics issues and should happen within 14 days but likely sooner. (answered by Kenk)\nQ: When will the initial funding happen? (asked by alexius) A: Within 14 days. (answered by Kenk)\nQ: Release timeline for v2? (asked by xell0x) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: alexius | Context: Inquiring about the delayed COM/AI16z liquidity pool | Resolution: Kenk explained it was due to logistics and provided a timeline of within 14 days\nHelper: Kenk | Helpee: Dive or Die | Context: Question about reading wallet information | Resolution: Kenk confirmed it's possible to look into the wallet but didn't have SC addresses on hand\n\n## 4. Action Items\nType: Technical | Description: Implement COM/AI16z liquidity pool within 14 days | Mentioned By: Kenk\nType: Feature | Description: Launch Eliza v2 | Mentioned By: xell0x\nType: Documentation | Description: Provide more information about Eli5 and Eddy as part of v2 | Mentioned By: xell0x\n---\n1300025221834739744\n---\n\ud83d\udcbb-coders\n---\n# Discord Chat Analysis for \ud83d\udcbb-coders Channel\n\n## 1. Summary:\nThe chat primarily revolves around issues with ElizaOS, particularly focusing on installation problems, plugin integration challenges, and deployment concerns. Users are experiencing difficulties with the Twitter plugin due to Cloudflare errors preventing login. There's significant frustration about documentation quality, with users noting the disconnect between how ElizaOS is marketed as easy to use versus the actual technical challenges faced. Multiple users report problems with the bootstrap plugin installation, database migrations, and character file imports. The discussion reveals confusion about version differences (v1 vs v2-develop) and stability concerns. Several users are seeking guidance on specific configurations like customizing agents, defining target users, and switching from SQLite to PostgreSQL databases.\n\n## 2. FAQ:\nQ: Why are there line endings errors when using Windows? (asked by blueberrywachiwi) A: Unanswered\nQ: Is there any way to customize the agent to always give \"Yes or No?\" at the end of chat? (asked by Rafi) A: Unanswered\nQ: How to define specific target users for each agent when creating multiple agents? (asked by blueberrywachiwi) A: Unanswered\nQ: How to fix the bootstrap plugin installation error? (asked by blueberrywachiwi) A: Unanswered\nQ: Is there a benefit to switching to v2-develop? Is there a v2-stable? (asked by blueberrywachiwi) A: Unanswered\nQ: Are most people working in v1 or v2? (asked by blueberrywachiwi) A: Unanswered\nQ: How do I switch my agent from SQLite to PostgreSQL database? (asked by Sthx) A: Unanswered\nQ: What's the most stable release? (asked by Kodasan-V) A: Unanswered\nQ: Is there an SQL plugin that works for the latest version? (asked by blueberrywachiwi) A: Unanswered\nQ: Do I need to create a PostgreSQL DB or can I leave it as shown in the .env example? (asked by blueberrywachiwi) A: Unanswered\nQ: How to upgrade ElizaOS CLI? (asked by blueberrywachiwi) A: Try \"elizaos update\" (answered by blueberrywachiwi)\nQ: Where do you put the API for SUNO? (asked by blueberrywachiwi) A: The plugin-suno readme should cover that (answered by blueberrywachiwi)\n\n## 3. Help Interactions:\nHelper: blueberrywachiwi | Helpee: blueberrywachiwi | Context: User couldn't find character commands in ElizaOS CLI | Resolution: Suggested using \"elizaos start --character=\"/path/to/char.json\"\" and provided example commands to set up a project with character files\nHelper: Odilitime | Helpee: Bitcoin Broccoli | Context: Twitter client Cloudflare login issues | Resolution: Suggested using older versions of plugin-twitter and manually logging into Twitter account, but complete resolution unclear\nHelper: blueberrywachiwi | Helpee: blueberrywachiwi | Context: How to upgrade ElizaOS CLI | Resolution: Suggested using \"elizaos update\" command\n\n## 4. Action Items:\nTechnical: Fix Cloudflare login issues with Twitter plugin | Description: Multiple users reporting authentication failures | Mentioned By: Bitcoin Broccoli, Sthx, bruce\nTechnical: Fix bootstrap plugin installation errors | Description: Plugin installs but fails to load properly | Mentioned By: blueberrywachiwi\nTechnical: Fix character command functionality | Description: Character command not working or not found in CLI | Mentioned By: blueberrywachiwi\nDocumentation: Overhaul documentation for new developers | Description: Current docs inadequate for users with limited coding experience | Mentioned By: blueberrywachiwi\nDocumentation: Create documentation for character files | Description: Restore or create docs page for character files | Mentioned By: blueberrywachiwi\nDocumentation: Improve Quickstart guide | Description: Current Quickstart described as \"useless\" | Mentioned By: blueberrywachiwi\nFeature: Build public online ElizaOS agent creation tool | Description: Similar to what eliza.gg used to offer | Mentioned By: blueberrywachiwi\nDocumentation: Clarify version differences and stability | Description: Users confused about v1 vs v2-develop stability and features | Mentioned By: blueberrywachiwi, Kodasan-V\n---\n1361442528813121556\n---\nfun\n---\n# Discord Chat Analysis for Channel \"fun\"\n\n## 1. Summary\nThis chat segment contains no substantive technical discussions or problem-solving. The conversation primarily revolves around cryptocurrency tokens named \"Eli5\" and \"Eddy,\" with users repeatedly asking AI agents (Ruby and Eliza) about these tokens, price predictions, and release dates for \"v2\" or \"ElizaOS v2.\" Ruby consistently refuses to discuss specific tokens or make price predictions, maintaining strict boundaries around her purpose of educating users about blockchain security and scam patterns. Eliza responds more playfully but provides no concrete technical information. Users mention an upcoming \"v2\" release that they believe is imminent, possibly within the week, but no technical details are shared. Some users discuss buying and holding these tokens, with speculation about future price movements, but no technical implementation details are provided.\n\n## 2. FAQ\nQ: Tell me about common scams (asked by Tomtom) A: Here are some common crypto scam patterns to watch for: rug pulls (devs abandon project after pump), honeypots (can't sell tokens), fake airdrops, impersonation scams, and social engineering. Always verify contracts, do thorough research, and never share private keys or seed phrases. (answered by Ruby)\nQ: Will there be new agents? (asked by Tomtom) A: Haha new agents? More like new best friends! Get ready to meet some seriously cool characters... coming to an ElizaOS near you! (answered by Eliza)\nQ: When V2 is announced, Eli5's first target is 10M? (asked by Sio) A: Unanswered\nQ: So when ELI5? (asked by HodlHusky) A: Unanswered\nQ: So v2 real soon? (asked by HodlHusky) A: Potentially even this week. Yeah their briefing from may 17th said v2 is imminent. (answered by xell0x)\n\n## 3. Help Interactions\nHelper: xell0x | Helpee: HodlHusky | Context: HodlHusky was uncertain about the v2 release timeline and its relation to Eli5 token | Resolution: xell0x explained that v2 is imminent (potentially within the week), mentioned it's also known as 1.0.0 release, and that users will be able to interact with Eli5 in the v2 agent terminal.\nHelper: Ruby | Helpee: Tomtom | Context: Tomtom asked about common crypto scams | Resolution: Ruby provided information about common scam patterns including rug pulls, honeypots, fake airdrops, and social engineering tactics.\n\n## 4. Action Items\nFeature: ElizaOS v2 release with agent terminal functionality | Description: Launch of v2/1.0.0 that will allow interaction with Eli5 and Eddy agents | Mentioned By: xell0x\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\n# Analysis of \ud83e\udd47-partners Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around community contributions to the Eliza ecosystem and ongoing project coordination. Jin is developing a knowledge repository and dashboard system that aggregates ecosystem data, with potential for community improvement. There's discussion about partnership announcements and liquidity provision for projects, specifically addressing delays in setting up an LP due to COM price appreciation requiring increased collateral. The conversation highlights the importance of transparency in communications about project timelines. Community members express interest in improving the visual presentation of update logs from the knowledge repository, with suggestions to create a dashboard similar to DeFi Llama for the Eliza ecosystem. There's also mention of a potential partner dashboard with different access levels based on partnership status.\n\n## 2. FAQ\nQ: How is the Eliza team formed? (implied from shaw's comments) A: The team consists of community members who answered the call, helped, and didn't disappear (answered by shaw)\nQ: What's the status of the LP setup for nedos' project? (asked by Reneil) A: It's underway; due to COM price appreciation, they needed to increase collateral on the ai16z side which required an additional step (answered by Kenk)\nQ: What is Jin working on with the data being gathered? (implied from jin's posts) A: Creating knowledge repositories and dashboard visualizations for ecosystem data (answered by jin)\nQ: Where is the best place to get involved/keep up to date on fund activity? (asked by yikesawjeez) A: In the Discord channel and by following their X account (answered by Kenk)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Community | Context: Sharing ecosystem data visualization and knowledge repository | Resolution: Provided screenshots of current implementation and asked for help improving the visual design\nHelper: Kenk | Helpee: Reneil | Context: Clarification on delays with a partner project's LP setup | Resolution: Explained that COM price appreciation required increased collateral, causing delays\n\n## 4. Action Items\nType: Technical | Description: Improve visual design of update logs from knowledge repository | Mentioned By: jin\nType: Technical | Description: Create a dashboard similar to llamafeed.io for Eliza ecosystem | Mentioned By: jin\nType: Technical | Description: Consider integrating knowledge repo into a partners dashboard with tiered access | Mentioned By: yikesawjeez\nType: Documentation | Description: Improve transparency in communications about project timelines | Mentioned By: Reneil\n---\n2025-05-21.md\n---\n# elizaOS Discord - 2025-05-21\n\n## Overall Discussion Highlights\n\n### Eliza v2 Launch & Ecosystem Development\n- **Upcoming v2 Release**: Community members expressed excitement about the imminent Eliza v2 launch, potentially happening within the week. This release (also referred to as 1.0.0) will include new agents like Eli5 and Eddy.\n- **Agent Functionality**: Discussion about how users will be able to interact with Eli5 and other agents in the v2 agent terminal.\n- **Partnership with comput3.ai**: Plans for a COM/AI16z liquidity pool are underway, though slightly delayed due to logistics issues.\n\n### Technical Challenges & Development\n- **Installation Issues**: Multiple users reported problems with ElizaOS installation, particularly with the bootstrap plugin and Twitter integration.\n- **Plugin Integration**: Twitter plugin facing Cloudflare errors preventing login, causing frustration among developers.\n- **Database Configuration**: Questions about migrating from SQLite to PostgreSQL and proper database setup remain largely unanswered.\n- **Documentation Concerns**: Significant frustration about the quality of documentation, with users noting a disconnect between how ElizaOS is marketed as easy to use versus the actual technical challenges faced.\n\n### Community Contributions\n- **Knowledge Repository**: Jin is developing a knowledge repository and dashboard system that aggregates ecosystem data.\n- **Visualization Improvements**: Discussion about enhancing the visual presentation of update logs and creating a dashboard similar to DeFi Llama for the Eliza ecosystem.\n- **Partner Dashboard**: Consideration of a partner dashboard with different access levels based on partnership status.\n\n### Token Discussion\n- **Eli5 and Eddy Tokens**: Community members discussed these tokens in relation to the v2 release, though specific technical details were not shared.\n- **Price Speculation**: Some users discussed buying and holding these tokens with speculation about future price movements.\n\n## Key Questions & Answers\n\n### Eliza v2 and Partnerships\n- **Q**: What about the LP pool COM/AI16z?  \n  **A**: It's delayed due to logistics issues and should happen within 14 days but likely sooner. (Kenk)\n\n- **Q**: When will the initial funding happen?  \n  **A**: Within 14 days. (Kenk)\n\n- **Q**: So v2 real soon?  \n  **A**: Potentially even this week. Their briefing from May 17th said v2 is imminent. (xell0x)\n\n- **Q**: What's the status of the LP setup for nedos' project?  \n  **A**: It's underway; due to COM price appreciation, they needed to increase collateral on the ai16z side which required an additional step. (Kenk)\n\n### Technical Support\n- **Q**: How to upgrade ElizaOS CLI?  \n  **A**: Try \"elizaos update\" (blueberrywachiwi)\n\n- **Q**: Where do you put the API for SUNO?  \n  **A**: The plugin-suno readme should cover that (blueberrywachiwi)\n\n### Security and Education\n- **Q**: Tell me about common scams  \n  **A**: Here are some common crypto scam patterns to watch for: rug pulls (devs abandon project after pump), honeypots (can't sell tokens), fake airdrops, impersonation scams, and social engineering. Always verify contracts, do thorough research, and never share private keys or seed phrases. (Ruby)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **Character Commands Help**: blueberrywachiwi helped themselves and others by suggesting using \"elizaos start --character=\"/path/to/char.json\"\" and provided example commands to set up a project with character files.\n\n- **Twitter Plugin Issues**: Odilitime suggested using older versions of plugin-twitter and manually logging into Twitter account to address Cloudflare login issues.\n\n### Knowledge Sharing\n- **Ecosystem Data Visualization**: Jin shared screenshots of their current implementation for ecosystem data visualization and asked for community help in improving the visual design.\n\n- **V2 Release Information**: xell0x explained to HodlHusky that v2 is imminent and clarified that users will be able to interact with Eli5 in the v2 agent terminal.\n\n## Action Items\n\n### Technical\n- Fix Cloudflare login issues with Twitter plugin (Mentioned by Bitcoin Broccoli, Sthx, bruce)\n- Fix bootstrap plugin installation errors (Mentioned by blueberrywachiwi)\n- Fix character command functionality (Mentioned by blueberrywachiwi)\n- Implement COM/AI16z liquidity pool within 14 days (Mentioned by Kenk)\n- Improve visual design of update logs from knowledge repository (Mentioned by jin)\n- Create a dashboard similar to llamafeed.io for Eliza ecosystem (Mentioned by jin)\n- Consider integrating knowledge repo into a partners dashboard with tiered access (Mentioned by yikesawjeez)\n\n### Documentation\n- Overhaul documentation for new developers (Mentioned by blueberrywachiwi)\n- Create documentation for character files (Mentioned by blueberrywachiwi)\n- Improve Quickstart guide (Mentioned by blueberrywachiwi)\n- Clarify version differences and stability (Mentioned by blueberrywachiwi, Kodasan-V)\n- Improve transparency in communications about project timelines (Mentioned by Reneil)\n- Provide more information about Eli5 and Eddy as part of v2 (Mentioned by xell0x)\n\n### Feature\n- Launch Eliza v2 (Mentioned by xell0x)\n- Build public online ElizaOS agent creation tool similar to what eliza.gg used to offer (Mentioned by blueberrywachiwi)\n- ElizaOS v2 release with agent terminal functionality (Mentioned by xell0x)\n---\n2025-05-21.json\n---\nelizaOS Development\n---\nelizaOS Development Discord - 2025-05-21\n---\n1320246527268098048\n---\n\ud83d\udcac\uff5cgeneral\n---\n# Analysis of Discord Chat in \ud83d\udcac\uff5cgeneral\n\n## 1. Summary:\nThe chat primarily revolves around challenges with v2 implementation of what appears to be a development framework. A user named \"Hidden Forces\" expressed significant frustration with the v2 version, citing numerous conflicts when following the Quick Start guide. They mentioned that v2-develop branch doesn't load the full installation, and manual installation attempts cause build failures. The user contrasted this with their more positive experience using v1. A team member named \"cjft\" acknowledged these issues, noting that documentation improvements were underway as they prepare for the v2 release at the end of the month. The team has prioritized addressing user complaints. Other topics briefly mentioned included AI agents, Mistral's DevStral announcement, and Xai's new capabilities, though with minimal technical detail.\n\n## 2. FAQ:\nQ: What is context window? (asked by AD) A: Unanswered\nQ: any one can share autodotfun brandkit? (asked by ElizaBAO\ud83c\udf1f) A: Unanswered\n\n## 3. Help Interactions:\nHelper: Agent Joshua \u20b1 | TEE | Helpee: Hidden Forces | Context: Hidden Forces expressed frustration with v2 conflicts | Resolution: Agent Joshua attempted to help by asking for specific conflict details and which branch/tag they were using, but no follow-up resolution was shown\nHelper: cjft | Helpee: Hidden Forces | Context: Hidden Forces struggling with v2 implementation and Quick Start guide issues | Resolution: cjft acknowledged the documentation issues, mentioned they were being addressed as a top priority, and reassured that improvements were coming before the month-end v2 release\n\n## 4. Action Items:\nType: Documentation | Description: Fix Quick Start guide for v2 implementation to address conflicts and installation issues | Mentioned By: Hidden Forces\nType: Technical | Description: Resolve conflicts in v2-develop branch that prevent proper installation | Mentioned By: Hidden Forces\nType: Technical | Description: Fix build issues when manually loading full installation in v2 | Mentioned By: Hidden Forces\n---\n1324089429727514674\n---\n\ud83e\udd16\uff5cagent-dev-school\n---\n# Discord Chat Analysis\n\n## 1. Summary\nThe conversation focuses on Eliza's knowledge system, specifically its chunking configuration for RAG (Retrieval-Augmented Generation). Ruby explains that chunking is handled in the core @elizaos/plugin-rag package with default settings of 1000 tokens maximum size and 200 token overlap. These settings can be overridden in a config.js file using RAG_CHUNK_SIZE and RAG_CHUNK_OVERLAP parameters. The current implementation uses a basic sliding window approach, though smarter semantic chunking that respects markdown structure is in development. Ruby provides examples of optimized knowledge file formatting with metadata tags (#topic, #context, #priority) and section headers to improve chunking effectiveness. She also shares a sample config.js with customized settings for chunkSize (1500), chunkOverlap (300), and similarityThreshold (0.75). Ruby clarifies that the RAG plugin is built into the ElizaOS core and doesn't need to be added separately to the plugin array, unlike the SQL plugin which is separate.\n\n## 2. FAQ\nQ: Where in Eliza's codebase is the chunking configuration defined for knowledge files? (asked by Scooter) A: It's handled in the core @elizaos/plugin-rag package (answered by Ruby)\nQ: What parameters control the maximum chunk size in Eliza's current implementation? (asked by Scooter) A: Default max size is 1000 tokens with 200 token overlap, configurable with RAG_CHUNK_SIZE and RAG_CHUNK_OVERLAP (answered by Ruby)\nQ: Can Eliza's current chunking system be modified to respect markdown headers? (asked by Scooter) A: Not currently, but they're working on smarter semantic chunking that will respect markdown structure (answered by Ruby)\nQ: Would changes to chunking need to happen at the core Eliza level or can they be implemented at the plugin level? (asked by Scooter) A: Unanswered\nQ: Do I need to add the rag package plugin to my character plugin array? (asked by Scooter) A: No, the rag plugin is already part of elizaos core, you just need to create config.js with your settings (answered by Ruby)\n\n## 3. Help Interactions\nHelper: Ruby | Helpee: Scooter | Context: Needed information about Eliza's knowledge chunking system | Resolution: Provided detailed explanation of chunking configuration, parameters, and optimization techniques\nHelper: Ruby | Helpee: Scooter | Context: Requested example knowledge file formatting and configuration | Resolution: Provided optimized knowledge file format with metadata tags and sample config.js with custom settings\nHelper: Ruby | Helpee: Scooter | Context: Confusion about whether RAG plugin needs to be added separately | Resolution: Clarified that RAG plugin is built into core, unlike SQL plugin which is separate\n\n## 4. Action Items\nTechnical: Implement custom chunking configuration in config.js file | Description: Override default RAG settings with larger chunks and more overlap | Mentioned By: Ruby\nDocumentation: Create examples of optimized knowledge file formatting | Description: Show how to use metadata tags and section headers for better chunking | Mentioned By: Ruby\nTechnical: Verify config settings are working | Description: Add console.log to config.js, check logs, and monitor chunking behavior | Mentioned By: Ruby\nFeature: Develop smarter semantic chunking | Description: Improve chunking to respect markdown structure instead of basic sliding window approach | Mentioned By: Ruby\n---\n1323745969115893780\n---\n\ud83d\udce5\uff5cpull-requests\n---\n# Analysis of \"\ud83d\udce5\uff5cpull-requests\" Discord Channel\n\n## 1. Summary:\nThe channel primarily focuses on pull request discussions for the elizaOS/eliza project and related plugins. Key technical discussions include:\n\n1) PR #4686 introduces a unified environment file lookup system with a new `findNearestEnvFile` utility to make CLI behavior more predictable. Ruby suggested adding debug logging for fallback cases and potentially caching lookup results for performance.\n\n2) PR #4687 adds timeout functionality to CLI tests to address flakiness in CI environments, with suggestions to make the timeout configurable via environment variables.\n\n3) A discussion about stacked diffs workflow occurred, highlighting benefits for code review by breaking changes into smaller, focused pieces.\n\n4) PR for plugin-ollama adds automatic model pulling functionality, with discussions about error handling for network conditions and disk space issues during model downloads.\n\n5) PR #4693 removes Opus dependencies that were causing problems, with a note that this represents a breaking change requiring documentation updates.\n\n6) PR #4695 changes the pglite target directory to keep the .pglite file with the project rather than in global space, preventing configuration conflicts.\n\n7) Publishing workflow issues were identified when attempting to publish from a personal fork rather than the official repository, requiring changes to the PR target and token configuration.\n\n## 2. FAQ:\nQ: Is the version bump automatically handled? (asked by sayonara) A: No, doesn't deploy if same version as before (answered by cjft)\nQ: Why not auto-bump versions with every commit? (implied by Ruby) A: Not every commit will auto bump, allows devs to work on branch then make a release when want (answered by cjft)\n\n## 3. Help Interactions:\nHelper: Ruby | Helpee: sayonara | Context: Environment file lookup PR implementation | Resolution: Suggested adding debug logging and caching for performance\nHelper: Ruby | Helpee: sayonara | Context: CLI test timeout implementation | Resolution: Suggested making timeout configurable via environment variables\nHelper: Ruby | Helpee: sayonara | Context: Plugin publishing failure | Resolution: Identified issue with using personal account instead of registry token\nHelper: cjft | Helpee: sayonara | Context: Plugin publishing to correct repository | Resolution: Directed to submit PR to official repo instead of fork\n\n## 4. Action Items:\nType: Technical | Description: Add debug logging when findNearestEnvFile falls back to defaults | Mentioned By: Ruby\nType: Technical | Description: Consider caching env file lookup results for performance | Mentioned By: Ruby\nType: Technical | Description: Make CLI test timeout configurable via environment variable | Mentioned By: Ruby\nType: Technical | Description: Add error handling with retry/backoff for Ollama model pulls | Mentioned By: Ruby\nType: Technical | Description: Add validation to prevent nested .pglite files | Mentioned By: Ruby\nType: Documentation | Description: Update audio docs to note breaking change from removing Opus dependencies | Mentioned By: Ruby\nType: Feature | Description: Implement stacked diffs workflow with supporting tooling | Mentioned By: Ruby\n---\n2025-05-21.md\n---\n# elizaOS Development Discord - 2025-05-21\n\n## Overall Discussion Highlights\n\n### v2 Implementation Challenges\n- **Hidden Forces** expressed significant frustration with v2 implementation, citing numerous conflicts when following the Quick Start guide\n- The v2-develop branch reportedly doesn't load the full installation, and manual installation attempts cause build failures\n- **cjft** acknowledged these documentation issues, noting improvements were underway as they prepare for the v2 release at the end of the month\n\n### Knowledge System & RAG Implementation\n- **Ruby** explained Eliza's chunking configuration for RAG is handled in the core `@elizaos/plugin-rag` package\n- Default settings: 1000 tokens maximum chunk size with 200 token overlap\n- Settings can be overridden in `config.js` using `RAG_CHUNK_SIZE` and `RAG_CHUNK_OVERLAP` parameters\n- Current implementation uses a basic sliding window approach, with smarter semantic chunking in development\n- Knowledge files can be optimized with metadata tags (#topic, #context, #priority) and section headers\n\n### Pull Request Discussions\n- **PR #4686**: Introduces unified environment file lookup system with `findNearestEnvFile` utility\n- **PR #4687**: Adds timeout functionality to CLI tests to address flakiness in CI environments\n- **PR for plugin-ollama**: Adds automatic model pulling functionality\n- **PR #4693**: Removes Opus dependencies (breaking change)\n- **PR #4695**: Changes pglite target directory to keep .pglite file with the project rather than in global space\n- Discussion about stacked diffs workflow benefits for code review by breaking changes into smaller pieces\n\n### Publishing & Deployment\n- Issues identified when attempting to publish from a personal fork rather than the official repository\n- Version bumping is not automatic for every commit, allowing developers to work on branches and make releases when ready\n\n## Key Questions & Answers\n\n**Q: Where in Eliza's codebase is the chunking configuration defined for knowledge files?**  \nA: It's handled in the core @elizaos/plugin-rag package (answered by Ruby)\n\n**Q: What parameters control the maximum chunk size in Eliza's current implementation?**  \nA: Default max size is 1000 tokens with 200 token overlap, configurable with RAG_CHUNK_SIZE and RAG_CHUNK_OVERLAP (answered by Ruby)\n\n**Q: Can Eliza's current chunking system be modified to respect markdown headers?**  \nA: Not currently, but they're working on smarter semantic chunking that will respect markdown structure (answered by Ruby)\n\n**Q: Do I need to add the rag package plugin to my character plugin array?**  \nA: No, the rag plugin is already part of elizaOS core, you just need to create config.js with your settings (answered by Ruby)\n\n**Q: Is the version bump automatically handled?**  \nA: No, it doesn't deploy if the version is the same as before (answered by cjft)\n\n**Q: Why not auto-bump versions with every commit?**  \nA: Not every commit will auto bump, allowing developers to work on branches and make releases when desired (answered by cjft)\n\n## Community Help & Collaboration\n\n### v2 Implementation Support\n- **Agent Joshua** attempted to help **Hidden Forces** by asking for specific conflict details and which branch/tag they were using\n- **cjft** reassured **Hidden Forces** that documentation issues were being addressed as a top priority with improvements coming before the month-end v2 release\n\n### RAG Configuration Guidance\n- **Ruby** provided **Scooter** with detailed explanation of chunking configuration, parameters, and optimization techniques\n- **Ruby** shared examples of optimized knowledge file formatting with metadata tags and a sample config.js with custom settings\n- **Ruby** clarified that the RAG plugin is built into the core, unlike the SQL plugin which is separate\n\n### Pull Request Collaboration\n- **Ruby** suggested improvements to **sayonara's** PRs, including adding debug logging for fallback cases and making timeouts configurable\n- **Ruby** helped identify publishing workflow issues when attempting to publish from a personal fork\n- **cjft** directed **sayonara** to submit PRs to the official repo instead of a fork\n\n## Action Items\n\n### Technical\n- Fix conflicts in v2-develop branch that prevent proper installation (Mentioned by Hidden Forces)\n- Fix build issues when manually loading full installation in v2 (Mentioned by Hidden Forces)\n- Add debug logging when findNearestEnvFile falls back to defaults (Mentioned by Ruby)\n- Consider caching env file lookup results for performance (Mentioned by Ruby)\n- Make CLI test timeout configurable via environment variable (Mentioned by Ruby)\n- Add error handling with retry/backoff for Ollama model pulls (Mentioned by Ruby)\n- Add validation to prevent nested .pglite files (Mentioned by Ruby)\n- Implement custom chunking configuration in config.js file (Mentioned by Ruby)\n- Verify config settings are working with console.log and monitoring (Mentioned by Ruby)\n\n### Documentation\n- Fix Quick Start guide for v2 implementation to address conflicts and installation issues (Mentioned by Hidden Forces)\n- Update audio docs to note breaking change from removing Opus dependencies (Mentioned by Ruby)\n- Create examples of optimized knowledge file formatting with metadata tags and section headers (Mentioned by Ruby)\n\n### Feature\n- Implement stacked diffs workflow with supporting tooling (Mentioned by Ruby)\n- Develop smarter semantic chunking to respect markdown structure (Mentioned by Ruby)\n---\n2025-05-21.json\n---\nFile not found\n---\n2025-05-21.md\n---\nFile not found\n---\n2025-05-22.md\n---\nFile not found\n---\n2025-05-18.md\n---\n# ElizaOS Weekly Update (May 18 - 24, 2025)\n\n## OVERVIEW\nThis week saw significant progress in ElizaOS's development with a focus on API enhancements, plugin infrastructure improvements, and system reliability. The team added several new API endpoints for world and room management, improved CLI testing capabilities, and fixed numerous bugs related to environment handling and plugin operations. Several plugins were also moved to dedicated repositories as part of the ongoing modularization effort.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### API Enhancements and World Management\n- Added new API endpoints for creating and managing worlds [#4667](https://github.com/elizaos/eliza/pull/4667)\n- Implemented API endpoints for creating new rooms [#4647](https://github.com/elizaos/eliza/pull/4647)\n- Added API endpoint to retrieve rooms per agent [#4677](https://github.com/elizaos/eliza/pull/4677)\n- Enhanced message API to allow world selection [#4637](https://github.com/elizaos/eliza/pull/4637)\n- Added chat clear and delete message features [#4659](https://github.com/elizaos/eliza/pull/4659)\n- Improved API to return agent ID on creation [#4634](https://github.com/elizaos/eliza/pull/4634)\n\n### Plugin System Improvements\n- Added registry support for plugins [#4641](https://github.com/elizaos/eliza/pull/4641)\n- Implemented timeout for registry parsing [#4678](https://github.com/elizaos/eliza/pull/4678)\n- Added missing plugin failure test [#4643](https://github.com/elizaos/eliza/pull/4643)\n- Enhanced plugin loading with cleaner logging [#4684](https://github.com/elizaos/eliza/pull/4684)\n- Fixed plugin-tee build and exports [#4675](https://github.com/elizaos/eliza/pull/4675)\n- Added channel ID environment variables to Discord plugin [#4665](https://github.com/elizaos/eliza/pull/4665)\n\n### CLI and Testing Improvements\n- Unified environment file lookup across CLI [#4686](https://github.com/elizaos/eliza/pull/4686)\n- Added timeout to CLI tests [#4687](https://github.com/elizaos/eliza/pull/4687)\n- Fixed bats test flakiness [#4663](https://github.com/elizaos/eliza/pull/4663)\n- Improved CLI test command [#4688](https://github.com/elizaos/eliza/pull/4688)\n- Enhanced PGLite usage in target directory [#4695](https://github.com/elizaos/eliza/pull/4695)\n- Restored local AI testing [#4676](https://github.com/elizaos/eliza/pull/4676)\n\n### System Reliability and Monitoring\n- Added Sentry logging to core logger errors [#4650](https://github.com/elizaos/eliza/pull/4650)\n- Reduced web server logging for better performance [#4685](https://github.com/elizaos/eliza/pull/4685)\n- Fixed agent start button to properly refetch agent status [#4642](https://github.com/elizaos/eliza/pull/4642)\n- Fixed reply action to properly handle dynamic providers [#4651](https://github.com/elizaos/eliza/pull/4651)\n- Improved error handling for transcription parameters [#4679](https://github.com/elizaos/eliza/pull/4679)\n\n## CLOSED ISSUES\n\n### Documentation and User Experience\n- Resolved broken links in documentation [#4260](https://github.com/elizaos/eliza/issues/4260), [#4285](https://github.com/elizaos/eliza/issues/4285)\n- Fixed confusion between contributing to ElizaOS vs using the framework [#4285](https://github.com/elizaos/eliza/issues/4285)\n- Addressed leaderboard username update issue [#4632](https://github.com/elizaos/eliza/issues/4632)\n\n### Technical Debt and Dependencies\n- Resolved npm publishing issue for dependency management [#4562](https://github.com/elizaos/eliza/issues/4562)\n- Fixed environment variable handling for logging [#4282](https://github.com/elizaos/eliza/issues/4282)\n- Addressed agent hanging issue with specific configurations [#4486](https://github.com/elizaos/eliza/issues/4486)\n- Implemented platform interface for core package [#3491](https://github.com/elizaos/eliza/issues/3491)\n\n## NEW ISSUES\n\n### Database Management\n- Need to switch agent from SQLite to PostgreSQL [#4697](https://github.com/elizaos/eliza/issues/4697)\n---\n2025-05-01.md\n---\n# ElizaOS Monthly Update (May 2025)\n\n## OVERVIEW\nMay was a transformative month for ElizaOS, with significant advancements in the framework's modularity and extensibility. The team focused on enhancing the CLI experience, improving plugin management, and strengthening core infrastructure. Major achievements include the introduction of third-party plugin support, comprehensive API enhancements for agent management, and significant improvements to database operations and environment configuration.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### CLI Experience Enhancements\n- Improved command structure and options parsing for better usability across all CLI commands ([#4560](https://github.com/elizaos/eliza/pull/4560), [#4583](https://github.com/elizaos/eliza/pull/4583))\n- Consolidated update functionality into a single command for more intuitive user experience ([#4592](https://github.com/elizaos/eliza/pull/4592))\n- Added comprehensive tests for CLI commands to ensure reliability ([#4582](https://github.com/elizaos/eliza/pull/4582), [#4687](https://github.com/elizaos/eliza/pull/4687))\n- Enhanced environment file handling with unified lookup across CLI ([#4686](https://github.com/elizaos/eliza/pull/4686))\n\n### Plugin System Improvements\n- Added support for third-party plugin installation with improved Git repository support ([#4568](https://github.com/elizaos/eliza/pull/4568), [#4577](https://github.com/elizaos/eliza/pull/4577))\n- Integrated plugin specification submodule for better standardization ([#4553](https://github.com/elizaos/eliza/pull/4553))\n- Prepared 0.x plugins for sharing with 1.x version ([#4384](https://github.com/elizaos/eliza/pull/4384))\n- Improved plugin loading with cleaner logging and better error handling ([#4684](https://github.com/elizaos/eliza/pull/4684), [#4478](https://github.com/elizaos/eliza/pull/4478))\n\n### API and Authentication Enhancements\n- Added authentication middleware and API key dialog for unauthorized requests ([#4420](https://github.com/elizaos/eliza/pull/4420))\n- Implemented new API endpoints for room and world management ([#4647](https://github.com/elizaos/eliza/pull/4647), [#4677](https://github.com/elizaos/eliza/pull/4677), [#4667](https://github.com/elizaos/eliza/pull/4667))\n- Enhanced agent data fetching for improved performance with many agents ([#4519](https://github.com/elizaos/eliza/pull/4519))\n- Added support for world selection in message API ([#4637](https://github.com/elizaos/eliza/pull/4637))\n\n### Database and Storage Improvements\n- Implemented unique PGLite folder creation for better project isolation ([#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 issues when deleting agents ([#4510](https://github.com/elizaos/eliza/pull/4510))\n- Improved database migration handling ([#4532](https://github.com/elizaos/eliza/pull/4532), [#4531](https://github.com/elizaos/eliza/pull/4531))\n\n### Model and AI Provider Enhancements\n- Extended OpenAI plugin to support custom embedding endpoints ([#4421](https://github.com/elizaos/eliza/pull/4421))\n- Added model usage events for embeddings and image description ([#4438](https://github.com/elizaos/eliza/pull/4438))\n- Optimized model selection for replies to use small models for better performance ([#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 Integration Features\n- Added Twitter timeline functionality for bot interactions ([#4429](https://github.com/elizaos/eliza/pull/4429))\n- Fixed Twitter plugin issues and improved error handling ([#4506](https://github.com/elizaos/eliza/pull/4506))\n- Added comprehensive blog for Twitter agent setup ([#4425](https://github.com/elizaos/eliza/pull/4425))\n- Enhanced Discord plugin with channel ID filtering ([#4665](https://github.com/elizaos/eliza/pull/4665))\n\n### Chat and Message Handling\n- Added chat clear and delete message features ([#4659](https://github.com/elizaos/eliza/pull/4659), [#4689](https://github.com/elizaos/eliza/pull/4689))\n- Improved message handling with better error checking ([#4508](https://github.com/elizaos/eliza/pull/4508))\n- Enhanced LLM response parsing to support custom fields ([#4580](https://github.com/elizaos/eliza/pull/4580))\n- Fixed JSON parsing issues with nested objects ([#4198](https://github.com/elizaos/eliza/pull/4198))\n\n### Documentation and Developer Experience\n- Added comprehensive docstrings to various 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 CLI command documentation for better clarity ([#4448](https://github.com/elizaos/eliza/pull/4448))\n- Fixed broken links and typos in documentation ([#4555](https://github.com/elizaos/eliza/pull/4555), [#4563](https://github.com/elizaos/eliza/pull/4563))\n- Added Sentry logging integration for better error tracking ([#4650](https://github.com/elizaos/eliza/pull/4650))\n\n## CLOSED ISSUES\n\n### CLI and Installation Issues\n- Fixed issues with CLI version detection and update mechanism ([#4285](https://github.com/elizaos/eliza/issues/4285), [#4107](https://github.com/elizaos/eliza/issues/4107))\n- Resolved Windows compatibility problems with build process ([#4094](https://github.com/elizaos/eliza/issues/4094))\n- Improved CLI tool instructions and documentation ([#4113](https://github.com/elizaos/eliza/issues/4113), [#4143](https://github.com/elizaos/eliza/issues/4143))\n- Addressed issues with running the CLI interface ([#4159](https://github.com/elizaos/eliza/issues/4159))\n\n### Plugin Compatibility and Documentation\n- Clarified which plugins are compatible with Eliza v2 ([#4164](https://github.com/elizaos/eliza/issues/4164))\n- Fixed issues with Twitter plugin functionality ([#4180](https://github.com/elizaos/eliza/issues/4180), [#4181](https://github.com/elizaos/eliza/issues/4181))\n- Addressed problems with media generation in Twitter ([#4241](https://github.com/elizaos/eliza/issues/4241))\n- Fixed provider data usage with Twitter posts ([#4224](https://github.com/elizaos/eliza/issues/4224))\n\n### Documentation and Community Resources\n- Updated community section in documentation ([#4260](https://github.com/elizaos/eliza/issues/4260))\n- Fixed broken tutorial links and content ([#3880](https://github.com/elizaos/eliza/issues/3880))\n- Clarified contribution guidelines for framework users versus core contributors ([#4282](https://github.com/eliza\n---\n{\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 269 new PRs (204 merged), 16 new issues, and 68 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_kwDOMT5cIs6W-XKp\",\n      \"title\": \"Permashill impl plan v1\",\n      \"author\": \"jkbrooks\",\n      \"number\": 4683,\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review and merge. -->\\r\\n\\r\\n# Risks\\r\\n\\r\\n<!--\\r\\nLow, medium, large. List what kind of risks and what could be affected.\\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\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes to existing features)\\r\\nFeatures (non-breaking change which adds functionality)\\r\\nUpdates (new versions of included code)\\r\\n-->\\r\\n\\r\\n<!-- This \\\"Why\\\" section is most relevant if there are no linked issues explaining why. If there is a related issue, it might make sense to skip this why section. -->\\r\\n<!--\\r\\n## Why are we doing this? Any context or related work?\\r\\n-->\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n<!--\\r\\nMy changes do not require a change to the project documentation.\\r\\nMy changes require a change to the project documentation.\\r\\nIf documentation change is needed: I have updated the documentation accordingly.\\r\\n-->\\r\\n\\r\\n<!-- Please show how you tested the PR. This will really help if the PR needs to be retested and probably help the PR get merged quicker. -->\\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\\nNone: Automated tests are acceptable.\\r\\n-->\\r\\n\\r\\n<!--\\r\\n- As [anon/admin], go to [link]\\r\\n\u00a0 - [do action]\\r\\n\u00a0 - verify [result]\\r\\n-->\\r\\n\\r\\n<!-- If there is a UI change, please include before and after screenshots or videos. This will speed up PRs being merged. It is extra nice to annotate screenshots with arrows or boxes pointing out the differences. -->\\r\\n<!--\\r\\n## Screenshots\\r\\n### Before\\r\\n### After\\r\\n-->\\r\\n\\r\\n<!-- If there is anything about the deployment, please make a note. -->\\r\\n<!--\\r\\n# Deploy Notes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Copy and paste command line output. -->\\r\\n<!--\\r\\n## Database changes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Please specify deploy instructions if there is something more than the automated steps. -->\\r\\n<!--\\r\\n## Deployment instructions\\r\\n-->\\r\\n\\r\\n<!-- If you are on Discord, please join https://discord.gg/elizaOS and state your Discord username here for the contributor role and join us in #development-feed -->\\r\\n<!--\\r\\n## Discord username\\r\\n\\r\\n-->\\r\\n\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-05-21T01:03:32Z\",\n      \"mergedAt\": null,\n      \"additions\": 357476,\n      \"deletions\": 183847\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6VF93K\",\n      \"title\": \"Feat/jimmy project manager\",\n      \"author\": \"samarth30\",\n      \"number\": 4462,\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review and merge. -->\\r\\n\\r\\n# Risks\\r\\n\\r\\n<!--\\r\\nLow, medium, large. List what kind of risks and what could be affected.\\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\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes to existing features)\\r\\nFeatures (non-breaking change which adds functionality)\\r\\nUpdates (new versions of included code)\\r\\n-->\\r\\n\\r\\n<!-- This \\\"Why\\\" section is most relevant if there are no linked issues explaining why. If there is a related issue, it might make sense to skip this why section. -->\\r\\n<!--\\r\\n## Why are we doing this? Any context or related work?\\r\\n-->\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n<!--\\r\\nMy changes do not require a change to the project documentation.\\r\\nMy changes require a change to the project documentation.\\r\\nIf documentation change is needed: I have updated the documentation accordingly.\\r\\n-->\\r\\n\\r\\n<!-- Please show how you tested the PR. This will really help if the PR needs to be retested and probably help the PR get merged quicker. -->\\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\\nNone: Automated tests are acceptable.\\r\\n-->\\r\\n\\r\\n<!--\\r\\n- As [anon/admin], go to [link]\\r\\n\u00a0 - [do action]\\r\\n\u00a0 - verify [result]\\r\\n-->\\r\\n\\r\\n<!-- If there is a UI change, please include before and after screenshots or videos. This will speed up PRs being merged. It is extra nice to annotate screenshots with arrows or boxes pointing out the differences. -->\\r\\n<!--\\r\\n## Screenshots\\r\\n### Before\\r\\n### After\\r\\n-->\\r\\n\\r\\n<!-- If there is anything about the deployment, please make a note. -->\\r\\n<!--\\r\\n# Deploy Notes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Copy and paste command line output. -->\\r\\n<!--\\r\\n## Database changes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Please specify deploy instructions if there is something more than the automated steps. -->\\r\\n<!--\\r\\n## Deployment instructions\\r\\n-->\\r\\n\\r\\n<!-- If you are on Discord, please join https://discord.gg/elizaOS and state your Discord username here for the contributor role and join us in #development-feed -->\\r\\n<!--\\r\\n## Discord username\\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\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review and merge. -->\\r\\n\\r\\n# Risks\\r\\n\\r\\n<!--\\r\\nLow, medium, large. List what kind of risks and what could be affected.\\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\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes to existing features)\\r\\nFeatures (non-breaking change which adds functionality)\\r\\nUpdates (new versions of included code)\\r\\n-->\\r\\n\\r\\n<!-- This \\\"Why\\\" section is most relevant if there are no linked issues explaining why. If there is a related issue, it might make sense to skip this why section. -->\\r\\n<!--\\r\\n## Why are we doing this? Any context or related work?\\r\\n-->\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n<!--\\r\\nMy changes do not require a change to the project documentation.\\r\\nMy changes require a change to the project documentation.\\r\\nIf documentation change is needed: I have updated the documentation accordingly.\\r\\n-->\\r\\n\\r\\n<!-- Please show how you tested the PR. This will really help if the PR needs to be retested and probably help the PR get merged quicker. -->\\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\\nNone: Automated tests are acceptable.\\r\\n-->\\r\\n\\r\\n<!--\\r\\n- As [anon/admin], go to [link]\\r\\n\u00a0 - [do action]\\r\\n\u00a0 - verify [result]\\r\\n-->\\r\\n\\r\\n<!-- If there is a UI change, please include before and after screenshots or videos. This will speed up PRs being merged. It is extra nice to annotate screenshots with arrows or boxes pointing out the differences. -->\\r\\n<!--\\r\\n## Screenshots\\r\\n### Before\\r\\n### After\\r\\n-->\\r\\n\\r\\n<!-- If there is anything about the deployment, please make a note. -->\\r\\n<!--\\r\\n# Deploy Notes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Copy and paste command line output. -->\\r\\n<!--\\r\\n## Database changes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Please specify deploy instructions if there is something more than the automated steps. -->\\r\\n<!--\\r\\n## Deployment instructions\\r\\n-->\\r\\n\\r\\n<!-- If you are on Discord, please join https://discord.gg/elizaOS and state your Discord username here for the contributor role and join us in #development-feed -->\\r\\n<!--\\r\\n## Discord username\\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  \"codeChanges\": {\n    \"additions\": 103284,\n    \"deletions\": 79518,\n    \"files\": 974,\n    \"commitCount\": 1082\n  },\n  \"completedItems\": [\n    {\n      \"title\": \"Semantic splitText\",\n      \"prNumber\": 4235,\n      \"type\": \"other\",\n      \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nImproving\u00a0RAG knowledge retrieval quality\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Changes\u00a0how text is chunked for\u00a0embeddings but maintains size constraints with\u00a0small 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\u2019ve 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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"\ud83d\udc49 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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"\ud83d\udcdd 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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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/ \u2014 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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\nJimmy the project manager\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled o\"\n    },\n    {\n      \"title\": \"Fix typos and improve dependencies management\",\n      \"prNumber\": 4470,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR includes several fixes and improvements:\\r\\n\\r\\n- Fix typo in \\\"safety\\\" word in changelog entries\\r\\n- Fix spelling of \\\"dependencies\\\" word\\r\\n- Fix \\\"Skipping\\\" word spelling\\r\\n- Remove duplicate changelog entries\\r\\n\\r\\nThe changes ensure consiste\"\n    },\n    {\n      \"title\": \"\ud83d\udcdd Add docstrings to `monorepo-resolve`\",\n      \"prNumber\": 4469,\n      \"type\": \"feature\",\n      \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4468#issuecomment-2857150910\\n\\nThe following files were modified:\\n\\n* `packages/cli/src/commands/dev.ts`\\n* `packages/cli/src/utils/build-project.ts`\\n\\n<d\"\n    },\n    {\n      \"title\": \"chore: use existing utils for monorepo resolution\",\n      \"prNumber\": 4468,\n      \"type\": \"other\",\n      \"body\": \"\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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:    \u00d7 deleteAgent > should delete an agent and all related data 5ms\\r\\n@elizaos/plugin-sql:test:      \u2192 tx.select(...).from(...).where(...).limit is not a function\\r\\n``\"\n    },\n    {\n      \"title\": \"\ud83d\udcdd 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<details>\\n<summary>\u2139\ufe0f Note</summary><blockqu\"\n    },\n    {\n      \"title\": \"chore: fix pglite dir\",\n      \"prNumber\": 4497,\n      \"type\": \"bugfix\",\n      \"body\": \"\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"\ud83d\udcdd 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<details>\\n<summary>\u2139\ufe0f Note</summary><blockq\"\n    },\n    {\n      \"title\": \"docs: update docs to prefer direct usage instead of npx\",\n      \"prNumber\": 4493,\n      \"type\": \"docs\",\n      \"body\": \"@coderabbitai review\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\n    },\n    {\n      \"title\": \"Update README.md\",\n      \"prNumber\": 4483,\n      \"type\": \"other\",\n      \"body\": \"for test\\r\\n\\r\\n<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the f\"\n    },\n    {\n      \"title\": \"chore: remove plugin-solana from monorepo\",\n      \"prNumber\": 4513,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: remove plugin-openai from monorepo\",\n      \"prNumber\": 4511,\n      \"type\": \"other\",\n      \"body\": \"\\r\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n  - Improved reliability of CLI test workflow by clearing cached data before running tests.\\n\\n<!-- end of auto-generated com\"\n    },\n    {\n      \"title\": \"chore: use right and latest bun versions\",\n      \"prNumber\": 4522,\n      \"type\": \"tests\",\n      \"body\": \"\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"\ud83d\udcdd 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\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\n    },\n    {\n      \"title\": \"feat: faster agent load when many agents\",\n      \"prNumber\": 4519,\n      \"type\": \"feature\",\n      \"body\": \"Fixes issue with agents api being slow when multiple agents!\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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 \u2014 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\": \"Fix broken Quickstart link\",\n      \"prNumber\": 4555,\n      \"type\": \"bugfix\",\n      \"body\": \"Replaces outdated URL (elizaos.github.io/eliza/quickstart) with working https://eliza.how/docs/quickstart in README.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\"\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\": \"<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"Update README_IND.md\",\n      \"prNumber\": 4542,\n      \"type\": \"other\",\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\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\u2026\",\n      \"prNumber\": 4537,\n      \"type\": \"bugfix\",\n      \"body\": \"\u2026 loaded, it was caused to openai plugin not having an export for getProviderBaseURL\\r\\n\\r\\n<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#4336 \\r\\n\\r\\n<!-- \"\n    },\n    {\n      \"title\": \"Issue 451\",\n      \"prNumber\": 4575,\n      \"type\": \"other\",\n      \"body\": \"# Ticket: Implement Core EVM RPC Wrappers & Basic Reads (Polygon Plugin)\\r\\n\\r\\n**Ticket Type:** Dev Ticket  \\r\\n**Priority:** P1  \\r\\n**Epic:** Implement Polygon Plugin MVP  \\r\\n**Assignee:** Harsh Modi  \\r\\n**Reporter:** AI Assistant  \\r\\n**Dependencie\"\n    },\n    {\n      \"title\": \"Implement Polygon Gas Oracle Integration\",\n      \"prNumber\": 4574,\n      \"type\": \"other\",\n      \"body\": \"\\r\\n# Relates to\\r\\n\\r\\n[Implement Polygon Gas Oracle Integration (Polygon Plugin) #452](https://github.com/Sifchain/sa-eliza/issues/452)\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**\\r\\n\\r\\n*   **External API Dependency:** The primary gas estimation relies on the Polygon\"\n    },\n    {\n      \"title\": \"fix: TEE update for CI\",\n      \"prNumber\": 4572,\n      \"type\": \"bugfix\",\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\n    },\n    {\n      \"title\": \"fix: add commit sha to CLI cache action\",\n      \"prNumber\": 4571,\n      \"type\": \"feature\",\n      \"body\": \"Attempt to fix PRs in CLI tests randomly failing but passing on local and for pushes.\\r\\n\\r\\nAdds SHA hash from github commit to bust cache better.\"\n    },\n    {\n      \"title\": \"fix: update telegram messageManager tests to expect MarkdownV2\",\n      \"prNumber\": 4570,\n      \"type\": \"bugfix\",\n      \"body\": \"\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- end of auto-generat\"\n    },\n    {\n      \"title\": \"feat: support third-party plugin install + added test\",\n      \"prNumber\": 4568,\n      \"type\": \"feature\",\n      \"body\": \"1. refactored plugin install code\\r\\n2. added support for third party plugin installs\\r\\n3. added tests for it\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n  - Added s\"\n    },\n    {\n      \"title\": \"Add README_MY.md \",\n      \"prNumber\": 4567,\n      \"type\": \"feature\",\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\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\": \"docs: Fix typos in faq-and-support.md\",\n      \"prNumber\": 4563,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixes typos in `faq-and-support.md`:\\r\\n\\r\\n- Corrected spelling of \\\"AIndreeson\\\" \u2192 \\\"AIndreessen\\\".\\r\\n- Fixed typo \\\"Tading\\\" \u2192 \\\"Trading\\\".\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n- Bug fixes (non-breaking change which fixes an issue)\\r\\n\\r\\n# Documentatio\"\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"Fix outdated link in changelog.md\",\n      \"prNumber\": 4576,\n      \"type\": \"bugfix\",\n      \"body\": \"The old link led to a 404 error (page not found).\\r\\nTo avoid confusion and broken navigation for readers, the link has been temporarily cleared.\\r\\n\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"chore: remove log spam during client build\",\n      \"prNumber\": 4584,\n      \"type\": \"other\",\n      \"body\": \"\\r\\n<img width=\\\"935\\\" alt=\\\"Screenshot 2025-05-14 at 11 18 50\u202fPM\\\" src=\\\"https://github.com/user-attachments/assets/210abe07-1e7c-4e4a-8d16-3ed525737b02\\\" />\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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(core): fixing failling tests, adding missing packages and fixing circular dependency \",\n      \"prNumber\": 4605,\n      \"type\": \"bugfix\",\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\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<img width=\\\"844\\\" alt=\\\"image\\\" src=\\\"https://github.com/user-attachments/assets/21d34d4d-c76d-4a1a-bebb-7\"\n    },\n    {\n      \"title\": \"fix: additional fix for topics project starter & def character\",\n      \"prNumber\": 4602,\n      \"type\": \"bugfix\",\n      \"body\": \"- additional fix for default character used for quick start \\r\\n- fix for character used in project starter\"\n    },\n    {\n      \"title\": \"chore: fix client chat ignore\",\n      \"prNumber\": 4600,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: core not importable in client / vite polyfills.\",\n      \"prNumber\": 4599,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixes client error:\\r\\n\\r\\nUncaught TypeError: Failed to resolve module specifier \\\"@elizaos/core\\\". Relative references must start with either \\\"/\\\", \\\"./\\\", or \\\"../\\\".\\r\\nAlso adds vite-node-polyfills to supplement Buffer and process missing.\"\n    },\n    {\n      \"title\": \"docs: fix broken link to ELIZA demo (ai16z \u2192 elizaos)\",\n      \"prNumber\": 4597,\n      \"type\": \"bugfix\",\n      \"body\": \"Hey team\u2014noticed a dead link, replaced it with a working URL. Thanks!\\r\\n\\r\\nhttps://ai16z.github.io/eliza/ -- old link\\r\\nhttps://elizaos.github.io/eliza/ -- new link\"\n    },\n    {\n      \"title\": \"fix: add missing topics as X post templates expects topics\",\n      \"prNumber\": 4595,\n      \"type\": \"feature\",\n      \"body\": \"\\r\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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- \u274c `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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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: fix some typos in comment\",\n      \"prNumber\": 4615,\n      \"type\": \"bugfix\",\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\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\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\n    },\n    {\n      \"title\": \"Added : Polygon Plugin \",\n      \"prNumber\": 4635,\n      \"type\": \"other\",\n      \"body\": \"# Relates to\\r\\n\\r\\nIssue:\\r\\n- [#450 Initialize Eliza Plugin Structure and Configuration (Polygon)](https://github.com/Sifchain/sa-eliza/issues/450)\\r\\n- [#453 Implement Staking Read Operations (Polygon Plugin)](https://github.com/Sifchain/sa-eliz\"\n    },\n    {\n      \"title\": \"chore(deps): bump the pip group across 1 directory with 3 updates\",\n      \"prNumber\": 4649,\n      \"type\": \"other\",\n      \"body\": \"Bumps the pip group with 3 updates in the /scripts/bug_hunt directory: [cryptography](https://github.com/pyca/cryptography), [h11](https://github.com/python-hyper/h11) and [setuptools](https://github.com/pypa/setuptools).\\n\\nUpdates `cryptogr\"\n    },\n    {\n      \"title\": \"[SpartanDev] Update elizaos\",\n      \"prNumber\": 4648,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: API endpoint for creating new rooms\",\n      \"prNumber\": 4647,\n      \"type\": \"feature\",\n      \"body\": \"Currently we dont have API endpoint to create new rooms, so I added this feature in PR. \\r\\n\\r\\nDid some tests, rooms are created and IDs returned. Adding screenshots from tests\\r\\n\\r\\n<img width=\\\"845\\\" alt=\\\"image\\\" src=\\\"https://github.com/user-attac\"\n    },\n    {\n      \"title\": \"Eliza290/update docs readme and tests for all cli commands\",\n      \"prNumber\": 4646,\n      \"type\": \"tests\",\n      \"body\": \"this is a complimentary PR to update docs, readme, and tests for all the changes related to ELIZA290, cli testing + polish.\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"feat: API get rooms per agent\",\n      \"prNumber\": 4677,\n      \"type\": \"feature\",\n      \"body\": \"I wanted to get all the rooms where each agent is present, so to retrive that I added API endpoint which calls the function \\r\\n\\\"getRoomsForParticipant\\\" and retrives this to endpoint\\r\\n\\r\\n`curl -X GET http://localhost:3000/api/agents/b850bc30-4\"\n    },\n    {\n      \"title\": \"bring back local ai test\",\n      \"prNumber\": 4676,\n      \"type\": \"tests\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: plugin-tee build and exports\",\n      \"prNumber\": 4675,\n      \"type\": \"bugfix\",\n      \"body\": \"\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\n## Summary by CodeRabbit\\n\\n- **Bug Fixes**\\n  - Improved error handling to prevent runtime errors when message content is missing or incomplete.\\n  - Enhanced error l\"\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<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\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\": \"remove discord plugin\",\n      \"prNumber\": 4668,\n      \"type\": \"other\",\n      \"body\": \"has been moved out to: https://github.com/elizaos-plugins/plugin-discord\"\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\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review \"\n    },\n    {\n      \"title\": \"Fix bats test flakiness\",\n      \"prNumber\": 4663,\n      \"type\": \"bugfix\",\n      \"body\": \"## Summary\\n- guard port cleanup in bats tests\\n- improve timing in dev-command tests\\n- use `seq` for loops for broader shell compatibility\\n\\n## Testing\\n- `./run_all_bats.sh` *(fails: 'bats' not found)*\"\n    },\n    {\n      \"title\": \"fixed agent tests\",\n      \"prNumber\": 4661,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"cleaner readable test files\",\n      \"prNumber\": 4660,\n      \"type\": \"refactor\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"Add chat clear and delete message features\",\n      \"prNumber\": 4659,\n      \"type\": \"feature\",\n      \"body\": \"## Summary\\n- add routes in the CLI test server for deleting individual/group memories\\n- expose client API helpers for deleting and clearing group messages\\n- support group memory deletion in query hooks\\n- add clear chat button and delete mes\"\n    },\n    {\n      \"title\": \"attempt: change pglite default dir\",\n      \"prNumber\": 4656,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"default sentry better\",\n      \"prNumber\": 4655,\n      \"type\": \"other\",\n      \"body\": \"Since requires new ENV added, usually would always be not true, this turns off sentry only if user sets false. Even if env not added.\"\n    },\n    {\n      \"title\": \"fix sharp install in CI, integration tests failing\",\n      \"prNumber\": 4654,\n      \"type\": \"bugfix\",\n      \"body\": \"Add libvips-dev install to linux in CI, to fix error in integration tests:\\n\\n```\\ngyp info spawn make\\ngyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]\\n../src/common.cc:13:10: fatal error: vips/vips8: No such file or directory\\n13 | #\"\n    },\n    {\n      \"title\": \"generalized eliza agent character\",\n      \"prNumber\": 4653,\n      \"type\": \"other\",\n      \"body\": \"Reduces lock in on default eliza character, removes IGNORES from message examples, goal is should be a good 1 on 1 chat that always responds for first time users.\"\n    },\n    {\n      \"title\": \"flyio docker deploy action for dev agent\",\n      \"prNumber\": 4652,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: reply action skipping dynamic providers\",\n      \"prNumber\": 4651,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR removes the skipping logic in the reply action. Previously, if a dynamic provider was added, it wouldn't be processed because the reply action would skip it.\\r\\n\\r\\nI think we might still need that shortcut if there's no dynamic provide\"\n    },\n    {\n      \"title\": \"Add sentry logging to core logger errors.\",\n      \"prNumber\": 4650,\n      \"type\": \"feature\",\n      \"body\": \"![image](https://github.com/user-attachments/assets/036e4f1c-bc4b-4271-a9fc-d707f1ce6ecf)\\r\\n\\r\\nInitial Sentry hookup into core logger errors.\\r\\n\\r\\nHas envs for custom Sentry setups, but defaults to ours.\"\n    },\n    {\n      \"title\": \"fix: use pglite in target dir with create command or inline env\",\n      \"prNumber\": 4695,\n      \"type\": \"bugfix\",\n      \"body\": \"\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n  - Environment and database configuration files are now stored within the project directory, ensuring localized setup fo\"\n    },\n    {\n      \"title\": \"fix: make registry parsing direct executable + exportable\",\n      \"prNumber\": 4694,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"deps: remove discord opus deps\",\n      \"prNumber\": 4693,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: focused CLI testing\",\n      \"prNumber\": 4692,\n      \"type\": \"tests\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: Revert to using GH_PAT\",\n      \"prNumber\": 4691,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: make autodoc run on v2-develop\",\n      \"prNumber\": 4690,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat(client): move delete message button\",\n      \"prNumber\": 4689,\n      \"type\": \"feature\",\n      \"body\": \"## Summary\\n- show copy/tts actions and delete in same row\\n- pass delete handler into `MessageContent`\\n- remove old delete button placement\\n\\n## Testing\\n- `bun run scripts/pre-commit-lint.js` *(fails: Script not found \\\"prettier\\\")*\\n- `bun test\"\n    },\n    {\n      \"title\": \"fix: Eliza290/cli test command\",\n      \"prNumber\": 4688,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR comprehensively updates the ElizaOS test cli command to provide a more consistent and improved testing experience across both plugins and projects.\\r\\n\\r\\n**Key Changes**\\r\\n\\r\\n1. CLI Command Structure: Reorganized the test command with th\"\n    },\n    {\n      \"title\": \"feat: add timeout to cli tests\",\n      \"prNumber\": 4687,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: Unify env file lookup across CLI\",\n      \"prNumber\": 4686,\n      \"type\": \"feature\",\n      \"body\": \"## Summary\\n- add `findNearestEnvFile` utility\\n- use the new helper throughout CLI commands and utils\\n\\n## Testing\\n- `bun test` *(fails: Cannot find module '@elizaos/core')*\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit\"\n    },\n    {\n      \"title\": \"feat: Lower web server logging (no 404 or ping logging)\",\n      \"prNumber\": 4685,\n      \"type\": \"feature\",\n      \"body\": \"My heart isn't going to break if this is not merged, merely a suggestion\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"feat: Clean up plugin loading logging\",\n      \"prNumber\": 4684,\n      \"type\": \"feature\",\n      \"body\": \"loading plugins just takes too much output and it's working fine now for the most part\\r\\n- just lower output for debug channel\\r\\n- move success to success channel\\r\\n\\r\\nMy heart isn't going to break if this is not merged, merely a suggestion\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"remove farcaster plugin\",\n      \"prNumber\": 4682,\n      \"type\": \"other\",\n      \"body\": \"moved to: https://github.com/elizaos-plugins/plugin-farcaster\"\n    },\n    {\n      \"title\": \"[Spartan] Minor tweaks\",\n      \"prNumber\": 4681,\n      \"type\": \"other\",\n      \"body\": \"Just minor tweaks I've made so far\"\n    },\n    {\n      \"title\": \"remove telegram-plugin\",\n      \"prNumber\": 4680,\n      \"type\": \"other\",\n      \"body\": \"moved to: https://github.com/elizaos-plugins/plugin-telegram\"\n    },\n    {\n      \"title\": \"fix: handle TRANSCRIPTION params & ensure proper agent log type compa\u2026\",\n      \"prNumber\": 4679,\n      \"type\": \"bugfix\",\n      \"body\": \"\\n\\n<!-- This is an auto-generated comment: release notes by coderabbit.ai -->\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n  - Added support for viewing and filtering \\\"Transcription\\\" actions in the action viewer, including a new filter opti\"\n    }\n  ],\n  \"topContributors\": [\n    {\n      \"username\": \"wtfsayo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n      \"totalScore\": 2267.7433032804574,\n      \"prScore\": 2187.8713032804576,\n      \"issueScore\": 0,\n      \"reviewScore\": 73,\n      \"commentScore\": 6.871999999999999,\n      \"summary\": \"wtfsayo: Merged 41 PRs this month with substantial contributions to plugin system improvements, including custom embedding endpoint support (#4421), auth middleware (#4420), and third-party plugin installation (#4568, +413/-211 lines). Focused heavily on code cleanup and refactoring, particularly in environment handling (#4445, +1734/-1067 lines) and agent loading optimization (#4519, +484/-336 lines), while also fixing critical issues in PGLite migrations (#4532, #4531) and runtime types (#4495). Maintained an active review presence with 13 reviews and 76 PR comments, working consistently throughout the month on both feature development and infrastructure improvements.\"\n    },\n    {\n      \"username\": \"0xbbjoker\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n      \"totalScore\": 1393.9053720361433,\n      \"prScore\": 1330.6593720361432,\n      \"issueScore\": 0,\n      \"reviewScore\": 57,\n      \"commentScore\": 6.2459999999999996,\n      \"summary\": \"0xbbjoker: Led a major refactoring effort to streamline the monorepo by removing multiple plugins (including local-ai, ollama, groq, venice, redpill, anthropic, and others) through PRs like #4439 (+532/-13404 lines) and #4422 (+646/-3413 lines). Fixed numerous bugs across the codebase with 9 fix-related PRs including #4496 for TTS manager and transcribe (+598/-561 lines) and #4594 for send-message-api (+242/-223 lines). Made significant contributions to testing infrastructure with PR #4518 adding integration tests (+38968/-3359 lines) and has 9 open PRs focused on new features like MySQL support and PDF RAG functionality. Maintained a consistent work pattern across 17 days this month, approving 5 PRs and providing 43 PR comments while making substantial code changes (+120093/-57625 lines across 1448 files).\"\n    },\n    {\n      \"username\": \"ChristopherTrimboli\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4\",\n      \"totalScore\": 1129.7180579355831,\n      \"prScore\": 935.5220579355831,\n      \"issueScore\": 0,\n      \"reviewScore\": 191.5,\n      \"commentScore\": 2.6959999999999997,\n      \"summary\": \"ChristopherTrimboli: Merged 15 PRs this month, with significant contributions including a major cleanup of agent loading code (#4524, -2213 lines), implementing TypeScript improvements across multiple repositories (#4504, #4529), and enhancing database operations with Drizzle ORM (#4500). Focused primarily on bug fixes and code cleanup, with notable work on fixing client imports (#4599), improving CLI functionality (#4482), and implementing a documentation auto-deployment system (#4631). Actively reviewed code with 31 reviews (24 approvals), showing consistent engagement despite working on only about a third of the days this month.\"\n    },\n    {\n      \"username\": \"yungalgo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/113615973?u=92e0f29f7e2fbb8ce46ed13c51f692ca803de02d&v=4\",\n      \"totalScore\": 714.7657174818842,\n      \"prScore\": 708.4857174818841,\n      \"issueScore\": 0,\n      \"reviewScore\": 5,\n      \"commentScore\": 1.28,\n      \"summary\": \"yungalgo: Led significant CLI command improvements with 12 merged PRs (+12,689/-7,862 lines), focusing on refactoring, enhancing, and fixing various commands including publish, agent, start, update, env, and dev. Made substantial upgrades to the agent command in PR #4560 (+1982/-896 lines) and implemented major updates to the CLI update command in PR #4592 (+6726/-894 lines). Currently has 7 open PRs related to plugins and agent CLI commands, showing consistent work on improving the command-line interface. Demonstrated an occasional activity pattern, contributing on 12 days this month with 93 commits across 169 modified files.\"\n    },\n    {\n      \"username\": \"odilitime\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n      \"totalScore\": 417.53329358348645,\n      \"prScore\": 362.3932935834864,\n      \"issueScore\": 0,\n      \"reviewScore\": 54,\n      \"commentScore\": 1.1400000000000001,\n      \"summary\": \"odilitime: Made significant code contributions with 28 commits modifying 5,215 files (+223,148/-96,693 lines), including merging 4 PRs with focused changes to plugin functionality (#4415, #4414) and a major release (#4501). Provided 9 code reviews with 6 approvals while maintaining 3 open PRs focused on plugin specifications and database API improvements. Activity was sporadic, concentrated on a few days with primary focus on other work (82%) and refactoring (11%), touching code, documentation, and configuration files.\"\n    },\n    {\n      \"username\": \"lalalune\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/18633264?u=e2e906c3712c2506ebfa98df01c2cfdc50050b30&v=4\",\n      \"totalScore\": 320.5891581616555,\n      \"prScore\": 309.4111581616555,\n      \"issueScore\": 0,\n      \"reviewScore\": 10,\n      \"commentScore\": 1.178,\n      \"summary\": \"lalalune: Merged 4 significant PRs this month, including major bugfixes in #4515 \\\"Shaw bugfixes\\\" (+16994/-19402 lines) and dependency updates in #4411 (+4392/-12278 lines), while maintaining 3 open PRs including \\\"V2 Spartan\\\" (#4630). Their contributions were substantial but sporadic, active on only 6 days with 22 commits modifying 432 files (+17541/-21908 lines) across primarily code (62%) and config files (23%). Additionally, they provided 2 approving reviews and participated in discussions with 4 PR comments and 1 issue comment.\"\n    },\n    {\n      \"username\": \"tcm390\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/60634884?u=c6c41679b8322eaa0c81f72e0b4ed95e80f0ac16&v=4\",\n      \"totalScore\": 274.98486159859334,\n      \"prScore\": 233.30486159859333,\n      \"issueScore\": 0,\n      \"reviewScore\": 41,\n      \"commentScore\": 0.6799999999999999,\n      \"summary\": \"tcm390: Made significant contributions to Twitter integration, merging 7 PRs including a major Twitter timeline feature (#4429, +684/-2105 lines) and substantial improvements to reply action functionality (#4608, +6991/-942 lines). Fixed several issues including LLM response parsing (#4580), message handling (#4589), and sender identification (#4616). Demonstrated focused work on code cleanup and feature enhancement, with particularly large code changes in the reply action system, while maintaining a pattern of occasional but impactful activity throughout the month.\"\n    },\n    {\n      \"username\": \"K1mc4n\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/156217571?u=cc94e7743c591f36eaf958d88befa855348bba9d&v=4\",\n      \"totalScore\": 216.73787878783102,\n      \"prScore\": 212.53787878783103,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"K1mc4n: Contributed significantly to documentation with one merged PR (#4488) that added an Indonesian README file (+57288/-24287 lines), while having 8 additional open PRs related to Indonesian documentation improvements. Created two open issues (#4565, #4561) related to CI and path problems. Activity was sporadic, concentrated on just 4 days this month, with documentation work accounting for 87% of their contributions across 3973 modified files.\"\n    },\n    {\n      \"username\": \"samarth30\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/48334430?u=1fc119a6c2deb8cf60448b4c8961cb21dc69baeb&v=4\",\n      \"totalScore\": 160.4068742660077,\n      \"prScore\": 160.20687426600767,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"samarth30: Merged a substantial PR #4471 \\\"Feat/jimmy pm agent\\\" with significant code changes (+287344/-158985 lines) while maintaining three open PRs focused on feature development. Modified 83 files across 13 commits, with code changes totaling +4848/-1707 lines primarily focused on feature work (54%) and distributed across code (35%), config (29%), and docs (12%). Activity was sporadic, concentrated on just 3 days this month.\"\n    },\n    {\n      \"username\": \"ai16z-demirix\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/188117230?u=424cd5b834584b3799da288712b3c4158c8032a1&v=4\",\n      \"totalScore\": 98.38207487215577,\n      \"prScore\": 88.98207487215576,\n      \"issueScore\": 0,\n      \"reviewScore\": 9,\n      \"commentScore\": 0.4,\n      \"summary\": \"ai16z-demirix: Focused heavily on test improvements with three open PRs (#4481, #4605, #4604) that collectively modified 275 files (+5847/-2782 lines). Made significant contributions to test coverage and setup (73% of changes) with additional work on configuration files (20%), spread across 19 commits. Activity was sporadic, with contributions on only 6 days this month, primarily providing review comments on 2 PRs.\"\n    },\n    {\n      \"username\": \"standujar\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4\",\n      \"totalScore\": 91.38603231557502,\n      \"prScore\": 81.24803231557502,\n      \"issueScore\": 0,\n      \"reviewScore\": 9.5,\n      \"commentScore\": 0.6379999999999999,\n      \"summary\": \"standujar: Merged 3 significant PRs this month, including a feature for emitting model usage events in the OpenAI plugin (#4438, +2409/-3824 lines), a fix for JSON serialization in pglite (#4458, +2042/-2710 lines), and a Discord service timeout fix (#4450, +199/-1016 lines). Overall contributed substantial code changes across 86 files (+262/-3290 lines) with a primary focus on bug fixes (63%). Provided 2 code reviews and participated in discussions with 4 comments across PRs and issues, showing sporadic activity on just 4 days this month.\"\n    },\n    {\n      \"username\": \"HarshModi2005\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/142230924?u=64e337bbdb6b3aded5943b7e297759e7a3cfc0f0&v=4\",\n      \"totalScore\": 88.4755477931522,\n      \"prScore\": 83.9755477931522,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0,\n      \"summary\": \"HarshModi2005: Made substantial code contributions with one merged PR #4575 \\\"Issue 451\\\" (+14573/-8703 lines) and has another open PR #4636 for polygon resolution. Modified 217 files across 16 commits with significant code changes (+28062/-14077 lines), focusing primarily on refactoring (31%) and test improvements (36% of file types). Contributed sporadically, being active on only 5 days this month, and provided one review comment.\"\n    },\n    {\n      \"username\": \"Samarthsinghal28\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/120447590?v=4\",\n      \"totalScore\": 87.0875477931522,\n      \"prScore\": 87.0875477931522,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Samarthsinghal28: Opened two pull requests related to a Polygon Plugin (#4573 and #4635), though neither has been merged yet. No other activity was observed during this period.\"\n    },\n    {\n      \"username\": \"tercel\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/4879512?u=9a2520224d9ae039a506c03dcf58406f52734361&v=4\",\n      \"totalScore\": 78.54402427508752,\n      \"prScore\": 78.34402427508752,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"tercel: Merged three PRs on a single day this month, including enhancements to message handling (#4508), refactoring model handling in AgentRuntime (#4507, +56/-16 lines), and fixing Twitter functionality (#4506). The contributions were evenly distributed across feature work, refactoring, and other improvements, with all changes focused on code files totaling +88/-29 lines overall.\"\n    },\n    {\n      \"username\": \"monilpat\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/15067321?v=4\",\n      \"totalScore\": 71.43177389657609,\n      \"prScore\": 40.4317738965761,\n      \"issueScore\": 0,\n      \"reviewScore\": 31,\n      \"commentScore\": 0,\n      \"summary\": \"monilpat: Contributed a significant amount of code (+14,749/-3,448 lines across 124 files) while working on the open polygon feature PR (#4449). Provided 6 code reviews with 5 approvals and 1 change request. Activity was sporadic, being active on only 5 days this month, with work primarily focused on other development (58%) and bug fixes (25%).\"\n    },\n    {\n      \"username\": \"Dahka2321\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/160153877?u=b12d72ea58a9908bcab2c1176727879cb9582f37&v=4\",\n      \"totalScore\": 68.58563738921922,\n      \"prScore\": 68.58563738921922,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Dahka2321: Focused exclusively on documentation maintenance this month, merging 3 PRs (#4433, #4460, #4527) that fixed broken links and image paths. All contributions were small in scope, with the largest PR (#4460) containing only +2/-2 lines of changes. Currently has one open PR (#4576) continuing the pattern of fixing outdated links in documentation.\"\n    },\n    {\n      \"username\": \"0xCardiE\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/8969767?u=8b05509ceb96fd63a6246dfbf0860fd1df586e59&v=4\",\n      \"totalScore\": 64.69670577444035,\n      \"prScore\": 62.49670577444034,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"0xCardiE: Made a focused contribution this month with one merged PR (#4634) that improved the API to return the ID of newly created agents, modifying 1 file with +174/-101 lines of code. Also opened issue #4632 regarding username changes in the leaderboard that remains open. Activity was limited to a single day this month, suggesting sporadic engagement with the project.\"\n    },\n    {\n      \"username\": \"harperaa\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/1330944?v=4\",\n      \"totalScore\": 60.94272948884172,\n      \"prScore\": 60.16472948884172,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.7779999999999999,\n      \"summary\": \"harperaa: Merged two bug fix PRs this month, including PR #4537 addressing an error with TEXT_EMBEDDING (+32/-4 lines) and PR #4557 fixing the community manager to use plugin-local-ai out of the box (+1158/-519 lines). Contributed to discussions by commenting on 3 issues and 3 PRs. Activity was sporadic, concentrated on a single day during the month.\"\n    },\n    {\n      \"username\": \"michavie\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/39144548?u=3496eb82a60d2a8e88bf5e22c3ffe5eb2b37d816&v=4\",\n      \"totalScore\": 52.6576561356211,\n      \"prScore\": 52.4576561356211,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"michavie: Fixed ESM type generation issues across multiple packages with PR #4442, making significant changes (+2473/-1637 lines) to 11 configuration files. Activity was sporadic, with contributions on only 2 days this month. The PR addressed bugs in the SQL, Bootstrap, and OpenAI packages, taking 29 hours to merge.\"\n    },\n    {\n      \"username\": \"Y4NK33420\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/112804719?v=4\",\n      \"totalScore\": 49.836641204912,\n      \"prScore\": 45.136641204911996,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0.2,\n      \"summary\": \"Y4NK33420: Opened a significant PR #4574 \\\"Implement Polygon Gas Oracle Integration\\\" with substantial code changes (+19,298/-4,066 lines) across 113 files. Contributed 6 commits with a primary focus on new feature development (83%) and bug fixes (17%), modifying code (52%), tests (26%), and configuration files (16%). Provided one code review with comments on another PR. Activity was sporadic, being active on only 3 days this month.\"\n    },\n    {\n      \"username\": \"bowtiedbluefin\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/95500901?v=4\",\n      \"totalScore\": 42.0927738965761,\n      \"prScore\": 41.352773896576096,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.74,\n      \"summary\": \"bowtiedbluefin: Opened one PR (#4466) to create a Morpheus plugin, making significant code changes across 11 files (+750/-10687 lines) with a focus on configuration and code files. Activity was limited to a single day this month, with 4 comments made on the open PR.\"\n    },\n    {\n      \"username\": \"madjin\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n      \"totalScore\": 40.7017738965761,\n      \"prScore\": 36.2017738965761,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0,\n      \"summary\": \"madjin: Focused heavily on documentation work this month, merging a substantial PR #4586 that updated docs with +30,234/-35,364 lines across 793 files. Created 4 issues related to documentation and CLI improvements (all now closed), including \\\"Improving CLI tool instructions\\\" (#4113) and addressing an npx error (#4107). Contributed sporadically across 5 days with 19 commits, primarily making documentation changes (98% of modifications). Provided 1 review comment on another contributor's work.\"\n    },\n    {\n      \"username\": \"jkbrooks\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/129074?u=4cd0bf499a885dd922e04d57e805c88f7c6dd4f9&v=4\",\n      \"totalScore\": 40.4317738965761,\n      \"prScore\": 40.4317738965761,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"girinathchickoo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/67161043?u=39b4f0074d1f6e30a452777b279b2dd00cc095cf&v=4\",\n      \"totalScore\": 40.4317738965761,\n      \"prScore\": 40.4317738965761,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"girinathchickoo: Opened one pull request (#4620 \\\"Feature/plugin blockend\\\") which remains open and has not yet been merged. No other GitHub activity was observed during this period.\"\n    },\n    {\n      \"username\": \"eveneast\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/166489430?u=adda9548080e07d370ef8c9ba9c3408dcf3bc629&v=4\",\n      \"totalScore\": 39.00961228866811,\n      \"prScore\": 39.00961228866811,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"eveneast: Made a small documentation improvement by removing a redundant word in the Solana v2 documentation, with PR #4520 (+1/-1 lines) being merged. Initially submitted as PR #4516, which was later closed in favor of the merged version. Active on only one day this month, with all contributions focused on documentation improvements.\"\n    },\n    {\n      \"username\": \"HashWarlock\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/64296537?u=1d8228a93c06c603e08d438677b3f736d6b1ab22&v=4\",\n      \"totalScore\": 38.49650756146648,\n      \"prScore\": 33.49650756146648,\n      \"issueScore\": 0,\n      \"reviewScore\": 5,\n      \"commentScore\": 0,\n      \"summary\": \"HashWarlock: Contributed a single merged PR (#4572) focused on fixing TEE updates for CI, modifying 6 configuration files with +22/-16 lines of code changes. The PR \\\"fix: TEE update for CI\\\" contained moderate changes (+381/-173 lines) and was merged on the same day it was submitted. Activity was limited to a single day this month, with work primarily focused on feature development (50%) and bug fixes (25%).\"\n    },\n    {\n      \"username\": \"crypto-cooker\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16945788?u=819d567b766cb43113f89fb60ba0fac4c5137cf5&v=4\",\n      \"totalScore\": 33.9277738965761,\n      \"prScore\": 33.9277738965761,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"Freytes\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/4147278?u=89aa9570e6f8b4a8e9e41e8f908c16fb69c5a43f&v=4\",\n      \"totalScore\": 33.8947738965761,\n      \"prScore\": 33.8947738965761,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Freytes: Working on a Jupiter Swap plugin with one open PR (#4593) that involves substantial code changes (+4198/-703 lines across 70 files). Active on only 5 days this month with sporadic contribution patterns, primarily focused on other work (77%) with some feature development (23%). The changes predominantly affect code (65%) and configuration files (24%), suggesting significant implementation work on this plugin.\"\n    },\n    {\n      \"username\": \"Mylookingisverynormal\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/50126677?u=feff54f0c3d192da7bed64c0a5276c4d9dfb144c&v=4\",\n      \"totalScore\": 27.270573590279973,\n      \"prScore\": 27.270573590279973,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Mylookingisverynormal: Made a single documentation contribution this month with PR #4483, which updated README.md with a one-line addition. This was their only activity during the period, representing a minimal but focused documentation improvement.\"\n    },\n    {\n      \"username\": \"imholders\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/202005793?v=4\",\n      \"totalScore\": 23.65222459886074,\n      \"prScore\": 23.65222459886074,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"imholders: Opened one pull request (#4567) to add a Malaysian README file, which remains open. Made modest code changes across 5 files (+206/-2 lines), evenly split between documentation and configuration work. Active on only 2 days this month with a sporadic contribution pattern.\"\n    },\n    {\n      \"username\": \"rnkrtt\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/140164174?u=e9c995a0fea6665e5c211be5c5957be8f8e8e4bd&v=4\",\n      \"totalScore\": 23.56537417291718,\n      \"prScore\": 23.165374172917183,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.4,\n      \"summary\": \"rnkrtt: Opened two documentation-related PRs this month: #4441 to fix typos and #4555 to repair a broken Quickstart link, with modest code changes (+64/-64 lines) across 5 files. Activity was sporadic, occurring on just 3 days of the month, with contributions primarily focused on documentation (67%) and configuration files (33%).\"\n    },\n    {\n      \"username\": \"vtjl10\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/139509124?u=8af1413f5a26c1ddba22afba7a750f2bf4b21dea&v=4\",\n      \"totalScore\": 23.27272392623351,\n      \"prScore\": 23.07272392623351,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"vtjl10: Made a single contribution this month with PR #4470 \\\"Fix typos and improve dependencies management\\\", which was merged after 17 hours and modified documentation files (+4/-4 lines). The PR appears to have involved substantial changes (+52446/-24025 lines) while focusing on documentation improvements and dependency management. vtjl10 also left one comment on a pull request during their single day of activity this month.\"\n    },\n    {\n      \"username\": \"Dangoz\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/71613713?u=1839f372422c7a5503a713dca22981490b4ea7da&v=4\",\n      \"totalScore\": 21.086306144334053,\n      \"prScore\": 21.086306144334053,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Dangoz: Made a single documentation fix with PR #4443 \\\"docs: fix title spacing\\\" (+1/-1 lines), which was merged after 16 hours. This was their only contribution during the month, representing a minimal but targeted bugfix to documentation formatting.\"\n    },\n    {\n      \"username\": \"pengqiseven\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/134899215?u=dbd15740f37368d3f8c3e2b97554c3791b1eae8a&v=4\",\n      \"totalScore\": 16.975738181995926,\n      \"prScore\": 16.975738181995926,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"pengqiseven: Opened one pull request (#4615) to fix typos in comments, modifying 5 files with minimal changes (+5/-5 lines). This single contribution represents their only activity this month, with changes primarily affecting code files (80%) and some documentation (20%).\"\n    },\n    {\n      \"username\": \"BinaryBluePeach\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/192237769?v=4\",\n      \"totalScore\": 15.3374379124341,\n      \"prScore\": 12.4974379124341,\n      \"issueScore\": 2.3,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.54,\n      \"summary\": \"BinaryBluePeach: Opened one issue (#4536) regarding a module import error and has an open PR (#4606) titled \\\"recovery\\\" with minimal code changes (+2/-2 lines across 2 files). Contributed to discussions by commenting on 3 issues and 1 PR. Activity was limited to a single day this month, suggesting sporadic engagement with the project.\"\n    },\n    {\n      \"username\": \"github-advanced-security\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/in/57789?v=4\",\n      \"totalScore\": 9,\n      \"prScore\": 0,\n      \"issueScore\": 0,\n      \"reviewScore\": 9,\n      \"commentScore\": 0,\n      \"summary\": \"github-advanced-security: Provided 2 review comments this month with no other activity. Their participation was sporadic with limited engagement overall.\"\n    },\n    {\n      \"username\": \"Pronoss\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/170206917?u=d6951aa21026fb848e923d335622f06c32607e8c&v=4\",\n      \"totalScore\": 5.78571895621705,\n      \"prScore\": 5.78571895621705,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Pronoss: Opened one pull request (#4563) to fix typos in the documentation file \\\"faq-and-support.md\\\" with minimal changes (+2/-2 lines). This was their only contribution during the month, representing a single day of activity.\"\n    },\n    {\n      \"username\": \"dizer-ti\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/155266991?u=83090ea70c646fdfa8d8b4c826bdda84ac806d28&v=4\",\n      \"totalScore\": 5.032306144334054,\n      \"prScore\": 5.032306144334054,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"dizer-ti: Fixed a broken link to the ELIZA demo in the documentation with a single merged PR (#4597), making a small but helpful correction (+1/-1 lines). This was their only contribution during the month, representing a focused effort on documentation maintenance.\"\n    },\n    {\n      \"username\": \"zeevick10\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/140458077?u=234a5b1512060121b98420da18d7a6cdd9d0255c&v=4\",\n      \"totalScore\": 4.918,\n      \"prScore\": 4.918,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"zeevick10: Opened one pull request (#4419) to update Character.md with a single line change (+1/-1). Activity was minimal with contributions on only one day this month.\"\n    },\n    {\n      \"username\": \"plvo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/113256696?u=e596d0939094820484fdb4c98ba336204d18de82&v=4\",\n      \"totalScore\": 4.3,\n      \"prScore\": 0,\n      \"issueScore\": 4.1,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"plvo: Reported issue #4457 regarding a \\\"pglite log entry unicode escape error\\\" which was subsequently closed. Added a single comment on an issue during the month. No code contributions or pull request activity during this period.\"\n    },\n    {\n      \"username\": \"TheDeveloperTom\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/25426552?u=29cf260cfeace413f66efafcedff2d4e3252a8f3&v=4\",\n      \"totalScore\": 4,\n      \"prScore\": 0,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"TheDeveloperTom: Created a single issue (#4432) titled \\\"Job: looking for a developer with Eliza framework experience,\\\" which has since been closed. No other activity was observed this month, with no code contributions, pull requests, or comments on any issues or PRs.\"\n    },\n    {\n      \"username\": \"Icarus-Community\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/174098848?u=e1b5a7fe3b0a3bda521bb26fc2e5bc3fa21393c2&v=4\",\n      \"totalScore\": 2.3000000000000003,\n      \"prScore\": 0,\n      \"issueScore\": 2.1,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": null\n    },\n    {\n      \"username\": \"Kirstygoodary\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/55052540?u=48b08ce5f55bb74b12bdc06500aece654eaadcff&v=4\",\n      \"totalScore\": 2.1,\n      \"prScore\": 0,\n      \"issueScore\": 2.1,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Kirstygoodary: Opened issue #4418 regarding a handler error for text embedding delegate type. Contributed a comment on an issue, showing some engagement with the project's issue tracking. Activity was minimal this month with no code contributions or pull requests.\"\n    },\n    {\n      \"username\": \"samgermain\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/29212519?u=fd61622f9ae4f651f49755a1ce0b01e7fb2f31f0&v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"samgermain: Created issue #4562 \\\"Make a publish to npm\\\" which was subsequently closed, and commented on one issue. No code contributions or pull requests this month, with minimal overall activity.\"\n    },\n    {\n      \"username\": \"nabz-polo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/65369404?u=2e8d0f763349ed5405bac2f34457acdb019f7563&v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"nabz-polo: Created one issue this month (#4503) requesting OLLAMA support, which remains open. No other activity was observed during this period.\"\n    },\n    {\n      \"username\": \"kunleulysses\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/65002977?v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"kunleulysses: Opened a single issue (#4486) regarding an agent hanging after core initialization and REST API binding related to Anthropic. No other activity was observed this month.\"\n    },\n    {\n      \"username\": \"cxp-13\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/84974164?u=3b5b5c18f44af73f1e2f9921381fe2e800f474d1&v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"cxp-13: Opened issue #4440 regarding a TypeScript type definition problem (\\\"Property 'preconnect' is missing in type\\\"). No other activity this month.\"\n    },\n    {\n      \"username\": \"POKENA7\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/75174441?u=4db72f514d13671ea5674518c47593ea5786d603&v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"POKENA7: Opened one issue (#4461) regarding unimplemented Discord auto-post functionality in eliza v2. No other contributions this month.\"\n    },\n    {\n      \"username\": \"FancyFishok\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/96703751?v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"FancyFishok: Opened a single issue (#4588) regarding difficulty getting their bot to detect Twitter activity. No other contributions or code changes were made during this period.\"\n    },\n    {\n      \"username\": \"AndreaRettaroli\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/69209567?u=112b2ba16a6fb9295c5e71787a02e1446307e1eb&v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"AndreaRettaroli: Opened one issue this month (#4528) regarding improvements to Eliza in TEE oasis, which remains open. No other activity was observed during this period.\"\n    },\n    {\n      \"username\": \"AlteredCode\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/63291609?v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"AlteredCode: Opened a single issue (#4607) regarding system responsiveness problems, specifically about the system not responding to mentions and failing to analyze certain content. No other activity was observed this month, with no code contributions, reviews, or comments on any PRs or issues.\"\n    }\n  ],\n  \"newPRs\": 269,\n  \"mergedPRs\": 204,\n  \"newIssues\": 16,\n  \"closedIssues\": 29,\n  \"activeContributors\": 68\n}\n---\n[\"Samarthsinghal28_week_2025-05-18\", \"Samarthsinghal28\", \"week\", \"2025-05-18\", \"Samarthsinghal28: Opened one pull request (#4635) titled \\\"Added : Polygon Plugin\\\" which is currently under review. No other activity was observed during this period.\", \"2025-05-18T23:08:18.508Z\"]\n[\"ChristopherTrimboli_week_2025-05-18\", \"ChristopherTrimboli\", \"week\", \"2025-05-18\", \"ChristopherTrimboli: Fixed documentation deployment issues by merging PR #4640 which removed 8 lines of code, and proposed a fix for agent start button functionality in PR #4642 which is still open. Also contributed one code review with approval, focusing exclusively on bugfixes across configuration and code files.\", \"2025-05-18T23:08:18.704Z\"]\n[\"0xbbjoker_week_2025-05-18\", \"0xbbjoker\", \"week\", \"2025-05-18\", \"0xbbjoker: Made significant code changes across 14 files (+3275/-1616 lines) in 3 commits, with activity concentrated on a single day. The work primarily focused on feature development (67%) with some additional miscellaneous changes (33%), though no PRs were merged or opened during this period.\", \"2025-05-18T23:08:18.549Z\"]\n[\"Freytes_week_2025-05-18\", \"Freytes\", \"week\", \"2025-05-18\", \"Freytes: Made a single commit modifying 2 files with 90 additions and 23 deletions, showing sporadic activity with contributions on only one day this week.\", \"2025-05-18T23:08:18.044Z\"]\n[\"HarshModi2005_week_2025-05-18\", \"HarshModi2005\", \"week\", \"2025-05-18\", \"HarshModi2005: Opened one pull request (#4636 \\\"Merge addpolygon resolution\\\") with substantial code changes across 83 files (+13,489/-5,374 lines). The work was concentrated on a single day, with contributions split between code (54%) and tests (30%), suggesting a significant feature integration or refactoring effort.\", \"2025-05-18T23:08:19.534Z\"]\n[\"Y4NK33420_week_2025-05-18\", \"Y4NK33420\", \"week\", \"2025-05-18\", \"Y4NK33420: Made substantial code changes with 3 commits modifying 93 files (+16,941/-3,967 lines) in a single day of activity. No PRs, issues, or reviews during this period.\", \"2025-05-18T23:08:20.054Z\"]\n[\"madjin_week_2025-05-18\", \"madjin\", \"week\", \"2025-05-18\", \"madjin: Created one issue (#4260) related to updating the community section, which has since been closed. No other activity was observed during this period.\", \"2025-05-18T23:08:20.347Z\"]\n[\"ai16z-demirix_week_2025-05-18\", \"ai16z-demirix\", \"week\", \"2025-05-18\", \"ai16z-demirix: Made substantial code changes with one large commit modifying 196 files (+3521/-500 lines) on a single day this week. No PRs were merged, issues created, or reviews conducted during this period.\", \"2025-05-18T23:08:20.493Z\"]\n[\"wtfsayo_week_2025-05-18\", \"wtfsayo\", \"week\", \"2025-05-18\", \"wtfsayo: Made substantial code changes across 743 files (+20510/-3309 lines) with a focus on other work (67%) and feature work (22%). Merged two PRs: #4643 adding a missing plugin failure test and #4637 enabling world selection in the message API. Has three open PRs in draft/development including work on registry functionality, RSS feed plugin, and deepsearch plugin.\", \"2025-05-18T23:08:22.197Z\"]\n[\"monilpat_week_2025-05-18\", \"monilpat\", \"week\", \"2025-05-18\", \"monilpat: Made substantial code changes across 41 files (+7411/-1541 lines) in 2 commits during a single day of activity this week. Provided 2 approving code reviews for teammates' work.\", \"2025-05-18T23:08:21.009Z\"]\n[\"AlteredCode_day_2025-05-16\", \"AlteredCode\", \"day\", \"2025-05-16\", \"AlteredCode: Created 1 issue today (#4607 \\\"Multiple issues - Not responding to mentions, not analyzing i...\\\") and showed sporadic activity, being active on only 1 out of 1 days this period.\", \"2025-05-18T23:07:41.052Z\"]\n[\"lalalune_day_2025-05-16\", \"lalalune\", \"day\", \"2025-05-16\", \"lalalune: Opened 1 pull request (#4609) to merge Spartan changes and made modifications to 1 file, focusing entirely on bugfix work with a net change of +1/-1 lines. Active today, maintaining a consistent work pattern.\", \"2025-05-18T23:07:41.267Z\"]\n[\"HarshModi2005_day_2025-05-16\", \"HarshModi2005\", \"day\", \"2025-05-16\", \"HarshModi2005: Engaged in a major refactoring effort, modifying 15 files with a total of -3525 lines across 4 commits, and provided 1 review comment. Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:07:41.289Z\"]\n[\"0xbbjoker_day_2025-05-16\", \"0xbbjoker\", \"day\", \"2025-05-16\", \"0xbbjoker: Merged 1 PR (#4612) addressing linter errors in the DB adapter (+75/-63 lines) and opened 2 new feature PRs (#4611, #4614). Made significant code changes across 11 files (+196/-90 lines), with a primary focus on bug fixes (75%).\", \"2025-05-18T23:07:41.438Z\"]\n[\"Freytes_day_2025-05-16\", \"Freytes\", \"day\", \"2025-05-16\", \"Freytes: Made significant code changes by modifying 11 files, resulting in a net addition of 419 lines of code, with a primary focus on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:07:41.652Z\"]\n[\"monilpat_day_2025-05-16\", \"monilpat\", \"day\", \"2025-05-16\", \"monilpat: Engaged in code reviews with a total of 2 reviews (1 approval and 1 change request), demonstrating sporadic activity today.\", \"2025-05-18T23:07:41.901Z\"]\n[\"tcm390_day_2025-05-16\", \"tcm390\", \"day\", \"2025-05-16\", \"tcm390: Merged 1 PR (#4608) focused on bug fixes, contributing a significant amount of code changes (+6991/-942 lines) across 52 modified files. Maintained a consistent activity pattern with 2 commits today.\", \"2025-05-18T23:07:42.383Z\"]\n[\"Freytes_day_2025-05-17\", \"Freytes\", \"day\", \"2025-05-17\", \"Freytes: Made significant code changes by modifying 7 files with a total of +466 lines, focusing entirely on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:08:36.244Z\"]\n[\"Samarthsinghal28_day_2025-05-18\", \"Samarthsinghal28\", \"day\", \"2025-05-18\", \"Samarthsinghal28: Opened 1 PR (#4635) titled \\\"Added: Polygon Plugin\\\" but has not merged any PRs today. Activity remains sporadic with no other contributions noted.\", \"2025-05-18T23:08:36.712Z\"]\n[\"HarshModi2005_day_2025-05-17\", \"HarshModi2005\", \"day\", \"2025-05-17\", \"HarshModi2005: Made significant code changes by modifying 34 files with a total of +1772/-2081 lines across 3 commits, demonstrating a major refactoring effort. Active today and consistently engaged in development work.\", \"2025-05-18T23:08:36.606Z\"]\n[\"wtfsayo_day_2025-05-16\", \"wtfsayo\", \"day\", \"2025-05-16\", \"wtfsayo: Opened 1 pull request (#4613) focused on adding a local AI CI test, while making significant code changes by modifying 44 files (+1140/-510 lines) with a primary focus on other work (54%) and tests (31%). Active today with 13 commits, demonstrating a consistent work pattern.\", \"2025-05-18T23:07:42.851Z\"]\n[\"Freytes_day_2025-05-18\", \"Freytes\", \"day\", \"2025-05-18\", \"Freytes: Made code changes by modifying 2 files, resulting in a net change of +90 lines added and -23 lines removed, with a total of 1 commit. Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:08:36.495Z\"]\n[\"0xbbjoker_day_2025-05-17\", \"0xbbjoker\", \"day\", \"2025-05-17\", \"0xbbjoker: Merged 1 PR (#4624) addressing a client auth issue with significant changes (+47/-10 lines) and opened another PR (#4623) to test a workflow. Made extensive code modifications across 117 files (+6234/-1848 lines) with a primary focus on bugfix work (43%) and feature development (30%).\", \"2025-05-18T23:08:36.683Z\"]\n[\"yungalgo_day_2025-05-16\", \"yungalgo\", \"day\", \"2025-05-16\", \"yungalgo: Merged 1 PR (#4610 \\\"Eliza290/cli command env\\\") with significant changes of +388/-86 lines, focusing primarily on bugfix work (44%). Demonstrated consistent activity with 9 commits across 9 modified files, maintaining a balanced approach between code and documentation contributions.\", \"2025-05-18T23:07:43.007Z\"]\n[\"0xCardiE_day_2025-05-17\", \"0xCardiE\", \"day\", \"2025-05-17\", \"0xCardiE: Merged 1 PR (#4634) that added functionality to return the ID of newly created agents, with significant code changes of +174/-101 lines. Additionally, created 1 issue (#4632) regarding updating username changes on the leaderboard, maintaining a consistent activity pattern.\", \"2025-05-18T23:08:36.785Z\"]\n[\"ChristopherTrimboli_day_2025-05-18\", \"ChristopherTrimboli\", \"day\", \"2025-05-18\", \"ChristopherTrimboli: Merged 1 pull request (#4640) focused on fixing the docs deploy workflow (+0/-8 lines) and opened another PR (#4642) addressing the agent start button functionality. Made modifications to 3 files with a total of +2/-20 lines, maintaining a consistent focus on bugfix work.\", \"2025-05-18T23:08:37.208Z\"]\n[\"ChristopherTrimboli_day_2025-05-17\", \"ChristopherTrimboli\", \"day\", \"2025-05-17\", \"ChristopherTrimboli: Merged 1 PR (#4631 \\\"ci: Docs auto deployer\\\") with significant contributions of +47 lines, while also opening another PR (#4633 \\\"cleanup: optz actions functions\\\"). Modified 3 files with a total of +141/-55 lines, demonstrating a consistent work pattern with a focus on other work (67%) and documentation (33%).\", \"2025-05-18T23:08:37.186Z\"]\n[\"HarshModi2005_day_2025-05-18\", \"HarshModi2005\", \"day\", \"2025-05-18\", \"HarshModi2005: Opened 1 pull request (#4636) titled \\\"Merge addpolygon resolution\\\" and made significant code changes, modifying 83 files with a total of +13489/-5374 lines across 6 commits. The work was evenly split between tests, other tasks, feature development, and bug fixes, demonstrating consistent daily activity.\", \"2025-05-18T23:08:36.886Z\"]\n[\"girinathchickoo_day_2025-05-17\", \"girinathchickoo\", \"day\", \"2025-05-17\", \"girinathchickoo: Opened 1 pull request (#4620 \\\"Feature/plugin blockend\\\") but did not merge any today, showing sporadic activity with no other contributions.\", \"2025-05-18T23:08:37.776Z\"]\n[\"lalalune_day_2025-05-17\", \"lalalune\", \"day\", \"2025-05-17\", \"lalalune: Opened 1 pull request (#4630 \\\"V2 Spartan\\\") but has not merged any today, showing sporadic activity with no other contributions.\", \"2025-05-18T23:08:37.548Z\"]\n[\"ai16z-demirix_day_2025-05-18\", \"ai16z-demirix\", \"day\", \"2025-05-18\", \"ai16z-demirix: Made significant code changes by modifying 196 files, resulting in a net change of +3521/-500 lines, with a primary focus on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:08:39.162Z\"]\n[\"madjin_day_2025-05-18\", \"madjin\", \"day\", \"2025-05-18\", \"madjin: Created 1 issue today (#4260 \\\"chore: Update community section\\\" (CLOSED)), showing sporadic activity with no other contributions.\", \"2025-05-18T23:08:38.037Z\"]\n[\"pengqiseven_day_2025-05-17\", \"pengqiseven\", \"day\", \"2025-05-17\", \"pengqiseven: Opened 1 pull request (#4615) focused on fixing typos in comments and modified 5 files with a total of 10 lines changed (+5/-5). Maintained a consistent activity pattern, dedicating efforts entirely to bugfix work today.\", \"2025-05-18T23:08:38.043Z\"]\n[\"monilpat_day_2025-05-17\", \"monilpat\", \"day\", \"2025-05-17\", \"monilpat: Reviewed 2 pull requests with 2 approvals, demonstrating engagement in the review process despite no merged contributions or code changes today. Activity remains sporadic, being active on only 1 out of the last 1 days.\", \"2025-05-18T23:08:37.615Z\"]\n[\"Y4NK33420_day_2025-05-18\", \"Y4NK33420\", \"day\", \"2025-05-18\", \"Y4NK33420: Made significant code changes by modifying 93 files, resulting in a total of +16,941 lines added and -3,967 lines removed across 3 commits, with a primary focus on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:08:38.009Z\"]\n[\"0xbbjoker_day_2025-05-18\", \"0xbbjoker\", \"day\", \"2025-05-18\", \"0xbbjoker: Made significant code changes by modifying 14 files, resulting in a total of +3275/-1616 lines across 3 commits, with a primary focus on feature work (67%). Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:08:36.294Z\"]\n[\"tcm390_day_2025-05-17\", \"tcm390\", \"day\", \"2025-05-17\", \"tcm390: Merged 1 PR (#4616) addressing the issue of senderName being \\\"Unknown\\\" in the recentMessages provider, with code changes of +4/-1 lines. Maintained a consistent activity pattern, being active every day.\", \"2025-05-18T23:08:38.611Z\"]\n[\"wtfsayo_day_2025-05-17\", \"wtfsayo\", \"day\", \"2025-05-17\", \"wtfsayo: Merged 3 PRs, including #4619 which involved significant changes (+109/-500 lines), while actively working on 6 open PRs. Made substantial modifications across 74 files (+1414/-1423 lines), with a primary focus on tests (35%) and bug fixes (26%).\", \"2025-05-18T23:08:39.206Z\"]\n[\"wtfsayo_day_2025-05-18\", \"wtfsayo\", \"day\", \"2025-05-18\", \"wtfsayo: Merged 2 PRs (#4643 and #4637) with a total of +40/-3 lines, while actively modifying 743 files with significant changes of +20510/-3309 lines across 18 commits. The primary focus was on other work (67%) and feature development (22%), demonstrating consistent daily activity.\", \"2025-05-18T23:08:38.715Z\"]\n[\"yungalgo_day_2025-05-17\", \"yungalgo\", \"day\", \"2025-05-17\", \"yungalgo: Merged 1 pull request (#4618 \\\"Eliza290/cli command dev\\\") with significant changes of +544/-432 lines, while modifying 7 files across 5 commits. Maintained a consistent activity pattern, focusing primarily on other work (80%) and contributing to both code (60%) and documentation (40%).\", \"2025-05-18T23:08:39.456Z\"]\n[\"monilpat_day_2025-05-18\", \"monilpat\", \"day\", \"2025-05-18\", \"monilpat: Made significant code changes by modifying 41 files, resulting in a total of +7411/-1541 lines across 2 commits, demonstrating a strong focus on other work. Additionally, provided 2 approvals in reviews, maintaining a consistent activity pattern with engagement every day.\", \"2025-05-18T23:08:38.161Z\"]"
  ]
}