{
  "date_generated_for": "2025-02-25",
  "ai_news_elizaos_discord_md_2025-02-24": {
    "filename": "2025-02-24.md",
    "content": "# elizaOS Discord - 2025-02-24\n\n## Overall Discussion Highlights\n\n### ElizaOS Platform Updates\n- **Version 0.25.8 Released**: Odilitime announced the release of ElizaOS v0.25.8 with plugins moved out of the main codebase to a separate repository at https://github.com/elizaos-plugins/\n- **ElizaOS V2 Development**: Witch clarified that ElizaOS V2 codebase is being developed by Shaw with an expected release in early April or sooner\n- **Rebranding Progress**: The team is working on rebranding ai16z to ElizaOS, including consolidating X (Twitter) accounts by swapping the @elizaOS and @ai16zdao handles while maintaining followers\n- **Token Status**: The ai16z token will maintain the same contract address through the rebrand, with plans to promote the token and announce planned tokenomics after the rebrand is complete\n\n### Technical Discussions\n- **Memory Allocation Issues**: Multiple users reported JavaScript heap out of memory errors when using RAG knowledge, with solutions involving increasing Node.js memory limits using `NODE_OPTIONS=\"--max-old-space-size=8192\"`\n- **Embedding Model Problems**: Users experienced issues with embedding models for RAG knowledge, particularly with the BGE model not being found, with suggestions to use `text-embedding-ada-002` instead\n- **Plugin Architecture Changes**: Confusion about the new plugin architecture after plugins were moved out of the main ElizaOS repository, with some plugins accidentally removed from the registry\n- **L2 Development**: DorianD has been working on building an L2 for ElizaOS using Solana validators, proposing a system where ai16z tokens could be staked to run validator or RPC nodes\n- **Agent Memory Systems**: Hidden Forces raised questions about implementing functional memory systems that exist outside character JSON files, specifically for managing podcast episode data\n\n### Community Projects\n- **Instacart Agent**: Scooper shared their successful implementation of an Instacart agent built on Eliza that helps with meal planning and grocery ordering within budget constraints\n- **AI News Aggregator**: Jin reported progress on an AI news aggregator that collects historical data from X, Discord, GitHub, and markets, with summarization capabilities\n- **DegenSpartanAI Trading**: Community members discussed the performance of DegenSpartanAI, a trading AI agent in early development, with Osint providing detailed technical suggestions for improving its trading strategy\n- **Community Analysis Tools**: Jin mentioned plans to combine discord-summarizer and ai-news repositories to filter out noise in the community, find pain points, reward contributors, and create FAQ content for AI agents\n\n## Key Questions & Answers\n\n**Q: Where have the plugins been moved to after the latest update?**  \nA: They have been moved to https://github.com/elizaos-plugins/ (answered by mtbc)\n\n**Q: How can I fix the \"JavaScript heap out of memory\" error?**  \nA: Set NODE_OPTIONS=\"--max-old-space-size=8192\" or other memory size values (answered by boolkeys)\n\n**Q: How can I run multiple characters in one deployment?**  \nA: Use \"pnpm start \u2014characters=\"character1.json,character2.json,3.json\"\" (answered by boolkeys)\n\n**Q: How to fix the RAG knowledge base embedding model error?**  \nA: Set embeddingModel to 'text-embedding-ada-002' in your character config (answered by Sabochee)\n\n**Q: Is there a LinkedIn plugin available?**  \nA: There was a PR but it was a joke with no working code (answered by Odilitime)\n\n**Q: What does the Instacart agent do?**  \nA: You can order groceries through Instacart. It helps you meal plan a week of recipes and then order groceries. (answered by scooper)\n\n**Q: Can you give a price limit param for the meal plan?**  \nA: Yep, you can tell it your budget. (answered by scooper)\n\n**Q: Can anyone know about ElizaOS tokenomics?**  \nA: Tokenomics is in the #tokenomics channel but they're waiting for launchpad release before releasing the full tokenomics + future plans. (answered by witch)\n\n**Q: Is eliza official ai16z token?**  \nA: No, our 2 official tokens are ai16z (pending rebrand but same CA) and DegenAI. eliza is a different project we are aligned with, but not under our scope. (answered by Patt)\n\n**Q: In terms of X accounts we currently have - ai16zdao / ElizaOS / Eliza Studios. Which accounts are being consolidated?**  \nA: The plan is to exchange the @elizaOS handle with @ai16zdao, with support from X. (answered by accelxr)\n\n**Q: How do we make sure we know how to distinguish between devs committed and building for the long term and those looking to extract from Eliza community for a quick cash grab?**  \nA: Using a combination of Labs/Studios partnerships, builder chats, demo days, and ecosystem funding to promote quality projects. (answered by accelxr)\n\n## Community Help & Collaboration\n\n1. **Memory Allocation Solutions**:  \n   boolkeys helped Pleasures resolve JavaScript heap out of memory errors by providing the command to increase Node.js memory allocation: `export NODE_OPTIONS=\"--max-old-space-size=4096\"` with options for different memory sizes.\n\n2. **Embedding Model Troubleshooting**:  \n   Sabochee assisted Waqas Wahid with embedding model errors in RAG knowledge by suggesting the use of `text-embedding-ada-002` model in character config.\n\n3. **PostgreSQL Configuration**:  \n   P\u039eTE provided detailed instructions to the community on configuring PostgreSQL with ElizaOS, including correct URL format and schema location.\n\n4. **Trading Strategy Suggestions**:  \n   Osint (aka not_in_a_dao_ai) provided DegenSpartanAI developers with a detailed workflow proposal for improving trading strategies, including BTC range monitoring, using coinrotator.app, and trading on daily timeframes.\n\n5. **Plugin Registry Fix**:  \n   Odilitime identified a commit that accidentally removed the SQD plugin from the registry and promised to handle restoring it after ian | sqd.ai reported the issue.\n\n6. **Telegram Bot Troubleshooting**:  \n   Sipit suggested to Quang Vinh that they should revoke their Telegram bot API key and get a new one to resolve connection timeout issues.\n\n7. **Development Environment Issues**:  \n   yikesawjeez helped DorianD with serialization issues by suggesting trying Claude via \"npm install -g anthropic/claude-code\" and updating Cursor to version 3.7 for access to a new agent.\n\n## Action Items\n\n### Technical\n1. **Fix memory allocation issues with RAG knowledge** - Implement better memory management for large knowledge bases (Mentioned by Multiple users)\n2. **Restore accidentally removed plugins in registry** - Fix commit that removed multiple plugins including SQD (Mentioned by Odilitime)\n3. **Fix action validation in agent runtime** - Investigate why handlers execute despite validate returning false (Mentioned by Sabochee)\n4. **Add WebSocket support to direct client** - Implement WebSocket functionality for direct client (Mentioned by shaw)\n5. **Implement L2 for ElizaOS using Solana validators** - Based on the linked tokenomics model (Mentioned by DorianD)\n6. **Add more logging or evaluation capabilities for agents** - To provide feedback on plugins (Mentioned by DorianD)\n7. **Research methods to allow staked coins to be re-hypothecated** - For L2 node payments (Mentioned by DorianD)\n8. **Resolve serialization issues in the L2 implementation** (Mentioned by DorianD)\n9. **Investigate and resolve compromised Telegram channels** (Mentioned by irio)\n10. **Finalize X handle swap between @elizaOS and @ai16zdao** (Mentioned by accelxr)\n11. **Update token name on CMC, CG, CEXs** - When updating token metadata (Mentioned by accelxr)\n12. **Implement OpenGraph image previews for the AI news aggregator** - Replace individual profile pictures with OpenGraph previews (Mentioned by jin)\n13. **Crawl and reprocess last 60 days of news** - Gather and analyze historical news data (Mentioned by jin)\n14. **Merge upgraded AI news aggregator** - Complete and merge with historical aggregation and summarization features (Mentioned by jin)\n15. **Implement BTC price range monitoring** - For $85k-$99k short term, $73k-$109k broader range (Mentioned by Osint)\n16. **Add functionality to enter positions at lower part of BTC trading range** (Mentioned by Osint)\n17. **Integrate with tools like coinrotator.app** - For simplified trend analysis (Mentioned by Osint)\n18. **Implement daily timeframe trading strategy** (Mentioned by Osint)\n19. **Fix issue with API key configuration** - In Eliza agent kit starter (Mentioned by Syntronyx)\n20. **Investigate ARM64 support for Docker deployments** (Mentioned by \u2572\u239d\u29f9Nat'\u29f8\u23a0\u2571)\n21. **Review and merge translation corrections pull request** (Mentioned by Void)\n22. **Address repetitive posting behavior in Twitter agents** (Mentioned by artzy)\n23. **Implement functional memory systems outside character JSON files** - For accessing vector arrays at runtime to recall podcast episode data (Mentioned by Hidden Forces)\n24. **Develop stateful TEEs with proof generation and verification** - Building trusted execution environments that guarantee agent sovereignty (Mentioned by Wukong of Fire)\n\n### Documentation\n1. **Update character file format documentation** - Clarify how to specify clients and plugins in the new version (Mentioned by Multiple users)\n2. **Create guide for using PostgreSQL with ElizaOS** - Document proper setup process for PostgreSQL adapter (Mentioned by P\u039eTE)\n3. **Update tokenomics documentation** - After launchpad release (Mentioned by witch)\n4. **Create formal announcement introducing the rebrand** - With clear messaging about token contract address (Mentioned by accelxr)\n5. **Develop brand kit and presentation guidelines for ElizaOS** (Mentioned by accelxr)\n\n### Feature\n1. **Add LinkedIn client implementation** - Develop a working LinkedIn plugin (Mentioned by 0xConsole)\n2. **Improve embedding model options for RAG** - Add support for free embedding models (Mentioned by Waqas Wahid)\n3. **Consider adding shorting capability or inverse token trading** - For bearish markets (Mentioned by Patt)\n4. **Explore Hyperliquid as a trading platform** - For AI agent to gain exposure to more coins (Mentioned by Osint)\n5. **Consider multi-chain support beyond Solana** (Mentioned by Void)\n6. **Create desktop app wrapper for Eliza** - On Mac and Windows (Mentioned by AD)\n7. **Improve character generation to prevent repetitive posts** (Mentioned by artzy)\n8. **Consider VRM-to-spritesheet pipeline** - For creating game assets (Mentioned by jin)\n9. **Explore Solana L2 system for staking ai16z tokens** - To run validator/RPC nodes (Mentioned by DorianD)\n10. **Develop recurring demo day** - For showcasing quality projects (Mentioned by accelxr)\n11. **Create an agent that writes stylized memecoin reviews** - In the style of Pitchfork journalists (Mentioned by SmashAdams)\n12. **Explore EVM based wallet support for ETH/BASE** (Mentioned by Zeke)"
  },
  "ai_news_elizaos_discord_md_2025-02-23": {
    "filename": "2025-02-23.md",
    "content": "# elizaOS Discord - 2025-02-23\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Releases\n- **v0.25.8 Release**: Odilitime announced the release of v0.25.8, which moved plugins out of the main codebase\n- **ElizaOS V2 Codebase**: Shaw is developing a new V2 codebase with expected release in early April\n- **Plugin System Changes**: Multiple users noted the recent changes to the plugin architecture, with plugins being moved to separate repositories\n- **Technical Challenges**: Users reported issues with database integration (particularly Qdrant and PGVector), embedding model configurations, and API authentication with various LLM providers\n\n### Rebranding from ai16z to ElizaOS\n- **Token Contract Address**: Team members clarified that despite rebranding, the token contract address will remain unchanged\n- **Ticker Change**: Working with daos.fun to change the ticker while maintaining the same contract address\n- **Messaging Concerns**: Partners discussed the challenge of maintaining clear messaging during the transition period\n- **Timeline**: accelxr confirmed the rebrand is on track for midweek implementation, pending community feedback and logistics\n\n### Community Projects & Implementations\n- **Instacart Agent**: A community member (scooper) shared their successful implementation of an Instacart agent built using ElizaOS for meal planning and grocery ordering\n- **L2 Development**: DorianD is working on an L2 solution for ElizaOS using Solana validators, despite facing significant build errors\n- **Avalanche Integration**: yikesawjeez offered to implement something on Avalanche over the weekend\n- **Eliza Fighter Game**: Discussion about creating a fighting game with Eliza characters using a VRM-to-spritesheet pipeline\n- **Clank Tank Show**: Jin announced the premiere of \"Clank Tank\" (a show featuring AI projects) with plans for improvements\n\n### Tokenomics & Blockchain\n- **Liquidity Layer**: Focus on building a liquidity layer for AI16 SPL2022 token across projects rather than creating a true L1 blockchain\n- **Token Status**: Multiple clarifications that ai16z is an infrastructure token for the ElizaOS ecosystem, not merely a meme coin\n- **Mintable Status**: wlt provided documentation explaining why the token remains mintable\n- **Yield Generation**: Research into re-hypothecation of staked coins to generate yield for paying L2 nodes\n\n### AI Model Discussions\n- **Grok-3 Trading Bot Claims**: Skepticism about claims of a profitable trading bot created using Grok-3, with experienced members dismissing it as \"engagement farming\"\n- **Embedding Models**: Questions about free embedding models for testing purposes\n- **Memory Vector Size**: Technical discussions about changing default memory vector size from 384 to 768 for Qdrant database\n\n## Key Questions & Answers\n\n**Q: Why is minting authority not renounced on ai16z token?**  \nA: Documentation explains the rationale: https://elizaos.github.io/eliza/community/Notes/lore/#why-mintable-on-dexscreener (answered by wlt \ud83e\udde9)\n\n**Q: How does the upcoming rebrand affect the ai16z token?**  \nA: The contract address remains unchanged. Once the rebrand is complete, they will be able to promote the token and announce planned tokenomics. (answered by Patt)\n\n**Q: Is ai16z token more like a meme coin or an elizaos ai infrastructure ecosystem token?**  \nA: It's an ElizaOS infrastructure token. Started as a meme token (parody of a16z) but has evolved into the largest web3 AI framework. (answered by Spyros and witch)\n\n**Q: Do I need to convert ai16z token to ElisaOS token?**  \nA: No new contract address, no new token. No action needed from holders. (answered by Spyros)\n\n**Q: Why is my Hyperbolic API failing to authenticate in v0.25.6?**  \nA: It's likely an issue on Hyperbolic's side as the plugin code hasn't changed; you need a valid API key with credits in your account. (answered by Odilitime and AIFlow.ML)\n\n**Q: How do I give an agent access to a SQL database as knowledge?**  \nA: Integrate it with langchain SQL service using langchain_community.utilities SQLDatabase. (answered by Kren)\n\n**Q: Does Eliza send the full character context each time or does it vectorize the input?**  \nA: It sends samples from the character file, including randomly selected engagements from the DB; there's context trimming if it exceeds model limits. (answered by NoContext)\n\n**Q: Does direct client of Eliza support websocket?**  \nA: No, but they want to add it. (answered by shaw)\n\n**Q: Is the project creating an actual L1 blockchain?**  \nA: No, it's still the AI16 SPL2022 token, just functioning as a liquidity layer across projects. (answered by yikesawjeez)\n\n**Q: Are you planning to change up the setting for every episode of Clank Tank?**  \nA: No, they want to be consistent per season at least, but can still make light improvements. (answered by jin)\n\n## Community Help & Collaboration\n\n1. **Hyperbolic API Authentication**  \n   - Helper: Odilitime  \n   - Helpee: Slise  \n   - Context: Hyperbolic API authentication failing in v0.25.6  \n   - Resolution: Identified it was a Hyperbolic issue, suggested switching to Redpill model which worked\n\n2. **Character Context Understanding**  \n   - Helper: NoContext  \n   - Helpee: devilsadvocate.sol  \n   - Context: Understanding how character context is sent to LLM  \n   - Resolution: Explained that samples from character file and random DB engagements are used, with context trimming if needed\n\n3. **Memory Allocation Error**  \n   - Helper: boolkeys  \n   - Helpee: domanodes  \n   - Context: JavaScript heap out of memory error  \n   - Resolution: Suggested increasing memory allocation with NODE_OPTIONS=\"--max-old-space-size=4096\" and provided options for different memory sizes\n\n4. **Plugin Registry Issue**  \n   - Helper: Odilitime  \n   - Helpee: ian  \n   - Context: SQD plugin missing from registry after being merged  \n   - Resolution: Identified the commit that accidentally removed multiple plugins and offered to handle restoring them\n\n5. **RAG Configuration**  \n   - Helper: boolkeys  \n   - Helpee: 9000  \n   - Context: How to use knowledge/RAG with Eliza  \n   - Resolution: Provided detailed documentation on RAG configuration, knowledge types, and file path setup\n\n6. **Nous Research Relationship**  \n   - Helper: jin  \n   - Helpee: Community  \n   - Context: Clarifying relationship with Nous Research  \n   - Resolution: Jin spoke with John and another Nous representative, confirmed that labeling ElizaOS as \"enemies\" didn't reflect the organization's view and they're on good terms\n\n7. **Rebranding Strategy**  \n   - Helper: accelxr  \n   - Helpee: Community  \n   - Context: Rebranding strategy and timeline  \n   - Resolution: Shared rebrand designs and confirmed midweek timeline for implementation, noting ticker change is outside their control\n\n## Action Items\n\n### Technical\n- Continue development of ElizaOS V2 codebase for early April release (mentioned by witch)\n- Implement token ticker change while maintaining the same contract address (mentioned by Patt)\n- Fix validation in action handlers to properly respect return values (mentioned by Sabochee)\n- Add websocket support to direct client (mentioned by shaw)\n- Fix memory vector size configuration for different embedding dimensions (mentioned by Lucas Fernandes)\n- Fix Twitter client ACTION_TIMELINE_TYPE=following setting (mentioned by Slise)\n- Fix \"Invalid array length\" error in knowledge processing (mentioned by Dean)\n- Implement liquidity layer on Avalanche over the weekend (mentioned by yikesawjeez)\n- Continue development of L2 for ElizaOS using Solana validators (mentioned by DorianD)\n- Implement logging/evaluation system for plugins (mentioned by DorianD)\n- Research re-hypothecation of staked coins (mentioned by DorianD)\n- Make discord-summarizer loop more autonomous/easier to deploy (mentioned by jin)\n- Improve AI/writers room for Clank Tank (mentioned by jin)\n\n### Documentation\n- Provide complete tokenomics documentation after launchpad release (mentioned by witch)\n- Update memory configuration documentation (mentioned by Lucas Fernandes)\n- Create guide for custom database adapters (mentioned by Lucas Fernandes)\n- Add examples for actions implementation (mentioned by domanodes)\n- Improve ElizaOS docs (mentioned by jin)\n- Ensure clear messaging during rebranding that ai16z ticker is ElizaOS (mentioned by HoneyBadger)\n- Change DEX screener banner to ElizaOS (mentioned by HoneyBadger)\n\n### Feature\n- Consider multi-chain support for the token beyond Solana (mentioned by Void)\n- Develop agent launch platform powered by Eliza with fee sharing back to protocol (mentioned by Zeke)\n- Open source the Instacart plugin for community use (mentioned by scooper)\n- Implement LinkedIn client (mentioned by 0xConsole)\n- Support for local embedding models (mentioned by Waqas Wahid)\n- Make Clank Tank judges less agreeable/include rejections (mentioned by HoneyBadger)\n- Develop Eliza plugin (Nethermind working on eliza-chaoschain-plugin) (mentioned by mat)\n- Explore VRM-to-spritesheet pipeline for Eliza Fighter game (mentioned by jin)\n- Prepare something for partners to help pick next episode pitches (mentioned by jin)"
  },
  "ai_news_elizaos_discord_md_2025-02-22": {
    "filename": "2025-02-22.md",
    "content": "# elizaOS Discord - 2025-02-22\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **V2 Development Progress**: Development appears ahead of schedule with significant progress made in recent weeks under Shaw's direction. The team is working on integrating components, polishing, and handling V1 migration.\n- **Documentation Improvements**: Jin is working on improving ElizaOS documentation and plans to make the discord-summarizer tool more autonomous and easier to deploy.\n- **Agent Registry Concept**: DorianD introduced the concept of an Eliza Agent Registry and shared a document with ideas for how agents can use DAO/coin functionality.\n- **GitHub Repository**: A repository for an Eliza plugin (eliza-chaoschain-plugin) was shared by a community member.\n\n### Technical Challenges\n- **Qdrant Adapter Issues**: Several users encountered problems with the Qdrant adapter, which lacks proper memory management implementation. Lucas Fernandes had to fork and modify the adapter to implement missing functionality.\n- **RAG Configuration**: Users discussed RAG mode configuration, sharing JSON snippets for setting up knowledge files and directories.\n- **Client Integration Problems**: Multiple users reported issues with client-specific implementations, particularly with Telegram bots and image generation.\n- **Context Management**: Discussions about how context is managed between messages, with clarification that terminal client doesn't maintain context but deployed clients do.\n\n### Token & Ecosystem\n- **ai16z Token Transition**: Confirmation that ai16z token is transitioning from a meme coin to an infrastructure token for the ElizaOS AI ecosystem, with no new token or change to the contract address.\n- **Token Design Questions**: Discussion about the mintable nature of the token, with references to documentation explaining this design choice.\n- **Liquidity Concerns**: Questions were raised about AI16z DAO selling tribute tokens through single-sided liquidity pools, with concerns about transparency.\n- **Cross-Chain Implementation**: A user offered to implement something on the Avalanche blockchain over the weekend, mentioning interest in checking whether \"avago\" supports Solana integration.\n\n### Content Production\n- **Clank Tank Launch**: Preparation for the premiere of \"Clank Tank\" - a new AI agent show, with the team working under time pressure to finalize audio elements and transitions.\n- **Production Elements**: Detailed discussion about sound effects, music tracks, transition elements, credits, and bumpers/commercials for the video production.\n\n### Community Concerns\n- **Platform Fragmentation**: Community members expressed concerns about fragmentation across multiple platforms (Discord, Telegram, ElizaOS Discord, Eliza Studios Discord), noting this could hinder knowledge sharing and collaboration.\n\n## Key Questions & Answers\n\n### Technical Implementation\n- **Q**: How do I give my agent access to a SQL database as knowledge?  \n  **A**: Use langchain_community.utilities SQLDatabase (answered by Kren)\n\n- **Q**: Does Eliza send the full character context each time or vectorize it?  \n  **A**: It uses samples and randomly selected data from the character file, with context trimming if needed (answered by NoContext)\n\n- **Q**: How is the EdriziAI character built? How is knowledge being provided?  \n  **A**: Use ragKnowledge: true in settings and specify knowledge files in the character JSON (answered by Sipit)\n\n- **Q**: Can you add more than one knowledge file?  \n  **A**: Yes, you can add multiple files or specify a directory (answered by Sipit)\n\n- **Q**: How can I keep track of conversation context?  \n  **A**: It keeps conversation context when deployed to clients like Slack/Discord/Twitter, terminal treats each message as new (answered by Kren)\n\n### Token & Ecosystem\n- **Q**: Is ai16z token more like a meme coin or an ElizaOS AI infrastructure ecosystem token?  \n  **A**: Started as a meme token parody of a16z, now it's the largest web3 AI framework and still growing (answered by witch)\n\n- **Q**: How to convert ai16z token to ElizaOS token? Is any action needed from holders?  \n  **A**: No new CA, no new token (answered by Spyros and SotoAlt | BOSSU)\n\n- **Q**: Why is minting authority not renounced on ai16z token?  \n  **A**: They've addressed this before in documentation: https://elizaos.github.io/eliza/community/Notes/lore/#why-mintable-on-dexscreener (answered by wlt \ud83e\udde9)\n\n- **Q**: Is the 1B supply fixed?  \n  **A**: Can't say fixed as that wouldn't be correct, but it has remained 1B (answered by Osint)\n\n### Content Production\n- **Q**: Are you planning to change up the setting for every episode [of Clank Tank]?  \n  **A**: No, want to be consistent per season at least, but can still do light improvements (answered by jin)\n\n- **Q**: What kind of transitions are needed?  \n  **A**: Simpler transitions with less going on, white on black text preferred (answered by jin)\n\n## Community Help & Collaboration\n\n1. **RAG Configuration Support**:\n   - Sipit helped Julian Neuss with setting up RAG mode for knowledge files by providing JSON configuration examples and advising to use eliza git repo instead of eliza-starter.\n   - Sipit also assisted AD with adding multiple knowledge files by providing JSON configuration for both multiple files and directory-based approaches.\n\n2. **Context Management Clarification**:\n   - Kren helped Lucas Fernandes understand how conversation context works between messages, explaining that terminal client doesn't maintain context but deployed clients do.\n   - NoContext explained to devilsadvocate.sol how context is passed to models, clarifying that random samples from character file are used and context trimming occurs.\n\n3. **Token Documentation**:\n   - wlt \ud83e\udde9 helped Kenshiro understand why minting authority wasn't renounced on ai16z token by providing documentation link explaining the design choice.\n   - Multiple users collaborated to clarify that there's no new token or contract address during the transition to ElizaOS.\n\n4. **Audio Production Collaboration**:\n   - boom provided fishai/jin with multiple music tracks, sound effects, and transition elements for the Clank Tank video production.\n   - The team collaborated in voice chat to finalize the edit, with boom emphasizing that \"music first\" is the proper workflow as \"music gives length, length gives markers, markers makes cuts easy.\"\n\n5. **Plugin Development**:\n   - mat shared a GitHub repository for eliza-chaoschain-plugin to help the community with Eliza plugin development.\n   - DorianD shared a document with ideas for agent DAO/coin integration and introduced the Eliza Agent Registry concept.\n\n## Action Items\n\n### Technical Tasks\n1. **Fix Qdrant adapter** to properly implement memory management functions (Mentioned by Lucas Fernandes)\n2. **Create embedding configs for Gemini** (Mentioned by Lucas Fernandes)\n3. **Implement coordinator for main LLM requests** to manage agent queue (Mentioned by parksthecoder)\n4. **Fix image generation with Twitter bot** (media parameter missing error) (Mentioned by Himanshu Singh)\n5. **Make discord-summarizer tool more autonomous and easier to deploy** (Mentioned by jin)\n6. **Review and potentially join ECMA committee** for AI agent communication standards (Mentioned by DorianD)\n7. **Create zip files of sound effects and transition cuts** for Clank Tank (Mentioned by jin)\n8. **Re-render credits without M3 token references** (Mentioned by jin)\n9. **Add bumpers/commercials between pitches** (Mentioned by jin)\n10. **Finalize video edit and upload** for scheduled premiere (Mentioned by jin)\n11. **Add appropriate music and sound effects** to transitions (Mentioned by boom)\n12. **Implement something on Avalanche blockchain** over the weekend (Mentioned by yikesawjeez)\n13. **Develop AI agent for managing liquidity ranges** based on pre-defined metrics (Mentioned by Aadjee)\n14. **Tool development to transform any API to an AI agent** without coding (Mentioned by npizza)\n15. **Address concerns about tribute token sales** (Mentioned by dral)\n\n### Documentation Needs\n1. **Update memory management documentation** to specify where MemoryConfig should be placed (Mentioned by Lucas Fernandes)\n2. **Add \"where to place snippet\" hints** in documentation (Mentioned by Lucas Fernandes)\n3. **Create examples for building RAGs on Eliza** (Mentioned by Lucas Fernandes)\n4. **Improve ElizaOS documentation** (Mentioned by jin)\n5. **Create list of all needed transitions** for video production (Mentioned by boom)\n6. **Update documentation site** with latest information (Mentioned by BOSSU)\n7. **Clarify token status** during transition to ElizaOS (Mentioned by Multiple users)\n\n### Feature Requests\n1. **Add support for WhatsApp Business client** (Mentioned by sillysurry)\n2. **Add ability to reload RAG knowledge** without restarting agent (Mentioned by Sipit)\n3. **Support for official Twitter API** instead of scraper (Mentioned by fiend)\n4. **Develop Eliza Agent Registry** (Mentioned by DorianD)\n5. **Improve Clank Tank production quality** (Mentioned by jin)\n6. **Website redesign for DegenAI v2** (Mentioned by Joe2th)\n7. **Database updates and reductions in inference costs** for DegenAI (Mentioned by Joe2th)\n8. **Expanding data layer** to include more sources and API routes for integration into data hub (Mentioned by Joe2th)"
  },
  "ai_news_elizaos_daily_json_2025-02-24": {
    "filename": "2025-02-24.json",
    "content": {
      "type": "elizaosDailySummary",
      "title": "Daily Report - 2025-02-24",
      "categories": [
        {
          "title": "Recent Updates to Eliza Project",
          "content": [
            {
              "text": "The Eliza project has seen numerous updates across various areas including bug fixes, feature additions, refactoring, and documentation improvements.\n\nBug fixes include handling short text items in knowledge processing, fixing Twitter client embedding dimensions, resolving social vitest issues, addressing pglite & migrations problems, setting up dimensions before starting clients, fixing extensions and migrations, handling speaker removal in Twitter spaces, and various small Twitter-related fixes. Documentation fixes addressed formatting issues in plugins.md and corrected typographical errors.\n\nFeature additions include adding database and plugin adapter types to core types, adding participant error handling, implementing space actions, adding agent server options with middleware settings, adding the 'agent' table and renaming 'user' to 'entity' table with multi-tenancy support, and adding functionality to check if plugins are installed with result display.\n\nRefactoring efforts reorganized API routes into a file-based structure, cleaned up the server, refactored the plugin-local-ai component, and improved memory queries, knowledge metadata, and browser support.\n\nOther changes include updating the Korean README and merging develop into main for the 0.25.8 release.",
              "sources": [
                "https://github.com/elizaOS/eliza/pull/3652",
                "https://github.com/elizaOS/eliza/pull/3651",
                "https://github.com/elizaOS/eliza/pull/3649",
                "https://github.com/elizaOS/eliza/pull/3640",
                "https://github.com/elizaOS/eliza/pull/3625",
                "https://github.com/elizaOS/eliza/pull/3622",
                "https://github.com/elizaOS/eliza/pull/3522",
                "https://github.com/elizaOS/eliza/pull/3672",
                "https://github.com/elizaOS/eliza/pull/3671",
                "https://github.com/elizaOS/eliza/pull/3670",
                "https://github.com/elizaOS/eliza/pull/3668",
                "https://github.com/elizaOS/eliza/pull/3667",
                "https://github.com/elizaOS/eliza/pull/3665",
                "https://github.com/elizaOS/eliza/pull/3663",
                "https://github.com/elizaOS/eliza/pull/3662",
                "https://github.com/elizaOS/eliza/pull/3660",
                "https://github.com/elizaOS/eliza/pull/3659",
                "https://github.com/elizaOS/eliza/pull/3656",
                "https://github.com/elizaOS/eliza/pull/3655",
                "https://github.com/elizaOS/eliza/pull/3648",
                "https://github.com/elizaOS/eliza/pull/3637",
                "https://github.com/elizaOS/eliza/pull/3606"
              ],
              "images": [],
              "videos": []
            }
          ],
          "topic": "completed_items"
        },
        {
          "title": "Recent Twitter Activity from dankvr and shawmakesmagic",
          "content": [
            {
              "text": "The users share thoughts on various tech and cultural topics. Dankvr discusses potential health concerns about technology similar to plastics, shares philosophical quotes about personal growth, recommends DAO experts, and envisions a future with open-source humanoid robots maintaining gardens. Meanwhile, shawmakesmagic discusses AI alignment transparency, responds to brand confusion with Nous models, showcases a new brand aesthetic, comments on memecoins and cryptocurrency market trends, and engages with followers on various topics.",
              "sources": [
                "https://twitter.com/dankvr/status/1894067730539565438",
                "https://twitter.com/dankvr/status/1894063926511378666",
                "https://twitter.com/dankvr/status/1894059054806262185",
                "https://twitter.com/dankvr/status/1893820466709647747",
                "https://twitter.com/shawmakesmagic/status/1894157551362871428",
                "https://twitter.com/shawmakesmagic/status/1893948184344359294",
                "https://twitter.com/shawmakesmagic/status/1893917952753229877",
                "https://twitter.com/shawmakesmagic/status/1893916371366396020",
                "https://twitter.com/shawmakesmagic/status/1893909777077481719",
                "https://twitter.com/shawmakesmagic/status/1893898613106868568",
                "https://twitter.com/shawmakesmagic/status/1893897286041940130",
                "https://twitter.com/shawmakesmagic/status/1893886291755901420"
              ],
              "images": [
                "https://pbs.twimg.com/media/GkkRFPbWYAA32sW.jpg",
                "https://pbs.twimg.com/media/GkinntjawAA8woy.jpg",
                "https://pbs.twimg.com/media/Gkinw_BWQAAhwNV.jpg",
                "https://pbs.twimg.com/media/Gkin0r9XIAATzhx.jpg",
                "https://pbs.twimg.com/media/GkiK0YYXEAAQ4G7.jpg"
              ],
              "videos": []
            },
            {
              "text": "On AI and technology, shawmakesmagic argues that transparency is the solution to AI alignment, noting that AI models inherit biases from their training data, particularly media sources. They also clarify being fans of Nous models when responding to apparent brand confusion. Dankvr speculates about potential health concerns with technology that might parallel issues with plastics, suggesting testing with routers.",
              "sources": [
                "https://twitter.com/dankvr/status/1894067730539565438",
                "https://twitter.com/shawmakesmagic/status/1894157551362871428",
                "https://twitter.com/shawmakesmagic/status/1893897286041940130"
              ],
              "images": [],
              "videos": []
            },
            {
              "text": "Both users share content related to cryptocurrency and Web3. Shawmakesmagic comments on memecoins with \"I should launch a memecoin\" and discusses the potential market impact when Kanye releases his coin. Dankvr recommends experts in DAOs (Decentralized Autonomous Organizations), mentioning @mrjasonchoi, @singularityhack, and @owocki.",
              "sources": [
                "https://twitter.com/dankvr/status/1894059054806262185",
                "https://twitter.com/shawmakesmagic/status/1893917952753229877",
                "https://twitter.com/shawmakesmagic/status/1893898613106868568"
              ],
              "images": [],
              "videos": []
            }
          ],
          "topic": "tweet"
        },
        {
          "title": "Recent Pull Requests in the elizaOS/eliza Repository",
          "content": [
            {
              "text": "Several new features and improvements have been proposed to the elizaOS/eliza repository through recent pull requests:\n\n1. A new storage plugin called 'storacha' has been introduced by fforbeck in PR #3657.\n\n2. Agent server options with middleware settings have been added by v1xingyue in PR #3648, enhancing server configuration capabilities.\n\n3. The UserRapport feature (PR #3647) by nusk0 aims to improve Twitter interactions with more tailored responses and better rapport building with users.\n\n4. A refactoring of API routes into a file-based structure has been implemented by wtfsayo in PR #3651, likely improving code organization and maintainability.\n\n5. X4ndar has submitted a pull request (#3666) titled 'Stable', though specific details about this PR are not provided in the source.\n\n6. A refactoring of the local-ai plugin has been completed by AIFlowML in PR #3663, marked as 'plugin-local-ai-final'.",
              "sources": [
                "https://github.com/elizaOS/eliza/pull/3657",
                "https://github.com/elizaOS/eliza/pull/3648",
                "https://github.com/elizaOS/eliza/pull/3647",
                "https://github.com/elizaOS/eliza/pull/3651",
                "https://github.com/elizaOS/eliza/pull/3666",
                "https://github.com/elizaOS/eliza/pull/3663"
              ],
              "images": [
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3657",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3648",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3647",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3651",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3666",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3663"
              ],
              "videos": []
            }
          ],
          "topic": "pull_request"
        },
        {
          "title": "ElizaOS GitHub Activity Update",
          "content": [
            {
              "text": "The elizaos/eliza repository showed increased activity over a two-day period. From February 24-25, 2025, there were 10 new PRs with 7 merged and 16 active contributors. Activity increased the following day (February 25-26, 2025) with 13 new PRs, 15 merged PRs, 2 new issues, and 17 active contributors. Overall, the project maintained strong contributor engagement with a slight growth in participation and significantly higher PR merge rate on the second day.",
              "sources": [
                0,
                1
              ],
              "images": [],
              "videos": []
            }
          ],
          "topic": "github_summary"
        },
        {
          "title": "Top contributors for elizaOS/eliza",
          "content": [
            {
              "text": "The provided sources mention 'Top contributors for elizaOS/eliza' but do not provide any specific details about who these contributors are or their contributions to the project. Without additional information, it's not possible to generate a detailed summary about the individual contributors, their roles, or the nature of their contributions to the elizaOS/eliza project.",
              "sources": [
                "Top contributors for elizaOS/eliza"
              ],
              "images": [],
              "videos": []
            }
          ],
          "topic": "contributors"
        },
        {
          "title": "Docker file issue: Invalid cachestore",
          "content": [
            {
              "text": "GitHub issue #3661 was opened by user avdheshcharjan regarding a Docker file issue with an invalid cachestore in the elizaOS/eliza repository. The specific details of the issue would require viewing the full content on GitHub.",
              "sources": [
                "https://github.com/elizaOS/eliza/issues/3661"
              ],
              "images": [
                "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/3661"
              ],
              "videos": []
            }
          ],
          "topic": "issue"
        }
      ],
      "date": 1740355200
    }
  },
  "ai_news_elizaos_daily_md_2025-02-24": {
    "filename": "2025-02-24.md",
    "content": "# Recent Updates to Eliza Project\n\n## Bug Fixes\n- Handled short text items in knowledge processing\n- Fixed Twitter client embedding dimensions\n- Resolved social vitest issues\n- Addressed pglite & migrations problems\n- Set up dimensions before starting clients\n- Fixed extensions and migrations\n- Handled speaker removal in Twitter spaces\n- Various small Twitter-related fixes\n- Fixed formatting issues in plugins.md\n- Corrected typographical errors\n\n## Feature Additions\n- Added database and plugin adapter types to core types\n- Added participant error handling\n- Implemented space actions\n- Added agent server options with middleware settings\n- Added 'agent' table and renamed 'user' to 'entity' table with multi-tenancy support\n- Added functionality to check if plugins are installed with result display\n\n## Refactoring\n- Reorganized API routes into a file-based structure\n- Cleaned up the server\n- Refactored the plugin-local-ai component\n- Improved memory queries, knowledge metadata, and browser support\n\n## Other Changes\n- Updated the Korean README\n- Merged develop into main for the 0.25.8 release\n\n# Recent Twitter Activity\n\n## Dankvr's Posts\n- Discussed potential health concerns about technology similar to plastics\n- Shared philosophical quotes about personal growth\n- Recommended DAO experts including @mrjasonchoi, @singularityhack, and @owocki\n- Envisioned a future with open-source humanoid robots maintaining gardens\n\n## Shawmakesmagic's Posts\n- Discussed AI alignment transparency and model biases from training data\n- Responded to brand confusion with Nous models\n- Showcased a new brand aesthetic\n- Commented on memecoins and cryptocurrency market trends\n- Engaged with followers on various topics\n\n# Recent Pull Requests in the elizaOS/eliza Repository\n\n## New Features and Improvements\n- New 'storacha' storage plugin introduced by fforbeck\n- Agent server options with middleware settings added by v1xingyue\n- UserRapport feature by nusk0 to improve Twitter interactions\n- Refactored API routes into a file-based structure by wtfsayo\n- 'Stable' pull request submitted by X4ndar\n- Refactored local-ai plugin completed by AIFlowML\n\n# ElizaOS GitHub Activity Update\n\n## Activity Metrics\n- February 24-25: 10 new PRs, 7 merged PRs, 16 active contributors\n- February 25-26: 13 new PRs, 15 merged PRs, 2 new issues, 17 active contributors\n- Overall strong contributor engagement with growth in participation\n- Higher PR merge rate on the second day\n\n# Docker File Issue\n- Issue #3661 opened by avdheshcharjan regarding an invalid cachestore"
  },
  "ai_news_elizaos_daily_discord_json_2025-02-24": {
    "filename": "2025-02-24.json",
    "content": {
      "server": "elizaOS",
      "title": "elizaOS Discord - 2025-02-24",
      "date": 1740355200,
      "stats": {
        "totalMessages": 757,
        "totalUsers": 157
      },
      "categories": [
        {
          "channelId": "1253563209462448241",
          "channelName": "discussion",
          "summary": "# Analysis of \"discussion\" Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around ElizaOS, an AI agent platform, and its associated token ai16z. Key technical discussions include:\n\n- A user (Syntronyx) reported issues with API key configuration in the Eliza agent kit starter, unable to get the system to read their OpenAI API key.\n- Odilitime announced release v0.25.8 of Eliza with plugins moved out of the main codebase.\n- Scooper shared their successful implementation of an Instacart agent built on Eliza that helps with meal planning and grocery ordering within budget constraints.\n- Witch clarified that ElizaOS V2 codebase is being developed by Shaw with an expected release in early April or sooner.\n- A user reported issues with running Eliza via Docker on ARM64 (Ampere) servers due to missing module support.\n- Artzy described problems with their agent's Twitter posts being repetitive despite various attempts at improving the character configuration.\n- Void submitted a pull request for translation corrections to the Eliza repository.\n- There was discussion about the upcoming rebrand of the ai16z token while maintaining the same contract address.\n\n## 2. FAQ\nQ: Can someone give me access to agent dev school? I'm getting error codes that it's not reading the API key. (asked by Syntronyx) A: See if grabbing it from #agent-dev-school does the trick (answered by Patt)\nQ: How does the upcoming rebrand affect the ai16z token? (asked by Octavian69) A: Once the rebrand is complete we will once again be able to promote the token and announce planned tokenomics. (answered by Patt)\nQ: What does the Instacart agent do? (asked by HoneyBadger) A: You can order groceries through Instacart. It helps you meal plan a week of recipes and then order groceries. (answered by scooper)\nQ: Can you give a price limit param for the meal plan? (asked by HoneyBadger) A: Yep, you can tell it your budget. (answered by scooper)\nQ: Can anyone know about ElizaOS tokenomics? (asked by 0xmujahid) A: Tokenomics is in the #tokenomics channel but they're waiting for launchpad release before releasing the full tokenomics + future plans. (answered by witch)\nQ: What is the ai16z token and the project about? (asked by Wonderland89) A: Take a look at the elizaOS website... the link is in #start-here (answered by Osint)\nQ: Is eliza official ai16z token? (asked by OnO) A: No, our 2 official tokens are ai16z (pending rebrand but same CA) and DegenAI. eliza is a different project we are aligned with, but not under our scope. (answered by Patt)\nQ: Is it possible to run Eliza via docker on a ARM64 (Amphere) server? (asked by \u2572\u239d\u29f9Nat'\u29f8\u23a0\u2571) A: Check #dev-support (answered by SotoAlt | BOSSU)\nQ: Do you know if there's an EVM based wallet for ETH / BASE? (asked by Zeke) A: I don't think so but good question, I relayed the question. (answered by Patt)\n\n## 3. Help Interactions\nHelper: Patt | Helpee: Syntronyx | Context: User having issues with API key configuration in Eliza agent kit | Resolution: Directed user to the agent-dev-school channel for proper access\nHelper: Odilitime | Helpee: Community | Context: Plugins integration in Eliza | Resolution: Released version 0.25.8 with plugins moved out of the main codebase\nHelper: scooper | Helpee: HoneyBadger | Context: Questions about Instacart agent capabilities | Resolution: Explained functionality including meal planning and budget constraints\nHelper: witch | Helpee: 0xmujahid | Context: Confusion about tokenomics and V2 release | Resolution: Clarified that ElizaOS V2 is being worked on by Shaw with expected release timeline and tokenomics information location\nHelper: Patt | Helpee: Zeke | Context: User looking for wallet address to give fees back to Eliza protocol | Resolution: Provided the official daos.fun address\nHelper: SotoAlt | BOSSU | Helpee: \u2572\u239d\u29f9Nat'\u29f8\u23a0\u2571 | Context: Issues running Eliza on ARM64 server | Resolution: Directed user to dev-support channel\n\n## 4. Action Items\nTechnical: Fix issue with API key configuration in Eliza agent kit starter | Mentioned By: Syntronyx\nTechnical: Investigate ARM64 support for Docker deployments | Mentioned By: \u2572\u239d\u29f9Nat'\u29f8\u23a0\u2571\nTechnical: Review and merge translation corrections pull request | Mentioned By: Void\nTechnical: Address repetitive posting behavior in Twitter agents | Mentioned By: artzy\nTechnical: Explore EVM based wallet support for ETH/BASE | Mentioned By: Zeke\nDocumentation: Update tokenomics documentation after launchpad release | Mentioned By: witch\nFeature: Consider multi-chain support beyond Solana | Mentioned By: Void\nFeature: Create desktop app wrapper for Eliza on Mac and Windows | Mentioned By: AD\nFeature: Improve character generation to prevent repetitive posts | Mentioned By: artzy",
          "messageCount": 232,
          "userCount": 76
        },
        {
          "channelId": "1300025221834739744",
          "channelName": "\ud83d\udcbb-coders",
          "summary": "# Analysis of \ud83d\udcbb-coders Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around issues with the latest ElizaOS update, which moved plugins out of the main repository. Users are experiencing various technical problems including memory allocation errors, embedding model issues with RAG knowledge, client configuration challenges, and plugin integration difficulties. Key discussions include:\n\n- Memory allocation errors when using RAG knowledge, with suggestions to increase Node.js memory limits using `NODE_OPTIONS=\"--max-old-space-size=8192\"`\n- Confusion about the new plugin architecture after plugins were moved out of the main ElizaOS repository\n- Issues with embedding models for RAG knowledge, particularly with the BGE model not being found\n- Problems with client configuration in character files after the update changed how clients are specified\n- Questions about action validation in the agent runtime, with users noting that handlers are being executed despite validation returning false\n- Challenges connecting to external services like Twitter, Telegram, and Gaia\n\nSeveral community members provided solutions, including using specific embedding models like `text-embedding-ada-002`, setting proper memory limits, and updating character configuration files to match the new format.\n\n## 2. FAQ\nQ: Where have the plugins been moved to after the latest update? (asked by ernest) A: They have been moved to https://github.com/elizaos-plugins/ (answered by mtbc)\nQ: How can I fix the \"JavaScript heap out of memory\" error? (asked by Pleasures) A: Set NODE_OPTIONS=\"--max-old-space-size=8192\" or other memory size values (answered by boolkeys)\nQ: What embedding model can I use for testing that's free? (asked by Waqas Wahid) A: Unanswered\nQ: How can I set a directory as runtime knowledge? (asked by Toby) A: Unanswered\nQ: What is the role of validate in actions if handlers execute despite validate returning false? (asked by Sabochee) A: Unanswered\nQ: How to specify clients in the new version of ElizaOS? (asked by Acul) A: Unanswered\nQ: How can I run multiple characters in one deployment? (asked by dereksidi) A: Use \"pnpm start \u2014characters=\"character1.json,character2.json,3.json\"\" (answered by boolkeys)\nQ: How to fix the RAG knowledge base embedding model error? (asked by Sabochee) A: Set embeddingModel to 'text-embedding-ada-002' in your character config (answered by Sabochee)\nQ: Is there a LinkedIn plugin available? (asked by 0xConsole) A: There was a PR but it was a joke with no working code (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: boolkeys | Helpee: Pleasures | Context: JavaScript heap out of memory error | Resolution: Provided command to increase Node.js memory allocation: export NODE_OPTIONS=\"--max-old-space-size=4096\" with options for different memory sizes\nHelper: Sabochee | Helpee: Waqas Wahid | Context: Embedding model error with RAG knowledge | Resolution: Suggested using text-embedding-ada-002 model in character config\nHelper: Odilitime | Helpee: ian | sqd.ai | Context: SQD plugin missing from registry after being merged | Resolution: Identified the commit that accidentally removed it and promised to handle restoring it\nHelper: P\u039eTE | Helpee: Community | Context: Setting up PostgreSQL with ElizaOS | Resolution: Provided detailed instructions on configuring PostgreSQL, including correct URL format and schema location\nHelper: Sipit | Helpee: Quang Vinh | Context: Telegram bot API connection timeout | Resolution: Suggested revoking the bot API key and getting a new one\n\n## 4. Action Items\nTechnical: Fix memory allocation issues with RAG knowledge | Description: Implement better memory management for large knowledge bases | Mentioned By: Multiple users\nTechnical: Restore accidentally removed plugins in registry | Description: Fix commit that removed multiple plugins including SQD | Mentioned By: Odilitime\nTechnical: Fix action validation in agent runtime | Description: Investigate why handlers execute despite validate returning false | Mentioned By: Sabochee\nTechnical: Add WebSocket support to direct client | Description: Implement WebSocket functionality for direct client | Mentioned By: shaw\nDocumentation: Update character file format documentation | Description: Clarify how to specify clients and plugins in the new version | Mentioned By: Multiple users\nDocumentation: Create guide for using PostgreSQL with ElizaOS | Description: Document proper setup process for PostgreSQL adapter | Mentioned By: P\u039eTE\nFeature: Add LinkedIn client implementation | Description: Develop a working LinkedIn plugin | Mentioned By: 0xConsole\nFeature: Improve embedding model options for RAG | Description: Add support for free embedding models | Mentioned By: Waqas Wahid",
          "messageCount": 202,
          "userCount": 58
        },
        {
          "channelId": "1308149076893630555",
          "channelName": "spartan_holders",
          "summary": "# Analysis of \"spartan_holders\" Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around DegenSpartanAI, a trading AI agent that appears to be in early development stages. Community members express mixed sentiments about its current performance, with some showing frustration over its trading results while others remain optimistic. Osint (aka not_in_a_dao_ai) provides detailed technical suggestions for improving the AI's trading strategy, including monitoring BTC price movements across different timeframes, entering positions at the lower part of BTC's trading range, and utilizing specific tools like coinrotator.app. They suggest implementing a workflow that considers BTC's price ranges ($85k-$99k and $73k-$109k), focuses on daily timeframes, and potentially uses platforms like Hyperliquid for trading exposure. The discussion highlights the challenges of developing effective trading AI in cryptocurrency markets and suggests that simplifying concepts through price change analysis might be beneficial if the AI cannot yet perform in-depth analysis.\n\n## 2. FAQ\nQ: Does Degen have any tools available to express bearishness? (asked by Patt) A: Unanswered\nQ: Would inverse tokens or perps be useful for the AI in bearish conditions? (asked by Patt) A: Unanswered\n\n## 3. Help Interactions\nHelper: Osint (aka not_in_a_dao_ai) | Helpee: DegenSpartanAI developers | Context: Providing trading strategy suggestions for the AI | Resolution: Detailed workflow proposal including BTC range monitoring, using coinrotator.app, and trading on daily timeframes\n\n## 4. Action Items\nType: Technical | Description: Implement BTC price range monitoring ($85k-$99k short term, $73k-$109k broader range) for trade entry timing | Mentioned By: Osint (aka not_in_a_dao_ai)\nType: Technical | Description: Add functionality to enter positions at lower part of BTC trading range | Mentioned By: Osint (aka not_in_a_dao_ai)\nType: Technical | Description: Integrate with tools like coinrotator.app for simplified trend analysis | Mentioned By: Osint (aka not_in_a_dao_ai)\nType: Feature | Description: Consider adding shorting capability or inverse token trading for bearish markets | Mentioned By: Patt\nType: Technical | Description: Explore Hyperliquid as a trading platform for AI agent to gain exposure to more coins | Mentioned By: Osint (aka not_in_a_dao_ai)\nType: Technical | Description: Implement daily timeframe trading strategy | Mentioned By: Osint (aka not_in_a_dao_ai)",
          "messageCount": 30,
          "userCount": 7
        },
        {
          "channelId": "1328592959444095038",
          "channelName": "associates",
          "summary": "# Analysis of \"associates\" Discord Channel\n\n## 1. Summary\nThe chat segment shows minimal technical discussion. Jin mentioned plans to combine two GitHub repositories (discord-summarizer and ai-news) to filter out noise in the community, find pain points, reward contributors, and create FAQ content for AI agents to scale developer relations. There was brief discussion about the team's pivot and approach to partnerships, with Shaw noting they now have a more serious team with dedicated resources for developer relations, partnerships, and operations. The rest of the conversation consisted of market commentary, memes, and brief exchanges about the project's status relative to market conditions.\n\n## 2. FAQ\nQ: How are you planning on filtering out the noise? (asked by Dragonbutt) A: By combining discord-summarizer and ai-news repositories to find pain points, reward contributors, and create FAQ for AI agents (answered by jin)\nQ: Do we have an obligation to resuscitate our partners? (asked by Smedroc - Street urchin @ ai16z) A: Got to rescue our own ship first. We're not the EU (answered by HoneyBadger)\nQ: What does that specifically mean for the \"DAO\"? (asked by Dragonbutt) A: We have a much more serious team now with more dedicated resources to dev rel, partnerships and ops (answered by shaw)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Dragonbutt | Context: Question about filtering out noise in the community | Resolution: Shared GitHub repositories that will be combined to find pain points, reward contributors, and create FAQ for AI agents\n\n## 4. Action Items\nTechnical: Combine discord-summarizer and ai-news repositories to filter community noise | Description: Create a system to identify pain points, reward contributors, and generate FAQ for AI agents | Mentioned By: jin\nDocumentation: Create FAQ content for AI agents | Description: Load frequently asked questions into AI agents to scale developer relations | Mentioned By: jin\nFeature: Implement contributor reward system | Description: Identify and reward valuable contributors based on automated analysis | Mentioned By: jin",
          "messageCount": 14,
          "userCount": 8
        },
        {
          "channelId": "1318770424632311930",
          "channelName": "tokenomics",
          "summary": "# Discord Chat Analysis - \"tokenomics\" Channel\n\n## 1. Summary:\nDorianD has been working on building an L2 for ElizaOS using Solana validators. After initial struggles with build errors, they made progress setting up three nodes for testing. Their goal is to implement a system based on a specific tokenomics model (linked to a HackMD document). DorianD is exploring ways to add more logging or evaluation capabilities for agents to provide feedback on plugins, which could be used for product improvements or plugin performance ratings. They're also researching methods to allow staked coins to be re-hypothecated to generate yield for paying L2 nodes. The development process has been challenging, with serialization issues that even advanced AI tools like Grok couldn't resolve. There were also technical difficulties with the Cursor development environment after upgrading, though these were eventually resolved.\n\n## 2. FAQ:\nQ: Is there a way to add more logging or evaluating actions for agents to provide feedback on plugins? (asked by DorianD) A: Unanswered\nQ: How can staked coins be re-hypothecated to create yield for paying L2 nodes? (asked by DorianD) A: Unanswered\n\n## 3. Help Interactions:\nHelper: yikesawjeez | Helpee: DorianD | Context: Serialization issues that Grok couldn't solve | Resolution: Suggested trying Claude via \"npm install -g anthropic/claude-code\" and updating Cursor to version 3.7 for access to a new agent\nHelper: yikesawjeez | Helpee: DorianD | Context: Development environment issues on Solana | Resolution: Acknowledged that \"devex on solana is hot garbage\" and mentioned that Avalanche (avax) also required configuration but should be simpler now\n\n## 4. Action Items:\nTechnical: Implement L2 for ElizaOS using Solana validators based on the linked tokenomics model | Mentioned By: DorianD\nTechnical: Add more logging or evaluation capabilities for agents to provide feedback on plugins | Mentioned By: DorianD\nTechnical: Research methods to allow staked coins to be re-hypothecated for L2 node payments | Mentioned By: DorianD\nTechnical: Resolve serialization issues in the L2 implementation | Mentioned By: DorianD",
          "messageCount": 18,
          "userCount": 2
        },
        {
          "channelId": "1301363808421543988",
          "channelName": "\ud83e\udd47-partners",
          "summary": "# Analysis of \ud83e\udd47-partners Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around the upcoming rebranding of ai16z to ElizaOS. Key discussions include the consolidation of X (Twitter) accounts, maintaining clarity about the token ticker, and ensuring a smooth transition. Partners express concerns about potential confusion between Eliza and ElizaOS brands. The team is working with X support to swap the @elizaOS and @ai16zdao handles while maintaining followers.\n\nTechnical discussions include a proposed Solana L2 system where ai16z tokens could be staked to run validator or RPC nodes, with agents registering on L1 by paying ai16z into a pool. There's also mention of a VRM-to-spritesheet pipeline for creating game assets, potentially for an \"Eliza Fighter\" game.\n\nThe team is developing multiple initiatives to support quality projects in the ecosystem, including Labs/Studios partnerships, builder chats, demo days, and ecosystem funding. They're also addressing issues with compromised Telegram channels by updating links on platforms like Dexscreener.\n\nThe community is actively monitoring competitor activities, including Pump.fun's AMM launch and sentiment shifts, which could present opportunities for ElizaOS.\n\n## 2. FAQ\nQ: If the teams featured in Clank Tank pump, does that mean fund is actually investing in them? (asked by Avanc) A: Unanswered\nQ: Are we changing the token name, but not the ticker? That will happen alongside the merge of accounts on X? (asked by DannyNOR NoFapArc) A: Unanswered\nQ: In terms of X accounts we currently have - ai16zdao / ElizaOS / Eliza Studios. Which accounts are being consolidated? (asked by Ka_yari) A: The plan is to exchange the @elizaOS handle with @ai16zdao, with support from X. (answered by accelxr)\nQ: How do we make sure we know how to distinguish between devs committed and building for the long term and those looking to extract from Eliza community for a quick cash grab? (asked by Ka_yari) A: Using a combination of Labs/Studios partnerships, builder chats, demo days, and ecosystem funding to promote quality projects. (answered by accelxr)\nQ: Will you be going to Hong Kong from April 6 to 9 for the annual Hong Kong Web3 event? (asked by Zolo) A: Unanswered\nQ: Where to look for latest tokenomics? Is it in the whitepaper? (asked by charlie) A: Unanswered\n\n## 3. Help Interactions\nHelper: ben | Helpee: Toni | Context: Ai16z dexscreener telegram link was updated to a scam link | Resolution: Dexscreener and other platforms updated with links to a new Telegram channel while investigating what happened with the original\nHelper: jin | Helpee: pragmatiko | Context: Concerns about Nous labeling ElizaOS as \"enemies\" | Resolution: Jin spoke with John from Nous who clarified that individual views don't reflect the organization's stance\nHelper: jin | Helpee: hubert | Context: Request for book club role | Resolution: Jin confirmed they're reading \"howtodao.xyz\" and created a book club\n\n## 4. Action Items\nType: Technical | Description: Investigate and resolve compromised Telegram channels | Mentioned By: irio\nType: Technical | Description: Finalize X handle swap between @elizaOS and @ai16zdao | Mentioned By: accelxr\nType: Technical | Description: Update token name on CMC, CG, CEXs when updating token metadata | Mentioned By: accelxr\nType: Documentation | Description: Create formal announcement introducing the rebrand with clear messaging about token contract address | Mentioned By: accelxr\nType: Documentation | Description: Develop brand kit and presentation guidelines for ElizaOS | Mentioned By: accelxr\nType: Feature | Description: Consider VRM-to-spritesheet pipeline for creating game assets | Mentioned By: jin\nType: Feature | Description: Explore Solana L2 system for staking ai16z tokens to run validator/RPC nodes | Mentioned By: DorianD\nType: Feature | Description: Develop recurring demo day for showcasing quality projects | Mentioned By: accelxr",
          "messageCount": 243,
          "userCount": 36
        },
        {
          "channelId": "1300756641406521416",
          "channelName": "ideas-feedback-rants",
          "summary": "# Analysis of \"ideas-feedback-rants\" Channel\n\n## 1. Summary\nThe chat segment contains three messages discussing agent development concepts. SmashAdams proposes creating an agent that writes stylized meme cryptocurrency reviews mimicking Pitchfork media journalists. Wukong of Fire mentions they're building stateful Trusted Execution Environments (TEEs) with proof generation and verification capabilities to ensure agent sovereignty, offering to discuss further. Hidden Forces raises a technical question about implementing functional memory systems that exist outside character JSON files, specifically for managing podcast episode data, and requests guidance on best practices for deeper machine memory systems.\n\n## 2. FAQ\nQ: How can I implement functional memory that exists outside character JSON files for recalling podcast episode data? (asked by Hidden Forces) A: Unanswered\n\n## 3. Help Interactions\nHelper: Wukong of Fire | Helpee: SmashAdams | Context: SmashAdams wanted to create an agent for writing stylized memecoin reviews | Resolution: Wukong offered their solution using stateful TEEs with proof generation and verification for agent sovereignty\n\n## 4. Action Items\nFeature: Create an agent that writes stylized memecoin reviews in the style of Pitchfork journalists | Description: Agent to generate overwrought longform reviews of new memecoins | Mentioned By: SmashAdams\nTechnical: Implement functional memory systems that exist outside character JSON files | Description: Need solution for accessing vector arrays at runtime to recall podcast episode data | Mentioned By: Hidden Forces\nTechnical: Develop stateful TEEs with proof generation and verification | Description: Building trusted execution environments that guarantee agent sovereignty | Mentioned By: Wukong of Fire",
          "messageCount": 3,
          "userCount": 3
        },
        {
          "channelId": "1313222089271939102",
          "channelName": "3d-ai-tv",
          "summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nJin reported progress on an AI news aggregator that's nearly complete after upgrades. The enhanced aggregator features historical data collection from X, Discord, GitHub, and markets, along with summarization capabilities. Jin shared a sample and mentioned working on implementing OpenGraph image previews to replace individual profile pictures in the display. After completing this feature, Jin plans to crawl and reprocess the last 60 days of news data. In a separate conversation, Jin requested a ShawAI VRM with a new hat, which Boom responded to with a mention.\n\n## 2. FAQ\nQ: Any of ya'll have shawai vrm with new hat? (asked by jin) A: [Boom responded with a mention] (answered by boom)\n\n## 3. Help Interactions\nHelper: boom | Helpee: jin | Context: Jin needed a ShawAI VRM with a new hat | Resolution: Boom responded with a mention that presumably provided what Jin needed\n\n## 4. Action Items\nTechnical: Implement OpenGraph image previews for the AI news aggregator | Description: Replace individual profile pictures with OpenGraph previews | Mentioned By: jin\nTechnical: Crawl and reprocess last 60 days of news | Description: Gather and analyze historical news data from the past 60 days | Mentioned By: jin\nTechnical: Merge upgraded AI news aggregator | Description: Complete and merge the news aggregator with historical aggregation and summarization features | Mentioned By: jin",
          "messageCount": 15,
          "userCount": 2
        }
      ]
    }
  },
  "ai_news_elizaos_daily_discord_md_2025-02-24": {
    "filename": "2025-02-24.md",
    "content": "# elizaOS Discord - 2025-02-24\n\n## Overall Discussion Highlights\n\n### ElizaOS Platform Updates\n- **Version 0.25.8 Released**: Odilitime announced the release of ElizaOS v0.25.8 with plugins moved out of the main codebase to a separate repository at https://github.com/elizaos-plugins/\n- **ElizaOS V2 Development**: Witch clarified that ElizaOS V2 codebase is being developed by Shaw with an expected release in early April or sooner\n- **Rebranding Progress**: The team is working on rebranding ai16z to ElizaOS, including consolidating X (Twitter) accounts by swapping the @elizaOS and @ai16zdao handles while maintaining followers\n- **Token Status**: The ai16z token will maintain the same contract address through the rebrand, with plans to promote the token and announce planned tokenomics after the rebrand is complete\n\n### Technical Discussions\n- **Memory Allocation Issues**: Multiple users reported JavaScript heap out of memory errors when using RAG knowledge, with solutions involving increasing Node.js memory limits using `NODE_OPTIONS=\"--max-old-space-size=8192\"`\n- **Embedding Model Problems**: Users experienced issues with embedding models for RAG knowledge, particularly with the BGE model not being found, with suggestions to use `text-embedding-ada-002` instead\n- **Plugin Architecture Changes**: Confusion about the new plugin architecture after plugins were moved out of the main ElizaOS repository, with some plugins accidentally removed from the registry\n- **L2 Development**: DorianD has been working on building an L2 for ElizaOS using Solana validators, proposing a system where ai16z tokens could be staked to run validator or RPC nodes\n- **Agent Memory Systems**: Hidden Forces raised questions about implementing functional memory systems that exist outside character JSON files, specifically for managing podcast episode data\n\n### Community Projects\n- **Instacart Agent**: Scooper shared their successful implementation of an Instacart agent built on Eliza that helps with meal planning and grocery ordering within budget constraints\n- **AI News Aggregator**: Jin reported progress on an AI news aggregator that collects historical data from X, Discord, GitHub, and markets, with summarization capabilities\n- **DegenSpartanAI Trading**: Community members discussed the performance of DegenSpartanAI, a trading AI agent in early development, with Osint providing detailed technical suggestions for improving its trading strategy\n- **Community Analysis Tools**: Jin mentioned plans to combine discord-summarizer and ai-news repositories to filter out noise in the community, find pain points, reward contributors, and create FAQ content for AI agents\n\n## Key Questions & Answers\n\n**Q: Where have the plugins been moved to after the latest update?**  \nA: They have been moved to https://github.com/elizaos-plugins/ (answered by mtbc)\n\n**Q: How can I fix the \"JavaScript heap out of memory\" error?**  \nA: Set NODE_OPTIONS=\"--max-old-space-size=8192\" or other memory size values (answered by boolkeys)\n\n**Q: How can I run multiple characters in one deployment?**  \nA: Use \"pnpm start \u2014characters=\"character1.json,character2.json,3.json\"\" (answered by boolkeys)\n\n**Q: How to fix the RAG knowledge base embedding model error?**  \nA: Set embeddingModel to 'text-embedding-ada-002' in your character config (answered by Sabochee)\n\n**Q: Is there a LinkedIn plugin available?**  \nA: There was a PR but it was a joke with no working code (answered by Odilitime)\n\n**Q: What does the Instacart agent do?**  \nA: You can order groceries through Instacart. It helps you meal plan a week of recipes and then order groceries. (answered by scooper)\n\n**Q: Can you give a price limit param for the meal plan?**  \nA: Yep, you can tell it your budget. (answered by scooper)\n\n**Q: Can anyone know about ElizaOS tokenomics?**  \nA: Tokenomics is in the #tokenomics channel but they're waiting for launchpad release before releasing the full tokenomics + future plans. (answered by witch)\n\n**Q: Is eliza official ai16z token?**  \nA: No, our 2 official tokens are ai16z (pending rebrand but same CA) and DegenAI. eliza is a different project we are aligned with, but not under our scope. (answered by Patt)\n\n**Q: In terms of X accounts we currently have - ai16zdao / ElizaOS / Eliza Studios. Which accounts are being consolidated?**  \nA: The plan is to exchange the @elizaOS handle with @ai16zdao, with support from X. (answered by accelxr)\n\n**Q: How do we make sure we know how to distinguish between devs committed and building for the long term and those looking to extract from Eliza community for a quick cash grab?**  \nA: Using a combination of Labs/Studios partnerships, builder chats, demo days, and ecosystem funding to promote quality projects. (answered by accelxr)\n\n## Community Help & Collaboration\n\n1. **Memory Allocation Solutions**:  \n   boolkeys helped Pleasures resolve JavaScript heap out of memory errors by providing the command to increase Node.js memory allocation: `export NODE_OPTIONS=\"--max-old-space-size=4096\"` with options for different memory sizes.\n\n2. **Embedding Model Troubleshooting**:  \n   Sabochee assisted Waqas Wahid with embedding model errors in RAG knowledge by suggesting the use of `text-embedding-ada-002` model in character config.\n\n3. **PostgreSQL Configuration**:  \n   P\u039eTE provided detailed instructions to the community on configuring PostgreSQL with ElizaOS, including correct URL format and schema location.\n\n4. **Trading Strategy Suggestions**:  \n   Osint (aka not_in_a_dao_ai) provided DegenSpartanAI developers with a detailed workflow proposal for improving trading strategies, including BTC range monitoring, using coinrotator.app, and trading on daily timeframes.\n\n5. **Plugin Registry Fix**:  \n   Odilitime identified a commit that accidentally removed the SQD plugin from the registry and promised to handle restoring it after ian | sqd.ai reported the issue.\n\n6. **Telegram Bot Troubleshooting**:  \n   Sipit suggested to Quang Vinh that they should revoke their Telegram bot API key and get a new one to resolve connection timeout issues.\n\n7. **Development Environment Issues**:  \n   yikesawjeez helped DorianD with serialization issues by suggesting trying Claude via \"npm install -g anthropic/claude-code\" and updating Cursor to version 3.7 for access to a new agent.\n\n## Action Items\n\n### Technical\n1. **Fix memory allocation issues with RAG knowledge** - Implement better memory management for large knowledge bases (Mentioned by Multiple users)\n2. **Restore accidentally removed plugins in registry** - Fix commit that removed multiple plugins including SQD (Mentioned by Odilitime)\n3. **Fix action validation in agent runtime** - Investigate why handlers execute despite validate returning false (Mentioned by Sabochee)\n4. **Add WebSocket support to direct client** - Implement WebSocket functionality for direct client (Mentioned by shaw)\n5. **Implement L2 for ElizaOS using Solana validators** - Based on the linked tokenomics model (Mentioned by DorianD)\n6. **Add more logging or evaluation capabilities for agents** - To provide feedback on plugins (Mentioned by DorianD)\n7. **Research methods to allow staked coins to be re-hypothecated** - For L2 node payments (Mentioned by DorianD)\n8. **Resolve serialization issues in the L2 implementation** (Mentioned by DorianD)\n9. **Investigate and resolve compromised Telegram channels** (Mentioned by irio)\n10. **Finalize X handle swap between @elizaOS and @ai16zdao** (Mentioned by accelxr)\n11. **Update token name on CMC, CG, CEXs** - When updating token metadata (Mentioned by accelxr)\n12. **Implement OpenGraph image previews for the AI news aggregator** - Replace individual profile pictures with OpenGraph previews (Mentioned by jin)\n13. **Crawl and reprocess last 60 days of news** - Gather and analyze historical news data (Mentioned by jin)\n14. **Merge upgraded AI news aggregator** - Complete and merge with historical aggregation and summarization features (Mentioned by jin)\n15. **Implement BTC price range monitoring** - For $85k-$99k short term, $73k-$109k broader range (Mentioned by Osint)\n16. **Add functionality to enter positions at lower part of BTC trading range** (Mentioned by Osint)\n17. **Integrate with tools like coinrotator.app** - For simplified trend analysis (Mentioned by Osint)\n18. **Implement daily timeframe trading strategy** (Mentioned by Osint)\n19. **Fix issue with API key configuration** - In Eliza agent kit starter (Mentioned by Syntronyx)\n20. **Investigate ARM64 support for Docker deployments** (Mentioned by \u2572\u239d\u29f9Nat'\u29f8\u23a0\u2571)\n21. **Review and merge translation corrections pull request** (Mentioned by Void)\n22. **Address repetitive posting behavior in Twitter agents** (Mentioned by artzy)\n23. **Implement functional memory systems outside character JSON files** - For accessing vector arrays at runtime to recall podcast episode data (Mentioned by Hidden Forces)\n24. **Develop stateful TEEs with proof generation and verification** - Building trusted execution environments that guarantee agent sovereignty (Mentioned by Wukong of Fire)\n\n### Documentation\n1. **Update character file format documentation** - Clarify how to specify clients and plugins in the new version (Mentioned by Multiple users)\n2. **Create guide for using PostgreSQL with ElizaOS** - Document proper setup process for PostgreSQL adapter (Mentioned by P\u039eTE)\n3. **Update tokenomics documentation** - After launchpad release (Mentioned by witch)\n4. **Create formal announcement introducing the rebrand** - With clear messaging about token contract address (Mentioned by accelxr)\n5. **Develop brand kit and presentation guidelines for ElizaOS** (Mentioned by accelxr)\n\n### Feature\n1. **Add LinkedIn client implementation** - Develop a working LinkedIn plugin (Mentioned by 0xConsole)\n2. **Improve embedding model options for RAG** - Add support for free embedding models (Mentioned by Waqas Wahid)\n3. **Consider adding shorting capability or inverse token trading** - For bearish markets (Mentioned by Patt)\n4. **Explore Hyperliquid as a trading platform** - For AI agent to gain exposure to more coins (Mentioned by Osint)\n5. **Consider multi-chain support beyond Solana** (Mentioned by Void)\n6. **Create desktop app wrapper for Eliza** - On Mac and Windows (Mentioned by AD)\n7. **Improve character generation to prevent repetitive posts** (Mentioned by artzy)\n8. **Consider VRM-to-spritesheet pipeline** - For creating game assets (Mentioned by jin)\n9. **Explore Solana L2 system for staking ai16z tokens** - To run validator/RPC nodes (Mentioned by DorianD)\n10. **Develop recurring demo day** - For showcasing quality projects (Mentioned by accelxr)\n11. **Create an agent that writes stylized memecoin reviews** - In the style of Pitchfork journalists (Mentioned by SmashAdams)\n12. **Explore EVM based wallet support for ETH/BASE** (Mentioned by Zeke)"
  },
  "github_summaries_daily_2025-02-25": {
    "filename": "2025-02-25.md",
    "content": "ElizaOS made significant strides today, focusing on enhancing the core framework's modularity and scalability through new features like improved plugin management and multi-tenancy support. Key efforts included resolving PGlite migration issues and refactoring server code for better performance, alongside addressing several critical bugs and memory challenges.\n\n## \ud83d\udea8 Needs Attention\n- **Urgent Discussions**:\n    - [elizaos/eliza#3664](https://github.com/elizaos/eliza/issues/3664): \"JavaScript heap out of memory\" error during knowledge/message processing requires immediate investigation into memory management.\n    - [elizaos/eliza#3661](https://github.com/elizaos/eliza/issues/3661): Docker file issue related to invalid cache store needs attention to prevent deployment problems.\n\n## \u2705 Completed Work\n### Core Framework Enhancements & Scalability\n- Implemented a new `agent` table and renamed the `user` table to `entity` to support multi-tenancy and future scalability within the ElizaOS framework ([elizaos/eliza#3637](https://github.com/elizaos/eliza/pull/3637)).\n- Added middleware settings for agent server options, providing developers with more control over server behavior ([elizaos/eliza#3648](https://github.com/elizaos/eliza/pull/3648)).\n- Cleaned up server code to enhance maintainability and performance ([elizaos/eliza#3667](https://github.com/elizaos/eliza/pull/3667)).\n- Refactored memory queries and knowledge metadata to improve system architecture and flexibility ([elizaos/eliza#3606](https://github.com/elizaos/eliza/pull/3606)).\n\n### Plugin Management & CLI Improvements\n- Introduced a feature to check and display installed plugins when using the CLI, enhancing user experience and visibility ([elizaos/eliza#3660](https://github.com/elizaos/eliza/pull/3660)).\n- Resolved multiple issues related to the TON Plugin, including batch transfer processing, wallet creation, and historical token price data retrieval, significantly enhancing its functionality ([elizaos/eliza#3043](https://github.com/elizaos/eliza/issues/3043), [elizaos/eliza#3042](https://github.com/elizaos/eliza/issues/3042), [elizaos/eliza#3032](https://github.com/elizaos/eliza/issues/3032), [elizaos/eliza#3031](https://github.com/elizaos/eliza/issues/3031), [elizaos/eliza#2984](https://github.com/elizaos/eliza/issues/2984)).\n\n### Bug Fixes & System Stability\n- Resolved issues with PGlite migrations, ensuring a code-first approach for SQL across the system ([elizaos/eliza#3672](https://github.com/elizaos/eliza/pull/3672)).\n- Fixed setup dimensions before starting the client, improving initialization processes ([elizaos/eliza#3668](https://github.com/elizaos/eliza/pull/3668)).\n- Addressed various minor bugs, including speaker removal in Twitter spaces and typographical errors in documentation ([elizaos/eliza#3662](https://github.com/elizaos/eliza/pull/3662), [elizaos/eliza#3656](https://github.com/elizaos/eliza/pull/3656)).\n\n## \ud83d\udc1e Issue Triage\n### New Issues\n- **elizaos/eliza**:\n    - [elizaos/eliza#3664](https://github.com/elizaos/eliza/issues/3664): \"JavaScript heap out of memory\" error during knowledge/message processing.\n    - [elizaos/eliza#3661](https://github.com/elizaos/eliza/issues/3661): Docker file issue related to invalid cache store.\n\n### Closed Issues\n- **elizaos/eliza**:\n    - [elizaos/eliza#3043](https://github.com/elizaos/eliza/issues/3043): TON Plugin: Batch transfer processing.\n    - [elizaos/eliza#3042](https://github.com/elizaos/eliza/issues/3042): TON Plugin: Wallet creation.\n    - [elizaos/eliza#3032](https://github.com/elizaos/eliza/issues/3032): TON Plugin: Historical token price data retrieval.\n    - [elizaos/eliza#3031](https://github.com/elizaos/eliza/issues/3031): TON Plugin: General functionality.\n    - [elizaos/eliza#2984](https://github.com/elizaos/eliza/issues/2984): TON Plugin: Overall enhancements."
  },
  "github_summaries_week_latest_2025-12-21.md": {
    "filename": "2025-12-21.md",
    "content": "# Overall Project Weekly Summary (Dec 21 - 27, 2025)\n\n## Executive Summary\nThis week, the ElizaOS project executed a focused push to enhance platform quality, delivering significant improvements to both user experience and backend stability. We rapidly resolved a large number of UI issues in the agent builder, while simultaneously shipping foundational upgrades for performance, reliability, and developer extensibility across core services and plugins.\n\n### Key Strategic Initiatives & Outcomes\n\n**Refining the User Experience**\n*To make our platform more intuitive and effective for users, we focused on identifying and rapidly resolving interface issues.*\n- A large batch of UI/UX refinements for the agent builder were resolved in [elizaos/eliza](https://github.com/elizaos/eliza), including improvements to button consistency ([#6274](https://github.com/elizaos/eliza/issues/6274)), adding an \"unsaved changes\" warning ([#6275](https://github.com/elizaos/eliza/issues/6275)), and other usability enhancements.\n- A new feature was added to the [elizaos-plugins/plugin-openai](https://github.com/elizaos-plugins/plugin-openai) to support real-time streaming of text generation, making agent interactions feel more immediate and responsive.\n- A new wave of issues was identified across multiple plugins to improve agent chat behavior, such as ensuring the most recent conversation opens by default ([#6281](https://github.com/elizaos-plugins/plugin-twitter/issues/6281)) and fixing conversation duplication bugs ([#6282](https://github.com/elizaos-plugins/plugin-twitter/issues/6282)).\n\n**Strengthening Platform Performance and Stability**\n*To ensure our framework is robust and scalable, we made critical updates to improve system reliability and throughput.*\n- The core platform in [elizaos/eliza](https://github.com/elizaos/eliza) was upgraded to use true Server-Sent Events (SSE), replacing less efficient polling methods for real-time updates ([#5930](https://github.com/elizaos/eliza/issues/5930)).\n- The [elizaos-plugins/plugin-knowledge](https://github.com/elizaos-plugins/plugin-knowledge) repository introduced configurable rate limiting for high-throughput APIs, providing greater control and stability under heavy load ([#49](https://github.com/elizaos-plugins/plugin-knowledge/pull/49)).\n- Significant refactoring and type-safety improvements were completed in the [elizaos-plugins/plugin-discord](https://github.com/elizaos-plugins/plugin-discord) plugin, resolving TypeScript errors and overhauling message handling logic for better stability ([#38](https://github.com/elizaos-plugins/plugin-discord/pull/38), [#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)).\n\n**Improving Developer Experience and Extensibility**\n*To empower our community and accelerate future development, we enhanced the core framework to make it easier to build powerful, type-safe plugins.*\n- The core runtime in [elizaos/eliza](https://github.com/elizaos/eliza) was updated to support generic types for custom event handlers, improving type safety and code clarity for plugin developers ([#6277](https://github.com/elizaos/eliza/pull/6277)).\n- A proposal for a new multi-bot voice architecture was submitted in the [elizaos-plugins/plugin-discord](https://github.com/elizaos-plugins/plugin-discord) repository, paving the way for future support of audio channels ([#36](https://github.com/elizaos-plugins/plugin-discord/pull/36)).\n\n### Cross-Repository Coordination\nThis week highlighted a tight feedback loop between user-facing plugins and the core platform. A coordinated effort to improve the agent builder UI saw numerous issues identified in the `plugin-discord` repository on one day and resolved in the main `elizaos/eliza` repository the next. Additionally, the new streaming text generation feature in `plugin-openai` is now awaiting integration with the main `elizaos` repository, demonstrating how plugin innovations are being prepared for project-wide rollout.\n\n## Repository Spotlights\n\n### elizaos/eliza\n- **UI/UX Overhaul:** A significant number of issues were closed to refine the agent builder and dashboard experience, including redesigning the dashboard as the primary landing page ([#6222](https://github.com/elizaos/eliza/issues/6222)), reducing long loading times ([#6248](https://github.com/elizaos/eliza/issues/6248)), and resolving a large set of UI bugs ([#6270](https://github.com/elizaos/eliza/issues/6270), [#6271](https://github.com/elizaos/eliza/issues/6271), [#6273](https://github.com/elizaos/eliza/issues/6273), [#6275](https://github.com/elizaos/eliza/issues/6275)).\n- **Core Framework Enhancements:** Generic type support was added for custom event handlers to improve developer experience and type safety ([#6277](https://github.com/elizaos/eliza/pull/6277)). The platform was also updated to use true SSE streaming instead of polling ([#5930](https://github.com/elizaos/eliza/issues/5930)).\n- **Bug Fixes:** A critical bug preventing agents from responding due to a `MessageBusService` error was resolved ([#6140](https://github.com/elizaos/eliza/issues/6140)).\n\n### elizaos-plugins/plugin-openai\n- **Streaming Support:** A major feature was added to enable streaming for text generation, allowing for real-time output delivery. This work is awaiting integration with the main ElizaOS repository ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)).\n- **New Feature Requests:** New issues were opened to improve user experience, including a proposal to summarize chat names ([#6278](https://github.com/elizaos-plugins/plugin-openai/issues/6278)) and add a user feedback button ([#6280](https://github.com/elizaos-plugins/plugin-openai/issues/6280)).\n\n### elizaos-plugins/plugin-discord\n- **Major Refactoring & Bug Fixes:** The plugin underwent significant maintenance, including resolving TypeScript type errors ([#38](https://github.com/elizaos-plugins/plugin-discord/pull/38), [#37](https://github.com/elizaos-plugins/plugin-discord/pull/37)), overhauling message handling logic ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)), and introducing a new permission system ([#34](https://github.com/elizaos-plugins/plugin-discord/pull/34)).\n- **Issue Identification:** A large volume of new issues were opened, primarily focused on refining the agent builder UI/UX ([#6270](https://github.com/elizaos-plugins/plugin-discord/issues/6270)-[#6275](https://github.com/elizaos-plugins/plugin-discord/issues/6275)), which drove rapid development in the main `elizaos/eliza` repository.\n- **Architectural Proposal:** A new multi-bot voice architecture was proposed to support audio channels and progressive updates in the future ([#36](https://github.com/elizaos-plugins/plugin-discord/pull/36)).\n\n### elizaos-plugins/plugin-knowledge\n- **Enhanced API Rate Limiting:** A new feature was merged to add configurable rate limits for high-throughput APIs, improving system stability. The update also increased default limits fivefold to better support demanding use cases ([#49](https://github.com/elizaos-plugins/plugin-knowledge/pull/49)).\n- **New Issues:** Several issues were opened to improve agent chat behavior ([#6281](https://github.com/elizaos-plugins/plugin-knowledge/issues/6281), [#6282](https://github.com/elizaos-plugins/plugin-knowledge/issues/6282)) and fix UI and documentation problems ([#6283](https://github.com/elizaos-plugins/plugin-knowledge/issues/6283), [#6284](https://github.com/elizaos-plugins/plugin-knowledge/issues/6284)).\n\n### elizaos-plugins/plugin-twitter\n- **Bug Fix:** A fix was merged to ensure that changes to posting enablement settings are applied immediately and consistently, improving the reliability of the plugin's core functionality ([#42](https://github.com/elizaos-plugins/plugin-twitter/pull/42)).\n- **Future Work Identified:** New issues were created to address bugs in agent chat behavior ([#6281](https://github.com/elizaos-plugins/plugin-twitter/issues/6281), [#6282](https://github.com/elizaos-plugins/plugin-twitter/issues/6282)) and to improve UI consistency and documentation ([#6283](https://github.com/elizaos-plugins/plugin-twitter/issues/6283), [#6284](https://github.com/elizaos-plugins/plugin-twitter/issues/6284))."
  },
  "github_summaries_month_latest_2025-12-01.md": {
    "filename": "2025-12-01.md",
    "content": "# Overall Project Monthly Summary (December 2025)\n\n## Executive Summary\nDecember was a pivotal month focused on strengthening the ElizaOS foundation and strategically expanding its capabilities. We executed a major push to improve core platform stability and defined a clear vision for a future user experience overhaul. Simultaneously, we expanded our agent ecosystem with key Web3 plugins and initiated a coordinated effort to introduce real-time streaming, making our agents more responsive and interactive.\n\n### Key Strategic Initiatives & Outcomes\n\n**Strengthening the Core Platform for Stability and Scale**\nTo support increasingly complex and autonomous agents, we invested heavily in making the underlying framework more robust, secure, and modern.\n-   A major server refactoring was completed in [elizaos/eliza](https://github.com/elizaos/eliza) to optimize the codebase and improve reliability ([#6199](https://github.com/elizaos/eliza/pull/6199)).\n-   Code quality and type safety were significantly enhanced by resolving build errors across the entire `elizaos/eliza` monorepo ([#6218](https://github.comcom/elizaos/eliza/pull/6218)).\n-   A critical security vulnerability in character secret encryption was fixed, ensuring user data is properly protected ([#6217](https://github.comcom/elizaos/eliza/pull/6217)).\n-   Agent autonomy was improved by enhancing how tools interact with memory in the Master Control Program, laying the groundwork for more sophisticated reasoning ([elizaos-plugins/plugin-mcp](https://github.com/elizaos-plugins/plugin-mcp), [#19](https://github.com/elizaos-plugins/plugin-mcp/pull/19)).\n\n**Expanding the Agent Ecosystem into Web3 and Beyond**\nWe continued to execute on our mission to thrive in both Web2 and Web3 by adding powerful new tools for agents to use.\n-   The [elizaos-plugins/registry](https://github.com/elizaos-plugins/registry) was expanded with three new community plugins, adding capabilities for DeFi ([#235](https://github.com/elizaos-plugins/registry/pull/235)), decentralized social media ([#243](https://github.com/elizaos-plugins/registry/pull/243)), and communication ([#242](https://github.com/elizaos-plugins/registry/pull/242)).\n-   The new self-hosted Farcaster plugin is a key step toward greater agent autonomy, allowing agents to connect directly to the network without relying on third-party APIs ([#243](https://github.com/elizaos-plugins/registry/pull/243)).\n\n**Laying the Groundwork for Real-Time, Responsive Agents**\nFor agents to feel truly interactive, they must process and respond to information as it arrives, not just after a long pause.\n-   Work was initiated across multiple plugins to add streaming support, a foundational feature for enabling real-time, conversational AI. This effort included the [OpenAI](https://github.com/elizaos-plugins/plugin-openai) ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)), [Anthropic](https://github.com/elizaos-plugins/plugin-anthropic) ([#12](https://github.com/elizaos-plugins/plugin-anthropic/pull/12)), and [OpenRouter](https://github.com/elizaos-plugins/plugin-openrouter) ([#21](https://github.com/elizaos-plugins/plugin-openrouter/pull/21)) plugins.\n\n**Refining the User Experience and Planning for the Future**\nMaking the platform intuitive is key to growing our community. This month, we cleared existing UI issues and laid out a detailed plan for a major user experience overhaul.\n-   A large number of UI/UX issues were resolved in [elizaos/eliza](https://github.com/elizaos/eliza), streamlining the interface by consolidating navigation ([#6173](https://github.com/elizaos/eliza/issues/6173)) and improving visual feedback ([#6235](https://github.com/elizaos/eliza/issues/6235)).\n-   A comprehensive plan for a redesigned dashboard and guided user onboarding was established through the creation of over 20 new strategic issues in [elizaos/eliza](https://github.com/elizaos/eliza) ([#6221](https://github.com/elizaos/eliza/issues/6221), [#6222](https://github.com/elizaos/eliza/issues/6222)).\n-   The developer experience was simplified by making ElizaOS Cloud the default AI provider in the CLI, complete with a new browser-based login flow ([elizaos/eliza](https://github.com/elizaos/eliza), [#6208](https://github.com/elizaos/eliza/pull/6208)).\n\n### Cross-Repository Coordination\nThis month saw a coordinated push to standardize and modernize key functionalities across the ElizaOS ecosystem.\n-   **Unified Streaming Support:** A parallel effort began across the `plugin-openai`, `plugin-anthropic`, and `plugin-openrouter` repositories to implement streaming. This shared initiative will bring more responsive, real-time interactions to agents regardless of the underlying model provider.\n-   **Architectural Alignment:** Following the modernization of core APIs in `elizaos/eliza`, work began in the `plugin-telegram` ([#22](https://github.com/elizaos-plugins/plugin-telegram/pull/22)) and `plugin-discord` ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)) plugins to refactor their messaging systems. This alignment ensures all plugins communicate with the core framework in a standardized, more modular way.\n\n## Repository Spotlights\n\n### elizaos/eliza\nThe core repository saw extensive activity focused on stability, user experience, and future planning.\n-   Completed a major server refactoring to optimize the codebase and API structure ([#6199](https://github.com/elizaos/eliza/pull/6199)).\n-   Resolved TypeScript build errors across the monorepo, significantly improving code stability and type safety ([#6218](https://github.com/elizaos/eliza/pull/6218)).\n-   Updated all project dependencies to their latest versions, resolving compatibility issues ([#6210](https://github.com/elizaos/eliza/pull/6210)).\n-   Fixed a critical security bug in character secret encryption ([#6217](https://github.comcom/elizaos/eliza/pull/6217)).\n-   Streamlined the developer experience by making ElizaOS Cloud the default provider in the CLI, adding a new browser-based login flow ([#6208](https://github.com/elizaos/eliza/pull/6208)).\n-   Closed a large batch of UI/UX issues, including consolidating the sidebar ([#6173](https://github.com/elizaos/eliza/issues/6173)) and adding an \"Unsaved Changes\" warning ([#6183](https://github.com/elizaos/eliza/issues/6183)).\n-   Opened over 20 new issues to define a comprehensive overhaul of the dashboard ([#6222](https://github.com/elizaos/eliza/issues/6222)) and agent creation workflow.\n-   Addressed community concerns regarding token snapshot eligibility for Tangem wallet users ([#6158](https://github.com/elizaos/eliza/issues/6158), [#6211](https://github.com/elizaos/eliza/issues/6211)).\n\n### elizaos-plugins/registry\nThe registry was expanded with new plugins, broadening agent capabilities in Web2 and Web3.\n-   Added the Moralis DeFi plugin (`@pyboom/plugin-moralis-v2`) to provide agents with Moralis v2 functionalities ([#235](https://github.com/elizaos-plugins/registry/pull/235)).\n-   Integrated the OpenChat plugin (`@tonyflam/plugin-openchat`) for agent communication ([#242](https://github.com/elizaos-plugins/registry/pull/242)).\n-   Introduced a self-hosted Farcaster plugin (`plugin-farcaster-local-hub`) that removes dependency on third-party APIs ([#243](https://github.com/elizaos-plugins/registry/pull/243)).\n\n### elizaos-plugins/plugin-mcp\nWork focused on foundational improvements for agent memory and tool interaction.\n-   Refactored memory handling by introducing an optional `mcpText` field and updating `handleToolResponse` to return a `Memory` object, enabling more robust agent configuration ([#19](https://github.com/elizaos-plugins/plugin-mcp/pull/19)).\n\n### elizaos-plugins/plugin-openai\nDevelopment began on a key feature for real-time interaction.\n-   Initiated work to add streaming support, opening a pull request to handle continuous data flows from the OpenAI API ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)).\n\n### elizaos-plugins/plugin-anthropic\nWork started on enhancing the plugin's real-time capabilities.\n-   A pull request was opened to introduce streaming support, enabling more dynamic and responsive agent communication ([#12](https://github.com/elizaos-plugins/plugin-anthropic/pull/12)).\n\n### elizaos-plugins/plugin-openrouter\nA significant enhancement was proposed to improve responsiveness.\n-   Work began on adding streaming support and refining the plugin's focus by removing tools support ([#21](https://github.com/elizaos-plugins/plugin-openrouter/pull/21)).\n\n### elizaos-plugins/plugin-telegram\nA major architectural refactor was initiated to improve integration with the core framework.\n-   A pull request was opened to implement a unified messaging API, aiming to standardize communication and enhance modularity ([#22](https://github.com/elizaos-plugins/plugin-telegram/pull/22)).\n\n### elizaos-plugins/plugin-discord\nThe plugin's internal architecture was improved for better maintainability.\n-   Work began on refactoring the message handling system to improve its structure and prepare for future enhancements ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)).\n\n### elizaos-plugins/plugin-mysql\nActivity focused on user support and documentation clarification.\n-   Resolved an issue by clarifying that documentation has been centralized in the `elizaos/docs` repository ([#6122](https://github.com/elizaos-plugins/plugin-mysql/issues/6122)).\n-   Provided a helpful tip to users that disabling other plugins may be necessary for successful initial table creation ([#1](https://github.com/elizaos-plugins/plugin-mysql/issues/1))."
  },
  "github_extracted_data_monthly_stats_text_2025-02": "{\n  \"interval\": {\n    \"intervalStart\": \"2025-02-01T00:00:00.000Z\",\n    \"intervalEnd\": \"2025-03-01T00:00:00.000Z\",\n    \"intervalType\": \"month\"\n  },\n  \"repository\": \"elizaos/eliza\",\n  \"overview\": \"From 2025-02-01 to 2025-03-01, elizaos/eliza had 448 new PRs (255 merged), 120 new issues, and 388 active contributors.\",\n  \"topIssues\": [\n    {\n      \"id\": \"I_kwDOMT5cIs6rhfR2\",\n      \"title\": \"RAG Knowledge JavaScript Heap Out of Memory\",\n      \"author\": \"suryanshkushwaha\",\n      \"number\": 3664,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-25T09:14:41Z\",\n      \"closedAt\": \"2025-04-19T18:32:38Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 17\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs6pmGrm\",\n      \"title\": \"Long messages cause an error\",\n      \"author\": \"lincheoll\",\n      \"number\": 3441,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-11T13:03:07Z\",\n      \"closedAt\": \"2025-03-04T04:23:36Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 14\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs6pavb1\",\n      \"title\": \"Cannot find module '@anush008/tokenizers-linux-arm64-gnu'\",\n      \"author\": \"GDA63\",\n      \"number\": 3418,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-10T13:07:29Z\",\n      \"closedAt\": \"2025-03-08T03:14:58Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 12\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs6q-8Ul\",\n      \"title\": \"agent isn't responding based on the provided knowledge.\",\n      \"author\": \"thopatevijay\",\n      \"number\": 3628,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-21T10:27:21Z\",\n      \"closedAt\": \"2025-03-08T01:15:16Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 10\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs6ry-sv\",\n      \"title\": \"Twitter Agent won't post / respond as it should\",\n      \"author\": \"mohsinn3\",\n      \"number\": 3693,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-26T17:08:51Z\",\n      \"closedAt\": \"2025-03-08T01:15:17Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 9\n    }\n  ],\n  \"topPRs\": [\n    {\n      \"id\": \"PR_kwDOMT5cIs6K85N9\",\n      \"title\": \"Update Eliza OmniFlix Plugin\",\n      \"author\": \"BlockEater96\",\n      \"number\": 3460,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-12T12:54:58Z\",\n      \"mergedAt\": null,\n      \"additions\": 373881,\n      \"deletions\": 16079\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6H-S3t\",\n      \"title\": \"chore: dev => main 0.1.9\",\n      \"author\": \"odilitime\",\n      \"number\": 2361,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-01-16T09:01:27Z\",\n      \"mergedAt\": \"2025-02-01T00:59:40Z\",\n      \"additions\": 250702,\n      \"deletions\": 16452\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6JteYE\",\n      \"title\": \"update deepseek\",\n      \"author\": \"0xgloria\",\n      \"number\": 3127,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-01T03:18:23Z\",\n      \"mergedAt\": null,\n      \"additions\": 140996,\n      \"deletions\": 704\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6Kijq6\",\n      \"title\": \"V2 Development\",\n      \"author\": \"lalalune\",\n      \"number\": 3393,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-09T04:25:04Z\",\n      \"mergedAt\": null,\n      \"additions\": 123786,\n      \"deletions\": 148968\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs6MAJuQ\",\n      \"title\": \"feat: support greenfield chain in bnb plugin\",\n      \"author\": \"clydemeng\",\n      \"number\": 3621,\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-02-21T06:32:05Z\",\n      \"mergedAt\": null,\n      \"additions\": 54685,\n      \"deletions\": 13535\n    }\n  ],\n  \"codeChanges\": {\n    \"additions\": 92539,\n    \"deletions\": 110476,\n    \"files\": 1004,\n    \"commitCount\": 1941\n  },\n  \"completedItems\": [\n    {\n      \"title\": \"fix: multi-biome-02\",\n      \"prNumber\": 3181,\n      \"type\": \"bugfix\",\n      \"body\": \"Add Biome linting and formatting configuration to the following plugins:\\r\\n- plugin-web-search\\r\\n- plugin-video-generation\\r\\n- plugin-udio\\r\\n- plugin-twitter\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"fix: multi-biome-01\",\n      \"prNumber\": 3180,\n      \"type\": \"bugfix\",\n      \"body\": \"Added biome to - plugin-zksync-era - plugin-zilliqa - plugin-zerion - plugin-whatsapp\"\n    },\n    {\n      \"title\": \"fix: plugin-0g\",\n      \"prNumber\": 3179,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed all the issues and added biome. Only issues still in place in upload.ts i had to add an \\r\\nany to overcome the issue on the line 370 const flowContract = getFlowContract(runtime.getSetting(\\\"ZEROG_FLOW_ADDRESS\\\"), signer as any); \\r\\n\\r\\n![S\"\n    },\n    {\n      \"title\": \"fix: plugin-0x\",\n      \"prNumber\": 3178,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed all the issues and added Biome\"\n    },\n    {\n      \"title\": \"fix: plugin-3g-generation\",\n      \"prNumber\": 3175,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed all the issues and added biome\"\n    },\n    {\n      \"title\": \"fix: plugin-abstract\",\n      \"prNumber\": 3174,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed all the issues but deployTokenAction.ts for the ANY and the result need probaly a refactoring.\\r\\n\\r\\n![Screenshot 2025-02-03 at 04 53 15](https://github.com/user-attachments/assets/15cd59ba-b0dc-4170-b5a1-31326f2fe2b4)\\r\\n\\r\\n`\\r\\n[{\\r\\n\\t\\\"resour\"\n    },\n    {\n      \"title\": \"fix: plugin-agentkit\",\n      \"prNumber\": 3172,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed the typing and added biome\"\n    },\n    {\n      \"title\": \"fix: plugin-akash\",\n      \"prNumber\": 3171,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed multiple issues and aded biome.\"\n    },\n    {\n      \"title\": \"fix: plugin-allora\",\n      \"prNumber\": 3169,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed all the issues and added biome\"\n    },\n    {\n      \"title\": \"docs: fix typos in .md\",\n      \"prNumber\": 3165,\n      \"type\": \"bugfix\",\n      \"body\": \"arch - arc\\r\\nastr0x., - astr0x, ( delete . )\"\n    },\n    {\n      \"title\": \"fix: upgrade openai and vercel ai packages to fix o1 errors\",\n      \"prNumber\": 3146,\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\\nOpenAI requests for o1 was not succeeding due to `max_tokens` being deprecated in favor of `max_completio\"\n    },\n    {\n      \"title\": \"feat (chore): plugin-coinmarketcap\",\n      \"prNumber\": 3134,\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\\nhttps://github.com/elizaOS/eliza/issues/3133\\r\\n<!-- This risks section\"\n    },\n    {\n      \"title\": \"feat (chore): plugin-coingecko test config and coverage\",\n      \"prNumber\": 3124,\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\\nhttps://github.com/elizaOS/eliza/issues/3123\\r\\n<!-- This risks section\"\n    },\n    {\n      \"title\": \"fix: typos in multiple files\",\n      \"prNumber\": 3111,\n      \"type\": \"bugfix\",\n      \"body\": \"- **index.ts**: Fixed `\\\"reponse\\\"` \u2192 `\\\"response\\\"`.\\r\\n- **README.md**: Fixed `\\\"conenct\\\"` \u2192 `\\\"connect\\\"`.\\r\\n- **GoplusSecurityService.ts**: Fixed `\\\"invaild\\\"` \u2192 `\\\"invalid\\\"` in error message.\\r\\n- **api.ts**: Fixed `\\\"RESPOURCE_REPONSE_TYPE\\\"` \u2192 `\\\"RESO\"\n    },\n    {\n      \"title\": \"chore: dev => main 0.1.9\",\n      \"prNumber\": 2361,\n      \"type\": \"other\",\n      \"body\": \"changelog\\r\\n- #2167\\r\\n- #2199\\r\\n- #2211\\r\\n- #2213\\r\\n- #2186\\r\\n- #2221\\r\\n- #1369\\r\\n- #2229\\r\\n- #2228\\r\\n- #2243\\r\\n- #2207\\r\\n- #2260\\r\\n- #2262\\r\\n- #2266\\r\\n- #2010?\\r\\n- #2264\\r\\n- #2256\\r\\n- #2255\\r\\n- #2268\\r\\n- #2232\\r\\n- #2240\\r\\n- #1482\\r\\n- #1710\\r\\n- #1442\\r\\n- #1417\\r\\n- #\"\n    },\n    {\n      \"title\": \"chore(fix): need to build core first + added `build:core`\",\n      \"prNumber\": 3398,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix build `bun run build` in root\",\n      \"prNumber\": 3396,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: cli build and init command\",\n      \"prNumber\": 3378,\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): Refactor generation to reflect handler pattern\",\n      \"prNumber\": 3376,\n      \"type\": \"refactor\",\n      \"body\": \"This PR implements a 'handlers' which can be used to hook in services\"\n    },\n    {\n      \"title\": \"Try loading character path from repo root\",\n      \"prNumber\": 3375,\n      \"type\": \"other\",\n      \"body\": \"This allows the user to specify character paths relative to the repository root:\\r\\n\\r\\n```\\r\\nbun run agent -- -- --character=./characters/trump.character.json\\r\\n```\\r\\n\\r\\nWe add `${cwd}../..` to the list of paths to try, to move up from `packages/a\"\n    },\n    {\n      \"title\": \"Fix yargs slice in character loading\",\n      \"prNumber\": 3374,\n      \"type\": \"bugfix\",\n      \"body\": \"To run an agent with a custom character you currently have to do (to escape a few layers of args parsing):\\r\\n\\r\\n```\\r\\nbun run agent -- -- --character=./characters/trump.character.json\\r\\n```\\r\\n\\r\\nHowever, this `yargs` parse slices off the argument\"\n    },\n    {\n      \"title\": \"fix build in core to target node23\",\n      \"prNumber\": 3371,\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\": \"resolve merge conflict\",\n      \"prNumber\": 3367,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"support anthropic provider\",\n      \"prNumber\": 3364,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: fix default character\",\n      \"prNumber\": 3345,\n      \"type\": \"bugfix\",\n      \"body\": \"Fix the default character\"\n    },\n    {\n      \"title\": \"feat: remove verifiable inference concept, will be plugin loaded\",\n      \"prNumber\": 3344,\n      \"type\": \"feature\",\n      \"body\": \"This PR removes verifiable inference as a concept, use this as plugin providers, add runtime handler functionality if no dice\"\n    },\n    {\n      \"title\": \"Delete all plugins\",\n      \"prNumber\": 3342,\n      \"type\": \"other\",\n      \"body\": \"This PR deletes virtually all plugins. These will be moved to https://github.com/elizaos-plugins and indepedently maintained.\"\n    },\n    {\n      \"title\": \"chore: develop => main\",\n      \"prNumber\": 3332,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: set package publish access to public\",\n      \"prNumber\": 3330,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: Twitter logging bug\",\n      \"prNumber\": 3327,\n      \"type\": \"bugfix\",\n      \"body\": \"Related issue: https://github.com/elizaOS/eliza/issues/3201\\r\\n\\r\\nThe issue was due to the parsedResponse already being returned as text.\"\n    },\n    {\n      \"title\": \"chore: remove remnant files/folders\",\n      \"prNumber\": 3326,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: add missing version property to package.json\",\n      \"prNumber\": 3325,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: fix typos in plugins.md\",\n      \"prNumber\": 3324,\n      \"type\": \"bugfix\",\n      \"body\": \"description in a title \"\n    },\n    {\n      \"title\": \"docs: fix typos and update functions\",\n      \"prNumber\": 3317,\n      \"type\": \"bugfix\",\n      \"body\": \"I reviewed the entire repository, no more typos found in docs. \\r\\nHope this helps streamline the project!\\r\\nBest regards,\\r\\nBilogweb3\\r\\n\"\n    },\n    {\n      \"title\": \"feat: allow plugins to interact w messangerManager to post on telegram\",\n      \"prNumber\": 3314,\n      \"type\": \"feature\",\n      \"body\": \"allow plugins to interact w messangerManager to post on tg\\r\\n\\r\\nthis allow to call the tg bot and generate messages\\r\\n\\r\\n\\r\\ntwitter client has a similar behaviour where you can access to post tweets\"\n    },\n    {\n      \"title\": \"fix: read modelConfig from character file\",\n      \"prNumber\": 3313,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3233\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. IMO, this is only bringing back intended behaviour\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nadd the `modelConfig` object to the character file schema, so \"\n    },\n    {\n      \"title\": \"fix: models unit test\",\n      \"prNumber\": 3312,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: parsing unit test failure\",\n      \"prNumber\": 3311,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: Fix plugin-solana-v2 package.json\",\n      \"prNumber\": 3308,\n      \"type\": \"bugfix\",\n      \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFixes issue: **Expected double-quoted property name in JSON at position 825** while parsing `{ \\\"name\\\": \\\"@elizaos/plugin-solana-v2' }` in `/home/oxy/everreach-ai-agent/packages/plugin-solana-v2/package.json`.\\r\\n\\r\\n# Risks\\r\\n\"\n    },\n    {\n      \"title\": \"chore: develop => main\",\n      \"prNumber\": 3307,\n      \"type\": \"other\",\n      \"body\": \"Changelog\\r\\n\\r\\n- #3261\\r\\n- #3262\\r\\n- #3269\\r\\n- #3268\\r\\n- #3264\\r\\n- #3258\\r\\n- #3270\\r\\n- #3271\\r\\n- #3278\\r\\n- #3286\\r\\n- #3248\\r\\n- #3283\\r\\n- #3284\\r\\n- #3285\\r\\n- #3238\\r\\n- #3220\\r\\n- #3281\\r\\n- #3306\"\n    },\n    {\n      \"title\": \"chore: bump version to 0.25.6-alpha.1\",\n      \"prNumber\": 3306,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: clean json before normalized\",\n      \"prNumber\": 3301,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: twitter - add actions suppress action ability.\",\n      \"prNumber\": 3286,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\n\\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\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\nWhen actions h\"\n    },\n    {\n      \"title\": \"fix: telegram- add actions suppress action ability.\",\n      \"prNumber\": 3285,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\n\\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\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\nWhen actions h\"\n    },\n    {\n      \"title\": \"fix: discord - add actions suppress action ability.\",\n      \"prNumber\": 3284,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\n\\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\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\nWhen actions h\"\n    },\n    {\n      \"title\": \"fix: quick-intel plugin: optimize template/add suppress init msg\",\n      \"prNumber\": 3283,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow risk, just optimizations\\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\\nImprovements (misc. changes to existing features)\\r\\n\\r\\nadd suppressInitialMessage flag on action\\r\"\n    },\n    {\n      \"title\": \"fix(core): improve OpenAI-like provider endpoint resolution in `generation.ts`\",\n      \"prNumber\": 3281,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nMedium (it's core plugin)\\r\\n\\r\\n# Background\\r\\n\\r\\nWhen configuring an OpenAI-Like Provider, the `generateText` call works, but the `generateObject` call fails. The reason is an endpoint error because `generateTe\"\n    },\n    {\n      \"title\": \"fix: DenyLoginSubtask\",\n      \"prNumber\": 3278,\n      \"type\": \"bugfix\",\n      \"body\": \"related: \\r\\nhttps://github.com/elizaOS/eliza/issues/3112\\r\\nhttps://github.com/elizaOS/eliza/issues/1431\\r\\n\\r\\nPreviously, we removed support for setting Twitter cookies via environment variables since we relied on the cached manager to retrieve \"\n    },\n    {\n      \"title\": \"fix: handleGoogle(options) lost apiKey\",\n      \"prNumber\": 3274,\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\\n`handleGoogle(options)` lost to pass `apiKey`\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nBug fixes\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\n\\r\\nWhen using `google` mod\"\n    },\n    {\n      \"title\": \"chore: fix spelling issues \",\n      \"prNumber\": 3271,\n      \"type\": \"bugfix\",\n      \"body\": \"Is the Title - incorrect\\r\\nAre the Title - correct\\r\\n\\r\\nrun my Marc - incorrect\\r\\nrun by Marc - correct\\r\\n\\r\\noutpair - incorrect\\r\\noutput - correct\\r\\n\\r\\nthe the - incorrect\\r\\nthe - correct\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"docs: fix typos and update broken link in docs\",\n      \"prNumber\": 3270,\n      \"type\": \"bugfix\",\n      \"body\": \"Hi! I corrected typos in multiple documentation files and fixed a broken link in the NEAR Developer Portal reference.\\r\\n- Updated NEAR Developer Portal link.\\r\\n- Fixed typos in multiple docs.\"\n    },\n    {\n      \"title\": \"Fix broken links on contributing.md\",\n      \"prNumber\": 3269,\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\\nN/A (Fixing broken links in documentation)\\r\\n\\r\\n<!-- This risks section must be filled out before the fin\"\n    },\n    {\n      \"title\": \"docs: Add GitHub issues link to CONTRIBUTING.md file\",\n      \"prNumber\": 3268,\n      \"type\": \"feature\",\n      \"body\": \"# What does this PR do?\\r\\nThis PR links the Github issues page in the \\\"Getting Help\\\" section of CONTRIBUTING.md file.\\r\\nHere is a before and after changes:\\r\\n\\r\\nBefore:\\r\\nCreate GitHub issues\\r\\n\\r\\nAfter:\\r\\nCreate [GitHub issues](https://github.com/\"\n    },\n    {\n      \"title\": \"Fix PG query: Use only 'text' subfield name, field name is not needed here\",\n      \"prNumber\": 3264,\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: Dynamic require of \\\"http\\\" is not supported error\",\n      \"prNumber\": 3262,\n      \"type\": \"bugfix\",\n      \"body\": \"When running pnpm start, the following error occurred: (due to new change of this PR: https://github.com/elizaOS/eliza/pull/3211)\\r\\n\\r\\n<img width=\\\"1003\\\" alt=\\\"Screenshot 2025-02-05 at 1 57 20\u202fPM\\\" src=\\\"https://github.com/user-attachments/assets\"\n    },\n    {\n      \"title\": \"fix: pnpm install\",\n      \"prNumber\": 3261,\n      \"type\": \"bugfix\",\n      \"body\": \"fixes a JSON syntax issue in packages/plugin-solana-v2/package.json that caused the following error during pnpm i:\\r\\n\\r\\n<img width=\\\"1006\\\" alt=\\\"Screenshot 2025-02-05 at 1 18 37\u202fPM\\\" src=\\\"https://github.com/user-attachments/assets/4bbf1aba-2e25-\"\n    },\n    {\n      \"title\": \"fix: handle invalid json\",\n      \"prNumber\": 3258,\n      \"type\": \"bugfix\",\n      \"body\": \"related: https://github.com/elizaOS/eliza/issues/3245\"\n    },\n    {\n      \"title\": \"fix: client-alexa\",\n      \"prNumber\": 3255,\n      \"type\": \"bugfix\",\n      \"body\": \"- Add @biomejs/biome as devDependency\\r\\n- Add lint and format scripts\\r\\n- Replace existing ESLint configuration\\r\\n- Standardize tsup dependency version\\r\\n- Fix all small issues\"\n    },\n    {\n      \"title\": \"fix(deps): update dependency vitest [security]\",\n      \"prNumber\": 3254,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR contains the following updates:\\n\\n| Package | Change | Age | Adoption | Passing | Confidence |\\n|---|---|---|---|---|---|\\n| [vitest](https://redirect.github.com/vitest-dev/vitest) ([source](https://redirect.github.com/vitest-dev/vites\"\n    },\n    {\n      \"title\": \"chore: remove unnecessary provider and transfer code\",\n      \"prNumber\": 3251,\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\": \"feat (chore): plugin-cronos test setup and coverage\",\n      \"prNumber\": 3250,\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\\nhttps://github.com/elizaOS/eliza/issues/3249\\r\\n<!-- This risks section\"\n    },\n    {\n      \"title\": \"fix: rag optimizations/fixes for context.\",\n      \"prNumber\": 3248,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Bug fixes and optimizations\\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\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes to exist\"\n    },\n    {\n      \"title\": \"feat (chore) plugin conflux: test config and coverage\",\n      \"prNumber\": 3247,\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\\nhttps://github.com/elizaOS/eliza/issues/3246\\r\\n<!-- This risks section\"\n    },\n    {\n      \"title\": \"fix: broken links in documentation\",\n      \"prNumber\": 3240,\n      \"type\": \"bugfix\",\n      \"body\": \"Hey! This PR fixes several broken links in the documentation. The links now correctly point to the relevant resources.\\r\\n\\r\\n## What's Changed?\\r\\n- Fixed incorrect or outdated URLs leading to non-existent pages.\\r\\n\\r\\nLet me know if there's anythi\"\n    },\n    {\n      \"title\": \"feat: (plugin-multiversx) Allow the use of herotag\",\n      \"prNumber\": 3238,\n      \"type\": \"feature\",\n      \"body\": \"Allow the use of herotag instead of address to send token\\r\\n\\r\\n# Relates to\\r\\n\\r\\nMultiversX plugin\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nIt modify the SEND_TOKEN action to include the use of herotag\\r\\nIt also add the \"\n    },\n    {\n      \"title\": \"fix: fix docker & types issue\",\n      \"prNumber\": 3220,\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\\n1. fix docker (NPMs had new apt requirement)\\r\\n2. \\\"fix\\\" (type ignore) new type issues that were introduced by bumping NPMs\\r\\n3. Properly includes zod (per Shakker's instructions, o\"\n    },\n    {\n      \"title\": \"feat: Add configuration for enabling/disabling Twitter post generation\",\n      \"prNumber\": 3219,\n      \"type\": \"feature\",\n      \"body\": \"Introduced ENABLE_TWITTER_POST_GENERATION config to control automatic tweet generation.\"\n    },\n    {\n      \"title\": \"chore: develop => main\",\n      \"prNumber\": 3216,\n      \"type\": \"other\",\n      \"body\": \"changelog\\r\\n- #3111\\r\\n- #3122\\r\\n- #3146\\r\\n- #3180\\r\\n- #3179\\r\\n- #3181\\r\\n- #3178\\r\\n- #3175\\r\\n- #3174\\r\\n- #3172\\r\\n- #3171\\r\\n- #3169\\r\\n- #3165\\r\\n- #3134\\r\\n- #3124\\r\\n- #3126\\r\\n- #3189\\r\\n- #3190\\r\\n- #3170\\r\\n- #3045\\r\\n- #3096\\r\\n- #3198\\r\\n- #3186\\r\\n- #3107\\r\\n- #3207\\r\\n- #3\"\n    },\n    {\n      \"title\": \"fix: remove duplicated dependencies\",\n      \"prNumber\": 3215,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: rename chat_2024-11-17.md\",\n      \"prNumber\": 3210,\n      \"type\": \"docs\",\n      \"body\": \"CONTRIBUTION.MD - CONTRIBUTING.md\"\n    },\n    {\n      \"title\": \"feat: Add CREATE_POOL action in MultiversX plugin\",\n      \"prNumber\": 3209,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\n\\r\\nMultiversX Plugin\\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\\nIt adds the CREATE_POOL feature witch trigger the following transactions on chain:\\r\\n- wrapEgld (optionnal)\\r\\n- createPair\\r\\n- \"\n    },\n    {\n      \"title\": \"fix: quick-intel plugin optimizations & fixes.\",\n      \"prNumber\": 3208,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow: Optimizations and fixes\\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\\nBug fixes (non-breaking change which fixes an issue)\\r\\n\\r\\n## Why are we doing this? Any context o\"\n    },\n    {\n      \"title\": \"docs: Update faq.md\",\n      \"prNumber\": 3207,\n      \"type\": \"docs\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: Fix Typos and Improve Consistency in Community Chat Logs\",\n      \"prNumber\": 3206,\n      \"type\": \"bugfix\",\n      \"body\": \"## **Description**\\r\\nThis pull request corrects minor typos, improves consistency in terminology, and enhances readability across multiple community chat logs. The changes include:\\r\\n\\r\\n- **Fixed spelling mistakes** (e.g.,*solona* \u2192 *Solana*, \"\n    },\n    {\n      \"title\": \"docs: Add weekly contributor meeting notes\",\n      \"prNumber\": 3204,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\nDocumentation updates - Adding weekly contributor meeting notes\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding meeting notes.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds meeting notes for two weekly contrib\"\n    },\n    {\n      \"title\": \"fix: think tag from venice\",\n      \"prNumber\": 3203,\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\\nResponse from Venice model.\\r\\n\\r\\n```\\r\\n<think>\\r\\nargs\\r\\n</think>\\r\\n\\r\\n```\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\"\n    },\n    {\n      \"title\": \"docs: Update Twitter to X (Twitter)\",\n      \"prNumber\": 3198,\n      \"type\": \"docs\",\n      \"body\": \"Since Twitter is now rebranded to X, so I have changes made changes in the README file. It is now \\\"X (Twitter)\\\" and I kept the Twitter keyword since people still use the word Twitter.\\r\\n\\r\\n#3196 \"\n    },\n    {\n      \"title\": \"fix: Slack download upload attachments\",\n      \"prNumber\": 3194,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nDidn't create an issue, but basically actions like \\\"describe an image\\\" is not working using the Slack client. \\r\\nThe raw attachment Slack ID is set to describe an image, which cannot proceed.\\r\\n\\r\\nSimilarly, when using actions \"\n    },\n    {\n      \"title\": \"fix: extract attribute from raw text instead of normalized json\",\n      \"prNumber\": 3190,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: update provider-utils\",\n      \"prNumber\": 3189,\n      \"type\": \"bugfix\",\n      \"body\": \"We encountered an issue where the app couldn't start due to the following error:\\r\\n\\r\\n<img width=\\\"798\\\" alt=\\\"Screenshot 2025-02-03 at 1 06 40\u202fPM\\\" src=\\\"https://github.com/user-attachments/assets/09c280f4-3937-4b07-a876-a3a4c6bed1f5\\\" />\\r\\n\\r\\nThis \"\n    },\n    {\n      \"title\": \"chore: add Biome configuration to Solana ecosystem plugins 07\",\n      \"prNumber\": 3186,\n      \"type\": \"feature\",\n      \"body\": \"Add Biome linting and formatting configuration to the following plugins:\\r\\n- plugin-solana-v2\\r\\n- plugin-solana-agent-kit\\r\\n- plugin-solana\\r\\n- plugin-sgx\\r\\n\\r\\nChanges include:\\r\\n- Add @biomejs/biome as devDependency\\r\\n- Add lint and format scripts\"\n    },\n    {\n      \"title\": \"feat: coingecko advanced -  various pools by network\",\n      \"prNumber\": 3170,\n      \"type\": \"feature\",\n      \"body\": \"Get trending pools on coingecko by specific network\\r\\n\\r\\nGet New pools on coingecko by specific network\"\n    },\n    {\n      \"title\": \"chore: Update GitHub Actions workflows and documentation\",\n      \"prNumber\": 3166,\n      \"type\": \"docs\",\n      \"body\": \"\\r\\nChanges:\\r\\n1. .github/workflows/image.yaml\\r\\n- Old: \\\"Container registry registry\\\"\\r\\n- New: \\\"Container registry\\\"\\r\\n- Why: Remove duplicate word for better readability\\r\\n\\r\\n2. .github/workflows/pr.yaml  \\r\\n- Old: actions/checkout@v3\\r\\n- New: action\"\n    },\n    {\n      \"title\": \"chore: Standardization of Security Check Identifiers across GoPlus plugin\",\n      \"prNumber\": 3164,\n      \"type\": \"other\",\n      \"body\": \"This PR updates the `ADRESS_SECURITY_CHECK` identifier across multiple files in the GoPlus plugin to ensure consistency and alignment with the correct naming convention. The change improves code clarity and reduces potential confusion in re\"\n    },\n    {\n      \"title\": \"fix: Update pnpm version during Docker build\",\n      \"prNumber\": 3158,\n      \"type\": \"bugfix\",\n      \"body\": \"Update pnpm version in docker build progress. Cause 9.4.0 is too low, comes out patch errors.\"\n    },\n    {\n      \"title\": \"Fix README_JA.md (add unwritten text and fix typo)\",\n      \"prNumber\": 3153,\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\\nnone\\r\\n\\r\\n# Risks\\r\\n\\r\\nnone\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nI fix README_JA typo and add unwritt\"\n    },\n    {\n      \"title\": \"chore: some fix after v0.1.9\",\n      \"prNumber\": 3141,\n      \"type\": \"bugfix\",\n      \"body\": \"1. update default_log_level to info \\r\\n2. display tips after default agent started\\r\\n3. before onchain json loading checking the wallet address.\\n4. default value should be empty value \"\n    },\n    {\n      \"title\": \"fix: remove duplicated plugins\",\n      \"prNumber\": 3126,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: Trump character but tweets in Spanish by default\",\n      \"prNumber\": 3119,\n      \"type\": \"feature\",\n      \"body\": \"<!-- Use this template by filling in information and copy and pasting relevant items out of the html comments. -->\\r\\n# Background\\r\\nBillions of people are not native English speakers & a template is needed to make it easier for anyone to crea\"\n    },\n    {\n      \"title\": \"clean up\",\n      \"prNumber\": 3116,\n      \"type\": \"refactor\",\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(reduce-providers): Generic Model Loading (OpenAI compatible endpoints)\",\n      \"prNumber\": 3114,\n      \"type\": \"other\",\n      \"body\": \"# Generic Model Loading System Implementation\\r\\n\\r\\n## Overview\\r\\nThe PR implements a generic model loading system with OpenAI-compatible endpoints.\\r\\n\\r\\n## Key Changes\\r\\n\\r\\n### 1. Unified Provider Configuration\\r\\n- Simplified provider setup using:\\r\"\n    },\n    {\n      \"title\": \"fix: plugin-anyone\",\n      \"prNumber\": 3107,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed all the issues and retouch a bit te code in in Anyone Plugin\"\n    },\n    {\n      \"title\": \"feat: plugin desk exchange\",\n      \"prNumber\": 3096,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to  \\r\\nN/A - New plugin contribution  \\r\\n\\r\\n# Risks  \\r\\n**Low**  \\r\\n- Only interacts with public DESK Exchange API endpoints  \\r\\n- Requires explicit private key configuration  \\r\\n- Has clear error handling  \\r\\n\\r\\n# Background  \\r\\n\\r\\n## What \"\n    },\n    {\n      \"title\": \"feat: Add edwin plugin to eliza\",\n      \"prNumber\": 3045,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to https://github.com/elizaOS/eliza/issues/3040\\r\\n\\r\\n<img width=\\\"810\\\" alt=\\\"image\\\" src=\\\"https://github.com/user-attachments/assets/faa1236c-2d32-4a4a-8ea2-0cff73da2679\\\" />\\r\\n\\r\\n# Risks\\r\\n\\r\\nThis plugin gives agents the ability to perform\"\n    },\n    {\n      \"title\": \"feat: Replace pnpm with Bun\",\n      \"prNumber\": 2852,\n      \"type\": \"feature\",\n      \"body\": \"This PR replaces pnpm with bun. Bun is faster and enables cool future stuff, like runtime loading of typescript.\\r\\n\\r\\nThis PR needs to be tested as it could cause some breaking issues in CI.\"\n    },\n    {\n      \"title\": \"chore: gui enhancements\",\n      \"prNumber\": 3727,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: disable agents in agent table before startup\",\n      \"prNumber\": 3726,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: Add rolodex\",\n      \"prNumber\": 3725,\n      \"type\": \"feature\",\n      \"body\": \"This PR adds a whole bunch of stuff. `Entities` now have `components`, which are bits of information that can be added to entities-- currently used for adding new contact info to the entity.\\r\\n\\r\\nRelationships are set up and working now, and \"\n    },\n    {\n      \"title\": \"fix: fix 0.25.8 oom bug\",\n      \"prNumber\": 3722,\n      \"type\": \"bugfix\",\n      \"body\": \"Current tag version v0.25.8 has oom bug with me.\\r\\nJust repair some block logic. \"\n    },\n    {\n      \"title\": \"fix: update character\",\n      \"prNumber\": 3717,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: tests favor local paths for consistency / adjust deps\",\n      \"prNumber\": 3716,\n      \"type\": \"tests\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: format pass\",\n      \"prNumber\": 3715,\n      \"type\": \"other\",\n      \"body\": \"# Risks\\r\\n\\r\\nLow\\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\\nUpdates (new versions of included code)\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\n\\r\\nKeep the code formatted, since our pipelin\"\n    },\n    {\n      \"title\": \"fix: clean up `pnpm clean` output and make `pnpm dev` faster on faster CPUs\",\n      \"prNumber\": 3714,\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\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\\n## Why are we doing this? Any context or related work?\\r\\n\\r\\nerrors/warnings make the project\"\n    },\n    {\n      \"title\": \"feat: ANTHROPIC_API_URL env.\",\n      \"prNumber\": 3711,\n      \"type\": \"feature\",\n      \"body\": \"Adds ANTHROPIC_API_URL to envs so can call other proxy AI endpoints.\\r\\n\\r\\nodi edit/note:\\r\\nEnables custom proxies for usage tracking/introspection\"\n    },\n    {\n      \"title\": \"fix: character creator\",\n      \"prNumber\": 3710,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat(agent): consolidate character/agent handling\",\n      \"prNumber\": 3708,\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  - Launched new character management views for creating, editing, and listing characters.\\n  - Introduced chat room m\"\n    },\n    {\n      \"title\": \"refactor: plugin local ai new\",\n      \"prNumber\": 3704,\n      \"type\": \"refactor\",\n      \"body\": \"Local models run with cache and models folder empty take some minutes. \\r\\nAll models and the tokenizer are DL into the models folder\\r\\nAll the files that we use for testing are into the cache folder. \\r\\nAt startup all the services are tested. \"\n    },\n    {\n      \"title\": \"lint and turbo fixes\",\n      \"prNumber\": 3703,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: submit update env for plugin viction\",\n      \"prNumber\": 3701,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\nhttps://github.com/elizaOS/eliza/pull/3701\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nIt adds support for Viction provider.\\r\\n\\r\\n## What kind of change is this?\\r\\nFeatures (non-breaking change which adds functio\"\n    },\n    {\n      \"title\": \"chore: security NPM updates / bump turbo\",\n      \"prNumber\": 3700,\n      \"type\": \"other\",\n      \"body\": \"- `pnpm audit --fix`\\r\\n- bump turbo from 2.4.2 to 2.4.4\\r\\n- ~~attempt to fix CI~~ remove unneeded dependencies in core/client-direct\"\n    },\n    {\n      \"title\": \"fix: CLI - escape paths with spaces correctly\",\n      \"prNumber\": 3699,\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\\n## What kind of change is this?\\r\\n\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\nMy changes do not require a change to the project do\"\n    },\n    {\n      \"title\": \"feat: better plugin loading error handling / json5 support for character file\",\n      \"prNumber\": 3698,\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\\n- convert character to json5 (allows comments and new lines, more human friendly format)\\r\\n- better error handling of plugins loading\\r\\n- logging updates\\r\\n\\r\\n## What kind of change \"\n    },\n    {\n      \"title\": \"feat: CLI install improvements\",\n      \"prNumber\": 3697,\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\\n- makes install/add on par with remove, not requiring `@elizaos-plugins/` prefix\\r\\n- skips pnpm adding to agent's package.json if it's already a dependency\\r\\n\\r\\n## What kind of chan\"\n    },\n    {\n      \"title\": \"chore: Update docs, adds changelog notes, merges pages, cleanup\",\n      \"prNumber\": 3694,\n      \"type\": \"refactor\",\n      \"body\": \"Did some merging of pages that had redundant information and general cleanup, added embedded videos, changelog page, script for updating changelog, and general cleanup.\"\n    },\n    {\n      \"title\": \"fix agent cli\",\n      \"prNumber\": 3691,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: mock agent form on client!\",\n      \"prNumber\": 3690,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: Performance Improvements and Metadata Refactoring\",\n      \"prNumber\": 3688,\n      \"type\": \"feature\",\n      \"body\": \"This PR contains several improvements to the application:\\r\\n\\r\\nReduces response latency by optimizing the shouldRespondHandler\\r\\nAdds debouncing to the message receive handler to prevent excessive processing\\r\\nRefactors name and username fields\"\n    },\n    {\n      \"title\": \"fix: media download action\",\n      \"prNumber\": 3687,\n      \"type\": \"bugfix\",\n      \"body\": \"In the current branch, the video service fails due to a missing yt-dlp dependency in the youtube-dl-exec module. This happens because Bun does not install yt-dlp automatically unless you manually navigate to the youtube-dl-exec folder and r\"\n    },\n    {\n      \"title\": \"feat: Add post-processing support for character loading\",\n      \"prNumber\": 3686,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\n\\r\\nn/a\\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\\n- Introduce `handlePostCharacterLoaded` method in agent startup process\\r\\n- Add optional `postProcessors` and `handlePostCharacterLoaded` to Character and P\"\n    },\n    {\n      \"title\": \"docs: fix broken links in README\",\n      \"prNumber\": 3684,\n      \"type\": \"bugfix\",\n      \"body\": \"Fix broken link\\r\\n\"\n    },\n    {\n      \"title\": \"feat: Add roles, ownership state and world settings to core\",\n      \"prNumber\": 3682,\n      \"type\": \"feature\",\n      \"body\": \"This PR moves roles, onboarding and server ownership state to core. This is still pretty WIP but should be expanded upon as the swarm agents are developed\\r\\n\\r\\nWorlds represent servers or other collections of entities with rooms in them\\r\\nAcco\"\n    },\n    {\n      \"title\": \"fix: PDF Message Sending Failure & getInstance Bug\",\n      \"prNumber\": 3681,\n      \"type\": \"bugfix\",\n      \"body\": \"1. Fix App Crash When Sending a PDF Message with No Text\\r\\nCurrently, sending a PDF message without any accompanying text causes the app to crash due to this line:\\r\\n[packages/core/src/memory.ts#L100](https://github.com/elizaOS/eliza/blob/5f1\"\n    },\n    {\n      \"title\": \"fix: discord voiceJoin/voiceLeave action\",\n      \"prNumber\": 3680,\n      \"type\": \"bugfix\",\n      \"body\": \"Currently, the actions in Discord are broken. This PR aims to fix the voiceJoin and voiceLeave actions.\\r\\n\\r\\nThe voiceJoin and voiceLeave actions were not working due to minor typos and undefined variables. This PR fixes these issues. Additio\"\n    },\n    {\n      \"title\": \"fix: character knowledge add directory\",\n      \"prNumber\": 3678,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\nCharacter config in file ts\\r\\n\\r\\n# Risks\\r\\nmedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nupdate knowledge in type Character\\r\\n\\r\\n## What kind of change is this?\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\n\\r\\n<!-- \"\n    },\n    {\n      \"title\": \"fix: twitter crash issue\",\n      \"prNumber\": 3677,\n      \"type\": \"bugfix\",\n      \"body\": \"The Twitter app fails to start due to this line: https://github.com/elizaOS/eliza/blob/5c1b5899cfb3bb5ec78ffecf8530a9ba19f29a35/packages/core/src/runtime.ts#L936\\r\\n\\r\\nFix:\\r\\nThis PR prevents the agent from connecting to itself, resolving the i\"\n    },\n    {\n      \"title\": \"fix: tg vitest\",\n      \"prNumber\": 3676,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: re-init migration issue\",\n      \"prNumber\": 3674,\n      \"type\": \"bugfix\",\n      \"body\": \"## Risks\\r\\nLow. This PR reduces risks related to database schema initialization and migration conflicts by properly integrating manual database configurations into Drizzle's migration system.\\r\\n\\r\\n## Background\\r\\n\\r\\n### What does this PR do?\\r\\nTh\"\n    },\n    {\n      \"title\": \"fix: fix CLI install\",\n      \"prNumber\": 3673,\n      \"type\": \"bugfix\",\n      \"body\": \"fixes issue introduced in #3660 \"\n    },\n    {\n      \"title\": \"fix: pglite & migrations\",\n      \"prNumber\": 3672,\n      \"type\": \"bugfix\",\n      \"body\": \"# Risks\\r\\nLow - Changes are limited to PGlite migrations with a code-first approach\\r\\n\\r\\n# Background\\r\\n## What does this PR do?\\r\\nFixes PGlite migrations and implements a code-first approach for SQL across the system. Specifically:\\r\\n* Adds supp\"\n    },\n    {\n      \"title\": \"fix: add participant error\",\n      \"prNumber\": 3671,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: Update README_KOR.md\",\n      \"prNumber\": 3670,\n      \"type\": \"docs\",\n      \"body\": \"Translation change to make it more natural in Korean language. and direct translate on things\\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\\ntranslat\"\n    },\n    {\n      \"title\": \"fix: set up dimension before starting client\",\n      \"prNumber\": 3668,\n      \"type\": \"bugfix\",\n      \"body\": \"![image](https://github.com/user-attachments/assets/cc048238-5964-45fc-9aa0-34fefbb699c3)\\r\\n\"\n    },\n    {\n      \"title\": \"clean up server\",\n      \"prNumber\": 3667,\n      \"type\": \"refactor\",\n      \"body\": \"cleans up server\\r\\n\\r\\nTODO; Add hyperfy, whisper services later\"\n    },\n    {\n      \"title\": \"Fix extension and migrations\",\n      \"prNumber\": 3665,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore:(refactor) - plugin-local-ai-final\",\n      \"prNumber\": 3663,\n      \"type\": \"refactor\",\n      \"body\": \"The Local AI run on R1 models from Deepseek.\\r\\nAll the features are tested but the TTS.\\r\\nAdded the mananer for the Studio LM \\r\\nAdded the manager for the Ollama (very bad performances) \\r\\n\\r\\n\\n\\n<!-- This is an auto-generated comment: release not\"\n    },\n    {\n      \"title\": \"fix: [twitter-space] handle speaker removal\",\n      \"prNumber\": 3662,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: checking the plugin is installed and display the result\",\n      \"prNumber\": 3660,\n      \"type\": \"feature\",\n      \"body\": \"When use cli list plugins we can also display the installed checking result like this : \\r\\n\\r\\n```\\r\\nAvailable plugins:\\r\\n     @elizaos-plugins/adapter-mongodb \\r\\n     @elizaos-plugins/adapter-pglite \\r\\n     @elizaos-plugins/adapter-postgres \\r\\n   \"\n    },\n    {\n      \"title\": \"fix: twitter small fix\",\n      \"prNumber\": 3659,\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  - Twitter posting is now activated only when explicitly started, providing users with greater control over operatio\"\n    },\n    {\n      \"title\": \"Fix Typographical Errors in Documentation\",\n      \"prNumber\": 3656,\n      \"type\": \"bugfix\",\n      \"body\": \"This pull request addresses minor typographical errors in the documentation files. \\r\\nSpecifically, it corrects the wording in the contributing guidelines and ensures consistency in the character file format.\\r\\n\\r\\n**Changes made:**\\r\\n- Updated \"\n    },\n    {\n      \"title\": \"feat: space action\",\n      \"prNumber\": 3655,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: Handle short text items in knowledge processing\",\n      \"prNumber\": 3652,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\nNo linked issue. This PR addresses a bug found in knowledge processing.\\r\\n\\r\\n# Risks\\r\\nLow. Only affects how short text items are processed, with a small isolated change to prevent errors.\\r\\n\\r\\n# Background\\r\\n## What does this PR do\"\n    },\n    {\n      \"title\": \"refactor api routes into file based\",\n      \"prNumber\": 3651,\n      \"type\": \"refactor\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: Fix plugins.md formatting\",\n      \"prNumber\": 3649,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed a formatting issue in the `docs/packages/plugin.md` to improve readability.\\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\\nL\"\n    },\n    {\n      \"title\": \"feat: add agent server opitons with middleware settings\",\n      \"prNumber\": 3648,\n      \"type\": \"feature\",\n      \"body\": \"Many developers may want to much  control the agent server. And the middlreware in express can be sollution. It helps inject developer custom code to the agent server.  \\r\\n\\r\\nUse cases: \\r\\nIf developer want  user's logined wallet address for a\"\n    },\n    {\n      \"title\": \"chore: stablize develop\",\n      \"prNumber\": 3645,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: generate structured objects and images with NEAR AI\",\n      \"prNumber\": 3644,\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\\nhttps://github.com/elizaOS/eliza/pull/3275\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This PR fixes a bug we encountered when t\"\n    },\n    {\n      \"title\": \"update discord link\",\n      \"prNumber\": 3643,\n      \"type\": \"other\",\n      \"body\": \"Update discord link to elizaOS\"\n    },\n    {\n      \"title\": \"chore: remove langchain dependency for text splitting\",\n      \"prNumber\": 3642,\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\\nSolves the issue #2917  \\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: Add database adapter and plugin adapter types to core types\",\n      \"prNumber\": 3640,\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[Issue #3639](https://github.com/elizaOS/eliza/issues/3639)\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n# Background\\r\\nAdapter is\"\n    },\n    {\n      \"title\": \"feat: Add `agent` table and rename `user` to `entity` table, add multi-tenancy\",\n      \"prNumber\": 3637,\n      \"type\": \"feature\",\n      \"body\": \"This PR splits the `users` table into `agents` and `entities`. Entities is a more general term which could encompass non-user objects in the future.\\r\\nPlatform-specific user data is stored in the `metadata` field.\\r\\nAgents can be `enabled` wh\"\n    },\n    {\n      \"title\": \"fix: twitter client embedding dimension\",\n      \"prNumber\": 3625,\n      \"type\": \"bugfix\",\n      \"body\": \"I encountered an issue where the app crashes when using the Twitter client at startup. The crash appears to be caused by an embedding dimension mismatch. I believe this happens because the Twitter client starts posting and create memory wit\"\n    },\n    {\n      \"title\": \"fix: Telegram E2E Test and Group Chat Issue\",\n      \"prNumber\": 3624,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR fixes the E2E test for Telegram by adding the chat attribute to the mocked message.\\r\\n\\r\\nAdditionally, the Telegram agent isn't working in my group chat (chat.type = \\\"group\\\") due to an undefined issue at this [line](https://github.com\"\n    },\n    {\n      \"title\": \"fix: social vitest\",\n      \"prNumber\": 3622,\n      \"type\": \"bugfix\",\n      \"body\": \"Resolves all Vitest errors by updating the test code to align with the changes introduced in PR [#3602.](https://github.com/elizaOS/eliza/pull/3602)\\r\\n\\r\\nIncludes changes from PRs: https://github.com/elizaOS/eliza/pull/3625, https://github.co\"\n    },\n    {\n      \"title\": \"fix: importing plugins from registry\",\n      \"prNumber\": 3611,\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\\nhttps://github.com/elizaOS/eliza/issues/3610\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks secti\"\n    },\n    {\n      \"title\": \"refactor: memory queries, knowledge metadata, and browser support\",\n      \"prNumber\": 3606,\n      \"type\": \"refactor\",\n      \"body\": \"This PR introduces three key architectural improvements:\\r\\n\\r\\n\ud83d\udd0d Memory System Enhancement\\r\\n- Made agent ID optional in memory operations\\r\\n- Added support for global memory queries\\r\\n- Enhanced memory retrieval flexibility\\r\\n\\r\\n\ud83d\udcca Knowledge Meta\"\n    },\n    {\n      \"title\": \"feat: add pglite support & database design\",\n      \"prNumber\": 3598,\n      \"type\": \"feature\",\n      \"body\": \"## What does this PR do?\\r\\n\\r\\nThis PR refactors our database layer to support both PostgreSQL and PGLite using an injectable connection manager pattern with Drizzle ORM. The main challenge has been fixed by streamlining connection management \"\n    },\n    {\n      \"title\": \"chore: develop => main (0.25.8 release)\",\n      \"prNumber\": 3522,\n      \"type\": \"other\",\n      \"body\": \"Changelog:\\r\\n- #3339\\r\\n- #3343\\r\\n- #3344\\r\\n- #3345\\r\\n- #3346\\r\\n- #3357\\r\\n- #3429\\r\\n- #3457\\r\\n- #3453\\r\\n- #3414\\r\\n- #3410\\r\\n- #3407\\r\\n- #3435\\r\\n- #3489\\r\\n- #3501\\r\\n- #3494\\r\\n- #3484\\r\\n- #3428\\r\\n- #3509\\r\\n- #3291\\r\\n- #2958\\r\\n- #3523\\r\\n- #3553\\r\\n- #3539\\r\\n- #3532\\r\\n- #\"\n    },\n    {\n      \"title\": \"docs: Update readme to clarify difference between eliza-starter and eliza repos\",\n      \"prNumber\": 3453,\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\\nhttps://github.com/elizaOS/eliza/issues/3387\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this P\"\n    },\n    {\n      \"title\": \"chore: Add adapter-sqlite to deps\",\n      \"prNumber\": 3357,\n      \"type\": \"feature\",\n      \"body\": \"This fixes `adapter-sqlite` not loading as the default adapter (occurs when no other plugins provide it).\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/blob/6f40883c7ae5bdb491a55753562785c40eaa7432/agent/src/index.ts#L678\\r\\n\\r\\nNote `adapter-sqlite` is \"\n    },\n    {\n      \"title\": \"chore: Remove plugin imports from agent\",\n      \"prNumber\": 3346,\n      \"type\": \"other\",\n      \"body\": \"Cleanup. Remove dead monorepo plugin imports from `agent` source.\"\n    },\n    {\n      \"title\": \"chore: move default character to agent\",\n      \"prNumber\": 3343,\n      \"type\": \"other\",\n      \"body\": \"Move the default character into the agent\"\n    },\n    {\n      \"title\": \"feat: Dynamic Plugin Loading (merged_)\",\n      \"prNumber\": 3339,\n      \"type\": \"feature\",\n      \"body\": \"Merges develop onto:\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/3336\\r\\n\\r\\nSuccessfully works on my machine\"\n    },\n    {\n      \"title\": \"feat: configuration: Set Lava as the default RPC URL for NEAR and Starknet\",\n      \"prNumber\": 3323,\n      \"type\": \"feature\",\n      \"body\": \"**Relates to**\\r\\nN/A\\r\\n\\r\\n**Risks**\\r\\nLow\\r\\n\\r\\n**Background / What does this PR do?**\\r\\nThis PR updates the default RPC URLs for NEAR and Starknet to use Lava.\\r\\n\\r\\n**What kind of change is this?**\\r\\nImprovements (configuration changes)\\r\\n\\r\\n**Document\"\n    },\n    {\n      \"title\": \"feat: Enable fetching relevant facts in the facts provider.\",\n      \"prNumber\": 2635,\n      \"type\": \"feature\",\n      \"body\": \"For some reason this was commented out. It looks like a great feature to include. Fetching relevant facts in addition to most recent facts is a good idea. I un-commented the code and renamed _embedding to embedding. \"\n    },\n    {\n      \"title\": \"fix: update chunk & Overlap in rag function\",\n      \"prNumber\": 2525,\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\\nRAG Chunk & Overlap increase\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled \"\n    },\n    {\n      \"title\": \"chore: turbo optimizations\",\n      \"prNumber\": 2503,\n      \"type\": \"other\",\n      \"body\": \"non critical improvments \\r\\n1)duplicate tasks for @elizaos/client-direct#build were identified in the configuration\\r\\n2)enable caching\\r\\n3)all changes were aimed at improving performance\\n\\n<!-- This is an auto-generated comment: release notes b\"\n    },\n    {\n      \"title\": \"feat: replace AgentRuntime to his interface to extend client\",\n      \"prNumber\": 2388,\n      \"type\": \"feature\",\n      \"body\": \"This allow to use different type of AgentRuntime that follow original IAgentRuntime interface\"\n    },\n    {\n      \"title\": \"fix: client speech to text\",\n      \"prNumber\": 3461,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: client speech to text\",\n      \"prNumber\": 3454,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: tg vitest\",\n      \"prNumber\": 3524,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: bump version & lockfile\",\n      \"prNumber\": 3523,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: add elevenlabs default voice\",\n      \"prNumber\": 3519,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: discord test\",\n      \"prNumber\": 3518,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: refactor string literal `http://localhost` with `SERVER_URL` env var in client\",\n      \"prNumber\": 3511,\n      \"type\": \"bugfix\",\n      \"body\": \"# Risks\\r\\nLow, literal is moved to short circuit fallback from the .env var.\\r\\n\\r\\n# Background\\r\\nI run Eliza on my home lab. I run the client on my pc. This lets me target my homelab eliza server\\r\\n\\r\\n## What does this PR do?\\r\\nIntroduces a new en\"\n    },\n    {\n      \"title\": \"chore: move characters out to submodule\",\n      \"prNumber\": 3509,\n      \"type\": \"other\",\n      \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Makes character repo official & updates workflows to init/update submodules\\r\\n- Also cleans out the adapters directories\\r\\n- Adds remove plugin support to CLI tool\\r\\n- Fixes expre\"\n    },\n    {\n      \"title\": \"docs: New remote deployment guide\",\n      \"prNumber\": 3501,\n      \"type\": \"docs\",\n      \"body\": \"# Relates to\\r\\n\\r\\nDocumentation\\r\\n\\r\\nAdds a new guide for deployment to a remote server\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, just adds a markdown file\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdds a single file to docs/docs/guides\\r\\n\\r\\n## What kind of change\"\n    },\n    {\n      \"title\": \"feat: enhance discord test\",\n      \"prNumber\": 3498,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: added right params for caching, length, for local embed on anthropic\",\n      \"prNumber\": 3497,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: client UI\",\n      \"prNumber\": 3496,\n      \"type\": \"bugfix\",\n      \"body\": \"The client is currently broken, and I'm facing this issue:\\r\\n\\r\\n<img width=\\\"591\\\" alt=\\\"Screenshot 2025-02-14 at 3 55 56\u202fPM\\\" src=\\\"https://github.com/user-attachments/assets/5dfe3935-6683-4e15-8e15-48fdaacafa80\\\" />\\r\\n\\r\\nUpgrading React in the docs\"\n    },\n    {\n      \"title\": \"chore: completed test suite for open-ai\",\n      \"prNumber\": 3495,\n      \"type\": \"tests\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: adding compass plugin env vars\",\n      \"prNumber\": 3494,\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\\nhttps://github.com/elizaOS/eliza/issues/3492\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section\"\n    },\n    {\n      \"title\": \"fix: ensure test runner continues execution after failures\",\n      \"prNumber\": 3490,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: fix incorrect image paths in Korean documentation\",\n      \"prNumber\": 3489,\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\\ncloses #3479 \\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow \u2013 This PR only updates documentation and does not affect any functi\"\n    },\n    {\n      \"title\": \"docs: Add weekly contributor meeting notes (2025-02-04 + 2025-02-11)\",\n      \"prNumber\": 3484,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\nDocumentation updates for weekly contributor meetings\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding new meeting notes.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds two new weekly contributor meeting notes:\\r\"\n    },\n    {\n      \"title\": \"docs: Added a Proper Ukrainian README Translation Create README_UA.md\",\n      \"prNumber\": 3483,\n      \"type\": \"docs\",\n      \"body\": \"## What does this PR do?\\r\\n\\r\\nI\u2019ve translated the README into Ukrainian to make it more accessible.\\r\\nThe translation stays true to the original while ensuring clarity and natural flow \ud83d\ude80\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"feat: discord test\",\n      \"prNumber\": 3478,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: add anthropic local embedding + misc\",\n      \"prNumber\": 3474,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: add tests for anthropic and improve oai test\",\n      \"prNumber\": 3472,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: add basic tests to openai plugin\",\n      \"prNumber\": 3466,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: just minor biome pref'd lint issues\",\n      \"prNumber\": 3462,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: commit d.a.t.a env configurations\",\n      \"prNumber\": 3457,\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- Connected to merged plugin implementation: [elizaos-plugins/registry#43](https://github.com/elizaos-plu\"\n    },\n    {\n      \"title\": \"feat: elevenlabs plugin\",\n      \"prNumber\": 3452,\n      \"type\": \"feature\",\n      \"body\": \"related: https://linear.app/eliza-labs/issue/ELI2-35/implement-elevenlabs-plugin\"\n    },\n    {\n      \"title\": \"chore: sqlite tests\",\n      \"prNumber\": 3445,\n      \"type\": \"tests\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: db path resolution\",\n      \"prNumber\": 3438,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: refactor + fixes to chat bubble ui + lint fixes + cleanup\",\n      \"prNumber\": 3437,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: clean up types and registry validation\",\n      \"prNumber\": 3436,\n      \"type\": \"refactor\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: Store stringKnowledge in knowledge when ragKnowledge is enabled (#3434)\",\n      \"prNumber\": 3435,\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#3434\\r\\n\\r\\n<!-- This risks section must be filled out before the final review and merge. -->\\r\\n\\r\\n# Risks\\r\\n\"\n    },\n    {\n      \"title\": \"fix: add @solana/web3.js deps\",\n      \"prNumber\": 3431,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: v1 CLI utility\",\n      \"prNumber\": 3429,\n      \"type\": \"feature\",\n      \"body\": \"# Risks\\r\\n\\r\\nLow, maybe it doesn't work for you\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nprovides a little CLI utility for listing/adding plugins to an elizaos V1 repo:\\r\\n\\r\\n`npx elizos`\\r\\n\\r\\nget a list of available plugins\\r\\n\\r\\n`npx elizos p\"\n    },\n    {\n      \"title\": \"fix: remove --no-frozen-lockfile from Dockerfile\",\n      \"prNumber\": 3428,\n      \"type\": \"bugfix\",\n      \"body\": \"This no longer runs properly with the --no-frozen-lockfile command set\\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 \"\n    },\n    {\n      \"title\": \"feat/added agent commands\",\n      \"prNumber\": 3424,\n      \"type\": \"feature\",\n      \"body\": \"scaffolding stuff\\r\\n\\r\\ntesting to be done!\\r\\n\\r\\nassumes AGENT_RUNTIME_URL env variable\"\n    },\n    {\n      \"title\": \"typo\",\n      \"prNumber\": 3423,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: add note about 0x prefix needed for evm private key\",\n      \"prNumber\": 3414,\n      \"type\": \"feature\",\n      \"body\": \"Update the  README to guide users to remember to add the \\\"0x\\\" prefix Infront their evm private keys. I experienced an \\\"invalid private key\\\" that was resolved by doing this. Thought this would save alot of people the hustle.\\r\\n\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"chore: client/FAQ/Character file Docs update\",\n      \"prNumber\": 3410,\n      \"type\": \"other\",\n      \"body\": \"Figure it's better to do smaller incremental docs updates vs one huge one\\r\\n\\r\\nThis one adds some readmes to client packages + FAQ to various pages\\r\\n\\r\\nRevamped the characterfile page and updated the favicon to elizaos branding\"\n    },\n    {\n      \"title\": \"chore: update change log\",\n      \"prNumber\": 3407,\n      \"type\": \"other\",\n      \"body\": \"Update wrong words in the changelog file.\\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 sectio\"\n    },\n    {\n      \"title\": \"added character methods\",\n      \"prNumber\": 3400,\n      \"type\": \"other\",\n      \"body\": \"this bloats the adapter tho!!\\r\\n\\r\\n> also not fully tested!!!\"\n    },\n    {\n      \"title\": \"feat: Added cachedir to filesystem cache\",\n      \"prNumber\": 3291,\n      \"type\": \"feature\",\n      \"body\": \"# Risks\\r\\n\\r\\nNo risks. Adds ability to define cache dir in .env for when using filesystem cache.\\r\\n\\r\\n# Background\\r\\n\\r\\nI wanted to use filesystem cache, but it wasn't working without baseDir provided.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdds ability \"\n    },\n    {\n      \"title\": \"feat: TON Plugin: NFT collection, item creation, metadata change and transfer actions\",\n      \"prNumber\": 3211,\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\\nhttps://github.com/elizaOS/eliza/issues/2962\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks secti\"\n    },\n    {\n      \"title\": \"fix: CVE-2024-48930\",\n      \"prNumber\": 2958,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR fixes CVE-2024-48930 by updating package dependencies.\"\n    },\n    {\n      \"title\": \"chore: fix lockfile\",\n      \"prNumber\": 3633,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: Bump version to 0.25.8\",\n      \"prNumber\": 3632,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: Showcase page in docs for plugins\",\n      \"prNumber\": 3620,\n      \"type\": \"feature\",\n      \"body\": \"- Fetches repos from https://github.com/elizaos-plugins/registry\\r\\n- Creates cards, has tags / filters, links to the repo\\r\\n- Images via opengraph (https://opengraph.githubassets.com/1/elizaOS/eliza)\\r\\n- Simple search bar\\r\\n\\r\\n![image](https://g\"\n    },\n    {\n      \"title\": \"fix: set agent from api\",\n      \"prNumber\": 3618,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nNone\\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- Rollbacks some changed introduced on https://github.com/elizaOS/eliza/commit/3f66c9aa08829a794c4c52b064c4bc7b81c1049a#diff-6ccf35df0aad3b9693dad2ec6826b87\"\n    },\n    {\n      \"title\": \"fix: catch typing error\",\n      \"prNumber\": 3617,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: Fix devcontainer.json Port Mapping Syntax and JSON Structure\",\n      \"prNumber\": 3616,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed port mapping syntax\\r\\n\\r\\nOld: \\\"-p=3000:3000\\\"\\r\\nNew: \\\"-p 3000:3000\\\"\\r\\nOld: \\\"-p=5173:5173\\\"\\r\\nNew: \\\"-p 5173:5173\\\"\\r\\nReason: The correct syntax for port mapping in Docker is -p <host_port>:<container_port> (without =). Using = can lead to synta\"\n    },\n    {\n      \"title\": \"feat: Add support for Secret AI LLM\",\n      \"prNumber\": 3615,\n      \"type\": \"feature\",\n      \"body\": \"# Risks\\r\\nLow: existing code should not be impacted.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nIt adds support for Secret AI LLM provider.\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeature (non-breaking change which adds functionality).\\r\\n\\r\\n\"\n    },\n    {\n      \"title\": \"feat: Agent/Character cli methods + refactor server\",\n      \"prNumber\": 3613,\n      \"type\": \"feature\",\n      \"body\": \"# CLI Features: ElizaOS Agent & Character Management\\r\\n\\r\\n## Agent Management (`agent.ts`)  \\r\\n**Requires:** `AGENT_RUNTIME_URL` environment variable   or server running on `3000` PORT locally\\r\\n**New Commands:**\\r\\n- `elizaos agent list` - List \"\n    },\n    {\n      \"title\": \"feat: improve test plugin\",\n      \"prNumber\": 3612,\n      \"type\": \"feature\",\n      \"body\": \"Enhance the plugin test logger by improving color formatting for better readability. Also, ensure the test process properly terminates after execution.\\r\\n\\r\\n<img width=\\\"1057\\\" alt=\\\"Screenshot 2025-02-20 at 6 20 28\u202fPM\\\" src=\\\"https://github.com/u\"\n    },\n    {\n      \"title\": \"fix: installing packages from new registry\",\n      \"prNumber\": 3609,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nMight be related to: https://github.com/elizaOS/eliza/issues/3571\\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- Use default [isolated](https://pnpm.io/npmrc#node-linker) pnpm node-linker setting.\\r\\n- This a\"\n    },\n    {\n      \"title\": \"fix: discord actions\",\n      \"prNumber\": 3608,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR fixes the Discord actions and makes all of them work, except for the download media plugin. I couldn't get `ytdl` to work on my end, so I have temporarily commented out this plugin for now.\\r\\n\\r\\n@odilitime would check the ytdl issue w\"\n    },\n    {\n      \"title\": \"chore: docs update\",\n      \"prNumber\": 3605,\n      \"type\": \"other\",\n      \"body\": \"- Consolidate pages (like packages section) into core\\r\\n  - There were too many redundant pages\\r\\n- Emphasis on explaining concepts vs code snippets\\r\\n- Update API pages\\r\\n- Improve readability and accuracy (add links to sources wherever possib\"\n    },\n    {\n      \"title\": \"chore: cleanup bun build warnings\",\n      \"prNumber\": 3603,\n      \"type\": \"refactor\",\n      \"body\": \"# Overview\\r\\nThis PR addresses several warnings that appear during `bun run build`, improving the developer experience and code quality.\\r\\n\\r\\n## Changes\\r\\n\\r\\n### \ud83d\udd12 Security\\r\\n- Replace unsafe `eval()` with `JSON.parse()` for template parsing\\r\\n- \"\n    },\n    {\n      \"title\": \"chore: refactor room state [v2]\",\n      \"prNumber\": 3602,\n      \"type\": \"refactor\",\n      \"body\": \"The goal of this PR is to refactor how the state for things like discordMessages is loaded in order to be more generic and not pollute state with temporary stuff like state.discordMessage etc\\r\\n\\r\\nAlso add better hooks for getting clients and\"\n    },\n    {\n      \"title\": \"docs: Fix broken links\",\n      \"prNumber\": 3599,\n      \"type\": \"bugfix\",\n      \"body\": \"Fixed broken img links in README.md of i18n for all languages\"\n    },\n    {\n      \"title\": \"feat: V2 update character management\",\n      \"prNumber\": 3595,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: gaianet support set api key\",\n      \"prNumber\": 3591,\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\": \"feat: allow eliza client to configure eliza server base URL via env var\",\n      \"prNumber\": 3589,\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- Fixes: https://github.com/elizaOS/eliza/issues/3585\\r\\n- Possibly a solution to: https://github.com/eli\"\n    },\n    {\n      \"title\": \"chore: Update and cleanup docs\",\n      \"prNumber\": 3584,\n      \"type\": \"refactor\",\n      \"body\": \"Another batch of updates to improve docs by explaining concepts, not just having code snippets, reorganizing the sidebar, adding notes to new videos, including video embeds, etc. \"\n    },\n    {\n      \"title\": \"fix: small discord/telegram/twitter clean up\",\n      \"prNumber\": 3582,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: gracefully handle database operations\",\n      \"prNumber\": 3581,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: discord + twitter e2e test\",\n      \"prNumber\": 3579,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: db-driven-character management\",\n      \"prNumber\": 3573,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: Modify the configuration for the plugin-nkn\",\n      \"prNumber\": 3570,\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\\nThis PR integrates the [`plugin-nkn`](https://github.com/nknorg/eliza-plugin-nkn) plugin into the `Eliza` project. It includes the following changes:\\r\\n- **Modifies the `.env` fil\"\n    },\n    {\n      \"title\": \"fix: fix case insensitive filename mismatches\",\n      \"prNumber\": 3561,\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\\n1. fixes case sensitive file system issues (and renamed some files, preferring dashes and noun-verb)\\r\\n2. fix integration-tests GitHub workflow\\r\\n\\r\\n## What kind of change is this?\\r\"\n    },\n    {\n      \"title\": \"fix: add log\",\n      \"prNumber\": 3560,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: [discord] add test channel id for e2e test + fix _shouldRespond function\",\n      \"prNumber\": 3559,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: Fix bedrock inference\",\n      \"prNumber\": 3553,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\nFixes [3328](https://github.com/elizaOS/eliza/issues/3328)\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow risk as this only adds one case statement for handling the Bedrock model provider\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does\"\n    },\n    {\n      \"title\": \"fix: typo\",\n      \"prNumber\": 3551,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"feat: add interactions vitest + fix twitter interactions code\",\n      \"prNumber\": 3550,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"fix: race condition\",\n      \"prNumber\": 3549,\n      \"type\": \"bugfix\",\n      \"body\": \"# Fix Race Condition in Plugin Loading\\r\\n\\r\\n## Issue Description\\r\\nWhen running multiple characters with the same plugin configuration, discovered a race condition where the `ensureEmbeddingDimension` method wasn't being properly executed befo\"\n    },\n    {\n      \"title\": \"chore: Trim <think> block from Ollama response\",\n      \"prNumber\": 3545,\n      \"type\": \"other\",\n      \"body\": \"This pull request includes a change to the `generateText` function in the `packages/core/src/generation.ts` file to improve the handling of responses from the Ollama model.\\r\\n\\r\\n* [`packages/core/src/generation.ts`](diffhunk://#diff-b68254579\"\n    },\n    {\n      \"title\": \"fix: twitter vitest\",\n      \"prNumber\": 3543,\n      \"type\": \"bugfix\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: update readme to model plugins (basic)\",\n      \"prNumber\": 3542,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"chore: remove anthropic local embed\",\n      \"prNumber\": 3540,\n      \"type\": \"other\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: Added sqlite3 errors to Quickstart\",\n      \"prNumber\": 3539,\n      \"type\": \"docs\",\n      \"body\": \"# Relates to\\r\\n\\r\\nCouldn't find any issues related to this but I've ran into this issue and believe it should be added to the doc as there is already something related to this.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\nOnly documentation change\\r\\n\\r\\n# Background\\r\\n\\r\\nW\"\n    },\n    {\n      \"title\": \"feat: telegram test suite\",\n      \"prNumber\": 3538,\n      \"type\": \"feature\",\n      \"body\": \"\"\n    },\n    {\n      \"title\": \"docs: fix branch naming example in CONTRIBUTING.md\",\n      \"prNumber\": 3532,\n      \"type\": \"bugfix\",\n      \"body\": \"## What does this PR do?\\r\\n\\r\\nThe example uses a double hyphen (`--`) between the issue number and the description, which isn't standard practice.\\r\\nI've updated it to use a single hyphen (`-`) to align with common Git conventions.  \\r\\n\\r\\nThis c\"\n    },\n    {\n      \"title\": \"Refactor - Plugin Local AI\",\n      \"prNumber\": 3526,\n      \"type\": \"refactor\",\n      \"body\": \"Initial refactoring of the Local AI.\\r\\n\\r\\n1 - Local inference work via deepseek R1 - In the process i removed the <think> that is not supported by our client. I tested the plugin as solo because the point was to have a solution to run immedia\"\n    },\n    {\n      \"title\": \"chore(deps): update dependency vitest [security]\",\n      \"prNumber\": 3525,\n      \"type\": \"tests\",\n      \"body\": \"This PR contains the following updates:\\n\\n| Package | Change | Age | Adoption | Passing | Confidence |\\n|---|---|---|---|---|---|\\n| [vitest](https://redirect.github.com/vitest-dev/vitest) ([source](https://redirect.github.com/vitest-dev/vites\"\n    },\n    {\n      \"title\": \"feat: update tee\",\n      \"prNumber\": 3512,\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\": \"Vector Dimensions & Character Schema Updates\",\n      \"prNumber\": 3486,\n      \"type\": \"other\",\n      \"body\": \"Vector Dimensions & Character Schema Updates\\r\\nImplementation Status\\r\\n\\r\\n\u2705 Embedding dimension issue solved and tested\\r\\n\u2705 Character schema updated with name as unique identifier\\r\\n\u2705 Plugin integration tests completed for multiple plugins\\r\\n\u26a0\ufe0f H\"\n    },\n    {\n      \"title\": \"fix plugins installing during init and plugins add\",\n      \"prNumber\": 3451,\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\\nFix `eliza init` and `eliza plugins add` commands in CLI\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This r\"\n    },\n    {\n      \"title\": \"docs: enhance README with detailed requirements and contribution guidelines\",\n      \"prNumber\": 3392,\n      \"type\": \"docs\",\n      \"body\": \"This commit improves the README.md file by:\\r\\n- Adding detailed system requirements section\\r\\n- Including project structure overview\\r\\n- Adding comprehensive contribution guidelines\\r\\n- Improving documentation organization\\r\\n- Making the project\"\n    },\n    {\n      \"title\": \"feat: add NEAR AI model provider\",\n      \"prNumber\": 3275,\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\\nAdd NEAR AI (https://near.ai) Inference API (OpenAI compatible) to Eliza: https://docs.near.ai/inferenc\"\n    },\n    {\n      \"title\": \"feat: save imageUrls for outbound tweets/messages\",\n      \"prNumber\": 3122,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\nAdding proper image URL handling for Twitter client memory system\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n- Memory storage: Ensures consistent image URL handling in both directions\\r\\n- Data consistency: Maintains image context through conversation th\"\n    }\n  ],\n  \"topContributors\": [\n    {\n      \"username\": \"tcm390\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/60634884?u=c6c41679b8322eaa0c81f72e0b4ed95e80f0ac16&v=4\",\n      \"totalScore\": 1694.2478988767923,\n      \"prScore\": 1603.3338988767923,\n      \"issueScore\": 4,\n      \"reviewScore\": 85,\n      \"commentScore\": 1.914\n    },\n    {\n      \"username\": \"odilitime\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n      \"totalScore\": 1172.1152698953508,\n      \"prScore\": 786.5572698953507,\n      \"issueScore\": 0,\n      \"reviewScore\": 379,\n      \"commentScore\": 6.558\n    },\n    {\n      \"username\": \"wtfsayo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n      \"totalScore\": 1001.4017832705239,\n      \"prScore\": 938.9857832705239,\n      \"issueScore\": 0,\n      \"reviewScore\": 60,\n      \"commentScore\": 2.416\n    },\n    {\n      \"username\": \"lalalune\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/18633264?u=e2e906c3712c2506ebfa98df01c2cfdc50050b30&v=4\",\n      \"totalScore\": 628.0978994190056,\n      \"prScore\": 577.4218994190055,\n      \"issueScore\": 0,\n      \"reviewScore\": 49,\n      \"commentScore\": 1.676\n    },\n    {\n      \"username\": \"AIFlowML\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/154863472?u=99689ad0f9ec0be78ba3b726c1ef10df796fbe7d&v=4\",\n      \"totalScore\": 597.019000689468,\n      \"prScore\": 596.6190006894681,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.4\n    },\n    {\n      \"username\": \"shakkernerd\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/165377636?u=5560dd9f2d310e1ba61dbba864006a951391a582&v=4\",\n      \"totalScore\": 357.8190632888958,\n      \"prScore\": 162.18106328889579,\n      \"issueScore\": 0,\n      \"reviewScore\": 195,\n      \"commentScore\": 0.6379999999999999\n    },\n    {\n      \"username\": \"0xbbjoker\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n      \"totalScore\": 351.7240855466058,\n      \"prScore\": 351.52408554660576,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2\n    },\n    {\n      \"username\": \"madjin\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n      \"totalScore\": 307.3476433794566,\n      \"prScore\": 303.00764337945657,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.33999999999999997\n    },\n    {\n      \"username\": \"mikirov\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/29272392?u=a4773a399c1cbcd34cdca9a7877cd61824c5bf09&v=4\",\n      \"totalScore\": 232.69193096436308,\n      \"prScore\": 230.93593096436308,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 1.7559999999999998\n    },\n    {\n      \"username\": \"HashWarlock\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/64296537?u=1d8228a93c06c603e08d438677b3f736d6b1ab22&v=4\",\n      \"totalScore\": 190.16409997540362,\n      \"prScore\": 184.7640999754036,\n      \"issueScore\": 0,\n      \"reviewScore\": 5,\n      \"commentScore\": 0.4\n    },\n    {\n      \"username\": \"azep-ninja\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/142059473?u=7bcfb03323132153f1cca74bdb66853b5e2e1dd5&v=4\",\n      \"totalScore\": 159.5007050655107,\n      \"prScore\": 159.5007050655107,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0\n    },\n    {\n      \"username\": \"ai16z-demirix\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/188117230?u=424cd5b834584b3799da288712b3c4158c8032a1&v=4\",\n      \"totalScore\": 154.2365340578587,\n      \"prScore\": 141.69653405785868,\n      \"issueScore\": 12,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.54\n    },\n    {\n      \"username\": \"yungalgo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/113615973?u=92e0f29f7e2fbb8ce46ed13c51f692ca803de02d&v=4\",\n      \"totalScore\": 135.3031026856691,\n      \"prScore\": 135.3031026856691,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0\n    },\n    {\n      \"username\": \"avaer\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/6926057?u=4f55bb6c993f04590b66d17136cdb9579b87bac4&v=4\",\n      \"totalScore\": 131.46888216250895,\n      \"prScore\": 126.96888216250895,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0\n    },\n    {\n      \"username\": \"v1xingyue\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/974169?u=96c6a113a91978c041e5cf90965d7b66c5540af4&v=4\",\n      \"totalScore\": 129.43712990256253,\n      \"prScore\": 124.93712990256253,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0\n    },\n    {\n      \"username\": \"Y-DA007\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/195081807?u=294325670bf70f360292a13fc03ac04feac1b1d7&v=4\",\n      \"totalScore\": 127.17047437417261,\n      \"prScore\": 127.17047437417261,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0\n    },\n    {\n      \"username\": \"lggg123\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/22415259?u=210e0fb7c522442e99a3ccceabb2de94700509bb&v=4\",\n      \"totalScore\": 124.2953216897283,\n      \"prScore\": 119.9553216897283,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.33999999999999997\n    },\n    {\n      \"username\": \"romain-lfg\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/191244204?v=4\",\n      \"totalScore\": 114.72532168972829,\n      \"prScore\": 114.72532168972829,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0\n    },\n    {\n      \"username\": \"jgabriele321\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/94648636?v=4\",\n      \"totalScore\": 107.7653216897283,\n      \"prScore\": 107.7653216897283,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0\n    },\n    {\n      \"username\": \"jmikedupont2\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16427113?u=2bdad12714de646188f98a07736a54f765ad5e3b&v=4\",\n      \"totalScore\": 102.3406945727269,\n      \"prScore\": 101.9406945727269,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.4\n    }\n  ],\n  \"newPRs\": 448,\n  \"mergedPRs\": 255,\n  \"newIssues\": 120,\n  \"closedIssues\": 84,\n  \"activeContributors\": 388\n}",
  "github_extracted_data_user_summaries_text_last_7_days_for_2025-02-25": "[\"Adz30_week_2025-02-23\", \"Adz30\", \"week\", \"2025-02-23\", \"Adz30: Created issue #3689 \\\"wallet issues\\\" which was subsequently closed. No other activity was observed during this period.\", \"2025-05-13T22:06:04.217Z\"]\n[\"AdityaSalunkhe21_week_2025-02-23\", \"AdityaSalunkhe21\", \"week\", \"2025-02-23\", \"AdityaSalunkhe21: Made code changes across 4 files (+85/-44 lines) in 2 commits, with activity on 2 days this week. No PRs, issues, or reviews were submitted during this period.\", \"2025-05-13T22:06:04.922Z\"]\n[\"0xJACKSON-dev_week_2025-02-23\", \"0xJACKSON-dev\", \"week\", \"2025-02-23\", \"0xJACKSON-dev: Created issue #3683 \\\"Utilize ChatGPT assistant API keys\\\" which was subsequently closed. No other activity was observed during this period.\", \"2025-05-13T22:06:04.237Z\"]\n[\"AIFlowML_week_2025-02-23\", \"AIFlowML\", \"week\", \"2025-02-23\", \"AIFlowML: Completed a major refactoring effort with two significant merged PRs (#3704 and #3663) that together modified 369 files with substantial code changes (+22,313/-15,708 lines). Created and closed issue #936 regarding LLM-suitable documentation, while maintaining moderate activity across 3 days of the week.\", \"2025-05-13T22:06:05.442Z\"]\n[\"0xbbjoker_week_2025-02-23\", \"0xbbjoker\", \"week\", \"2025-02-23\", \"0xbbjoker: Merged two PRs this week addressing database-related fixes, with PR #3674 making substantial changes (+12124/-7112 lines) to resolve re-initialization migration issues and PR #3672 (+29/-86 lines) fixing pglite and migration problems. Also opened PR #3675 to address an issue with database path.\", \"2025-05-13T22:06:05.153Z\"]\n[\"Ansh1902396_week_2025-02-23\", \"Ansh1902396\", \"week\", \"2025-02-23\", \"Ansh1902396: Has one open pull request (#3709 \\\"updayte\\\") with no merged contributions this week. No other activity was observed during this period.\", \"2025-05-13T22:06:06.172Z\"]\n[\"BranchManager69_week_2025-02-23\", \"BranchManager69\", \"week\", \"2025-02-23\", \"BranchManager69: Minimal activity this week with one open PR (#3718) marked as \\\"Closed\\\" and a single PR comment. No code changes, issue activity, or reviews were recorded during this period.\", \"2025-05-13T22:06:06.221Z\"]\n[\"ChristopherTrimboli_week_2025-02-23\", \"ChristopherTrimboli\", \"week\", \"2025-02-23\", \"ChristopherTrimboli: Contributed a single feature enhancement this week by merging PR #3711, which added support for the ANTHROPIC_API_URL environment variable (+3/-2 lines). Activity was limited to just one day during this period, with minimal code changes across two files.\", \"2025-05-13T22:06:07.318Z\"]\n[\"Dahka2321_week_2025-02-23\", \"Dahka2321\", \"week\", \"2025-02-23\", \"Dahka2321: Fixed broken links in the README documentation through PR #3684 (+1/-1 lines), which was merged after 12 hours.\", \"2025-05-13T22:06:06.830Z\"]\n[\"Doge-is-Dope_week_2025-02-23\", \"Doge-is-Dope\", \"week\", \"2025-02-23\", \"Doge-is-Dope: Made a single documentation improvement with PR #3649, fixing formatting issues in plugins.md with minimal changes (+4/-4 lines).\", \"2025-05-13T22:06:07.222Z\"]\n[\"Hopium21_week_2025-02-23\", \"Hopium21\", \"week\", \"2025-02-23\", \"Hopium21: Made a small but helpful contribution with PR #3707 that fixed grammar issues and added a guard to the createVerifiableLogApiRouter, modifying 3 files with minimal changes (+3/-3 lines).\", \"2025-05-13T22:06:08.949Z\"]\n[\"HashWarlock_week_2025-02-23\", \"HashWarlock\", \"week\", \"2025-02-23\", \"HashWarlock: Fixed a Docker image issue for CI/CD setup with PR #3732 (+20437/-6969 lines) and created issue #928 for character file storage service support. Active on only one day this week, focusing entirely on bugfix work across code and configuration files.\", \"2025-05-13T22:06:13.326Z\"]\n[\"IshaVenikar_week_2025-02-23\", \"IshaVenikar\", \"week\", \"2025-02-23\", \"IshaVenikar: Made significant code changes across 23 files (+861/-175 lines) in 7 commits, with most work (86%) focused on non-bugfix activities and the remainder (14%) on bug fixes. Activity was concentrated on a single day during this period, showing a sporadic contribution pattern.\", \"2025-05-13T22:06:09.483Z\"]\n[\"SITADRITA1_week_2025-02-23\", \"SITADRITA1\", \"week\", \"2025-02-23\", \"SITADRITA1: Opened PR #3705 focused on documentation improvements, addressing grammar, typos, and formatting issues across 6 files (+21/-23 lines). Active on 2 days this week, making 6 commits exclusively to documentation files.\", \"2025-05-13T22:06:10.328Z\"]\n[\"Tony363_week_2025-02-23\", \"Tony363\", \"week\", \"2025-02-23\", \"Tony363: Opened PR #3733 \\\"finally got it to make the request\\\" with changes across 8 files (+187/-3 lines), primarily focusing on configuration files (50%) and code (25%). Activity was limited to a single day this week with one commit.\", \"2025-05-13T22:06:11.394Z\"]\n[\"X4ndar_week_2025-02-23\", \"X4ndar\", \"week\", \"2025-02-23\", \"X4ndar: Has one open pull request (#3666 \\\"Stable\\\") with no merged PRs or other activity this period.\", \"2025-05-13T22:06:11.186Z\"]\n[\"EonHao_week_2025-02-23\", \"EonHao\", \"week\", \"2025-02-23\", \"EonHao: Made 2 commits modifying 2 files (+306/-206 lines) on a single day this week. The work was evenly split between bugfix work (50%) and other work (50%), involving various file types.\", \"2025-05-13T22:06:08.233Z\"]\n[\"avdheshcharjan_week_2025-02-23\", \"avdheshcharjan\", \"week\", \"2025-02-23\", \"avdheshcharjan: Reported a Docker file issue (#3661) regarding an invalid cachestore, which has since been closed. Participated in issue discussions with one comment.\", \"2025-05-13T22:06:17.370Z\"]\n[\"batudo_week_2025-02-23\", \"batudo\", \"week\", \"2025-02-23\", \"batudo: Merged PR #3653 \\\"fix: Fix splitText\\\" which made significant code changes (+10757/-5908 lines). Provided one review comment on another PR. Active on only one day this week, focusing entirely on bugfix work.\", \"2025-05-13T22:06:13.757Z\"]\n[\"boolkeys_week_2025-02-23\", \"boolkeys\", \"week\", \"2025-02-23\", \"boolkeys: Fixed a bug related to handling short text items in knowledge processing through PR #3652 (+19/-0 lines). Engaged in discussions by commenting on 4 issues and 1 PR. Activity was limited to a single day this week.\", \"2025-05-13T22:06:14.077Z\"]\n[\"btspoony_week_2025-02-23\", \"btspoony\", \"week\", \"2025-02-23\", \"btspoony: Added post-processing support for character loading through PR #3686 (+43/-2 lines), which was merged after 11 hours. Made a total of 4 commits across 6 files (+86/-4 lines), with 75% of work focused on feature development and 25% on bug fixes.\", \"2025-05-13T22:06:14.818Z\"]\n[\"Xayaan_week_2025-02-23\", \"Xayaan\", \"week\", \"2025-02-23\", \"Xayaan: Made significant documentation improvements through two merged PRs (#3736 and #3735), focusing on custom plugins documentation with substantial changes (+2823/-1765 lines). Both PRs were merged on the same day, with PR #3736 containing the majority of changes, updating the README for custom plugins how-to.\", \"2025-05-13T22:06:12.195Z\"]\n[\"cryptokatze_week_2025-02-23\", \"cryptokatze\", \"week\", \"2025-02-23\", \"cryptokatze: Updated the Korean README documentation with PR #3670, making modest changes (+8/-9 lines) that were merged within 5 hours.\", \"2025-05-13T22:06:16.949Z\"]\n[\"dav3yblaz3_week_2025-02-23\", \"dav3yblaz3\", \"week\", \"2025-02-23\", \"dav3yblaz3: Provided one code review with approval this week. Activity was minimal with no PRs created or merged, no issues opened or commented on, and no code changes made.\", \"2025-05-13T22:06:17.253Z\"]\n[\"MOSSV2_week_2025-02-23\", \"MOSSV2\", \"week\", \"2025-02-23\", \"MOSSV2: Opened two PRs related to memory management: #3720 \\\"add memory management\\\" and #3730 \\\"feat: add membase in memory management\\\". No other activity was observed during this period.\", \"2025-05-13T22:06:09.658Z\"]\n[\"fforbeck_week_2025-02-23\", \"fforbeck\", \"week\", \"2025-02-23\", \"fforbeck: Opened one pull request (#3657) focused on a new \\\"storacha plugin\\\" feature, making substantial code changes with +1064/-196 lines across 14 files. The contribution was concentrated on a single day, with the majority of changes affecting code (57%) and configuration files (29%).\", \"2025-05-13T22:06:19.006Z\"]\n[\"christopherpile_week_2025-02-23\", \"christopherpile\", \"week\", \"2025-02-23\", \"christopherpile: Opened one PR (#3650 \\\"Cp agent\\\") with substantial code changes, modifying 2,762 files with +29,889/-368,230 lines in a single commit. The changes were entirely focused on documentation work, with activity on just one day during this period.\", \"2025-05-13T22:06:15.734Z\"]\n[\"corymaklin_week_2025-02-23\", \"corymaklin\", \"week\", \"2025-02-23\", \"corymaklin: Opened one PR (#3646) for a \\\"Hyperlane GOAT Plugin\\\" with moderate code changes (+257/-119 lines) across 15 files. Activity was concentrated on a single day, with the majority of changes focused on configuration files (75%) rather than code (25%).\", \"2025-05-13T22:06:16.099Z\"]\n[\"jgarrettvml_week_2025-02-23\", \"jgarrettvml\", \"week\", \"2025-02-23\", \"jgarrettvml: Created issue #3679 about character files not loading, which has since been closed. Engaged in discussions on 3 different issues through comments. No code contributions or pull requests during this period.\", \"2025-05-13T22:06:19.969Z\"]\n[\"hkhangus_week_2025-02-23\", \"hkhangus\", \"week\", \"2025-02-23\", \"hkhangus: Made a small but targeted contribution by merging PR #3678 to fix character knowledge directory issues, with minimal code changes (+1/-1 lines). This single PR, which took 17 hours to merge, represents their only activity during the week.\", \"2025-05-13T22:06:20.207Z\"]\n[\"jmikedupont2_week_2025-02-23\", \"jmikedupont2\", \"week\", \"2025-02-23\", \"jmikedupont2: Currently has 4 open PRs (#3728, #3712, #3669, #3695) with no merged contributions this week. Made 2 comments on pull requests but showed no other activity during this period.\", \"2025-05-13T22:06:20.640Z\"]\n[\"everimbaq_week_2025-02-23\", \"everimbaq\", \"week\", \"2025-02-23\", \"everimbaq: Made substantial code changes across 3228 files (+16692/-431694 lines) with 8 commits, showing a significant reduction in codebase size. Active on 3 days this week with a balanced focus on feature work (38%) and other work (38%), along with some bugfix and refactoring efforts (13% each).\", \"2025-05-13T22:06:18.230Z\"]\n[\"ido567_week_2025-02-23\", \"ido567\", \"week\", \"2025-02-23\", \"ido567: Reported issue #3692 regarding an \\\"Unexpected ERR_USE_AFTER_CLOSE error while running Eliza on D...\\\" which has since been closed. Added one comment on an issue, with no other activity during this period.\", \"2025-05-13T22:06:20.247Z\"]\n[\"juanc07_week_2025-02-23\", \"juanc07\", \"week\", \"2025-02-23\", \"juanc07: Contributed 2 code reviews with comments this week. Made a small refactoring change with 1 commit modifying a single file (+1/-3 lines). Activity was limited to a single day during this period.\", \"2025-05-13T22:06:21.731Z\"]\n[\"leopardracer_week_2025-02-23\", \"leopardracer\", \"week\", \"2025-02-23\", \"leopardracer: Fixed typographical errors in documentation by merging PR #3656 (+2/-2 lines) which modified 4 files. Active on 2 days this week with a focus on documentation improvements.\", \"2025-05-13T22:06:21.994Z\"]\n[\"lqkhanh195_week_2025-02-23\", \"lqkhanh195\", \"week\", \"2025-02-23\", \"lqkhanh195: Created issue #3702 regarding \\\"No REST API backend\\\" which was subsequently closed. Engaged in discussions by commenting on 2 issues. No code contributions or pull requests during this period.\", \"2025-05-13T22:06:22.817Z\"]\n[\"lalalune_week_2025-02-23\", \"lalalune\", \"week\", \"2025-02-23\", \"lalalune: Merged 3 substantial PRs this week, including a new rolodex feature (#3725, +5098/-3055), performance improvements (#3688, +1926/-1651), and core functionality enhancements (#3682, +3457/-3462), while also creating 8 issues outlining architectural changes and improvements. Demonstrated very consistent work across 5 days with 40 commits modifying 678 files (+31242/-19514 lines), primarily focusing on new features and bug fixes.\", \"2025-05-13T22:06:23.226Z\"]\n[\"mohsinn3_week_2025-02-23\", \"mohsinn3\", \"week\", \"2025-02-23\", \"mohsinn3: Reported one issue (#3693) about Twitter Agent functionality, which has since been closed. Engaged in discussions on 5 different issues through comments. No code contributions or pull requests during this period.\", \"2025-05-13T22:06:24.297Z\"]\n[\"mtbc_week_2025-02-23\", \"mtbc\", \"week\", \"2025-02-23\", \"mtbc: Made a single large commit modifying 223 files with substantial code changes (+9679/-2837 lines).\", \"2025-05-13T22:06:24.542Z\"]\n[\"madjin_week_2025-02-23\", \"madjin\", \"week\", \"2025-02-23\", \"madjin: Focused extensively on documentation improvements, merging two substantial PRs (#3729 and #3694) that collectively added over 14,700 lines while removing nearly 5,900 lines across 637 files. Created issue #1044 for documentation improvements based on frequently asked questions from Discord. Active on 4 days this week, with 99% of changes being documentation-related, demonstrating a concentrated effort to enhance project documentation.\", \"2025-05-13T22:06:24.859Z\"]\n[\"nusk0_week_2025-02-23\", \"nusk0\", \"week\", \"2025-02-23\", \"nusk0: Opened PR #3647 for a user rapport feature focused on tailored Twitter interactions, making significant code changes (+3/-1632 lines) across 12 files. Engaged in discussions by commenting on 4 issues and 1 PR, with activity concentrated on a single day this week.\", \"2025-05-13T22:06:25.513Z\"]\n[\"quanghuynguyen1902_week_2025-02-23\", \"quanghuynguyen1902\", \"week\", \"2025-02-23\", \"quanghuynguyen1902: Created issue #3723 requesting to \\\"Add plugin-evm\\\" which has since been closed. No other activity was observed during this period.\", \"2025-05-13T22:06:26.521Z\"]\n[\"shakkernerd_week_2025-02-23\", \"shakkernerd\", \"week\", \"2025-02-23\", \"shakkernerd: Provided 2 approvals in code reviews this week. Made a small bugfix contribution with 6 lines modified across 1 file in a single commit.\", \"2025-05-13T22:06:26.834Z\"]\n[\"khiemsoft_week_2025-02-23\", \"khiemsoft\", \"week\", \"2025-02-23\", \"khiemsoft: Contributed a single merged PR (#3701) that added environment updates for the Viction plugin, with 10 lines added and none removed. The contribution was focused on feature work, modifying 2 files across 2 commits on a single day this week.\", \"2025-05-13T22:06:22.432Z\"]\n[\"odilitime_week_2025-02-23\", \"odilitime\", \"week\", \"2025-02-23\", \"odilitime: Merged 11 PRs this week, with significant work on development tooling improvements including CLI fixes (#3699, #3698, #3697, #3673), dependency updates (#3700 with +990/-3651 lines), and repository maintenance (#3715, #3716). Demonstrated consistent daily activity with 73 commits across 8475 files (+137k/-1053k lines), focusing primarily on configuration and bug fixes while also providing 35 code reviews (26 approvals). Created and closed issue #617 for persistent plugin storage.\", \"2025-05-13T22:06:26.855Z\"]\n[\"thanghd98_week_2025-02-23\", \"thanghd98\", \"week\", \"2025-02-23\", \"thanghd98: Made a single commit this week, adding 5 lines across one file. Activity was limited to just one day during this period.\", \"2025-05-13T22:06:28.283Z\"]\n[\"suryanshkushwaha_week_2025-02-23\", \"suryanshkushwaha\", \"week\", \"2025-02-23\", \"suryanshkushwaha: Reported a memory issue by creating issue #3664 \\\"RAG Knowledge JavaScript Heap Out of Memory\\\" which was subsequently closed. Also contributed one comment on an issue, showing sporadic activity during this period.\", \"2025-05-13T22:06:27.038Z\"]\n[\"tomicvladan_week_2025-02-23\", \"tomicvladan\", \"week\", \"2025-02-23\", \"tomicvladan: Reported issue #3685 regarding Twitter media being ignored when Discord approvals are enabled, which has since been closed.\", \"2025-05-13T22:06:28.519Z\"]\n[\"think-in-universe_week_2025-02-23\", \"think-in-universe\", \"week\", \"2025-02-23\", \"think-in-universe: Merged one PR (#3644) that fixed the generation of structured objects and images with NEAR AI, contributing +51/-5 lines across 4 files. Activity was sporadic with contributions on only one day this week, focusing primarily on other work (50%) with some feature and bugfix work (25% each).\", \"2025-05-13T22:06:28.985Z\"]\n[\"twilwa_week_2025-02-23\", \"twilwa\", \"week\", \"2025-02-23\", \"twilwa: Made a single commit this week, modifying one file with 54 lines added and none removed. Activity was limited to just one day during this period.\", \"2025-05-13T22:06:29.354Z\"]\n[\"v1xingyue_week_2025-02-23\", \"v1xingyue\", \"week\", \"2025-02-23\", \"v1xingyue: Merged 3 significant PRs this week, including a critical OOM bug fix (#3722, +8417/-4595 lines), plugin installation verification (#3660), and agent server middleware settings (#3648, +9889/-6746 lines). Contributed substantial code changes across 37 files (+4030/-3390 lines) with a balanced focus between feature development and bug fixing. Also created issue #909 requesting a Provider ID feature, which has already been closed.\", \"2025-05-13T22:06:31.227Z\"]\n[\"yungalgo_week_2025-02-23\", \"yungalgo\", \"week\", \"2025-02-23\", \"yungalgo: Made significant code changes across 23 files (+1003/-395 lines) in 3 commits, with activity concentrated on a single day. Work was primarily focused on other development tasks (67%) with some bugfix work (33%), though no PRs were opened or merged during this period.\", \"2025-05-13T22:06:31.407Z\"]\n[\"wtfsayo_week_2025-02-23\", \"wtfsayo\", \"week\", \"2025-02-23\", \"wtfsayo: Merged 10 PRs this week, with significant work on agent handling consolidation in #3708 (+4352/-3165 lines) and implementing the mock agent form on client in #3690 (+868/-155 lines). Consistently active across 6 days, focusing on code refactoring with file-based API routes (#3651), server cleanup (#3667), and various GUI enhancements (#3727). Contributed a massive amount of code changes across 705 files (+37345/-28248 lines) while maintaining a steady workflow averaging 3 hours from PR creation to merge.\", \"2025-05-13T22:06:32.479Z\"]\n[\"tcm390_week_2025-02-23\", \"tcm390\", \"week\", \"2025-02-23\", \"tcm390: Merged 13 PRs this week with significant contributions including a major feature for client UI agent configuration with plugins (#3731, +1496/-1457 lines) and space action functionality (#3655, +5065/-2228 lines), while also addressing numerous fixes across various components like character creator, Twitter functionality, and Discord actions. Consistently active every day with 94 commits modifying 242 files (+8107/-6810 lines total), demonstrating a balanced focus between new features (13%), bug fixes (12%), and refactoring work (15%).\", \"2025-05-13T22:06:29.326Z\"]",
  "_metadata": {
    "generated_at": "2026-01-01T02:18:08.169177Z",
    "target_date": "2025-02-25",
    "source_repo": {
      "full_name": "elizaOS/knowledge",
      "owner": "elizaOS",
      "repo": "knowledge"
    },
    "sources_successful": 10,
    "sources_failed": 0,
    "source_keys": [
      "ai_news_elizaos_discord_md_2025-02-24",
      "ai_news_elizaos_discord_md_2025-02-23",
      "ai_news_elizaos_discord_md_2025-02-22",
      "ai_news_elizaos_daily_json_2025-02-24",
      "ai_news_elizaos_daily_md_2025-02-24",
      "ai_news_elizaos_daily_discord_json_2025-02-24",
      "ai_news_elizaos_daily_discord_md_2025-02-24",
      "github_summaries_daily_2025-02-25",
      "github_summaries_week_latest_2025-12-21.md",
      "github_summaries_month_latest_2025-12-01.md"
    ],
    "failed_keys": [],
    "total_characters": 201328,
    "estimated_tokens": 50332,
    "file_size_bytes": 216628
  }
}