{
  "date_generated_for": "2025-02-16",
  "ai_news_elizaos_discord_md_2025-02-15": {
    "filename": "2025-02-15.md",
    "content": "# elizaOS Discord - 2025-02-15\n\n## Overall Discussion Highlights\n\n### Security Incident: Shaw's Twitter Account Hack\n- Shaw's Twitter account was compromised, with the hacker posting phishing links to fake ElizaOS websites (eliza-os.net and elizaos.co)\n- The scam posts promoted a fake token migration, attempting to drain users' wallets\n- Community members quickly mobilized to report the scam posts and domains to registrars\n- Several users reported losing funds, with one claiming to have lost $40,000\n- Team members confirmed the hack and warned users not to trust posts from Shaw's account\n- \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f confirmed taking down malicious units and setting up monitoring\n- The incident highlighted the need for more secure communication channels, with Jin suggesting on-chain communications via memos or mirror.xyz\n\n### ElizaOS Development & Features\n- Shaw is developing a new agent swarm system for v2, allowing agents to perform useful work with role-based privileges\n- The system enables agents to create tasks, execute them with confirmation, and interact with other agents\n- Users discussed memory separation by user ID to maintain privacy in multi-user environments\n- Twitter integration challenges include rate limits, verification requirements, and avoiding shadow bans\n- Multiple users encountered issues with better-sqlite3 installation, which can be resolved by rebuilding the module\n- ElizaOS can run multiple agents simultaneously, though with memory constraints\n- Various LLM providers can be used beyond the default options\n\n### Community Events & Rebranding\n- Plans to change \"What Did You Get Done This Week\" (WDYGDTW) format to a \"Clank Tank\" game show inspired by Shark Tank\n- Jin mentioned integrating a weekly space into this new format, potentially premiering the following Friday\n- Fishai is leading video editing work for the show, creating an intro resembling Shark Tank in style\n- The community discussed the ongoing rebranding from ai16z to ElizaOS\n- Many noted that the ElizaOS brand is gaining recognition while ai16z remains less known\n\n### Tokenomics & Partnerships\n- DorianD suggested capturing fees from trading pools that use the network coin\n- yikesawjeez proposed positioning their token as an \"agent meta index fund\" by creating liquidity pairs with various AI/agent projects\n- A partnership with BNB Chain was highlighted, suggesting potential for multichain expansion beyond Solana\n- The DegenAI Twitter account was reported as banned, with rhota mentioning they've reached out to X (Twitter) to resolve it\n- rhota mentioned implementing basic trade testing plans for their Trading v2 platform\n\n## Key Questions & Answers\n\n**Security Incident**\n- **Q: Is Shaw hacked?**  \n  **A:** Yes, don't trust whatever he posts for now (answered by jin)\n\n- **Q: Did you sign a transaction or connect your wallet?**  \n  **A:** I signed a transaction yes (answered by bert)\n\n- **Q: My other wallets weren't connected to the site only the one that got drained so ill be fine right?**  \n  **A:** Yes king if other wallets weren't connected you should be safe, but please double check and revoke any permissions (answered by BOSSU)\n\n- **Q: How can Shaw not have 2fa for his twitter account?**  \n  **A:** It is [enabled], it might not be the culprit (answered by jin)\n\n- **Q: How else could someone get access to his twitter account?**  \n  **A:** Twitter may disable 2FA during account recovery processes (answered by Patt)\n\n**Technical Questions**\n- **Q: How can I separate memory by user to keep data private between multi-users?**  \n  **A:** Pass userId and roomId parameters with your API request (answered by lefrog)\n\n- **Q: How do I make the agent respond more short and concise?**  \n  **A:** Make your message/post examples all short & concise (answered by Phoenix | Livepeer-Eliza.com)\n\n- **Q: How do I enable DEBUG mode to see what's wrong with my plugin?**  \n  **A:** Use DEFAULT_LOG_LEVEL=debug pnpm dev or try trace level (answered by Odilitime)\n\n- **Q: What makes eliza different from other agent frameworks?**  \n  **A:** Most starred and active open source github repo to build ai agents in crypto; TypeScript language is more accessible than other dev languages; Vibrant community; Most serious project about integrating AI to community management (answered by Ka_yari)\n\n- **Q: How can I report a vulnerability?**  \n  **A:** Dm @shaw, he'll help you with the vulnerability report (answered by BOSSU)\n\n**Project Direction**\n- **Q: Why ai16z should be stayed as DAO? Is it efficient at this moment? What DAO did so far for this project?**  \n  **A:** We're moving away from that name to ElizaOS. It's a DAO because we treat holders as partners. With new tokenomics coming soon, the token will be the backbone of ElizOS eco (answered by HoneyBadger)\n\n- **Q: How do we know if our character is getting selected for the block tank event?**  \n  **A:** We're building a process for sifting through submissions and following up. Personally I want it to feel like an event for being chosen / getting on the show (answered by jin)\n\n- **Q: Is it really possible to keep the CA but change the ticker and name?**  \n  **A:** Yes, CA won't change (answered by jin)\n\n## Community Help & Collaboration\n\n**Security Incident Response**\n- Multiple community members alerted others about Shaw's compromised Twitter account, warning against clicking links or connecting wallets\n- Bealers provided specific instructions to report phishing domains to Tucows registrar via abuse form\n- joellelb recommended using Wallet Guard and Pocket Universe to scan wallets and revoke access after the security incident\n- witch explained to concerned users that without connecting wallets or signing transactions, their funds should be safe\n\n**Technical Troubleshooting**\n- engineer helped Odilitime resolve a local SQL DB issue by switching to MongoDB using adapter-mongodb with connection string in .env\n- elizaos-bridge-odi provided a command to rebuild sqlite3 module for better-sqlite3 errors: `pnpm build && cd node_modules/better-sqlite3 && pnpm rebuild && cd ../.. && pnpm start`\n- Odilitime helped pupathebig with plugin loading failures by providing debugging tips including log level settings\n- lefrog explained to \ud83e\udde7ThanosDaSith24\ud83e\udde7 how to create private chatrooms by passing userID and roomID parameters\n- \ua9c1Ninja_Dev\ua9c2 confirmed to BowTiedBlueFin that each character and agent has separate memory against each user\n- Mr. Stark shared configuration settings with LucaP to avoid Twitter bot rate limits and shadow bans\n\n**Content Creation Collaboration**\n- boom helped fishai with background music recommendations for the TV show intro, sharing multiple music options\n- fishai created a revised intro video for jin with tightened transitions and added voiceovers\n- boom shared a collection of graphics elements via elements.envato.com link for the show\n\n## Action Items\n\n### Technical\n- **Security**\n  - Implement security measures to prevent Twitter account compromises (Mentioned by Multiple users)\n  - Take down malicious links from hacked account (Mentioned by \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f)\n  - Set up monitoring to take down any malicious units shared (Mentioned by \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f)\n  - Report domains eliza-os.net and elizaos.co to Tucows registrar (Mentioned by Bealers)\n  - Delete fraudulent posts from compromised Shaw account (Mentioned by hyper)\n  - Secure compromised social media accounts (Mentioned by Bealers)\n  - Restore/unban the DegenAI Twitter account (Mentioned by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f)\n  - Implement on-chain communications via token memos with frontend website for verification (Mentioned by jin)\n\n- **Framework Improvements**\n  - Fix better-sqlite3 installation issues by rebuilding the module (Mentioned by elizaos-bridge-odi)\n  - Implement proper memory separation by user ID for multi-user environments (Mentioned by BowTiedBlueFin)\n  - Create REST API documentation for client-direct (Mentioned by lefrog)\n  - Fix Twitter rate limiting and shadow ban issues (Mentioned by LucaP)\n  - Improve plugin loading error messages and debugging (Mentioned by pupathebig)\n  - Add agent identifiers to the eliza logger (Mentioned by uai_thne)\n  - Change client's listening address from localhost to server IP (Mentioned by Roforico)\n\n- **Trading Platform**\n  - Iterate on Trading v2 platform to implement more complex quantitative strategies (Mentioned by rhota)\n  - Implement fee capture from trading pools using the network coin (Mentioned by DorianD)\n  - Create liquidity pairs between AI16 and agent projects in treasury (zerebro, arc, etc.) (Mentioned by yikesawjeez)\n\n- **Content Creation**\n  - Fix frame errors in intro video (Mentioned by fishai)\n  - Adjust fade timing in intro (currently too long) (Mentioned by jin)\n  - Create stingers/transition bumpers for PlayCanvas default loading screens (Mentioned by fishai)\n  - Record browser playback of episodes and edit with intro/outro (Mentioned by jin)\n  - Remove ai16z mugs from content (Mentioned by Odilitime)\n\n### Documentation\n- Add Discord link to the website for easier discovery (Mentioned by Milan)\n- Document how to run multiple agents simultaneously (Mentioned by ivorad)\n- Create documentation for the REST API (Mentioned by jin)\n- Document how to enable DEBUG mode for troubleshooting (Mentioned by pupathebig)\n- Create security advisory about ongoing phishing attempts (Mentioned by Bealers)\n- Document the long-term strategy and buyback mechanisms (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create guide for token launches with minimum requirements (Mentioned by yikesawjeez)\n\n### Features\n- Change \"What Did You Get Done This Week\" format to \"Clank Tank\" game show (Mentioned by jin)\n- Create a process for selecting submissions for the Block Tank event (Mentioned by jin)\n- Implement voice AI feature for analysis of voice recordings (Mentioned by winded4752)\n- Suggest X implement new security features to prevent crypto scams (Mentioned by MJ)\n- Suggest Pump Fun implement KYC and limit token creation to prevent scams (Mentioned by MJ)\n- Implement immediate response while processing longer requests (Mentioned by Shinkowski II)\n- Create a way to filter certain words from agent output (Mentioned by Mr. Stark)\n- Position token as an \"agent meta index fund\" with liquidity pairs for all relevant AI projects (Mentioned by yikesawjeez)\n- Add voiceovers to the intro (Mentioned by jin)\n- Implement token migration from ai16z to ElizaOS (Mentioned by mat)\n- Expand to multiple blockchains, particularly with BNB Chain (Mentioned by DannyNOR NoFapArc)\n- Develop compliance agent for social media (Mentioned by shaw)\n- Create LAMP stack equivalent for agents (Mentioned by jin)\n- Develop agent swarm system with role-based privileges (Mentioned by shaw)\n- Implement social awareness for agents (Mentioned by shaw)\n- Create a template for swarm of agents for crypto projects (Mentioned by witch)"
  },
  "ai_news_elizaos_discord_md_2025-02-14": {
    "filename": "2025-02-14.md",
    "content": "# elizaOS Discord - 2025-02-14\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **ElizaOS V2 Progress**: Shaw reported significant progress on the development of ElizaOS V2, which features a swarm of autonomous agents that can work together. The system allows agents to recognize \"boss\" relationships, execute tasks based on roles, and interact with each other (e.g., a compliance agent preventing a social media agent from posting problematic content).\n- **Database Adapters**: Users discussed solutions for vector mismatch errors, with many successfully resolving issues by switching from SQLite to MongoDB or by using different embedding models.\n- **Plugin Development**: Active discussions around the plugin registry (https://github.com/elizaos-plugins) and creating custom plugins for specific use cases. Several PRs were merged successfully.\n- **Room Model Concept**: Shaw explained that the room model in Eliza allows agents to interact with multiple other agents and people in a shared space, facilitating multi-agent conversations.\n\n### Project Structure & Branding\n- **Brand Consolidation**: The team is working on consolidating their brand identity, debating whether to merge their Twitter accounts (ai16zdao and elizaOS) and standardize on blue coloring rather than orange.\n- **Token Renaming**: Discussions about renaming the token from ai16z to elizaOS, though the team faces legal constraints in how explicitly they can mention this before the official change.\n- **Organizational Structure**: Debate about whether ElizaOS and ai16zdao should be managed as separate entities or combined under one team, with TyePo suggesting focusing on one account until the project develops further.\n\n### DegenAI Updates\n- **Trading Strategy**: Rhota shared details about DegenAI's current trading approach, which uses a basic take profit/stop loss strategy with plans to test randomization and indicator-based strategies.\n- **Twitter Account Suspension**: DegenAI's Twitter account was suspended, with the team working to restore it. Speculation that the suspension occurred because it wasn't disclosed that the account is automated.\n- **New Data Layer**: The team implemented a new data/sentiment layer to enhance DegenAI's trading functionality, moving beyond the initial basic implementation that scraped trending tokens from Birdeye.\n\n### Tokenomics Discussion\n- **Liquidity Issues**: The team is addressing problems with their \"pumpfun LP model\" using a linear approach. Witch proposed a new strategy where agents would have their own AT/Sol pools rather than being pooled with ai16z, while still using trading fees to buy back ai16z tokens.\n- **Token Sink Mechanisms**: Mat suggested focusing on token sink mechanisms during the startup phase to address liquidity concerns.\n\n### Media Production\n- **AI TV Show Development**: A team is creating video assets for an AI-related TV show or podcast, including stingers, bumpers, and intro/outro sequences. The show appears to be replacing X space sessions.\n- **Format Change**: Discussion about changing the format of \"What Did You Get Done This Week\" (WDYGDTW) to something more engaging like a game show inspired by Shark Tank, now called \"Clank Tank.\"\n\n## Key Questions & Answers\n\n### Technical Implementation\n- **Q**: How can I fix the vector mismatch error in SQLite?  \n  **A**: Switch from local database to MongoDB using adapter-mongodb by adding your connection string to MONGODB_CONNECTION_STRING in .env (answered by engineer)\n\n- **Q**: Can someone explain why Eliza agents need a room and roomID?  \n  **A**: Room model allows agents to be in a room with many other agents and people, facilitating multi-agent conversations (answered by shaw)\n\n- **Q**: How can I make my agent stop conversing after a certain number of replies on Twitter?  \n  **A**: You can modify the Twitter client to count interactions and ignore after reaching a limit (answered by elizaos-bridge-odi)\n\n- **Q**: Which node version is used to compile the main Eliza repo?  \n  **A**: Node v23.3.0 (answered by Tobiloba)\n\n- **Q**: How to create a plugin that executes regularly without user input?  \n  **A**: Copy and modify the Twitter client for your use case (answered by elizaos-bridge-odi)\n\n### Project Direction\n- **Q**: What trading strategies is DegenAI currently using?  \n  **A**: A basic take profit/stop loss strategy with specific percentages at different price points (answered by rhota)\n\n- **Q**: Should the project consolidate to one Twitter account or maintain separate accounts?  \n  **A**: Most partners favor consolidation, and the team is working toward this, likely within a week (answered by jasyn_bjorn)\n\n- **Q**: Why wasn't the $ai16z token mentioned in the roadmap?  \n  **A**: Legal constraints prevent explicit promotion before the official ticker change (answered by jasyn_bjorn)\n\n- **Q**: Is there like a civitai for Eliza stuff, a website people post character files and plugins to?  \n  **A**: There's a plugin registry at https://github.com/elizaos-plugins (answered by Patt)\n\n- **Q**: Where do I begin learning how to build AI agents?  \n  **A**: Check https://github.com/elizaos/awesome-eliza and join the dev channels (answered by Patt)\n\n## Community Help & Collaboration\n\n### Technical Problem Solving\n- **Vector Mismatch Resolution**: Engineer helped Odilitime resolve vector mismatch errors by switching from SQLite to MongoDB adapter, adding the connection string to .env.\n\n- **Node Version Compatibility**: Pagameba assisted Necron Don with node version compatibility issues by suggesting using node 23.3 and reinstalling node_modules.\n\n- **Package Dependencies**: Neodotneo helped Redd resolve an error with onnxruntime-node dependency by suggesting adding an override in package.json, which worked with yarn.\n\n- **Debugging Context**: Psyfreak directed lefrog to packages/core/generation.ts in the generateText function for viewing input context when debugging.\n\n### Project Guidance\n- **Plugin Registry**: Ian helped with plugin registry submission, resulting in a successfully merged PR.\n\n- **Trading Strategy Explanation**: Rhota provided a detailed breakdown of current and planned trading strategies in response to PrudentSpartan's request for more specific information.\n\n- **Brand Clarification**: SM Sith Lord helped clarify brand naming confusion, noting that \"Block Tank\" is now \"Clank Tank\" and \"ai16z\" should be \"ElizaOS\" in most cases.\n\n## Action Items\n\n### Technical\n- Complete development of agent swarm architecture for ElizaOS V2 (Mentioned by shaw)\n- Implement role-based permissions system for agents (Mentioned by shaw)\n- Develop social awareness capabilities for agents (Mentioned by shaw)\n- Fix vector mismatch error by switching from local database to MongoDB adapter (Mentioned by engineer)\n- Modify Twitter client to limit conversation depth (Mentioned by elizaos-bridge-odi)\n- Implement proper memory management for multi-user systems (Mentioned by BowTiedBlueFin)\n- Fix Twitter media upload functionality (Mentioned by Mr. SUI)\n- Implement and test randomized trading strategies with varying aggressiveness levels (Mentioned by rhota)\n- Develop indicator-based trading strategies using VWAP (Mentioned by rhota)\n- Work with execution provider to build real-time indicator tracking for fast-moving meme tokens (Mentioned by rhota)\n- Restore DegenAI's suspended Twitter account (Mentioned by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f)\n- Complete token renaming from ai16z to elizaOS (Mentioned by witch)\n- Create stingers/transition bumpers for play canvas default loading screens (Mentioned by fishai)\n- Fix frame errors and off-beat hits in the intro video (Mentioned by fishai)\n- Implement staking mechanisms/LP rewards to incentivize liquidity provision (Mentioned by witch)\n- Develop token sink mechanisms as part of startup phase focus (Mentioned by mat)\n\n### Documentation\n- Create comprehensive overview of project vision that ties individual features to the bigger picture (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Establish a structured content repository beyond Twitter for long-term documentation (Mentioned by accelxr)\n- Update all social channels, website and GitHub with consistent branding (Mentioned by pragmatiko)\n- Create clear explanation of DegenAI's purpose, value proposition, and ecosystem role (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Develop infographic explaining trading strategies in less technical terms (Mentioned by rhota)\n- Update website with comprehensive DegenAI information (Mentioned by rhota)\n- Create guide for integrating adapter-supabase (Mentioned by Mohit)\n- Update plugin template link in registry README (Mentioned by ian)\n- Define proper organizational structure for ElizaOS and ai16zdao/ElizaDAO (Mentioned by Odilitime)\n- Create a comprehensive guide for new users explaining Eliza's core concepts like rooms (Implied from multiple basic questions)\n- Improve visibility of resources like YouTube channel and recordings (Implied from Cryptosi.eth's difficulty finding resources)\n- Clearly communicate how the new pool strategy adds value to ai16z token through buybacks and LP additions (Mentioned by witch)\n\n### Feature\n- Add agent identifiers to eliza logger (Mentioned by uai_thne)\n- Create custom RAG for document processing (Mentioned by Salacoste)\n- Implement WebSocket support for real-time data (Mentioned by ualp.)\n- Add voice analysis capability (Mentioned by winded4752)\n- Development of plugin for working with embeddings and memory retrieval using similarity scores (Mentioned by Daniel BNV)\n- AI chatbot for crypto applications powered by Eliza (Mentioned by DIGITAL TUNDRA)\n- Add graphical analysis capabilities similar to gemxbt (Mentioned by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f)\n- Integrate DegenAI with Discord channels (Mentioned by Patt)\n- Eventually have an AI agent manage the X account (Mentioned by TyePo)\n- Consider rebranding ai16zdao to ElizaDAO (Mentioned by TyePo and flockaflame)\n- Create a template for swarm of agents that could be deployed to launch a crypto project (Mentioned by witch)\n- Create a group chat for official ElizaOS/DAO partners (Mentioned by CtrlAltElite)\n- Create TV screen images for news segments that can be reusable (Mentioned by jin)\n- Develop a new format for community updates replacing \"What Did You Get Done This Week\" (Mentioned by jin)\n- Develop a character generator tool for ElizaOS (Mentioned by Rick)\n- Create a repository for sharing character files similar to Civitai (Mentioned by Feddie Xtzeth)"
  },
  "ai_news_elizaos_discord_md_2025-02-13": {
    "filename": "2025-02-13.md",
    "content": "# elizaOS Discord - 2025-02-13\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Updates\n\n- **ElizaOS V2 Progress**: The team is restructuring the plugin architecture to allow plugins to live in separate repositories for better scalability. Shaw is fully dedicated to shipping V2, with internal release targets moved up.\n\n- **Docker & Deployment Issues**: Multiple users reported issues with Docker containers, particularly with ARM64 architecture and module dependencies. Solutions included installing required dependencies with `apt-get update && apt-get install -y wget` and using `node:23-slim`.\n\n- **Memory Management Challenges**: Users discussed context exceeding the 128K token limit after Twitter agents run for a while, and vector mismatch errors in SQLite databases. Odilitime suggested using OpenAI embeddings instead of local ones to resolve vector issues.\n\n- **Twitter Integration**: Several discussions focused on Twitter functionality, including thread creation, media uploads, and API limitations. The `buildConversationThread` method in `utils.ts` inside client-twitter was highlighted as the key to implementing thread posting.\n\n- **Hosting Options**: Community members discussed various hosting solutions including AWS, GCP, Railway, Akash, and Concabo, with 4-8GB RAM being recommended as sufficient for most ElizaOS deployments.\n\n### DegenAI Development\n\n- **Trading Strategy Updates**: DegenAI has moved from a basic implementation to a more sophisticated version with a data/sentiment layer. The current strategy uses basic take profit/stop loss approaches with specific percentages.\n\n- **Future Trading Plans**: The team plans to implement randomized trading strategies with varying aggressiveness levels and develop indicator-based strategies using VWAP. They noted challenges with traditional indicators from sources like TradingView updating too slowly for fast-moving meme tokens.\n\n### Branding & Communication Strategy\n\n- **Brand Consolidation Debate**: Extensive discussion occurred about whether to consolidate the project's two X (Twitter) accounts - ai16zdao and ElizaOS - into a single account. A poll showed strong support for consolidation.\n\n- **Brand Identity Clarification**: Jin explained the distinction between the two brands: ElizaOS represents the professional, technical side with a blue theme and GitHub organization, while ai16zdao embodies the investment DAO, crypto culture, and orange branding.\n\n- **Token Renaming**: The team has decided to rename the token from ai16z to elizaOS, but can't change the ticker yet due to technical issues with daosfun. Legal considerations are also affecting how they communicate about the token.\n\n### Tokenomics & Launchpad\n\n- **Dual Pool Model**: The team confirmed they're using a dual pool model for agent tokens: AT/SOL and AI16Z/AT, which differs from competitors like Virtuals and Arc who pair directly with their platform tokens.\n\n- **Launchpad Progress**: The launchpad technology is ready with a partnership secured with a Solana ecosystem player for custom LP solutions. Three additional partners have signed on to launch with them.\n\n### 3D AI TV Project\n\n- **Visual Asset Management**: The team is creating generic category-based images for a news aggregator system that displays content on TVs in a virtual environment, as a temporary solution until the aggregator provides better images.\n\n- **Branding Updates**: \"Block Tank\" has been renamed to \"Clank Tank\" and most references to \"ai16z\" should be changed to \"ElizaOS\" except when discussing the token specifically.\n\n## Key Questions & Answers\n\n**Q: How do I fix the module error \"@anush008/tokenizers-linux-arm64-gnu\" in Docker?**  \nA: Install wget and other dependencies with \"apt-get update && apt-get install -y wget\" and use node:23-slim.\n\n**Q: How do I specify which model to use with TogetherAI API?**  \nA: Edit the models.ts file in the core package.\n\n**Q: What are recommended specs for hosting ElizaOS?**  \nA: 4-8GB RAM is sufficient for most deployments.\n\n**Q: How do I make a Twitter agent post in threads instead of single tweets?**  \nA: Check utils.ts inside client-twitter and look for the buildConversationThread method.\n\n**Q: How do I create a plugin that executes regularly without user input?**  \nA: Copy and modify the Twitter client as a starting point.\n\n**Q: How do I fix vector mismatch error with SQLite?**  \nA: Try using OpenAI embeddings instead of local ones for consistent dimensions.\n\n**Q: What trading strategies is DegenAI currently using?**  \nA: A basic take profit/stop loss strategy with specific percentages for profit-taking and stop-loss levels.\n\n**Q: Is AI16Z still planning to pair agent tokens with SOL instead of AI16Z?**  \nA: Yes, with a dual pool model that includes both AT/SOL and AI16Z/AT pools.\n\n**Q: What is the status of the launchpad?**  \nA: The tech is ready, with a partnership secured with a top-tier Solana ecosystem player for custom LP solutions. Three additional partners have signed on to launch.\n\n**Q: Will the ai16z and ElizaOS social accounts be consolidated?**  \nA: A poll showed strong support for consolidation, and the team is working with brand designers to refine the brandkit.\n\n## Community Help & Collaboration\n\n1. **Docker Build Issues**\n   - Helper: Derby\n   - Helpee: minco\n   - Context: Cannot find module '@anush008/tokenizers-linux-arm64-gnu' in Docker\n   - Resolution: Install wget and other dependencies with apt-get and use node:23-slim\n\n2. **Model Selection with TogetherAI**\n   - Helper: Odilitime\n   - Helpee: Slise\n   - Context: How to specify which model to use with TogetherAI API\n   - Resolution: Edit models.ts file in the core package\n\n3. **Twitter Thread Creation**\n   - Helper: elizaos-bridge-odi\n   - Helpee: amit\n   - Context: How to make Twitter agent post in threads\n   - Resolution: Check utils.ts inside client-twitter for buildConversationThread method\n\n4. **Scheduled Plugin Execution**\n   - Helper: elizaos-bridge-odi\n   - Helpee: miladyboy\n   - Context: Creating a plugin that executes regularly without user input\n   - Resolution: Copy and modify the Twitter client\n\n5. **Vector Mismatch Resolution**\n   - Helper: Odilitime\n   - Helpee: engineer\n   - Context: Vector mismatch error with SQLite\n   - Resolution: Try using OpenAI embeddings instead of local ones\n\n6. **Tokenomics Model Explanation**\n   - Helper: witch\n   - Helpee: mat\n   - Context: Explaining why the dual pool model is beneficial despite differing from competitors\n   - Resolution: Witch explained that the approach prevents transferring liquidity issues to new projects while still adding value to AI16Z through buybacks\n\n7. **Project Updates for Partners**\n   - Helper: accelxr\n   - Helpee: Multiple partners\n   - Context: Partners were concerned about lack of transparency and progress updates\n   - Resolution: Provided a comprehensive update on all projects including DegenAI, The Autonomous Investor, V2, and Launchpad, with screenshots of the sentiment data hub\n\n## Action Items\n\n### Technical Tasks\n\n1. **Docker & Deployment**\n   - Fix Docker build for ARM64 architecture by installing required dependencies | Mentioned By: Derby\n   - Implement proper error handling for token limit exceeding 128K | Mentioned By: passer\n   - Add support for API key in Gaianet integration | Mentioned By: Slise\n   - Fix vector mismatch error in SQLite | Mentioned By: engineer\n   - Move database outside Docker container for better scaling | Mentioned By: Paul - Zyfi\n\n2. **Twitter & Social Media Integration**\n   - Fix Twitter media upload functionality | Mentioned By: Mr. SUI\n   - Add thread creation capability for Twitter | Mentioned By: amit\n   - Determine whether to consolidate ai16zdao/ElizaOS X accounts | Mentioned By: jin\n   - Complete the token renaming from ai16z to elizaOS | Mentioned By: witch\n\n3. **DegenAI Enhancements**\n   - Implement randomized trading strategies with varying aggressiveness levels | Mentioned By: rhota\n   - Develop indicator-based strategies using VWAP | Mentioned By: rhota\n   - Solve indicator data latency issues | Mentioned By: rhota\n\n4. **ElizaOS Core Development**\n   - Complete the restructuring of plugins to live in separate repositories | Mentioned By: accelxr\n   - Finalize the sentiment/data layer integration for DegenAI V2 | Mentioned By: accelxr\n   - Create mechanism to limit agent conversation depth | Mentioned By: brka\n   - Refine plugin for embedding-based memory retrieval | Mentioned By: Daniel BNV\n\n5. **3D AI TV Project**\n   - Create generic images/videos for each news category | Mentioned By: SM Sith Lord\n   - Create a fallback generic image for unexpected categories | Mentioned By: SM Sith Lord\n   - Adjust episode generator to specify category instead of image URLs | Mentioned By: SM Sith Lord\n   - Create stingers/bumpers for transitions | Mentioned By: jin\n   - Update branding from \"Block Tank\" to \"Clank Tank\" | Mentioned By: SM Sith Lord\n\n### Documentation Needs\n\n1. **Integration Guides**\n   - Create guide for adapter-supabase integration | Mentioned By: Mohit\n   - Update plugin registry documentation with correct links | Mentioned By: ian | sqd.ai\n   - Create or improve documentation about room/roomID concept | Mentioned By: parksthecoder\n   - Clarify where demo day recordings are posted | Mentioned By: Cryptosi.eth\n\n2. **Brand & Communication**\n   - Clarify the distinct brand identities of ElizaOS vs ai16zdao | Mentioned By: jin\n   - Create clear explanation of DegenAI's value proposition | Mentioned By: \ucc0c G \u8dfb \u3058\n   - Improve technical communications with less jargon | Mentioned By: \ucc0c G \u8dfb \u3058\n   - Update website with comprehensive DegenAI information | Mentioned By: \ucc0c G \u8dfb \u3058\n   - Update tokenomics documentation to explain the dual pool model | Mentioned By: witch\n   - Create a comprehensive overview that ties features to vision | Mentioned By: \ucc0c G \u8dfb \u3058 PrudentSpartan\n   - Establish a permanent home for content beyond Twitter | Mentioned By: accelxr\n\n### Feature Requests\n\n1. **Integration & Connectivity**\n   - Add support for WebSocket connections | Mentioned By: ualp.\n   - Implement scheduled tasks without user input | Mentioned By: miladyboy\n   - Develop or document Telegram integration for Eliza agents | Mentioned By: npizza.\n\n2. **Platform Enhancements**\n   - Add graphical analysis capabilities similar to gemxbt | Mentioned By: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f\n   - Implement staking mechanisms/LP rewards for liquidity | Mentioned By: witch\n   - Launch the agent marketplace/launchpad with custom LP solution | Mentioned By: accelxr\n   - Implement the accelerator program for ETHDenver | Mentioned By: accelxr\n   - Develop a more engaging social media strategy | Mentioned By: HoneyBadger\n   - Create centralized repository for Eliza character files | Mentioned By: Feddie Xtzeth"
  },
  "ai_news_elizaos_daily_json_2025-02-15": {
    "filename": "2025-02-15.json",
    "content": {
      "type": "elizaosDailySummary",
      "title": "Daily Report - 2025-02-15",
      "categories": [
        {
          "title": "DankVR's Tech Insights: VRM Tools, Blockchain Security, and Community Building",
          "content": [
            {
              "text": "DankVR shared VRM-related tools and tips, including a VRM optimizer that allows drag-and-drop of multiple VRMs at once with batch download functionality. They also mentioned an open-source VRM to LoRA training pipeline for those with access to VRM files.",
              "sources": [
                "https://twitter.com/dankvr/status/1890878378778984601",
                "https://twitter.com/dankvr/status/1890868343550194103"
              ],
              "images": [
                "https://pbs.twimg.com/media/Gj22n_WXIAAVp29.jpg",
                "https://pbs.twimg.com/media/Gj22pxXWkAEF8r6.jpg"
              ],
              "videos": []
            },
            {
              "text": "On blockchain security, DankVR discussed onchain communications as a more secure alternative to platforms like Twitter and Discord, which are vulnerable to account hijacking. They tested various wallets for memo support, finding that Rabby, Leap, Phantom, and Zcash offer this functionality, while MetaMask and Magic Eden don't. They highlighted how DAOs can use token2022 standard for onchain messaging as backup communication.",
              "sources": [
                "https://twitter.com/dankvr/status/1890848135896846780",
                "https://twitter.com/dankvr/status/1890843125372891279",
                "https://twitter.com/dankvr/status/1890841242583416991"
              ],
              "images": [
                "https://pbs.twimg.com/media/Gj2OULYWYAALMZ-.png"
              ],
              "videos": []
            },
            {
              "text": "DankVR warned about the dangers of signing malicious transactions, noting that unlike disconnecting apps, signing a malicious signature requires creating a new seed phrase as there's no recovery option. They also pointed out scammers using verified badges on Twitter to impersonate legitimate accounts.",
              "sources": [
                "https://twitter.com/dankvr/status/1890801638127878313",
                "https://twitter.com/dankvr/status/1890799216731025818",
                "https://twitter.com/dankvr/status/1890778469216231828",
                "https://twitter.com/dankvr/status/1890777551427035645"
              ],
              "images": [
                "https://pbs.twimg.com/media/Gj14-grWYAAEx6S.jpg"
              ],
              "videos": []
            },
            {
              "text": "On community building, DankVR discussed the challenge of high performers disengaging when faced with excessive complaints from less active members. They suggested implementing contribution-based reputation systems with on-chain tracking of verifiable work like GitHub commits and governance proposals to create more balanced, sustainable communities.",
              "sources": [
                "https://twitter.com/dankvr/status/1890621804277834233",
                "https://twitter.com/dankvr/status/1890609982875259000",
                "https://twitter.com/dankvr/status/1890608513388327271"
              ],
              "images": [
                "https://pbs.twimg.com/media/GjzIirMW0AAsIvF.png"
              ],
              "videos": []
            },
            {
              "text": "Shaw, a collaborator, shared progress on an AI onboarding system where agents onboard in their own voice and receive necessary information with follow-up tasks. Shaw humorously noted needing \"an AI COO to onboard the AI freelancers,\" suggesting they're developing a sophisticated AI workflow system.",
              "sources": [
                "https://twitter.com/shawmakesmagic/status/1890898181249999340",
                "https://twitter.com/shawmakesmagic/status/1890701636189700514",
                "https://twitter.com/shawmakesmagic/status/1890699433420943864"
              ],
              "images": [
                "https://pbs.twimg.com/media/Gj3RctyW0AA68dm.jpg",
                "https://pbs.twimg.com/media/Gj0c1F1XYAAeren.jpg"
              ],
              "videos": []
            }
          ],
          "topic": "tweet"
        },
        {
          "title": "Recent Updates to the Eliza Project",
          "content": [
            {
              "text": "The Eliza project has seen several recent updates across different areas:\n\n**Bug Fixes:**\n- Fixed Vitest issues in the TypeScript generator (tg)\n- Resolved Discord test failures\n- Refactored hardcoded 'http://localhost' strings to use the SERVER_URL environment variable in the client\n- Addressed security vulnerability CVE-2024-48930\n\n**Features:**\n- Added ElevenLabs default voice support\n- Implemented cachedir functionality to the filesystem cache\n\n**Documentation:**\n- Added a proper Ukrainian translation of the README file\n\n**Other Changes:**\n- Bumped version numbers and updated the lockfile\n- Moved character definitions to a separate submodule for better organization",
              "sources": [
                "https://github.com/elizaOS/eliza/pull/3524",
                "https://github.com/elizaOS/eliza/pull/3523",
                "https://github.com/elizaOS/eliza/pull/3519",
                "https://github.com/elizaOS/eliza/pull/3518",
                "https://github.com/elizaOS/eliza/pull/3511",
                "https://github.com/elizaOS/eliza/pull/3509",
                "https://github.com/elizaOS/eliza/pull/3483",
                "https://github.com/elizaOS/eliza/pull/3291",
                "https://github.com/elizaOS/eliza/pull/2958"
              ],
              "images": [],
              "videos": []
            }
          ],
          "topic": "completed_items"
        },
        {
          "title": "Recent Pull Requests in elizaOS/eliza Repository",
          "content": [
            {
              "text": "Several pull requests have been submitted to the elizaOS/eliza repository, showing active development across multiple areas:\n\n- HashWarlock submitted PR #3512 to update the tee feature\n- tenthirtyone created PR #3511 to refactor hardcoded localhost URLs with environment variables in the client\n- odilitime merged PR #3522 for the 0.25.8 release, moving code from develop to main branch\n- lggg123 contributed PR #3536 related to a Sui agent hackathon feature\n- AIFlowML submitted PR #3526 to refactor the Plugin Local AI\n- yungalgo created PR #3516 to consolidate RAG (Retrieval-Augmented Generation) knowledge\n\nThese pull requests demonstrate ongoing improvements to the Eliza project across features, infrastructure, and knowledge management.",
              "sources": [
                "https://github.com/elizaOS/eliza/pull/3512",
                "https://github.com/elizaOS/eliza/pull/3511",
                "https://github.com/elizaOS/eliza/pull/3522",
                "https://github.com/elizaOS/eliza/pull/3536",
                "https://github.com/elizaOS/eliza/pull/3526",
                "https://github.com/elizaOS/eliza/pull/3516"
              ],
              "images": [
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3512",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3511",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3522",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3536",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3526",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/3516"
              ],
              "videos": []
            }
          ],
          "topic": "pull_request"
        },
        {
          "title": "Recent GitHub Issues in elizaOS/eliza Repository",
          "content": [
            {
              "text": "Three recent issues have been reported in the elizaOS/eliza GitHub repository:\n\n1. Issue #3513: A user named kon-rad reported that the client is showing a blank page with errors.\n\n2. Issue #3514: User Etette encountered a port scanning error specifically when using Render.\n\n3. Issue #3527: User andyvalerio identified an incorrect import in the advanced-sdk-ts component.",
              "sources": [
                "https://github.com/elizaOS/eliza/issues/3513",
                "https://github.com/elizaOS/eliza/issues/3514",
                "https://github.com/elizaOS/eliza/issues/3527"
              ],
              "images": [
                "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/3513",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/3514",
                "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/3527"
              ],
              "videos": []
            }
          ],
          "topic": "issue"
        },
        {
          "title": "ElizaOS GitHub Activity Summary",
          "content": [
            {
              "text": "The elizaos/eliza repository showed significant activity over a two-day period. From February 15-16, 2025, there were 2 new PRs (none merged), 2 new issues, and 9 active contributors. Activity increased substantially the following day (February 16-17, 2025) with 18 new PRs (9 merged), 2 new issues, and 21 active contributors. This represents a notable increase in both pull request activity and contributor participation between the two days.",
              "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"
        }
      ],
      "date": 1739577600
    }
  },
  "ai_news_elizaos_daily_md_2025-02-15": {
    "filename": "2025-02-15.md",
    "content": "# DankVR's Tech Insights: VRM Tools, Blockchain Security, and Community Building\n\n## VRM-Related Tools and Tips\n- Shared VRM optimizer with drag-and-drop functionality for multiple VRMs\n- Batch download capability included\n- Mentioned open-source VRM to LoRA training pipeline\n\n## Blockchain Security\n- Discussed onchain communications as more secure alternative to Twitter and Discord\n- Tested wallets for memo support:\n  - Supported: Rabby, Leap, Phantom, and Zcash\n  - Not supported: MetaMask and Magic Eden\n- Highlighted DAOs using token2022 standard for onchain messaging\n- Warned about dangers of signing malicious transactions\n- Noted scammers using verified badges on Twitter for impersonation\n\n## Community Building\n- Addressed challenge of high performers disengaging due to excessive complaints\n- Suggested contribution-based reputation systems\n- Proposed on-chain tracking of verifiable work (GitHub commits, governance proposals)\n\n## AI Onboarding System\n- Shaw shared progress on AI onboarding system\n- System allows agents to onboard in their own voice\n- Provides necessary information with follow-up tasks\n\n# Recent Updates to the Eliza Project\n\n## Bug Fixes\n- Fixed Vitest issues in the TypeScript generator\n- Resolved Discord test failures\n- Refactored hardcoded localhost strings to use SERVER_URL environment variable\n- Addressed security vulnerability CVE-2024-48930\n\n## Features\n- Added ElevenLabs default voice support\n- Implemented cachedir functionality to the filesystem cache\n\n## Documentation\n- Added Ukrainian translation of the README file\n\n## Other Changes\n- Bumped version numbers and updated lockfile\n- Moved character definitions to a separate submodule\n\n# Recent Pull Requests in elizaOS/eliza Repository\n\n- HashWarlock: Updated tee feature (PR #3512)\n- tenthirtyone: Refactored hardcoded localhost URLs with environment variables (PR #3511)\n- odilitime: Merged 0.25.8 release, moving code from develop to main branch (PR #3522)\n- lggg123: Contributed Sui agent hackathon feature (PR #3536)\n- AIFlowML: Refactored Plugin Local AI (PR #3526)\n- yungalgo: Consolidated RAG knowledge (PR #3516)\n\n# Recent GitHub Issues in elizaOS/eliza Repository\n\n- Issue #3513: Client showing blank page with errors (reported by kon-rad)\n- Issue #3514: Port scanning error when using Render (reported by Etette)\n- Issue #3527: Incorrect import in advanced-sdk-ts component (reported by andyvalerio)\n\n# ElizaOS GitHub Activity Summary\n\n- Feb 15-16, 2025: 2 new PRs, 2 new issues, 9 active contributors\n- Feb 16-17, 2025: 18 new PRs (9 merged), 2 new issues, 21 active contributors\n- Notable increase in both pull request activity and contributor participation"
  },
  "ai_news_elizaos_daily_discord_json_2025-02-15": {
    "filename": "2025-02-15.json",
    "content": {
      "server": "elizaOS",
      "title": "elizaOS Discord - 2025-02-15",
      "date": 1739577600,
      "stats": {
        "totalMessages": 1391,
        "totalUsers": 195
      },
      "categories": [
        {
          "channelId": "1253563209462448241",
          "channelName": "discussion",
          "summary": "# Analysis of Discord Chat in \"discussion\" Channel\n\n## 1. Summary\nThe chat primarily revolves around a security incident where Shaw's Twitter account was hacked, leading to scam posts promoting a fake ElizaOS token. The hacker posted malicious links that drained users' wallets when they connected and signed transactions. Several users reported losing funds, with one claiming to have lost $40,000. Community members warned others not to click links or connect wallets until official confirmation from the team. \n\nBefore the hack, discussions focused on changing the format of the \"What Did You Get Done This Week\" (WDYGDTW) event to a \"Clank Tank\" game show inspired by Shark Tank. Jin mentioned they were planning to integrate a weekly space into this new format, potentially premiering the following Friday.\n\nThere were also brief technical discussions about ElizaOS's differentiators from other agent frameworks, with community members highlighting its TypeScript accessibility, vibrant community, and integration of AI into community management.\n\n## 2. FAQ\nQ: Does eliza have a voice ai feature? Can I submit a voice recording for analysis? (asked by winded4752) A: We can transcribe voice recordings for you, head to coders channel for all the technical details (answered by BOSSU)\nQ: What makes eliza different from other agent frameworks? (asked by Rihan) A: Most starred and active open source github repo to build ai agents in crypto; TypeScript language is more accessible than other dev languages; Vibrant community; Most serious project about integrating AI to community management (answered by Ka_yari)\nQ: Why ai16z should be stayed as DAO? Is it efficient at this moment? What DAO did so far for this project? (asked by kokoro) A: We're moving away from that name to ElizaOS. It's a DAO because we treat holders as partners. With new tokenomics coming soon, the token will be the backbone of ElizOS eco (answered by HoneyBadger)\nQ: How can I report a vulnerability? (asked by Faeeq) A: Dm @shaw, he'll help you with the vulnerability report (answered by BOSSU)\nQ: Is Shaw hacked? (asked by multiple users) A: Yes, don't trust whatever he posts for now (answered by jin)\nQ: Did you sign a transaction or connect your wallet? (asked by GBA ADVANCE) A: I signed a transaction yes (answered by bert)\nQ: My other wallets weren't connected to the site only the one that got drained so ill be fine right? (asked by bert) A: Yes king if other wallets weren't connected you should be safe, but please double check and revoke any permissions (answered by BOSSU)\nQ: How do we know if our character is getting selected for the block tank event? (asked by Bacon Egg & Cheese) A: We're building a process for sifting through submissions and following up. Personally I want it to feel like an event for being chosen / getting on the show (answered by jin)\n\n## 3. Help Interactions\nHelper: BOSSU | Helpee: Multiple users | Context: Shaw's Twitter account was hacked with scam links being posted | Resolution: Advised users to disconnect wallets, not click any links, and wait for official updates\nHelper: jin | Helpee: Community | Context: Confirming Shaw's account was hacked | Resolution: Warned users not to trust posts from Shaw's account\nHelper: \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f | Helpee: Community | Context: Malicious links from hacked account | Resolution: Confirmed taking down malicious units and setting up monitoring\nHelper: Ka_yari | Helpee: Rihan | Context: Question about ElizaOS differentiators | Resolution: Provided detailed explanation of ElizaOS advantages over other agent frameworks\nHelper: joellelb | Helpee: Community | Context: Wallet security after hack | Resolution: Recommended using Wallet Guard and Pocket Universe to scan wallets and revoke access\nHelper: scooper | Helpee: Community | Context: Deployment issues | Resolution: Shared that using develop branch without 100 plugins solved deployment problems\n\n## 4. Action Items\nType: Technical | Description: Implement security measures to prevent Twitter account compromises | Mentioned By: Multiple users\nType: Technical | Description: Take down malicious links from hacked account | Mentioned By: \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f\nType: Technical | Description: Set up monitoring to take down any malicious units shared | Mentioned By: \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f\nType: Feature | Description: Change \"What Did You Get Done This Week\" format to \"Clank Tank\" game show | Mentioned By: jin\nType: Feature | Description: Create a process for selecting submissions for the Block Tank event | Mentioned By: jin\nType: Documentation | Description: Add Discord link to the website for easier discovery | Mentioned By: Milan\nType: Feature | Description: Implement voice AI feature for analysis of voice recordings | Mentioned By: winded4752\nType: Technical | Description: Suggest X implement new security features to prevent crypto scams | Mentioned By: MJ\nType: Technical | Description: Suggest Pump Fun implement KYC and limit token creation to prevent scams | Mentioned By: MJ",
          "messageCount": 404,
          "userCount": 89
        },
        {
          "channelId": "1300025221834739744",
          "channelName": "\ud83d\udcbb-coders",
          "summary": "# Discord Chat Analysis: \ud83d\udcbb-coders Channel\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS framework implementation issues and troubleshooting. Key technical discussions include database configuration problems, agent memory management, Twitter integration challenges, and plugin development. Users frequently encounter issues with better-sqlite3 installation, which can be resolved by rebuilding the module. Multiple users sought help with separating memory by user ID to maintain privacy in multi-user environments, which is possible by passing userId and roomId parameters. Twitter integration discussions focused on rate limits, verification requirements, and avoiding shadow bans. Plugin development was another major topic, with users struggling with debugging and proper plugin loading. The chat also revealed that ElizaOS can run multiple agents simultaneously, though with memory constraints, and that various LLM providers can be used beyond the default options.\n\n## 2. FAQ\nQ: How do I delete the database? (asked by ivorad) A: Unanswered\nQ: How can I separate memory by user to keep data private between multi-users? (asked by BowTiedBlueFin) A: Pass userId and roomId parameters with your API request (answered by lefrog)\nQ: How should I request to have my plugin added directly to the elizaos-plugins organization on GitHub? (asked by Addy) A: Unanswered\nQ: Is there any way we can add agent identifiers to the eliza logger? (asked by uai_thne) A: Unanswered\nQ: Can we use jina ai on eliza? (asked by Saitamai) A: Unanswered\nQ: How do I make the agent respond more short and concise? (asked by Blockonaut | Alchemist) A: Make your message/post examples all short & concise (answered by Phoenix | Livepeer-Eliza.com)\nQ: How do I make telegram client greet new users and start conversations with them? (asked by pupathebig) A: Unanswered\nQ: Is there a tutorial on how to connect your agent chat to a website? (asked by \ud83e\udde7ThanosDaSith24\ud83e\udde7) A: Unanswered\nQ: How does an Eliza agent evade getting banned on X when using the frontend API? (asked by ad0ll) A: Unanswered\nQ: How do I enable DEBUG mode to see what's wrong with my plugin? (asked by pupathebig) A: Use DEFAULT_LOG_LEVEL=debug pnpm dev or try trace level (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: engineer | Helpee: Odilitime | Context: Local SQL DB had different embedding size from meta-llama model | Resolution: Switched to MongoDB using adapter-mongodb with connection string in .env\nHelper: \ua9c1Ninja_Dev\ua9c2 | Helpee: BowTiedBlueFin | Context: Needed to separate memory by user for privacy | Resolution: Confirmed each character and agent has separate memory against each user\nHelper: Mr. Stark | Helpee: LucaP | Context: Twitter bot rate limits and shadow bans | Resolution: Shared configuration settings and advised to only allow replies, not original posts\nHelper: elizaos-bridge-odi | Helpee: lefrog | Context: better-sqlite3 errors in eliza-starter | Resolution: Provided command to rebuild sqlite3 module: pnpm build && cd node_modules/better-sqlite3 && pnpm rebuild && cd ../.. && pnpm start\nHelper: Odilitime | Helpee: pupathebig | Context: Plugin loading failures and debugging | Resolution: Provided debugging tips including log level settings and code locations to investigate\nHelper: lefrog | Helpee: \ud83e\udde7ThanosDaSith24\ud83e\udde7 | Context: Creating private chatrooms | Resolution: Explained to pass userID and roomID parameters to isolate chats to specific users\n\n## 4. Action Items\nType: Technical | Description: Fix better-sqlite3 installation issues by rebuilding the module | Mentioned By: elizaos-bridge-odi\nType: Technical | Description: Implement proper memory separation by user ID for multi-user environments | Mentioned By: BowTiedBlueFin\nType: Technical | Description: Create REST API documentation for client-direct | Mentioned By: lefrog\nType: Technical | Description: Fix Twitter rate limiting and shadow ban issues | Mentioned By: LucaP\nType: Technical | Description: Improve plugin loading error messages and debugging | Mentioned By: pupathebig\nType: Documentation | Description: Document how to run multiple agents simultaneously | Mentioned By: ivorad\nType: Documentation | Description: Create documentation for the REST API | Mentioned By: jin\nType: Documentation | Description: Add instructions for changing client's listening address from localhost to server IP | Mentioned By: Roforico\nType: Documentation | Description: Document how to enable DEBUG mode for troubleshooting | Mentioned By: pupathebig\nType: Feature | Description: Add agent identifiers to the eliza logger | Mentioned By: uai_thne\nType: Feature | Description: Implement immediate response while processing longer requests | Mentioned By: Shinkowski II\nType: Feature | Description: Create a way to filter certain words from agent output | Mentioned By: Mr. Stark",
          "messageCount": 314,
          "userCount": 60
        },
        {
          "channelId": "1300756641406521416",
          "channelName": "ideas-feedback-rants",
          "summary": "No significant technical discussions, decisions, or problem-solving occurred in this brief chat segment. The message contains only a music recommendation from Random Disco to another user (tagged by ID), suggesting music that they describe as matching the \"vibe of the ai16z project.\" The message includes a YouTube link to a music teaser.",
          "messageCount": 1,
          "userCount": 1
        },
        {
          "channelId": "1308149076893630555",
          "channelName": "spartan_holders",
          "summary": "# Analysis of \"spartan_holders\" Discord Chat\n\n## 1. Summary\nThe chat segment primarily discusses an issue with the DegenAI Twitter account being banned. Team member rhota acknowledges they're aware of the situation and have reached out to X (Twitter) to resolve it. Additionally, rhota briefly mentions that they've implemented basic trade testing plans for their Trading v2 platform, which has only been live for a few days. They explain these are simple stress tests for buy/sell execution, with plans to iterate and develop more complex quantitative strategies in the future. Rhota also references a sentiment analysis platform as their \"secret sauce.\" The conversation shows the team is in an early implementation phase of their trading platform and is actively working on both technical development and resolving their social media presence issues.\n\n## 2. FAQ\nQ: What I shared are some very basic trade testing plans, none of that is novel? (asked by rhota) A: Self-answered by explaining these are simple stress tests for buy/sell execution with more complex quant strategies coming later (answered by rhota)\nQ: is there any possibility for unban degenspartanai official account? (asked by anotherAndrewSHA) A: We're working on \ud83d\ude4f (answered by rhota)\n\n## 3. Help Interactions\nHelper: rhota | Helpee: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f | Context: Twitter account (DegenAI) has been banned | Resolution: Team is aware and has reached out to X (Twitter)\n\n## 4. Action Items\nType: Technical | Description: Iterate on Trading v2 platform to implement more complex quantitative strategies | Mentioned By: rhota\nType: Technical | Description: Restore/unban the DegenAI Twitter account | Mentioned By: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f",
          "messageCount": 13,
          "userCount": 5
        },
        {
          "channelId": "1328592959444095038",
          "channelName": "associates",
          "summary": "# Discord Chat Analysis - \"associates\" channel\n\n## 1. Summary\nThe chat segment primarily focuses on security concerns regarding scam posts impersonating the project. Community members identified and reported multiple fraudulent Twitter/X posts from a compromised account (Shaw's) and suspicious domains (eliza-os.net and elizaos.co). Members alerted others to report these domains to the registrar (Tucows) and warned against clicking links from the compromised account. The conversation indicates this was an ongoing security incident with multiple fraudulent posts appearing throughout the morning. There was minimal technical discussion beyond security reporting procedures, with a brief mention of AI agents trending on BSC (Binance Smart Chain).\n\n## 2. FAQ\nQ: Is Shaw's post a scam? (asked by Zapdart) A: Yes it is. Be careful Frens (answered by Zapdart)\nQ: SCAM TWITTER POST FLOATING AROUND BE CAREFUL!!! (asked by GBA ADVANCE) A: Definitely a scam. Do not follow links from any of Shaw's posts until further notice (answered by Bealers)\n\n## 3. Help Interactions\nHelper: Bealers | Helpee: Community | Context: Fraudulent domains impersonating the project | Resolution: Provided specific instructions to report domains to Tucows registrar via abuse form\nHelper: Zapdart | Helpee: Community | Context: Identifying scam posts from Shaw's account | Resolution: Confirmed scam nature and tagged team members for awareness\nHelper: hyper | Helpee: Community | Context: Additional fraudulent post identified | Resolution: Shared link and requested deletion\n\n## 4. Action Items\nType: Technical | Description: Report domains eliza-os.net and elizaos.co to Tucows registrar via abuse form | Mentioned By: Bealers\nType: Technical | Description: Delete fraudulent posts from compromised Shaw account | Mentioned By: hyper\nType: Technical | Description: Secure compromised social media accounts | Mentioned By: Bealers\nType: Documentation | Description: Create security advisory about ongoing phishing attempts | Mentioned By: Bealers",
          "messageCount": 18,
          "userCount": 8
        },
        {
          "channelId": "1318770424632311930",
          "channelName": "tokenomics",
          "summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe conversation in the tokenomics channel briefly touched on value capture strategies for the project's token. DorianD suggested capturing fees from trading pools that use the network coin, noting that most trading moves away from virtual pools to these network coin pools. Later, yikesawjeez proposed a strategy to position their token as an \"agent meta index fund\" by creating liquidity pairs with various AI/agent projects already in the treasury (mentioned were zerebro, arc, and another launchpad). This would allow them to execute on a previously discussed plan to become a \"pseudo-L1 of the entire agent meta.\" The strategy would provide exposure to the AI memecoin ecosystem and offer liquidity pairs with individual projects users might want to increase positions in. There was also a brief comment about effective tokenomics containing \"a hint of ponzi-nomics\" for value capture.\n\n## 2. FAQ\nQ: How can we capture more trading fees? (asked by DorianD) A: By capturing fees from pools that use the network coin, where most trading moves to (answered by DorianD)\nQ: What strategy could position us in the AI agent ecosystem? (asked by yikesawjeez) A: Creating liquidity pairs between AI16 and various agent projects already in the treasury to become a \"pseudo-L1 of the entire agent meta\" (answered by yikesawjeez)\n\n## 3. Help Interactions\nHelper: yikesawjeez | Helpee: Channel members | Context: Expanding on tokenomics strategy for AI ecosystem positioning | Resolution: Proposed creating liquidity pairs with AI16 and various agent projects to function as an \"agent meta index fund\"\n\n## 4. Action Items\nType: Technical | Description: Implement fee capture from trading pools using the network coin | Mentioned By: DorianD\nType: Technical | Description: Create liquidity pairs between AI16 and agent projects in treasury (zerebro, arc, etc.) | Mentioned By: yikesawjeez\nType: Feature | Description: Position token as an \"agent meta index fund\" with liquidity pairs for all relevant AI projects | Mentioned By: yikesawjeez",
          "messageCount": 6,
          "userCount": 4
        },
        {
          "channelId": "1301363808421543988",
          "channelName": "\ud83e\udd47-partners",
          "summary": "# Analysis of \ud83e\udd47-partners Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around a security incident where Shaw's Twitter account was compromised. The hacker posted phishing links to fake Eliza OS websites (eliza-os.net and elizaos.co) promoting a fake token migration. Community members quickly mobilized to report the scam posts and domains. Several users who clicked the links were concerned about wallet security, though those who didn't connect wallets or sign transactions were likely safe. The incident highlighted the need for more secure communication channels, with Jin suggesting on-chain communications via memos or mirror.xyz as alternatives.\n\nShaw was also developing a new agent swarm system for v2, allowing agents to perform useful work with role-based privileges. The system enables agents to create tasks, execute them with confirmation, and interact with other agents (like a compliance agent preventing a social media agent from posting problematic content).\n\nThe community discussed the ongoing rebranding from ai16z to ElizaOS, with many noting that the ElizaOS brand is gaining recognition while ai16z remains less known. A partnership with BNB Chain was highlighted, suggesting potential for multichain expansion beyond Solana.\n\n## 2. FAQ\nQ: How can we make agents censorship resistant? (asked by Jerry.ART) A: We need on-chain agents that cannot be shut down and can perform useful on-chain activities (answered by Jerry.ART)\nQ: Why would we have increased resilience? Should we? (asked by Odilitime) A: Unanswered\nQ: When will degenai's x account suspension be restored? (asked by \ucb48\ub9ac\ub0a8\ud460) A: Skely reached out to people who helped before but they can no longer help. We're waiting on additional help. (answered by Odilitime)\nQ: What is the reason for the suspension? (asked by \ucb48\ub9ac\ub0a8\ud460) A: Unanswered\nQ: How can Shaw not have 2fa for his twitter account? (asked by M3xR) A: It is [enabled], it might not be the culprit (answered by jin)\nQ: How else could someone get access to his twitter account? (asked by M3xR) A: Twitter may disable 2FA during account recovery processes (answered by Patt)\nQ: Is it possible to have a group chat of people who are officially partnered with Eliza OS/DAO? (asked by CtrlAltElite) A: Not a bad idea (answered by jin)\nQ: Who has elizaos.eth? (asked by jin) A: Unanswered\nQ: Is it really possible to keep the CA but change the ticker and name? (asked by Patt) A: Yes, CA won't change (answered by jin)\nQ: If Shaw's acting as the CTO at Eliza Labs, is the team planning on bringing on a CEO? (asked by HoneyBadger) A: There's been no discussion of that afaik (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: Multiple community members | Helpee: Community | Context: Shaw's Twitter account was hacked with phishing posts | Resolution: Community members reported posts, reported phishing domains to registrars, and warned others not to click links\nHelper: witch | Helpee: CRAY, GBA ADVANCE | Context: Users concerned about security after clicking phishing links | Resolution: Explained that without connecting wallets or signing transactions, funds should be safe\nHelper: Bealers | Helpee: Community | Context: Identifying and reporting phishing domains | Resolution: Found domain registrar information and shared reporting links for eliza-os.net and elizaos.co\nHelper: jin | Helpee: Community | Context: Need for more secure communication channels | Resolution: Proposed on-chain communications via memos or mirror.xyz as alternatives to centralized platforms\nHelper: witch | Helpee: Jerry.ART | Context: Confusion about DegenSpartan vs. DegenspartanAI accounts | Resolution: Explained that DegenSpartan is the original account that DegenspartanAI was based on as a parody\n\n## 4. Action Items\nTechnical: Implement on-chain communications via token memos with frontend website for verification | Description: Create a system to post official communications on-chain that can be verified | Mentioned By: jin\nTechnical: Develop agent swarm system with role-based privileges | Description: Continue development of v2 agent swarm with task creation and execution capabilities | Mentioned By: shaw\nTechnical: Implement social awareness for agents | Description: Add capability for agents to understand social context and prevent problematic posts | Mentioned By: shaw\nTechnical: Create a template for swarm of agents for crypto projects | Description: Develop deployable templates with Discord mods, partnership managers, marketing managers | Mentioned By: witch\nDocumentation: Document the long-term strategy and buyback mechanisms | Description: Clarify how $degenai ties to the DAO | Mentioned By: \ucc0c G \u8dfb \u3058 PrudentSpartan\nDocumentation: Create guide for token launches | Description: Develop documentation outlining minimum requirements for successful token launches | Mentioned By: yikesawjeez\nFeature: Implement token migration from ai16z to ElizaOS | Description: Complete rebranding process to align token name with project name | Mentioned By: mat\nFeature: Expand to multiple blockchains | Description: Consider multichain strategy, particularly with BNB Chain | Mentioned By: DannyNOR NoFapArc\nFeature: Develop compliance agent for social media | Description: Create agent that prevents social media agents from posting problematic content | Mentioned By: shaw\nFeature: Create LAMP stack equivalent for agents | Description: Develop standardized technology stack for agent development | Mentioned By: jin",
          "messageCount": 539,
          "userCount": 52
        },
        {
          "channelId": "1313222089271939102",
          "channelName": "3d-ai-tv",
          "summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe discussion revolves around creating intro/outro sequences and transitions for an AI TV show. Fishai is leading the video editing work, creating an intro that resembles Shark Tank in style. The team is working against a deadline, with jin expressing frustration about delays in the premiere. The main technical challenges include finding appropriate background music, creating stingers/transitions, fixing frame errors, adjusting fade timing, and adding voiceovers. Boom provides music suggestions and shares links to potential graphics elements. The workflow involves creating the intro/outro, recording browser playback of episodes, and combining them in editing software like CapCut. The team iterates on the intro by tightening transitions and adding voiceovers based on feedback.\n\n## 2. FAQ\nQ: Is the video black for others? (asked by jin) A: Multiple users confirmed they could see the video (answered by eskender.eth and boom)\nQ: What kind of background music is needed for the intro? (asked by fishai) A: Something that fits in the realm of Shark Tank, less crunchy than initial suggestions (answered by boom and jin)\nQ: What exactly are we trying to create? (asked by boom) A: Need intro/outro for recording browser playback and editing episodes (answered by jin)\n\n## 3. Help Interactions\nHelper: boom | Helpee: fishai | Context: Needed background music recommendations for TV show intro | Resolution: Shared multiple music options including lofi tracks and dramatic music suggestions\nHelper: fishai | Helpee: jin | Context: Needed intro video with tighter transitions and voiceover | Resolution: Created revised version with tightened transitions and added voiceovers\nHelper: boom | Helpee: jin | Context: Needed graphics elements for the show | Resolution: Shared collection of graphics via elements.envato.com link\n\n## 4. Action Items\nType: Technical | Description: Fix frame errors in intro video | Mentioned By: fishai\nType: Technical | Description: Adjust fade timing in intro (currently too long) | Mentioned By: jin\nType: Technical | Description: Create stingers/transition bumpers for PlayCanvas default loading screens | Mentioned By: fishai\nType: Technical | Description: Record browser playback of episodes and edit with intro/outro | Mentioned By: jin\nType: Technical | Description: Remove ai16z mugs from content | Mentioned By: Odilitime\nType: Feature | Description: Add voiceovers to the intro | Mentioned By: jin",
          "messageCount": 96,
          "userCount": 6
        }
      ]
    }
  },
  "ai_news_elizaos_daily_discord_md_2025-02-15": {
    "filename": "2025-02-15.md",
    "content": "# elizaOS Discord - 2025-02-15\n\n## Overall Discussion Highlights\n\n### Security Incident: Shaw's Twitter Account Hack\n- Shaw's Twitter account was compromised, with the hacker posting phishing links to fake ElizaOS websites (eliza-os.net and elizaos.co)\n- The scam posts promoted a fake token migration, attempting to drain users' wallets\n- Community members quickly mobilized to report the scam posts and domains to registrars\n- Several users reported losing funds, with one claiming to have lost $40,000\n- Team members confirmed the hack and warned users not to trust posts from Shaw's account\n- \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f confirmed taking down malicious units and setting up monitoring\n- The incident highlighted the need for more secure communication channels, with Jin suggesting on-chain communications via memos or mirror.xyz\n\n### ElizaOS Development & Features\n- Shaw is developing a new agent swarm system for v2, allowing agents to perform useful work with role-based privileges\n- The system enables agents to create tasks, execute them with confirmation, and interact with other agents\n- Users discussed memory separation by user ID to maintain privacy in multi-user environments\n- Twitter integration challenges include rate limits, verification requirements, and avoiding shadow bans\n- Multiple users encountered issues with better-sqlite3 installation, which can be resolved by rebuilding the module\n- ElizaOS can run multiple agents simultaneously, though with memory constraints\n- Various LLM providers can be used beyond the default options\n\n### Community Events & Rebranding\n- Plans to change \"What Did You Get Done This Week\" (WDYGDTW) format to a \"Clank Tank\" game show inspired by Shark Tank\n- Jin mentioned integrating a weekly space into this new format, potentially premiering the following Friday\n- Fishai is leading video editing work for the show, creating an intro resembling Shark Tank in style\n- The community discussed the ongoing rebranding from ai16z to ElizaOS\n- Many noted that the ElizaOS brand is gaining recognition while ai16z remains less known\n\n### Tokenomics & Partnerships\n- DorianD suggested capturing fees from trading pools that use the network coin\n- yikesawjeez proposed positioning their token as an \"agent meta index fund\" by creating liquidity pairs with various AI/agent projects\n- A partnership with BNB Chain was highlighted, suggesting potential for multichain expansion beyond Solana\n- The DegenAI Twitter account was reported as banned, with rhota mentioning they've reached out to X (Twitter) to resolve it\n- rhota mentioned implementing basic trade testing plans for their Trading v2 platform\n\n## Key Questions & Answers\n\n**Security Incident**\n- **Q: Is Shaw hacked?**  \n  **A:** Yes, don't trust whatever he posts for now (answered by jin)\n\n- **Q: Did you sign a transaction or connect your wallet?**  \n  **A:** I signed a transaction yes (answered by bert)\n\n- **Q: My other wallets weren't connected to the site only the one that got drained so ill be fine right?**  \n  **A:** Yes king if other wallets weren't connected you should be safe, but please double check and revoke any permissions (answered by BOSSU)\n\n- **Q: How can Shaw not have 2fa for his twitter account?**  \n  **A:** It is [enabled], it might not be the culprit (answered by jin)\n\n- **Q: How else could someone get access to his twitter account?**  \n  **A:** Twitter may disable 2FA during account recovery processes (answered by Patt)\n\n**Technical Questions**\n- **Q: How can I separate memory by user to keep data private between multi-users?**  \n  **A:** Pass userId and roomId parameters with your API request (answered by lefrog)\n\n- **Q: How do I make the agent respond more short and concise?**  \n  **A:** Make your message/post examples all short & concise (answered by Phoenix | Livepeer-Eliza.com)\n\n- **Q: How do I enable DEBUG mode to see what's wrong with my plugin?**  \n  **A:** Use DEFAULT_LOG_LEVEL=debug pnpm dev or try trace level (answered by Odilitime)\n\n- **Q: What makes eliza different from other agent frameworks?**  \n  **A:** Most starred and active open source github repo to build ai agents in crypto; TypeScript language is more accessible than other dev languages; Vibrant community; Most serious project about integrating AI to community management (answered by Ka_yari)\n\n- **Q: How can I report a vulnerability?**  \n  **A:** Dm @shaw, he'll help you with the vulnerability report (answered by BOSSU)\n\n**Project Direction**\n- **Q: Why ai16z should be stayed as DAO? Is it efficient at this moment? What DAO did so far for this project?**  \n  **A:** We're moving away from that name to ElizaOS. It's a DAO because we treat holders as partners. With new tokenomics coming soon, the token will be the backbone of ElizOS eco (answered by HoneyBadger)\n\n- **Q: How do we know if our character is getting selected for the block tank event?**  \n  **A:** We're building a process for sifting through submissions and following up. Personally I want it to feel like an event for being chosen / getting on the show (answered by jin)\n\n- **Q: Is it really possible to keep the CA but change the ticker and name?**  \n  **A:** Yes, CA won't change (answered by jin)\n\n## Community Help & Collaboration\n\n**Security Incident Response**\n- Multiple community members alerted others about Shaw's compromised Twitter account, warning against clicking links or connecting wallets\n- Bealers provided specific instructions to report phishing domains to Tucows registrar via abuse form\n- joellelb recommended using Wallet Guard and Pocket Universe to scan wallets and revoke access after the security incident\n- witch explained to concerned users that without connecting wallets or signing transactions, their funds should be safe\n\n**Technical Troubleshooting**\n- engineer helped Odilitime resolve a local SQL DB issue by switching to MongoDB using adapter-mongodb with connection string in .env\n- elizaos-bridge-odi provided a command to rebuild sqlite3 module for better-sqlite3 errors: `pnpm build && cd node_modules/better-sqlite3 && pnpm rebuild && cd ../.. && pnpm start`\n- Odilitime helped pupathebig with plugin loading failures by providing debugging tips including log level settings\n- lefrog explained to \ud83e\udde7ThanosDaSith24\ud83e\udde7 how to create private chatrooms by passing userID and roomID parameters\n- \ua9c1Ninja_Dev\ua9c2 confirmed to BowTiedBlueFin that each character and agent has separate memory against each user\n- Mr. Stark shared configuration settings with LucaP to avoid Twitter bot rate limits and shadow bans\n\n**Content Creation Collaboration**\n- boom helped fishai with background music recommendations for the TV show intro, sharing multiple music options\n- fishai created a revised intro video for jin with tightened transitions and added voiceovers\n- boom shared a collection of graphics elements via elements.envato.com link for the show\n\n## Action Items\n\n### Technical\n- **Security**\n  - Implement security measures to prevent Twitter account compromises (Mentioned by Multiple users)\n  - Take down malicious links from hacked account (Mentioned by \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f)\n  - Set up monitoring to take down any malicious units shared (Mentioned by \u212d\ud835\udd26\ud835\udd2d\ud835\udd25\ud835\udd22\ud835\udd2f)\n  - Report domains eliza-os.net and elizaos.co to Tucows registrar (Mentioned by Bealers)\n  - Delete fraudulent posts from compromised Shaw account (Mentioned by hyper)\n  - Secure compromised social media accounts (Mentioned by Bealers)\n  - Restore/unban the DegenAI Twitter account (Mentioned by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f)\n  - Implement on-chain communications via token memos with frontend website for verification (Mentioned by jin)\n\n- **Framework Improvements**\n  - Fix better-sqlite3 installation issues by rebuilding the module (Mentioned by elizaos-bridge-odi)\n  - Implement proper memory separation by user ID for multi-user environments (Mentioned by BowTiedBlueFin)\n  - Create REST API documentation for client-direct (Mentioned by lefrog)\n  - Fix Twitter rate limiting and shadow ban issues (Mentioned by LucaP)\n  - Improve plugin loading error messages and debugging (Mentioned by pupathebig)\n  - Add agent identifiers to the eliza logger (Mentioned by uai_thne)\n  - Change client's listening address from localhost to server IP (Mentioned by Roforico)\n\n- **Trading Platform**\n  - Iterate on Trading v2 platform to implement more complex quantitative strategies (Mentioned by rhota)\n  - Implement fee capture from trading pools using the network coin (Mentioned by DorianD)\n  - Create liquidity pairs between AI16 and agent projects in treasury (zerebro, arc, etc.) (Mentioned by yikesawjeez)\n\n- **Content Creation**\n  - Fix frame errors in intro video (Mentioned by fishai)\n  - Adjust fade timing in intro (currently too long) (Mentioned by jin)\n  - Create stingers/transition bumpers for PlayCanvas default loading screens (Mentioned by fishai)\n  - Record browser playback of episodes and edit with intro/outro (Mentioned by jin)\n  - Remove ai16z mugs from content (Mentioned by Odilitime)\n\n### Documentation\n- Add Discord link to the website for easier discovery (Mentioned by Milan)\n- Document how to run multiple agents simultaneously (Mentioned by ivorad)\n- Create documentation for the REST API (Mentioned by jin)\n- Document how to enable DEBUG mode for troubleshooting (Mentioned by pupathebig)\n- Create security advisory about ongoing phishing attempts (Mentioned by Bealers)\n- Document the long-term strategy and buyback mechanisms (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create guide for token launches with minimum requirements (Mentioned by yikesawjeez)\n\n### Features\n- Change \"What Did You Get Done This Week\" format to \"Clank Tank\" game show (Mentioned by jin)\n- Create a process for selecting submissions for the Block Tank event (Mentioned by jin)\n- Implement voice AI feature for analysis of voice recordings (Mentioned by winded4752)\n- Suggest X implement new security features to prevent crypto scams (Mentioned by MJ)\n- Suggest Pump Fun implement KYC and limit token creation to prevent scams (Mentioned by MJ)\n- Implement immediate response while processing longer requests (Mentioned by Shinkowski II)\n- Create a way to filter certain words from agent output (Mentioned by Mr. Stark)\n- Position token as an \"agent meta index fund\" with liquidity pairs for all relevant AI projects (Mentioned by yikesawjeez)\n- Add voiceovers to the intro (Mentioned by jin)\n- Implement token migration from ai16z to ElizaOS (Mentioned by mat)\n- Expand to multiple blockchains, particularly with BNB Chain (Mentioned by DannyNOR NoFapArc)\n- Develop compliance agent for social media (Mentioned by shaw)\n- Create LAMP stack equivalent for agents (Mentioned by jin)\n- Develop agent swarm system with role-based privileges (Mentioned by shaw)\n- Implement social awareness for agents (Mentioned by shaw)\n- Create a template for swarm of agents for crypto projects (Mentioned by witch)"
  },
  "github_summaries_daily_2025-02-16": {
    "filename": "2025-02-16.md",
    "content": "On Feb 16, 2025, the ElizaOS project saw significant progress with new features like a default ElevenLabs voice and improved filesystem cache configuration, alongside critical bug fixes addressing Telegram and Discord test failures and a security vulnerability. Documentation was also enhanced with a Ukrainian README translation, while new issues emerged regarding Discord plugin transcription errors and SDK import problems.\n\n## \ud83d\udea8 Needs Attention\n- **Blocked Issues/PRs**:\n    - [elizaos/eliza#3527](https://github.com/elizaos/eliza/issues/3527): A wrong import in the advanced SDK TypeScript package is causing difficulties in adding `@elizaos/agent` to new projects and requires investigation.\n    - [elizaos/eliza#3515](https://github.com/elizaos/eliza/issues/3515): A text transcription error for the Discord plugin after installing ffmpeg needs to be addressed.\n\n## \u2705 Completed Work\n- **Core Framework Enhancements**:\n    - Integrated a default voice for ElevenLabs, expanding audio capabilities: [elizaos/eliza#3519](https://github.com/elizaos/eliza/pull/3519).\n    - Enabled defining a cache directory in the `.env` file for improved filesystem cache management: [elizaos/eliza#3291](https://github.com/elizaos/eliza/pull/3291).\n- **Stability and Security Improvements**:\n    - Resolved issues with Telegram Vitest, enhancing testing reliability: [elizaos/eliza#3524](https://github.com/elizaos/eliza/pull/3524).\n    - Fixed problems with Discord tests, ensuring plugin stability: [elizaos/eliza#3518](https://github.com/elizaos/eliza/pull/3518).\n    - Refactored `http://localhost` to use `SERVER_URL` environment variable for better configuration management: [elizaos/eliza#3511](https://github.com/elizaos/eliza/pull/3511).\n    - Addressed CVE-2024-48930 by updating package dependencies, improving security: [elizaos/eliza#2958](https://github.com/elizaos/eliza/pull/2958).\n- **Documentation and Infrastructure Updates**:\n    - Added a Ukrainian translation of the README, improving accessibility: [elizaos/eliza#3483](https://github.com/elizaos/eliza/pull/3483).\n    - Performed a version bump and lockfile updates: [elizaos/eliza#3523](https://github.com/elizaos/eliza/pull/3523).\n    - Moved character data to a submodule and updated workflows for better organization: [elizaos/eliza#3509](https://github.com/elizaos/eliza/pull/3509).\n\n## \ud83d\udc1e Issue Triage\n- **New Issues**:\n    - elizaos/eliza:\n        - [#3515](https://github.com/elizaos/eliza/issues/3515): Reported a text transcription error for the Discord plugin after installing ffmpeg.\n        - [#3527](https://github.com/elizaos/eliza/issues/3527): Highlights a wrong import in the advanced SDK TypeScript package, causing difficulties in adding `@elizaos/agent` to new projects.\n- **Closed Issues**:\n    - elizaos/eliza:\n        - [#3316](https://github.com/elizaos/eliza/issues/3316): Resolved build failures with pnpm.\n        - [#3515](https://github.com/elizaos/eliza/issues/3515): Resolved issues related to text transcription errors in the Discord plugin."
  },
  "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-16": "[\"0xcodercrane_week_2025-02-16\", \"0xcodercrane\", \"week\", \"2025-02-16\", \"0xcodercrane: Created two issues this week (#3596 regarding a key error in the AppSidebar's Skeleton Item and #3571 about errors during node module installation), both of which have been closed. No code contributions or PR activity during this period.\", \"2025-05-13T22:05:45.546Z\"]\n[\"0xalberto_week_2025-02-16\", \"0xalberto\", \"week\", \"2025-02-16\", \"0xalberto: Created issue #3592 regarding \\\"pnpm start:client is not fetching localhost:3000\\\" which was subsequently closed. Contributed to discussions by commenting on 7 different issues. No code changes or pull requests during this period.\", \"2025-05-13T22:05:45.638Z\"]\n[\"0xCryptoZen_week_2025-02-16\", \"0xCryptoZen\", \"week\", \"2025-02-16\", \"0xCryptoZen: Created issue #3569 regarding server connection problems when setting SERVER_PORT=3000 in the .env file, which has since been closed. Added one comment on an issue during the period, showing sporadic activity.\", \"2025-05-13T22:05:45.840Z\"]\n[\"AIFlowML_week_2025-02-16\", \"AIFlowML\", \"week\", \"2025-02-16\", \"AIFlowML: Completed a significant refactoring effort with PR #3526 \\\"Refactor - Plugin Local AI\\\" (+3777/-451 lines) that modified 30 files across the codebase. The work primarily focused on test improvements (41% of changes) with substantial code modifications (53%), demonstrating occasional activity pattern with contributions on 2 days this week.\", \"2025-05-13T22:05:46.457Z\"]\n[\"0xbbjoker_week_2025-02-16\", \"0xbbjoker\", \"week\", \"2025-02-16\", \"0xbbjoker: Merged two significant PRs this week: #3598 adding PGLite support with database design changes (+12,189/-13,810 lines) and #3549 fixing a race condition (+367/-124 lines). Also has an open PR (#3597) related to Drizzle v2 PGLite integration, with their contributions showing substantial code changes across database functionality.\", \"2025-05-13T22:05:46.497Z\"]\n[\"ECWireless_week_2025-02-16\", \"ECWireless\", \"week\", \"2025-02-16\", \"ECWireless: Made substantial code changes across 76 files (+10,872/-780 lines) through 9 commits, with activity concentrated on 2 days of the week. Work primarily focused on feature development (67%) with some bugfix work (11%) and other contributions (22%).\", \"2025-05-13T22:05:48.151Z\"]\n[\"GabrielCartier_week_2025-02-16\", \"GabrielCartier\", \"week\", \"2025-02-16\", \"GabrielCartier: Contributed to documentation by merging PR #3539 which added SQLite3 errors to the Quickstart guide (+13,119/-368,688 lines). This documentation improvement was their only activity this week, showing a focused effort on enhancing error documentation.\", \"2025-05-13T22:05:50.030Z\"]\n[\"Deeptanshu-sankhwar_week_2025-02-16\", \"Deeptanshu-sankhwar\", \"week\", \"2025-02-16\", \"Deeptanshu-sankhwar: Merged a single PR (#3642) that removed the langchain dependency for text splitting, making a moderate code change (+538/-328 lines). Contributed to one issue discussion but otherwise showed limited activity during this period.\", \"2025-05-13T22:05:47.991Z\"]\n[\"KristofferGW_week_2025-02-16\", \"KristofferGW\", \"week\", \"2025-02-16\", \"KristofferGW: Created issue #3556 regarding a build failure error (exit code 137), which has since been closed. No other activity this week.\", \"2025-05-13T22:05:49.104Z\"]\n[\"L-jasmine_week_2025-02-16\", \"L-jasmine\", \"week\", \"2025-02-16\", \"L-jasmine: Added Gaianet API key support through PR #3591 (+4/-1 lines), which was merged after 16 hours. Also opened a related PR #3590 that remains open, with both PRs focused on the same feature enhancement.\", \"2025-05-13T22:05:50.413Z\"]\n[\"NeoByteXx_week_2025-02-16\", \"NeoByteXx\", \"week\", \"2025-02-16\", \"NeoByteXx: Made a single contribution this week by merging PR #3616 which fixed the devcontainer.json port mapping syntax and JSON structure, modifying 3 lines of configuration code (+3/-3).\", \"2025-05-13T22:05:50.790Z\"]\n[\"Schzzt_week_2025-02-16\", \"Schzzt\", \"week\", \"2025-02-16\", \"Schzzt: Opened one pull request (#3623) to add a new embedding provider for Ali Bailian, making substantial code changes with +1,871/-10 lines across 23 files. This significant contribution was focused on a single day of activity during the week.\", \"2025-05-13T22:05:51.371Z\"]\n[\"WNUMIK_week_2025-02-16\", \"WNUMIK\", \"week\", \"2025-02-16\", \"WNUMIK: Created issue #3546 \\\"RAG Search Error\\\" which was subsequently closed. No other activity was observed during this period.\", \"2025-05-13T22:05:51.782Z\"]\n[\"HashWarlock_week_2025-02-16\", \"HashWarlock\", \"week\", \"2025-02-16\", \"HashWarlock: Made code changes across 16 files (+147/-85 lines) in 3 commits, with activity on 2 days this week. The work was primarily focused on feature development (67%) with some other work (33%), though no PRs were merged or opened.\", \"2025-05-13T22:05:48.644Z\"]\n[\"ad0ll_week_2025-02-16\", \"ad0ll\", \"week\", \"2025-02-16\", \"ad0ll: Opened PR #3558 \\\"Demo news\\\" with changes to 4 files (+293/-64 lines), primarily modifying configuration files (75%) and code (25%). Activity was limited to a single day this week.\", \"2025-05-13T22:05:57.371Z\"]\n[\"alphahughes1_week_2025-02-16\", \"alphahughes1\", \"week\", \"2025-02-16\", \"alphahughes1: Opened one pull request (#3557) titled \\\"Create webpack.yml\\\" with a single commit that added a new configuration file (+28 lines). Activity was limited to a single day this week with a focus on configuration work.\", \"2025-05-13T22:05:52.725Z\"]\n[\"Luks3110_week_2025-02-16\", \"Luks3110\", \"week\", \"2025-02-16\", \"Luks3110: Identified and addressed a type definition issue by first creating issue #3639 regarding the undefined \\\"Adapter\\\" type alias, then resolving it through PR #3640 which added database adapter and plugin adapter types to core types (+4/-1 lines).\", \"2025-05-13T22:05:50.446Z\"]\n[\"amirmabhout_week_2025-02-16\", \"amirmabhout\", \"week\", \"2025-02-16\", \"amirmabhout: Reported one issue (#3562) regarding misleading and diverging instructions in the client-twitter component, which has since been closed. No other activity was observed during this period.\", \"2025-05-13T22:05:53.137Z\"]\n[\"amirkhonov_week_2025-02-16\", \"amirkhonov\", \"week\", \"2025-02-16\", \"amirkhonov: Contributed a single merged PR (#3545) that trimmed the `<think>` block from Ollama responses, making a small but targeted change (+1/-1 lines). This focused contribution was their only activity during the week.\", \"2025-05-13T22:05:53.193Z\"]\n[\"andriyk-hacken_week_2025-02-16\", \"andriyk-hacken\", \"week\", \"2025-02-16\", \"andriyk-hacken: Has two open PRs this week: #3544 \\\"feat: add Extractor Agent Firewall plugin\\\" and #3534 \\\"plugin-extractor\\\", but no merged contributions. No other activity was recorded during this period.\", \"2025-05-13T22:05:53.620Z\"]\n[\"andyvalerio_week_2025-02-16\", \"andyvalerio\", \"week\", \"2025-02-16\", \"andyvalerio: Reported issue #3527 regarding incorrect imports in the advanced-sdk-ts package, which has since been closed. Commented on one issue but had no other activity this period.\", \"2025-05-13T22:05:54.463Z\"]\n[\"baizele_week_2025-02-16\", \"baizele\", \"week\", \"2025-02-16\", \"baizele: Made a single commit this week, adding 1 line of code across 1 file with sporadic activity.\", \"2025-05-13T22:05:55.017Z\"]\n[\"ben-dh3_week_2025-02-16\", \"ben-dh3\", \"week\", \"2025-02-16\", \"ben-dh3: Opened PR #3554 \\\"feat: new plugin zapper\\\" with substantial code changes (+68470/-318 lines) across 6 files. Active on only one day this week, with the majority of changes focused on adding new functionality.\", \"2025-05-13T22:05:55.373Z\"]\n[\"brunolorente_week_2025-02-16\", \"brunolorente\", \"week\", \"2025-02-16\", \"brunolorente: Created issue #3629 reporting an error in the parsing.ts file, which has since been closed. No other activity this week.\", \"2025-05-13T22:05:55.919Z\"]\n[\"clydemeng_week_2025-02-16\", \"clydemeng\", \"week\", \"2025-02-16\", \"clydemeng: Opened one pull request (#3621) to add support for Greenfield chain in the BNB plugin, which remains under review.\", \"2025-05-13T22:05:56.891Z\"]\n[\"bguiz_week_2025-02-16\", \"bguiz\", \"week\", \"2025-02-16\", \"bguiz: Merged a significant PR (#3589) that allows the Eliza client to configure the Eliza server base URL, involving substantial code changes (+15,697/-370,144 lines). Created two feature-related issues (#3585 and #3567) focused on configuration improvements, both of which were subsequently closed. Contributed small but focused code modifications across three different file types (code, docs, and config) with a total of +18/-1 lines.\", \"2025-05-13T22:05:57.402Z\"]\n[\"Cooops_week_2025-02-16\", \"Cooops\", \"week\", \"2025-02-16\", \"Cooops: Opened one pull request (#3619) titled \\\"Reverting to small models on should logic\\\" which remains open and has not yet been merged. No other GitHub activity was recorded during this period.\", \"2025-05-13T22:05:47.492Z\"]\n[\"faeeq_week_2025-02-16\", \"faeeq\", \"week\", \"2025-02-16\", \"faeeq: Created issue #3563 regarding a vulnerability related to defaiza, which has since been closed. No other activity this week.\", \"2025-05-13T22:06:04.058Z\"]\n[\"eeemmmmmm_week_2025-02-16\", \"eeemmmmmm\", \"week\", \"2025-02-16\", \"eeemmmmmm: Opened one pull request (#3528) to fix prompts.ts, making minor code changes (+2/-2 lines) in a single file. Active on only one day this week with a single commit.\", \"2025-05-13T22:05:59.988Z\"]\n[\"ebaizel_week_2025-02-16\", \"ebaizel\", \"week\", \"2025-02-16\", \"ebaizel: Fixed Bedrock inference issues with PR #3553 merged this week, while PR #3552 \\\"3328 fix bedrock\\\" remains open. Made substantial code changes across 2,537 files (+13,087/-368,687 lines) in a single commit, focusing entirely on bugfix work.\", \"2025-05-13T22:05:59.393Z\"]\n[\"firemountain_week_2025-02-16\", \"firemountain\", \"week\", \"2025-02-16\", \"firemountain: Opened PR #3607 to update image.yaml, making configuration changes across 2 files (+37/-42 lines). Activity was limited to a single day this week with a focus on configuration updates.\", \"2025-05-13T22:06:02.050Z\"]\n[\"github-advanced-security_week_2025-02-16\", \"github-advanced-security\", \"week\", \"2025-02-16\", \"github-advanced-security: Provided 3 review comments on pull requests this week with no other activity observed.\", \"2025-05-13T22:06:01.552Z\"]\n[\"ferraignez_week_2025-02-16\", \"ferraignez\", \"week\", \"2025-02-16\", \"ferraignez: Opened 5 PRs this week (#3594, #3593, #3575, #3574, #3531) focused on character-related features and test configurations, with moderate code changes (+245/-2 lines) across 4 files. Activity was concentrated on 2 days, primarily modifying configuration files (80%) and test files (20%).\", \"2025-05-13T22:06:01.219Z\"]\n[\"cpereiramt_week_2025-02-16\", \"cpereiramt\", \"week\", \"2025-02-16\", \"cpereiramt: Opened a new issue (#3547) for a Notion.so plugin which was subsequently closed, and created an open PR (#3548) to implement this feature with initial configuration work. Made significant code changes across 10 files (+360/-1 lines) with equal focus on feature development and bug fixing, primarily modifying code and configuration files.\", \"2025-05-13T22:05:59.079Z\"]\n[\"henrikaxelsen_week_2025-02-16\", \"henrikaxelsen\", \"week\", \"2025-02-16\", \"henrikaxelsen: Created and closed issue #3578 regarding connection problems between front end and back end, and added one comment to an issue. No code contributions or pull requests during this period.\", \"2025-05-13T22:06:02.242Z\"]\n[\"iKapitonau_week_2025-02-16\", \"iKapitonau\", \"week\", \"2025-02-16\", \"iKapitonau: Merged a significant PR #3615 adding support for Secret AI LLM, which involved extensive code changes across 2,880 files (+26,662/-385,933 lines). Active on 2 days this week, focusing primarily on feature development with this substantial code modification.\", \"2025-05-13T22:06:03.744Z\"]\n[\"ice-coldbell_week_2025-02-16\", \"ice-coldbell\", \"week\", \"2025-02-16\", \"ice-coldbell: Opened PR #3565 \\\"Added feature: Plugin Merkle\\\" with substantial code changes (+1374/-6 lines across 22 files), working primarily on a new feature. Also created and closed issue #3564 \\\"Add plugin-merkle\\\" related to this development effort, with activity concentrated on a single day this week.\", \"2025-05-13T22:06:04.160Z\"]\n[\"daniel-trevino_week_2025-02-16\", \"daniel-trevino\", \"week\", \"2025-02-16\", \"daniel-trevino: Merged two bug fix PRs this week: #3618 addressing agent setting from API (+5/-7 lines) and #3609 fixing package installation from new registry with substantial changes (+216/-192 lines). Has an open feature PR (#3566) to replace UUID with native Node crypto functionality, and was active on 2 days with most changes focused on configuration files (54%) and code (31%).\", \"2025-05-13T22:05:58.832Z\"]\n[\"iheron_week_2025-02-16\", \"iheron\", \"week\", \"2025-02-16\", \"iheron: Made a small feature contribution by merging PR #3570 which modified the configuration for the plugin-nkn (+4/-0 lines). This was their only activity for the week, consisting of a single commit that modified 2 files.\", \"2025-05-13T22:06:04.320Z\"]\n[\"khiemsoft_week_2025-02-16\", \"khiemsoft\", \"week\", \"2025-02-16\", \"khiemsoft: Opened PR #3586 to add a Viction plugin, modifying 4 files with 24 additions and 13 deletions across 2 commits. Activity was limited to a single day this week, with work split evenly between feature development and bug fixes.\", \"2025-05-13T22:06:06.531Z\"]\n[\"kent-neo_week_2025-02-16\", \"kent-neo\", \"week\", \"2025-02-16\", \"kent-neo: Reported two issues related to Twitter functionality: #3588 regarding controlling reply length and single tweet format, and #3587 about automatic replies to Twitter thread tweets, both of which have been closed.\", \"2025-05-13T22:06:06.388Z\"]\n[\"julienbrs_week_2025-02-16\", \"julienbrs\", \"week\", \"2025-02-16\", \"julienbrs: Opened PR #3641 to add Paradex DEX integration (+3515/-1256 lines across 58 files), which implements the feature requested in issue #3627 that they created and later closed. Their work involved significant refactoring (50%) and feature development (30%), with contributions spread across code (73%) and configuration files (19%) on two separate days.\", \"2025-05-13T22:06:06.558Z\"]\n[\"kilavvy_week_2025-02-16\", \"kilavvy\", \"week\", \"2025-02-16\", \"kilavvy: Opened PR #3630 to fix typos in documentation files, making small changes across 4 files (+5/-5 lines). Activity was limited to a single day this week, with equal focus on code and documentation files.\", \"2025-05-13T22:06:06.926Z\"]\n[\"lggg123_week_2025-02-16\", \"lggg123\", \"week\", \"2025-02-16\", \"lggg123: Opened one pull request (#3536 \\\"Feat/sui agent hackathong\\\") that remains under review. No other GitHub activity was recorded during this period.\", \"2025-05-13T22:06:08.410Z\"]\n[\"lokendrasurya_week_2025-02-16\", \"lokendrasurya\", \"week\", \"2025-02-16\", \"lokendrasurya: Created issue #3626 \\\"WebService usage help\\\" which has since been closed. No other activity this week.\", \"2025-05-13T22:06:08.548Z\"]\n[\"lefrog-dont-code_week_2025-02-16\", \"lefrog-dont-code\", \"week\", \"2025-02-16\", \"lefrog-dont-code: Merged PR #3583 \\\"Optional Venice system prompt removal\\\" with significant code changes (+67768/-394183 lines), while also opening PR #3580 for adding a 'pnpm reload' script. Active on 2 days this week, primarily focusing on feature work (67%) with modifications to 5 files across code and configuration files.\", \"2025-05-13T22:06:09.060Z\"]\n[\"lalalune_week_2025-02-16\", \"lalalune\", \"week\", \"2025-02-16\", \"lalalune: Completed two major refactoring efforts with merged PRs #3637 (renaming user table to entity and adding agent table) and #3602 (refactoring room state), involving substantial code changes (+23.5k/-18.7k lines). Maintained consistent activity across 5 days while providing 6 code reviews (4 approvals, 2 comments) and making 5 PR comments. Modified an impressive 5,688 files with significant net code reduction (+116k/-656k lines) across 28 commits, primarily focusing on refactoring work.\", \"2025-05-13T22:06:08.532Z\"]\n[\"mioku50_week_2025-02-16\", \"mioku50\", \"week\", \"2025-02-16\", \"mioku50: Created issue #3576 \\\"No work upload files 0G plugin\\\" which was subsequently closed.\", \"2025-05-13T22:06:10.746Z\"]\n[\"jgabriele321_week_2025-02-16\", \"jgabriele321\", \"week\", \"2025-02-16\", \"jgabriele321: Opened 3 PRs (#3638, #3635, #3634) focused on adding Toby voice functionality to various features. Made substantial code changes across 2196 files (+239,858/-14,346 lines) with a heavy emphasis on configuration files (50%) and tests (30%). Active on 2 days this week, primarily working on feature development and bug fixes.\", \"2025-05-13T22:06:04.842Z\"]\n[\"mdqst_week_2025-02-16\", \"mdqst\", \"week\", \"2025-02-16\", \"mdqst: Fixed documentation in CONTRIBUTING.md with PR #3532 (+21/-58 lines), correcting branch naming examples. This single contribution focused on improving project documentation through a moderate-sized change that was merged after 32 hours.\", \"2025-05-13T22:06:10.653Z\"]\n[\"mtbc_week_2025-02-16\", \"mtbc\", \"week\", \"2025-02-16\", \"mtbc: Made a single commit modifying one file with 10 additions and 2 deletions, with activity on only one day this week.\", \"2025-05-13T22:06:10.603Z\"]\n[\"madjin_week_2025-02-16\", \"madjin\", \"week\", \"2025-02-16\", \"madjin: Led a major documentation overhaul with three significant merged PRs (#3620, #3605, #3584) totaling over +17k/-19k lines, including a new Showcase page for plugins and extensive docs cleanup. Consistently active every day of the week with 20 commits across 536 modified files, primarily focused on documentation improvements (79% of changes) with some code work (13%). Created and closed two issues (#3083, #3604) related to documentation and troubleshooting improvements.\", \"2025-05-13T22:06:09.963Z\"]\n[\"mxchinegod_week_2025-02-16\", \"mxchinegod\", \"week\", \"2025-02-16\", \"mxchinegod: Opened one work-in-progress PR (#3517) focused on YouTube transcription and MongoDB embedding functionality, modifying 15 files with 346 additions and 62 deletions across configuration (50%) and code (43%) files. Activity was limited to a single day this week, with the PR remaining open and work characterized as bugfix-related.\", \"2025-05-13T22:06:11.796Z\"]\n[\"nimrod-teich_week_2025-02-16\", \"nimrod-teich\", \"week\", \"2025-02-16\", \"nimrod-teich: Made a single comment on a PR with minimal code changes (+2/-2 lines) across one file. Activity was limited to a single day this week.\", \"2025-05-13T22:06:12.811Z\"]\n[\"nusk0_week_2025-02-16\", \"nusk0\", \"week\", \"2025-02-16\", \"nusk0: Made significant code contributions with 3 commits modifying 26 files (+2329/-65 lines), working across various file types with an even distribution of bugfix, test, and other work. Active on 3 days this week with a moderately consistent work pattern.\", \"2025-05-13T22:06:12.720Z\"]\n[\"ppsimatikas_week_2025-02-16\", \"ppsimatikas\", \"week\", \"2025-02-16\", \"ppsimatikas: Opened one PR (#3572) for a new \\\"Xtreamly plugin for eliza\\\" feature, with significant code changes totaling +13,220/-368,759 lines across 2,549 files. Activity was limited to a single day this week, with the work evenly split between feature development (50%) and bug fixes (50%), primarily affecting code files (44%), configuration (25%), and tests (19%).\", \"2025-05-13T22:06:14.040Z\"]\n[\"odilitime_week_2025-02-16\", \"odilitime\", \"week\", \"2025-02-16\", \"odilitime: Led a significant release effort with 5 merged PRs including the 0.25.8 release (#3522, #3523, #3632, #3633) and a notable bugfix for case insensitive filename mismatches (#3561, +1099/-682 lines). Maintained a very active review presence with 28 reviews (22 approvals) and 32 PR comments across the week. Contributed substantial code changes across 8040 files (+69k/-1148k lines), working consistently across 6 days with focus split between release management and bug fixing.\", \"2025-05-13T22:06:14.422Z\"]\n[\"qiaqiatic_week_2025-02-16\", \"qiaqiatic\", \"week\", \"2025-02-16\", \"qiaqiatic: Opened PR #3537 to update the prompt for drama creation, modifying 3 files with significant additions (+488/-94 lines). The changes primarily focused on configuration files (67%) with some code modifications (33%), with activity limited to a single day this week.\", \"2025-05-13T22:06:19.266Z\"]\n[\"royalnine_week_2025-02-16\", \"royalnine\", \"week\", \"2025-02-16\", \"royalnine: Fixed a bug related to importing plugins from registry with PR #3611 (+1/-0 lines), which was merged after 7 hours. Also created issue #3610 \\\"Fix plugin import from plugin registry\\\" which was subsequently closed, and contributed one comment on an issue.\", \"2025-05-13T22:06:20.173Z\"]\n[\"shakkernerd_week_2025-02-16\", \"shakkernerd\", \"week\", \"2025-02-16\", \"shakkernerd: Provided 3 approvals on code reviews this week. Made a small code change with 1 commit modifying a single file (+2/-2 lines). Activity was limited to a single day during this period.\", \"2025-05-13T22:06:15.103Z\"]\n[\"sharif331_week_2025-02-16\", \"sharif331\", \"week\", \"2025-02-16\", \"sharif331: Created issue #3614 regarding a visual representation, which was subsequently closed. No other activity this week.\", \"2025-05-13T22:06:16.016Z\"]\n[\"sukrucildirr_week_2025-02-16\", \"sukrucildirr\", \"week\", \"2025-02-16\", \"sukrucildirr: Fixed broken links in documentation with one merged PR (#3599) that modified 27 files with balanced changes (+28/-28 lines). The contribution was focused entirely on documentation improvements, completed in a single day this week.\", \"2025-05-13T22:06:17.703Z\"]\n[\"thanghd98_week_2025-02-16\", \"thanghd98\", \"week\", \"2025-02-16\", \"thanghd98: Made a single commit this week with modest code changes (+12/-10 lines) focused on bug fixes. Activity was limited to just one day during this period.\", \"2025-05-13T22:06:19.559Z\"]\n[\"tercel_week_2025-02-16\", \"tercel\", \"week\", \"2025-02-16\", \"tercel: Opened PR #3568 \\\"Main tercel\\\" with moderate code changes (+162/-10 lines) across 10 files, with an even split between code and documentation work. Participated in discussions with 2 PR comments and 1 issue comment, showing sporadic activity concentrated on a single day this week.\", \"2025-05-13T22:06:19.509Z\"]\n[\"think-in-universe_week_2025-02-16\", \"think-in-universe\", \"week\", \"2025-02-16\", \"think-in-universe: Made 2 commits modifying 4 files (+46/-1 lines) with a focus on bug fixes. Activity was limited to a single day this week.\", \"2025-05-13T22:06:22.024Z\"]\n[\"tcm390_week_2025-02-16\", \"tcm390\", \"week\", \"2025-02-16\", \"tcm390: Extremely active this week with 17 merged PRs, primarily focused on fixing and improving test suites across multiple platforms including Twitter, Discord, and Telegram, adding over 11.6k lines while removing 3.9k. Notable contributions include implementing E2E tests for Discord and Twitter in PR #3579 (+1538/-493), fixing Twitter vitest in PR #3543 (+4037/-933), and making significant improvements to the test plugin in PR #3612, while maintaining consistent daily activity throughout the week.\", \"2025-05-13T22:06:19.493Z\"]\n[\"thopatevijay_week_2025-02-16\", \"thopatevijay\", \"week\", \"2025-02-16\", \"thopatevijay: Reported one issue (#3628) about an agent not responding based on provided knowledge, which has since been closed. Engaged in discussions on two issues through comments. No code contributions or pull request activity during this period.\", \"2025-05-13T22:06:21.692Z\"]\n[\"w1ld3r_week_2025-02-16\", \"w1ld3r\", \"week\", \"2025-02-16\", \"w1ld3r: Opened two PRs (#3530 and #3529) related to adding embedding zero vector functionality, with a small code change (+2/-0 lines). Participated in discussions by commenting on one PR and one issue, showing sporadic activity with contributions on only one day this period.\", \"2025-05-13T22:06:22.114Z\"]\n[\"wolfskyknight_week_2025-02-16\", \"wolfskyknight\", \"week\", \"2025-02-16\", \"wolfskyknight: Reported issue #3515 regarding a text transcription error in the Discord plugin, which has since been closed. Engaged in discussions on 4 different issues, providing feedback and comments. No code contributions or pull requests during this period.\", \"2025-05-13T22:06:22.148Z\"]\n[\"sogolmalek_week_2025-02-16\", \"sogolmalek\", \"week\", \"2025-02-16\", \"sogolmalek: Made a single commit this week with minimal code changes (+1/-0 lines). Activity was limited to one day during this period.\", \"2025-05-13T22:06:16.392Z\"]\n[\"wtfsayo_week_2025-02-16\", \"wtfsayo\", \"week\", \"2025-02-16\", \"wtfsayo: Led a major refactoring effort with 6 merged PRs, most notably #3613 \\\"Agent/Character cli methods + refactor server\\\" (+7102/-8995) and #3573 \\\"feat: db-driven-character management\\\" (+5534/-1263), contributing a substantial +30925/-17163 lines across 616 files. Maintained very consistent activity across 6 days, primarily focusing on code changes (69%) with some documentation updates (12%), while also providing 1 approval review and 6 PR comments.\", \"2025-05-13T22:06:24.513Z\"]\n[\"yungalgo_week_2025-02-16\", \"yungalgo\", \"week\", \"2025-02-16\", \"yungalgo: Merged two significant PRs this week, including a substantial refactoring of memory queries, knowledge metadata, and browser support (#3606, +1378/-579 lines) and cleanup of bun build warnings (#3603, +56/-46 lines). Contributed a total of +3824/-3487 lines across 47 files, with activity spread across 3 days and a continued focus on the open PR #3516 for consolidating RAG knowledge.\", \"2025-05-13T22:06:24.714Z\"]",
  "_metadata": {
    "generated_at": "2026-01-01T02:18:04.893269Z",
    "target_date": "2025-02-16",
    "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-15",
      "ai_news_elizaos_discord_md_2025-02-14",
      "ai_news_elizaos_discord_md_2025-02-13",
      "ai_news_elizaos_daily_json_2025-02-15",
      "ai_news_elizaos_daily_md_2025-02-15",
      "ai_news_elizaos_daily_discord_json_2025-02-15",
      "ai_news_elizaos_daily_discord_md_2025-02-15",
      "github_summaries_daily_2025-02-16",
      "github_summaries_week_latest_2025-12-21.md",
      "github_summaries_month_latest_2025-12-01.md"
    ],
    "failed_keys": [],
    "total_characters": 210102,
    "estimated_tokens": 52525,
    "file_size_bytes": 226491
  }
}