{ "date_generated_for": "2025-01-26", "ai_news_elizaos_discord_md_2025-01-25": { "filename": "2025-01-25.md", "content": "# elizaOS Discord - 2025-01-25\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Updates\n- **DeepSeek R1 Integration**: Users report positive experiences with DeepSeek R1, noting its solid reasoning capabilities and cost-effectiveness compared to OpenAI. Multiple users are exploring proper configuration methods for DeepSeek as a model provider in their agents.\n- **Twitter/X Integration Challenges**: Many users experiencing login failures, authentication issues, and problems with agents posting in incorrect formats (including JSON or thinking monologues). Solutions discussed include using VPNs, setting up proxies, and verifying accounts with blue checks.\n- **Database Configuration**: Discussions about switching from SQLite to PostgreSQL/Supabase for better persistence. Users implementing knowledge systems to allow agents to access and utilize stored information.\n- **Memory Issues**: A brief mention of a \"memory issue fixed\" by 0xCatnipKing suggests some development progress.\n- **WebAssembly SIMD Support**: A user (Deepdelver) experienced runtime errors related to WebAssembly SIMD support when trying to build ElizaOS on a VM, specifically mentioning \"Wasm SIMD unsupported\" errors.\n- **Plugin Development**: Users creating and modifying plugins for various functionalities like Solana blockchain integration, web search, and Twitter actions.\n\n### Tokenomics & Treasury Management\n- **Major Tokenomics Update**: Shaw announced a significant update where the DAO plans to use its treasury assets (valued at $15-30M) to create one-sided liquidity pools paired with AI16Z tokens. This strategy aims to generate buy pressure and provide liquidity for partner tokens while avoiding direct selling of treasury assets.\n- **Value Accrual Framework**: Jin and timshel outlined a vision centered on \"attention/code/capital\" as the core pillars for token value growth:\n - Attention: Proliferating ElizaOS usage\n - Code: Improving ElizaOS functionality\n - Capital: Value accrual to treasury\n- **Revenue Models**: Discussions explored multiple potential revenue models including agent marketplace fees, investment strategies (where ai16z could function as a tier-1 investor in startups), launchpad services, and revenue sharing mechanisms.\n- **Launchpad Development**: A no-code launchpad platform was described as \"imminent\" by Shaw.\n\n### AI16Z & DegenAI Integration\n- **Super Agent Concept**: Community members, particularly tigerguo, expressed interest in understanding how DegenAI and Eliza might merge to create a \"super agent\" with enhanced capabilities.\n- **Web3 Industry Tools**: Feature requests include token analysis, blockchain transactions via voice commands, and optimized LP yield pool information.\n- **Leadership Changes**: Rhota mentioned joining to help organize alongside Skely, focusing on creating brand guidelines based on Degen's lore.\n\n### 3D AI TV Project\n- **News Aggregator Development**: The team is working on transitioning to a new aggregator (github.com/bozp-pzob/ai-news) that includes additional features like market summaries but faces issues with JSON uploads.\n- **Delivery Format Decision**: The team is considering different delivery formats (pre-rendered cutscene video vs. in-browser embedded playback).\n- **AI Personalities**: Development of character personalities for Shaw, Eliza, Degen Sparan, Peepo, and Cyborg Marc is in progress.\n- **Infrastructure Needs**: The project requires someone to host the aggregator on a persistent server to provide daily JSON updates at a consistent URL.\n\n## Key Questions & Answers\n\n### ElizaOS Technical\n- **Q**: How does DeepSeek R1 compare to other models? \n **A**: \"It's cheaper than OpenAI with solid reasoning capabilities, and its RL part works well\" (ITZMIZZLE)\n\n- **Q**: How to use DeepSeek as a model provider? \n **A**: \"Add DeepSeek configuration to .env file\" ([elizaos] )\n\n- **Q**: How to fix Twitter login issues on a VPS? \n **A**: \"Set up a proxy on the VPS to login with that IP and complete 2FA\" (shvedity)\n\n- **Q**: How should secrets be configured for multiple agents? \n **A**: \"Secrets can be defined in each agent's character JSON file for specific configurations\" (sb)\n\n- **Q**: How to stop agents from using em dashes in replies? \n **A**: \"Add specific instructions to replace them with semicolons, commas, or periods\" (mark rizzn hopkins)\n\n### Tokenomics & Investment\n- **Q**: How will the DAO's treasury assets be utilized? \n **A**: \"The assets will be deployed into one-sided LPs paired with AI16Z tokens to create buy pressure and provide liquidity for partner tokens\" (shaw)\n\n- **Q**: How will ai16z differentiate in the saturated launchpad space? \n **A**: \"By offering Solana agents with 50+ plugins and focusing on new users rather than expecting projects to port over\" (DorianD)\n\n- **Q**: Could ai16z function as a tier-1 investor alongside traditional VCs? \n **A**: \"It's possible if leveraging the community of 100,000+ partners who could support portfolio companies, though likely would need connections like a16z for deal flow\" (mat)\n\n- **Q**: How does the liquidity pooling help the AI16Z token? \n **A**: \"It creates additional volume and liquidity fees for the DAO\" (shaw and jin)\n\n### AI Portfolio & Projects\n- **Q**: How do I get involved in the AI portfolio? \n **A**: \"Holding the AI16Z token gives you exposure to the portfolio managed by AI MARC. Check pump.fun for the whitepaper.\" (Phoenix | Livepeer-Eliza.com)\n\n- **Q**: Thoughts on Virtuals Solana announcement? \n **A**: \"Feels like they want to capitalize on the SOL halo effect with no real value proposition for users; mostly monetary incentives to boost agent growth; 'meh' overall\" (smetter)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **Helper**: sb | **Helpee**: Bizzo \n **Context**: Agent defaulting to largest model despite configuration \n **Resolution**: Explained that character settings take priority over .env and provided correct configuration format\n\n- **Helper**: fourcolors | **Helpee**: MochinoLabs \n **Context**: Build errors with mistral model interface \n **Resolution**: Provided solution involving package.json overrides and version bumps\n\n- **Helper**: Amir_qfwri | **Helpee**: Sergey Danilovich \n **Context**: Using Supabase instead of local database \n **Resolution**: Instructed to add POSTGRES_URL in .env file with Supabase connection string\n\n- **Helper**: [elizaos] | **Helpee**: mike\ud83c\udded\ud83c\uddfa \n **Context**: Running multiple agents with different Twitter credentials \n **Resolution**: Explained how to create different character.json files with their own credentials\n\n### Project Guidance\n- **Helper**: timshel | **Helpee**: DorianD \n **Context**: Needed clarity on ai16z's strategic vision \n **Resolution**: Provided detailed framework of \"attention/code/capital\" and outlined potential for ai16z to function as a venture investor\n\n- **Helper**: Ka_yari | **Helpee**: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f \n **Context**: Anxiety about AI16Z price drops \n **Resolution**: Advised that projects with this level of ambition take time, highlighted the tech and developer interest as reassuring factors\n\n- **Helper**: avirtualfuture | **Helpee**: Dilettante \n **Context**: Understanding DeepSeek's impact on AI industry \n **Resolution**: Explained that open source can implement state-of-the-art without self-nerfing, creating pressure on closed models\n\n## Action Items\n\n### Technical\n- Fix WebAssembly SIMD support issues when running ElizaOS on VMs (Deepdelver)\n- Resolve @discordjs/opus installation issues (David_Dyor)\n- Fix RAG lookup from knowledge which appears to be broken (kAI wilder)\n- Implement solution for agents stuck in endless reply loops on Twitter ([elizaos] )\n- Fix Discord integration infinite loop issue (mark rizzn hopkins)\n- Resolve issue with headless mode not being respected by new front end (mark rizzn hopkins)\n- Fix Twitter client to handle 2FA and suspicious login detection (multiple users)\n- Implement proper DeepSeek R1 integration with ElizaOS (multiple users)\n- Implement one-sided liquidity pools with treasury assets paired against AI16Z (shaw)\n- Consider Orca pool for the DefAI strategy ([[{{,,,}}]])\n- Explore implementation of agent-controlled token distribution to reward quality interactions (DorianD)\n- Investigate TrustDB metadata buying/selling between node instances (DorianD)\n- Fix bug preventing new aggregator from uploading latest JSON updates (jin)\n- Implement support for the new version of news aggregator response that includes images in Unity frontend (SM Sith Lord)\n- Host the aggregator on an always-up node.js server or GitHub Pages for persistent daily JSON URL (SM Sith Lord and jin)\n- Integrate Eliza framework features into DegenAI to create a \"super agent\" (tigerguo)\n- Investigate and address Aiora platform issues (Bogdanoff)\n\n### Documentation\n- Create guide for embedding API credentials in character JSON files (Mr. Stark)\n- Update tokenomics documentation (witch)\n- Update contribution docs to clarify PR should point to develop branch (pixel_pavel)\n- Create guide for setting up and using the Solana plugin ([elizaos] )\n- Develop CLI that allows selecting packages to include on install and update (luccasveg)\n- Update the awesome-eliza GitHub repository with ecosystem developments (jin)\n- Break up DAO tokenomics explanations into separate parts (shaw)\n- Create clearer onboarding information for AI16Z portfolio participation (David_Dyor)\n- Create hackmd progress logs to track development (jin)\n- Develop brand guidelines based on Degen's lore (rhota)\n- Create and publish website roadmap and tokenomics (tigerguo)\n\n### Features\n- Add ability to augment character knowledge after deployment (veTechno)\n- Implement tweet automation with conditional emoji usage (dragonlord)\n- Implement feature to hide non-dialogue text in agent conversations (David_Dyor)\n- Add support for multiple plugins in a single character (eliza builder)\n- Implement user restriction for on-chain interactions (El Pulpo \ud83d\udc19)\n- Create configurable Twitter actions with rate limiting and execution limits (Addy)\n- Implement new knowledge system for easier document ingestion (Mad)\n- Add support for PDF files in knowledge system (veTechno)\n- Develop revenue sharing mechanism for ai16z token to anticipate market trends (mat)\n- Create agent launchpad with bonding curve AMM for token launches (unreadyplayer)\n- Implement agent tokens paired with ai16z to compete with Virtuals (unreadyplayer)\n- Develop wallet/trading/defi management services through agents (mat)\n- Create social account management services through agents (mat)\n- Launch no-code launchpad platform (shaw)\n- Consider text-to-GLTF functionality (avirtualfuture)\n- Explore potential for L1/L2 solution for agent data storage (avirtualfuture)\n- Discuss rebranding strategies (jin)\n- Decide on delivery format (pre-rendered cutscene vs. in-browser playback) (SM Sith Lord)\n- Establish repository for consistent personality profiles (SM Sith Lord)\n- Schedule regular check-in calls and establish timelines (shaw)\n- Create more AI personality profiles for characters (Degen Sparan/Peepo/Cyborg Marc) (SM Sith Lord)\n- Implement Web3 industry tools for token analysis, blockchain transactions, and LP yield optimization (tigerguo)\n- Token-gated access to premium features (tigerguo)\n- Expand elizaOS Agent marketplace to Solana blockchain (\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)" }, "ai_news_elizaos_discord_md_2025-01-24": { "filename": "2025-01-24.md", "content": "# elizaOS Discord - 2025-01-24\n\n## Overall Discussion Highlights\n\n### Technical Development\n- **ElizaOS v2 Development**: The team is working toward a v2 release, potentially targeting March-April, with a v1.5 plugin architecture being developed as an interim step.\n- **DeepSeek Integration**: Significant discussion about integrating DeepSeek's R1 model with ElizaOS, with jin confirming it's technically simple via OpenRouter and will be tested with DegenAI soon. The model reportedly performs well for tool/action calling without requiring GPU resources.\n- **Embedding Dimension Issues**: Multiple users encountered vector dimension mismatches (384 vs 1536) when configuring different embedding models, resolved by setting `USE_OPENAI_EMBEDDING=TRUE` in the .env file.\n- **Node.js Compatibility**: Several users struggled with Node.js version compatibility, with v23.3.0 being recommended over newer versions.\n- **RAG Implementation**: Discussions about implementing Retrieval Augmented Generation for knowledge management, with documentation shared on loading large documents into the knowledge base.\n- **TrustDB Technology**: DorianD highlighted TrustDB as a solution for decentralized trust relationships between agents, potentially eliminating the need for centralized verification systems.\n\n### Platform & Ecosystem\n- **Tokenomics Debate**: Extensive discussion about ai16z tokenomics models, with competing approaches between simple, proven models versus more complex systems with additional utility.\n- **Market Conditions**: Partners expressed concerns about AI16Z token price declines due to whale sell-offs, though some maintained conviction citing GitHub activity (7k new stars, 500+ pull requests) and growing holder numbers.\n- **Partnerships**: Announcement of a partnership with Virtuals on Solana, and discussions about potential collaborations with Centrifuge for tokenization.\n- **Block Tank Initiative**: Jin mentioned a \"Block Tank\" concept (AI investor simulation for project evaluation) that would help scale/decentralize decision making.\n- **3D AI TV Project**: Development of a space-themed virtual environment for an AI-powered TV show with multiple camera angles and AI personalities presenting content.\n\n### Agent Development\n- **Twitter Integration Challenges**: Several users struggled with Twitter integration, particularly with authentication issues and controlling agent behavior (retweets, replies, original posts).\n- **Character Configuration**: Extensive discussion about setting model providers and secrets within character JSON files versus global .env settings.\n- **LLM Integration**: Community explored integration with various LLMs, with particular interest in DeepSeek-R1's reasoning capabilities compared to other models like Claude and GPT.\n- **Mobile Applications**: Discussion about potential Android app for running DeepSeek model on phones without cloud hosting dependencies.\n\n## Key Questions & Answers\n\n**Q: How do I fix the \"Vector dimension mismatch\" error?** \nA: Set `USE_OPENAI_EMBEDDING=TRUE` in your .env file (answered by boja)\n\n**Q: Is there a way to make an agent ONLY reply to tweets and not create original tweets?** \nA: Comment out this line: https://github.com/elizaOS/eliza/blob/6490485e5bb142336208a116f903446a2dd4db38/packages/client-twitter/src/post.ts#L289 (answered by tcm390)\n\n**Q: How do I load large text documents into the knowledge database?** \nA: Use the processCharacterRAGKnowledge function in the codebase (answered by Qu\u0103ng)\n\n**Q: Will DeepSeek be integrated with ElizaOS?** \nA: Technically since OpenRouter supports it, we can change to DeepSeek in 1 line of code. Will be testing with DegenAI soon. (answered by jin)\n\n**Q: How do I fix the version mismatch error from @ai-sdk/provider?** \nA: Update \"@ai-sdk/mistral\" to version \"1.0.9\" (answered by elizaos-bridge-odi)\n\n**Q: How do I get my agent to respond to Telegram group messages?** \nA: Make sure the bot is admin and has message permissions in the group, and users need to tag the bot (answered by meowtoshi)\n\n**Q: How does the proposed bonding curve + dual pool structure work?** \nA: It's similar to Virtuals launchpad but not exactly the same. Virtuals uses a single pool, and once a token graduates from the bonding curve, a single agent/virtuals pair is created. (answered by BigChungus)\n\n**Q: Is it possible to edit prompted songs to remove one vocalist?** \nA: Not yet, but you could remove vocals with another AI tool and then upload with new lyrics in Suno (answered by boom)\n\n## Community Help & Collaboration\n\n- **Embedding Dimension Fix**: boja helped j. resolve vector dimension mismatch errors by suggesting setting USE_OPENAI_EMBEDDING=TRUE in .env file.\n\n- **Twitter Configuration**: tcm390 helped RoomTemp IQ disable original tweets while keeping replies by providing the specific code line to comment out.\n\n- **Telegram Bot Setup**: meowtoshi assisted flck with Telegram bot permissions, explaining that bots need to be tagged in groups and have proper admin permissions.\n\n- **ElizaOS Setup Guide**: warfreakzplays created a detailed guide document for proper Eliza setup after seeing j. struggle with persistent embedding errors.\n\n- **DeepSeek Integration**: Kraus confirmed successful testing of DeepSeek with Eliza for Display Name and suggested using the chat model instead of reasoning model if needed.\n\n- **Solana Development**: elev8blyss offered help with Solana program deployments to Alsara2k, with Patt vouching for their skills.\n\n- **News Aggregator Troubleshooting**: SM Sith Lord helped boom with a non-updating news aggregator by suggesting config adjustments and providing information about the new version with images.\n\n- **Whale Tracking**: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f provided wallet addresses and transaction details of major sellers affecting AI16Z price to help partners understand market movements.\n\n## Action Items\n\n### Technical\n- Fix Twitter client to properly handle reply-to-reply interactions (Mentioned by ant)\n- Fix RAG knowledge retrieval in develop branch (Mentioned by kAI wilder)\n- Update trustDB implementation and consider moving it into core as an extension (Mentioned by 0xbbjoker)\n- Fix version conflict between @ai-sdk/provider and @ai-sdk/mistral (Mentioned by JobyID)\n- Fix Discord client token validation (Mentioned by Mayor)\n- Integrate DeepSeek models with ElizaOS via OpenRouter (Mentioned by jin)\n- Develop plugin architecture for v1.5 (Mentioned by jin)\n- Complete text-to-GLTF functionality before Eliza v2 release (Mentioned by avirtualfuture)\n- Check if Collab-land bot is running routine audits of wallets for role verification (Mentioned by kalshnikov)\n- Support the new version of news aggregator response that includes images (Mentioned by SM Sith Lord)\n- Fix bugs in news aggregator that's showing errors (Mentioned by SM Sith Lord)\n- Implement lighting from cubemap for black areas in 3D environment (Mentioned by SM Sith Lord)\n- Fix issue with news aggregator not uploading latest updates (Mentioned by jin)\n- Implement a dual pool structure for the agent marketplace similar to Virtuals (Mentioned by BigChungus)\n- Explore integration of TrustDB for decentralized agent verification (Mentioned by DorianD)\n- Develop Block Tank simulation for agent evaluation (Mentioned by jin)\n\n### Feature Requests\n- Add support for Notion integration (Mentioned by Vesper)\n- Implement dynamic loading of topics for character.json (Mentioned by HamsterdamCapital)\n- Add option to disable original tweets while keeping replies (Mentioned by RoomTemp IQ)\n- Create plugin for Zerion integration (Mentioned by Pranav)\n- Create an Android app for Eliza to run DeepSeek model on phones without cloud hosting (Mentioned by Display Name)\n- Expand Eliza to Base blockchain with exclusive elizaOS Agent marketplace tied to token (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- Launch Eliza on Solana blockchain (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- Add boosters, panels and wires to the space station set for 3D AI TV (Mentioned by boom)\n- Add more \"TVs\" and an LED desk to the 3D set (Mentioned by boom)\n- Implement staking for AI16Z token (Mentioned by ElonMoney)\n- Position AI16Z as primary token for entire ecosystem (Mentioned by ElonMoney)\n- Create token buyback mechanism using launchpad revenue (Mentioned by ElonMoney)\n- Launch agent marketplace with multi-chain approach (Base and Solana) (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- Add Ethereum support to the launchpad (Mentioned by mat)\n- Create a mechanism for agents to distribute tokens to users who impress them (Mentioned by DorianD)\n- Implement a revenue sharing mechanism through the ai16z token (Mentioned by mat)\n- Develop a trust delegation market for agent creators (Mentioned by bong49)\n\n### Documentation\n- Create guide for loading large documents into knowledge base (Mentioned by kAI wilder)\n- Update contribution docs to clarify PR should point to develop branch not main (Mentioned by pixel_pavel)\n- Document how to configure multiple agents with different settings (Mentioned by Pouncer_)\n- Update awesome-eliza GitHub repository with ecosystem information (Mentioned by jin)\n- Create temp tattoos with Eliza OS logo for Denver and SXSW events (Mentioned by Astrid)\n- Create a document explaining the \"attention/code/capital\" framework (Mentioned by timshel)\n- Document the purpose of proposed value engines (Mentioned by yikesawjeez)\n- Prepare slides explaining Block Tank value proposition (Mentioned by jin)\n- Announce full-time team and official labs (Mentioned by Amie | Eliza Labs)\n- Create repository for AI personality profiles (Mentioned by SM Sith Lord)" }, "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_daily_json_2025-01-25": { "filename": "2025-01-25.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-01-25", "categories": [ { "title": "DankVR and Shaw's Recent Twitter Activities", "content": [ { "text": "DankVR (@dankvr) announced a new AI x VC game show in collaboration with @ai16zdao and @ElizaOS_ai. The trailer was released with more information and a demo promised for the following day. The concept involves pitching ideas to AI judges in a simulation.", "sources": "https://twitter.com/dankvr/status/1882956781179322529", "images": "https://pbs.twimg.com/ext_tw_video_thumb/1882945167230996480/pu/img/Dwu1W8cS3YjCURBo.jpg", "videos": "https://video.twimg.com/ext_tw_video/1882945167230996480/pu/vid/avc1/1280x720/70BwMvt5xRn8-CYW.mp4?tag=12" }, { "text": "DankVR mentioned that ElizaOS has multiple clients and shared images demonstrating this. He also discussed the possibility of achievements, whitelists, and airdrops for people who build things, suggesting NFTs that can only be earned rather than bought.", "sources": "https://twitter.com/dankvr/status/1883198938347716853, https://twitter.com/dankvr/status/1883061730663919938", "images": "https://pbs.twimg.com/media/GiJ3MwrW8AAspPk.png", "videos": "" }, { "text": "Shaw (@shawmakesmagic) announced the Jupiter Exchange x ElizaOS MAGIC FUND, aimed at accelerating 'ambitious founders building gud tek' who are creating technology for a brighter future.", "sources": "https://twitter.com/shawmakesmagic/status/1883124194013319340", "images": "https://pbs.twimg.com/media/GiIws0Ga0AAPWLb.jpg", "videos": "" }, { "text": "Shaw shared thoughts on DeFi interfaces, suggesting that chat interfaces powered by LLMs would be better than current complex DeFi pages that confuse average users who have 'billions of dollars in their wallets'.", "sources": "https://twitter.com/shawmakesmagic/status/1883266852350210431", "images": "https://pbs.twimg.com/media/GiK07uibEAENxTp.jpg,https://pbs.twimg.com/media/GiK07ukboAAeLVv.jpg", "videos": "" }, { "text": "Shaw also discussed AI's impact on jobs, suggesting that while AI will replace most jobs, this could be positive as 'most jobs suck' and humans could focus on more meaningful activities if the benefits of automated labor are properly distributed.", "sources": "https://twitter.com/shawmakesmagic/status/1883161966350569629, https://twitter.com/shawmakesmagic/status/1883264830049824829", "images": "", "videos": "" } ], "topic": "tweet" }, { "title": "Recent ElizaOS Updates: New Plugins, Features, and Bug Fixes", "content": [ { "text": "## New Plugins\n\nElizaOS has added several new plugins to enhance functionality:\n\n- **Ankr plugin** (#2773) - Integration with Ankr blockchain infrastructure\n- **Zerion plugin** (#2766) - For DeFi portfolio management\n- **Moralis plugin** (#2764) - Web3 development tools integration\n- **Form chain plugin** (#2728) - Form processing capabilities\n- **Intelligent email evaluation and automation** (#2709) - Email processing features\n- **Bittensor bitmind API** (#2682) - Integration with Bittensor network\n- **DCAP plugin** (#2638) - Data Confidentiality Attestation Protocol\n- **Mind Network plugin** (#2431) - Decentralized AI infrastructure\n- **Quick intel plugin** (#2391) - Token security analysis\n- **News plugin** (#1248) - News aggregation and analysis\n- **Edriziai Startup Mentor AI Assistant** (#2687) - AI-powered startup mentorship", "sources": [ "https://github.com/elizaOS/eliza/pull/2773", "https://github.com/elizaOS/eliza/pull/2766", "https://github.com/elizaOS/eliza/pull/2764", "https://github.com/elizaOS/eliza/pull/2728", "https://github.com/elizaOS/eliza/pull/2709", "https://github.com/elizaOS/eliza/pull/2682", "https://github.com/elizaOS/eliza/pull/2638", "https://github.com/elizaOS/eliza/pull/2431", "https://github.com/elizaOS/eliza/pull/2391", "https://github.com/elizaOS/eliza/pull/1248", "https://github.com/elizaOS/eliza/pull/2687" ], "images": [], "videos": [] }, { "text": "## Feature Enhancements\n\n- **Amazon Bedrock** added as an LLM provider (#2769)\n- **MultiversX plugin** improvements with swap functionality (#2651)\n- **Solana web3.js V2** integration with automated LPing on Orca (#2136)\n- **MongoDB adaptor** for database integration (#1427)\n- **Alexa skill notification** basic functionality (#2564)\n- **Turbo cache** configuration improvements (#2768, #2775)", "sources": [ "https://github.com/elizaOS/eliza/pull/2769", "https://github.com/elizaOS/eliza/pull/2651", "https://github.com/elizaOS/eliza/pull/2136", "https://github.com/elizaOS/eliza/pull/1427", "https://github.com/elizaOS/eliza/pull/2564", "https://github.com/elizaOS/eliza/pull/2768", "https://github.com/elizaOS/eliza/pull/2775" ], "images": [], "videos": [] }, { "text": "## Bug Fixes\n\n- Fixed Twitter homeTimeline name parsing bug (#2789)\n- Resolved topics formatting bug in composeState (#2788)\n- Fixed ethers/viem issue in mind network plugin (#2783)\n- Corrected DTS error mismatch in ai-sdk mistral model (#2782)\n- Made template message footer more explicit (#2774)\n- Fixed path issues across all files (#2763)\n- Resolved goal updating bug in goal evaluator's handler (#2725, #2791)", "sources": [ "https://github.com/elizaOS/eliza/pull/2789", "https://github.com/elizaOS/eliza/pull/2788", "https://github.com/elizaOS/eliza/pull/2783", "https://github.com/elizaOS/eliza/pull/2782", "https://github.com/elizaOS/eliza/pull/2774", "https://github.com/elizaOS/eliza/pull/2763", "https://github.com/elizaOS/eliza/pull/2725", "https://github.com/elizaOS/eliza/pull/2791" ], "images": [], "videos": [] }, { "text": "## Documentation and Testing\n\n- Added documentation on configuring secrets for multi-agent workflows (#2632)\n- Added one-click deployment documentation (#2631)\n- Improved testing for plugin abstract with test config (#2621)\n- Updated tokenContract.ts in Coinbase plugin (#2781)\n- Added custom TEE log path functionality (#2616)", "sources": [ "https://github.com/elizaOS/eliza/pull/2632", "https://github.com/elizaOS/eliza/pull/2631", "https://github.com/elizaOS/eliza/pull/2621", "https://github.com/elizaOS/eliza/pull/2781", "https://github.com/elizaOS/eliza/pull/2616" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Recent GitHub Issues in the elizaOS/eliza Repository", "content": [ { "text": "Several feature requests and enhancement proposals have been submitted to the elizaOS/eliza repository:\n\n- DaveSimoes proposed adding a GUI feature (#2787)\n- metakai1 suggested enhancing INFO logging for successful RAG knowledge vector matches (#2785)\n- Sleepyhead01 requested a Twitter user tracker query feature (#2776)\n- wtfsayo proposed setting up one-click deployment options for both Render.com (#2780) and DigitalOcean (#2779)\n- fifahuihua suggested adding a new plugin called 'plugin-apro' (#2793)", "sources": [ "https://github.com/elizaOS/eliza/issues/2787", "https://github.com/elizaOS/eliza/issues/2785", "https://github.com/elizaOS/eliza/issues/2776", "https://github.com/elizaOS/eliza/issues/2780", "https://github.com/elizaOS/eliza/issues/2779", "https://github.com/elizaOS/eliza/issues/2793" ], "images": [], "videos": [] }, { "text": "Several users have reported technical issues with the application:\n\n- actuallyrizzn reported two separate issues: an infinite typing loop in Discord integration (#2792) and problems with the headless web interface not connecting in version 0.1.8+build-1 (#2795)\n- nicky-ru identified a message ID collision issue in the Telegram client (#2796)\n- imransbaig reported that the application won't run on Replit (#2803)", "sources": [ "https://github.com/elizaOS/eliza/issues/2792", "https://github.com/elizaOS/eliza/issues/2795", "https://github.com/elizaOS/eliza/issues/2796", "https://github.com/elizaOS/eliza/issues/2803" ], "images": [], "videos": [] } ], "topic": "issue" }, { "title": "Recent Pull Requests in the elizaOS/eliza Repository", "content": [ { "text": "The elizaOS/eliza repository has seen several new pull requests focused on adding new plugins and improving existing functionality. Recent PRs include:\n\n- Commerce cleanup and plugin testing (PR #2790)\n- Addition of the Ankr plugin (PR #2773)\n- Intelligent email evaluation and automation plugin (PR #2709)\n- Access Token Management implementation (PR #2808)\n- Deribit client and plugin (PR #2809)\n- Gelato plugin relay creation (PR #2799)\n- APRO plugin support (PR #2794)\n- News plugin (PR #1248)\n\nThese pull requests demonstrate ongoing development to expand the platform's capabilities through various plugins covering finance, commerce, communication, and information services.", "sources": [ "https://github.com/elizaOS/eliza/pull/2790", "https://github.com/elizaOS/eliza/pull/2773", "https://github.com/elizaOS/eliza/pull/2709", "https://github.com/elizaOS/eliza/pull/2808", "https://github.com/elizaOS/eliza/pull/2809", "https://github.com/elizaOS/eliza/pull/2799", "https://github.com/elizaOS/eliza/pull/2794", "https://github.com/elizaOS/eliza/pull/1248" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2790", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2773", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2709", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2808", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2809", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2799", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2794", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/1248" ], "videos": [] } ], "topic": "pull_request" }, { "title": "ElizaOS GitHub Activity Update", "content": [ { "text": "The elizaos/eliza repository showed significant activity over a two-day period. From January 25-26, 2025, there were 16 new pull requests with 29 merged, 6 new issues created, and 42 active contributors. Activity decreased slightly the following day (January 26-27, 2025) with 12 new pull requests, only 2 of which were merged, 8 new issues, and 21 active contributors. Overall, the project maintained substantial development momentum with continued contributions and issue tracking.", "sources": [ 0, 1 ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Top contributors for elizaOS/eliza", "content": [ { "text": "The provided sources mention 'Top contributors for elizaOS/eliza' but do not provide any specific details about who these contributors are or their contributions to the project. Without additional information, it's not possible to generate a detailed summary about the individual contributors, their roles, or the nature of their contributions to the elizaOS/eliza project.", "sources": [ "Top contributors for elizaOS/eliza" ], "images": [], "videos": [] } ], "topic": "contributors" } ], "date": 1737763200 } }, "ai_news_elizaos_daily_md_2025-01-25": { "filename": "2025-01-25.md", "content": "# DankVR and Shaw's Recent Twitter Activities\n\n- DankVR (@dankvr) announced a new AI x VC game show in collaboration with @ai16zdao and @ElizaOS_ai\n - Released trailer with demo promised for the following day\n - Concept involves pitching ideas to AI judges in a simulation\n- DankVR mentioned ElizaOS has multiple clients\n - Discussed possibilities for achievements, whitelists, and airdrops\n - Suggested NFTs that can only be earned rather than bought\n- Shaw (@shawmakesmagic) announced the Jupiter Exchange x ElizaOS MAGIC FUND\n - Fund aims to accelerate \"ambitious founders building gud tek\"\n- Shaw shared thoughts on DeFi interfaces\n - Suggested chat interfaces powered by LLMs would improve user experience\n- Shaw discussed AI's impact on jobs\n - Noted potential positive outcomes if benefits of automated labor are properly distributed\n\n# Recent ElizaOS Updates\n\n## New Plugins\n- Ankr plugin - Integration with Ankr blockchain infrastructure\n- Zerion plugin - For DeFi portfolio management\n- Moralis plugin - Web3 development tools integration\n- Form chain plugin - Form processing capabilities\n- Intelligent email evaluation and automation - Email processing features\n- Bittensor bitmind API - Integration with Bittensor network\n- DCAP plugin - Data Confidentiality Attestation Protocol\n- Mind Network plugin - Decentralized AI infrastructure\n- Quick intel plugin - Token security analysis\n- News plugin - News aggregation and analysis\n- Edriziai Startup Mentor AI Assistant - AI-powered startup mentorship\n\n## Feature Enhancements\n- Amazon Bedrock added as an LLM provider\n- MultiversX plugin improvements with swap functionality\n- Solana web3.js V2 integration with automated LPing on Orca\n- MongoDB adaptor for database integration\n- Alexa skill notification basic functionality\n- Turbo cache configuration improvements\n\n## Bug Fixes\n- Fixed Twitter homeTimeline name parsing bug\n- Resolved topics formatting bug in composeState\n- Fixed ethers/viem issue in mind network plugin\n- Corrected DTS error mismatch in ai-sdk mistral model\n- Made template message footer more explicit\n- Fixed path issues across all files\n- Resolved goal updating bug in goal evaluator's handler\n\n## Documentation and Testing\n- Added documentation on configuring secrets for multi-agent workflows\n- Added one-click deployment documentation\n- Improved testing for plugin abstract with test config\n- Updated tokenContract.ts in Coinbase plugin\n- Added custom TEE log path functionality\n\n# Recent GitHub Issues\n\n## Feature Requests\n- GUI feature proposal\n- Enhanced INFO logging for successful RAG knowledge vector matches\n- Twitter user tracker query feature\n- One-click deployment options for Render.com and DigitalOcean\n- New 'plugin-apro' proposal\n\n## Technical Issues\n- Infinite typing loop in Discord integration\n- Headless web interface connection problems in version 0.1.8+build-1\n- Message ID collision issue in the Telegram client\n- Application not running on Replit\n\n# Recent Pull Requests\n\n- Commerce cleanup and plugin testing\n- Addition of the Ankr plugin\n- Intelligent email evaluation and automation plugin\n- Access Token Management implementation\n- Deribit client and plugin\n- Gelato plugin relay creation\n- APRO plugin support\n- News plugin\n\n# ElizaOS GitHub Activity Update\n\n- January 25-26, 2025:\n - 16 new pull requests with 29 merged\n - 6 new issues created\n - 42 active contributors\n- January 26-27, 2025:\n - 12 new pull requests with 2 merged\n - 8 new issues\n - 21 active contributors" }, "ai_news_elizaos_daily_discord_json_2025-01-25": { "filename": "2025-01-25.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-01-25", "date": 1737763200, "stats": { "totalMessages": 1716, "totalUsers": 275 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Analysis of Discord Chat in \"discussion\" Channel\n\n## 1. Summary\nThe chat primarily consists of casual conversation with minimal technical discussion. There are a few notable technical topics:\n\n- A user (David_Dyor) encountered issues installing @discordjs/opus, receiving a 404 error when attempting to download pre-built binaries. Another user (0xCatnipKing) suggested dropping the \"js\" part of the package name.\n\n- Mr. Stark shared a solution for embedding Twitter API credentials into character JSON files for ElizaOS agents, providing the correct format structure.\n\n- A user (Deepdelver) experienced runtime errors related to WebAssembly SIMD support when trying to build ElizaOS on a VM, specifically mentioning \"Wasm SIMD unsupported\" errors.\n\n- There were questions about ElizaOS functionality, including how to augment a character's knowledge base after deployment, limiting on-chain interactions to a single user, and using multiple plugins simultaneously.\n\n- A brief mention of a \"memory issue fixed\" by 0xCatnipKing suggests some development progress.\n\n- YoungPhlo mentioned transcribing/summarizing notes from Twitter Spaces sessions, which appears to be a regular community service.\n\nThe chat contains minimal substantive technical discussion, with most messages being greetings, token price speculation, and casual conversation.\n\n## 2. FAQ\nQ: How do I make my eliza tweet an emoji every 10th tweet? (asked by dragonlord) A: Check the agent dev school channel for tweet automation stuff (answered by BOSSU)\nQ: Is it possible to augment a character's knowledge once they are live? (asked by veTechno) A: Head to the coders channel for knowledge augmentation questions (answered by BOSSU)\nQ: How can I hide the non-dialogue text that appears when chatting with the agent? (asked by David_Dyor) A: Unanswered\nQ: Can we use 2 plugins simultaneously in a single character in eliza? (asked by eliza builder) A: Unanswered\nQ: How do I get my agent to listen to system prompts? (asked by dragonlord) A: Unanswered\nQ: Is there anyone that figured out how to limit the number of users capable of asking the agent for on-chain interaction to 1? (asked by El Pulpo \ud83d\udc19) A: Unanswered\nQ: Do I need nodeshift to run eliza? (asked by crypto night) A: Unanswered\n\n## 3. Help Interactions\nHelper: 0xCatnipKing | Helpee: David_Dyor | Context: Issues installing @discordjs/opus package | Resolution: Suggested dropping the \"js\" part of the package name\nHelper: Mr. Stark | Helpee: Community | Context: Embedding Twitter API credentials in character JSON files | Resolution: Shared correct format structure for embedding credentials\nHelper: YoungPhlo | Helpee: Jet | Context: Difficulty identifying speakers in Twitter Spaces | Resolution: Explained that speakers' names light up with a purple indicator when speaking\nHelper: [[{{,,,}}]] | Helpee: Bogdanoff | Context: Concerns about Aiora project status | Resolution: Explained that platforms were down due to a critical bug and that the team was working on it\n\n## 4. Action Items\nTechnical: Fix WebAssembly SIMD support issues when running ElizaOS on VMs | Description: Runtime errors occur with message \"Wasm SIMD unsupported\" | Mentioned By: Deepdelver\nTechnical: Resolve @discordjs/opus installation issues | Description: Pre-built binaries not found at expected URL | Mentioned By: David_Dyor\nTechnical: Implement feature to hide non-dialogue text in agent conversations | Description: Hide memory logs and create-text for cleaner UI | Mentioned By: David_Dyor\nTechnical: Add support for multiple plugins in a single character | Description: Allow characters to use multiple plugins simultaneously | Mentioned By: eliza builder\nTechnical: Implement user restriction for on-chain interactions | Description: Limit on-chain interaction capability to a single user | Mentioned By: El Pulpo \ud83d\udc19\nDocumentation: Create guide for embedding API credentials in character JSON files | Description: Document the correct format for Twitter API credentials | Mentioned By: Mr. Stark\nDocumentation: Update tokenomics documentation | Description: Provide clear information about upcoming tokenomics changes | Mentioned By: witch\nFeature: Add ability to augment character knowledge after deployment | Description: Allow adding new knowledge (e.g., PDFs) to existing agents | Mentioned By: veTechno\nFeature: Implement tweet automation with conditional emoji usage | Description: Allow agents to tweet emojis at specific intervals | Mentioned By: dragonlord", "messageCount": 439, "userCount": 109 }, { "channelId": "1300025221834739744", "channelName": "\ud83d\udcbb-coders", "summary": "# Analysis of \ud83d\udcbb-coders Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS agent development issues and solutions. Key technical discussions include:\n\nDeepSeek R1 model integration, with users reporting positive experiences regarding its reasoning capabilities and cost-effectiveness compared to OpenAI. Several users are exploring how to properly configure DeepSeek as a model provider in their agents.\n\nTwitter/X integration challenges are prevalent, with many users experiencing login failures, authentication issues, and problems with agents posting in incorrect formats (like JSON or including thinking monologues). Solutions discussed include using VPNs, setting up proxies, and verifying accounts with blue checks to prevent suspicious login flags.\n\nDatabase configuration is another focus area, with discussions about switching from SQLite to PostgreSQL/Supabase for better persistence. Users are implementing knowledge systems to allow agents to access and utilize stored information.\n\nCharacter file configuration issues appear frequently, with users struggling to properly set up model providers, plugins, and client integrations. The community is actively helping troubleshoot installation problems across different operating systems.\n\nPlugin development and customization is a significant topic, with users creating and modifying plugins for various functionalities like Solana blockchain integration, web search, and Twitter actions.\n\n## 2. FAQ\nQ: How does DeepSeek R1 compare to other models? (asked by Saitamai) A: It's cheaper than OpenAI with solid reasoning capabilities, and its RL part works well (answered by ITZMIZZLE)\nQ: Is RAG lookup from knowledge broken? (asked by kAI wilder) A: Unanswered\nQ: How should secrets be configured for multiple agents? (asked by ! m\u144cGET\u1515\u144c !) A: Secrets can be defined in each agent's character JSON file for specific configurations (answered by sb)\nQ: How to integrate ElizaOS with a frontend website? (asked by xfajarr.) A: Unanswered\nQ: How to stop agents from posting the thinking monologue on Twitter? (asked by Blues_Clue) A: Unanswered\nQ: How to fix Twitter login issues on a VPS? (asked by shvedity) A: Set up a proxy on the VPS to login with that IP and complete 2FA (answered by shvedity)\nQ: How to use DeepSeek as a model provider? (asked by \ud83c\udf08\u20e4 \u2728\u2b52\u0e4b\u08ed\u2b51\u3010=\u035f\u035f\u035e\ud83c\udf08\u20e4 \u2b52\u0e4b\u08ed\u2b51.) A: Add DeepSeek configuration to .env file (answered by [elizaos] )\nQ: How to integrate Eliza with Notion? (asked by Vesper) A: It's possible and agents could be the new websites (answered by jin)\nQ: How to stop agents from using em dashes in replies? (asked by rouss) A: Add specific instructions to replace them with semicolons, commas, or periods (answered by mark rizzn hopkins)\n\n## 3. Help Interactions\nHelper: sb | Helpee: Bizzo | Context: Agent defaulting to largest model despite configuration | Resolution: Explained that character settings take priority over .env and provided correct configuration format\nHelper: fourcolors | Helpee: MochinoLabs | Context: Build errors with mistral model interface | Resolution: Provided solution involving package.json overrides and version bumps\nHelper: kAI wilder | Helpee: Haphazardly | Context: Evaluator handler not executing | Resolution: Explained that handlers are only called under certain conditions and suggested setting it to always run\nHelper: EcchiPen | Helpee: \ud83e\udde7ThanosDaSith24\ud83e\udde7 | Context: Installation failing with plugin errors | Resolution: Suggested removing problematic plugins and rebuilding\nHelper: Amir_qfwri | Helpee: Sergey Danilovich | Context: Using Supabase instead of local database | Resolution: Instructed to add POSTGRES_URL in .env file with Supabase connection string\nHelper: [elizaos] | Helpee: mike\ud83c\udded\ud83c\uddfa | Context: Running multiple agents with different Twitter credentials | Resolution: Explained how to create different character.json files with their own credentials\n\n## 4. Action Items\nType: Technical | Description: Fix RAG lookup from knowledge which appears to be broken | Mentioned By: kAI wilder\nType: Technical | Description: Implement solution for agents stuck in endless reply loops on Twitter | Mentioned By: [elizaos] \nType: Technical | Description: Fix Discord integration infinite loop issue | Mentioned By: mark rizzn hopkins\nType: Technical | Description: Resolve issue with headless mode not being respected by new front end | Mentioned By: mark rizzn hopkins\nType: Technical | Description: Fix Twitter client to handle 2FA and suspicious login detection | Mentioned By: multiple users\nType: Technical | Description: Implement proper DeepSeek R1 integration with ElizaOS | Mentioned By: multiple users\nType: Feature | Description: Create configurable Twitter actions with rate limiting and execution limits | Mentioned By: Addy\nType: Feature | Description: Implement new knowledge system for easier document ingestion | Mentioned By: Mad\nType: Feature | Description: Add support for PDF files in knowledge system | Mentioned By: veTechno\nType: Documentation | Description: Update contribution docs to clarify PR should point to develop branch | Mentioned By: pixel_pavel\nType: Documentation | Description: Create guide for setting up and using the Solana plugin | Mentioned By: [elizaos] \nType: Documentation | Description: Develop CLI that allows selecting packages to include on install and update | Mentioned By: luccasveg", "messageCount": 643, "userCount": 120 }, { "channelId": "1300756641406521416", "channelName": "ideas-feedback-rants", "summary": "# Discord Channel Analysis: ideas-feedback-rants\n\n## 1. Summary\nThe chat segment primarily revolves around discussions about AI-related tokens and projects. Users are seeking clarification about how to participate in the AI16Z portfolio and expressing concerns about potential scams. Phoenix from Livepeer-Eliza.com confirms that AI MARC is managing a portfolio via AI16Z token, and holding the token provides exposure to this portfolio. There's mention that DegenSpartan AI operates on a similar model. The conversation also includes a suggestion to expand elizaOS Agent marketplace to Base blockchain while simultaneously launching on Solana to capitalize on market momentum. Jin notes that degenspartanai and elizaos are already on Base and multiple other blockchains. A music producer offers their services for an upcoming 3D TV show. Finally, there's a warning about a potential scam involving Aiora, with claims of non-functioning services and abandoned communication channels.\n\n## 2. FAQ\nQ: How do I get involved in the AI portfolio? (asked by David_Dyor) A: Holding the AI16Z token gives you exposure to the portfolio managed by AI MARC. Check pump.fun for the whitepaper. (answered by Phoenix | Livepeer-Eliza.com)\nQ: Do I have to convert SOL to DAO token? (asked by David_Dyor) A: You can buy AI16Z via Raydium. (answered by Phoenix | Livepeer-Eliza.com)\nQ: Can I take part in the music/audio side of the upcoming 3D TV show? (asked by Random Disco) A: Unanswered\n\n## 3. Help Interactions\nHelper: Phoenix | Livepeer-Eliza.com | Helpee: David_Dyor | Context: Confusion about how to participate in AI16Z portfolio | Resolution: Explained that holding the AI16Z token provides exposure and directed to pump.fun for whitepaper information.\nHelper: jin | Helpee: \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 | Context: Suggestion to expand to Base blockchain | Resolution: Clarified that degenspartanai and elizaos are already on Base and 20+ other blockchains.\n\n## 4. Action Items\nFeature: Expand elizaOS Agent marketplace to Solana blockchain | Description: Launch elizaOS on Solana while leveraging existing presence on Base | 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\nDocumentation: Create clearer onboarding information for AI16Z portfolio participation | Description: Users are confused about how to get involved with the AI portfolio | Mentioned By: David_Dyor\nTechnical: Investigate and address Aiora platform issues | Description: Reports of non-functioning services including Intel platform and Gen Image | Mentioned By: Bogdanoff", "messageCount": 7, "userCount": 6 }, { "channelId": "1308149076893630555", "channelName": "spartan_holders", "summary": "# Discord Chat Analysis for \"spartan_holders\" Channel\n\n## 1. Summary:\nThe conversation primarily revolves around the future development of DegenAI and its potential integration with the Eliza framework. Community members, particularly tigerguo, expressed interest in understanding how these two products might merge to create a \"super agent\" with enhanced capabilities. There are concerns about the lack of communication between developers and the community regarding roadmap, tokenomics, and future plans. Rhota, who appears to be a new organizer working alongside Skely, mentioned they're taking a step back to create brand guidelines based on Degen's lore and requested community interviews. However, tigerguo emphasized that the community cares more about product features and tokenomics than character design and branding. Specific feature requests include Web3 industry tools like token analysis, blockchain transactions via voice commands, and optimized LP yield pool information.\n\n## 2. FAQ:\nQ: I would like to know if the features from the Eliza framework will be integrated into DegenAI, making it a super agent? (asked by tigerguo.) A: Unanswered\nQ: Who is the current leader of DegenAI? Is Skely still in charge (asked by cool.eth) A: He's still involved but I've come in to help organize things (answered by rhota)\nQ: How is degenai's website doing? (asked by cool.eth) A: Unanswered\nQ: Which features would you most like to see? (asked by rhota) A: I hope it can become a tool that people in the Web3 industry would like to use, helping us with various tasks... (answered by tigerguo.)\n\n## 3. Help Interactions:\nHelper: jin | Helpee: Channel members | Context: Directing members to tag the correct person | Resolution: Provided the correct user ID to tag\n\n## 4. Action Items:\nTechnical: Integrate Eliza framework features into DegenAI to create a \"super agent\" | Description: Merge capabilities like token analysis, voice commands for blockchain transactions, and LP yield pool optimization | Mentioned By: tigerguo.\nDocumentation: Create and publish website roadmap and tokenomics | Description: Community needs clarity on future plans and token utility | Mentioned By: tigerguo.\nFeature: Implement Web3 industry tools | Description: Token analysis with alpha recommendations, voice/text commands for blockchain transactions, LP yield pool optimization | Mentioned By: tigerguo.\nFeature: Token-gated access to premium features | Description: Require users to hold a certain amount of DegenAI tokens to access advanced features | Mentioned By: tigerguo.\nDocumentation: Develop brand guidelines based on Degen's lore | Description: Creating consistent branding through community interviews | Mentioned By: rhota", "messageCount": 27, "userCount": 6 }, { "channelId": "1328592959444095038", "channelName": "associates", "summary": "# Discord Chat Analysis - \"associates\" Channel\n\n## 1. Summary\nThe chat primarily revolves around discussions about elizaOS ecosystem developments and token economics. Shaw shared a draft announcement about a significant tokenomics update where the DAO plans to use its treasury assets (valued at $15-30M) to create one-sided liquidity pools paired with their own token. This approach aims to generate buy pressure and provide liquidity for partner tokens while avoiding direct selling of treasury assets. Community members generally responded positively to this strategy. Other discussions included mentions of Virtuals' Solana announcement, Shaw's presentation at a Solana event in Istanbul (referenced as \"Catstanbul\"), and brief exchanges about various crypto projects including Tribe (a social finance app on Solana). The channel also contains reminders about contributing to the \"awesome-eliza\" GitHub repository and occasional sharing of crypto-related news and videos.\n\n## 2. FAQ\nQ: Thoughts on Virtuals Solana announcement? (asked by Smedroc - Street urchin @ ai16z) A: Feels like they want to capitalize on the SOL halo effect with no real value proposition for users; mostly monetary incentives to boost agent growth; \"meh\" overall (answered by smetter)\nQ: Any things from partner dao for us? (asked by Wilcox) A: Unanswered\n\n## 3. Help Interactions\nHelper: jin | Helpee: Community | Context: Seeking contributions to the awesome-eliza GitHub repository | Resolution: Jin offered tips for help with finding and updating ecosystem information\nHelper: kingdode | Helpee: Community | Context: Finding Shaw's presentation at a Solana event | Resolution: Provided timestamp (2:50) for the talk in a shared Jupiter Exchange video\nHelper: GujuViper | Helpee: Community | Context: Locating discussion about Stargate in a video | Resolution: Shared YouTube link with timestamp where Stargate is discussed\n\n## 4. Action Items\nType: Technical | Description: Implement one-sided LPs with treasury tokens against elizaOS token as part of tokenomics update | Mentioned By: shaw\nType: Documentation | Description: Update the awesome-eliza GitHub repository with ecosystem developments | Mentioned By: jin\nType: Feature | Description: Integrate native LP functionality for treasury tokens to show total LP value and returns/APR | Mentioned By: shaw\nType: Documentation | Description: Create a public announcement about the tokenomics update with additional context about future plans | Mentioned By: shaw", "messageCount": 64, "userCount": 18 }, { "channelId": "1318770424632311930", "channelName": "tokenomics", "summary": "# Analysis of \"tokenomics\" Discord Channel\n\n## 1. Summary\nThe discussion focused on developing tokenomics for ai16z/ElizaOS with emphasis on creating sustainable value accrual mechanisms. Jin and timshel outlined a vision centered on \"attention/code/capital\" as the core pillars for token value growth. The conversation explored multiple potential revenue models including: agent marketplace fees, investment strategies (where ai16z could function as a tier-1 investor in startups), launchpad services, and revenue sharing mechanisms. \n\nSeveral participants expressed concerns about the saturated launchpad space, questioning differentiation strategies. DorianD advocated for simpler tokenomics rather than complex staking/voting mechanisms, preferring practical use cases like agents paying for TrustDB data or services. Timshel proposed an innovative approach where ai16z could function as a venture capital entity (aixVC) with 100,000+ partners/supporters, potentially gaining access to tier-1 investment deals.\n\nThe group debated integration strategies with existing platforms like pump.fun versus building proprietary solutions with revenue sharing. DorianD suggested a novel mechanism where agents could distribute tokens to users who provide valuable interactions, potentially creating engagement incentives while improving agent data quality.\n\n## 2. FAQ\nQ: How will ai16z differentiate in the saturated launchpad space? (asked by bong49) A: By offering Solana agents with 50+ plugins and focusing on new users rather than expecting projects to port over (answered by DorianD)\nQ: What are the core components for growing ai16z token value? (asked by timshel) A: Attention (proliferating ElizaOS usage), Code (improving ElizaOS functionality), and Capital (value accrual to treasury) (answered by timshel)\nQ: Could ai16z function as a tier-1 investor alongside traditional VCs? (asked by timshel) A: It's possible if leveraging the community of 100,000+ partners who could support portfolio companies, though likely would need connections like a16z for deal flow (answered by mat)\nQ: How is the progress of the token economy model and when is the planned launch date? (asked by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f) A: Unanswered\nQ: Do mee.fun agents share the same TrustDB/Node instance or get their own? (asked by DorianD) A: Unanswered\n\n## 3. Help Interactions\nHelper: timshel | Helpee: DorianD | Context: Needed clarity on ai16z's strategic vision | Resolution: Provided detailed framework of \"attention/code/capital\" and outlined potential for ai16z to function as a venture investor\nHelper: unreadyplayer | Helpee: DorianD | Context: Discussion about partnering with pump.fun | Resolution: Suggested alternative approach using Cybers platform with revenue sharing and token burns instead\nHelper: shakejr | Helpee: DorianD | Context: Evaluating proposal for agents to reward quality interactions | Resolution: Identified potential issues with data quality and memory storage from people gaming the system\n\n## 4. Action Items\nType: Technical | Description: Explore implementation of agent-controlled token distribution to reward quality interactions | Mentioned By: DorianD\nType: Technical | Description: Investigate TrustDB metadata buying/selling between node instances | Mentioned By: DorianD\nType: Feature | Description: Develop revenue sharing mechanism for ai16z token to anticipate market trends | Mentioned By: mat\nType: Feature | Description: Create agent launchpad with bonding curve AMM for token launches | Mentioned By: unreadyplayer\nType: Feature | Description: Implement agent tokens paired with ai16z to compete with Virtuals | Mentioned By: unreadyplayer\nType: Technical | Description: Pitch pump.fun to add \"upload character file\" field in addition to JPEG | Mentioned By: DorianD\nType: Feature | Description: Develop wallet/trading/defi management services through agents | Mentioned By: mat\nType: Feature | Description: Create social account management services through agents | Mentioned By: mat", "messageCount": 119, "userCount": 12 }, { "channelId": "1301363808421543988", "channelName": "\ud83e\udd47-partners", "summary": "# Analysis of \ud83e\udd47-partners Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around discussions about AI16Z token price movements, tokenomics updates, and the intersection of AI technology with crypto. A significant announcement was made by Shaw regarding a tokenomics update where the DAO's treasury assets (valued at $15-30M) will be deployed into one-sided liquidity pools paired with AI16Z tokens. This strategy aims to create continuous buy pressure on AI16Z while providing liquidity for partner tokens. The chat also covered discussions about DeepSeek's AI models and their impact on the AI industry, with avirtualfuture noting that DeepSeek models are pressuring the industry and changing competitive dynamics. Partners expressed concerns about AI16Z's price performance, with some discussing market cycles and potential catalysts for growth. There were mentions of upcoming features including a launchpad, which was described as \"imminent\" and will be a no-code platform. Additionally, discussions touched on the potential for an AI16Z/Eliza sovereign chain or L1/L2 solution, though no concrete plans were confirmed.\n\n## 2. FAQ\nQ: How will the DAO's treasury assets be utilized? (asked by shaw) A: The assets will be deployed into one-sided LPs paired with AI16Z tokens to create buy pressure and provide liquidity for partner tokens (answered by shaw)\nQ: Is an AI16Z/Eliza sovereign chain or L1 still on the table? (asked by arkhanteeth) A: An L1 is not confirmed, but avirtualfuture noted it's not crazy and could be useful for storing agent data (answered by avirtualfuture)\nQ: How can non-technical persons fine-tune an agent with academic texts? (asked by bong49) A: Unanswered\nQ: When is V2 expected to launch? (asked by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f) A: April (answered by tappatdet)\nQ: Is the upcoming launchpad no-code friendly? (asked by 0xcryptolord) A: It's a no-code platform (answered by shaw)\nQ: How can we benefit from the DeepSeek hype? (asked by Burtiik) A: The narrative around open source and smaller players competing with OpenAI is positive for the ecosystem (answered by kingdode)\nQ: How does the liquidity pooling help the AI16Z token? (asked by smug) A: It creates additional volume and liquidity fees for the DAO (answered by shaw and jin)\n\n## 3. Help Interactions\nHelper: Ka_yari | Helpee: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f | Context: Anxiety about AI16Z price drops | Resolution: Advised that projects with this level of ambition take time, highlighted the tech and developer interest as reassuring factors\nHelper: avirtualfuture | Helpee: Dilettante | Context: Understanding DeepSeek's impact on AI industry | Resolution: Explained that open source can implement state-of-the-art without self-nerfing, creating pressure on closed models\nHelper: jin | Helpee: smug | Context: Confusion about how liquidity pooling helps AI16Z token | Resolution: Explained it creates additional volume for both AI16Z and partner tokens\n\n## 4. Action Items\nTechnical: Implement one-sided liquidity pools with treasury assets paired against AI16Z | Description: Deploy AUM tokens into LPs to create buy pressure and provide liquidity | Mentioned By: shaw\nTechnical: Consider Orca pool for the DefAI strategy | Description: Use Orca for the DefAI liquidity pool since they created the plugin | Mentioned By: [[{{,,,}}]]\nDocumentation: Break up DAO tokenomics explanations into separate parts | Description: Simplify messaging by explaining components separately (Launchpad, investment, TV show) | Mentioned By: shaw\nFeature: Integrate native LP tracking for treasury tokens | Description: Show total LP'd value and returns/APR in treasury dashboard | Mentioned By: shaw\nFeature: Launch no-code launchpad platform | Description: Create a platform for non-technical users to build on Eliza | Mentioned By: shaw\nFeature: Consider text-to-GLTF functionality | Description: Develop capability to convert text to 3D models | Mentioned By: avirtualfuture\nFeature: Explore potential for L1/L2 solution for agent data storage | Description: Consider blockchain as memory storage for agents | Mentioned By: avirtualfuture\nFeature: Discuss rebranding strategies | Description: Evaluate potential rebranding options | Mentioned By: jin", "messageCount": 376, "userCount": 45 }, { "channelId": "1313222089271939102", "channelName": "3d-ai-tv", "summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe discussion centers around the development of an AI news aggregator system with a Unity frontend. There are two versions of the aggregator being discussed: an existing one with bugs showing errors like \"Unable to generate summary for Freytes\" and a new one hosted at github.com/bozp-pzob/ai-news that includes additional features like market summaries. The team is working on transitioning to the new aggregator but faces issues with it not uploading new JSONs. They need someone to host the aggregator on a persistent server to provide daily JSON updates at a consistent URL. There's also discussion about AI personalities for characters named Shaw, Eliza, Degen Sparan, Peepo, and Cyborg Marc. The team is considering different delivery formats (pre-rendered cutscene video vs. in-browser embedded playback) and needs to decide which approach to take. Members are coordinating on hosting Twitter/X spaces and documenting progress through hackmd logs. Shaw suggests scheduling regular check-in calls to establish timelines and coordinate with the investment side of the business.\n\n## 2. FAQ\nQ: Where is the new aggregator hosted? (implied by jin) A: At github.com/bozp-pzob/ai-news (answered by jin)\nQ: What delivery format should be used for the project? (implied by SM Sith Lord) A: Need to decide between pre-rendered cutscene video vs. in-browser embedded playback (answered by SM Sith Lord)\nQ: Why isn't the new aggregator uploading JSONs? (implied by jin) A: Unanswered, but jin mentioned a developer is looking into the bug\n\n## 3. Help Interactions\nHelper: jin | Helpee: boom | Context: boom mentioned not having API keys to run the aggregator | Resolution: jin offered to provide API keys and explained that spending limits on the multisig are meant to cover these costs\nHelper: SM Sith Lord | Helpee: fishai | Context: fishai asked about AI personalities | Resolution: SM Sith Lord shared that they have personalities for Shaw and Eliza but need others to contribute more personality profiles\nHelper: David_Dyor | Helpee: jin | Context: jin needed help hosting Twitter/X spaces | Resolution: David_Dyor offered to host occasional X spaces based on his experience from Gitcoin\n\n## 4. Action Items\nTechnical: Fix bug preventing new aggregator from uploading latest JSON updates | Mentioned By: jin\nTechnical: Implement support for the new version of news aggregator response that includes images in Unity frontend | Mentioned By: SM Sith Lord\nTechnical: Host the aggregator on an always-up node.js server or GitHub Pages for persistent daily JSON URL | Mentioned By: SM Sith Lord and jin\nTechnical: Create more AI personality profiles for characters (Degen Sparan/Peepo/Cyborg Marc) | Mentioned By: SM Sith Lord\nDocumentation: Create hackmd progress logs to track development | Mentioned By: jin\nFeature: Decide on delivery format (pre-rendered cutscene vs. in-browser playback) | Mentioned By: SM Sith Lord\nFeature: Establish repository for consistent personality profiles | Mentioned By: SM Sith Lord\nFeature: Schedule regular check-in calls and establish timelines | Mentioned By: shaw", "messageCount": 41, "userCount": 6 } ] } }, "ai_news_elizaos_daily_discord_md_2025-01-25": { "filename": "2025-01-25.md", "content": "# elizaOS Discord - 2025-01-25\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Updates\n- **DeepSeek R1 Integration**: Users report positive experiences with DeepSeek R1, noting its solid reasoning capabilities and cost-effectiveness compared to OpenAI. Multiple users are exploring proper configuration methods for DeepSeek as a model provider in their agents.\n- **Twitter/X Integration Challenges**: Many users experiencing login failures, authentication issues, and problems with agents posting in incorrect formats (including JSON or thinking monologues). Solutions discussed include using VPNs, setting up proxies, and verifying accounts with blue checks.\n- **Database Configuration**: Discussions about switching from SQLite to PostgreSQL/Supabase for better persistence. Users implementing knowledge systems to allow agents to access and utilize stored information.\n- **Memory Issues**: A brief mention of a \"memory issue fixed\" by 0xCatnipKing suggests some development progress.\n- **WebAssembly SIMD Support**: A user (Deepdelver) experienced runtime errors related to WebAssembly SIMD support when trying to build ElizaOS on a VM, specifically mentioning \"Wasm SIMD unsupported\" errors.\n- **Plugin Development**: Users creating and modifying plugins for various functionalities like Solana blockchain integration, web search, and Twitter actions.\n\n### Tokenomics & Treasury Management\n- **Major Tokenomics Update**: Shaw announced a significant update where the DAO plans to use its treasury assets (valued at $15-30M) to create one-sided liquidity pools paired with AI16Z tokens. This strategy aims to generate buy pressure and provide liquidity for partner tokens while avoiding direct selling of treasury assets.\n- **Value Accrual Framework**: Jin and timshel outlined a vision centered on \"attention/code/capital\" as the core pillars for token value growth:\n - Attention: Proliferating ElizaOS usage\n - Code: Improving ElizaOS functionality\n - Capital: Value accrual to treasury\n- **Revenue Models**: Discussions explored multiple potential revenue models including agent marketplace fees, investment strategies (where ai16z could function as a tier-1 investor in startups), launchpad services, and revenue sharing mechanisms.\n- **Launchpad Development**: A no-code launchpad platform was described as \"imminent\" by Shaw.\n\n### AI16Z & DegenAI Integration\n- **Super Agent Concept**: Community members, particularly tigerguo, expressed interest in understanding how DegenAI and Eliza might merge to create a \"super agent\" with enhanced capabilities.\n- **Web3 Industry Tools**: Feature requests include token analysis, blockchain transactions via voice commands, and optimized LP yield pool information.\n- **Leadership Changes**: Rhota mentioned joining to help organize alongside Skely, focusing on creating brand guidelines based on Degen's lore.\n\n### 3D AI TV Project\n- **News Aggregator Development**: The team is working on transitioning to a new aggregator (github.com/bozp-pzob/ai-news) that includes additional features like market summaries but faces issues with JSON uploads.\n- **Delivery Format Decision**: The team is considering different delivery formats (pre-rendered cutscene video vs. in-browser embedded playback).\n- **AI Personalities**: Development of character personalities for Shaw, Eliza, Degen Sparan, Peepo, and Cyborg Marc is in progress.\n- **Infrastructure Needs**: The project requires someone to host the aggregator on a persistent server to provide daily JSON updates at a consistent URL.\n\n## Key Questions & Answers\n\n### ElizaOS Technical\n- **Q**: How does DeepSeek R1 compare to other models? \n **A**: \"It's cheaper than OpenAI with solid reasoning capabilities, and its RL part works well\" (ITZMIZZLE)\n\n- **Q**: How to use DeepSeek as a model provider? \n **A**: \"Add DeepSeek configuration to .env file\" ([elizaos] )\n\n- **Q**: How to fix Twitter login issues on a VPS? \n **A**: \"Set up a proxy on the VPS to login with that IP and complete 2FA\" (shvedity)\n\n- **Q**: How should secrets be configured for multiple agents? \n **A**: \"Secrets can be defined in each agent's character JSON file for specific configurations\" (sb)\n\n- **Q**: How to stop agents from using em dashes in replies? \n **A**: \"Add specific instructions to replace them with semicolons, commas, or periods\" (mark rizzn hopkins)\n\n### Tokenomics & Investment\n- **Q**: How will the DAO's treasury assets be utilized? \n **A**: \"The assets will be deployed into one-sided LPs paired with AI16Z tokens to create buy pressure and provide liquidity for partner tokens\" (shaw)\n\n- **Q**: How will ai16z differentiate in the saturated launchpad space? \n **A**: \"By offering Solana agents with 50+ plugins and focusing on new users rather than expecting projects to port over\" (DorianD)\n\n- **Q**: Could ai16z function as a tier-1 investor alongside traditional VCs? \n **A**: \"It's possible if leveraging the community of 100,000+ partners who could support portfolio companies, though likely would need connections like a16z for deal flow\" (mat)\n\n- **Q**: How does the liquidity pooling help the AI16Z token? \n **A**: \"It creates additional volume and liquidity fees for the DAO\" (shaw and jin)\n\n### AI Portfolio & Projects\n- **Q**: How do I get involved in the AI portfolio? \n **A**: \"Holding the AI16Z token gives you exposure to the portfolio managed by AI MARC. Check pump.fun for the whitepaper.\" (Phoenix | Livepeer-Eliza.com)\n\n- **Q**: Thoughts on Virtuals Solana announcement? \n **A**: \"Feels like they want to capitalize on the SOL halo effect with no real value proposition for users; mostly monetary incentives to boost agent growth; 'meh' overall\" (smetter)\n\n## Community Help & Collaboration\n\n### Technical Assistance\n- **Helper**: sb | **Helpee**: Bizzo \n **Context**: Agent defaulting to largest model despite configuration \n **Resolution**: Explained that character settings take priority over .env and provided correct configuration format\n\n- **Helper**: fourcolors | **Helpee**: MochinoLabs \n **Context**: Build errors with mistral model interface \n **Resolution**: Provided solution involving package.json overrides and version bumps\n\n- **Helper**: Amir_qfwri | **Helpee**: Sergey Danilovich \n **Context**: Using Supabase instead of local database \n **Resolution**: Instructed to add POSTGRES_URL in .env file with Supabase connection string\n\n- **Helper**: [elizaos] | **Helpee**: mike\ud83c\udded\ud83c\uddfa \n **Context**: Running multiple agents with different Twitter credentials \n **Resolution**: Explained how to create different character.json files with their own credentials\n\n### Project Guidance\n- **Helper**: timshel | **Helpee**: DorianD \n **Context**: Needed clarity on ai16z's strategic vision \n **Resolution**: Provided detailed framework of \"attention/code/capital\" and outlined potential for ai16z to function as a venture investor\n\n- **Helper**: Ka_yari | **Helpee**: \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f \n **Context**: Anxiety about AI16Z price drops \n **Resolution**: Advised that projects with this level of ambition take time, highlighted the tech and developer interest as reassuring factors\n\n- **Helper**: avirtualfuture | **Helpee**: Dilettante \n **Context**: Understanding DeepSeek's impact on AI industry \n **Resolution**: Explained that open source can implement state-of-the-art without self-nerfing, creating pressure on closed models\n\n## Action Items\n\n### Technical\n- Fix WebAssembly SIMD support issues when running ElizaOS on VMs (Deepdelver)\n- Resolve @discordjs/opus installation issues (David_Dyor)\n- Fix RAG lookup from knowledge which appears to be broken (kAI wilder)\n- Implement solution for agents stuck in endless reply loops on Twitter ([elizaos] )\n- Fix Discord integration infinite loop issue (mark rizzn hopkins)\n- Resolve issue with headless mode not being respected by new front end (mark rizzn hopkins)\n- Fix Twitter client to handle 2FA and suspicious login detection (multiple users)\n- Implement proper DeepSeek R1 integration with ElizaOS (multiple users)\n- Implement one-sided liquidity pools with treasury assets paired against AI16Z (shaw)\n- Consider Orca pool for the DefAI strategy ([[{{,,,}}]])\n- Explore implementation of agent-controlled token distribution to reward quality interactions (DorianD)\n- Investigate TrustDB metadata buying/selling between node instances (DorianD)\n- Fix bug preventing new aggregator from uploading latest JSON updates (jin)\n- Implement support for the new version of news aggregator response that includes images in Unity frontend (SM Sith Lord)\n- Host the aggregator on an always-up node.js server or GitHub Pages for persistent daily JSON URL (SM Sith Lord and jin)\n- Integrate Eliza framework features into DegenAI to create a \"super agent\" (tigerguo)\n- Investigate and address Aiora platform issues (Bogdanoff)\n\n### Documentation\n- Create guide for embedding API credentials in character JSON files (Mr. Stark)\n- Update tokenomics documentation (witch)\n- Update contribution docs to clarify PR should point to develop branch (pixel_pavel)\n- Create guide for setting up and using the Solana plugin ([elizaos] )\n- Develop CLI that allows selecting packages to include on install and update (luccasveg)\n- Update the awesome-eliza GitHub repository with ecosystem developments (jin)\n- Break up DAO tokenomics explanations into separate parts (shaw)\n- Create clearer onboarding information for AI16Z portfolio participation (David_Dyor)\n- Create hackmd progress logs to track development (jin)\n- Develop brand guidelines based on Degen's lore (rhota)\n- Create and publish website roadmap and tokenomics (tigerguo)\n\n### Features\n- Add ability to augment character knowledge after deployment (veTechno)\n- Implement tweet automation with conditional emoji usage (dragonlord)\n- Implement feature to hide non-dialogue text in agent conversations (David_Dyor)\n- Add support for multiple plugins in a single character (eliza builder)\n- Implement user restriction for on-chain interactions (El Pulpo \ud83d\udc19)\n- Create configurable Twitter actions with rate limiting and execution limits (Addy)\n- Implement new knowledge system for easier document ingestion (Mad)\n- Add support for PDF files in knowledge system (veTechno)\n- Develop revenue sharing mechanism for ai16z token to anticipate market trends (mat)\n- Create agent launchpad with bonding curve AMM for token launches (unreadyplayer)\n- Implement agent tokens paired with ai16z to compete with Virtuals (unreadyplayer)\n- Develop wallet/trading/defi management services through agents (mat)\n- Create social account management services through agents (mat)\n- Launch no-code launchpad platform (shaw)\n- Consider text-to-GLTF functionality (avirtualfuture)\n- Explore potential for L1/L2 solution for agent data storage (avirtualfuture)\n- Discuss rebranding strategies (jin)\n- Decide on delivery format (pre-rendered cutscene vs. in-browser playback) (SM Sith Lord)\n- Establish repository for consistent personality profiles (SM Sith Lord)\n- Schedule regular check-in calls and establish timelines (shaw)\n- Create more AI personality profiles for characters (Degen Sparan/Peepo/Cyborg Marc) (SM Sith Lord)\n- Implement Web3 industry tools for token analysis, blockchain transactions, and LP yield optimization (tigerguo)\n- Token-gated access to premium features (tigerguo)\n- Expand elizaOS Agent marketplace to Solana blockchain (\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)" }, "github_summaries_daily_2025-01-26": { "filename": "2025-01-26.md", "content": "# ElizaOS Daily Update (Jan 26, 2025)\n\n## OVERVIEW \nToday, significant progress was made in enhancing the ElizaOS framework, particularly with the introduction of a new news plugin and a critical bug fix in the goal objectives update logic. The development team focused on improving plugin functionality and addressing various issues reported by users, contributing to a more robust and user-friendly experience.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### New Features\n- Introduced a new **news-plugin** to enhance the capabilities of the ElizaOS framework. This feature is linked to the AI Agent Dev School Video #2. See [PR #1248](https://github.com/elizaOS/eliza/pull/1248).\n\n### Bug Fixes\n- Resolved a bug in the goal objectives update lookup logic, which was affecting the bootstrap plugin's evaluator. This fix is documented in [PR #2791](https://github.com/elizaOS/eliza/pull/2791).\n\n### Active Development Areas\n- The **plugin-news** area saw 6 changes, while **plugin-bootstrap** and **agent/src** had 1 change each, indicating focused development efforts in these modules.\n\n## CLOSED ISSUES\n\n### Plugin Enhancements\n- Closed the issue regarding the addition of support for the DeepSeek API, which will allow more developers to explore the framework. See [#2658](https://github.com/elizaOS/eliza/issues/2658).\n- Resolved the request for supporting default grok in the generate object for the Twitter plugin, enhancing its functionality. See [#1983](https://github.com/elizaOS/eliza/issues/1983).\n\n### Action and Integration Improvements\n- Addressed the issue related to deciding which actions to use from a plugin, streamlining the selection process. See [#1266](https://github.com/elizaOS/eliza/issues/1266).\n- Closed the request for native integration support for FullsendFI, which would facilitate SOL transfers using Twitter UIDs. See [#1072](https://github.com/elizaOS/eliza/issues/1072).\n\n## NEW ISSUES\n\n### Plugin Testing and Coverage\n- Identified the need for improved test configuration and coverage for the **plugin-0x** package, highlighting gaps in current testing practices. See [#2806](https://github.com/elizaOS/eliza/issues/2806).\n- Noted similar requirements for the **plugin-0g**, indicating a broader need for enhanced testing structures. See [#2804](https://github.com/elizaOS/eliza/issues/2804).\n\n### User Experience Challenges\n- Reported issues regarding multiple agents working together, indicating a need for clearer guidance on functionality. See [#2801](https://github.com/elizaOS/eliza/issues/2801).\n- Addressed a bug related to message ID collisions in the Telegram client, which could lead to message delivery issues. See [#2796](https://github.com/elizaOS/eliza/issues/2796).\n- Highlighted connectivity issues with the headless web interface and Discord integration, which are impacting user experience. See [#2795](https://github.com/elizaOS/eliza/issues/2795) and [#2792](https://github.com/elizaOS/eliza/issues/2792)." }, "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\\\"\\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![ankr](https://github.com/user-attachments/assets/553e6c0a-8850-4d68-a711-7b13ce443686)\\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![Screenshot 2025-01-23 at 13 11 03](https://github.com/user-attachments/assets/531c96fb-9a01-40ef-8b04-4e8214832efb)\\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![nvidia](https://github.com/user-attachments/assets/f27fe3f8-9daf-4dc2-9c6c-93deda5f9da4)\\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![image](https://github.com/user-attachments/assets/43e847c9-5d02-43f0-a0c9-a857bc332a03)\\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