{
"date_generated_for": "2025-01-24",
"ai_news_elizaos_discord_md_2025-01-23": {
"filename": "2025-01-23.md",
"content": "# elizaOS Discord - 2025-01-23\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **ElizaOS v2 Progress**: Jin advised users to \"stick to v1\" for now as v2 will be backwards compatible. The dev team is refactoring the plugin system and improving memory management for AI agents.\n- **Installation Improvements**: The dev branch has reduced Eliza installation to a 2-second process.\n- **Model Integration**: Discussions about integrating Deepseek models with ElizaOS, which Jin noted could be done with a single line of code change through OpenRouter.\n- **RAG Implementation**: Several users discussed implementing Retrieval Augmented Generation for Eliza, with kAI wilder explaining the knowledgeManager system.\n\n### Technical Issues & Solutions\n- **Vector Dimension Mismatch**: Multiple users encountered \"Vector dimension mismatch\" errors. The solution is to set USE_OPENAI_EMBEDDING=TRUE in the .env file.\n- **Plugin Configuration**: Users struggled with plugin integration, particularly the dexscreener plugin. The solution involved removing API key checks in index.ts files.\n- **Twitter Integration**: Several discussions about configuring Twitter agents, including how to disable retweets and make agents respond to replies.\n- **Node.js Version**: Users reported success with Node v23.3.0 for resolving various errors.\n\n### DegenSpartanAI & Trading\n- **Trading Status**: DegenSpartanAI temporarily stopped trading because it ran out of SOL.\n- **Performance Tracking**: Community members recommended Birdeye and Waveform platforms for tracking DegenSpartanAI's trading performance.\n- **Development Roadmap**: Rhota mentioned they're working on improving trading functionality and developing a roadmap to be shared by the end of the following week.\n\n### Tokenomics Discussions\n- **Competing Approaches**: Debate between simple models versus complex mechanisms:\n - One approach follows pump.fun/virtuals model with dual pool structure and bonding curve\n - Vasily Sumanov proposed staking/delegation to whitelist trusted agents with slashing mechanisms\n - DorianD advocated for simplicity to avoid barriers to adoption\n - Akin suggested positioning ai16z as a premium service token\n- **Block Tank Concept**: An AI-led venture capital concept combining game show elements with investment decisions, designed to scale and decentralize project vetting.\n\n### 3D AI TV Show Development\n- **Camera System**: Boom worked on camera variations including jib cam, pan and zoom pivot cam, and B-roll options with percentage-based switching logic.\n- **Block Tank Configuration**: SM Sith Lord provided a pre-generated Block Tank episode setup with 6 actors and 4 locations for testing without making AI calls.\n- **Visual Elements**: Discussions about scene design elements, including removing the floor to showcase the Earth backdrop and adding boosters, panels, wires, and LED desks.\n\n## Key Questions & Answers\n\n**Q: How do I fix \"Vector dimension mismatch\" error?** \nA: Set USE_OPENAI_EMBEDDING=TRUE in .env file (answered by boja)\n\n**Q: How do I fix the dexscreener plugin not working?** \nA: Remove the API key check in index.ts and directly add dexScreenerPlugin (answered by bifkn)\n\n**Q: How do I make my agent respond to replies on Twitter?** \nA: Check ACTION_INTERVAL, ENABLE_ACTION_PROCESSING, MAX_ACTIONS_PROCESSING, ACTION_TIMELINE_TYPE settings (answered by tcm390)\n\n**Q: How do I disable Twitter retweets?** \nA: Remove retweet from the actions portion in the code (answered by paxva)\n\n**Q: Is there a way for the agent to memorize tweets without actually responding to them?** \nA: Agents can observe without interacting, just follow the profile (answered by BOSSU)\n\n**Q: How far away is ElizaOS v2?** \nA: Jin advised to \"stick to v1\" as it will be \"backwards compatible\" (answered by jin)\n\n**Q: Is Deepseek integrated yet with ElizaOS as an option?** \nA: \"Technically since openrouter supports it we can change to deepseek in 1 line of code\" (answered by jin)\n\n**Q: Where do we keep track of degenspartanai performance?** \nA: Birdeye and Waveform are recommended platforms (answered by Noname)\n\n**Q: What LLMs have you been able to integrate with Eliza?** \nA: Check coders channel for LLM integration information (answered by BOSSU)\n\n**Q: Does Eliza have any dependency for GPU?** \nA: For basic Eliza you just need CPU, but GPU makes things faster (answered by BOSSU)\n\n## Community Help & Collaboration\n\n### Technical Support\n- **bifkn helped kobra** fix the dexscreener plugin by identifying that it was checking for an API key that doesn't exist; solution was to remove the check in index.ts.\n- **EcchiPen helped Vesper** set up a Telegram bot for groups by providing step-by-step guidance and a video tutorial.\n- **tcm390 helped Silent Quasar** with action callback issues by sharing example code showing how to implement callback function in actions.\n- **robotlovecoffee helped j.** with persistent Eliza setup errors by creating and sharing a detailed PDF guide.\n- **kAI wilder helped Qu\u0103ng** load documents into knowledge base by creating and sharing a document explaining the knowledgeManager system.\n- **Kraus helped Display Name** with concerns about using DeepSeek model with Eliza, confirming successful implementation and suggesting using the chat model instead of reasoning model if JSON generation is problematic.\n\n### Community Contributions\n- **jin tipped Grafixart 137.80 ai16z (\u2248$120)** for artwork contributions, specifically creating stickers.\n- **SM Sith Lord provided boom** with a pre-generated Block Tank episode configuration for testing without making AI calls.\n- **yikesawjeez shared AI tools** for 3D/video generation, including links to Hunyuan3D-2, Go-with-the-Flow, and FilmAgent repositories.\n\n## Action Items\n\n### Technical\n- Fix vector dimension mismatch in embedding endpoint configuration (Mentioned by j.)\n- Implement RAG (Retrieval Augmented Generation) for Eliza (Mentioned by Qu\u0103ng)\n- Create configuration for disabling retweet feature on Twitter agents (Mentioned by nearfriend)\n- Develop functionality for agents to memorize tweets without responding (Mentioned by Mahesh)\n- Fix dexscreener plugin to work without requiring an API key check (Mentioned by bifkn)\n- Fix embedding dimension mismatch issues in SQLite adapter (Mentioned by boja)\n- Improve Twitter client to handle replies to replies (Mentioned by ant)\n- Fix trustDB schema and SQL statements (Mentioned by Jesse | Telos)\n- Fix RAG functionality in develop branch (Mentioned by kAI wilder)\n- Verify if Collab-land bot is properly auditing wallet holdings for role verification (Mentioned by kalshnikov)\n- Integrate Deepseek model with DegenAI for testing (Mentioned by jin)\n- Complete memory management system for passing memories between AI instances (Mentioned by jin)\n- Finish refactoring plugin system in v2 (Mentioned by jin)\n- Implement a simple submission fee for Block Tank to reduce spam (Mentioned by jin)\n- Create a mechanism for token holders to delegate stake to vouch for agents (Mentioned by Vasily Sumanov)\n- Develop a dual pool structure similar to virtuals/pump.fun (Mentioned by BigChungus)\n- Integrate TrustDB with tokenomics for decentralized agent trust scoring (Mentioned by DorianD)\n- Implement additional camera variations for the show (Mentioned by boom)\n- Fix or update the news aggregator (Mentioned by boom)\n- Adjust lighting for black areas (Mentioned by SM Sith Lord)\n- Address the SOL shortage issue for DegenAI (Mentioned by jin)\n\n### Documentation\n- Create better documentation for plugin development workflow (Mentioned by Saburo)\n- Document how to configure Telegram bot to only respond to specific keywords (Mentioned by Meciah)\n- Create documentation for character file secrets configuration (Mentioned by Deeznutz)\n- Create a 2-3 page whitepaper explaining tokenomics simply (Mentioned by Akin)\n- Create visual explanations of each tokenomics mechanism (Mentioned by jin)\n- Document the purpose of proposed value engines (Mentioned by yikesawjeez)\n- Complete tokenomics slides and presentations (Mentioned by jin)\n- Create documentation for AI agent memory management (Mentioned by jin)\n- Create and share a high-level roadmap (Mentioned by rhota)\n- Make tracking DegenSpartanAI performance easier (Mentioned by jin)\n- Provide documentation on ElizaOS v2 (Mentioned by Leo Young)\n- Create guide for setting up Eliza with cloud backends like Supabase or Firebase (Mentioned by Magnacor)\n\n### Feature\n- Add ability to disable original tweets and only enable replies (Mentioned by RoomTemp IQ)\n- Create a CLI installer that selects which adapters/plugins to include (Mentioned by gel)\n- Add support for loading large documents into knowledge base (Mentioned by kAI wilder)\n- Add support for Zerion integration (Mentioned by Pranav)\n- Build plugin for elizaOS (Mentioned by Pranav)\n- Create AI doctor with avatar featuring real-time voice chat and body sync (Mentioned by Parzival)\n- Integrate Lit Protocol Agent Wallet for decentralized key management (Mentioned by Rick)\n- Create more DegenAI-themed stickers (Mentioned by jin)\n- Create a weekly newsletter monitoring key X accounts (Mentioned by jin)\n- Implement temporary tattoo service at events (Mentioned by Astrid)\n- Consider adding partners to associates role (Mentioned by \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20)\n- Implement a system for tracking how long teams hold ai16z tokens (Mentioned by Akin)\n- Create a leaderboard for staked agents (Mentioned by yikesawjeez)\n- Develop a premium service tier for teams that hold ai16z tokens (Mentioned by Akin)\n- Implement AI-led venture capital/game show concept (\"Block Tank\") (Mentioned by jin)\n- Launch agent marketplace/launchpad (Mentioned by Dippuccino)\n- Implement staking for AI16Z token (Mentioned by ElonMoney)\n- Set up token buybacks using launchpad revenue (Mentioned by ElonMoney)\n- Add visual elements to the set (boosters, panels, wires, LED desk) (Mentioned by boom)\n- Bring back LlamaCloud support (Mentioned by Vesper)\n- Implement DeepSeek model with Eliza (Mentioned by Display Name)\n- Create Android app for Eliza (Mentioned by Display Name)"
},
"ai_news_elizaos_discord_md_2025-01-22": {
"filename": "2025-01-22.md",
"content": "# elizaOS Discord - 2025-01-22\n\n**Date: January 22, 2025**\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Integrations\n- **Plugin System Refactoring**: The dev branch has reduced ElizaOS installation and boot time to approximately 2 seconds.\n- **Multiple Integrations Announced**: ElizaOS is now integrated with Polygon, Story Protocol, Merlin Layer2, Thirdweb, Fleek, Sui Network, and Bebop DEX.\n- **Memory Management Challenges**: Jin noted that \"passing around memories\" between different agent instances will be important for maintaining consistent agent personalities.\n- **Award Recognition**: ElizaOS received an award as \"most influential\" at the DAOvos AI x crypto summit.\n- **LLAMACLOUD Support**: Users requested the restoration of LLAMACLOUD support functionality.\n\n### DegenAI/DegenSpartanAI\n- **Trading Performance**: DegenAI has been actively trading and generating profits, with portfolio growth from $2,600 to $6,000 over 4 days.\n- **Public Wallet Concerns**: Community members debated whether having a public wallet (BzsJQeZ7cvk3pTHmKeuvdhNDkDxcZ6uCXxW2rjwC7RTq) is strategically sound, with some concerned about copy trading diluting the AI's edge.\n- **Multiple Wallets Strategy**: The team is considering implementing multiple wallets for DegenAI to prevent strategy dilution.\n- **Roadmap Development**: The team is working on improving trading capabilities and developing a roadmap to be shared soon.\n\n### Tokenomics Development\n- **Bonding Curve Model**: Unreadyplayer explained their approach using Cybers, where 77.5% of tokens are traded on the curve and 22.5% goes to locked LP.\n- **Expert Consultation**: Yardy introduced Vasily Sumanov, a token engineering expert who created a detailed tokenomics document.\n- **Tension in Approach**: There's debate between those wanting to release a simple draft tokenomics model quickly versus those developing a more sophisticated approach.\n- **Proof-of-Stake Solution**: The tokenomics document appears to include a proof-of-stake solution for trust issues, with suggestions to leverage Jito's restaking platform.\n\n### 3D AI TV Show Development\n- **Two Main Projects**: The team is working on a news show and a \"Block Tank\" show (similar to Shark Tank).\n- **Unity-Based System**: Implementation handles different event types (episodeGenerated, prepareScene, speak) and manages scene transitions, camera movements, and actor dialogues.\n- **Camera Techniques**: Various camera setups (jib cam, pan and zoom pivot cam) for different shot types, with A-roll and B-roll options that have percentage-based switching logic.\n- **Block Tank Format**: Features multiple actors (jin, peepo, spartan, elizahost, aimarc, aishaw) and several locations with 4 judges, 1 host, and 1-2 pitchers.\n\n### Technical Issues & Troubleshooting\n- **Plugin Integration Problems**: Users reported issues with bootstrap, node, solana, and dexscreener plugins.\n- **Twitter/X Client Issues**: Problems with authentication, retweets, likes, and post formatting were discussed.\n- **Embedding API Errors**: Users encountered \"Vector dimension mismatch\" errors when switching between embedding models.\n- **Windows Compatibility**: Several users discussed workarounds for Windows compatibility issues by using WSL2 for development.\n- **Telegram Bot Integration**: Questions about adding bots to group chats and controlling response triggers.\n\n### Community Projects\n- **ElizaTown**: A community platform for exploring and sharing ElizaOS characters was introduced by ShadowBeast.\n- **Ninja Terminal**: Dreygo announced a terminal for market data that will soon be integrated with an agent for better market making.\n- **AI Character Generator**: Users mentioned developing an AI character generator specifically for ElizaOS.\n- **Awesome-Eliza Repository**: Jin requested help for adding entries, improving descriptions, and organizing content in the GitHub repository.\n\n### Telegram TOS Warning\n- **Important Alert**: User \"kirsten\" warned about Telegram's updated terms of service that will impact Eliza agents by restricting the use of third-party blockchains aside from TON, with enforcement beginning February 21st.\n\n## Key Questions & Answers\n\n### ElizaOS Development\n- **Q**: How do I fix the \"Cannot read properties of undefined (reading 'actions')\" error with bootstrap plugin? \n **A**: Try a different version tag, as this appears to be a bug (answered by Odilitime)\n\n- **Q**: How do I get the dexscreener plugin working? \n **A**: Remove the API key check in index.ts and just add dexScreenerPlugin directly (answered by bifkn)\n\n- **Q**: How do I fix \"Vector dimension mismatch\" error? \n **A**: This happens when switching between embedding models; clear your local db with `rm -f ./agent/data/db.sqlite` (answered by Yoda26)\n\n- **Q**: How do I run Eliza in WSL instead of Windows? \n **A**: Clone the repo directly in WSL or move project files to Linux filesystem instead of /mnt/c/ (answered by Vesper)\n\n- **Q**: How do I change the default model to gpt-4o-mini? \n **A**: Edit your .env file with SMALL_OPENAI_MODEL=gpt-4o-mini, MEDIUM_OPENAI_MODEL=gpt-4o-mini, LARGE_OPENAI_MODEL=gpt-4o-mini (answered by Sora Dimichi)\n\n### DegenAI/DegenSpartanAI\n- **Q**: Where do we keep track of degenspartanai performance? \n **A**: Birdeye and Waveform (answered by Noname)\n\n- **Q**: Can you summarize the current update status of degenspartan ai and the future update schedule? \n **A**: Will make a post later tonight and maybe also today announcement (answered by jin)\n\n### Tokenomics\n- **Q**: What % of the token is locked in the LP against the SOL received in bonding? \n **A**: 22.5% goes to locked LP and 77.5% is traded on the bonding curve (answered by unreadyplayer)\n\n- **Q**: Does this take SOL or ai16z as the coin used for funding the bonding curve? \n **A**: This model uses ai16z as the base token, like Virtuals (answered by unreadyplayer)\n\n- **Q**: How do you guys profit? \n **A**: We'll use our 50% of the fees to cover operational costs and buy ai16z, which when it appreciates will bolster our treasury (answered by unreadyplayer)\n\n### 3D AI TV\n- **Q**: Do I just need custom config to do the blocktank tests or is that a whole new runner? \n **A**: Yeah it's just the show-config.json mostly. And the different html & json files are so you don't accidentally overwrite a different show's save. (answered by SM Sith Lord)\n\n- **Q**: How do you make the TTS ignore the \"tv\" actor's dialogue line? \n **A**: What I did in my handler was just check which actor is speaking early on in the event handling. And if the actor is \"tv\", it just does the media loading & cancels out of the normal handling. (answered by SM Sith Lord)\n\n## Community Help & Collaboration\n\n### Plugin Troubleshooting\n- **Helper**: bifkn | **Helpee**: kobra \n **Context**: Dexscreener plugin not working despite being enabled \n **Resolution**: Identified that the API key check in index.ts needed to be removed since dexscreener doesn't use API keys\n\n- **Helper**: EcchiPen | **Helpee**: CoinBurn \n **Context**: Agent retweeting too often on Twitter \n **Resolution**: Provided environment variables to control Twitter behavior including TWITTER_RETWEETS_ENABLE\n\n### Deployment & Environment Setup\n- **Helper**: EcchiPen | **Helpee**: ashish \n **Context**: Docker build failing with \"failed to compute cache key\" error \n **Resolution**: Provided step-by-step instructions including installing build-essential, checking out the correct tag, and building the Docker image\n\n- **Helper**: Vesper | **Helpee**: SINISTER \n **Context**: Running Eliza on Windows \n **Resolution**: Suggested using WSL instead of GitBash which resolved the issue\n\n### DegenAI Support\n- **Helper**: Noname | **Helpee**: Rabbidfly \n **Context**: Asking where to track DegenSpartanAI performance \n **Resolution**: Provided Birdeye link and suggested Waveform as another platform, sharing a specific link\n\n- **Helper**: M3xR | **Helpee**: Channel members \n **Context**: Reminder about Jupiter airdrop \n **Resolution**: Shared information about claiming the airdrop with a link to Jupiter's announcement\n\n### Project Updates & Documentation\n- **Helper**: witch | **Helpee**: \ubcf4\ud584 \n **Context**: \ubcf4\ud584 expressed concern about lack of progress and updates on ai16z/ElizaOS \n **Resolution**: witch compiled and shared an extensive list of recent developments and integrations from the past week, demonstrating significant project activity\n\n- **Helper**: witch | **Helpee**: Multiple partners \n **Context**: Need for a concise overview of ai16z ecosystem \n **Resolution**: witch created and shared a one-page document explaining ai16z, Eliza Labs, elizaOS, and tokenomics\n\n### 3D AI TV Development\n- **Helper**: SM Sith Lord | **Helpee**: boom \n **Context**: Setting up Block Tank testing environment \n **Resolution**: Provided a zip file with pre-configured setup to replay bundled episodes using browser-based TTS without making AI calls\n\n## Action Items\n\n### Technical\n- Fix dexscreener plugin to work without requiring API key configuration (mentioned by kobra)\n- Fix Twitter client to prevent posting JSON instead of normal text (mentioned by SecretRecipe)\n- Implement proper rate limiting for Twitter posts (mentioned by mr.code)\n- Fix bootstrap plugin \"Cannot read properties of undefined (reading 'actions')\" error (mentioned by TPB_Solana)\n- Fix Telegram bot to only respond to specific keywords or mentions (mentioned by Meciah)\n- Fix embedding API errors when switching between models (mentioned by Amit Surve)\n- Improve Docker deployment process (mentioned by cjohndesign)\n- Fix Twitter Spaces functionality (mentioned by SquintDev)\n- Update Telegram-based Eliza agents to comply with new TOS restrictions (mentioned by kirsten)\n- Integrate Ninja Terminal data with agents for market making (mentioned by Dreygo)\n- Implement ElizaTown platform for sharing ElizaOS characters (mentioned by ShadowBeast)\n- Implement multiple wallets for DegenAI to prevent strategy dilution (mentioned by jin and M3xR)\n- Improve DegenAI trading capabilities (mentioned by rhota)\n- Implement responsive design for mobile users on the ai16z listing page (mentioned by unreadyplayer)\n- Implement dark theme for the platform (mentioned by unreadyplayer)\n- Consider leveraging Jito's restaking platform for the proof of stake solution (mentioned by BigChungus)\n- Create a system for passing memories between different AI agent instances (mentioned by jin)\n- Implement a newsletter system based on changelog updates (mentioned by jin)\n- Improve PR templates for plugin contributions (mentioned by DorianD)\n- Implement proper handling for TV actor dialogue to prevent TTS from reading URLs (mentioned by boom)\n- Fix JSON response loading issues in TVtest (mentioned by boom)\n- Consider creating a separate event type for TV-specific actions (mentioned by boom)\n- Integrate multiple camera types (jib cam, pan and zoom pivot) for AI TV (mentioned by boom)\n\n### Documentation\n- Create comprehensive guide for plugin development (mentioned by mconstant)\n- Document all available environment variables and their functions (mentioned by SecretRecipe)\n- Create guide for deploying Eliza to production environments (mentioned by Magicred1)\n- Add README files to all plugins (mentioned by kobra)\n- Create guide for database adapter configuration (mentioned by ad0ll)\n- Create guide for setting up Eliza with cloud backends (mentioned by Magnacor)\n- Provide clear documentation on ElizaOS V2 (mentioned by Leo Young)\n- Create and share a high-level roadmap (mentioned by rhota)\n- Post update on DegenSpartanAI status and future schedule (mentioned by jin)\n- Release draft tokenomics document for community feedback (mentioned by Akin)\n- Create simplified 2-3 page whitepaper version of tokenomics (mentioned by Akin)\n- Distill each tokenomics mechanism into simple visuals/tweets (mentioned by jin)\n- Create a capabilities-focused website (mentioned by avirtualfuture)\n- Develop better explanations of what plugins do (mentioned by DorianD)\n- Establish a formal ElizaOS news channel independent of core developers (mentioned by DorianD)\n- Update README for ai-news project (mentioned by jin)\n\n### Feature\n- Create stickers for the community (mentioned by Grafixart)\n- Develop AI doctor with avatar (mentioned by Parzival)\n- Add support for human-in-the-loop agent actions (mentioned by rabbai0078155)\n- Add SMS integration for AI assistant (mentioned by Jungle)\n- Support for non-AWS S3-compatible storage (mentioned by dtb)\n- Add support for DeepSeek model (mentioned by dook_us)\n- Implement multi-stage actions for plugins (mentioned by egoarka)\n- Add support for WhatsApp integration (mentioned by Carlos Bastidas)\n- Consider DegenAI as a broader DeFi tool for public use (mentioned by tigerguo.)\n- Implement a token economy model (mentioned by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f)\n- Develop a soulbound NFT system (mentioned by witch)\n- Share DegenAI trading videos on X (mentioned by anon)\n- Establish ElizaOS fee structure (mentioned by \ubcf4\ud584)\n- Create a weekly newsletter monitoring specific X accounts (mentioned by jin)\n- Include services building on ElizaOS in newsletter (mentioned by Astrid)\n- Create a folder of funny screenshots from agent interactions for social media content (mentioned by Astrid)\n- Hold contests for best AI agent with voting during newshour (mentioned by Astrid)\n- Implement Block Tank show with multiple actors and locations (mentioned by SM Sith Lord)"
},
"ai_news_elizaos_discord_md_2025-01-21": {
"filename": "2025-01-21.md",
"content": "# elizaOS Discord - 2025-01-21\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Ecosystem\n\n- **ElizaOS Partnerships**: Multiple integrations were announced this week, including partnerships with Polygon, Story Protocol, Merlin Layer 2, Thirdweb, Fleek, Sui Network, and Bebop DEX.\n\n- **DegenAI Progress**: DegenSpartanAI has begun trading with a portfolio that grew from $2,600 to $6,000 in four days, demonstrating its trading capabilities. The trading wallet (BzsJQeZ7cvk3pTHmKeuvdhNDkDxcZ6uCXxW2rjwC7RTq) has been made public for transparency.\n\n- **Telegram Policy Change**: Kirsten warned about Telegram's updated terms of service affecting Eliza agents by restricting \"third-party blockchains\" aside from TON, with enforcement starting February 21.\n\n- **Deepseek R1 Model**: Jin described it as \"a wakeup call for American open source AI\" that offers performance comparable to o1/sonnet models at 30x cheaper cost and is MIT licensed.\n\n- **Kraken Listing**: Kraken has added ai16z to its listing roadmap, signaling increased institutional interest.\n\n### Technical Discussions\n\n- **Docker Deployment Issues**: Users discussed troubleshooting \"process.stdout.clearLine is not a function\" errors in Docker environments, with recommendations to use docker-compose instead of regular Docker.\n\n- **Database Challenges**: Several users reported issues with SQLite and Supabase adapters, with workarounds shared for forcing SQLite when Supabase connections fail.\n\n- **Model Provider Configuration**: Discussions about configuring various AI model providers (OpenAI, Anthropic, Gaia, DeepSeek) and setting environment variables correctly.\n\n- **Client Integration Problems**: Users troubleshooting Twitter, Telegram, and Discord integrations, including authentication issues and rate limiting concerns.\n\n### Community Projects\n\n- **ElizaTown**: ShadowBeast introduced ElizaTown, an open-source platform for exploring and sharing ElizaOS characters.\n\n- **3D AI TV Projects**: Development of a news show and \"Block Tank\" project in Unity, with discussions about scene setup, character models, and event handling for interactive 3D environments.\n\n- **Cybers Tokenization Platform**: Unreadyplayer from Cybers presented their tokenization platform with a customized bonding curve AMM that could integrate with ai16z, featuring permanent LP locking and fee distribution.\n\n- **DegenAI Website**: Ongoing development with community feedback about improving design, adding clear purpose, and including tokenomics information.\n\n## Key Questions & Answers\n\n**Q: How do I fix the \"process.stdout.clearLine is not a function\" error in Docker?** \nA: Use docker-compose instead of regular Docker, as it handles terminal interactions better. (Heady Shotta)\n\n**Q: How do I clear the database in Eliza?** \nA: Delete the db.sqlite file in the agent/data directory. (DeGenX)\n\n**Q: How much RAM is needed to run ElizaOS?** \nA: 2GB RAM is sufficient for basic operation; running multiple agents may require more. (Mad)\n\n**Q: How do I activate a Discord bot with ElizaOS?** \nA: Turn on Privileged Gateway Intents in Discord Developer Portal. (nori)\n\n**Q: What is the difference between partner and associate?** \nA: Partner requires 100k AI16Z tokens, Associate requires 10k. (Smore)\n\n**Q: How does the Cybers tokenization platform work with ai16z?** \nA: It uses ai16z as the base token, with 50% of fees going to ai16z treasury and 50% to Cybers which they'll use to buy ai16z. (unreadyplayer)\n\n**Q: What is the goal of the DegenAI website?** \nA: It's a landing page with plans to include DegenSpartan lore, quotes, trade visualization, development roadmap, functionality details, and updates. (jin and yikesawjeez)\n\n**Q: What progress has been made with ai16z recently?** \nA: Numerous partnerships and integrations from the past week, including with Polygon, Story Protocol, Merlin Layer 2, Thirdweb, Fleek, Sui Network, and Bebop DEX. (witch)\n\n## Community Help & Collaboration\n\n- **Database Troubleshooting**: Perez helped averma with a database initialization error with Supabase by providing code to force SQLite database instead.\n\n- **Windows Installation Support**: EcchiPen provided step-by-step instructions for using WSL and Docker to ashish who was having Windows installation issues.\n\n- **Docker Deployment Guidance**: Mconstant shared docker-compose.yml configuration and deployment tips for Phala Cloud with joaointech.\n\n- **Model Configuration Help**: Sora Dimichi shared .env configuration for setting gpt-4o-mini as the default model.\n\n- **Tokenomics Explanation**: Witch created and shared a one-page document summarizing ai16z, Eliza Labs, ElizaOS, and tokenomics plans to address partner questions.\n\n- **3D Model Fixes**: SM Sith Lord helped boom with fixing reversed normals on Block Tank models, suggesting scaling the model by -1 (though boom ultimately created a custom shader).\n\n## Action Items\n\n### Technical\n\n- Fix SQLite database connection issues with plugins (Iv/-\\nB)\n- Implement memory persistence across different clients to enable agents to share context between Twitter, Discord, Telegram (Jungle)\n- Fix Twitter like functionality in v0.1.8 that worked in v0.1.7 (SecretRecipe)\n- Resolve DeepSeek model integration issues (TruffleSoul)\n- Fix website responsiveness issues for DegenAI (M3xR)\n- Implement virtual exchange functionality with real-time market data (jin)\n- Create 2D website version before moving to full 3D implementation (jin)\n- Implement multiple wallets for DegenAI to prevent strategy dilution (M3xR)\n- Integrate Cybers tokenization platform with ai16z as token pair (unreadyplayer)\n- Fix the daily summary JSON data showing incorrect dates for 3D news show (boom)\n- Implement media URL loading logic for images in Unity (boom)\n- Create character personalities for Degen, Eliza, and Tubbs (fishai)\n- Fix visemes for character models, particularly Vitalik (boom)\n- Implement proper event handling for TV events (boom)\n\n### Documentation\n\n- Document environment variables for Twitter behavior control (EcchiPen)\n- Create better Docker deployment guide (cjohndesign)\n- Update model provider configuration documentation (cryptoAYA)\n- Create development roadmap and timeline for DegenAI (tigerguo.)\n- Document DegenAI's AI functions and capabilities (tigerguo.)\n- Create an updates section for the DegenAI website (tigerguo.)\n- Publish tokenomics information including the 8% buyback (\ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create Eliza trained on Eliza docs and agent dev school to onboard more developers (jin)\n- Develop three-tier certification program for ElizaOS users and developers (DorianD)\n- Create AI agents/workflows to keep documentation updated with changing codebase (jin)\n- Document the event system architecture for 3D AI TV projects (boom)\n- Contribute to awesome-eliza GitHub repository (adding entries, improving descriptions, fixing typos, organizing content) (jin)\n\n### Features\n\n- Add rate limiting for agent responses to prevent API rate limiting (mr.code)\n- Add SMS integration capability via services like Twilio (Jungle)\n- Support for non-English language responses (Xisk99)\n- Visualize DegenAI's trades on the website (jin)\n- Add virtual exchange to the DegenAI website (tigerguo.)\n- Expose development team members on the DegenAI website (tigerguo.)\n- Implement an AI copilot that summarizes discussions and provides structured information about tokenomics (ElonMoney)\n- Develop an \"enterprise support\" model for the DAO to support F500 companies using ElizaOS (DorianD)\n- Implement staking for CYBR against agent tokens to incentivize bonding, buying and holding (unreadyplayer)\n- Develop a \"capabilities\" marketing website showcasing ElizaOS capabilities (avirtualfuture)\n- Build a starter project generator where users can activate plugins by \"loading cartridges\" (avirtualfuture)\n- Implement a soulbound NFT system for partners (witch)\n- Develop an Eliza News Channel independent of Eliza Labs (DorianD)"
},
"ai_news_elizaos_daily_json_2025-01-23": {
"filename": "2025-01-23.json",
"content": {
"type": "elizaosDailySummary",
"title": "Daily Report - 2025-01-23",
"categories": [
{
"title": "Eliza OS GitHub Updates Summary",
"content": [
{
"text": "# New Plugins\n\nEliza OS has added several new plugins to enhance functionality:\n\n- **Hyperbolic-plugin** (PR #2701)\n- **Eliza OmniFlix Plugin** (PR #2693)\n- **Suno music generation** (PR #2679)\n- **Samsung SmartThings plugin** (PR #2678)\n- **Udio music generation** (PR #2660)\n- **SimsAI Release V1.0** (PR #2618)\n- **Football plugin** (PR #2461)\n- **Adapter-qdrant** (PR #2322)\n- **Chainbase plugin** (PR #2162)\n- **Holdstation swap plugin** (PR #2741)\n- **Ethstorage plugin** (PR #2737)\n- **Sei Plugin** (PR #2720)\n- **Imgflip plugin** for generating memes (PR #2711)\n- **Lit plugin** (PR #2703)\n- **Mina blockchain support** (PR #2702)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2701",
"https://github.com/elizaOS/eliza/pull/2693",
"https://github.com/elizaOS/eliza/pull/2679",
"https://github.com/elizaOS/eliza/pull/2678",
"https://github.com/elizaOS/eliza/pull/2660",
"https://github.com/elizaOS/eliza/pull/2618",
"https://github.com/elizaOS/eliza/pull/2461",
"https://github.com/elizaOS/eliza/pull/2322",
"https://github.com/elizaOS/eliza/pull/2162",
"https://github.com/elizaOS/eliza/pull/2741",
"https://github.com/elizaOS/eliza/pull/2737",
"https://github.com/elizaOS/eliza/pull/2720",
"https://github.com/elizaOS/eliza/pull/2711",
"https://github.com/elizaOS/eliza/pull/2703",
"https://github.com/elizaOS/eliza/pull/2702"
],
"images": [],
"videos": []
},
{
"text": "# Bug Fixes\n\nSeveral bugs were addressed in recent updates:\n\n- Fixed duplicated handlePendingTweet (PR #2715)\n- Fixed unexpected JSON Metadata in Twitter Bot Replies (PR #2712)\n- Corrected STT plugin userId type (PR #2704)\n- Fixed aesthetic issues with bullets and numbered lists (PR #2698)\n- Fixed types syntax issue (PR #2694)\n- Ensured scoped IDs are properly used for existing knowledge checks (PR #2690)\n- Fixed debug targets to show elizalogger debug messages (PR #2685)\n- Removed wrong comment (PR #2683)\n- Fixed TON plugin build issues (PR #2757, PR #2755)\n- Deleted plugin-bootstrap sex message to prevent API sensitivity alerts (PR #2748)\n- Resolved @ai-sdk/provider version conflicts (PR #2714)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2715",
"https://github.com/elizaOS/eliza/pull/2712",
"https://github.com/elizaOS/eliza/pull/2704",
"https://github.com/elizaOS/eliza/pull/2698",
"https://github.com/elizaOS/eliza/pull/2694",
"https://github.com/elizaOS/eliza/pull/2690",
"https://github.com/elizaOS/eliza/pull/2685",
"https://github.com/elizaOS/eliza/pull/2683",
"https://github.com/elizaOS/eliza/pull/2757",
"https://github.com/elizaOS/eliza/pull/2755",
"https://github.com/elizaOS/eliza/pull/2748",
"https://github.com/elizaOS/eliza/pull/2714"
],
"images": [],
"videos": []
},
{
"text": "# Feature Enhancements\n\nSignificant feature improvements were implemented:\n\n- Added error message functionality (PR #2717)\n- Improved handling of user IDs and memory storage for Space (PR #2686)\n- Implemented runProcess function in test library (PR #2672)\n- Added custom S3 endpoint URL for 'plugin-node' (PR #2176)\n- Enhanced TON plugin with debug scripts and transfer fixes (PR #2744)\n- Restricted Discord bot to respond only in allowed channels (PR #2743)\n- Added minimal workflow to resolve ephemeral check (PR #2735)\n- Implemented biome automation via Python with reporting (PR #2733)\n- Moved cleanJsonResponse to parsing (PR #2732)\n- Improved Twitter parsing (PR #2730)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2717",
"https://github.com/elizaOS/eliza/pull/2686",
"https://github.com/elizaOS/eliza/pull/2672",
"https://github.com/elizaOS/eliza/pull/2176",
"https://github.com/elizaOS/eliza/pull/2744",
"https://github.com/elizaOS/eliza/pull/2743",
"https://github.com/elizaOS/eliza/pull/2735",
"https://github.com/elizaOS/eliza/pull/2733",
"https://github.com/elizaOS/eliza/pull/2732",
"https://github.com/elizaOS/eliza/pull/2730"
],
"images": [],
"videos": []
},
{
"text": "# Other Changes\n\n- Removed log that could potentially cause app crashes (PR #2716)\n- Improved GitBook Provider Output by including query context (PR #2659)\n- Performed lint pass (PR #2580)\n- Added Hyperliquid environment variables to env example (PR #2736)\n- Added source example links to core/evaluators (PR #2724)\n- Updated test configuration and coverage for client-eliza-home (PR #2719)\n- Updated to latest allora-sdk version in the Allora Plugin (PR #2707)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2716",
"https://github.com/elizaOS/eliza/pull/2659",
"https://github.com/elizaOS/eliza/pull/2580",
"https://github.com/elizaOS/eliza/pull/2736",
"https://github.com/elizaOS/eliza/pull/2724",
"https://github.com/elizaOS/eliza/pull/2719",
"https://github.com/elizaOS/eliza/pull/2707"
],
"images": [],
"videos": []
}
],
"topic": "completed_items"
},
{
"title": "Twitter Activity from @dankvr and @shawmakesmagic",
"content": [
{
"text": "Twitter users @dankvr and @shawmakesmagic have been active on various crypto, AI, and political topics. @dankvr shared content about anonymity in crypto, referencing a 'tornado cash shirt' that became a bestseller, and discussed trading activities related to @0xPolygon and @degenspartanai.",
"sources": [
"https://twitter.com/dankvr/status/1882526536454324455",
"https://twitter.com/dankvr/status/1882514261374910670",
"https://twitter.com/dankvr/status/1882446896918368661"
],
"images": [
"https://pbs.twimg.com/media/GiAGw7iWcAA-VIV.png"
],
"videos": []
},
{
"text": "@shawmakesmagic discussed forms of capital, ranking mindshare/attention, competence, trust, authenticity, and network above money. He also congratulated the Moemate team on their token launch and engaged with @VitalikButerin about democratizing lobbying through memecoins.",
"sources": [
"https://twitter.com/shawmakesmagic/status/1882478335403639168",
"https://twitter.com/shawmakesmagic/status/1882562071675720123",
"https://twitter.com/shawmakesmagic/status/1882560703338553570",
"https://twitter.com/shawmakesmagic/status/1882563516403773817"
],
"images": [],
"videos": []
},
{
"text": "A significant thread from @shawmakesmagic addressed conspiracy theories about election manipulation, emphatically stating 'GUYS WE DIDN'T RIG THE ELECTION' and explaining that 'Elon has no idea Eliza exists, X doesn't use/need Eliza.' He described the conspiracy as 'obviously a LARP by some troll' and expressed frustration about fake GitHub claims.",
"sources": [
"https://twitter.com/shawmakesmagic/status/1882455120715423912",
"https://twitter.com/shawmakesmagic/status/1882455837106716899",
"https://twitter.com/shawmakesmagic/status/1882218390879920213"
],
"images": [
"https://pbs.twimg.com/media/Gh_TmyCXMAAlgKT.jpg"
],
"videos": []
},
{
"text": "@shawmakesmagic also shared thoughts on authenticity, stating 'You should really just allow characters to be characters' and 'If you're not crashing out sometimes you're not being real,' advocating for people to 'be yourself and stop trying to control other people's behavior.'",
"sources": [
"https://twitter.com/shawmakesmagic/status/1882349308391072003"
],
"images": [],
"videos": []
}
],
"topic": "tweet"
},
{
"title": "Recent Issues in the ElizaOS GitHub Repository",
"content": [
{
"text": "Several issues have been reported in the ElizaOS GitHub repository related to package dependencies, plugin functionality, and client operations. These include:\n\n1. Package dependency issues:\n - Issue #2721: The @elizaos/plugin-tee-log@0.1.8 package has an incorrect workspace dependency reference\n - Issue #2729: The @elizaos/plugin-rabbi-trader plugin has not been published to npm\n\n2. Client and plugin functionality problems:\n - Issue #2700: Error in fetching tweets in client-twitter\n - Issue #2754: Image vision/description not working on Twitter client\n - Issue #2695: Plugins field appears to be unusable in character.json\n - Issue #2697: Difficulty creating hardcoded responses in actions\n\n3. Build and integration issues:\n - Issue #2727: Failed client build when running 'pnpm build'\n - Issue #2722: Request for Deepseek support in the Eliza eliza-starter repository\n\n4. User assistance requests:\n - Issue #2745: Question about Twitter API requirements\n - Issue #2746: General request for help",
"sources": [
"https://github.com/elizaOS/eliza/issues/2721",
"https://github.com/elizaOS/eliza/issues/2722",
"https://github.com/elizaOS/eliza/issues/2700",
"https://github.com/elizaOS/eliza/issues/2697",
"https://github.com/elizaOS/eliza/issues/2695",
"https://github.com/elizaOS/eliza/issues/2745",
"https://github.com/elizaOS/eliza/issues/2727",
"https://github.com/elizaOS/eliza/issues/2746",
"https://github.com/elizaOS/eliza/issues/2754",
"https://github.com/elizaOS/eliza/issues/2729"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2721",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2722",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2700",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2697",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2695",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2745",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2727",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2746",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2754",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2729"
],
"videos": []
}
],
"topic": "issue"
},
{
"title": "Recent Pull Requests in the elizaOS/eliza Repository",
"content": [
{
"text": "Several new plugins and features have been proposed for the Eliza project through recent pull requests. These include:\n\n- A lit plugin (PR #2703)\n- The official SimsAI plugin release V1.0 (PR #2618)\n- An OmniFlix plugin (PR #2693)\n- A Form chain plugin (PR #2728)\n- The plugin-feel which is still in progress (PR #867)\n\nAdditionally, there are improvements to GitHub functionality:\n- GitHub plugins unique rooms feature (PR #2767)\n- GitHub client multi-user support (PR #2752)\n\nOther technical enhancements include:\n- Removing hardcoded branch names when committing changes (PR #2705)\n- Biome automation via Python with reporting capabilities (PR #2733)\n\nThese pull requests represent ongoing development efforts to expand Eliza's capabilities and improve its functionality.",
"sources": [
"https://github.com/elizaOS/eliza/pull/2705",
"https://github.com/elizaOS/eliza/pull/2703",
"https://github.com/elizaOS/eliza/pull/2618",
"https://github.com/elizaOS/eliza/pull/2693",
"https://github.com/elizaOS/eliza/pull/2767",
"https://github.com/elizaOS/eliza/pull/2752",
"https://github.com/elizaOS/eliza/pull/867",
"https://github.com/elizaOS/eliza/pull/2728",
"https://github.com/elizaOS/eliza/pull/2733"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2705",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2703",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2618",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2693"
],
"videos": []
}
],
"topic": "pull_request"
},
{
"title": "ElizaOS GitHub Activity Update",
"content": [
{
"text": "The elizaos/eliza repository showed consistent activity over a two-day period. From January 23-24, 2025, there were 28 new pull requests with 24 merged, 9 new issues created, and 62 active contributors. The following day (January 24-25, 2025) saw 24 new pull requests with 20 merged, 17 new issues, and a slight increase to 64 active contributors. Overall, the project maintained strong development momentum with high PR merge rates and steady contributor engagement.",
"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, their contributions, or any statistics related to the project. Without additional information, it's not possible to generate a detailed summary about the top contributors to the elizaOS/eliza project.",
"sources": [
"Top contributors for elizaOS/eliza"
],
"images": [],
"videos": []
}
],
"topic": "contributors"
}
],
"date": 1737590400
}
},
"ai_news_elizaos_daily_md_2025-01-23": {
"filename": "2025-01-23.md",
"content": "# Eliza OS GitHub Updates Summary\n\n## New Plugins\n- **Hyperbolic-plugin** (PR #2701)\n- **Eliza OmniFlix Plugin** (PR #2693)\n- **Suno music generation** (PR #2679)\n- **Samsung SmartThings plugin** (PR #2678)\n- **Udio music generation** (PR #2660)\n- **SimsAI Release V1.0** (PR #2618)\n- **Football plugin** (PR #2461)\n- **Adapter-qdrant** (PR #2322)\n- **Chainbase plugin** (PR #2162)\n- **Holdstation swap plugin** (PR #2741)\n- **Ethstorage plugin** (PR #2737)\n- **Sei Plugin** (PR #2720)\n- **Imgflip plugin** for generating memes (PR #2711)\n- **Lit plugin** (PR #2703)\n- **Mina blockchain support** (PR #2702)\n- **Form chain plugin** (PR #2728)\n\n## Bug Fixes\n- Fixed duplicated handlePendingTweet (PR #2715)\n- Fixed unexpected JSON Metadata in Twitter Bot Replies (PR #2712)\n- Corrected STT plugin userId type (PR #2704)\n- Fixed aesthetic issues with bullets and numbered lists (PR #2698)\n- Fixed types syntax issue (PR #2694)\n- Ensured scoped IDs are properly used for existing knowledge checks (PR #2690)\n- Fixed debug targets to show elizalogger debug messages (PR #2685)\n- Removed wrong comment (PR #2683)\n- Fixed TON plugin build issues (PR #2757, PR #2755)\n- Deleted plugin-bootstrap sex message to prevent API sensitivity alerts (PR #2748)\n- Resolved @ai-sdk/provider version conflicts (PR #2714)\n\n## Feature Enhancements\n- Added error message functionality (PR #2717)\n- Improved handling of user IDs and memory storage for Space (PR #2686)\n- Implemented runProcess function in test library (PR #2672)\n- Added custom S3 endpoint URL for 'plugin-node' (PR #2176)\n- Enhanced TON plugin with debug scripts and transfer fixes (PR #2744)\n- Restricted Discord bot to respond only in allowed channels (PR #2743)\n- Added minimal workflow to resolve ephemeral check (PR #2735)\n- Implemented biome automation via Python with reporting (PR #2733)\n- Moved cleanJsonResponse to parsing (PR #2732)\n- Improved Twitter parsing (PR #2730)\n- GitHub plugins unique rooms feature (PR #2767)\n- GitHub client multi-user support (PR #2752)\n- Removed hardcoded branch names when committing changes (PR #2705)\n\n## Other Changes\n- Removed log that could potentially cause app crashes (PR #2716)\n- Improved GitBook Provider Output by including query context (PR #2659)\n- Performed lint pass (PR #2580)\n- Added Hyperliquid environment variables to env example (PR #2736)\n- Added source example links to core/evaluators (PR #2724)\n- Updated test configuration and coverage for client-eliza-home (PR #2719)\n- Updated to latest allora-sdk version in the Allora Plugin (PR #2707)\n\n## GitHub Activity Metrics\n- January 23-24, 2025: 28 new PRs (24 merged), 9 new issues, 62 active contributors\n- January 24-25, 2025: 24 new PRs (20 merged), 17 new issues, 64 active contributors\n\n## Twitter Activity\n- @dankvr shared content about anonymity in crypto, referencing a 'tornado cash shirt' and discussed trading activities related to @0xPolygon and @degenspartanai\n- @shawmakesmagic discussed forms of capital, ranking mindshare/attention above money\n- @shawmakesmagic congratulated the Moemate team on their token launch\n- @shawmakesmagic engaged with @VitalikButerin about democratizing lobbying through memecoins\n- @shawmakesmagic addressed conspiracy theories about election manipulation\n- @shawmakesmagic shared thoughts on authenticity and being genuine online"
},
"ai_news_elizaos_daily_discord_json_2025-01-23": {
"filename": "2025-01-23.json",
"content": {
"server": "elizaOS",
"title": "elizaOS Discord - 2025-01-23",
"date": 1737590400,
"stats": {
"totalMessages": 3260,
"totalUsers": 362
},
"categories": [
{
"channelId": "1253563209462448241",
"channelName": "discussion",
"summary": "# Discord Chat Analysis\n\n## 1. Summary\nThis Discord chat primarily revolves around the ElizaOS platform, an AI agent development framework. Most interactions involve BOSSU (an AI assistant) responding to user queries about ElizaOS functionality, development resources, and community information. The chat reveals that ElizaOS allows users to build custom AI agents with various capabilities, including Twitter integration. Users frequently ask about technical aspects like model integration, vector dimension mismatches, and agent configuration. The community appears to be actively developing agents, with discussions about LLM integration, embedding endpoints, and customization options. There's also significant interest in the project's tokens (ai16z, degenai) with some price discussion. Key resources mentioned include \"agent dev school\" on YouTube and a coders channel for technical support. The chat indicates ElizaOS is positioning itself as a framework for building personalized AI agents with social media capabilities.\n\n## 2. FAQ\nQ: How do I run Eliza? (asked by j.) A: Check the coders channel and agent dev school on YouTube for setup help (answered by BOSSU)\nQ: Does Eliza have any dependency for GPU? (asked by Alan) A: For basic Eliza you just need CPU, but GPU makes things faster (answered by BOSSU)\nQ: What's the default model Eliza is using? (asked by Alan) A: Llama by default but check coders channel for all model options (answered by BOSSU)\nQ: Is there a way to make an agent ONLY in reply guy mode without creating original tweets? (asked by RoomTemp IQ) A: Check coders channel for customizing reply settings (answered by BOSSU)\nQ: How do I fix \"SqliteError: Vector dimension mismatch. First vector has 384 dimensions, while the second has 1536 dimensions\"? (asked by j.) A: Head to coders channel for help with vector dimension mismatches (answered by BOSSU)\nQ: Which command can be used to update Eliza? (asked by bonidom) A: Head to coders channel for update help (answered by BOSSU)\nQ: How do I disable the retweet feature of Twitter when using Eliza? (asked by nearfriend) A: Head to coders channel for Twitter configuration help (answered by BOSSU)\nQ: What LLMs have you been able to integrate with Eliza? (asked by gelgit.eth) A: Check coders channel for LLM integration information (answered by BOSSU)\nQ: Is there a way for the agent to memorize tweets without actually responding to them? (asked by Mahesh) A: Agents can observe without interacting, just follow the profile (answered by BOSSU)\nQ: What's the best unified source of latest ElizaOS partnerships? (asked by Zardique) A: Check rules-and-links for all the latest updates and partnerships (answered by BOSSU)\n\n## 3. Help Interactions\nHelper: BOSSU | Helpee: CryptoPAC | Context: Looking for agent dev school channel | Resolution: Directed to elizaos discord for agent dev school resources\nHelper: BOSSU | Helpee: GBA ADVANCE | Context: Running LLM locally on Windows with 4070 GPU | Resolution: Suggested oobabooga webui for local LLM setup\nHelper: BOSSU | Helpee: Magnacor | Context: Setting up Eliza bot with cloud backend | Resolution: Directed to coders channel for tutorials on setting up agents\nHelper: Mad | Helpee: gelgit.eth | Context: LLM integration with Eliza | Resolution: Suggested using OpenRouter for access to multiple LLMs\nHelper: jin | Helpee: Grafixart | Context: Rewarding user for creating stickers | Resolution: Tipped 137.80 ai16z (\u2248$120) for artwork contributions\n\n## 4. Action Items\nType: Technical | Description: Fix vector dimension mismatch in embedding endpoint configuration | Mentioned By: j.\nType: Technical | Description: Implement RAG (Retrieval Augmented Generation) for Eliza | Mentioned By: Qu\u0103ng\nType: Technical | Description: Create configuration for disabling retweet feature on Twitter agents | Mentioned By: nearfriend\nType: Technical | Description: Develop functionality for agents to memorize tweets without responding | Mentioned By: Mahesh\nType: Technical | Description: Build plugin for elizaOS | Mentioned By: Pranav\nType: Feature | Description: Create AI doctor with avatar featuring real-time voice chat and body sync | Mentioned By: Parzival\nType: Feature | Description: Integrate Lit Protocol Agent Wallet for decentralized key management | Mentioned By: Rick\nType: Feature | Description: Create more DegenAI-themed stickers | Mentioned By: jin\nType: Documentation | Description: Provide documentation on ElizaOS v2 | Mentioned By: Leo Young\nType: Documentation | Description: Create guide for setting up Eliza with cloud backends like Supabase or Firebase | Mentioned By: Magnacor",
"messageCount": 396,
"userCount": 133
},
{
"channelId": "1300025221834739744",
"channelName": "\ud83d\udcbb-coders",
"summary": "# Analysis of \ud83d\udcbb-coders Discord Chat\n\n## 1. Summary\nThe chat revolves around users troubleshooting various issues with the Eliza agent framework. Key technical discussions include: configuring plugins like dexscreener, handling embedding dimension mismatches, Twitter client functionality issues, and deployment challenges. Users struggle with environment setup, model configuration, and client integration. Several users encounter errors with SQLite, embedding dimensions, and Twitter interactions. Solutions include modifying index.ts files to properly load plugins, adjusting environment variables, and using specific Node.js versions (23.3.0). The conversation highlights the complexity of the codebase and the need for better documentation, especially regarding plugin integration and client configuration.\n\n## 2. FAQ\nQ: How do I fix the dexscreener plugin not working? (asked by kobra) A: Remove the API key check in index.ts and directly add dexScreenerPlugin (answered by bifkn)\nQ: How do I fix \"Vector dimension mismatch\" error? (asked by j.) A: Set USE_OPENAI_EMBEDDING=TRUE in .env file (answered by boja)\nQ: How do I make my agent respond to replies on Twitter? (asked by paxva) A: Check ACTION_INTERVAL, ENABLE_ACTION_PROCESSING, MAX_ACTIONS_PROCESSING, ACTION_TIMELINE_TYPE settings (answered by tcm390)\nQ: How do I disable Twitter retweets? (asked by paxva) A: Remove retweet from the actions portion in the code (answered by paxva)\nQ: How do I integrate a website with my Eliza agent? (asked by robotlovecoffee) A: Unanswered\nQ: How do I implement human-in-the-loop agent actions? (asked by robotlovecoffee) A: Unanswered\nQ: How do I load large text documents into the knowledge database? (asked by kAI wilder) A: Use processCharacterRAGKnowledge in the codebase (answered by Qu\u0103ng)\nQ: How do I implement multi-stage actions properly? (asked by egoarka) A: Use two actions for better security (answered by EcchiPen)\nQ: How do I fix the \"language plpgsql does not exist\" error? (asked by starlord) A: Unanswered\nQ: How do I make my Telegram bot only respond when mentioned? (asked by Meciah) A: Unanswered\n\n## 3. Help Interactions\nHelper: bifkn | Helpee: kobra | Context: Dexscreener plugin not working despite being loaded | Resolution: Identified that the plugin was checking for an API key that doesn't exist; solution was to remove the check in index.ts\nHelper: EcchiPen | Helpee: Vesper | Context: Setting up Telegram bot for groups | Resolution: Provided step-by-step guidance and video tutorial on how to add a bot to a group\nHelper: tcm390 | Helpee: Silent Quasar | Context: Action callback not being triggered | Resolution: Shared example code showing how to implement callback function in actions\nHelper: validsyntax | Helpee: j. | Context: Multiple embedding errors and node version issues | Resolution: Suggested using Node v23.3.0 and systematically debugging errors\nHelper: robotlovecoffee | Helpee: j. | Context: Persistent errors with Eliza setup | Resolution: Created and shared a detailed PDF guide for setting up Eliza starter\nHelper: kAI wilder | Helpee: Qu\u0103ng | Context: Loading documents into knowledge base | Resolution: Created and shared a document explaining the knowledgeManager system\nHelper: Kren | Helpee: BlueChip | Context: Twitter client not posting after first tweet | Resolution: Explained the tweet interval system and where to find relevant settings\n\n## 4. Action Items\nType: Technical | Description: Fix dexscreener plugin to work without requiring an API key check | Mentioned By: bifkn\nType: Technical | Description: Fix embedding dimension mismatch issues in SQLite adapter | Mentioned By: boja\nType: Technical | Description: Improve Twitter client to handle replies to replies | Mentioned By: ant\nType: Technical | Description: Fix trustDB schema and SQL statements | Mentioned By: Jesse | Telos\nType: Technical | Description: Fix the issue with Twitter client not responding to mentions | Mentioned By: paxva\nType: Technical | Description: Fix RAG functionality in develop branch | Mentioned By: kAI wilder\nType: Documentation | Description: Create better documentation for plugin development workflow | Mentioned By: Saburo\nType: Documentation | Description: Document how to configure Telegram bot to only respond to specific keywords | Mentioned By: Meciah\nType: Documentation | Description: Create documentation for character file secrets configuration | Mentioned By: Deeznutz\nType: Feature | Description: Add ability to disable original tweets and only enable replies | Mentioned By: RoomTemp IQ\nType: Feature | Description: Create a CLI installer that selects which adapters/plugins to include | Mentioned By: gel\nType: Feature | Description: Add support for loading large documents into knowledge base | Mentioned By: kAI wilder\nType: Feature | Description: Add support for Zerion integration | Mentioned By: Pranav",
"messageCount": 1619,
"userCount": 169
},
{
"channelId": "1300756641406521416",
"channelName": "ideas-feedback-rants",
"summary": "# Discord Channel Analysis: ideas-feedback-rants\n\n## 1. Summary\nThe channel contains minimal technical discussion, focusing instead on various unrelated topics. The most relevant technical conversation revolves around using the DeepSeek model with Eliza, particularly the DeepSeek-Coder-V2 model mentioned in a tweet. Users discussed its potential advantages including not requiring a GPU, possible implementation as an Android app, and its effectiveness for tool/action calling. There was confirmation that both the reasoning (r1) and chat models work well with Eliza, with the chat model being a viable alternative if JSON generation is problematic. Other topics included questions about cryptocurrency exchanges, AI-generated music modification, and various unrelated inquiries about projects and tokens.\n\n## 2. FAQ\nQ: Which model is best for image and video generation with the Instagram plugin? (asked by Daniel BNV) A: Unanswered\nQ: Was buying AI16Z tokens on Raydium the wrong way to get involved with the DAO? (asked by David_Dyor) A: Unanswered\nQ: Can the DeepSeek model be used with Eliza? (asked by Display Name) A: Yes, I have played around using it with Eliza. It does a very good job and is very cheap to run, especially for tool/action calling. (answered by Kraus)\nQ: Is it possible to edit prompted songs to remove one vocalist? (asked by Dr. Neuro) A: Remove vocal with another AI tool maybe, then upload and try the lyrics in a new prompt in SUno. (answered by boom)\n\n## 3. Help Interactions\nHelper: Kraus | Helpee: Display Name | Context: Concerns about using DeepSeek model with Eliza, particularly for JSON generation | Resolution: Kraus confirmed having successfully used the model with Eliza, noting it works well and is cheap to run, suggesting using the chat model instead of reasoning model if JSON generation is problematic.\nHelper: boom | Helpee: Dr. Neuro | Context: Wanting to remove male vocalist from AI-generated song | Resolution: Suggested using another AI tool to remove vocals, then uploading and trying new lyrics in SUno.\n\n## 4. Action Items\nFeature: Bring back LlamaCloud support | Description: Restore support for LlamaCloud | Mentioned By: Vesper\nFeature: Implement DeepSeek model with Eliza | Description: Use the DeepSeek-Coder-V2 model with Eliza as it reportedly outperforms 4o and doesn't need a GPU | Mentioned By: Display Name\nFeature: Create Android app for Eliza | Description: Develop a mobile app to run Eliza locally on phones without cloud hosting | Mentioned By: Display Name\nTechnical: Test DeepSeek model for JSON generation | Description: Verify if the DeepSeek reasoning model can properly generate JSON for Eliza | Mentioned By: Display Name",
"messageCount": 36,
"userCount": 16
},
{
"channelId": "1308149076893630555",
"channelName": "spartan_holders",
"summary": "# Analysis of spartan_holders Discord Channel\n\n## 1. Summary\nThe Discord chat segment primarily revolves around DegenSpartan AI, an autonomous trading AI. Jin, a key team member, was asked to provide updates on the project's status and future plans. Jin later shared Twitter/X posts with updates, indicating that future updates will be more autonomous. Rhota mentioned they're working on improving the trading functionality now that it's live and developing a roadmap to be shared by the end of the following week. Community members discussed tracking the AI's performance, with Birdeye and Waveform being recommended platforms. There was also discussion about the AI's trading patterns, volatility, and potential future use cases. A notable technical issue mentioned was that the DegenAI had stopped trading because it ran out of SOL (Solana).\n\n## 2. FAQ\nQ: Can you summarize the current update status of degenspartan ai and the future update schedule? (asked by NkT) A: Jin will make a post later and shared Twitter/X links with updates, noting updates will be more autonomous (answered by jin)\nQ: Where do we keep track of degenspartanai performance? (asked by Rabbidfly) A: Birdeye and Waveform are recommended platforms (answered by Noname)\nQ: Have you planned or considered turning it into a DefAI tool that everyone can use? (asked by tigerguo.) A: Unanswered\nQ: When will degenai resume trading? (asked by cool.eth) A: Seems like he's out of sol (answered by jin)\n\n## 3. Help Interactions\nHelper: Noname | Helpee: Rabbidfly | Context: Asking where to track DegenSpartanAI performance | Resolution: Suggested Birdeye and Waveform platforms, shared specific Waveform link\nHelper: rhota | Helpee: tigerguo. | Context: Confusion about future plans for DegenAI | Resolution: Explained they're working on improving trading and developing a roadmap to share soon\n\n## 4. Action Items\nTechnical: Improve the trading functionality of DegenSpartanAI | Description: Working on enhancing the live trading capabilities | Mentioned By: rhota\nDocumentation: Create and share a high-level roadmap | Description: To be shared by end of next week | Mentioned By: rhota\nTechnical: Make DegenSpartanAI updates more autonomous | Description: Implementing more autonomous update processes | Mentioned By: jin\nTechnical: Address the SOL shortage issue | Description: DegenAI stopped trading due to running out of SOL | Mentioned By: jin\nDocumentation: Make tracking DegenSpartanAI performance easier | Description: Working on making performance tracking more accessible | Mentioned By: jin",
"messageCount": 49,
"userCount": 14
},
{
"channelId": "1328592959444095038",
"channelName": "associates",
"summary": "# Discord Channel \"associates\" Analysis\n\n## 1. Summary\nThis Discord chat segment shows minimal technical discussion, focusing instead on community engagement, partnerships, and market sentiment. Members discussed potential X accounts to monitor for a newsletter, including shawmakesmagic, ai16zdao, 0xwitchy, and microstrategy. There was brief discussion about a potential BTC reserve and its impact on AI token prices, with some members debating short-term trading strategies versus holding. A member raised a concern about Collab-land bot not properly auditing wallet holdings for role verification. Community initiatives were mentioned, including a temporary tattoo machine for events in Denver and SXSW featuring the Eliza OS logo. The chat also touched on partnerships, including a mention of Nillion. Overall, the conversation was casual with limited technical depth or concrete problem-solving.\n\n## 2. FAQ\nQ: Which X accounts should we monitor for a weekly newsletter? (asked by jin) A: Suggestions included shawmakesmagic, ai16zdao, himgajira, 0xwitchy, microstrategy, and partners listed on the partner page (answered by multiple users)\nQ: Can someone check my logic here about BTC reserve impact on AI alts? (asked by kalshnikov) A: Not necessarily that bc.d goes up with a BTC reserve, especially with Trump's statement about AI and crypto. More capital inflow across the board is expected (answered by smetter)\nQ: Do we know more in detail how the new tokenomics will benefit partners? (asked by smetter) A: Number go up (answered by Smedroc - Street urchin @ ai16z)\nQ: Anyone a solana dev or know any solana devs? (asked by Alsara2k) A: I know some Solana devs and I have done a few program deployments on Solana though I'm not an expert myself (answered by elev8blyss)\n\n## 3. Help Interactions\nHelper: smetter | Helpee: kalshnikov | Context: kalshnikov asked for feedback on his trading logic regarding BTC reserve impact on AI tokens | Resolution: smetter provided alternative perspective that capital inflow would be across the board, kalshnikov decided to sell sketchy positions but keep the rest\nHelper: elev8blyss | Helpee: Alsara2k | Context: Alsara2k was looking for Solana developers | Resolution: elev8blyss offered help, mentioning they've done program deployments on Solana\nHelper: Patt | Helpee: Alsara2k | Context: Alsara2k needed Solana developers | Resolution: Patt vouched for elev8blyss as a builder worth talking to\n\n## 4. Action Items\nTechnical: Verify if Collab-land bot is properly auditing wallet holdings for role verification | Description: A member moved tokens to another wallet but retained roles in this server while losing them in another server | Mentioned By: kalshnikov\nFeature: Create a weekly newsletter monitoring key X accounts | Description: Compile updates from accounts like shawmakesmagic, ai16zdao, 0xwitchy, and microstrategy | Mentioned By: jin\nFeature: Implement temporary tattoo service at events | Description: Bring temp tattoo machine with Eliza OS logo to Denver and SXSW events | Mentioned By: Astrid\nFeature: Consider adding partners to associates role | Description: Let other coins that are partnered join the associates channel | Mentioned By: \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20",
"messageCount": 64,
"userCount": 17
},
{
"channelId": "1318770424632311930",
"channelName": "tokenomics",
"summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe discussion centers on developing tokenomics for ai16z, with multiple competing approaches being debated. The main tension is between simple, proven models versus more complex mechanisms. One approach follows the pump.fun/virtuals model with a dual pool structure and bonding curve, where tokens are paired with SOL and fees are collected. Vasily Sumanov proposed a more complex model involving staking/delegation to whitelist trusted agents, with potential slashing mechanisms for bad actors. Community members like DorianD advocated for simplicity, arguing that complex tokenomics creates barriers to adoption and that the focus should be on increasing installations rather than token mechanisms. Akin suggested a model where teams hold ai16z tokens to access premium services, positioning the launchpad as a high-quality, curated platform rather than a mass-market solution. The Block Tank concept was mentioned as a potential curation mechanism where agents could evaluate projects. The discussion also touched on technical implementation details like TrustDB for decentralized trust scoring between agents, and whether staking creates unnecessary tax complications and sell pressure.\n\n## 2. FAQ\nQ: What is the dual pool structure being discussed? (asked by bong49) A: It's similar to virtuals/pump.fun where tokens are paired with SOL in liquidity pools, with fees collected from transactions (answered by BigChungus)\nQ: How would the trust mechanism for agents work in Vasily's proposal? (asked by bong49) A: Teams would stake ai16z tokens as skin in the game and could get slashed if they act dishonestly, with token holders able to delegate their stake to vouch for agents (answered by Vasily Sumanov)\nQ: Would staking create tax implications? (asked by yikesawjeez) A: Yes, staking creates income that's taxed at higher rates than capital gains, potentially creating sell pressure as people sell to cover tax bills (answered by DorianD)\nQ: How many agents could be manually assessed per month? (asked by jin) A: Approximately 10-20 agents per month could be properly assessed (answered by Vasily Sumanov)\nQ: What is Block Tank? (asked by Akin) A: A system where users submit projects that generate episodes for AI investors to evaluate and score (answered by jin)\nQ: How does TrustDB work? (asked by Vasily Sumanov) A: It's a system where agents assign trust scores to other agents/humans in a decentralized way (answered by DorianD)\nQ: How should the ai16z launchpad be positioned? (asked by Akin) A: As a premium \"Four Seasons not Motel 6\" with fewer, higher-quality launches rather than mass market (answered by Akin)\n\n## 3. Help Interactions\nHelper: DorianD | Helpee: Vasily Sumanov | Context: Understanding TrustDB technology | Resolution: DorianD provided documentation link and explained how agents assign trust scores to each other\nHelper: jin | Helpee: Vasily Sumanov | Context: Needed access to tokenomics channel | Resolution: Jin granted appropriate role permissions\nHelper: yardy | Helpee: Community | Context: Bringing in token engineering expertise | Resolution: Introduced Vasily Sumanov who created a detailed tokenomics proposal\nHelper: witch | Helpee: Community | Context: Explaining why Bancor comparison is irrelevant | Resolution: Provided clear distinctions between Bancor's issues and ai16z's situation\nHelper: bong49 | Helpee: Community | Context: Sharing perspective on token delegation market | Resolution: Explained how a Curve-like gauge-bribe mechanism could work for agent staking\n\n## 4. Action Items\nType: Technical | Description: Implement a simple submission fee for Block Tank to reduce spam | Mentioned By: jin\nType: Technical | Description: Create a mechanism for token holders to delegate stake to vouch for agents | Mentioned By: Vasily Sumanov\nType: Technical | Description: Develop a dual pool structure similar to virtuals/pump.fun | Mentioned By: BigChungus\nType: Technical | Description: Integrate TrustDB with tokenomics for decentralized agent trust scoring | Mentioned By: DorianD\nType: Documentation | Description: Create a 2-3 page whitepaper explaining tokenomics simply | Mentioned By: Akin\nType: Documentation | Description: Create visual explanations of each tokenomics mechanism | Mentioned By: jin\nType: Documentation | Description: Document the purpose of proposed value engines | Mentioned By: yikesawjeez\nType: Feature | Description: Implement a system for tracking how long teams hold ai16z tokens | Mentioned By: Akin\nType: Feature | Description: Create a leaderboard for staked agents | Mentioned By: yikesawjeez\nType: Feature | Description: Develop a premium service tier for teams that hold ai16z tokens | Mentioned By: Akin",
"messageCount": 348,
"userCount": 11
},
{
"channelId": "1301363808421543988",
"channelName": "\ud83e\udd47-partners",
"summary": "# Analysis of \ud83e\udd47-partners Discord Chat\n\n## 1. Summary\nThe chat primarily focused on market conditions affecting AI16Z and related tokens, with discussions about whale selling activity and price movements. Key technical topics included ElizaOS development, with mentions of v2 progress, plugin system refactoring, and memory management for AI agents. Jin mentioned that the dev branch has improved Eliza installation to a 2-second process. There were discussions about integrating Deepseek models with ElizaOS, which Jin noted could be done with a single line of code change through OpenRouter. The team is working on tokenomics slides and presentations, with each covering different strategies. Partners expressed concerns about development timelines and communication regarding features like the launchpad and DegenAI trading functionality. Jin also mentioned an AI-led venture capital concept combining game show elements with investment decisions, designed to scale and decentralize the project vetting process.\n\n## 2. FAQ\nQ: How far away is ElizaOS v2? (asked by DorianD) A: Jin advised to \"stick to v1\" as it will be \"backwards compatible\" (answered by jin)\nQ: Will the 10% donations from projects using ElizaOS just get put into LPs or will it get traded? (asked by DorianD) A: Unanswered\nQ: Is Deepseek integrated yet with ElizaOS as an option? (asked by litn) A: \"Technically since openrouter supports it we can change to deepseek in 1 line of code\" (answered by jin)\nQ: How does the AI-led VC/game show increase demand/buy pressure for AI16Z? (asked by HoneyBadger) A: Jin mentioned he explains the value proposition in docs/slides (answered by jin)\nQ: Why is Shaw no longer active on Discord? (asked by HoneyBadger) A: Shaw is sick with the flu and traveling (answered by DannyNOR NoFapArc and jin)\n\n## 3. Help Interactions\nHelper: jin | Helpee: DorianD | Context: Question about memory management for AI agents | Resolution: Jin explained that \"passing around memories gunna be a thing\" and that he's prepared a section of docs for this\nHelper: avirtualfuture | Helpee: DorianD | Context: Concerns about performance bottlenecks with multiple processes | Resolution: Explained that \"llm token generation is the bottleneck\" and the system would need to be \"really bad\" to be bottlenecked elsewhere\nHelper: ElonMoney | Helpee: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f | Context: Question about upcoming tokenomics model | Resolution: Shared key points including staking, AI16Z as primary ecosystem token, and launchpad revenue being used for buybacks\n\n## 4. Action Items\nType: Technical | Description: Integrate Deepseek model with DegenAI for testing | Mentioned By: jin\nType: Technical | Description: Complete memory management system for passing memories between AI instances | Mentioned By: jin\nType: Technical | Description: Finish refactoring plugin system in v2 | Mentioned By: jin\nType: Documentation | Description: Complete tokenomics slides and presentations | Mentioned By: jin\nType: Documentation | Description: Create documentation for AI agent memory management | Mentioned By: jin\nType: Feature | Description: Implement AI-led venture capital/game show concept (\"Block Tank\") | Mentioned By: jin\nType: Feature | Description: Launch agent marketplace/launchpad | Mentioned By: Dippuccino\nType: Feature | Description: Implement staking for AI16Z token | Mentioned By: ElonMoney\nType: Feature | Description: Set up token buybacks using launchpad revenue | Mentioned By: ElonMoney",
"messageCount": 689,
"userCount": 57
},
{
"channelId": "1313222089271939102",
"channelName": "3d-ai-tv",
"summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe channel discussions focus on developing a TV show simulation with 3D elements and AI integration. SM Sith Lord shared implementation details about handling the \"tv\" actor to prevent TTS from reading URLs aloud. Boom worked on camera variations for the show, creating multiple camera types including jib cam, pan and zoom pivot cam, and B-roll options with percentage-based switching logic. SM Sith Lord provided a pre-generated Block Tank episode configuration with 6 actors (jin, peepo, spartan, elizahost, aimarc, aishaw) and 4 locations for testing without making AI calls. The setup includes 4 judges, 1 host, and 1-2 pitchers. There were discussions about scene design elements, with boom removing the floor to better showcase the Earth backdrop and suggesting additional elements like boosters, panels, wires, and LED desks. Community members shared relevant AI tools including Hunyuan3D-2, Go-with-the-Flow, and FilmAgent. There were concerns about the news aggregator not updating, with boom noting the summary.json still showing the 21st.\n\n## 2. FAQ\nQ: What did SM Sith Lord do in their handler for the \"tv\" actor? (implied from SM Sith Lord's explanation) A: They check which actor is speaking early in event handling, and if it's \"tv\", it loads media and cancels normal handling to prevent TTS from reading URLs aloud. (answered by SM Sith Lord)\nQ: Do I just need custom config to do the blocktank tests or is that a whole new runner? (asked by boom) A: It's mostly just the show-config.json, with different HTML & JSON files to avoid overwriting different show's saves. (answered by SM Sith Lord)\nQ: Is it possible to pass an AVI created in Blender into a Huggingface engine to make it a real cinematic trailer? (asked by D. Ratta) A: Unanswered\nQ: Is there a way I can run the summary manually if needed? (asked by boom) A: Unanswered\n\n## 3. Help Interactions\nHelper: SM Sith Lord | Helpee: boom | Context: Needed Block Tank configuration for testing | Resolution: Provided a zip file with pre-generated Block Tank episode setup to replay using browser-based TTS without making AI calls\nHelper: SM Sith Lord | Helpee: boom | Context: Understanding the actor setup for Block Tank | Resolution: Explained the configuration includes 6 actors and 4 locations, with 4 judges, 1 host, and 1-2 pitchers\nHelper: yikesawjeez | Helpee: Channel members | Context: Sharing AI tools for 3D/video generation | Resolution: Shared links to Hunyuan3D-2, Go-with-the-Flow, and FilmAgent repositories\n\n## 4. Action Items\nTechnical: Implement additional camera variations for the show | Description: Add more camera types including jib cam and B-roll options with percentage-based switching | Mentioned By: boom\nTechnical: Fix or update the news aggregator | Description: The summary.json is not updating beyond the 21st | Mentioned By: boom\nFeature: Add visual elements to the set | Description: Add boosters, panels, wires, LED desk, and improve lighting on black areas | Mentioned By: boom\nTechnical: Adjust lighting for black areas | Description: Make pure black areas take light from the cubemap to improve visibility | Mentioned By: SM Sith Lord",
"messageCount": 59,
"userCount": 7
}
]
}
},
"ai_news_elizaos_daily_discord_md_2025-01-23": {
"filename": "2025-01-23.md",
"content": "# elizaOS Discord - 2025-01-23\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **ElizaOS v2 Progress**: Jin advised users to \"stick to v1\" for now as v2 will be backwards compatible. The dev team is refactoring the plugin system and improving memory management for AI agents.\n- **Installation Improvements**: The dev branch has reduced Eliza installation to a 2-second process.\n- **Model Integration**: Discussions about integrating Deepseek models with ElizaOS, which Jin noted could be done with a single line of code change through OpenRouter.\n- **RAG Implementation**: Several users discussed implementing Retrieval Augmented Generation for Eliza, with kAI wilder explaining the knowledgeManager system.\n\n### Technical Issues & Solutions\n- **Vector Dimension Mismatch**: Multiple users encountered \"Vector dimension mismatch\" errors. The solution is to set USE_OPENAI_EMBEDDING=TRUE in the .env file.\n- **Plugin Configuration**: Users struggled with plugin integration, particularly the dexscreener plugin. The solution involved removing API key checks in index.ts files.\n- **Twitter Integration**: Several discussions about configuring Twitter agents, including how to disable retweets and make agents respond to replies.\n- **Node.js Version**: Users reported success with Node v23.3.0 for resolving various errors.\n\n### DegenSpartanAI & Trading\n- **Trading Status**: DegenSpartanAI temporarily stopped trading because it ran out of SOL.\n- **Performance Tracking**: Community members recommended Birdeye and Waveform platforms for tracking DegenSpartanAI's trading performance.\n- **Development Roadmap**: Rhota mentioned they're working on improving trading functionality and developing a roadmap to be shared by the end of the following week.\n\n### Tokenomics Discussions\n- **Competing Approaches**: Debate between simple models versus complex mechanisms:\n - One approach follows pump.fun/virtuals model with dual pool structure and bonding curve\n - Vasily Sumanov proposed staking/delegation to whitelist trusted agents with slashing mechanisms\n - DorianD advocated for simplicity to avoid barriers to adoption\n - Akin suggested positioning ai16z as a premium service token\n- **Block Tank Concept**: An AI-led venture capital concept combining game show elements with investment decisions, designed to scale and decentralize project vetting.\n\n### 3D AI TV Show Development\n- **Camera System**: Boom worked on camera variations including jib cam, pan and zoom pivot cam, and B-roll options with percentage-based switching logic.\n- **Block Tank Configuration**: SM Sith Lord provided a pre-generated Block Tank episode setup with 6 actors and 4 locations for testing without making AI calls.\n- **Visual Elements**: Discussions about scene design elements, including removing the floor to showcase the Earth backdrop and adding boosters, panels, wires, and LED desks.\n\n## Key Questions & Answers\n\n**Q: How do I fix \"Vector dimension mismatch\" error?** \nA: Set USE_OPENAI_EMBEDDING=TRUE in .env file (answered by boja)\n\n**Q: How do I fix the dexscreener plugin not working?** \nA: Remove the API key check in index.ts and directly add dexScreenerPlugin (answered by bifkn)\n\n**Q: How do I make my agent respond to replies on Twitter?** \nA: Check ACTION_INTERVAL, ENABLE_ACTION_PROCESSING, MAX_ACTIONS_PROCESSING, ACTION_TIMELINE_TYPE settings (answered by tcm390)\n\n**Q: How do I disable Twitter retweets?** \nA: Remove retweet from the actions portion in the code (answered by paxva)\n\n**Q: Is there a way for the agent to memorize tweets without actually responding to them?** \nA: Agents can observe without interacting, just follow the profile (answered by BOSSU)\n\n**Q: How far away is ElizaOS v2?** \nA: Jin advised to \"stick to v1\" as it will be \"backwards compatible\" (answered by jin)\n\n**Q: Is Deepseek integrated yet with ElizaOS as an option?** \nA: \"Technically since openrouter supports it we can change to deepseek in 1 line of code\" (answered by jin)\n\n**Q: Where do we keep track of degenspartanai performance?** \nA: Birdeye and Waveform are recommended platforms (answered by Noname)\n\n**Q: What LLMs have you been able to integrate with Eliza?** \nA: Check coders channel for LLM integration information (answered by BOSSU)\n\n**Q: Does Eliza have any dependency for GPU?** \nA: For basic Eliza you just need CPU, but GPU makes things faster (answered by BOSSU)\n\n## Community Help & Collaboration\n\n### Technical Support\n- **bifkn helped kobra** fix the dexscreener plugin by identifying that it was checking for an API key that doesn't exist; solution was to remove the check in index.ts.\n- **EcchiPen helped Vesper** set up a Telegram bot for groups by providing step-by-step guidance and a video tutorial.\n- **tcm390 helped Silent Quasar** with action callback issues by sharing example code showing how to implement callback function in actions.\n- **robotlovecoffee helped j.** with persistent Eliza setup errors by creating and sharing a detailed PDF guide.\n- **kAI wilder helped Qu\u0103ng** load documents into knowledge base by creating and sharing a document explaining the knowledgeManager system.\n- **Kraus helped Display Name** with concerns about using DeepSeek model with Eliza, confirming successful implementation and suggesting using the chat model instead of reasoning model if JSON generation is problematic.\n\n### Community Contributions\n- **jin tipped Grafixart 137.80 ai16z (\u2248$120)** for artwork contributions, specifically creating stickers.\n- **SM Sith Lord provided boom** with a pre-generated Block Tank episode configuration for testing without making AI calls.\n- **yikesawjeez shared AI tools** for 3D/video generation, including links to Hunyuan3D-2, Go-with-the-Flow, and FilmAgent repositories.\n\n## Action Items\n\n### Technical\n- Fix vector dimension mismatch in embedding endpoint configuration (Mentioned by j.)\n- Implement RAG (Retrieval Augmented Generation) for Eliza (Mentioned by Qu\u0103ng)\n- Create configuration for disabling retweet feature on Twitter agents (Mentioned by nearfriend)\n- Develop functionality for agents to memorize tweets without responding (Mentioned by Mahesh)\n- Fix dexscreener plugin to work without requiring an API key check (Mentioned by bifkn)\n- Fix embedding dimension mismatch issues in SQLite adapter (Mentioned by boja)\n- Improve Twitter client to handle replies to replies (Mentioned by ant)\n- Fix trustDB schema and SQL statements (Mentioned by Jesse | Telos)\n- Fix RAG functionality in develop branch (Mentioned by kAI wilder)\n- Verify if Collab-land bot is properly auditing wallet holdings for role verification (Mentioned by kalshnikov)\n- Integrate Deepseek model with DegenAI for testing (Mentioned by jin)\n- Complete memory management system for passing memories between AI instances (Mentioned by jin)\n- Finish refactoring plugin system in v2 (Mentioned by jin)\n- Implement a simple submission fee for Block Tank to reduce spam (Mentioned by jin)\n- Create a mechanism for token holders to delegate stake to vouch for agents (Mentioned by Vasily Sumanov)\n- Develop a dual pool structure similar to virtuals/pump.fun (Mentioned by BigChungus)\n- Integrate TrustDB with tokenomics for decentralized agent trust scoring (Mentioned by DorianD)\n- Implement additional camera variations for the show (Mentioned by boom)\n- Fix or update the news aggregator (Mentioned by boom)\n- Adjust lighting for black areas (Mentioned by SM Sith Lord)\n- Address the SOL shortage issue for DegenAI (Mentioned by jin)\n\n### Documentation\n- Create better documentation for plugin development workflow (Mentioned by Saburo)\n- Document how to configure Telegram bot to only respond to specific keywords (Mentioned by Meciah)\n- Create documentation for character file secrets configuration (Mentioned by Deeznutz)\n- Create a 2-3 page whitepaper explaining tokenomics simply (Mentioned by Akin)\n- Create visual explanations of each tokenomics mechanism (Mentioned by jin)\n- Document the purpose of proposed value engines (Mentioned by yikesawjeez)\n- Complete tokenomics slides and presentations (Mentioned by jin)\n- Create documentation for AI agent memory management (Mentioned by jin)\n- Create and share a high-level roadmap (Mentioned by rhota)\n- Make tracking DegenSpartanAI performance easier (Mentioned by jin)\n- Provide documentation on ElizaOS v2 (Mentioned by Leo Young)\n- Create guide for setting up Eliza with cloud backends like Supabase or Firebase (Mentioned by Magnacor)\n\n### Feature\n- Add ability to disable original tweets and only enable replies (Mentioned by RoomTemp IQ)\n- Create a CLI installer that selects which adapters/plugins to include (Mentioned by gel)\n- Add support for loading large documents into knowledge base (Mentioned by kAI wilder)\n- Add support for Zerion integration (Mentioned by Pranav)\n- Build plugin for elizaOS (Mentioned by Pranav)\n- Create AI doctor with avatar featuring real-time voice chat and body sync (Mentioned by Parzival)\n- Integrate Lit Protocol Agent Wallet for decentralized key management (Mentioned by Rick)\n- Create more DegenAI-themed stickers (Mentioned by jin)\n- Create a weekly newsletter monitoring key X accounts (Mentioned by jin)\n- Implement temporary tattoo service at events (Mentioned by Astrid)\n- Consider adding partners to associates role (Mentioned by \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20)\n- Implement a system for tracking how long teams hold ai16z tokens (Mentioned by Akin)\n- Create a leaderboard for staked agents (Mentioned by yikesawjeez)\n- Develop a premium service tier for teams that hold ai16z tokens (Mentioned by Akin)\n- Implement AI-led venture capital/game show concept (\"Block Tank\") (Mentioned by jin)\n- Launch agent marketplace/launchpad (Mentioned by Dippuccino)\n- Implement staking for AI16Z token (Mentioned by ElonMoney)\n- Set up token buybacks using launchpad revenue (Mentioned by ElonMoney)\n- Add visual elements to the set (boosters, panels, wires, LED desk) (Mentioned by boom)\n- Bring back LlamaCloud support (Mentioned by Vesper)\n- Implement DeepSeek model with Eliza (Mentioned by Display Name)\n- Create Android app for Eliza (Mentioned by Display Name)"
},
"github_summaries_daily_2025-01-24": {
"filename": "2025-01-24.md",
"content": "# ElizaOS Daily Update (Jan 24, 2025)\n\n## OVERVIEW \nOn January 24, 2025, significant progress was made in enhancing the ElizaOS framework, with multiple new features and bug fixes implemented. Key developments included the addition of several plugins and improvements to existing functionalities, particularly in the TON and Discord bot areas. The team also addressed various issues, contributing to a more robust and user-friendly experience.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Plugin Enhancements\n- Added a new **TON plugin** with debug scripts and fixed transfer issues ([#2744](https://github.com/elizaos/eliza/pull/2744)).\n- Introduced a **Sei plugin** to streamline agent development ([#2720](https://github.com/elizaos/eliza/pull/2720)).\n- Implemented a **Imgflip plugin** for meme generation using the imgflip.com API ([#2711](https://github.com/elizaos/eliza/pull/2711)).\n- Added a **plugin-holdstation** for swap functionalities ([#2741](https://github.com/elizaos/eliza/pull/2741)).\n- Launched a **plugin-ethstorage** to assist users with Ethereum storage ([#2737](https://github.com/elizaos/eliza/pull/2737)).\n\n### Bug Fixes and Improvements\n- Resolved a **build issue** with the TON plugin ([#2757](https://github.com/elizaos/eliza/pull/2757)).\n- Fixed a **429 error** encountered when sending transactions with the TON plugin ([#2755](https://github.com/elizaos/eliza/pull/2755)).\n- Addressed a **version conflict** with the @ai-sdk/provider, ensuring compatibility ([#2714](https://github.com/elizaos/eliza/pull/2714)).\n- Improved **Twitter parsing** functionalities ([#2730](https://github.com/elizaos/eliza/pull/2730)).\n\n### Testing and Documentation\n- Added tests for the **client-eliza-home** package to enhance coverage ([#2719](https://github.com/elizaos/eliza/pull/2719)).\n- Updated the **Allora Plugin** to use the latest SDK version ([#2707](https://github.com/elizaos/eliza/pull/2707)).\n- Enhanced documentation by adding **hyperliquid environment variables** to the example file ([#2736](https://github.com/elizaos/eliza/pull/2736)).\n\n## CLOSED ISSUES\n\n### Resolved Technical Issues\n- Closed the issue regarding the **ECONNRESET error** faced by users trying to log in to Twitter ([#2738](https://github.com/elizaos/eliza/issues/2738)).\n- Addressed the **test coverage** gaps in the client-eliza-home package ([#2718](https://github.com/elizaos/eliza/issues/2718)).\n\n## NEW ISSUES\n\n### Emerging Challenges\n- Users reported a **read ECONNRESET issue** when attempting to use the Twitter agent, indicating potential connectivity problems ([#2739](https://github.com/elizaos/eliza/issues/2739)).\n- A bug was identified where the **echochambers plugin** does not exist on the npm registry, causing installation issues ([#2756](https://github.com/elizaos/eliza/issues/2756)).\n- Requests for new database adapters for **Airtable**, **Google Sheets**, and **Notion** were raised, highlighting the need for expanded database integration ([#2760](https://github.com/elizaos/eliza/issues/2760), [#2761](https://github.com/elizaos/eliza/issues/2761), [#2759](https://github.com/elizaos/eliza/issues/2759))."
},
"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-01": "{\n \"interval\": {\n \"intervalStart\": \"2025-01-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-02-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-01-01 to 2025-02-01, elizaos/eliza had 1039 new PRs (735 merged), 401 new issues, and 694 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs6l7_A4\",\n \"title\": \"Missing Module: '@anush008/tokenizers-linux-arm64-gnu'\",\n \"author\": \"morning3tar\",\n \"number\": 2242,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-13T13:29:04Z\",\n \"closedAt\": \"2025-03-08T01:09:54Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 30\n },\n {\n \"id\": \"I_kwDOMT5cIs6lSxzf\",\n \"title\": \"Error: Could not find wrtc binary on any of the paths when running pnpm start\",\n \"author\": \"arvin-crypto\",\n \"number\": 1965,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-07T15:47:26Z\",\n \"closedAt\": \"2025-03-02T01:55:50Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 27\n },\n {\n \"id\": \"I_kwDOMT5cIs6mwy61\",\n \"title\": \"@elizaos/agent@0.1.9-alpha.1 start: `node --loader ts-node/esm src/index.ts \\\"--isRoot\\\" \\\"--characters=characters/eternalai.character.json\\\"`\",\n \"author\": \"illink7\",\n \"number\": 2530,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-19T20:13:23Z\",\n \"closedAt\": \"2025-03-08T01:17:17Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 22\n },\n {\n \"id\": \"I_kwDOMT5cIs6m5hCt\",\n \"title\": \"Bot is only responding to target users and ignoring all other mentions on twitter\",\n \"author\": \"Xayaan\",\n \"number\": 2563,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-20T18:46:01Z\",\n \"closedAt\": \"2025-03-08T01:17:17Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 21\n },\n {\n \"id\": \"I_kwDOMT5cIs6lwYFX\",\n \"title\": \"\u2009ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL\u2009\",\n \"author\": \"TobiGoldD\",\n \"number\": 2127,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-10T19:14:51Z\",\n \"closedAt\": \"2025-03-02T01:56:01Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 20\n }\n ],\n \"topPRs\": [\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_kwDOMT5cIs6JBWtl\",\n \"title\": \"Add Access Token Management\",\n \"author\": \"elpulpo0\",\n \"number\": 2808,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-26T22:16:38Z\",\n \"mergedAt\": null,\n \"additions\": 224271,\n \"deletions\": 12973\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HcIgk\",\n \"title\": \"chore: Prep v0.1.8 (dev => main)\",\n \"author\": \"odilitime\",\n \"number\": 2171,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-11T23:36:42Z\",\n \"mergedAt\": \"2025-01-12T07:32:53Z\",\n \"additions\": 100844,\n \"deletions\": 46015\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HLoVX\",\n \"title\": \"Fix/resolve conflicts\",\n \"author\": \"yueliao11\",\n \"number\": 2060,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-09T09:58:41Z\",\n \"mergedAt\": null,\n \"additions\": 87145,\n \"deletions\": 43714\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HJPhr\",\n \"title\": \"Development\",\n \"author\": \"juansebsol\",\n \"number\": 2041,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-09T01:24:35Z\",\n \"mergedAt\": null,\n \"additions\": 81946,\n \"deletions\": 43391\n }\n ],\n \"codeChanges\": {\n \"additions\": 450243,\n \"deletions\": 138188,\n \"files\": 2487,\n \"commitCount\": 5528\n },\n \"completedItems\": [\n {\n \"title\": \"chore: support more debians distros\",\n \"prNumber\": 1875,\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\\nAdd more playwright support for various debian distros.\\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 c\"\n },\n {\n \"title\": \"fix: Fix postinstall script\",\n \"prNumber\": 1872,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nFixes develop's install-phase (broken in #1834 )\\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\"\n },\n {\n \"title\": \"docs: Add DAO donation ask & dev discord\",\n \"prNumber\": 1867,\n \"type\": \"feature\",\n \"body\": \"Self explanatory I hope\"\n },\n {\n \"title\": \"feat: Add Stargaze plugin\",\n \"prNumber\": 1861,\n \"type\": \"feature\",\n \"body\": \"This plugins allows Eliza to get NFT information from the main NFT marketplace in Cosmos (Stargaze). \\r\\n\\r\\n![\\\"image\\\"](\\\"https://github.com/user-attachments/assets/03b9b7fe-85fe-407f-a0ff-dbeeea73f1e1\\\")
\\r\\n![]()
\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1838\\r\\n\\r\\n# Risks\\r\\n\\r\\nlow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR \"\n },\n {\n \"title\": \"test: adding more tests for goals,memory and provider. Fixing generation.test.ts\",\n \"prNumber\": 1840,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/186\\r\\nhttps://github.com/elizaOS/eliza/issues/183\\r\\nhttps://github.\"\n },\n {\n \"title\": \"correct faq docs link in both contribution md files\",\n \"prNumber\": 1839,\n \"type\": \"other\",\n \"body\": \"This pull request includes a small change to the `CONTRIBUTING.md` and `docs/docs/contributing.md` files. The change corrects the link to the FAQ page to point to the correct location.\\r\\n\\r\\n* [`CONTRIBUTING.md`](diffhunk://#diff-eca12c0a30e25\"\n },\n {\n \"title\": \"chore: update bootstrap plugin export\",\n \"prNumber\": 1836,\n \"type\": \"other\",\n \"body\": \"Relates to:\\r\\nPlugin export collisions in character files\\r\\n\\r\\nRisks\\r\\nLow - This is a minor bug fix that ensures proper module exports\\r\\n\\r\\nBackground\\r\\nWhat does this PR do?\\r\\nEnsures the bootstrap plugin has a proper default export at the bottom\"\n },\n {\n \"title\": \"Update README_KOR.md\",\n \"prNumber\": 1835,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\nModified the previous sentence to align with the meaning in Korean.\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1725\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/917\\r\\nhttps://github.com/eli\"\n },\n {\n \"title\": \"Update .env.example\",\n \"prNumber\": 1829,\n \"type\": \"other\",\n \"body\": \"Grok / xAI API Key are the same. Same endpoint. It's confusing to split it into Grok and xAI separately. If someone wants to use Grok, they will enter their xAI API key at the GROK_API_KEY, and it works.\"\n },\n {\n \"title\": \"fix(solana token provider): await cached data\",\n \"prNumber\": 1828,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nExecuting trades\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/1483/\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nMaintains original document structure and layout\\r\\nPreserves all formatting, emojis, and technical terms\\r\\n\"\n },\n {\n \"title\": \"docs: update faq.md\",\n \"prNumber\": 1746,\n \"type\": \"docs\",\n \"body\": \"Removed mentions of some items.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNo issue for this pr\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n#1694\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNo specific issue or ticket.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nFix issue where an agent on twitter tries to use ImageDescriptionService to get the description of a picture from a twitter \"\n },\n {\n \"title\": \"fix: 1634 fix image description service\",\n \"prNumber\": 1667,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n[(https://github.com/elizaOS/eliza/issues/1643 ]\\r\\n)\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nGenerating image\"\n },\n {\n \"title\": \"fix: Update Supabase schema.sql\",\n \"prNumber\": 1660,\n \"type\": \"bugfix\",\n \"body\": \"There is an extra semicolon that causes a syntax error when trying to upload the schema to Supabase.\\r\\n\\r\\n(ie. by using the SQL editor in the GUI, it fails due to this syntax error)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nFixes Supa\"\n },\n {\n \"title\": \"fix: Fix bug in plugin-bootstrap/src/evaluators/facts.ts\",\n \"prNumber\": 1648,\n \"type\": \"bugfix\",\n \"body\": \"{{user1}} should be {{user2}} :\\r\\n\\r\\n-------\\r\\nin factEvaluator, in the examples template,\\r\\n\\r\\n{{user1}} should be {{user2}} instead\\r\\n\\r\\n {\\r\\n user: \\\"{{user1}}\\\",\\r\\n content: { text: \\\"Which city?\"\n },\n {\n \"title\": \"Added Hungarian README\",\n \"prNumber\": 1645,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\nzero \\r\\n\\r\\n## What does this PR do?\\r\\nAdd Hungarian README\\r\\n\\r\\n## Discord username\\r\\nmhoused\\r\\n\"\n },\n {\n \"title\": \"fix: lockfile wasn't updated after dependency + bring viem to root level package.json\",\n \"prNumber\": 1642,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to:\\r\\n\\r\\nTrunk being broken\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This change updates the `pnpm-lock.yaml` file, which could affect dependency resolutions. Potential risks include:\\r\\n\\r\\n- **Dependency Resolution Changes:** Updates might lead to differen\"\n },\n {\n \"title\": \"chore: update viem dependency version in plugin-evm and plugin-goat\",\n \"prNumber\": 1637,\n \"type\": \"other\",\n \"body\": \"# Relates to:\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1635\\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\\nupdate the version of viem to 2.21.58 in plugin-evm and plugin-goat.\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nUpdate\"\n },\n {\n \"title\": \"Add README_AR.md\",\n \"prNumber\": 1634,\n \"type\": \"feature\",\n \"body\": \"Add Arabic language for readme.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nLow - This change affects the Docker container configuration. It may require updates to documentation and\"\n },\n {\n \"title\": \"fix: Support for Non-OpenAI Models in Token Trimming\",\n \"prNumber\": 1605,\n \"type\": \"bugfix\",\n \"body\": \"related: \\r\\nhttps://github.com/elizaOS/eliza/issues/1439\\r\\nhttps://github.com/elizaOS/eliza/issues/1565\\r\\n\\r\\nneed to be tested: https://github.com/elizaOS/eliza/issues/1439#issuecomment-2566405036\"\n },\n {\n \"title\": \"fix: activate web-search plugin in agents/\",\n \"prNumber\": 1577,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n- Issues reported by using of crashes due to this error `Error in trust score provider: Cannot read prope\"\n },\n {\n \"title\": \"feat: use custom conditions for live monorepo types\",\n \"prNumber\": 1365,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nCloses: #1363\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nN/A\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\"\n },\n {\n \"title\": \"Feat/genlayer plugin\",\n \"prNumber\": 975,\n \"type\": \"feature\",\n \"body\": \"This is my first time contributing to this project. I've based my code on the docs, but mostly copying other plugins\\r\\n\\r\\nPlease let me know anything that can be improved :)\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nDTS-error-mismatch-LanguageModelV1-in-ai-sdk-m\"\n },\n {\n \"title\": \"chore(plugin-coinbase): Update tokenContract.ts\",\n \"prNumber\": 2781,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nSometimes an LLM like llama-70b might not return a valid JSON format and this can cause random errors tha\"\n },\n {\n \"title\": \"feat: added Ankr plugin\",\n \"prNumber\": 2773,\n \"type\": \"feature\",\n \"body\": \"# Ankr Plugin for Eliza AI Flow\\r\\n\\r\\n \\r\\nAnkr APIs as Data & Execution Layer:\\r\\n\\r\\nAgents use Ankr\u2019s Multi-Chain RPC to monitor real-time asset prices, liq\"\n },\n {\n \"title\": \"feat: Add Amazon Bedrock as LLM provider\",\n \"prNumber\": 2769,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2753\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow risk: the changed code should only impact a runtime when Amazon Bedrock is used \"\n },\n {\n \"title\": \"feat: create /.turbo/config.json\",\n \"prNumber\": 2768,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nremote cache\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n429 error when running TON plugin to sending a TX.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n#2742\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**: The change introduces a restriction mechanism for the bot's responses, which only applies if `allowedChannelIds` is defined in the configuration. Existing behavi\"\n },\n {\n \"title\": \"feat(plugin-holdstation): add plugin holdstation swap\",\n \"prNumber\": 2741,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo specific issue or ticket is linked to this PR.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nEnv variables, \\r\\n\\r\\n# Risks\\r\\n\\r\\nlow\\r\\n\\r\\n# Background\\r\\n\\r\\nPretty simple update, just adding to `.env.example\"\n },\n {\n \"title\": \"feat: minimal workflow to resolve ephemeral check\",\n \"prNumber\": 2735,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nmerge queue\\r\\n\\r\\n\\r\\n## What does this PR do?\\r\\nCurrent intended path links.\\r\\n## What kind of change is this?\\r\\nDocumentation links.\\r\\n\\r\\n\\r\\n# Relates to\\r\\nAdding a dedicated Sei plugin that streamlines the development experience for creating agents that can in\"\n },\n {\n \"title\": \"client-eliza-home: test config and test coverage\",\n \"prNumber\": 2719,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2718\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNew feature addition.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nLit Protocol Integration for ElizaOS\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nCore Mina blockchain plugin for Eliza OS that provides essential services and actions for token operati\"\n },\n {\n \"title\": \"feat: Hyperbolic-plugin \",\n \"prNumber\": 2701,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n\\r\\n\\r\\n# Hyperbolic Plugin for ElizaOS\\r\\n\\r\\n## Overview\\r\\nThis PR introduces a new plugin for managing GPU instances on the H\"\n },\n {\n \"title\": \"Mostly aesthetic changes, fixed some wonky bullets and numbered lists.\",\n \"prNumber\": 2698,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nDocumentation\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Provide aesthetic tweaks (some wonky bullets and structure)\\r\\n- Add some minor clarifications\\r\\n- Update for newer characters\\r\\n\\r\\n## What kind of change is this?\\r\"\n },\n {\n \"title\": \"chore: fix types syntax issue\",\n \"prNumber\": 2694,\n \"type\": \"bugfix\",\n \"body\": \"fixes missing `};` before simsai profile inteface\"\n },\n {\n \"title\": \"feat(new-plugin): Eliza OmniFlix Plugin\",\n \"prNumber\": 2693,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nOmniFlix Network Integration Plugin for Eliza AI Agent\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2206\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nA plugin that integrates BitMind's API into ElizaOS agents, enabling access to AI services and digital \"\n },\n {\n \"title\": \"feat(new-plugin): suno music generation \",\n \"prNumber\": 2679,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-suno\\r\\n\\r\\nA Suno AI music generation plugin for ElizaOS that enables AI-powered music creation and audio manipulation.\\r\\n\\r\\n## Overview\\r\\n\\r\\nThe Suno plugin integrates Suno AI's powerful music generation capabilities into ElizaO\"\n },\n {\n \"title\": \"feat(new-plugin): eliza samsung smarthings plugin\",\n \"prNumber\": 2678,\n \"type\": \"feature\",\n \"body\": \"# Client-Eliza-Home Functionality Overview\\r\\n\\r\\n## Core Purpose\\r\\nThe client-eliza-home package serves as a bridge between ElizaOS and SmartThings-enabled smart home devices, enabling natural language control and automation of home devices.\\r\\n\\r\"\n },\n {\n \"title\": \"Revert \\\"feat(new-plugin): suno Eliza plugin\\\"\",\n \"prNumber\": 2673,\n \"type\": \"other\",\n \"body\": \"Reverts elizaOS/Eliza#2656\\r\\n\\r\\nPlugin not ready, implements old plugin interface etc\"\n },\n {\n \"title\": \"feat: Implement runProcess function in test library\",\n \"prNumber\": 2672,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nImproving test utilities functionality\\r\\n\\r\\n# Risks\\r\\nLow - This is a test utility function implementation that:\\r\\n- Only affects test code, not production code\\r\\n- Uses standard Node.js APIs (spawn)\\r\\n- Has proper error handling\\r\\n-\"\n },\n {\n \"title\": \"fix debug targets to show elizalogger debug messages\",\n \"prNumber\": 2670,\n \"type\": \"bugfix\",\n \"body\": \"fix for #2667 \\r\\nJust fixes the two debug targets in the package.json to include `DEFAULT_LOG_LEVEL=debug`\"\n },\n {\n \"title\": \"chore(spelling-fixes): docs\",\n \"prNumber\": 2669,\n \"type\": \"bugfix\",\n \"body\": \"Hello\\r\\nI fixed several spelling issue.\\r\\nBr, Elias.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n\\t- Updated README.md with improved grammatical clarity in instruct\"\n },\n {\n \"title\": \"fix(plugin-depin): sentientAI description\",\n \"prNumber\": 2668,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nIssue #2657 \\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow: This change only modifies the GitBook provider\u2019s return format to incl\"\n },\n {\n \"title\": \"feat(new-plugin): suno Eliza plugin\",\n \"prNumber\": 2656,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-suno\\r\\n\\r\\nA Suno AI music generation plugin for ElizaOS that enables AI-powered music creation and audio manipulation.\\r\\n\\r\\n## Overview\\r\\n\\r\\nThe Suno plugin integrates Suno AI's powerful music generation capabilities into ElizaO\"\n },\n {\n \"title\": \"fix: a typo bug in conflux plugin\",\n \"prNumber\": 2654,\n \"type\": \"bugfix\",\n \"body\": \"In handler function of packages/plugin-conflux/src/actions/confiPump.ts:\\r\\n\\r\\n```\\r\\n // Generate content based on template\\r\\n const context = composeContext({\\r\\n state,\\r\\n template: confluxTransferTemplate, \"\n },\n {\n \"title\": \"feat: Add swap & improvements for multiversx-plugin\",\n \"prNumber\": 2651,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nmultiversx-plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nThe PR is not related to any issues.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2620\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n\\t- Updated `.gitignore` to exclude `node-comp\"\n },\n {\n \"title\": \"feat(plugin-holdstation): add plugin holdstation swap\",\n \"prNumber\": 2596,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo specific issue or ticket is linked to this PR.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Relates to\\r\\n\\r\\n## LINK TO ISSUE OR TICKET \\r\\nhttps://github.com/elizaOS/eliza/issues/2561\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2572\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- *\"\n },\n {\n \"title\": \"feat(plugin-farcaster): test config and test coverage\",\n \"prNumber\": 2567,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2566\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added text-to-speech support for Indonesian, Tagalog, and M\"\n },\n {\n \"title\": \"fix:Incorrect boolean parsing for ENABLE_OPEN_AI_COMMUNITY_PLUGIN setting #2559\",\n \"prNumber\": 2560,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2559\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\nThis change only affects the configuration parsing for the ENABLE_OPEN_AI_COMM\"\n },\n {\n \"title\": \"chore(revert): optimize pnpm cache configuration\",\n \"prNumber\": 2556,\n \"type\": \"other\",\n \"body\": \"edit: reverting most pnpm caching attempts\"\n },\n {\n \"title\": \"chore: optimize pnpm cache configuration\",\n \"prNumber\": 2555,\n \"type\": \"other\",\n \"body\": \"Optimizes pnpm cache configuration to improve package reuse during installation.\\n\\nChanges made:\\n- Move pnpm setup before cache configuration\\n- Add architecture-specific cache keys\\n- Include package.json in cache key for better specificity\\n-\"\n },\n {\n \"title\": \"feat: Cosmos Plugin - IBC swap action\",\n \"prNumber\": 2554,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n# Risks\\r\\nLow risk \u2013 this PR adds an action to an existing plugin and does not interfere with the core f\"\n },\n {\n \"title\": \"chore: remove cleanup step from integration tests workflow\",\n \"prNumber\": 2553,\n \"type\": \"refactor\",\n \"body\": \"# Remove cleanup step from integration tests workflow\\n\\nThis PR removes the cleanup step from the integration tests workflow as requested. The cleanup step was running `pnpm clean` which is no longer needed in the workflow.\\n\\n## Changes\\n- Rem\"\n },\n {\n \"title\": \"chore: remove cleanup step from integration tests workflow\",\n \"prNumber\": 2551,\n \"type\": \"refactor\",\n \"body\": \"# Remove cleanup step from integration tests workflow\\n\\nThis PR removes the cleanup step from the integration tests workflow as requested. The cleanup step was running `pnpm clean` which is no longer needed in the workflow.\\n\\n## Changes\\n- Rem\"\n },\n {\n \"title\": \"feat(plugin-devin): implement client-agnostic Devin plugin\",\n \"prNumber\": 2549,\n \"type\": \"feature\",\n \"body\": \"# Devin Plugin PR\\n\\n## Changes\\n- Implemented client-agnostic Devin plugin\\n- Added comprehensive test coverage\\n- Created detailed README documentation\\n- Merged develop branch successfully\\n\\n## Testing\\n- Unit tests passing\\n- API integration ver\"\n },\n {\n \"title\": \"feat: Updated READ.me file with pre-requisites to enable telegram bot\",\n \"prNumber\": 2547,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nTelegram Client\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Renamed internal method for object generation\\n\\t- Improved code formatting and readability\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Improved error handling for AgentKit actions initialization\\n\\t- Enhanced code readability with formatting adjustments i\"\n },\n {\n \"title\": \"test configuration and tests for client-lens\",\n \"prNumber\": 2534,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2533\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/5bdc0051-b97c-450b-be29-1cc66ea1d1b6\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFollow up on https:/\"\n },\n {\n \"title\": \"feat: add anthropic image provider for vision\",\n \"prNumber\": 2524,\n \"type\": \"feature\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nVision image descriptions\\r\\n\\r\\n# Risks\\r\\n\\r\\nlow: \\r\\nadded an image provider for anthropic which generally defaulted to openai. so the risk is pretty low\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nadd AnthropicImageProvider \"\n },\n {\n \"title\": \"feat: plugin rabbi trader tests\",\n \"prNumber\": 2520,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2519\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFeature/plugin coingecko #1761\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Documentation**\\r\\n\\t- Added a citation section to the R\"\n },\n {\n \"title\": \"docs: add docs/README_JA.md\",\n \"prNumber\": 2515,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n\\t- Updated Japanese README with comprehensive project details\\n\\t- Added project overview for Eliza\\n\\t- Included setup \"\n },\n {\n \"title\": \"feat: add support for NVIDIA inference for ElizaOS\",\n \"prNumber\": 2512,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n\\r\\n\\r\\n# Add NVIDIA Model Provider Support to ElizaOS\\r\\n\\r\\nThis PR adds support for NVIDIA's AI models through their inference API, expanding ElizaOS's\"\n },\n {\n \"title\": \"test: plugin-tee - adjusting project structure and new tests\",\n \"prNumber\": 2508,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2507\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n- `@elizaos/plugin-agentkit` - default configuration in the agent/src/index.ts file for easier import b\"\n },\n {\n \"title\": \"test: api timeout handling for plugin-binance\",\n \"prNumber\": 2504,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2486\\r\\n\\r\\n\\r\\n\\r\\nThis PR introduces the new **plugin-openai** for text generation functionality using OpenAI's GPT models.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\nNo linked issue.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. \\r\\nThis change introduces a default logger level, which affects logging outputs. Potential risks include unexpected logging behavior if the `DEFAULT_LOG_L\"\n },\n {\n \"title\": \"feat(plugin-new): initia plugin + chore revert to integrationTests from stable release 0.1.7\",\n \"prNumber\": 2448,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nI am developing Initia plugin for elizaOS.\\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\\nThis PR is base initia plugin development. I implemented INIT token transfer action for agent.\\r\\n\\r\\n## What kind of ch\"\n },\n {\n \"title\": \"feat: create version.cmd for windows support\",\n \"prNumber\": 2442,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nIssue: Build failures on Windows platform\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Changes are isolated to build scripts and type definitions. No runtime behavior is affected.\\r\\n\\r\\n- Windows build script changes only affect local development on Wi\"\n },\n {\n \"title\": \"feat: add Mind Network plugin\",\n \"prNumber\": 2431,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nNo specific linked issue or ticket, as this is a feature addition for the Mind Network plugin.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow:\\r\\n\\r\\nThe plugin is newly introduced and self-contained, limiting its impact on unrelated parts of the Eliza ecos\"\n },\n {\n \"title\": \"fix: Fix Incorrect Tweet ID Parameter Passed to sendTweet Function\",\n \"prNumber\": 2430,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/1958#issuecomment-2582289612\\r\\n\\r\\nThe issue occurred because the LLM generated a verbose response like:\\r\\n\\\"Received The most interesting and relevant tweet for XXX to reply to is 187954009886315\"\n },\n {\n \"title\": \"feat:add plugin-lightning\",\n \"prNumber\": 2429,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-lightning\\r\\n\\r\\nThis plugin enables create lightning invoice or payInvoice.\\r\\n\\r\\n## Features\\r\\n\\r\\n- \ud83d\udcb1 Make a new off-chain invoice.\\r\\n- \ud83d\udcca Make an off-chain payment.\\r\\n\\r\\n## Installation\\r\\n\\r\\nAdd the plugin to your Eliza configuratio\"\n },\n {\n \"title\": \"feat: add a way to create/store/restore agents in the filesystem\",\n \"prNumber\": 2389,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nNo Issue.\\r\\n\\r\\n# Risks\\r\\n\\r\\nAs it is using a env variable to enable/disable the feature, there are no risks involved.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nIf USE_CHARACTER_STORAGE is enabled in the .env:\\r\\n\\r\\nIt stores a\"\n },\n {\n \"title\": \"feat: plugin for OriginTrail Decentralized Knowledge Graph\",\n \"prNumber\": 2380,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A - New plugin contribution\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow:\\r\\n- Requires you to explicitly provide your private key in the environment variable before it does anything with your funds\\r\\n- Creation of OriginTrail Knowledge Assets spends y\"\n },\n {\n \"title\": \"feat: add adapter-qdrant\",\n \"prNumber\": 2322,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdd qdrant adapter into Eliza system.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFixes [#2272](https://github.com/elizaOS/eliza/issues/2272)\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nAI Agent Dev School Video #2: https://www.youtube.com/watch?v=XenGeAcPAQo&t=3383s \\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"chore: updated .gitignore + removed build files\",\n \"prNumber\": 3117,\n \"type\": \"other\",\n \"body\": \"chore: updated .gitignore + removed build files\"\n },\n {\n \"title\": \"fix: auto-scrolling issue in client\",\n \"prNumber\": 3115,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/1977\\r\\n\\r\\nNoticed that when chatting with a character on the client, the conversation doesn\u2019t automatically scroll to the bottom after submitting a message and receiving a response. This PR fix\"\n },\n {\n \"title\": \"fix: fixing the error parsing json when an array is a value in a JSON\u2026\",\n \"prNumber\": 3113,\n \"type\": \"bugfix\",\n \"body\": \"\u2026 object\\r\\n\\r\\n# Relates to\\r\\n\\r\\nHaven't created a ticket, but it seems to be related to recent changes in the `normalizeJsonString` function.\\r\\n\\r\\nWhen using the Slack client, JSON like:\\r\\n\\r\\n```json\\r\\n{\\r\\n \\\"objective\\\": \\\"The user wants to summarize \"\n },\n {\n \"title\": \"fix: docker build command by skipping eslint files\",\n \"prNumber\": 3110,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\nRunning docker build fails because eslint config have been removed\\r\\n![Screenshot 2025-01-31 at 14 13 58](https://github.c\"\n },\n {\n \"title\": \"fix: plugin-apro\",\n \"prNumber\": 3106,\n \"type\": \"bugfix\",\n \"body\": \"Investigated and added the peoper ether to the configuration it was missing and fixed all the code.\"\n },\n {\n \"title\": \"fix: plugin-aptos\",\n \"prNumber\": 3104,\n \"type\": \"bugfix\",\n \"body\": \"Fixed all the issues and added Biome.\"\n },\n {\n \"title\": \"docs: Add \\\"What Did You Get Done This Week? 11\\\" notes\",\n \"prNumber\": 3103,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nDocumentation updates for community streams\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding a new community stream summary.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds the summary document for \\\"What Did You \"\n },\n {\n \"title\": \"fix: plugin-arthera-biome\",\n \"prNumber\": 3102,\n \"type\": \"bugfix\",\n \"body\": \"fixed al issues \"\n },\n {\n \"title\": \"fix: plugin-asterai\",\n \"prNumber\": 3101,\n \"type\": \"bugfix\",\n \"body\": \"Added only the Biome. Code was good.\"\n },\n {\n \"title\": \"fix: plugin-autonome-v1\",\n \"prNumber\": 3098,\n \"type\": \"bugfix\",\n \"body\": \"Fixed all issues.\"\n },\n {\n \"title\": \"fix: fixed build error in plugin-email-automation \",\n \"prNumber\": 3097,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3071\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3067\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3062\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nNavigate links to specified resources\\r\\n## What kind of change is this?\\r\\nDocum\"\n },\n {\n \"title\": \"fix: OpenAI embedding issue\",\n \"prNumber\": 3003,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIssue: OpenAI embeddings error when running character without OpenAI API key configured in .env file. \\r\"\n },\n {\n \"title\": \"feat (chore): plugin avalanche test config and coverage\",\n \"prNumber\": 2999,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2998\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2996\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2991\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2981\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2979\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNo specific issue or ticket. This PR updates the README with a French\"\n },\n {\n \"title\": \"fix: handle whitespace in quote conversion\",\n \"prNumber\": 2961,\n \"type\": \"bugfix\",\n \"body\": \"I noticed that array parsing sometimes fails because, in this PR (https://github.com/elizaOS/eliza/pull/2802/files), the regex matches 'something' only if it is immediately followed by a comma, closing brace, or closing bracket, without any\"\n },\n {\n \"title\": \"fix: plugin-letzai\",\n \"prNumber\": 2960,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors.\"\n },\n {\n \"title\": \"fix: plugin-lightning\",\n \"prNumber\": 2959,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors and also the missing use of Zod.\"\n },\n {\n \"title\": \"fix: plugin-lit\",\n \"prNumber\": 2957,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and leaved only 3 any that we can change only afer testing. \"\n },\n {\n \"title\": \"fix: plugin-massa\",\n \"prNumber\": 2955,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors.\"\n },\n {\n \"title\": \"fix-plugin-mina\",\n \"prNumber\": 2954,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors \"\n },\n {\n \"title\": \"fix: mind-network\",\n \"prNumber\": 2953,\n \"type\": \"bugfix\",\n \"body\": \"Added only missing logging.\"\n },\n {\n \"title\": \"fix: plugin-moralis\",\n \"prNumber\": 2952,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the issues.\"\n },\n {\n \"title\": \"fix: {{maxTweetLength}} doesn't work in tweet post template \",\n \"prNumber\": 2951,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/2927\"\n },\n {\n \"title\": \"fix: remove unnecessary @ts-expect-error directive in chat component\",\n \"prNumber\": 2950,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\nTypeScript error TS2578 in chat component\\r\\n\\r\\n# Risks\\r\\nLow - This is a simple removal of an unnecessary TypeScript directive that was causing an error.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nRemoves an unnecessary @ts-exp\"\n },\n {\n \"title\": \"fix: add missing plugins in package.json\",\n \"prNumber\": 2947,\n \"type\": \"feature\",\n \"body\": \"There were several missing plugins in package.json, which prevented the app from starting. I\u2019ve added them back. It seems this issue was caused by a merge conflict in this: https://github.com/elizaOS/eliza/commit/b3bc2547285663abbf4c3852f38\"\n },\n {\n \"title\": \"fix: remove dead code\",\n \"prNumber\": 2945,\n \"type\": \"bugfix\",\n \"body\": \"removed dead code (comments)\"\n },\n {\n \"title\": \"fix: plugin-movement\",\n \"prNumber\": 2943,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors \"\n },\n {\n \"title\": \"fix: plugin-multiversx\",\n \"prNumber\": 2942,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors present. \"\n },\n {\n \"title\": \"fix: plugin-near\",\n \"prNumber\": 2941,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and typing.\"\n },\n {\n \"title\": \"fix: plugin-news\",\n \"prNumber\": 2940,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the type and literals.\"\n },\n {\n \"title\": \"fix: building error\",\n \"prNumber\": 2938,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: plugin-nft-collection\",\n \"prNumber\": 2937,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and most if not all the typing.\"\n },\n {\n \"title\": \"fix: plugin-nft-generation\",\n \"prNumber\": 2934,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed partially the typing and the reassigmnet logic. To fix it all we need to redo partially the code. I leave for a nother PR.\"\n },\n {\n \"title\": \"feat: add public access to packages.\",\n \"prNumber\": 2933,\n \"type\": \"feature\",\n \"body\": \"This ensures all packages that are not marked private are properly scoped and can be published to npm registry.\"\n },\n {\n \"title\": \"fix template typos\",\n \"prNumber\": 2932,\n \"type\": \"bugfix\",\n \"body\": \"Minor fixes as first contribution, noticed while diving source code\"\n },\n {\n \"title\": \"chore: inconsistent folder naming conventipn\",\n \"prNumber\": 2931,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: invalid npm package naming convention\",\n \"prNumber\": 2930,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: missing version prop in package.json\",\n \"prNumber\": 2929,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"ci: changes to allow package scoping to public\",\n \"prNumber\": 2928,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"Update lpmanager.character.json\",\n \"prNumber\": 2921,\n \"type\": \"other\",\n \"body\": \"The subject of the sentence is \\\"the center price\\\", which is singular, so the correct verb form is \\\"is\\\" instead of \\\"are\\\".\"\n },\n {\n \"title\": \"feat: new model provider for LM Studio\",\n \"prNumber\": 2913,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdd LM Studio model provider\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2859\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2853\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2849\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo issue yet; can file an issue if you'd like?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"fix: plugin-tts \",\n \"prNumber\": 2829,\n \"type\": \"bugfix\",\n \"body\": \"Fixed non-critical issues highlighted by strict biome linting:\\n- Updated imports to use `node:` prefix\\n- Changed bracket notation to dot notation for object access\\n- Added explicit type for `target_voice`\\n- Simplified environment variable a\"\n },\n {\n \"title\": \"feat: add new readmes, move some others for consistency\",\n \"prNumber\": 2828,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, its documentation \\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nUpdates the d\"\n },\n {\n \"title\": \"fix: plugin-zksync-era multiple errors and issues as documented\",\n \"prNumber\": 2819,\n \"type\": \"bugfix\",\n \"body\": \"# Fix plugin-zksync-era\\r\\n\\r\\n- Replace non-null assertion with fallback in useGetAccount\\r\\n- Avoid parameter reassignment in transferAction handler\\r\\n- Add explicit typing for hash variable\\r\\n- Convert string concatenations to template literals\\r\"\n },\n {\n \"title\": \"fix: nvidia nim environment\",\n \"prNumber\": 2817,\n \"type\": \"bugfix\",\n \"body\": \"# Fix: NVIDIA NIM Plugin Environment Variables Typo\\r\\n\\r\\n## Changes\\r\\n- Fixed typo in environment variable names in `actionGetTopic.ts`:\\r\\n - `NVIDIA_OFFTOPIC_SYSTEM`\\r\\n - `NVIDIA_OFFTOPIC_USER`\\r\\n\\r\\n## Technical Details\\r\\n- Modified: `packages/p\"\n },\n {\n \"title\": \"fix: akash splash \",\n \"prNumber\": 2816,\n \"type\": \"bugfix\",\n \"body\": \"# Akash Plugin UI Enhancement\\r\\n\\r\\n## Changes\\r\\n- Updated splash screen design for Akash plugin\\r\\n- Enhanced visual presentation of the interface\\r\\n- Improved user experience with better layout\\r\\n\\r\\n## Technical Details\\r\\n- Modified: `packages/plug\"\n },\n {\n \"title\": \"docs: Update client-telegram README.md\",\n \"prNumber\": 2814,\n \"type\": \"docs\",\n \"body\": \"Just corrected some formatting issues, and added details about configuration of advanced features via character.json files.\\r\\n\\r\\n\\r\\n\\r\\n# R\"\n },\n {\n \"title\": \"feat: Add Access Token Management to MultiversX Plugin\",\n \"prNumber\": 2810,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nmultiversx-plugin\\r\\n\\r\\n# Risks\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Add the possibility to limit token management to one user or all user\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements\\r\\n\\r\\n# Documentation change\"\n },\n {\n \"title\": \"test: plugin-0x test configuration and coverage\",\n \"prNumber\": 2807,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2806\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2804\\r\\n\\r\\nNo specific issue or ticket referenced.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\nLow \u2014 this PR primarily refines the parsing function\"\n },\n {\n \"title\": \"feat(new-plugin): create gelato plugin relay\",\n \"prNumber\": 2799,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\nNo linked issue. This PR introduces a Gelato Relay plugin with support for both `sponsoredCall` and `sponsoredCallERC2771` functionalities.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Dependency\\r\\n\u2757 \u2757 **Must be merged with : https://github.com/elizaOS/agent-twitter-client/pull/57**\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n\"\n },\n {\n \"title\": \"chore(update-plugin-initialization): btcfun & trikon plugin\",\n \"prNumber\": 2643,\n \"type\": \"other\",\n \"body\": \"# btcfun Plugin for Eliza\\r\\n\\r\\n## Description\\r\\nBTC.Fun enables users to effortlessly launch and trade Runes/BRC20 tokens on the Bitcoin network in a permissionless environment. Through the platform, anyone can create their own Runes/BRC20 tok\"\n },\n {\n \"title\": \"feat(client-alexa): Basic Alexa skill notification\",\n \"prNumber\": 2564,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nMedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Integrate communication with \"\n },\n {\n \"title\": \"docs: Add \\\"What Did You Get Done This Week? #10\\\" notes\",\n \"prNumber\": 2558,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nDocumentation updates for community streams\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding a new community stream summary.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds the summary and transcript for \\\"What Di\"\n },\n {\n \"title\": \"feat(new-plugin): quick intel plugin for token security analysis\",\n \"prNumber\": 2391,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - This plugin is isolated and:\\r\\n\\r\\n- Uses established API endpoints\\r\\n- Has proper error handling\\r\\n- Follows existing plugin patterns\\r\\n- No database changes required\\r\\n- No deployment risks\\r\\n\\r\\n# Background\\r\\n\"\n },\n {\n \"title\": \"feat(new-plugin): 0x plugin to swap on evms\",\n \"prNumber\": 2329,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2230\\r\\nCreated a plugin for 0x protocol, a feature request from \"\n },\n {\n \"title\": \"feat: custom s3 endpoint url for 'plugin-node'\",\n \"prNumber\": 2176,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2174, and builds upon https://github.com/elizaOS/eliza/pull/2379\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This affects only the `plugin-node`, and it changes logic in a way that is backward compatible. \\r\\n\\r\\n\"\n },\n {\n \"title\": \"feat: Separate Knowledge system + Multi-Agent RAG Optimization\",\n \"prNumber\": 1620,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow Risk, as the new RAG system is completely separate, and must be enabled by the user to use as of now.\\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. ch\"\n },\n {\n \"title\": \"feat(new-plugin): deva client integration\",\n \"prNumber\": 1238,\n \"type\": \"feature\",\n \"body\": \"# Pull Request: Integrate Deva into Eliza\\r\\n\\r\\n## Relates to\\r\\n\\r\\nThis PR adds a new [Deva](https://www.deva.me/) client integration for the Eliza AI agent, enabling posting and scheduling posts to the [Deva](https://www.deva.me/) feed.\\r\\n\\r\\n## R\"\n },\n {\n \"title\": \"feat: Add Extra Multimedia Support for Telegram Client \",\n \"prNumber\": 2510,\n \"type\": \"feature\",\n \"body\": \"This PR is based on https://github.com/elizaOS/eliza/pull/1837\\r\\nI\u2019ve remade this PR because maintainer edit access was not enabled, making it difficult to make necessary changes directly.\\n\\n\\n\\n## Summary by Cod\"\n },\n {\n \"title\": \"chore: update createToken.ts\",\n \"prNumber\": 2493,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\ncreat -> create\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\"\n },\n {\n \"title\": \"chore: corrected the link to the banner\",\n \"prNumber\": 2491,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2481\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n[Issue #2252](https://github.com/elizaOS/eliza/issues/2252)\\r\\n[Expands on #2328](https://github.com/eliz\"\n },\n {\n \"title\": \"fix: linting errors\",\n \"prNumber\": 2474,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: add openai env to smokeTests\",\n \"prNumber\": 2472,\n \"type\": \"feature\",\n \"body\": \"Reverts elizaOS/eliza#2459\"\n },\n {\n \"title\": \"test: adding test configuration and tests for redis adapter\",\n \"prNumber\": 2470,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2469\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2467\\r\\n\\r\\nThis pull request relates to resolving the issue where `animated.div` from `@react-spring/web` was not accepting the `children` prop in TypeScript, causing type errors.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**\"\n },\n {\n \"title\": \"chore: set openai as default character's provider\",\n \"prNumber\": 2460,\n \"type\": \"other\",\n \"body\": \"chore: set openai as default character's provider\"\n },\n {\n \"title\": \"revert: \\\"refactor: dockerize smoke tests\\\"\",\n \"prNumber\": 2459,\n \"type\": \"refactor\",\n \"body\": \"Reverts elizaOS/eliza#2420\"\n },\n {\n \"title\": \"feat: Add features to the Solana Agent Kit \",\n \"prNumber\": 2458,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1619\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2453\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2405 \\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\"\n },\n {\n \"title\": \"fix: conditional use of useQuery in AgentRoute component to prevent runtime errors.\",\n \"prNumber\": 2413,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nGeneral improvement; no specific issue linked.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2406\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2403\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFix the Remote Attestation Action to prevent hallucination in Twitter and Discord clients when publishing\"\n },\n {\n \"title\": \"feat: add safe_mode (& cfg_scale) for venice image generation\",\n \"prNumber\": 2354,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nVery low\\r\\n\\r\\n# Background\\r\\n\\r\\nVenice has uncensored image generation which may create issues for agents running on platforms with strict terms of service related to nudity or graphic content.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nVenice r\"\n },\n {\n \"title\": \"fix: align base url in client if api runs on a different port\",\n \"prNumber\": 2353,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2344\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAction: DESCRIBE_IMAGE\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nLow risks, the only risk is that someone hooks up this plugin with their Solana wallet and because it is so easy to use spends more tokens than\"\n },\n {\n \"title\": \"feat: Telegram autonomous agent enhancement\",\n \"prNumber\": 2338,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\n[PR 2335](https://github.com/elizaOS/eliza/pull/2335)\\r\\n# Risks\\r\\n\\r\\nLow risk, minimal changes to Discord client\\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\\nFeatures (non-breaking change wh\"\n },\n {\n \"title\": \"fix: formatting in Browser section of README.md\",\n \"prNumber\": 2336,\n \"type\": \"bugfix\",\n \"body\": \"Hey all! I saw strange formatting in the README.md and figured it was an extra three backticks ```\\r\\n\\r\\nSure enough, deleting those made the section render as intended. I also reworded one of the sentences that had three \\\"and\\\"s to make it a l\"\n },\n {\n \"title\": \"feat: Discord autonomous agent enhancement\",\n \"prNumber\": 2335,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow risk, minimal changes to Discord client\\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\\nFeatures (non-breaking change which adds functionality)\\r\\n\\r\\nThis feature add the \"\n },\n {\n \"title\": \"Update README_TR.md\",\n \"prNumber\": 2334,\n \"type\": \"other\",\n \"body\": \"Added WSL 2 link\"\n },\n {\n \"title\": \"fix: SwapAction in evm-plugin\",\n \"prNumber\": 2332,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nfix bugs & improvements in plugin-evm\\r\\n\\r\\n# Risks\\r\\n\\r\\nMedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\"\n },\n {\n \"title\": \"feat: Enable Multiple remote character urls\",\n \"prNumber\": 2328,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n[Issue #2252](https://github.com/elizaOS/eliza/issues/2252)\\r\\n[Expands on PR #2281](https://github.com/e\"\n },\n {\n \"title\": \"feat: dexscreener trending\",\n \"prNumber\": 2325,\n \"type\": \"feature\",\n \"body\": \"Adding code from https://github.com/elizaOS/eliza/pull/1584\\r\\nto DS plugin for fetching trending, boosted and latest tokens added to dexscreener\"\n },\n {\n \"title\": \"fix: correct OPENROUTER_API_KEY env in config\",\n \"prNumber\": 2324,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\n# Risks\\r\\nLOW\\r\\n\\r\\n# Background\\r\\nset private runtime envs for each character, eg: \\r\\n```\\r\\ncharacter.settings.secrets = {...privateEnvs};\\r\\n```\\r\\nuse openrouter as ModelProvider and set OPENROUTER_API_KEY as agent runtime secrects\"\n },\n {\n \"title\": \"feat: Onchain Agent Transformer - transform any Eliza agents into unstoppable Solidity smart contracts deployed on 10+ blockchains\",\n \"prNumber\": 2319,\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\\nTransform any Eliza agents into unstoppable Solidity smart contracts deployed on 10+ blockchains\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nMore flexible than with env and support for\"\n },\n {\n \"title\": \"docs: Update README.md\",\n \"prNumber\": 2309,\n \"type\": \"docs\",\n \"body\": \"Remove duplicate in the readme\"\n },\n {\n \"title\": \"fix: farcaster memory\",\n \"prNumber\": 2307,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nRe-implements #2039 and updates Remote Attestations to have more content to ensure older generated RA Quo\"\n },\n {\n \"title\": \"fix: Update package.json of core package\",\n \"prNumber\": 2301,\n \"type\": \"bugfix\",\n \"body\": \"these packages are being used in prod build and generate errors if you decide to just use this package in a project.\\r\\n\\r\\n# Background\\r\\n\\r\\nThese packages are being used under src/ folder and needs to be part of the dependencies not dev depende\"\n },\n {\n \"title\": \"feat: coinbase agentkit plugin for eliza\",\n \"prNumber\": 2298,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAdding AgentKit EVM support to Eliza\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2223 \\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2164\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2212\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nGives eliza agents their own abstract global wallets so they can use Abstract similar to how real users\"\n },\n {\n \"title\": \"docs: Add Greek translation for README_GR\",\n \"prNumber\": 2199,\n \"type\": \"feature\",\n \"body\": \"Relates to\\r\\nThis pull request relates to issue https://github.com/elizaOS/eliza/issues/2197.\\r\\n\\r\\nRisks\\r\\nLow: This PR only adds a Greek translation for the README file and updates the main README to include a link to the new translation. No f\"\n },\n {\n \"title\": \"fix(plugin-twitter): change prompt to ensure it returns json\",\n \"prNumber\": 2196,\n \"type\": \"bugfix\",\n \"body\": \"per masterdai https://discord.com/channels/1253563208833433701/1300025221834739744/1327947002943770705\\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\\nPrompt improvement\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nBug fixes (non-\"\n },\n {\n \"title\": \"refactor: websearch into a service\",\n \"prNumber\": 2195,\n \"type\": \"refactor\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\n\\r\\nRemove Tavily from core https://github.com/elizaOS/eliza/issues/2123\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. While it touche\"\n },\n {\n \"title\": \"chore: 0.1.8.build.1 (dev => main)\",\n \"prNumber\": 2194,\n \"type\": \"other\",\n \"body\": \"Fixes docker build\\r\\nUnbotches version for npm publish/release\\r\\n\\r\\nChangelog\\r\\n- #2184\\r\\n- #2182\\r\\n- #2187\\r\\n- #2193\"\n },\n {\n \"title\": \"chore: Prep 0.1.8.build.1\",\n \"prNumber\": 2193,\n \"type\": \"other\",\n \"body\": \"- Bump version to 0.1.8.build.1\"\n },\n {\n \"title\": \"fix postgres adapter migration extension creation which already exists at this point\",\n \"prNumber\": 2188,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/2067\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nSuper low-risk, text mutation/scrub prior to sending Tweet.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does \"\n },\n {\n \"title\": \"feat: \ud83c\udf88 perf(vscode): Set file nesting for md and DockerFile\",\n \"prNumber\": 2177,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2172\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/pull/1620\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo issue\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\\n\\r\\nThis is a brand new feature.\\r\\nIt is only effective when using dependency\"\n },\n {\n \"title\": \"refactor: farcaster client env configuration \",\n \"prNumber\": 2087,\n \"type\": \"refactor\",\n \"body\": \"# Relates to\\r\\nRefactoring Farcaster Client Implementation\\r\\n\\r\\n# Risks\\r\\nLow - This is primarily a refactoring change that improves code organization and configuration management without changing core functionality.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What \"\n },\n {\n \"title\": \"feat: atoma provider\",\n \"prNumber\": 2082,\n \"type\": \"feature\",\n \"body\": \"# Background\\r\\n\\r\\nAtoma is a decentralized private and verifiable AI execution network. It provides the infrastructure for developers and enterprises to use open-source AI models and build AI applications with full privacy.\\r\\n\\r\\n## What does th\"\n },\n {\n \"title\": \"feat: add external router path and new tweet generation\",\n \"prNumber\": 2081,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\nN/A - this is an issue and will be described below in the Backgroun\"\n },\n {\n \"title\": \"feat: full overhaul of client\",\n \"prNumber\": 2038,\n \"type\": \"feature\",\n \"body\": \"This PR replaces the entire `client` app with a refreshed look. From this base it's very easy to add additional features going forward.\\r\\n\\r\\n\\r\\n\\r\\n## Featu\"\n },\n {\n \"title\": \"chore(ci): add pnpm lockfile consistency check workflow\",\n \"prNumber\": 2015,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nN/A - Direct improvement to CI process\\r\\n\\r\\n# Risks\\r\\nLow - This is a new CI workflow that doesn't affect the production code.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nCurrently, on the main branch, `pnpm install` fails to ru\"\n },\n {\n \"title\": \"feat: Adding plugin for B\u00b2 Network\",\n \"prNumber\": 2010,\n \"type\": \"feature\",\n \"body\": \"B\u00b2 Network is a Bitcoin Layer2 network. Add this plugin to integrate with Eliza so that users can interact with B\u00b2 Network through Eliza agent.\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAdd B\u00b2 Network plugin into Eliza system.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\nMain implementa\"\n },\n {\n \"title\": \"feat: add instagram client\",\n \"prNumber\": 1964,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow, is a new client, does't have any impact on old code.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nImplements a new Instagram client for ElizaOS that:\\r\\n\\r\\n1. Handles Instagram authentication and session management\\r\\n2. Provides media posting\"\n },\n {\n \"title\": \"chore(plugin-solana): replace console with elizaLogger\",\n \"prNumber\": 1888,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nInteracting with Injective chain\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nAdd cross-chain swaps to ElizaOS through Squid Router\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does t\"\n },\n {\n \"title\": \"feat: Add support for VoyageAI embeddings API\",\n \"prNumber\": 1442,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nA bug or change in behavior of embedding provider selection could cause an unexpected switch. This could cause pre-existing embeddings and new embeddings to be incompatible.\\r\\n\\r\\nI removed `isOllama` flag from the config. It seemed\"\n },\n {\n \"title\": \"feat: add birdeye plugin\",\n \"prNumber\": 1417,\n \"type\": \"feature\",\n \"body\": \"# Overview\\r\\n\\r\\n- This PR introduces a new plugin for the data provider [Birdeye](https://www.birdeye.so/). \\r\\n- The plugin includes API endpoints and related types for all [Birdeye API](https://docs.birdeye.so/) endpoints even though not all \"\n },\n {\n \"title\": \"feat: improve GOAT integration by allowing tool calling when using generateText\",\n \"prNumber\": 1403,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\nhttps://x.com/sunosuporno/status/1870967395780792741\\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\\nTwo main things:\\r\\n1. Update `generateText` API to be able to pass through tool options to leverage the mo\"\n },\n {\n \"title\": \"fix: postgres-adapter - remove nonsensical schema check\",\n \"prNumber\": 1377,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\nCloses: https://github.com/elizaOS/eliza/issues/1376\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A (No specific issue or ticket linked)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n- This change only adds support for BNB cha\"\n },\n {\n \"title\": \"feat: Add devcontainer\",\n \"prNumber\": 1807,\n \"type\": \"feature\",\n \"body\": \"Hello from Hunter ($drpxbt) Team\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, no code is changed.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nEnables to open workspace in devcontainer (docker with vs code)\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nIm\"\n },\n {\n \"title\": \"fix: fix the chat stuck in infinite loop\",\n \"prNumber\": 1755,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nthe chat stuck in infinite loop when using model_local https://github.com/elizaOS/eliza/issues/1213\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2169\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"add github to client enumerations\",\n \"prNumber\": 2157,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdding the github to the `Clients` enumeration due to error when trying to run. `Invalid enum value'\\r\\n\\r\\n<\"\n },\n {\n \"title\": \"fix: correct SUI/USD price calculation\",\n \"prNumber\": 2150,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to Eliza client-twitter/plugin/SttTtsSpacesPlugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAI function enhancement, similar with #1446, @odilitime \\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nbug fix typo\\r\\n\\r\\n\\r\\n\\r\\n# \"\n },\n {\n \"title\": \"feat: Lens Network Plugin\",\n \"prNumber\": 2101,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A (No specific issue or ticket linked)\\r\\n\\r\\n---\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow \\r\\n- This change only adds support for the Lens Testnet network to enable transfers of Grass tokens between users. \\r\\n- Other features and functionalities of \"\n },\n {\n \"title\": \"Fix: Supabase updates\",\n \"prNumber\": 2100,\n \"type\": \"bugfix\",\n \"body\": \"Fixes an issue where missing rooms in the Supabase database caused errors when fetching them using `.single()`. Additionally, ensures that the database seed values contain valid timestamps and required non-null fields. Also fixes an issue w\"\n },\n {\n \"title\": \"Add gemini to image vision\",\n \"prNumber\": 2099,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow - This PR adds a new embedding model provider (Heurist) with BAAI/bge-large-en-v1.5 as the default model. Changes are additive and follow existing patterns.\\r\\n\\r\\n# Backgro\"\n },\n {\n \"title\": \"fix: Update clients.md to fix package name\",\n \"prNumber\": 2091,\n \"type\": \"bugfix\",\n \"body\": \"@eliza needs to be @elizaos in order for successful installation and imports\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nThere is no risk because only documentation is added.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n\\r\\n# Relates to\\r\\n- The Korean README file (`README_KOR.md`).\\r\\n\\r\\n# R\"\n },\n {\n \"title\": \"Update README_CN to match latest English README\",\n \"prNumber\": 2069,\n \"type\": \"tests\",\n \"body\": \"# Relates to\\r\\n\\r\\n- The Chinese README file (`README_CN.md`).\\r\\n\\r\\n# Risks\\r\\n\\r\\n- **Low**: This PR only updates documentation and does not affect code or functionality.\\r\\n- **Affected**: The Chinese README file (`README_CN.md`).\\r\\n\\r\\n# Background\\r\\n\\r\"\n },\n {\n \"title\": \"feat: pro api support, trending coins api\",\n \"prNumber\": 2068,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n- #1761\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low** - Adding new functionality and API support with proper error handling\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n1. Adds support for CoinGecko Pro API\\r\\n\\r\\n - Configurable through environment \"\n },\n {\n \"title\": \"fix: Bugfix in LetzAI Plugin -> missing named export and Plugin-type\",\n \"prNumber\": 2062,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n0002--feat-letzai-plugin tiny bugfix in the export of the module. Plugin was already merged to dev but \"\n },\n {\n \"title\": \"Galadriel docs and .env.example update\",\n \"prNumber\": 2061,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/2011\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - no functional changes\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdd a tutorial on how to use the Galadriel provider.\\r\\nAlso update the `.env.example` to put \"\n },\n {\n \"title\": \"revert: #2048\",\n \"prNumber\": 2059,\n \"type\": \"other\",\n \"body\": \"Reverts elizaOS/Eliza#2048\\r\\n\\r\\n\\r\\nuntil further review\"\n },\n {\n \"title\": \"Fix: case-sensitive column reference in knowledge table CHECK constraint\",\n \"prNumber\": 2058,\n \"type\": \"bugfix\",\n \"body\": \"Resolves a SQL error (42703: column \\\"isshared\\\" does not exist) in the knowledge table's CHECK constraint. The issue was caused by an incorrect column reference due to PostgreSQL\u2019s case sensitivity when handling column names inside constrain\"\n },\n {\n \"title\": \"feat: solana transaction more lenient\",\n \"prNumber\": 2053,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFixes the Key Derive functionality, by using path for reliable key derivation. Subject is documented and \"\n },\n {\n \"title\": \"chore: add conditionals for supabase to agent directory\",\n \"prNumber\": 2032,\n \"type\": \"feature\",\n \"body\": \"Added Condional for Supabase to the initializeDatabase function to allow for ease of use for Supabase as well as keeping the postgres and sqlite functionality. In conjunction with https://github.com/elizaOS/eliza/pull/2031\\r\\n\\r\\n# Relates to\\r\"\n },\n {\n \"title\": \"Update .env.example\",\n \"prNumber\": 2031,\n \"type\": \"other\",\n \"body\": \"Added Supabase variables. In conjunction with https://github.com/elizaOS/eliza/pull/2032\\r\\n\\r\\n# Relates to\\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\\nAdds Supabase variables to the .env\\r\\n\\r\\n## What kind of change is t\"\n },\n {\n \"title\": \"fix: include schema.sql and seed.sql in package files\",\n \"prNumber\": 2030,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nFixes #2009 - @elizaos/adapter-postgres package does not bundle together schema.sql\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Adding missing SQL files to package bundling. Only affects package distribution, not functionality.\\r\\n\\r\\n# Background\\r\\n\\r\\n\"\n },\n {\n \"title\": \"Fix: fix starknet plugin by replacing walletProvider with portfolio provider\",\n \"prNumber\": 2029,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2028\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates\\r\\nto readme.md rus\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nEliza currently supports various AI providers but lacks native integration with **nineteen.ai**, which \"\n },\n {\n \"title\": \"fix: letzAi build issues\",\n \"prNumber\": 2021,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nmultiversx-plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n- Minor bug fixed.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nAuto Client not working.\\r\\n\\r\\n\\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-Add client-telegram README.me file\\r\\n-Update comments to \"\n },\n {\n \"title\": \"feat: implement getKnowledge, searchKnowledge, createKnowledge, removeKnowledge and clearKnowledge methods\",\n \"prNumber\": 2005,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"Update plugins.md -- Allora README Fix\",\n \"prNumber\": 2003,\n \"type\": \"bugfix\",\n \"body\": \"- Fixed a comment-uncomment typo at the end of the Allora Documentation.\\r\\n- Added a link to more comprehensive documentation + examples at the bottom\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nNone\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n* None, just a chore\\r\\n\\r\\n# Risks\\r\\n\\r\\n* None\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n* Moves README\"\n },\n {\n \"title\": \"test: changing test structure for core package. Fixing failling outdated tests\",\n \"prNumber\": 1989,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1988\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow. Manually tested successfully. Purely additive in nature.\\r\\n\\r\\n# Background\\r\\nThe EVM plugin only had mainnet\"\n },\n {\n \"title\": \"chore: add debug logging for context\",\n \"prNumber\": 1980,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nWhile playing with Eliza and using multiple clients, I noticed that the contexts are often assembled in a mess with many bugs. I want to solve these in my future pull requests, but first, I want to add Eliza, the simple modi\"\n },\n {\n \"title\": \"test: adding tests for twitter plugin\",\n \"prNumber\": 1976,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nChanging project structure, adding tests for twitter plugin in __tests__ directory.\\r\\n# Risks\\r\\nLow: adding\"\n },\n {\n \"title\": \"chore: Cleaner logs on agent startup\",\n \"prNumber\": 1973,\n \"type\": \"refactor\",\n \"body\": \"# Risks\\r\\n\\r\\nLow. Cleans up the logs shown during agent startup.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nCleaning up the logs so that instead of:\\r\\n\\r\\n```\\r\\nSUCCESS\\r\\nSUCCESS\\r\\nCreating runtime for character Eliza\\r\\n```\\r\\n\\r\\nit shows\\r\\n\\r\\n```\\r\\n[\"\n },\n {\n \"title\": \"fix: Fix db init race condition affecting builds\",\n \"prNumber\": 1968,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1914#\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nCorrects the info from the auto generated readme for the Abstract plugin\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIntegration of the Anyone Network within the Eliza repository\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot tied to particular issue. Adding tests for twitter client, since \"\n },\n {\n \"title\": \"feat: Add Allora plugin\",\n \"prNumber\": 1955,\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[Allora Network](https://allora.network/) is an AI-powered inference platform that delivers real-time, self-improving predictions and insights for various use cases. By aggregating a\"\n },\n {\n \"title\": \"feat: Add fraxtal chain to evm\",\n \"prNumber\": 1954,\n \"type\": \"feature\",\n \"body\": \"add fraxtal to chains\"\n },\n {\n \"title\": \"fix: fixed error in C3PO and improved error handling feedback\",\n \"prNumber\": 1951,\n \"type\": \"bugfix\",\n \"body\": \"- Resolved an array in the c3po character file where the messageExamples were an object rather an 2D array.\\r\\n- Character validation handling has been improved\\r\\n\\r\\nBefore:\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/2a7fa7c8-d903-4\"\n },\n {\n \"title\": \"fix: Added Local Embedding Manager to reuse Local embed model - Fixes High Ram Issues\",\n \"prNumber\": 1950,\n \"type\": \"bugfix\",\n \"body\": \"# Fixes\\r\\n#1942 #866 #1623\\r\\n\\r\\n# Relates to\\r\\nMemory optimization for character file knowledge processing\\r\\n\\r\\n# Risks\\r\\nLow - This change optimizes the embedding model initialization without changing core functionality.\\r\\n\\r\\n# Background\\r\\n## What \"\n },\n {\n \"title\": \"feat: support for eternalai provider can write request/response log info\",\n \"prNumber\": 1948,\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\\nConfig eternalai logging from env, change name in env for consistent format\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nMore flexible than with env\\r\\n\\r\\n## Why are we doing this? Any con\"\n },\n {\n \"title\": \"feat: improve twitter paragraph splitting if containing url\",\n \"prNumber\": 1947,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot related to specific issue. Since we are improving packages struct\"\n },\n {\n \"title\": \"API route update\",\n \"prNumber\": 1923,\n \"type\": \"other\",\n \"body\": \"Update to the API route\"\n },\n {\n \"title\": \"Fix typo Update CHANGELOG.md\",\n \"prNumber\": 1922,\n \"type\": \"bugfix\",\n \"body\": \"# Fix Typo in CHANGELOG.md\\r\\n\\r\\n## Description:\\r\\n\\r\\nThis pull request fixes a typographical error in the `CHANGELOG.md` file. The word \\\"initital\\\" was corrected to \\\"initial.\\\"\\r\\n\\r\\n## Changes:\\r\\n- Corrected \\\"initital\\\" to \\\"initial\\\" in the `CHANGELOG\"\n },\n {\n \"title\": \"fix: handle empty input text to avoid memory content empty error\",\n \"prNumber\": 1919,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n- #1906 \\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\ncloses https://github.com/elizaOS/eliza/issues/1901\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFixes #1448 \\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nClosing #1796 in favor of this to avoid conflicts.\\r\\nTEE Plugin and Adding Remote Attestations to be uploade\"\n },\n {\n \"title\": \"Feat: Support wildcard in TWITTER_TARGET_USERS 1883\",\n \"prNumber\": 1884,\n \"type\": \"feature\",\n \"body\": \"# Support wildcard in TWITTER_TARGET_USERS\\r\\n\\r\\nFixes enhancement request #1883 \\r\\n## Summary\\r\\nAdded support for wildcard `*` in `TWITTER_TARGET_USERS` configuration to allow monitoring all users. This change enables broader interaction patter\"\n },\n {\n \"title\": \"feat: Use recommended settings in jupiter swap\",\n \"prNumber\": 1882,\n \"type\": \"feature\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nNo issue\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow risk to introduce regression in jupiter swaps\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nUse similar api call as jup.ag to perform swaps with dynamic slippage and dynamic priority fee\\r\\n\\r\\n## W\"\n },\n {\n \"title\": \"Fixed broken API Documentation URL\",\n \"prNumber\": 1881,\n \"type\": \"bugfix\",\n \"body\": \"fixed broken API Documentation in local-development.md\\r\\n\\r\\nit's not a lot, but it's honest work.\"\n },\n {\n \"title\": \"feat: add OpenWeather plugin\",\n \"prNumber\": 1880,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow - This is an additive change that introduces a new plugin without modifying existing functionality. The main risks are:\\r\\n\\r\\n- Rate limiting from OpenWeather API (1000 free API calls per day)\\r\\n- Potential timeout issues when th\"\n },\n {\n \"title\": \"test: adding test setup for telegram client\",\n \"prNumber\": 1879,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot related to specific issue. Since we are improving project and fol\"\n },\n {\n \"title\": \"chore(core): enable strict null checks\",\n \"prNumber\": 1878,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nType safety\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIssue: #1809\\r\\n\\r\\n\\r\\n\\r\\n# \"\n },\n {\n \"title\": \"feat: add coin price plugin (CoinMarketCap, CoinGecko & CoinCap)\",\n \"prNumber\": 1808,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#1773 & #1382\\r\\n\\r\\n\\r\\n\\r\\n#\"\n },\n {\n \"title\": \"fix: broken ci docs missed frozen pnpm file out-of-sync\",\n \"prNumber\": 1798,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# \u25c0\ufe0f Relates to:\\r\\n\\r\\nFixes the build related to the pnpm-lock not being in sync from the `docs/` dir\\r\\n\\r\\n# \u26a0\ufe0f Risks\\r\\n\\r\\n* low\"\n },\n {\n \"title\": \"feat: plugin new RabbiTrader\",\n \"prNumber\": 1785,\n \"type\": \"feature\",\n \"body\": \"# Rabbi Trader Plugin\\r\\n\\r\\nAn automated cryptocurrency trading plugin for Solana tokens with integrated trust scoring, market analysis, and Twitter notifications. Built on top of Goat, used actively with: https://x.com/rabbischlomo_ai\\r\\n\\r\\n## F\"\n },\n {\n \"title\": \"feat: Image descriptions into interaction.ts\",\n \"prNumber\": 1775,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to: Irys Plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. README update.\\r\\n\\r\\n\\r\\n# Ba\"\n },\n {\n \"title\": \"Opacity Verifiable Interference zkTLS Plugin\",\n \"prNumber\": 1673,\n \"type\": \"other\",\n \"body\": \"Co-authored @Hmac512 @RonTuretzky @Gajesh2007 \\r\\n## Background\\r\\nA few weeks ago, issues with aixbt were observed, where users mistakenly believed the moderation was performed by humans. This misconception caused a public relations disaster \"\n },\n {\n \"title\": \"Add support for Movement Network\",\n \"prNumber\": 1621,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow - non-breaking changes made to the Aptos Plugin\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdds support for transacting on Movement Network Testnet and Mainnet\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nNew Pl\"\n },\n {\n \"title\": \"feat: add massa-plugin\",\n \"prNumber\": 1582,\n \"type\": \"feature\",\n \"body\": \"\\r\\n## What does this PR do?\\r\\n\\r\\nAdd Massa plugin with Transfer action\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change which adds functionality)\\r\\n\\r\\n## Screenshots\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/bcb1f\"\n },\n {\n \"title\": \"feat: added new plugin - zktls - reclaim\",\n \"prNumber\": 1558,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\nA few weeks ago, we observed issues with aixbt, where users mistakenly believed the moderation was performed by humans. This misconception caused a public relations disaster and raised concerns about the AI\"\n },\n {\n \"title\": \"feat: support TEE logging and support running eliza in Intel SGX\",\n \"prNumber\": 1470,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to: \\r\\nKeywords: TEE, Intel SGX, Logging, Attestation, Verification, Gramine.\\r\\n\\r\\n\"\n },\n {\n \"title\": \"feat: Make templates in composeContext dynamic\",\n \"prNumber\": 1467,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n