{
"date_generated_for": "2025-01-14",
"ai_news_elizaos_discord_md_2025-01-13": {
"filename": "2025-01-13.md",
"content": "# elizaOS Discord - 2025-01-13\n\n## Overall Discussion Highlights\n\n### Rebranding from ai16z to ElizaOS\n- The project is planning to rebrand from \"ai16z\" to \"ElizaOS\" due to potential trademark issues with a16z (Andreessen Horowitz)\n- This rebranding aims to better align the project's name with its technical foundation while avoiding legal complications\n- The team is consulting with Solana Foundation about whether the token ticker can be changed, but any change would need to wait at least 2 months\n- Shaw explained that rebranding would enable partnerships and collaborations currently on hold\n\n### ElizaOS Framework Development\n- The team is working on V2 of the framework with improved autonomy features\n- GitHub repository shows significant development activity with daily updates and numerous contributors\n- The framework currently has 77 plugins and supports multimodality\n- Docker image optimization by Mike D reduced image size by removing image/audio/video processing components\n- Several users are building applications on top of the Eliza framework, including GOATAGI and Ninjapump\n\n### Tokenomics and Marketplace\n- Jin is finalizing a tokenomics paper that will include multiple flywheel strategies to be implemented in phases\n- A \"Marketplace of Trust\" is being developed as part of the tokenomics strategy\n- Projects built on ElizaOS will contribute 10% back to the treasury through a tribute model\n- DorianD suggested embedding this 10% tribute mechanism in the codebase to ensure revenue even from forked implementations\n- Discussion about reframing the \"launchpad\" concept as an \"agent marketplace\"\n\n### AI TV Show Development\n- Team is developing an AI-powered TV show system with three formats:\n - AI Podcast (daily GitHub updates)\n - Jedi Council (characters discussing blockchain topics)\n - Block Tank (a Shark Tank-style show for crypto pitches)\n- SM Sith Lord manages the backend show generation system while Boom handles the Unity frontend\n- Technical challenges include JSON data flow issues and debates about 3D model formats (VRM vs. FBX)\n\n### Community Structure\n- New \"associates\" channel created for users holding 10,000+ AI16Z tokens (compared to \"partners\" with 100,000+)\n- Jin proposed creating an intermediate \"executive\" role (50k tokens) between associates and partners\n- Tip.cc bot implemented for distributing tokens within the community through airdrops, triviadrops, and red envelopes\n\n### DegenAI Concerns\n- Community members expressed frustration about lack of clear information regarding DegenAI's roadmap and integration with the ai16z ecosystem\n- Uncertainty about whether DegenAI is actively trading, with conflicting claims\n- Jin and Odilitime acknowledged feedback about improving communications, mentioning a website is coming soon\n\n## Key Questions & Answers\n\n**Q: How can I reduce the Docker image size for Eliza?** \nA: Remove image processing, hugging face, audio processing, video processing, and local onnx components (answered by Mike D.)\n\n**Q: How do I run multiple agents at once?** \nA: Use `pnpm start --characters=\"characters/1.character.json,characters/2.character.json\"` (answered by elamore)\n\n**Q: Why is ai16z rebranding to ElizaOS?** \nA: To avoid potential trademark issues with a16z (Andreessen Horowitz) and to better align the name with the technical foundation of the project. (answered by Shaw)\n\n**Q: How does the news update system work for the AI Podcast?** \nA: The system checks a JSON file at \"https://elizaos.github.io/data/daily/summary.json\" which contains GitHub updates, then generates episode content based on this data (answered by SM Sith Lord)\n\n**Q: What is the risk with requiring AI16Z for agent launches?** \nA: It could create illiquidity in the primary pool post-bond, especially with full range. (answered by eskender.eth)\n\n**Q: How does pump.fun's model work?** \nA: They take 20% tribute when the bonding curve for 80% of coins sold hits 100%, and reward creators with 0.5 SOL. (answered by DorianD)\n\n**Q: What is the DegenAI DAO wallet address?** \nA: AM84n1iLdxgVTAyENBcLdjXoyvjentTbu5Q6EpKV1PeG (answered by SHADOW |Zer0)\n\n**Q: How can I find a comprehensive list of live agents that use the Eliza framework?** \nA: Check https://www.daos.fun/HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC under AUM and https://elizas.world/ (answered by DorianD)\n\n**Q: Any tips on tools to improve beat/vocals for generated songs?** \nA: Use compression and multiband compression, break into stems if possible, and map to tempo in Ableton (answered by boom)\n\n## Community Help & Collaboration\n\n- **WSL Setup Help**: adonisabril provided step-by-step instructions for setting up WSL, cloning the repo, and running Eliza to help bendermind\n- **Database Schema Fix**: custodian shared a working SQL schema that resolved room creation function issues for kingCuckDad\n- **Node-llama-cpp Installation**: n00b_SaUce shared a solution to delete .pnp.cjs file and rebuild to fix Huggingface dependency errors\n- **Music Generation**: boom provided detailed advice to Dr. Neuro on improving AI-generated music quality using compression techniques and shared an optimized prompt for song generation\n- **Deployment Solution**: Mike D. shared a GitHub repository for one-click deployment using terraform with AWS t4g instances for cost-efficient hosting\n- **Discord Error Fix**: Stealt\u210fyNinja.ADSC shared a workaround for Discord opus errors by removing Discord voice functionality\n\n## Action Items\n\n### Technical\n- Complete V2 of ElizaOS framework with improved autonomy features (Mentioned by Shaw)\n- Implement a staking system for AI16Z tokens with quarterly rewards (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- Consider embedding 10% tribute code in the Solana plugin (Mentioned by DorianD)\n- Fix the Twitter client to prevent posting message format instead of just the text content (Mentioned by Snuggyverse_E)\n- Implement event-driven architecture to decouple content generation from posting (Mentioned by Kraus)\n- Fix embedding dimension mismatch issues (Mentioned by Vaas)\n- Add support for ARM64 architecture (Mentioned by Morning3tar)\n- Fix Discord client dependency issues (Mentioned by PiagaShihari)\n- Move JSON download to happen after show ends instead of during recording (Mentioned by SM Sith Lord)\n- Implement character controller system for easier character management (Mentioned by fishai)\n- Create an \"executive\" role for users with 50k AI16Z tokens (Mentioned by jin)\n- Implement 8% DegenAI buyback as promised in tokenomics (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n\n### Documentation\n- Create comprehensive guide for web search plugin (Mentioned by jomolopo)\n- Update documentation on embedding configuration for Heurist (Mentioned by LeonGamer)\n- Create guide for Twitter bot settings configuration (Mentioned by SEDANO_YGG)\n- Create better documentation for plugins and clients (Mentioned by pagameba)\n- Create up-to-date beginner tutorial videos for visual learners (Mentioned by Lint-Minux)\n- Complete FAQ document for rebranding (Mentioned by Jin)\n- Create a one-pager introducing ai16z/ElizaOS (Mentioned by 0xwitch)\n- Create a clear roadmap for DegenAI showing now/next/future plans (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Publish wallet address and trading activity of DegenAI (Mentioned by ZeroLearn)\n\n### Features\n- Implement agent-to-agent Twitter group chats (Mentioned by Stealt\u210fyNinja.ADSC)\n- Develop no-code platform for building AI agents (Mentioned by CBK)\n- Implement a Reddit client (Mentioned by Oleg O.)\n- Add confirmation flow for blockchain transactions (Mentioned by tankjadu)\n- Implement a Bitcoin plugin (Mentioned by MonteCrypto)\n- Add support for Twitter spaces (Mentioned by trenchio)\n- Create \"Gauntlet of the Gods\" for community curation of agents (Mentioned by Robin)\n- Develop an agent marketplace instead of a launchpad (Mentioned by jin)\n- Implement futures and options trading strategies with AI-managed hedging (Mentioned by Display Name)\n- Add Degen Spartan for crypto market updates in AI TV shows (Mentioned by Smedroc)\n- Add DegenSpartanai to elizaOS affiliate account (Mentioned by cool.eth)"
},
"ai_news_elizaos_discord_md_2025-01-12": {
"filename": "2025-01-12.md",
"content": "# elizaOS Discord - 2025-01-12\n\n## Overall Discussion Highlights\n\n### ElizaOS Framework Development\n- **ElizaOS v2 Development**: Shaw described it as \"the most advanced agent framework I've ever seen\" with significant improvements being developed.\n- **Framework Updates**: ElizaOS has received updates (v0.1.8) and supports various LLM providers including Anthropic and local models.\n- **Windows Compatibility Issues**: Multiple users reported build failures on Windows with the latest Eliza release, with WSL emerging as the recommended solution.\n- **ARM Architecture Support**: Users on ARM devices face tokenizer compatibility issues, indicating a need for better ARM compatibility.\n\n### Project Direction & Governance\n- **Controversy Aftermath**: Shaw acknowledged mistakes regarding support for AICC (viewed as a \"vampire attack\"), announced a shift to \"wartime mode\" focusing on building rather than social media drama.\n- **Rebranding Plans**: Jin announced plans to rebrand from AI16Z to ElizaOS to expand utility, reach, and demand for the token.\n- **Tokenomics Development**: The team is working on a comprehensive tokenomics paper and FAQ page, with Jin finalizing documentation.\n- **Tribute Model Debate**: Community debated the value of the tribute model (projects sending 10% of tokens to the DAO), how to properly LP these tokens, and strategies for sustainable ecosystem growth.\n\n### Agent Development & Integration\n- **Twitter Integration Issues**: Users encountered authentication problems, rate limiting, and shadowbanning concerns when integrating agents with Twitter.\n- **Telegram Bot Implementation**: Several users sought help with implementing Telegram bots using ElizaOS.\n- **Voice Integration**: Discussions about integrating ElevenLabs for giving voice capabilities to AI agents.\n- **RAG Knowledge Systems**: Users worked on implementing Retrieval-Augmented Generation knowledge systems for their agents.\n\n### DegenAI Concerns\n- **Development Progress**: Community members expressed frustration about apparent lack of communication regarding DegenAI's development progress.\n- **Transparency Issues**: Concerns about a developer named \"Skely\" who allegedly sold tokens while still being involved in development.\n- **Trading Capabilities**: Questions about DegenAI's current trading strategy and performance, with requests for more transparency.\n\n### AI-Powered Media Production\n- **3D TV Show System**: Development of \"The AI Podcast\" which delivers GitHub updates in short videos, with technical discussions on improving the system.\n- **AI Music Generation**: Discussions about using Suno for AI music generation with suggestions for improving audio quality through DAWs like Ableton.\n- **Content Format Experimentation**: SM Sith Lord demonstrated a \"Crypto Shark Tank\" show concept, showing how the system can be adapted to different formats.\n\n## Key Questions & Answers\n\n**Q: How do I run multiple agents at once?** \nA: Use pnpm start --characters=\"characters/1.character.json,characters/2.character.json\" (answered by elamore)\n\n**Q: How can I control the number of Twitter replies my agent makes at once?** \nA: Add rate limiting in interactions.ts with code that tracks and limits total interactions (answered by Apeguru)\n\n**Q: How do I enable image generation in my agent?** \nA: Set image generation to true in .env file and use OpenAI; don't load the plugin in character file (answered by validsyntax)\n\n**Q: How can I run Eliza on Windows?** \nA: Use WSL (Windows Subsystem for Linux) as the latest version has compatibility issues with Windows (answered by koloxarto)\n\n**Q: How do I set up RAG knowledge for my agent?** \nA: Add \"ragKnowledge\": true in character secrets and format knowledge objects with path and shared properties (answered by \ua9c1Ninja_Dev\ua9c2)\n\n**Q: How does the 10% tribute model work?** \nA: Projects voluntarily send 10% of their tokens to the DAO as a gesture of alignment, creating shared incentives for mutual success (answered by jin)\n\n**Q: What is the relationship between DegenAI and AI16Z?** \nA: DegenAI is actively trading and buying AI16Z tokens, currently holding 4.1% of supply with plans to continue accumulation (answered by shaw)\n\n**Q: Is there a way to improve beat/vocals for AI-generated songs?** \nA: Use compression, multiband compression, and extract stems to work with them separately in Ableton; time map tracks to tempo for better mixing (answered by boom)\n\n**Q: How should the show_config.json be handled after episode generation?** \nA: Copy the automatically downloaded show_config.json into your folder after each episode to make it \"canon\" and prevent repetitive jokes (answered by SM Sith Lord)\n\n## Community Help & Collaboration\n\n### Agent Development Support\n- **adonisabril** helped **bendermind** set up Eliza on WSL by providing step-by-step instructions for installing Ubuntu, configuring WSL, and running Eliza through Cursor editor.\n- **Apeguru** assisted **Heady Shotta** with limiting Twitter interactions by sharing code snippet to modify interactions.ts to limit the number of interactions per check.\n- **validsyntax** explained to **Heady Shotta** that image generation should be enabled in .env file, not in character file.\n- **Tobiloba** identified incorrect endpoint usage and parameter issues for **0xRB** when troubleshooting direct client API problems.\n- **custodian** shared SQL schema with **kingCuckDad** that resolved room creation errors with Supabase database adapter.\n\n### Documentation & Knowledge Sharing\n- **0xwitch** created a comprehensive one-pager to introduce the ai16z token, explaining the token's purpose, ecosystem, and benefits.\n- **DorianD** outlined a format for regular \"ElizaOS Breakfast Club\" showcase events to foster cross-collaboration between tribute projects.\n- **masterdai** created and shared a tutorial video on building Eliza OS plugins.\n- **ethertopia** shared a collaborative document link for community to work on organizing information about DegenAI.\n\n### Technical Troubleshooting\n- **SM Sith Lord** helped **boom** debug why news aggregator content wasn't appearing in episodes by creating a new version of the show runner that outputs JSON data to console.\n- **fishai** suggested using Game Creator 2 package and implementing a character controller approach with prefabs to **boom** for improving code architecture.\n- **jin** added **4n7m4n** to the appropriate channel after reviewing their PR when they contributed to GitHub but couldn't access dev channels.\n- **boom** provided detailed advice to **Dr. Neuro** on improving AI-generated music quality, suggesting compression techniques and DAW workflows.\n\n## Action Items\n\n### Technical\n- Develop and release ElizaOS v2 with improved agent framework capabilities (mentioned by shaw)\n- Fix Windows compatibility issues with latest Eliza release (mentioned by bendermind)\n- Implement proper rate limiting for Twitter interactions to prevent shadowbanning (mentioned by pupathebig)\n- Fix Supabase adapter compatibility issues with room creation and queries (mentioned by kingCuckDad)\n- Add support for ARM architecture (mentioned by Morning3tar)\n- Implement voice capabilities for AI agents using ElevenLabs integration (mentioned by Adil)\n- Create a way for agents to run their own Twitter group chats (mentioned by Stealt\u210fyNinja.ADSC)\n- Fix authentication issues with Twitter for agent integration (mentioned by wizardsupreme)\n- Develop ElizaOS plugin for on-chain communication between AI agents (mentioned by talirezun)\n- Update client-direct package to version 0.1.8 to match other packages (mentioned by Jonatan Chaverri)\n- Implement stem extraction and processing workflow for AI-generated music (mentioned by boom)\n- Create universal API standard for AI Agents (\"AICode\") (mentioned by 0xTheDot)\n- Build AI Market Making system for Solana Memecoin (mentioned by Dreygo)\n- Modify 3D TV show code to have JSON download happen after show ends (mentioned by SM Sith Lord)\n- Create a more modular character system using prefabs and a unified character controller (mentioned by fishai)\n- Create an agent to distribute rewards and track contributions (mentioned by jin)\n- LP the tokens that are sent to the DAO rather than holding them indefinitely (mentioned by jin)\n\n### Documentation\n- Create comprehensive guide for RAG knowledge implementation (mentioned by Apeguru)\n- Update WSL setup guide for Eliza with clearer instructions for Windows users (mentioned by bendermind)\n- Create guide for managing multiple agents efficiently (mentioned by jason1977)\n- Provide clearer documentation on how to use different LLM providers with ElizaOS (mentioned by Iv/-\\nB)\n- Create comprehensive guide for Twitter bot configuration options (mentioned by SEDANO_YGG)\n- Complete and release the tokenomics paper with comprehensive flywheel strategies (mentioned by jin)\n- Update the FAQ page on elizaos.ai/dao with current information (mentioned by jin)\n- Document the RPGF (Retroactive Public Goods Funding) flywheel (mentioned by jin)\n- Create a one-pager explaining AI16Z for new investors (mentioned by 0xwitch)\n- Create a less technical explanation of the project plan to reduce FUD (mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Create a dedicated webpage introducing DegenAI's autonomous trading (mentioned by ldl)\n\n### Feature\n- Develop a launchpad for AI projects (mentioned by twinkletoes.ron)\n- Create a channel for holders with smaller amounts of ai16z/degenai (mentioned by jin)\n- Add confirmation step for blockchain transactions (mentioned by bifkn)\n- Support for official Twitter API with developer keys (mentioned by eschnou)\n- Add ability to dynamically add/remove agents without restarting (mentioned by kingCuckDad)\n- Implement futures and options trading strategies for hedging (mentioned by Display Name)\n- Add neutral and bearish trading strategies using options (mentioned by Display Name)\n- Create an \"ElizaOS Breakfast Club\" for ecosystem projects to showcase their agents (mentioned by DorianD)\n- Implement a rating system for closer cooperation with partners (mentioned by dral)\n- Develop a marketplace for token generation, builder bursaries, trust, tasks, and swarms (mentioned by \u039e Xil)\n- Add vesting, team allocation, and whitelist features to the launchpad (mentioned by mat)\n- Create an LST or LRT (Liquid Staking/Restaking 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- Implement \"roast mode\" where characters make fun of each other in AI shows (mentioned by boom)\n- Add option to toggle between \"short form\" and \"long form\" content generation (mentioned by boom)\n- Create a debugging UI with scrolling event feed to visualize system flow (mentioned by boom)\n- Coordinate rebranding from AI16Z to ElizaOS across all platforms (mentioned by witch)"
},
"ai_news_elizaos_discord_md_2025-01-11": {
"filename": "2025-01-11.md",
"content": "# elizaOS Discord - 2025-01-11\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **ElizaOS v0.1.8 Released**: Odilitime shared the GitHub link for the latest version\n- **New Integrations**: ElizaOS now supports Ollama and Deepseek integration\n- **Windows Build Issues**: Several users reported problems building the latest version on Windows, while WSL appears to work better\n- **Twitter Integration Challenges**: Multiple users experiencing authentication problems, rate limiting, and formatting errors with Twitter integration\n- **Database Connections**: Recurring issues with Supabase and PostgreSQL adapters, particularly for RAG implementation\n\n### Agent Development\n- **Orca LP Plugin**: A developer mentioned working on this plugin (not yet launched)\n- **Twitter Spaces Integration**: Directive Creator experimenting with Twitter Spaces for Eliza\n- **VRM Optimization**: Developers discussing optimizing 3D models using gltf-transform extensions\n- **Swarm Chat Feature**: Development underway for enabling multiple AI agents to discuss topics together\n- **RAG Implementation**: Discussions about proper implementation of Retrieval Augmented Generation for agents\n\n### AI16Z Ecosystem\n- **Launchpad Development**: Plans for Q1 launch of an AI16Z launchpad similar to Virtuals\n- **Tokenomics Model Debate**: Extensive discussion about the 10% tribute model where projects built on ElizaOS contribute tokens to the DAO treasury\n- **Liquidity Pool Structure**: Debate on whether to use ai16z or SOL as the base pair for launchpad liquidity pools\n- **Community Concerns**: Discussions about leadership communication, particularly regarding Shaw's tweets and involvement with other projects like AICC\n- **DegenAI Trust Issues**: Community discovered that Skely, a core developer, sold all his DegenAI tokens, causing significant trust concerns\n\n### AI TV Show Development\n- **AI16Z Podcast Show**: Team working on a show featuring Eliza, Shaw, and Marc discussing tech news\n- **Unity Implementation**: Boom working on camera angles, scene transitions, and visual effects\n- **FishAI System**: Modular AI system offered by fishai that could power various show concepts\n- **Content Constraints**: Careful content filtering required as anything said on the show is considered an endorsement\n\n## Key Questions & Answers\n\n**Q: How do I verify for the partner role?** \nA: Hold 100k AI16Z tokens and verify through CollabLand in the roles channel\n\n**Q: Does ElizaOS support Ollama or Deepseek?** \nA: Yes, check the changelog for implementation details\n\n**Q: How do I fix Twitter authentication errors?** \nA: Try logging in manually through a browser first, consider using 2FA, and be aware that datacenter IPs may cause Twitter to be more hostile toward your account\n\n**Q: What causes the agent to post in JSON format on Twitter?** \nA: Add `Return the tweet in JSON format like: {\"text\": \"your tweet here\"}` in eliza/packages/plugin-twitter/src/templates.ts\n\n**Q: How do I enable image generation in tweets?** \nA: Set IMAGE_GEN to true and add image generation as a plugin in your character file\n\n**Q: How do I run Eliza on WSL?** \nA: Install Ubuntu, install node, nvm, node v23.1.0, pnpm, clone repo, and run pnpm install\n\n**Q: How do I limit the number of interactions with a tweet?** \nA: You can modify the interactions.ts file to add a maximum interaction limit\n\n**Q: How do I use RAG knowledge in Eliza?** \nA: Set \"ragKnowledge\": true in character secrets and format knowledge objects correctly\n\n**Q: Should ai16z be used as the base currency for the launchpad?** \nA: Mixed opinions - some argue it would create a monetary premium like L1 tokens, while others suggest SOL would reduce friction and enable broader ecosystem growth\n\n**Q: How does the pump.fun model work?** \nA: It sells 80% on bonding curve, and when it reaches 100%, the SOL is unlocked and the remaining 20% is used to create a new LP on Raydium\n\n## Community Help & Collaboration\n\n- **VRM Optimization**: Jin suggested asking \"rayan from oncyber for gltf-transform extension\" to help Directive Creator with 3D model optimization\n- **Twitter Integration**: Masterdai provided code fix for templates.ts to help 0xJam3s resolve JSON formatting issues in tweets\n- **WSL Setup**: Quixotechdon provided step-by-step instructions for setting up Ubuntu and installing necessary dependencies to help bendermind run Eliza on WSL\n- **Character File Format**: Kobra explained proper array format for user-bot interactions in character file to help Match resolve multiple response issues\n- **Twitter Rate Limiting**: Apeguru provided code snippet to add a maximum interaction limit to interactions.ts, helping Heady Shotta limit tweet interactions\n- **Show Configuration**: SM Sith Lord explained to boom how the config file stores episode history and should be preserved between generations to maintain episode continuity\n- **Chat Summarization**: Jin and YoungPhlo discussed automating Discord chat summarization, with YoungPhlo noting the need for a preference model to reduce hallucinations\n\n## Action Items\n\n### Technical Tasks\n- **Fix Twitter client** to prevent JSON formatting in replies by adding proper formatting in templates.ts (Mentioned by masterdai)\n- **Implement proper rate limiting** for Twitter interactions by modifying interactions.ts (Mentioned by Apeguru)\n- **Fix Supabase adapter issues** by changing .single() to .maybeSingle() in adapter code (Mentioned by Apeguru)\n- **Fix Windows build issues** for latest Eliza version by resolving dependency conflicts (Mentioned by bendermind)\n- **Fix PostgreSQL adapter** for RAG knowledge to work with PostgreSQL 16 (Mentioned by koloxarto)\n- **Automate chat summarization** to automatically summarize Discord discussions (Mentioned by jin)\n- **Implement VRM optimization** using gltf-transform extension for 3D models (Mentioned by jin)\n- **Develop Orca LP plugin** for liquidity pool integration (Mentioned by YoungPhlo)\n- **Fix Twitter authentication issues** for agents (Mentioned by wizardsupreme)\n- **Create a launchpad** that mimics pump.fun's liquidity seeding model with bonding curve mechanism (Mentioned by eskender.eth)\n- **Implement vesting, team allocation, and whitelist features** for the launchpad (Mentioned by mat)\n- **Develop a system to LP the tokens** sent to the DAO through tribute (Mentioned by jin)\n- **Fix scene transition glitches** with render texture caching (Mentioned by boom)\n- **Implement donotdestroyonload for UI elements** to prevent UI from reloading during scene changes (Mentioned by boom)\n- **Expand news aggregator** to include social media updates from DankVR and ShawMakesMagic (Mentioned by SM Sith Lord)\n\n### Documentation Needs\n- **Create comprehensive guide for RAG implementation** documenting how memory and knowledge management works (Mentioned by Lorcann)\n- **Create prompt engineering guide** for Eliza with templates for character components (Mentioned by Snapper)\n- **Create a one-pager** to introduce the ai16z token explaining value proposition and ecosystem benefits (Mentioned by 0xwitch)\n- **Document the tribute model** and its benefits explaining how the 10% tribute model works (Mentioned by jin)\n- **Create a roadmap** with clear deadlines for tokenomics implementation (Mentioned by \u963f\u62c9\u65af\u52a0\u7684\u72d7\ud83d\udd2f)\n- **Clarify the current state** of the game/application on the website (Mentioned by DorianD)\n- **Address potential citation issues** regarding Stanford Ville's paper imagery (Mentioned by Kellyooy)\n- **Create list of approved jokes** for show intro to avoid repetition (Mentioned by boom)\n- **Create agent directory** compiling a comprehensive list of agents built on Eliza (Mentioned by Defi Cait)\n- **Improve ElizaOS embedding documentation** to better document how to embed agents in other platforms (Mentioned by KBeeKeychain)\n\n### Feature Requests\n- **Support for official Twitter API** with developer keys to avoid restrictions (Mentioned by eschnou)\n- **Add support for multiple model providers** in one agent for different functions (Mentioned by validsyntax)\n- **Implement agent-to-agent communication** to enable coordinated multi-agent systems (Mentioned by Gus F)\n- **Implement a partner ecosystem showcase** with weekly calls for tribute projects (Mentioned by DorianD)\n- **Create a rating system** for closer cooperation with partner projects (Mentioned by \u8f9e\u5c18\u9e3d\u9e3d)\n- **Develop an agent** to help answer questions about the launchpad (Mentioned by jin)\n- **Create a network of launchpads** with fee distribution (Mentioned by eskender.eth)\n- **Develop SNL-style outro** with band for the AI show (Mentioned by boom)\n- **Create Jedi Council show concept** with different characters allowing more creative freedom (Mentioned by SM Sith Lord)\n- **Implement procedural animations** for flying objects in the show (Mentioned by boom)\n- **Add laser eyes effect** for characters as a new visual effect (Mentioned by boom)\n- **Implement swarm chat** to enable multiple AI agents to discuss topics together (Mentioned by cr3a1)\n- **Create GenAI storybook creator** for AI-generated storybooks (Mentioned by YoungPhlo)\n- **Build Eliza agent for Roblox** to develop integration with the platform (Mentioned by YoungPhlo)\n- **Implement voice capabilities** for agents using Eleven Labs (Mentioned by Adil)"
},
"ai_news_elizaos_daily_json_2025-01-13": {
"filename": "2025-01-13.json",
"content": {
"type": "elizaosDailySummary",
"title": "Daily Report - 2025-01-13",
"categories": [
{
"title": "Eliza OS Recent Updates and Improvements",
"content": [
{
"text": "# New Features and Enhancements\n\nEliza OS has received numerous feature additions and improvements:\n\n## Blockchain and Cryptocurrency Integration\n- Added CoinGecko price per address functionality (PR #2262)\n- Added support for gravity chain in EVM plugin (PR #2228)\n- Integrated Gitcoin passport functionality (PR #2296)\n- Added B\u00b2 Network plugin (PR #2010)\n- Implemented OpenZeppelin governance plugin for EVM (PR #1710)\n- Added cross-chain swaps through Squid Router (PR #1482)\n- Added Birdeye plugin for Solana analytics (PR #1417)\n- Added AGW support to the Abstract plugin (PR #2207)\n\n## User Experience Improvements\n- Merged Eliza Installer with the current start.sh script (PR #2229)\n- Added character creation template function to start.sh (PR #2232)\n- Added Direct Client API with Delete Agent functionality (PR #2267)\n- Added limit parameter to memory retrieval across adapters (PR #2264)\n- Added an example service (PR #2249)\n\n## Documentation and Internationalization\n- Added Farsi (Persian) readme (PR #2260)\n- Added \"What Did You Get Done This Week? #9\" notes (PR #2243)\n- Added weekly contributor meeting notes (PR #2285)\n\n## Security and Verification\n- Added plugin for TEE verifiable log (PR #1369)\n- Fixed derive key and updated remote attestation (PR #2303)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2262",
"https://github.com/elizaOS/eliza/pull/2228",
"https://github.com/elizaOS/eliza/pull/2296",
"https://github.com/elizaOS/eliza/pull/2010",
"https://github.com/elizaOS/eliza/pull/1710",
"https://github.com/elizaOS/eliza/pull/1482",
"https://github.com/elizaOS/eliza/pull/1417",
"https://github.com/elizaOS/eliza/pull/2207",
"https://github.com/elizaOS/eliza/pull/2229",
"https://github.com/elizaOS/eliza/pull/2232",
"https://github.com/elizaOS/eliza/pull/2267",
"https://github.com/elizaOS/eliza/pull/2264",
"https://github.com/elizaOS/eliza/pull/2249",
"https://github.com/elizaOS/eliza/pull/2260",
"https://github.com/elizaOS/eliza/pull/2243",
"https://github.com/elizaOS/eliza/pull/2285",
"https://github.com/elizaOS/eliza/pull/1369",
"https://github.com/elizaOS/eliza/pull/2303"
],
"images": [],
"videos": []
},
{
"text": "# Bug Fixes and Maintenance\n\nSeveral bugs were fixed and maintenance tasks completed:\n\n## Bug Fixes\n- Fixed IME causing multiple messages on Enter (PR #2274)\n- Fixed missing @elizaos/plugin-b2 (PR #2268)\n- Fixed test/lint in develop branch (PR #2266)\n- Resolved Windows path issue in pnpm build client (PR #2240)\n- Fixed export of b2Plugin (PR #2291)\n\n## Maintenance and Reverts\n- Reverted \"Add support for VoyageAI embeddings API\" (PR #2290)\n- Fixed typo in README.md (PR #2256)\n- Fixed minor typo in CHANGELOG.md (PR #2255)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2274",
"https://github.com/elizaOS/eliza/pull/2268",
"https://github.com/elizaOS/eliza/pull/2266",
"https://github.com/elizaOS/eliza/pull/2240",
"https://github.com/elizaOS/eliza/pull/2291",
"https://github.com/elizaOS/eliza/pull/2290",
"https://github.com/elizaOS/eliza/pull/2256",
"https://github.com/elizaOS/eliza/pull/2255"
],
"images": [],
"videos": []
}
],
"topic": "completed_items"
},
{
"title": "Open Source Development, RPGF, and Contributor Tools",
"content": [
{
"text": "dankvr collaborated with META_DREAMER to improve the contributor leaderboard for the elizaOS repo, adding a weighted scoring system and bonding curve to gamify open-source development. This system makes it easier to track contributions and sets the stage for Retroactive Public Goods Funding (RPGF).",
"sources": [
"https://twitter.com/dankvr/status/1878673133361885542"
],
"images": [
"https://pbs.twimg.com/media/GhJVCGgXMAA0dGR.jpg",
"https://pbs.twimg.com/media/GhJVFANXYAA4ity.jpg"
],
"videos": []
},
{
"text": "When discussing tools for tracking contributions, dankvr shared several options including @eas_eth, @deworkxyz, discord-summarizer, @coordinape, standup channels, weekly check-ins, and @givepraise bot.",
"sources": [
"https://twitter.com/dankvr/status/1878881787365265809"
],
"images": [],
"videos": []
},
{
"text": "dankvr emphasized that meaningful impact in open source isn't just about quantity of commits or PRs. Sometimes a single PR can change the course of a project, which is why RPGF needs to be approached with thought and care.",
"sources": [
"https://twitter.com/dankvr/status/1878876447466799486"
],
"images": [],
"videos": []
},
{
"text": "The elizaOS project has a live preview available, with code publicly accessible for iteration on sybil resistance strategies in future versions.",
"sources": [
"https://twitter.com/dankvr/status/1878854919530422781",
"https://twitter.com/dankvr/status/1878854819143991660",
"https://twitter.com/dankvr/status/1878854464049950843"
],
"images": [],
"videos": []
},
{
"text": "dankvr mentioned using Gitcoin passport during grant rounds and noted there's a draft PR for eliza integration, though there are blockers related to EVM compatibility with SPL tokens.",
"sources": [
"https://twitter.com/dankvr/status/1878858257407852694"
],
"images": [],
"videos": []
},
{
"text": "In related development news, shawmakesmagic is working on a v2 that will feature full autonomy, unified wallet abstraction, plugin registry, easy setup, and a modular design with generic types for customization.",
"sources": [
"https://twitter.com/shawmakesmagic/status/1878727225119531248",
"https://twitter.com/shawmakesmagic/status/1878726380017647931"
],
"images": [],
"videos": []
},
{
"text": "dankvr views the crypto/AI space as more collaborative (PVE) than competitive (PVP), noting that 'useful agents act as a rising tide' and that open source tends toward 'permissionless collaborative/positive sum mindsets'.",
"sources": [
"https://twitter.com/dankvr/status/1878745372719505539",
"https://twitter.com/dankvr/status/1878705968856670389"
],
"images": [],
"videos": []
}
],
"topic": "tweet"
},
{
"title": "Recent GitHub Issues in the elizaOS/eliza Repository",
"content": [
{
"text": "Several technical issues have been reported in the elizaOS/eliza GitHub repository, covering a range of problems:\n\n1. Authentication issues: Twitter authentication is failing on Cloud with Error 399 (#2225).\n\n2. Missing dependencies: The '@anush008/tokenizers-linux-arm64-gnu' module is missing (#2242).\n\n3. Data retrieval problems: The getRecentPostInteractions function is returning all memory instead of filtered results (#2253).\n\n4. Deployment issues: Client-direct v0.1.8 failed to deploy to npm, causing inconsistencies (#2227).\n\n5. Runtime errors: Users are encountering 'Uncaught TypeError: Cannot read properties of null (reading 'useState')' (#2226) and Wasm SIMD unsupported errors when running pnpm start (#2279).\n\n6. Content limitations: Tweets are being cut off, with users looking for ways to adjust tweet length (#2277).\n\n7. Integration problems: The farcaster-client is failing to embed (#2302).\n\n8. Database compatibility: Using Postgres with Direct Client POST /agents/:agentId/set {character} is causing crashes with Exit status 7 (#2306).\n\n9. Hardware configuration: Users are seeking guidance on running Eliza locally with two graphical cards (#2304).",
"sources": [
"https://github.com/elizaOS/eliza/issues/2225",
"https://github.com/elizaOS/eliza/issues/2242",
"https://github.com/elizaOS/eliza/issues/2253",
"https://github.com/elizaOS/eliza/issues/2227",
"https://github.com/elizaOS/eliza/issues/2226",
"https://github.com/elizaOS/eliza/issues/2277",
"https://github.com/elizaOS/eliza/issues/2302",
"https://github.com/elizaOS/eliza/issues/2279",
"https://github.com/elizaOS/eliza/issues/2306",
"https://github.com/elizaOS/eliza/issues/2304"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2225",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2242",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2253",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2227",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2226",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2277",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2302",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2279",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2306",
"https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2304"
],
"videos": []
}
],
"topic": "issue"
},
{
"title": "Recent Pull Requests to elizaOS/eliza Repository",
"content": [
{
"text": "Several new features and improvements have been proposed to the elizaOS/eliza repository through recent pull requests. These include:\n\n1. Social media integrations with a Twitter follow feature (PR #2224) and NFT opportunities tweet functionality (PR #2297).\n\n2. Blockchain support expansions with plugins for NEAR Protocol Intents (PR #2244), Tron blockchain operations (PR #2275), and BNB chain support (PR #2278).\n\n3. Technical improvements including ARM64 fastembed support (PR #2259), a plugin for tee-verifiable-log (PR #1369), and a fix for the Supabase adapter (PR #2258).\n\n4. NFT market analysis capabilities with thin floor NFT opportunities (PR #2289).\n\nThese pull requests demonstrate ongoing development to enhance the platform's capabilities across social media integration, blockchain support, and technical infrastructure.",
"sources": [
"https://github.com/elizaOS/eliza/pull/2224",
"https://github.com/elizaOS/eliza/pull/2259",
"https://github.com/elizaOS/eliza/pull/1369",
"https://github.com/elizaOS/eliza/pull/2244",
"https://github.com/elizaOS/eliza/pull/2258",
"https://github.com/elizaOS/eliza/pull/2275",
"https://github.com/elizaOS/eliza/pull/2278",
"https://github.com/elizaOS/eliza/pull/2297",
"https://github.com/elizaOS/eliza/pull/2289"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2224",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2259",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/1369",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2244",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2258",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2275",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2278",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2297",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2289"
],
"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 13-14, 2025, there were 27 new pull requests with 7 merged, 12 new issues created, and 66 active contributors. The following day (January 14-15, 2025) saw increased PR activity with 34 new pull requests and a higher merge rate of 20 PRs, while new issues decreased to 7. The active contributor count remained relatively stable, with a slight decrease from 66 to 63 contributors.",
"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": 1736726400
}
},
"ai_news_elizaos_daily_md_2025-01-13": {
"filename": "2025-01-13.md",
"content": "# Eliza OS Recent Updates and Improvements\n\n## New Features and Enhancements\n\n### Blockchain and Cryptocurrency Integration\n- Added CoinGecko price per address functionality\n- Added support for gravity chain in EVM plugin\n- Integrated Gitcoin passport functionality\n- Added B\u00b2 Network plugin\n- Implemented OpenZeppelin governance plugin for EVM\n- Added cross-chain swaps through Squid Router\n- Added Birdeye plugin for Solana analytics\n- Added AGW support to the Abstract plugin\n\n### User Experience Improvements\n- Merged Eliza Installer with the current start.sh script\n- Added character creation template function to start.sh\n- Added Direct Client API with Delete Agent functionality\n- Added limit parameter to memory retrieval across adapters\n- Added an example service\n\n### Documentation and Internationalization\n- Added Farsi (Persian) readme\n- Added \"What Did You Get Done This Week? #9\" notes\n- Added weekly contributor meeting notes\n\n### Security and Verification\n- Added plugin for TEE verifiable log\n- Fixed derive key and updated remote attestation\n\n## Bug Fixes and Maintenance\n\n### Bug Fixes\n- Fixed IME causing multiple messages on Enter\n- Fixed missing @elizaos/plugin-b2\n- Fixed test/lint in develop branch\n- Resolved Windows path issue in pnpm build client\n- Fixed export of b2Plugin\n\n### Maintenance and Reverts\n- Reverted \"Add support for VoyageAI embeddings API\"\n- Fixed typo in README.md\n- Fixed minor typo in CHANGELOG.md\n\n# Open Source Development, RPGF, and Contributor Tools\n\n- Improved contributor leaderboard with weighted scoring system and bonding curve to gamify open-source development\n- Implemented tracking system for Retroactive Public Goods Funding (RPGF)\n- Shared various contribution tracking tools including @eas_eth, @deworkxyz, discord-summarizer, @coordinape, and @givepraise bot\n- Live preview available for the elizaOS project with publicly accessible code\n- Integration work with Gitcoin passport during grant rounds\n\n## Development Updates\n- Work in progress on v2 featuring full autonomy, unified wallet abstraction, plugin registry, easy setup, and modular design\n- Collaborative approach to crypto/AI space development with open source focus\n\n# Recent Pull Requests\n\n## Social Media Integrations\n- Twitter follow feature\n- NFT opportunities tweet functionality\n\n## Blockchain Support Expansions\n- Plugins for NEAR Protocol Intents\n- Tron blockchain operations\n- BNB chain support\n\n## Technical Improvements\n- ARM64 fastembed support\n- Plugin for tee-verifiable-log\n- Fix for the Supabase adapter\n- NFT market analysis capabilities with thin floor NFT opportunities\n\n# GitHub Activity Update\n\n- January 13-14, 2025: 27 new pull requests (7 merged), 12 new issues, 66 active contributors\n- January 14-15, 2025: 34 new pull requests (20 merged), 7 new issues, 63 active contributors"
},
"ai_news_elizaos_daily_discord_json_2025-01-13": {
"filename": "2025-01-13.json",
"content": {
"server": "elizaOS",
"title": "elizaOS Discord - 2025-01-13",
"date": 1736726400,
"stats": {
"totalMessages": 7504,
"totalUsers": 701
},
"categories": [
{
"channelId": "1253563209462448241",
"channelName": "discussion",
"summary": "# Analysis of Discord Chat in \"discussion\" Channel\n\n## 1. Summary\nThe chat primarily revolves around community discussions about the ai16z project, with minimal technical content. Most conversations focus on token price, market sentiment, and community dynamics rather than technical development. \n\nA few notable technical points emerged:\n- The Eliza framework is being used to build AI agents for various purposes including Twitter bots, Telegram bots, and specialized applications\n- There are discussions about a potential launchpad for AI projects being developed\n- Some users are building applications on top of the Eliza framework, including GOATAGI (an arena for AI agents to battle using price predictions) and Ninjapump (a platform for volume bots and bundle buying)\n- Several developers asked technical questions about implementing web search plugins, embedding configurations for Heurist, and running Eliza locally with different model providers\n- The project appears to be taking a \"wartime\" development approach with focus on building rather than social media engagement\n\nThe community seems divided between those focused on development/building and those concerned about token price and market perception. There's significant discussion about \"FUD\" (fear, uncertainty, doubt) affecting the project.\n\n## 2. FAQ\nQ: How can I build a Twitter bot using the Eliza framework? (asked by Heady Shotta) A: Check the coders channel for telegram bot questions (answered by BOSSU)\nQ: How can I find a comprehensive, up-to-date list of live agents that use the Eliza framework? (asked by AL) A: Check https://www.daos.fun/HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC under AUM and https://elizas.world/ (answered by DorianD)\nQ: How do I tweak Twitter settings for my agent to only respond to set accounts and not respond to previous tagged tweets? (asked by SEDANO_YGG) A: Check the coders channel for Twitter bot help (answered by BOSSU)\nQ: Why am I being forced to use Llama locally when trying to start default characters despite updating my .env with Anthropic keys? (asked by Iv/-\\nB) A: Unanswered\nQ: How do I configure Embedding for Heurist? (asked by LeonGamer) A: Check the coders channel for technical help (answered by BOSSU)\nQ: Has anybody built a way for agents to run their own Twitter group chats yet? (asked by Stealt\u210fyNinja.ADSC) A: Not that I know of (answered by shakejr)\nQ: I contributed a PR to Eliza. How do I join the coders-feed channel? (asked by Pythonberg) A: Head to the coders channel for tech stuff (answered by BOSSU)\nQ: Why were all packages updated to version 0.1.8 except the client-direct (latest is 0.1.7)? (asked by Jonatan Chaverri) A: Unanswered\nQ: How do I make a proposal for the DAO? (asked by Foro) A: Unanswered\nQ: Is there a NO CODE platform to build and deploy an AI agent for scouring CT and sites for alpha using ELIZA? (asked by CBK) A: Check agent dev school on YouTube for no code solutions (answered by BOSSU)\n\n## 3. Help Interactions\nHelper: DorianD | Helpee: AL | Context: Looking for a list of live agents using Eliza framework | Resolution: Provided two resources: daos.fun AUM list and elizas.world\nHelper: shakejr | Helpee: Stealt\u210fyNinja.ADSC | Context: Building Twitter group chats for agents | Resolution: Confirmed no known solution exists yet, suggested the user try building it\nHelper: jin | Helpee: Toony | Context: User unable to post in meme channel | Resolution: Manually verified the user and confirmed access to the channel\nHelper: jin | Helpee: MonteCrypto | Context: User contributed PR #2249 and wanted contributor role | Resolution: Added the role\nHelper: BOSSU | Helpee: Emmanuel Aguero | Context: Deploying eliza-starter to integrate in web app | Resolution: Directed to agent dev school on YouTube for deployment tips\nHelper: BOSSU | Helpee: Rihan | Context: Building text-to-song generator with poor PC specs | Resolution: Directed to coders channel for technical help\nHelper: BOSSU | Helpee: benji8 | Context: Building agent without OpenAI API key but with Perplexity API key | Resolution: Directed to coders channel for technical help\nHelper: BOSSU | Helpee: SecretRecipe | Context: Having trouble starting with fresh latest Eliza | Resolution: Directed to coders channel for technical help\n\n## 4. Action Items\nTechnical: Investigate why client-direct package wasn't updated to version 0.1.8 with other packages | Description: Inconsistency in package versioning noted by user | Mentioned By: Jonatan Chaverri\nTechnical: Build Twitter group chat functionality for agents | Description: Feature to allow agents to run their own Twitter group chats with verification capabilities | Mentioned By: Stealt\u210fyNinja.ADSC\nTechnical: Fix issue with Anthropic model provider selection | Description: User unable to use Anthropic despite configuring .env and character files | Mentioned By: Iv/-\\nB\nTechnical: Develop ElizaOS plugin for on-chain communication | Description: Enable seamless AI agent integration with on-chain communication capabilities | Mentioned By: talirezun\nTechnical: Create ElizaOS plugin for decentralized storage NFTs | Description: Allow AI agents to mint storage NFTs for self-sovereign data management | Mentioned By: talirezun\nDocumentation: Create comprehensive guide for web search plugin | Description: Documentation needed for implementing and using the web search plugin | Mentioned By: jomolopo\nDocumentation: Update documentation on embedding configuration for Heurist | Description: Guide needed for configuring embeddings with Heurist | Mentioned By: LeonGamer\nDocumentation: Create guide for Twitter bot settings configuration | Description: Documentation for configuring Twitter bots to respond selectively | Mentioned By: SEDANO_YGG\nFeature: Implement agent-to-agent Twitter group chats | Description: Allow agents to create and manage their own Twitter group chats | Mentioned By: Stealt\u210fyNinja.ADSC\nFeature: Develop no-code platform for building AI agents | Description: Platform for non-technical users to build agents without coding | Mentioned By: CBK",
"messageCount": 1306,
"userCount": 308
},
{
"channelId": "1300025221834739744",
"channelName": "\ud83d\udcbb-coders",
"summary": "# Analysis of Discord Chat in \"\ud83d\udcbb-coders\" Channel\n\n## 1. Summary\nThe chat primarily revolves around technical issues with the Eliza AI agent framework. Key discussions include:\n- Docker image optimization by Mike D, who reduced image size by removing image/audio/video processing components\n- Twitter integration challenges including authentication issues, rate limiting, and response formatting\n- Environment setup problems across different platforms (Windows, WSL, Ubuntu)\n- Database configuration issues with Supabase and PostgreSQL\n- Plugin development and implementation questions\n- Deployment strategies for AWS and other cloud platforms\n- Character file configuration and customization\n- Issues with embedding models and dimension mismatches\n- Multi-agent deployment and management\n\nUsers shared concrete solutions for WSL setup, database schema fixes, dependency issues, and workarounds for Twitter authentication. The conversation demonstrates a collaborative community working through various technical challenges with the Eliza framework.\n\n## 2. FAQ\nQ: How can I reduce the Docker image size for Eliza? (asked by 0xRider) A: Remove image processing, hugging face, audio processing, video processing, and local onnx components (answered by Mike D.)\nQ: How do I integrate the agents into Twitter chats? (asked by Stealt\u210fyNinja.ADSC) A: Use the Twitter plugin/client (answered by Mike D.)\nQ: How do I enable image generation? (asked by Heady Shotta) A: Set image generation to true in .env file and use OpenAI as the provider (answered by validsyntax)\nQ: How do I add custom actions? (asked by Adamc96) A: Custom actions are defined in plugins, look at the Twitter plugin for examples (answered by Mike D.)\nQ: How do I fix the node-llama-cpp installation issue? (asked by m2e_chris) A: Delete the .pnp.cjs file at the root level, run pnpm clean, pnpm install --no-frozen-lockfile, and pnpm build (answered by n00b_SaUce)\nQ: Has anyone got Eliza running on WSL Linux Ubuntu? (asked by bradtheaverage) A: Yes, follow the guide at elizaos.github.io/eliza/docs/guides/wsl/ (answered by cryptoAYA)\nQ: How do I run multiple agents at once? (asked by Jessy | Unicake\ud83e\udd84) A: Use pnpm start --characters=\"characters/1.character.json,characters/2.character.json\" (answered by elamore)\nQ: How do I set up the PostgreSQL DB adapter? (asked by suhelkap.eth) A: Unanswered\nQ: How do I make my agent respond to tweets addressing users in a certain way only when replying? (asked by mrpalettevibes) A: Unanswered\nQ: How do I fix the Twitter login failure issue? (asked by HamsterdamCapital) A: 2FA is optional, check credentials (answered by JSunDerulo)\n\n## 3. Help Interactions\nHelper: adonisabril | Helpee: bendermind | Context: Setting up WSL for Eliza on Windows | Resolution: Provided step-by-step instructions for setting up WSL, cloning the repo, and running Eliza\nHelper: JSunDerulo | Helpee: validsyntax | Context: Image model configuration | Resolution: Provided correct configuration settings for character file to use different image model providers\nHelper: n00b_SaUce | Helpee: Community | Context: Huggingface dependency error during build | Resolution: Shared solution to delete .pnp.cjs file and rebuild\nHelper: MonteCrypto | Helpee: bifkn | Context: Implementing confirmation for actions | Resolution: Directed to Shaw's dev school video about form providers that can be adapted for confirmations\nHelper: realcringo | Helpee: bifkn | Context: Build errors with latest develop update | Resolution: Suggested rolling back to a specific version of embedding.ts file\nHelper: Stealt\u210fyNinja.ADSC | Helpee: Community | Context: Discord opus error | Resolution: Shared workaround by removing Discord voice functionality\nHelper: custodian | Helpee: kingCuckDad | Context: Supabase adapter schema issues | Resolution: Shared working SQL schema that resolved the room creation function issue\nHelper: koloxarto | Helpee: michaelben | Context: Embedding model configuration | Resolution: Explained how to configure embedding models through environment variables\n\n## 4. Action Items\nType: Technical | Description: Fix the Twitter client to prevent posting message format instead of just the text content | Mentioned By: Snuggyverse_E\nType: Technical | Description: Implement event-driven architecture to decouple content generation from posting | Mentioned By: Kraus\nType: Technical | Description: Add support for storing cookies over agent restarts for Twitter authentication | Mentioned By: netdragonx\nType: Technical | Description: Fix the Supabase adapter schema to include all required functions | Mentioned By: 4n7m4n\nType: Technical | Description: Implement a REST API for character management without service restart | Mentioned By: jason1977\nType: Technical | Description: Fix embedding dimension mismatch issues | Mentioned By: Vaas\nType: Technical | Description: Add support for ARM64 architecture | Mentioned By: Morning3tar\nType: Technical | Description: Fix Discord client dependency issues | Mentioned By: PiagaShihari\nType: Feature | Description: Implement a Reddit client | Mentioned By: Oleg O.\nType: Feature | Description: Add confirmation flow for blockchain transactions | Mentioned By: tankjadu\nType: Feature | Description: Implement a Bitcoin plugin | Mentioned By: MonteCrypto\nType: Feature | Description: Add support for Twitter spaces | Mentioned By: trenchio\nType: Documentation | Description: Create better documentation for plugins and clients | Mentioned By: pagameba\nType: Documentation | Description: Create up-to-date beginner tutorial videos for visual learners | Mentioned By: Lint-Minux\nType: Documentation | Description: Document how to use the web-search plugin | Mentioned By: jomolopo\\",
"messageCount": 1849,
"userCount": 254
},
{
"channelId": "1300756641406521416",
"channelName": "ideas-feedback-rants",
"summary": "# Analysis of \"ideas-feedback-rants\" Discord Channel\n\n## 1. Summary\nThe channel primarily features discussions around AI agent development, music generation, trading strategies, and deployment solutions. Several users shared their projects and sought feedback. Key technical discussions included: (1) Using Eliza OS for various applications, including plugins and deployment in games like Sims 4; (2) Music generation with Suno and post-processing techniques in Ableton; (3) AI agent deployment platforms with one-click solutions; (4) Trading strategies incorporating futures and options with AI-managed hedging; (5) Prompt engineering for music generation with specific formatting suggestions. Multiple deployment solutions were highlighted, including Fleek's browser-based platform and a Terraform-based deployment system focusing on cost efficiency with AWS t4g instances. The community demonstrated collaborative problem-solving around audio enhancement, agent deployment, and prompt optimization.\n\n## 2. FAQ\nQ: For trading are \"Futures and options\" strategies being considered? (asked by Display Name) A: Unanswered\nQ: Any tips on tools to improve beat/vocals for generated songs? (asked by Dr. Neuro) A: Use compression and multiband compression, break into stems if possible, and map to tempo in Ableton (answered by boom)\nQ: What's the difference between your solution and nearai? (asked by WiseStone) A: Looking for cheapest possible solution using AWS free tier with terraform (answered by Mike D.)\nQ: Where can I send my community supply? (asked by BATURIN) A: To the DAO (answered by Bacon Egg & Cheese)\n\n## 3. Help Interactions\nHelper: boom | Helpee: Dr. Neuro | Context: Improving AI-generated music quality | Resolution: Suggested using compression, multiband compression, breaking into stems, and provided a detailed prompt for song generation\nHelper: Mike D. | Helpee: Community | Context: Deploying Eliza agents efficiently | Resolution: Shared GitHub repository for one-click deployment using terraform with AWS t4g instances\nHelper: masterdai | Helpee: Community | Context: Building Eliza OS plugins | Resolution: Shared a tutorial link on Twitter for plugin development\n\n## 4. Action Items\nType: Technical | Description: Experiment with compression and stem extraction for improving AI-generated music | Mentioned By: boom\nType: Technical | Description: Implement API for AI Agents to become a universal connector across platforms | Mentioned By: 0xTheDot\nType: Technical | Description: Create AI Market Making for Solana Memecoin with volume bot configuration | Mentioned By: Dreygo\nType: Feature | Description: Implement futures and options trading strategies with AI-managed hedging | Mentioned By: Display Name\nType: Feature | Description: Deploy Eliza in Sims 4 | Mentioned By: prism\nType: Technical | Description: Test and optimize Eliza deployment on AWS t4g.small instances | Mentioned By: Mike D.\nType: Feature | Description: Enable ordering from Amazon directly through Discord via AI agent | Mentioned By: Denko",
"messageCount": 66,
"userCount": 18
},
{
"channelId": "1308149076893630555",
"channelName": "spartan_holders",
"summary": "# Analysis of \"spartan_holders\" Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around concerns about DegenAI's development status, communication issues, and token price movements. Community members express frustration about the lack of clear information regarding DegenAI's roadmap, trading capabilities, and integration with the ai16z ecosystem. Several members, particularly \ucc0c G \u8dfb \u3058 PrudentSpartan, repeatedly request more transparent communication about development progress and tokenomics. There's uncertainty about whether DegenAI is actively trading, with some members claiming it is while others question the evidence. The conversation reveals a disconnect between what the development team considers sufficient communication and what token holders expect. Jin and Odilitime acknowledge the feedback about improving communications, mentioning that a website is coming soon and that they're working on systems to better inform the community. Despite the concerns, some members express continued confidence in the project, noting they're buying more tokens during price dips.\n\n## 2. FAQ\nQ: Is DegenAI holder excluded from Nomad whitelist? (asked by ap_serry \ud83e\udde9) A: We are dei partners. I have just accepted it. Maybe when degenai hits 500m and its expensive we will get some love from the projects (answered by Curtisdonthurtus)\nQ: Is Skely really the lead developer of degenai? (asked by 0xkamikaze) A: Unanswered\nQ: What did \"degenai week\" mean? (asked by \ucc0c G \u8dfb \u3058 PrudentSpartan) A: It meant a focus on DegenSpartanAi, he's now up and trading AND communicating on the timeline but still needs lots of work. (answered by Odilitime)\nQ: What is the DegenAI DAO wallet address? (asked by \ucc0c G \u8dfb \u3058 PrudentSpartan) A: AM84n1iLdxgVTAyENBcLdjXoyvjentTbu5Q6EpKV1PeG (answered by SHADOW |Zer0)\nQ: Will DegenSpartanai's X account be set as a subsidiary account of elizaOS_ai? (asked by xiaojiucai) A: Unanswered\nQ: Can you add DegenSpartanai to elizaOS affiliate account? (asked by cool.eth) A: Unanswered\n\n## 3. Help Interactions\nHelper: SHADOW |Zer0 | Helpee: \ucc0c G \u8dfb \u3058 PrudentSpartan | Context: Requesting the DAO wallet address | Resolution: Provided the wallet address AM84n1iLdxgVTAyENBcLdjXoyvjentTbu5Q6EpKV1PeG\nHelper: Odilitime | Helpee: Multiple users | Context: Explaining the status of DegenAI development | Resolution: Clarified that DegenAI is trading but still needs work, and that building takes time\nHelper: jin | Helpee: \ucc0c G \u8dfb \u3058 PrudentSpartan | Context: Feedback on visualization for documentation | Resolution: Acknowledged the feedback was good and mentioned they have visual designers ready\n\n## 4. Action Items\nTechnical: Implement DegenAI trading capabilities in production environment | Mentioned By: Multiple users\nTechnical: Connect DegenAI tokenomics with ai16z tokenomics whitepaper | Mentioned By: \ucc0c G \u8dfb \u3058 PrudentSpartan\nDocumentation: Create a clear roadmap for DegenAI showing now/next/future plans | Mentioned By: \ucc0c G \u8dfb \u3058 PrudentSpartan\nDocumentation: Publish wallet address and trading activity of DegenAI | Mentioned By: ZeroLearn\nDocumentation: Create less technical documentation similar to Zerebro team's approach | Mentioned By: \ucc0c G \u8dfb \u3058 PrudentSpartan\nFeature: Implement 8% DegenAI buyback as promised in tokenomics | Mentioned By: \ucc0c G \u8dfb \u3058 PrudentSpartan\nFeature: Add DegenSpartanai to elizaOS affiliate account | Mentioned By: cool.eth\nDocumentation: Post a summary of DegenAI progress on ai16z Twitter | Mentioned By: ZeroLearn\nDocumentation: Launch website with clear information about DegenAI | Mentioned By: Odilitime\nTechnical: Develop automated communication systems for project updates | Mentioned By: Odilitime",
"messageCount": 126,
"userCount": 24
},
{
"channelId": "1318770424632311930",
"channelName": "tokenomics",
"summary": "# Discord Channel \"tokenomics\" Analysis\n\n## 1. Summary\nThe discussion focuses on developing a tokenomics model and launchpad for ElizaOS agents. Key points include:\n\nDorianD and eskender.eth debated requiring AI16Z tokens for agent launches, with DorianD arguing it would create demand for AI16Z while eskender.eth expressed concerns about liquidity. Robin described a pre-sale platform with vesting mechanisms and \"Devotion\" staking to prevent sniping and dumping. The group discussed a \"Gauntlet of the Gods\" for community curation of agents.\n\n\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 shared a comprehensive ElizaOS Launchpad architecture including treasury management (BTC, ElizaOSsol, AI16Z, USDC), contribution mechanisms, developer payments in SOL rather than AI16Z to avoid sell pressure, and a staking system with quarterly rewards.\n\nDorianD emphasized studying pump.fun's model, which charges no upfront fees but takes 20% tribute when the bonding curve reaches 100%, and even rewards creators with 0.5 SOL. Jin suggested reframing the \"launchpad\" as an \"agent marketplace.\" The group noted competition from Alchemist AI and discussed Fleek's integration with ElizaOS. DorianD suggested embedding a 10% tribute mechanism in the codebase to ensure revenue even from forked implementations.\n\n## 2. FAQ\nQ: What is the risk with requiring AI16Z for agent launches? (asked by eskender.eth) A: It could create illiquidity in the primary pool post-bond, especially with full range. (answered by eskender.eth)\nQ: What is \"ElizaOSsol\"? (asked by DorianD) A: It's a liquid restaking token (LRT) similar to JupSOL or AI16zSOL. (answered 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)\nQ: What does \"If a tribute token is used\" mean? (asked by DorianD) A: It refers to whether creators are making their own token or just making an agent and paying fees in AI16Z or SOL. (answered 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)\nQ: How does pump.fun's model work? (asked by DorianD) A: They take 20% tribute when the bonding curve for 80% of coins sold hits 100%, and reward creators with 0.5 SOL. (answered by DorianD)\n\n## 3. Help Interactions\nHelper: Robin | Helpee: DorianD | Context: DorianD wanted to understand the pre-sale platform | Resolution: Robin explained their platform with vesting mechanisms and \"Devotion\" staking to prevent sniping and dumping.\nHelper: DorianD | Helpee: Channel members | Context: Understanding pump.fun's model | Resolution: DorianD explained how pump.fun charges no upfront fees but takes 20% tribute when bonding curve reaches 100%, and rewards creators with 0.5 SOL.\nHelper: \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 | Helpee: Channel members | Context: Needed a comprehensive tokenomics model | Resolution: Shared a detailed ElizaOS Launchpad architecture covering treasury management, contribution mechanisms, and staking systems.\n\n## 4. Action Items\nTechnical: Implement a staking system for AI16Z tokens | Description: Create quarterly rewards for staking with incentives for longer holding periods | 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\nTechnical: Consider embedding 10% tribute code in the Solana plugin | Description: Add code that ensures 10% tribute even when the repo is forked | Mentioned By: DorianD\nTechnical: Develop LST/LRT for ElizaOS | Description: Create a liquid staking token similar to JupSOL to support payments to devs and team | 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\nFeature: Create \"Gauntlet of the Gods\" | Description: A permissioned presale platform for agents to prove themselves worthy to the community | Mentioned By: Robin\nFeature: Develop an agent marketplace instead of a launchpad | Description: Reframe the concept as a marketplace for agents rather than a token launchpad | Mentioned By: jin\nDocumentation: Create proposal for vvaifu integration | Description: Develop a formal proposal to integrate with the existing vvaifu launchpad | Mentioned By: jin",
"messageCount": 101,
"userCount": 6
},
{
"channelId": "1301363808421543988",
"channelName": "\ud83e\udd47-partners",
"summary": "# Analysis of \ud83e\udd47-partners Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around several key developments for the ai16z project. The most significant technical discussion centers on a planned rebranding from \"ai16z\" to \"ElizaOS\" due to potential trademark issues with a16z (Andreessen Horowitz). This rebranding aims to better align the project's name with its technical foundation while avoiding legal complications. \n\nThe team is working on releasing tokenomics documentation, with Jin mentioning he's been working late to complete it. There are discussions about the ElizaOS framework's capabilities, with Shaw defending against criticism that mischaracterizes the framework's functionality. The GitHub repository shows significant development activity, with daily updates and numerous contributors.\n\nA \"Marketplace of Trust\" is mentioned as part of the tokenomics strategy, which will include a tribute model where projects built on ElizaOS contribute back to the ecosystem. The team is also working on V2 of the framework, which Shaw indicates will enable more autonomous capabilities.\n\nTechnical discussions include integration with various hardware platforms, including a potential robot implementation using Unitree H1 hardware. There are also conversations about the framework's architecture, its plugin system (with 77 plugins mentioned), and comparisons with competing frameworks.\n\n## 2. FAQ\nQ: Why is ai16z rebranding to ElizaOS? (asked by multiple users) A: To avoid potential trademark issues with a16z (Andreessen Horowitz) and to better align the name with the technical foundation of the project. (answered by Shaw)\nQ: Can the ticker symbol be changed? (asked by multiple users) A: It's technically unclear if it's possible, and the team is consulting with Solana Foundation. Any change would need to wait at least 2 months. (answered by Jin and Shaw)\nQ: What is the status of the tokenomics paper? (asked by \ucc0c G \u8dfb \u3058 PrudentSpartan) A: Jin is working on finishing the last 2 pages, and it will include multiple flywheel strategies to be implemented in phases. (answered by Jin)\nQ: What is DUNA? (asked by CypherPanther) A: It's a framework for DAOs developed by a16z crypto. (answered by jasyn_bjorn)\nQ: What are the key components of the ElizaOS ecosystem? (asked by multiple users) A: ElizaOS (tech), Eliza Labs (company), Eliza Foundation, and the ai16z token. (answered by Jin)\nQ: How does ElizaOS compare to other frameworks? (asked by multiple users) A: Shaw mentioned that critics often don't actually run the code, and most criticisms are inaccurate. The framework has 77 plugins and supports multimodality. (answered by Shaw and yikesawjeez)\nQ: When is the demo day? (asked by kimidan_) A: Jin mentioned another one is coming in 2 weeks. (answered by Jin)\nQ: What is the tribute model mentioned in tokenomics? (asked by multiple users) A: Projects built on ElizaOS will contribute 10% back to the treasury, which will be used to create buy pressure through LP. (answered by Shaw)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Multiple users | Context: Provided links to GitHub repositories, JSON data, and other resources to help users track development progress | Resolution: Shared comprehensive list of resources for monitoring project development\nHelper: yikesawjeez | Helpee: Multiple users | Context: Corrected misunderstandings about ElizaOS framework capabilities after a critical article was shared | Resolution: Detailed specific technical capabilities that were misrepresented in the criticism\nHelper: jin | Helpee: Multiple users | Context: Created a hackmd document to collect questions and answers about the rebranding | Resolution: Document created and shared for collaborative input\nHelper: shaw | Helpee: Multiple users | Context: Explained the reasoning behind rebranding and potential collaborations with a16z | Resolution: Clarified that rebranding would enable partnerships and collaborations currently on hold\nHelper: 0xcryptolord | Helpee: Multiple users | Context: Provided a PR communications framework for how to announce the rebranding | Resolution: Outlined a 7-point strategy focusing on growth and opportunity rather than legal concerns\n\n## 4. Action Items\nType: Technical | Description: Complete V2 of ElizaOS framework with improved autonomy features | Mentioned By: Shaw\nType: Technical | Description: Implement Twitter bot to summarize daily and weekly development activities | Mentioned By: Jin\nType: Technical | Description: Finish tokenomics paper with flywheel strategies | Mentioned By: Jin\nType: Technical | Description: Create a 3D show for \"clank tank\" (AI agents evaluating projects) | Mentioned By: Jin\nType: Documentation | Description: Update the ElizaOS website with new partnerships | Mentioned By: GV\nType: Documentation | Description: Complete FAQ document for rebranding | Mentioned By: Jin\nType: Documentation | Description: Create a one-pager introducing ai16z/ElizaOS | Mentioned By: 0xwitch\nType: Feature | Description: Develop integration with Unitree H1 robot hardware | Mentioned By: Ava\nType: Feature | Description: Implement Kanye-inspired Eliza agent | Mentioned By: Jin\nType: Feature | Description: Develop a marketplace for ElizaOS plugins | Mentioned By: Multiple users",
"messageCount": 2799,
"userCount": 135
},
{
"channelId": "1313222089271939102",
"channelName": "3d-ai-tv",
"summary": "# Analysis of 3d-ai-tv Discord Chat\n\n## 1. Summary\nThe chat revolves around the development of an AI-powered TV show system, primarily focusing on the \"AI Podcast\" which delivers GitHub updates in short 1-minute videos. SM Sith Lord manages the backend show generation system that produces JSON episode structures, while Boom handles the Unity frontend that visualizes these episodes with 3D characters. The team encountered issues with the news aggregator data accuracy and discussed technical improvements to the system.\n\nKey technical discussions included:\n- Debugging the JSON data flow from the news aggregator to the show generation system\n- Improving the Unity implementation with better character management and animation systems\n- Discussing modularization of the codebase to support multiple show formats\n- Addressing VRM vs. FBX format debate for 3D character models and animations\n- Implementing QA processes to ensure factual accuracy of generated content\n- Adding visual effects like particle systems for glitch animations\n- Planning for scaling to support multiple show formats (AI Podcast, Jedi Council, Block Tank)\n\nThe team is working on three distinct show formats: the AI Podcast (daily GitHub updates), Jedi Council (characters discussing blockchain topics), and Block Tank (a Shark Tank-style show for crypto pitches).\n\n## 2. FAQ\nQ: How does the news update system work for the AI Podcast? (asked by boom) A: The system checks a JSON file at \"https://elizaos.github.io/data/daily/summary.json\" which contains GitHub updates, then generates episode content based on this data (answered by SM Sith Lord)\nQ: Why does the download window pop up during recording and interrupt the flow? (asked by boom) A: This can be changed to happen after the show ends instead of during it (answered by SM Sith Lord)\nQ: How do we check if the AI is hallucinating information? (asked by boom) A: Fact-check against what the news aggregator provides; if accurate to that but still incorrect, notify the news aggregator maintainers (answered by SM Sith Lord)\nQ: Why use VRM format when FBX has better animation support? (asked by fishai) A: VRM is used for hopes of interoperability and is heavily used in Asia for V-Tubing and 3D avatars (answered by VEGA)\nQ: Can your framework plug in any Eliza? (asked by Odilitime) A: Yes, and they're working with LaserShark to swap Anthropic with Eliza + character personalities (answered by SM Sith Lord)\nQ: What shows are currently being developed? (asked by VEGA) A: Three shows: AI Podcast (GitHub updates), Jedi Council (blockchain discussions), and Block Tank (Shark Tank style) (answered by SM Sith Lord)\n\n## 3. Help Interactions\nHelper: SM Sith Lord | Helpee: boom | Context: Issues with the show runner not loading specific GitHub updates | Resolution: Provided a fixed version of the code that outputs JSON info to console for debugging\nHelper: SM Sith Lord | Helpee: boom | Context: Download window interrupting recording flow | Resolution: Agreed to modify code to have JSON download happen after show ends\nHelper: SM Sith Lord | Helpee: boom | Context: Confusion about QA process for checking content accuracy | Resolution: Explained the process of checking generated content against the news aggregator JSON\nHelper: fishai | Helpee: boom | Context: Spaghetti code and scaling issues with Unity implementation | Resolution: Suggested using Game Creator 2 package and implementing a character controller system\nHelper: PENDINGREALITY | Helpee: fishai | Context: Need for VRM animation format support | Resolution: Shared a GitHub repository for converting animation clips to VRMA format\n\n## 4. Action Items\nTechnical: Move JSON download to happen after show ends instead of during recording | Description: Modify show runner to avoid interrupting recording flow | Mentioned By: SM Sith Lord\nTechnical: Implement character controller system for easier character management | Description: Create a modular system to handle different character prefabs | Mentioned By: fishai\nTechnical: Add particle effects to glitch animations | Description: Enhance visual effects for character transitions | Mentioned By: boom\nTechnical: Implement word detection in dialogue for triggering special effects | Description: Parse dialogue text to trigger effects when specific words are mentioned | Mentioned By: boom\nTechnical: Add more character-specific animations | Description: Create 2-3 hero animations per character to enhance personality | Mentioned By: boom\nDocumentation: Create documentation for the Jedi Council show | Description: Document the technical implementation details | Mentioned By: SM Sith Lord\nDocumentation: Create flow map of the entire program | Description: Generate comprehensive documentation of the codebase structure | Mentioned By: boom\nFeature: Create a meta episode explaining how the show works | Description: Generate a special episode where characters explain the system | Mentioned By: boom\nFeature: Add Degen Spartan for crypto market updates | Description: Include character commentary on current market conditions | Mentioned By: Smedroc\nFeature: Implement a system for interviewing AIs live | Description: Create audio-aware AIs that can respond in a stream context | Mentioned By: boom",
"messageCount": 803,
"userCount": 10
},
{
"channelId": "1328592959444095038",
"channelName": "associates",
"summary": "# Analysis of \"associates\" Discord Channel\n\n## 1. Summary\nThe chat primarily revolves around the creation of a new \"associates\" channel for users holding 10,000+ AI16Z tokens, compared to \"partners\" who hold 100,000+ tokens. The main technical discussion centers on the implementation of the tip.cc bot for distributing tokens within the community. Jin demonstrates various tipping features including airdrops, triviadrops, mathdrops, and red envelopes to distribute AI16Z tokens to channel members. A significant governance discussion emerges about whether associates should have read-only access to the partners channel, with various arguments presented about transparency versus exclusivity. Jin proposes creating an intermediate \"executive\" role (50k tokens) between associates and partners. The community also discusses potential bounties for associates to earn more tokens by contributing skills to the project.\n\n## 2. FAQ\nQ: How much is associates? (asked by kingdode) A: 10k (answered by anon)\nQ: How would the token rebrand work? (asked by Supertramp) A: They will enable voting in 1-2 months so we can change it without migration (answered by shaw)\nQ: What are the requirements for associates? (asked by Kush) A: 10k (answered by anon)\nQ: How does the $tip bot work? (asked by 00n00) A: Check if you have a balance with \"$balances\" and you can tip someone by writing \"$tip\" then add the discord handle (answered by Srn Srnzzz | plebian)\nQ: What's the amount for executive? (asked by flockaflame) A: 50k ai16z (implied by jin)\nQ: What's the best way to approach the team for a partnership? (asked by thebasement) A: https://eliza.gg/partnerships (answered by jin)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Channel members | Context: Demonstrating tip.cc bot functionality | Resolution: Successfully showed airdrops, triviadrops, mathdrops, and red envelopes to distribute AI16Z tokens\nHelper: jin | Helpee: Smedroc - Street urchin @ ai16z | Context: Request for PNG file of duct tape | Resolution: Provided GitHub repo link with tape assets\nHelper: Srn Srnzzz | plebian | Helpee: 00n00 | Context: Explaining how the tip bot works | Resolution: Explained checking balances and tipping process\nHelper: jin | Helpee: Community | Context: Balancing access to partner channel | Resolution: Implemented read-only access to partner channel for associates\n\n## 4. Action Items\nType: Technical | Description: Create an \"executive\" role for users with 50k AI16Z tokens | Mentioned By: jin\nType: Technical | Description: Implement bounties aligned with community skills to earn more tokens | Mentioned By: jin\nType: Technical | Description: Create a system for associates to contribute to DAO direction alongside partners | Mentioned By: MicoM.ron\nType: Documentation | Description: Update documentation on tip.cc bot usage for the community | Mentioned By: jin\nType: Feature | Description: Consider including associates in future airdrops at a lower rate than partners | Mentioned By: Srn Srnzzz | plebian\nType: Feature | Description: Create a mechanism for associates to earn more tokens through contributions | Mentioned By: jin",
"messageCount": 454,
"userCount": 70
}
]
}
},
"ai_news_elizaos_daily_discord_md_2025-01-13": {
"filename": "2025-01-13.md",
"content": "# elizaOS Discord - 2025-01-13\n\n## Overall Discussion Highlights\n\n### Rebranding from ai16z to ElizaOS\n- The project is planning to rebrand from \"ai16z\" to \"ElizaOS\" due to potential trademark issues with a16z (Andreessen Horowitz)\n- This rebranding aims to better align the project's name with its technical foundation while avoiding legal complications\n- The team is consulting with Solana Foundation about whether the token ticker can be changed, but any change would need to wait at least 2 months\n- Shaw explained that rebranding would enable partnerships and collaborations currently on hold\n\n### ElizaOS Framework Development\n- The team is working on V2 of the framework with improved autonomy features\n- GitHub repository shows significant development activity with daily updates and numerous contributors\n- The framework currently has 77 plugins and supports multimodality\n- Docker image optimization by Mike D reduced image size by removing image/audio/video processing components\n- Several users are building applications on top of the Eliza framework, including GOATAGI and Ninjapump\n\n### Tokenomics and Marketplace\n- Jin is finalizing a tokenomics paper that will include multiple flywheel strategies to be implemented in phases\n- A \"Marketplace of Trust\" is being developed as part of the tokenomics strategy\n- Projects built on ElizaOS will contribute 10% back to the treasury through a tribute model\n- DorianD suggested embedding this 10% tribute mechanism in the codebase to ensure revenue even from forked implementations\n- Discussion about reframing the \"launchpad\" concept as an \"agent marketplace\"\n\n### AI TV Show Development\n- Team is developing an AI-powered TV show system with three formats:\n - AI Podcast (daily GitHub updates)\n - Jedi Council (characters discussing blockchain topics)\n - Block Tank (a Shark Tank-style show for crypto pitches)\n- SM Sith Lord manages the backend show generation system while Boom handles the Unity frontend\n- Technical challenges include JSON data flow issues and debates about 3D model formats (VRM vs. FBX)\n\n### Community Structure\n- New \"associates\" channel created for users holding 10,000+ AI16Z tokens (compared to \"partners\" with 100,000+)\n- Jin proposed creating an intermediate \"executive\" role (50k tokens) between associates and partners\n- Tip.cc bot implemented for distributing tokens within the community through airdrops, triviadrops, and red envelopes\n\n### DegenAI Concerns\n- Community members expressed frustration about lack of clear information regarding DegenAI's roadmap and integration with the ai16z ecosystem\n- Uncertainty about whether DegenAI is actively trading, with conflicting claims\n- Jin and Odilitime acknowledged feedback about improving communications, mentioning a website is coming soon\n\n## Key Questions & Answers\n\n**Q: How can I reduce the Docker image size for Eliza?** \nA: Remove image processing, hugging face, audio processing, video processing, and local onnx components (answered by Mike D.)\n\n**Q: How do I run multiple agents at once?** \nA: Use `pnpm start --characters=\"characters/1.character.json,characters/2.character.json\"` (answered by elamore)\n\n**Q: Why is ai16z rebranding to ElizaOS?** \nA: To avoid potential trademark issues with a16z (Andreessen Horowitz) and to better align the name with the technical foundation of the project. (answered by Shaw)\n\n**Q: How does the news update system work for the AI Podcast?** \nA: The system checks a JSON file at \"https://elizaos.github.io/data/daily/summary.json\" which contains GitHub updates, then generates episode content based on this data (answered by SM Sith Lord)\n\n**Q: What is the risk with requiring AI16Z for agent launches?** \nA: It could create illiquidity in the primary pool post-bond, especially with full range. (answered by eskender.eth)\n\n**Q: How does pump.fun's model work?** \nA: They take 20% tribute when the bonding curve for 80% of coins sold hits 100%, and reward creators with 0.5 SOL. (answered by DorianD)\n\n**Q: What is the DegenAI DAO wallet address?** \nA: AM84n1iLdxgVTAyENBcLdjXoyvjentTbu5Q6EpKV1PeG (answered by SHADOW |Zer0)\n\n**Q: How can I find a comprehensive list of live agents that use the Eliza framework?** \nA: Check https://www.daos.fun/HeLp6NuQkmYB4pYWo2zYs22mESHXPQYzXbB8n4V98jwC under AUM and https://elizas.world/ (answered by DorianD)\n\n**Q: Any tips on tools to improve beat/vocals for generated songs?** \nA: Use compression and multiband compression, break into stems if possible, and map to tempo in Ableton (answered by boom)\n\n## Community Help & Collaboration\n\n- **WSL Setup Help**: adonisabril provided step-by-step instructions for setting up WSL, cloning the repo, and running Eliza to help bendermind\n- **Database Schema Fix**: custodian shared a working SQL schema that resolved room creation function issues for kingCuckDad\n- **Node-llama-cpp Installation**: n00b_SaUce shared a solution to delete .pnp.cjs file and rebuild to fix Huggingface dependency errors\n- **Music Generation**: boom provided detailed advice to Dr. Neuro on improving AI-generated music quality using compression techniques and shared an optimized prompt for song generation\n- **Deployment Solution**: Mike D. shared a GitHub repository for one-click deployment using terraform with AWS t4g instances for cost-efficient hosting\n- **Discord Error Fix**: Stealt\u210fyNinja.ADSC shared a workaround for Discord opus errors by removing Discord voice functionality\n\n## Action Items\n\n### Technical\n- Complete V2 of ElizaOS framework with improved autonomy features (Mentioned by Shaw)\n- Implement a staking system for AI16Z tokens with quarterly rewards (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- Consider embedding 10% tribute code in the Solana plugin (Mentioned by DorianD)\n- Fix the Twitter client to prevent posting message format instead of just the text content (Mentioned by Snuggyverse_E)\n- Implement event-driven architecture to decouple content generation from posting (Mentioned by Kraus)\n- Fix embedding dimension mismatch issues (Mentioned by Vaas)\n- Add support for ARM64 architecture (Mentioned by Morning3tar)\n- Fix Discord client dependency issues (Mentioned by PiagaShihari)\n- Move JSON download to happen after show ends instead of during recording (Mentioned by SM Sith Lord)\n- Implement character controller system for easier character management (Mentioned by fishai)\n- Create an \"executive\" role for users with 50k AI16Z tokens (Mentioned by jin)\n- Implement 8% DegenAI buyback as promised in tokenomics (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n\n### Documentation\n- Create comprehensive guide for web search plugin (Mentioned by jomolopo)\n- Update documentation on embedding configuration for Heurist (Mentioned by LeonGamer)\n- Create guide for Twitter bot settings configuration (Mentioned by SEDANO_YGG)\n- Create better documentation for plugins and clients (Mentioned by pagameba)\n- Create up-to-date beginner tutorial videos for visual learners (Mentioned by Lint-Minux)\n- Complete FAQ document for rebranding (Mentioned by Jin)\n- Create a one-pager introducing ai16z/ElizaOS (Mentioned by 0xwitch)\n- Create a clear roadmap for DegenAI showing now/next/future plans (Mentioned by \ucc0c G \u8dfb \u3058 PrudentSpartan)\n- Publish wallet address and trading activity of DegenAI (Mentioned by ZeroLearn)\n\n### Features\n- Implement agent-to-agent Twitter group chats (Mentioned by Stealt\u210fyNinja.ADSC)\n- Develop no-code platform for building AI agents (Mentioned by CBK)\n- Implement a Reddit client (Mentioned by Oleg O.)\n- Add confirmation flow for blockchain transactions (Mentioned by tankjadu)\n- Implement a Bitcoin plugin (Mentioned by MonteCrypto)\n- Add support for Twitter spaces (Mentioned by trenchio)\n- Create \"Gauntlet of the Gods\" for community curation of agents (Mentioned by Robin)\n- Develop an agent marketplace instead of a launchpad (Mentioned by jin)\n- Implement futures and options trading strategies with AI-managed hedging (Mentioned by Display Name)\n- Add Degen Spartan for crypto market updates in AI TV shows (Mentioned by Smedroc)\n- Add DegenSpartanai to elizaOS affiliate account (Mentioned by cool.eth)"
},
"github_summaries_daily_2025-01-14": {
"filename": "2025-01-14.md",
"content": "# ElizaOS Daily Update (Jan 14, 2025)\n\n## OVERVIEW \nToday, significant advancements were made in the ElizaOS project, including the integration of Gitcoin passport functionality for enhanced trust in AI agents. Documentation was updated with meeting notes, and several bug fixes were implemented to improve system stability. The team also focused on refining existing features and addressing user-reported issues.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Feature Enhancements\n- Integrated Gitcoin passport to allow AI agents to assess Ethereum address credibility, aiding in decision-making ([#2296](https://github.com/elizaos/eliza/pull/2296)).\n- Added Delete Agent functionality to the Direct Client API, enhancing user control over agent management ([#2267](https://github.com/elizaos/eliza/pull/2267)).\n- Introduced a character creation template function in the `start.sh` script to streamline character setup ([#2232](https://github.com/elizaos/eliza/pull/2232)).\n\n### Bug Fixes\n- Resolved multiple message sending issue when using IME, improving user experience ([#2272](https://github.com/elizaos/eliza/issues/2272)).\n- Fixed embedding errors by reverting a previous feature related to VoyageAI embeddings API ([#2290](https://github.com/elizaos/eliza/pull/2290)).\n- Addressed Windows path issues in the build process, ensuring compatibility ([#2240](https://github.com/elizaos/eliza/pull/2240)).\n\n### Documentation Updates\n- Added notes from weekly contributor meetings to enhance transparency and collaboration within the team ([#2285](https://github.com/elizaos/eliza/pull/2285)).\n- Corrected a typo in the README file to improve clarity ([#2256](https://github.com/elizaos/eliza/pull/2256)).\n\n## CLOSED ISSUES\n\n### Resolved Bugs\n- Fixed the issue where the chat input sent multiple messages when using IME, enhancing input reliability ([#2272](https://github.com/elizaos/eliza/issues/2272)).\n- Closed the issue regarding model loading failures from the `.env` file, ensuring correct model initialization ([#2250](https://github.com/elizaos/eliza/issues/2250)).\n- Resolved lock file errors that were preventing project setup on Ubuntu, improving onboarding for new developers ([#2183](https://github.com/elizaos/eliza/issues/2183)).\n\n## NEW ISSUES\n\n### User-Reported Challenges\n- Users reported issues with the `POST /agents/:agentId/set {character}` endpoint crashing, indicating potential stability concerns ([#2306](https://github.com/elizaos/eliza/issues/2306)).\n- A request for guidance on running Eliza locally with multiple graphical cards was raised, highlighting a need for better documentation ([#2304](https://github.com/elizaos/eliza/issues/2304)).\n- Users are experiencing compilation runtime errors when executing the `pnpm start` command, suggesting a need for troubleshooting support ([#2279](https://github.com/elizaos/eliza/issues/2279))."
},
"github_summaries_week_latest_2025-12-21.md": {
"filename": "2025-12-21.md",
"content": "# Overall Project Weekly Summary (Dec 21 - 27, 2025)\n\n## Executive Summary\nThis week, the ElizaOS project executed a focused push to enhance platform quality, delivering significant improvements to both user experience and backend stability. We rapidly resolved a large number of UI issues in the agent builder, while simultaneously shipping foundational upgrades for performance, reliability, and developer extensibility across core services and plugins.\n\n### Key Strategic Initiatives & Outcomes\n\n**Refining the User Experience**\n*To make our platform more intuitive and effective for users, we focused on identifying and rapidly resolving interface issues.*\n- A large batch of UI/UX refinements for the agent builder were resolved in [elizaos/eliza](https://github.com/elizaos/eliza), including improvements to button consistency ([#6274](https://github.com/elizaos/eliza/issues/6274)), adding an \"unsaved changes\" warning ([#6275](https://github.com/elizaos/eliza/issues/6275)), and other usability enhancements.\n- A new feature was added to the [elizaos-plugins/plugin-openai](https://github.com/elizaos-plugins/plugin-openai) to support real-time streaming of text generation, making agent interactions feel more immediate and responsive.\n- A new wave of issues was identified across multiple plugins to improve agent chat behavior, such as ensuring the most recent conversation opens by default ([#6281](https://github.com/elizaos-plugins/plugin-twitter/issues/6281)) and fixing conversation duplication bugs ([#6282](https://github.com/elizaos-plugins/plugin-twitter/issues/6282)).\n\n**Strengthening Platform Performance and Stability**\n*To ensure our framework is robust and scalable, we made critical updates to improve system reliability and throughput.*\n- The core platform in [elizaos/eliza](https://github.com/elizaos/eliza) was upgraded to use true Server-Sent Events (SSE), replacing less efficient polling methods for real-time updates ([#5930](https://github.com/elizaos/eliza/issues/5930)).\n- The [elizaos-plugins/plugin-knowledge](https://github.com/elizaos-plugins/plugin-knowledge) repository introduced configurable rate limiting for high-throughput APIs, providing greater control and stability under heavy load ([#49](https://github.com/elizaos-plugins/plugin-knowledge/pull/49)).\n- Significant refactoring and type-safety improvements were completed in the [elizaos-plugins/plugin-discord](https://github.com/elizaos-plugins/plugin-discord) plugin, resolving TypeScript errors and overhauling message handling logic for better stability ([#38](https://github.com/elizaos-plugins/plugin-discord/pull/38), [#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)).\n\n**Improving Developer Experience and Extensibility**\n*To empower our community and accelerate future development, we enhanced the core framework to make it easier to build powerful, type-safe plugins.*\n- The core runtime in [elizaos/eliza](https://github.com/elizaos/eliza) was updated to support generic types for custom event handlers, improving type safety and code clarity for plugin developers ([#6277](https://github.com/elizaos/eliza/pull/6277)).\n- A proposal for a new multi-bot voice architecture was submitted in the [elizaos-plugins/plugin-discord](https://github.com/elizaos-plugins/plugin-discord) repository, paving the way for future support of audio channels ([#36](https://github.com/elizaos-plugins/plugin-discord/pull/36)).\n\n### Cross-Repository Coordination\nThis week highlighted a tight feedback loop between user-facing plugins and the core platform. A coordinated effort to improve the agent builder UI saw numerous issues identified in the `plugin-discord` repository on one day and resolved in the main `elizaos/eliza` repository the next. Additionally, the new streaming text generation feature in `plugin-openai` is now awaiting integration with the main `elizaos` repository, demonstrating how plugin innovations are being prepared for project-wide rollout.\n\n## Repository Spotlights\n\n### elizaos/eliza\n- **UI/UX Overhaul:** A significant number of issues were closed to refine the agent builder and dashboard experience, including redesigning the dashboard as the primary landing page ([#6222](https://github.com/elizaos/eliza/issues/6222)), reducing long loading times ([#6248](https://github.com/elizaos/eliza/issues/6248)), and resolving a large set of UI bugs ([#6270](https://github.com/elizaos/eliza/issues/6270), [#6271](https://github.com/elizaos/eliza/issues/6271), [#6273](https://github.com/elizaos/eliza/issues/6273), [#6275](https://github.com/elizaos/eliza/issues/6275)).\n- **Core Framework Enhancements:** Generic type support was added for custom event handlers to improve developer experience and type safety ([#6277](https://github.com/elizaos/eliza/pull/6277)). The platform was also updated to use true SSE streaming instead of polling ([#5930](https://github.com/elizaos/eliza/issues/5930)).\n- **Bug Fixes:** A critical bug preventing agents from responding due to a `MessageBusService` error was resolved ([#6140](https://github.com/elizaos/eliza/issues/6140)).\n\n### elizaos-plugins/plugin-openai\n- **Streaming Support:** A major feature was added to enable streaming for text generation, allowing for real-time output delivery. This work is awaiting integration with the main ElizaOS repository ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)).\n- **New Feature Requests:** New issues were opened to improve user experience, including a proposal to summarize chat names ([#6278](https://github.com/elizaos-plugins/plugin-openai/issues/6278)) and add a user feedback button ([#6280](https://github.com/elizaos-plugins/plugin-openai/issues/6280)).\n\n### elizaos-plugins/plugin-discord\n- **Major Refactoring & Bug Fixes:** The plugin underwent significant maintenance, including resolving TypeScript type errors ([#38](https://github.com/elizaos-plugins/plugin-discord/pull/38), [#37](https://github.com/elizaos-plugins/plugin-discord/pull/37)), overhauling message handling logic ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)), and introducing a new permission system ([#34](https://github.com/elizaos-plugins/plugin-discord/pull/34)).\n- **Issue Identification:** A large volume of new issues were opened, primarily focused on refining the agent builder UI/UX ([#6270](https://github.com/elizaos-plugins/plugin-discord/issues/6270)-[#6275](https://github.com/elizaos-plugins/plugin-discord/issues/6275)), which drove rapid development in the main `elizaos/eliza` repository.\n- **Architectural Proposal:** A new multi-bot voice architecture was proposed to support audio channels and progressive updates in the future ([#36](https://github.com/elizaos-plugins/plugin-discord/pull/36)).\n\n### elizaos-plugins/plugin-knowledge\n- **Enhanced API Rate Limiting:** A new feature was merged to add configurable rate limits for high-throughput APIs, improving system stability. The update also increased default limits fivefold to better support demanding use cases ([#49](https://github.com/elizaos-plugins/plugin-knowledge/pull/49)).\n- **New Issues:** Several issues were opened to improve agent chat behavior ([#6281](https://github.com/elizaos-plugins/plugin-knowledge/issues/6281), [#6282](https://github.com/elizaos-plugins/plugin-knowledge/issues/6282)) and fix UI and documentation problems ([#6283](https://github.com/elizaos-plugins/plugin-knowledge/issues/6283), [#6284](https://github.com/elizaos-plugins/plugin-knowledge/issues/6284)).\n\n### elizaos-plugins/plugin-twitter\n- **Bug Fix:** A fix was merged to ensure that changes to posting enablement settings are applied immediately and consistently, improving the reliability of the plugin's core functionality ([#42](https://github.com/elizaos-plugins/plugin-twitter/pull/42)).\n- **Future Work Identified:** New issues were created to address bugs in agent chat behavior ([#6281](https://github.com/elizaos-plugins/plugin-twitter/issues/6281), [#6282](https://github.com/elizaos-plugins/plugin-twitter/issues/6282)) and to improve UI consistency and documentation ([#6283](https://github.com/elizaos-plugins/plugin-twitter/issues/6283), [#6284](https://github.com/elizaos-plugins/plugin-twitter/issues/6284))."
},
"github_summaries_month_latest_2025-12-01.md": {
"filename": "2025-12-01.md",
"content": "# Overall Project Monthly Summary (December 2025)\n\n## Executive Summary\nDecember was a pivotal month focused on strengthening the ElizaOS foundation and strategically expanding its capabilities. We executed a major push to improve core platform stability and defined a clear vision for a future user experience overhaul. Simultaneously, we expanded our agent ecosystem with key Web3 plugins and initiated a coordinated effort to introduce real-time streaming, making our agents more responsive and interactive.\n\n### Key Strategic Initiatives & Outcomes\n\n**Strengthening the Core Platform for Stability and Scale**\nTo support increasingly complex and autonomous agents, we invested heavily in making the underlying framework more robust, secure, and modern.\n- A major server refactoring was completed in [elizaos/eliza](https://github.com/elizaos/eliza) to optimize the codebase and improve reliability ([#6199](https://github.com/elizaos/eliza/pull/6199)).\n- Code quality and type safety were significantly enhanced by resolving build errors across the entire `elizaos/eliza` monorepo ([#6218](https://github.comcom/elizaos/eliza/pull/6218)).\n- A critical security vulnerability in character secret encryption was fixed, ensuring user data is properly protected ([#6217](https://github.comcom/elizaos/eliza/pull/6217)).\n- Agent autonomy was improved by enhancing how tools interact with memory in the Master Control Program, laying the groundwork for more sophisticated reasoning ([elizaos-plugins/plugin-mcp](https://github.com/elizaos-plugins/plugin-mcp), [#19](https://github.com/elizaos-plugins/plugin-mcp/pull/19)).\n\n**Expanding the Agent Ecosystem into Web3 and Beyond**\nWe continued to execute on our mission to thrive in both Web2 and Web3 by adding powerful new tools for agents to use.\n- The [elizaos-plugins/registry](https://github.com/elizaos-plugins/registry) was expanded with three new community plugins, adding capabilities for DeFi ([#235](https://github.com/elizaos-plugins/registry/pull/235)), decentralized social media ([#243](https://github.com/elizaos-plugins/registry/pull/243)), and communication ([#242](https://github.com/elizaos-plugins/registry/pull/242)).\n- The new self-hosted Farcaster plugin is a key step toward greater agent autonomy, allowing agents to connect directly to the network without relying on third-party APIs ([#243](https://github.com/elizaos-plugins/registry/pull/243)).\n\n**Laying the Groundwork for Real-Time, Responsive Agents**\nFor agents to feel truly interactive, they must process and respond to information as it arrives, not just after a long pause.\n- Work was initiated across multiple plugins to add streaming support, a foundational feature for enabling real-time, conversational AI. This effort included the [OpenAI](https://github.com/elizaos-plugins/plugin-openai) ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)), [Anthropic](https://github.com/elizaos-plugins/plugin-anthropic) ([#12](https://github.com/elizaos-plugins/plugin-anthropic/pull/12)), and [OpenRouter](https://github.com/elizaos-plugins/plugin-openrouter) ([#21](https://github.com/elizaos-plugins/plugin-openrouter/pull/21)) plugins.\n\n**Refining the User Experience and Planning for the Future**\nMaking the platform intuitive is key to growing our community. This month, we cleared existing UI issues and laid out a detailed plan for a major user experience overhaul.\n- A large number of UI/UX issues were resolved in [elizaos/eliza](https://github.com/elizaos/eliza), streamlining the interface by consolidating navigation ([#6173](https://github.com/elizaos/eliza/issues/6173)) and improving visual feedback ([#6235](https://github.com/elizaos/eliza/issues/6235)).\n- A comprehensive plan for a redesigned dashboard and guided user onboarding was established through the creation of over 20 new strategic issues in [elizaos/eliza](https://github.com/elizaos/eliza) ([#6221](https://github.com/elizaos/eliza/issues/6221), [#6222](https://github.com/elizaos/eliza/issues/6222)).\n- The developer experience was simplified by making ElizaOS Cloud the default AI provider in the CLI, complete with a new browser-based login flow ([elizaos/eliza](https://github.com/elizaos/eliza), [#6208](https://github.com/elizaos/eliza/pull/6208)).\n\n### Cross-Repository Coordination\nThis month saw a coordinated push to standardize and modernize key functionalities across the ElizaOS ecosystem.\n- **Unified Streaming Support:** A parallel effort began across the `plugin-openai`, `plugin-anthropic`, and `plugin-openrouter` repositories to implement streaming. This shared initiative will bring more responsive, real-time interactions to agents regardless of the underlying model provider.\n- **Architectural Alignment:** Following the modernization of core APIs in `elizaos/eliza`, work began in the `plugin-telegram` ([#22](https://github.com/elizaos-plugins/plugin-telegram/pull/22)) and `plugin-discord` ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)) plugins to refactor their messaging systems. This alignment ensures all plugins communicate with the core framework in a standardized, more modular way.\n\n## Repository Spotlights\n\n### elizaos/eliza\nThe core repository saw extensive activity focused on stability, user experience, and future planning.\n- Completed a major server refactoring to optimize the codebase and API structure ([#6199](https://github.com/elizaos/eliza/pull/6199)).\n- Resolved TypeScript build errors across the monorepo, significantly improving code stability and type safety ([#6218](https://github.com/elizaos/eliza/pull/6218)).\n- Updated all project dependencies to their latest versions, resolving compatibility issues ([#6210](https://github.com/elizaos/eliza/pull/6210)).\n- Fixed a critical security bug in character secret encryption ([#6217](https://github.comcom/elizaos/eliza/pull/6217)).\n- Streamlined the developer experience by making ElizaOS Cloud the default provider in the CLI, adding a new browser-based login flow ([#6208](https://github.com/elizaos/eliza/pull/6208)).\n- Closed a large batch of UI/UX issues, including consolidating the sidebar ([#6173](https://github.com/elizaos/eliza/issues/6173)) and adding an \"Unsaved Changes\" warning ([#6183](https://github.com/elizaos/eliza/issues/6183)).\n- Opened over 20 new issues to define a comprehensive overhaul of the dashboard ([#6222](https://github.com/elizaos/eliza/issues/6222)) and agent creation workflow.\n- Addressed community concerns regarding token snapshot eligibility for Tangem wallet users ([#6158](https://github.com/elizaos/eliza/issues/6158), [#6211](https://github.com/elizaos/eliza/issues/6211)).\n\n### elizaos-plugins/registry\nThe registry was expanded with new plugins, broadening agent capabilities in Web2 and Web3.\n- Added the Moralis DeFi plugin (`@pyboom/plugin-moralis-v2`) to provide agents with Moralis v2 functionalities ([#235](https://github.com/elizaos-plugins/registry/pull/235)).\n- Integrated the OpenChat plugin (`@tonyflam/plugin-openchat`) for agent communication ([#242](https://github.com/elizaos-plugins/registry/pull/242)).\n- Introduced a self-hosted Farcaster plugin (`plugin-farcaster-local-hub`) that removes dependency on third-party APIs ([#243](https://github.com/elizaos-plugins/registry/pull/243)).\n\n### elizaos-plugins/plugin-mcp\nWork focused on foundational improvements for agent memory and tool interaction.\n- Refactored memory handling by introducing an optional `mcpText` field and updating `handleToolResponse` to return a `Memory` object, enabling more robust agent configuration ([#19](https://github.com/elizaos-plugins/plugin-mcp/pull/19)).\n\n### elizaos-plugins/plugin-openai\nDevelopment began on a key feature for real-time interaction.\n- Initiated work to add streaming support, opening a pull request to handle continuous data flows from the OpenAI API ([#21](https://github.com/elizaos-plugins/plugin-openai/pull/21)).\n\n### elizaos-plugins/plugin-anthropic\nWork started on enhancing the plugin's real-time capabilities.\n- A pull request was opened to introduce streaming support, enabling more dynamic and responsive agent communication ([#12](https://github.com/elizaos-plugins/plugin-anthropic/pull/12)).\n\n### elizaos-plugins/plugin-openrouter\nA significant enhancement was proposed to improve responsiveness.\n- Work began on adding streaming support and refining the plugin's focus by removing tools support ([#21](https://github.com/elizaos-plugins/plugin-openrouter/pull/21)).\n\n### elizaos-plugins/plugin-telegram\nA major architectural refactor was initiated to improve integration with the core framework.\n- A pull request was opened to implement a unified messaging API, aiming to standardize communication and enhance modularity ([#22](https://github.com/elizaos-plugins/plugin-telegram/pull/22)).\n\n### elizaos-plugins/plugin-discord\nThe plugin's internal architecture was improved for better maintainability.\n- Work began on refactoring the message handling system to improve its structure and prepare for future enhancements ([#32](https://github.com/elizaos-plugins/plugin-discord/pull/32)).\n\n### elizaos-plugins/plugin-mysql\nActivity focused on user support and documentation clarification.\n- Resolved an issue by clarifying that documentation has been centralized in the `elizaos/docs` repository ([#6122](https://github.com/elizaos-plugins/plugin-mysql/issues/6122)).\n- Provided a helpful tip to users that disabling other plugins may be necessary for successful initial table creation ([#1](https://github.com/elizaos-plugins/plugin-mysql/issues/1))."
},
"github_extracted_data_monthly_stats_text_2025-01": "{\n \"interval\": {\n \"intervalStart\": \"2025-01-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-02-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-01-01 to 2025-02-01, elizaos/eliza had 1039 new PRs (735 merged), 401 new issues, and 694 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs6l7_A4\",\n \"title\": \"Missing Module: '@anush008/tokenizers-linux-arm64-gnu'\",\n \"author\": \"morning3tar\",\n \"number\": 2242,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-13T13:29:04Z\",\n \"closedAt\": \"2025-03-08T01:09:54Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 30\n },\n {\n \"id\": \"I_kwDOMT5cIs6lSxzf\",\n \"title\": \"Error: Could not find wrtc binary on any of the paths when running pnpm start\",\n \"author\": \"arvin-crypto\",\n \"number\": 1965,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-07T15:47:26Z\",\n \"closedAt\": \"2025-03-02T01:55:50Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 27\n },\n {\n \"id\": \"I_kwDOMT5cIs6mwy61\",\n \"title\": \"@elizaos/agent@0.1.9-alpha.1 start: `node --loader ts-node/esm src/index.ts \\\"--isRoot\\\" \\\"--characters=characters/eternalai.character.json\\\"`\",\n \"author\": \"illink7\",\n \"number\": 2530,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-19T20:13:23Z\",\n \"closedAt\": \"2025-03-08T01:17:17Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 22\n },\n {\n \"id\": \"I_kwDOMT5cIs6m5hCt\",\n \"title\": \"Bot is only responding to target users and ignoring all other mentions on twitter\",\n \"author\": \"Xayaan\",\n \"number\": 2563,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-20T18:46:01Z\",\n \"closedAt\": \"2025-03-08T01:17:17Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 21\n },\n {\n \"id\": \"I_kwDOMT5cIs6lwYFX\",\n \"title\": \"\u2009ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL\u2009\",\n \"author\": \"TobiGoldD\",\n \"number\": 2127,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-10T19:14:51Z\",\n \"closedAt\": \"2025-03-02T01:56:01Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 20\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6H-S3t\",\n \"title\": \"chore: dev => main 0.1.9\",\n \"author\": \"odilitime\",\n \"number\": 2361,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-16T09:01:27Z\",\n \"mergedAt\": \"2025-02-01T00:59:40Z\",\n \"additions\": 250702,\n \"deletions\": 16452\n },\n {\n \"id\": \"PR_kwDOMT5cIs6JBWtl\",\n \"title\": \"Add Access Token Management\",\n \"author\": \"elpulpo0\",\n \"number\": 2808,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-26T22:16:38Z\",\n \"mergedAt\": null,\n \"additions\": 224271,\n \"deletions\": 12973\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HcIgk\",\n \"title\": \"chore: Prep v0.1.8 (dev => main)\",\n \"author\": \"odilitime\",\n \"number\": 2171,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-11T23:36:42Z\",\n \"mergedAt\": \"2025-01-12T07:32:53Z\",\n \"additions\": 100844,\n \"deletions\": 46015\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HLoVX\",\n \"title\": \"Fix/resolve conflicts\",\n \"author\": \"yueliao11\",\n \"number\": 2060,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-09T09:58:41Z\",\n \"mergedAt\": null,\n \"additions\": 87145,\n \"deletions\": 43714\n },\n {\n \"id\": \"PR_kwDOMT5cIs6HJPhr\",\n \"title\": \"Development\",\n \"author\": \"juansebsol\",\n \"number\": 2041,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-01-09T01:24:35Z\",\n \"mergedAt\": null,\n \"additions\": 81946,\n \"deletions\": 43391\n }\n ],\n \"codeChanges\": {\n \"additions\": 450243,\n \"deletions\": 138188,\n \"files\": 2487,\n \"commitCount\": 5528\n },\n \"completedItems\": [\n {\n \"title\": \"chore: support more debians distros\",\n \"prNumber\": 1875,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdd more playwright support for various debian distros.\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\\n## Why are we doing this? Any c\"\n },\n {\n \"title\": \"fix: Fix postinstall script\",\n \"prNumber\": 1872,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nFixes develop's install-phase (broken in #1834 )\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\n\\r\\n## Why are we doing this? Any context\"\n },\n {\n \"title\": \"docs: Add DAO donation ask & dev discord\",\n \"prNumber\": 1867,\n \"type\": \"feature\",\n \"body\": \"Self explanatory I hope\"\n },\n {\n \"title\": \"feat: Add Stargaze plugin\",\n \"prNumber\": 1861,\n \"type\": \"feature\",\n \"body\": \"This plugins allows Eliza to get NFT information from the main NFT marketplace in Cosmos (Stargaze). \\r\\n\\r\\n![\\\"image\\\"](\\\"https://github.com/user-attachments/assets/03b9b7fe-85fe-407f-a0ff-dbeeea73f1e1\\\")
\\r\\n![]()
\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1838\\r\\n\\r\\n# Risks\\r\\n\\r\\nlow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR \"\n },\n {\n \"title\": \"test: adding more tests for goals,memory and provider. Fixing generation.test.ts\",\n \"prNumber\": 1840,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/186\\r\\nhttps://github.com/elizaOS/eliza/issues/183\\r\\nhttps://github.\"\n },\n {\n \"title\": \"correct faq docs link in both contribution md files\",\n \"prNumber\": 1839,\n \"type\": \"other\",\n \"body\": \"This pull request includes a small change to the `CONTRIBUTING.md` and `docs/docs/contributing.md` files. The change corrects the link to the FAQ page to point to the correct location.\\r\\n\\r\\n* [`CONTRIBUTING.md`](diffhunk://#diff-eca12c0a30e25\"\n },\n {\n \"title\": \"chore: update bootstrap plugin export\",\n \"prNumber\": 1836,\n \"type\": \"other\",\n \"body\": \"Relates to:\\r\\nPlugin export collisions in character files\\r\\n\\r\\nRisks\\r\\nLow - This is a minor bug fix that ensures proper module exports\\r\\n\\r\\nBackground\\r\\nWhat does this PR do?\\r\\nEnsures the bootstrap plugin has a proper default export at the bottom\"\n },\n {\n \"title\": \"Update README_KOR.md\",\n \"prNumber\": 1835,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\nModified the previous sentence to align with the meaning in Korean.\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1725\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/917\\r\\nhttps://github.com/eli\"\n },\n {\n \"title\": \"Update .env.example\",\n \"prNumber\": 1829,\n \"type\": \"other\",\n \"body\": \"Grok / xAI API Key are the same. Same endpoint. It's confusing to split it into Grok and xAI separately. If someone wants to use Grok, they will enter their xAI API key at the GROK_API_KEY, and it works.\"\n },\n {\n \"title\": \"fix(solana token provider): await cached data\",\n \"prNumber\": 1828,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nExecuting trades\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/1483/\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nMaintains original document structure and layout\\r\\nPreserves all formatting, emojis, and technical terms\\r\\n\"\n },\n {\n \"title\": \"docs: update faq.md\",\n \"prNumber\": 1746,\n \"type\": \"docs\",\n \"body\": \"Removed mentions of some items.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNo issue for this pr\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n#1694\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNo specific issue or ticket.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nFix issue where an agent on twitter tries to use ImageDescriptionService to get the description of a picture from a twitter \"\n },\n {\n \"title\": \"fix: 1634 fix image description service\",\n \"prNumber\": 1667,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n[(https://github.com/elizaOS/eliza/issues/1643 ]\\r\\n)\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nGenerating image\"\n },\n {\n \"title\": \"fix: Update Supabase schema.sql\",\n \"prNumber\": 1660,\n \"type\": \"bugfix\",\n \"body\": \"There is an extra semicolon that causes a syntax error when trying to upload the schema to Supabase.\\r\\n\\r\\n(ie. by using the SQL editor in the GUI, it fails due to this syntax error)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nFixes Supa\"\n },\n {\n \"title\": \"fix: Fix bug in plugin-bootstrap/src/evaluators/facts.ts\",\n \"prNumber\": 1648,\n \"type\": \"bugfix\",\n \"body\": \"{{user1}} should be {{user2}} :\\r\\n\\r\\n-------\\r\\nin factEvaluator, in the examples template,\\r\\n\\r\\n{{user1}} should be {{user2}} instead\\r\\n\\r\\n {\\r\\n user: \\\"{{user1}}\\\",\\r\\n content: { text: \\\"Which city?\"\n },\n {\n \"title\": \"Added Hungarian README\",\n \"prNumber\": 1645,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\nzero \\r\\n\\r\\n## What does this PR do?\\r\\nAdd Hungarian README\\r\\n\\r\\n## Discord username\\r\\nmhoused\\r\\n\"\n },\n {\n \"title\": \"fix: lockfile wasn't updated after dependency + bring viem to root level package.json\",\n \"prNumber\": 1642,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to:\\r\\n\\r\\nTrunk being broken\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This change updates the `pnpm-lock.yaml` file, which could affect dependency resolutions. Potential risks include:\\r\\n\\r\\n- **Dependency Resolution Changes:** Updates might lead to differen\"\n },\n {\n \"title\": \"chore: update viem dependency version in plugin-evm and plugin-goat\",\n \"prNumber\": 1637,\n \"type\": \"other\",\n \"body\": \"# Relates to:\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1635\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nupdate the version of viem to 2.21.58 in plugin-evm and plugin-goat.\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nUpdate\"\n },\n {\n \"title\": \"Add README_AR.md\",\n \"prNumber\": 1634,\n \"type\": \"feature\",\n \"body\": \"Add Arabic language for readme.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nLow - This change affects the Docker container configuration. It may require updates to documentation and\"\n },\n {\n \"title\": \"fix: Support for Non-OpenAI Models in Token Trimming\",\n \"prNumber\": 1605,\n \"type\": \"bugfix\",\n \"body\": \"related: \\r\\nhttps://github.com/elizaOS/eliza/issues/1439\\r\\nhttps://github.com/elizaOS/eliza/issues/1565\\r\\n\\r\\nneed to be tested: https://github.com/elizaOS/eliza/issues/1439#issuecomment-2566405036\"\n },\n {\n \"title\": \"fix: activate web-search plugin in agents/\",\n \"prNumber\": 1577,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n- Issues reported by using of crashes due to this error `Error in trust score provider: Cannot read prope\"\n },\n {\n \"title\": \"feat: use custom conditions for live monorepo types\",\n \"prNumber\": 1365,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nCloses: #1363\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nN/A\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\"\n },\n {\n \"title\": \"Feat/genlayer plugin\",\n \"prNumber\": 975,\n \"type\": \"feature\",\n \"body\": \"This is my first time contributing to this project. I've based my code on the docs, but mostly copying other plugins\\r\\n\\r\\nPlease let me know anything that can be improved :)\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nDTS-error-mismatch-LanguageModelV1-in-ai-sdk-m\"\n },\n {\n \"title\": \"chore(plugin-coinbase): Update tokenContract.ts\",\n \"prNumber\": 2781,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nSometimes an LLM like llama-70b might not return a valid JSON format and this can cause random errors tha\"\n },\n {\n \"title\": \"feat: added Ankr plugin\",\n \"prNumber\": 2773,\n \"type\": \"feature\",\n \"body\": \"# Ankr Plugin for Eliza AI Flow\\r\\n\\r\\n \\r\\nAnkr APIs as Data & Execution Layer:\\r\\n\\r\\nAgents use Ankr\u2019s Multi-Chain RPC to monitor real-time asset prices, liq\"\n },\n {\n \"title\": \"feat: Add Amazon Bedrock as LLM provider\",\n \"prNumber\": 2769,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2753\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow risk: the changed code should only impact a runtime when Amazon Bedrock is used \"\n },\n {\n \"title\": \"feat: create /.turbo/config.json\",\n \"prNumber\": 2768,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nremote cache\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n429 error when running TON plugin to sending a TX.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n#2742\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**: The change introduces a restriction mechanism for the bot's responses, which only applies if `allowedChannelIds` is defined in the configuration. Existing behavi\"\n },\n {\n \"title\": \"feat(plugin-holdstation): add plugin holdstation swap\",\n \"prNumber\": 2741,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo specific issue or ticket is linked to this PR.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nEnv variables, \\r\\n\\r\\n# Risks\\r\\n\\r\\nlow\\r\\n\\r\\n# Background\\r\\n\\r\\nPretty simple update, just adding to `.env.example\"\n },\n {\n \"title\": \"feat: minimal workflow to resolve ephemeral check\",\n \"prNumber\": 2735,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nmerge queue\\r\\n\\r\\n\\r\\n## What does this PR do?\\r\\nCurrent intended path links.\\r\\n## What kind of change is this?\\r\\nDocumentation links.\\r\\n\\r\\n\\r\\n# Relates to\\r\\nAdding a dedicated Sei plugin that streamlines the development experience for creating agents that can in\"\n },\n {\n \"title\": \"client-eliza-home: test config and test coverage\",\n \"prNumber\": 2719,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2718\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNew feature addition.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nLit Protocol Integration for ElizaOS\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nCore Mina blockchain plugin for Eliza OS that provides essential services and actions for token operati\"\n },\n {\n \"title\": \"feat: Hyperbolic-plugin \",\n \"prNumber\": 2701,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n\\r\\n\\r\\n# Hyperbolic Plugin for ElizaOS\\r\\n\\r\\n## Overview\\r\\nThis PR introduces a new plugin for managing GPU instances on the H\"\n },\n {\n \"title\": \"Mostly aesthetic changes, fixed some wonky bullets and numbered lists.\",\n \"prNumber\": 2698,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nDocumentation\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Provide aesthetic tweaks (some wonky bullets and structure)\\r\\n- Add some minor clarifications\\r\\n- Update for newer characters\\r\\n\\r\\n## What kind of change is this?\\r\"\n },\n {\n \"title\": \"chore: fix types syntax issue\",\n \"prNumber\": 2694,\n \"type\": \"bugfix\",\n \"body\": \"fixes missing `};` before simsai profile inteface\"\n },\n {\n \"title\": \"feat(new-plugin): Eliza OmniFlix Plugin\",\n \"prNumber\": 2693,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nOmniFlix Network Integration Plugin for Eliza AI Agent\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2206\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nA plugin that integrates BitMind's API into ElizaOS agents, enabling access to AI services and digital \"\n },\n {\n \"title\": \"feat(new-plugin): suno music generation \",\n \"prNumber\": 2679,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-suno\\r\\n\\r\\nA Suno AI music generation plugin for ElizaOS that enables AI-powered music creation and audio manipulation.\\r\\n\\r\\n## Overview\\r\\n\\r\\nThe Suno plugin integrates Suno AI's powerful music generation capabilities into ElizaO\"\n },\n {\n \"title\": \"feat(new-plugin): eliza samsung smarthings plugin\",\n \"prNumber\": 2678,\n \"type\": \"feature\",\n \"body\": \"# Client-Eliza-Home Functionality Overview\\r\\n\\r\\n## Core Purpose\\r\\nThe client-eliza-home package serves as a bridge between ElizaOS and SmartThings-enabled smart home devices, enabling natural language control and automation of home devices.\\r\\n\\r\"\n },\n {\n \"title\": \"Revert \\\"feat(new-plugin): suno Eliza plugin\\\"\",\n \"prNumber\": 2673,\n \"type\": \"other\",\n \"body\": \"Reverts elizaOS/Eliza#2656\\r\\n\\r\\nPlugin not ready, implements old plugin interface etc\"\n },\n {\n \"title\": \"feat: Implement runProcess function in test library\",\n \"prNumber\": 2672,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nImproving test utilities functionality\\r\\n\\r\\n# Risks\\r\\nLow - This is a test utility function implementation that:\\r\\n- Only affects test code, not production code\\r\\n- Uses standard Node.js APIs (spawn)\\r\\n- Has proper error handling\\r\\n-\"\n },\n {\n \"title\": \"fix debug targets to show elizalogger debug messages\",\n \"prNumber\": 2670,\n \"type\": \"bugfix\",\n \"body\": \"fix for #2667 \\r\\nJust fixes the two debug targets in the package.json to include `DEFAULT_LOG_LEVEL=debug`\"\n },\n {\n \"title\": \"chore(spelling-fixes): docs\",\n \"prNumber\": 2669,\n \"type\": \"bugfix\",\n \"body\": \"Hello\\r\\nI fixed several spelling issue.\\r\\nBr, Elias.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n\\t- Updated README.md with improved grammatical clarity in instruct\"\n },\n {\n \"title\": \"fix(plugin-depin): sentientAI description\",\n \"prNumber\": 2668,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nIssue #2657 \\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow: This change only modifies the GitBook provider\u2019s return format to incl\"\n },\n {\n \"title\": \"feat(new-plugin): suno Eliza plugin\",\n \"prNumber\": 2656,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-suno\\r\\n\\r\\nA Suno AI music generation plugin for ElizaOS that enables AI-powered music creation and audio manipulation.\\r\\n\\r\\n## Overview\\r\\n\\r\\nThe Suno plugin integrates Suno AI's powerful music generation capabilities into ElizaO\"\n },\n {\n \"title\": \"fix: a typo bug in conflux plugin\",\n \"prNumber\": 2654,\n \"type\": \"bugfix\",\n \"body\": \"In handler function of packages/plugin-conflux/src/actions/confiPump.ts:\\r\\n\\r\\n```\\r\\n // Generate content based on template\\r\\n const context = composeContext({\\r\\n state,\\r\\n template: confluxTransferTemplate, \"\n },\n {\n \"title\": \"feat: Add swap & improvements for multiversx-plugin\",\n \"prNumber\": 2651,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nmultiversx-plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nThe PR is not related to any issues.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2620\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n\\t- Updated `.gitignore` to exclude `node-comp\"\n },\n {\n \"title\": \"feat(plugin-holdstation): add plugin holdstation swap\",\n \"prNumber\": 2596,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo specific issue or ticket is linked to this PR.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Relates to\\r\\n\\r\\n## LINK TO ISSUE OR TICKET \\r\\nhttps://github.com/elizaOS/eliza/issues/2561\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2572\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- *\"\n },\n {\n \"title\": \"feat(plugin-farcaster): test config and test coverage\",\n \"prNumber\": 2567,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2566\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added text-to-speech support for Indonesian, Tagalog, and M\"\n },\n {\n \"title\": \"fix:Incorrect boolean parsing for ENABLE_OPEN_AI_COMMUNITY_PLUGIN setting #2559\",\n \"prNumber\": 2560,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2559\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\nThis change only affects the configuration parsing for the ENABLE_OPEN_AI_COMM\"\n },\n {\n \"title\": \"chore(revert): optimize pnpm cache configuration\",\n \"prNumber\": 2556,\n \"type\": \"other\",\n \"body\": \"edit: reverting most pnpm caching attempts\"\n },\n {\n \"title\": \"chore: optimize pnpm cache configuration\",\n \"prNumber\": 2555,\n \"type\": \"other\",\n \"body\": \"Optimizes pnpm cache configuration to improve package reuse during installation.\\n\\nChanges made:\\n- Move pnpm setup before cache configuration\\n- Add architecture-specific cache keys\\n- Include package.json in cache key for better specificity\\n-\"\n },\n {\n \"title\": \"feat: Cosmos Plugin - IBC swap action\",\n \"prNumber\": 2554,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n# Risks\\r\\nLow risk \u2013 this PR adds an action to an existing plugin and does not interfere with the core f\"\n },\n {\n \"title\": \"chore: remove cleanup step from integration tests workflow\",\n \"prNumber\": 2553,\n \"type\": \"refactor\",\n \"body\": \"# Remove cleanup step from integration tests workflow\\n\\nThis PR removes the cleanup step from the integration tests workflow as requested. The cleanup step was running `pnpm clean` which is no longer needed in the workflow.\\n\\n## Changes\\n- Rem\"\n },\n {\n \"title\": \"chore: remove cleanup step from integration tests workflow\",\n \"prNumber\": 2551,\n \"type\": \"refactor\",\n \"body\": \"# Remove cleanup step from integration tests workflow\\n\\nThis PR removes the cleanup step from the integration tests workflow as requested. The cleanup step was running `pnpm clean` which is no longer needed in the workflow.\\n\\n## Changes\\n- Rem\"\n },\n {\n \"title\": \"feat(plugin-devin): implement client-agnostic Devin plugin\",\n \"prNumber\": 2549,\n \"type\": \"feature\",\n \"body\": \"# Devin Plugin PR\\n\\n## Changes\\n- Implemented client-agnostic Devin plugin\\n- Added comprehensive test coverage\\n- Created detailed README documentation\\n- Merged develop branch successfully\\n\\n## Testing\\n- Unit tests passing\\n- API integration ver\"\n },\n {\n \"title\": \"feat: Updated READ.me file with pre-requisites to enable telegram bot\",\n \"prNumber\": 2547,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nTelegram Client\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Renamed internal method for object generation\\n\\t- Improved code formatting and readability\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n\\t- Improved error handling for AgentKit actions initialization\\n\\t- Enhanced code readability with formatting adjustments i\"\n },\n {\n \"title\": \"test configuration and tests for client-lens\",\n \"prNumber\": 2534,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2533\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nhttps://github.com/user-attachments/assets/5bdc0051-b97c-450b-be29-1cc66ea1d1b6\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFollow up on https:/\"\n },\n {\n \"title\": \"feat: add anthropic image provider for vision\",\n \"prNumber\": 2524,\n \"type\": \"feature\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nVision image descriptions\\r\\n\\r\\n# Risks\\r\\n\\r\\nlow: \\r\\nadded an image provider for anthropic which generally defaulted to openai. so the risk is pretty low\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nadd AnthropicImageProvider \"\n },\n {\n \"title\": \"feat: plugin rabbi trader tests\",\n \"prNumber\": 2520,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2519\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFeature/plugin coingecko #1761\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Documentation**\\r\\n\\t- Added a citation section to the R\"\n },\n {\n \"title\": \"docs: add docs/README_JA.md\",\n \"prNumber\": 2515,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Documentation**\\n\\t- Updated Japanese README with comprehensive project details\\n\\t- Added project overview for Eliza\\n\\t- Included setup \"\n },\n {\n \"title\": \"feat: add support for NVIDIA inference for ElizaOS\",\n \"prNumber\": 2512,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n\\r\\n\\r\\n# Add NVIDIA Model Provider Support to ElizaOS\\r\\n\\r\\nThis PR adds support for NVIDIA's AI models through their inference API, expanding ElizaOS's\"\n },\n {\n \"title\": \"test: plugin-tee - adjusting project structure and new tests\",\n \"prNumber\": 2508,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2507\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n- `@elizaos/plugin-agentkit` - default configuration in the agent/src/index.ts file for easier import b\"\n },\n {\n \"title\": \"test: api timeout handling for plugin-binance\",\n \"prNumber\": 2504,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2486\\r\\n\\r\\n\\r\\n\\r\\nThis PR introduces the new **plugin-openai** for text generation functionality using OpenAI's GPT models.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\nNo linked issue.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. \\r\\nThis change introduces a default logger level, which affects logging outputs. Potential risks include unexpected logging behavior if the `DEFAULT_LOG_L\"\n },\n {\n \"title\": \"feat(plugin-new): initia plugin + chore revert to integrationTests from stable release 0.1.7\",\n \"prNumber\": 2448,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nI am developing Initia plugin for elizaOS.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nThis PR is base initia plugin development. I implemented INIT token transfer action for agent.\\r\\n\\r\\n## What kind of ch\"\n },\n {\n \"title\": \"feat: create version.cmd for windows support\",\n \"prNumber\": 2442,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nIssue: Build failures on Windows platform\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Changes are isolated to build scripts and type definitions. No runtime behavior is affected.\\r\\n\\r\\n- Windows build script changes only affect local development on Wi\"\n },\n {\n \"title\": \"feat: add Mind Network plugin\",\n \"prNumber\": 2431,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nNo specific linked issue or ticket, as this is a feature addition for the Mind Network plugin.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow:\\r\\n\\r\\nThe plugin is newly introduced and self-contained, limiting its impact on unrelated parts of the Eliza ecos\"\n },\n {\n \"title\": \"fix: Fix Incorrect Tweet ID Parameter Passed to sendTweet Function\",\n \"prNumber\": 2430,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/1958#issuecomment-2582289612\\r\\n\\r\\nThe issue occurred because the LLM generated a verbose response like:\\r\\n\\\"Received The most interesting and relevant tweet for XXX to reply to is 187954009886315\"\n },\n {\n \"title\": \"feat:add plugin-lightning\",\n \"prNumber\": 2429,\n \"type\": \"feature\",\n \"body\": \"# @elizaos/plugin-lightning\\r\\n\\r\\nThis plugin enables create lightning invoice or payInvoice.\\r\\n\\r\\n## Features\\r\\n\\r\\n- \ud83d\udcb1 Make a new off-chain invoice.\\r\\n- \ud83d\udcca Make an off-chain payment.\\r\\n\\r\\n## Installation\\r\\n\\r\\nAdd the plugin to your Eliza configuratio\"\n },\n {\n \"title\": \"feat: add a way to create/store/restore agents in the filesystem\",\n \"prNumber\": 2389,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nNo Issue.\\r\\n\\r\\n# Risks\\r\\n\\r\\nAs it is using a env variable to enable/disable the feature, there are no risks involved.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nIf USE_CHARACTER_STORAGE is enabled in the .env:\\r\\n\\r\\nIt stores a\"\n },\n {\n \"title\": \"feat: plugin for OriginTrail Decentralized Knowledge Graph\",\n \"prNumber\": 2380,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A - New plugin contribution\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow:\\r\\n- Requires you to explicitly provide your private key in the environment variable before it does anything with your funds\\r\\n- Creation of OriginTrail Knowledge Assets spends y\"\n },\n {\n \"title\": \"feat: add adapter-qdrant\",\n \"prNumber\": 2322,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdd qdrant adapter into Eliza system.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFixes [#2272](https://github.com/elizaOS/eliza/issues/2272)\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nAI Agent Dev School Video #2: https://www.youtube.com/watch?v=XenGeAcPAQo&t=3383s \\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"chore: updated .gitignore + removed build files\",\n \"prNumber\": 3117,\n \"type\": \"other\",\n \"body\": \"chore: updated .gitignore + removed build files\"\n },\n {\n \"title\": \"fix: auto-scrolling issue in client\",\n \"prNumber\": 3115,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/1977\\r\\n\\r\\nNoticed that when chatting with a character on the client, the conversation doesn\u2019t automatically scroll to the bottom after submitting a message and receiving a response. This PR fix\"\n },\n {\n \"title\": \"fix: fixing the error parsing json when an array is a value in a JSON\u2026\",\n \"prNumber\": 3113,\n \"type\": \"bugfix\",\n \"body\": \"\u2026 object\\r\\n\\r\\n# Relates to\\r\\n\\r\\nHaven't created a ticket, but it seems to be related to recent changes in the `normalizeJsonString` function.\\r\\n\\r\\nWhen using the Slack client, JSON like:\\r\\n\\r\\n```json\\r\\n{\\r\\n \\\"objective\\\": \\\"The user wants to summarize \"\n },\n {\n \"title\": \"fix: docker build command by skipping eslint files\",\n \"prNumber\": 3110,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\nRunning docker build fails because eslint config have been removed\\r\\n![Screenshot 2025-01-31 at 14 13 58](https://github.c\"\n },\n {\n \"title\": \"fix: plugin-apro\",\n \"prNumber\": 3106,\n \"type\": \"bugfix\",\n \"body\": \"Investigated and added the peoper ether to the configuration it was missing and fixed all the code.\"\n },\n {\n \"title\": \"fix: plugin-aptos\",\n \"prNumber\": 3104,\n \"type\": \"bugfix\",\n \"body\": \"Fixed all the issues and added Biome.\"\n },\n {\n \"title\": \"docs: Add \\\"What Did You Get Done This Week? 11\\\" notes\",\n \"prNumber\": 3103,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nDocumentation updates for community streams\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding a new community stream summary.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds the summary document for \\\"What Did You \"\n },\n {\n \"title\": \"fix: plugin-arthera-biome\",\n \"prNumber\": 3102,\n \"type\": \"bugfix\",\n \"body\": \"fixed al issues \"\n },\n {\n \"title\": \"fix: plugin-asterai\",\n \"prNumber\": 3101,\n \"type\": \"bugfix\",\n \"body\": \"Added only the Biome. Code was good.\"\n },\n {\n \"title\": \"fix: plugin-autonome-v1\",\n \"prNumber\": 3098,\n \"type\": \"bugfix\",\n \"body\": \"Fixed all issues.\"\n },\n {\n \"title\": \"fix: fixed build error in plugin-email-automation \",\n \"prNumber\": 3097,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3071\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3067\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/3062\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nNavigate links to specified resources\\r\\n## What kind of change is this?\\r\\nDocum\"\n },\n {\n \"title\": \"fix: OpenAI embedding issue\",\n \"prNumber\": 3003,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIssue: OpenAI embeddings error when running character without OpenAI API key configured in .env file. \\r\"\n },\n {\n \"title\": \"feat (chore): plugin avalanche test config and coverage\",\n \"prNumber\": 2999,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2998\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2996\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2991\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2981\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2979\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNo specific issue or ticket. This PR updates the README with a French\"\n },\n {\n \"title\": \"fix: handle whitespace in quote conversion\",\n \"prNumber\": 2961,\n \"type\": \"bugfix\",\n \"body\": \"I noticed that array parsing sometimes fails because, in this PR (https://github.com/elizaOS/eliza/pull/2802/files), the regex matches 'something' only if it is immediately followed by a comma, closing brace, or closing bracket, without any\"\n },\n {\n \"title\": \"fix: plugin-letzai\",\n \"prNumber\": 2960,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors.\"\n },\n {\n \"title\": \"fix: plugin-lightning\",\n \"prNumber\": 2959,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors and also the missing use of Zod.\"\n },\n {\n \"title\": \"fix: plugin-lit\",\n \"prNumber\": 2957,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and leaved only 3 any that we can change only afer testing. \"\n },\n {\n \"title\": \"fix: plugin-massa\",\n \"prNumber\": 2955,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors.\"\n },\n {\n \"title\": \"fix-plugin-mina\",\n \"prNumber\": 2954,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors \"\n },\n {\n \"title\": \"fix: mind-network\",\n \"prNumber\": 2953,\n \"type\": \"bugfix\",\n \"body\": \"Added only missing logging.\"\n },\n {\n \"title\": \"fix: plugin-moralis\",\n \"prNumber\": 2952,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the issues.\"\n },\n {\n \"title\": \"fix: {{maxTweetLength}} doesn't work in tweet post template \",\n \"prNumber\": 2951,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/2927\"\n },\n {\n \"title\": \"fix: remove unnecessary @ts-expect-error directive in chat component\",\n \"prNumber\": 2950,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\nTypeScript error TS2578 in chat component\\r\\n\\r\\n# Risks\\r\\nLow - This is a simple removal of an unnecessary TypeScript directive that was causing an error.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nRemoves an unnecessary @ts-exp\"\n },\n {\n \"title\": \"fix: add missing plugins in package.json\",\n \"prNumber\": 2947,\n \"type\": \"feature\",\n \"body\": \"There were several missing plugins in package.json, which prevented the app from starting. I\u2019ve added them back. It seems this issue was caused by a merge conflict in this: https://github.com/elizaOS/eliza/commit/b3bc2547285663abbf4c3852f38\"\n },\n {\n \"title\": \"fix: remove dead code\",\n \"prNumber\": 2945,\n \"type\": \"bugfix\",\n \"body\": \"removed dead code (comments)\"\n },\n {\n \"title\": \"fix: plugin-movement\",\n \"prNumber\": 2943,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all errors \"\n },\n {\n \"title\": \"fix: plugin-multiversx\",\n \"prNumber\": 2942,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors present. \"\n },\n {\n \"title\": \"fix: plugin-near\",\n \"prNumber\": 2941,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and typing.\"\n },\n {\n \"title\": \"fix: plugin-news\",\n \"prNumber\": 2940,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the type and literals.\"\n },\n {\n \"title\": \"fix: building error\",\n \"prNumber\": 2938,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: plugin-nft-collection\",\n \"prNumber\": 2937,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed all the errors and most if not all the typing.\"\n },\n {\n \"title\": \"fix: plugin-nft-generation\",\n \"prNumber\": 2934,\n \"type\": \"bugfix\",\n \"body\": \"## Fixed partially the typing and the reassigmnet logic. To fix it all we need to redo partially the code. I leave for a nother PR.\"\n },\n {\n \"title\": \"feat: add public access to packages.\",\n \"prNumber\": 2933,\n \"type\": \"feature\",\n \"body\": \"This ensures all packages that are not marked private are properly scoped and can be published to npm registry.\"\n },\n {\n \"title\": \"fix template typos\",\n \"prNumber\": 2932,\n \"type\": \"bugfix\",\n \"body\": \"Minor fixes as first contribution, noticed while diving source code\"\n },\n {\n \"title\": \"chore: inconsistent folder naming conventipn\",\n \"prNumber\": 2931,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: invalid npm package naming convention\",\n \"prNumber\": 2930,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: missing version prop in package.json\",\n \"prNumber\": 2929,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"ci: changes to allow package scoping to public\",\n \"prNumber\": 2928,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"Update lpmanager.character.json\",\n \"prNumber\": 2921,\n \"type\": \"other\",\n \"body\": \"The subject of the sentence is \\\"the center price\\\", which is singular, so the correct verb form is \\\"is\\\" instead of \\\"are\\\".\"\n },\n {\n \"title\": \"feat: new model provider for LM Studio\",\n \"prNumber\": 2913,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdd LM Studio model provider\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2859\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2853\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2849\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo issue yet; can file an issue if you'd like?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"fix: plugin-tts \",\n \"prNumber\": 2829,\n \"type\": \"bugfix\",\n \"body\": \"Fixed non-critical issues highlighted by strict biome linting:\\n- Updated imports to use `node:` prefix\\n- Changed bracket notation to dot notation for object access\\n- Added explicit type for `target_voice`\\n- Simplified environment variable a\"\n },\n {\n \"title\": \"feat: add new readmes, move some others for consistency\",\n \"prNumber\": 2828,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, its documentation \\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nUpdates the d\"\n },\n {\n \"title\": \"fix: plugin-zksync-era multiple errors and issues as documented\",\n \"prNumber\": 2819,\n \"type\": \"bugfix\",\n \"body\": \"# Fix plugin-zksync-era\\r\\n\\r\\n- Replace non-null assertion with fallback in useGetAccount\\r\\n- Avoid parameter reassignment in transferAction handler\\r\\n- Add explicit typing for hash variable\\r\\n- Convert string concatenations to template literals\\r\"\n },\n {\n \"title\": \"fix: nvidia nim environment\",\n \"prNumber\": 2817,\n \"type\": \"bugfix\",\n \"body\": \"# Fix: NVIDIA NIM Plugin Environment Variables Typo\\r\\n\\r\\n## Changes\\r\\n- Fixed typo in environment variable names in `actionGetTopic.ts`:\\r\\n - `NVIDIA_OFFTOPIC_SYSTEM`\\r\\n - `NVIDIA_OFFTOPIC_USER`\\r\\n\\r\\n## Technical Details\\r\\n- Modified: `packages/p\"\n },\n {\n \"title\": \"fix: akash splash \",\n \"prNumber\": 2816,\n \"type\": \"bugfix\",\n \"body\": \"# Akash Plugin UI Enhancement\\r\\n\\r\\n## Changes\\r\\n- Updated splash screen design for Akash plugin\\r\\n- Enhanced visual presentation of the interface\\r\\n- Improved user experience with better layout\\r\\n\\r\\n## Technical Details\\r\\n- Modified: `packages/plug\"\n },\n {\n \"title\": \"docs: Update client-telegram README.md\",\n \"prNumber\": 2814,\n \"type\": \"docs\",\n \"body\": \"Just corrected some formatting issues, and added details about configuration of advanced features via character.json files.\\r\\n\\r\\n\\r\\n\\r\\n# R\"\n },\n {\n \"title\": \"feat: Add Access Token Management to MultiversX Plugin\",\n \"prNumber\": 2810,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nmultiversx-plugin\\r\\n\\r\\n# Risks\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Add the possibility to limit token management to one user or all user\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements\\r\\n\\r\\n# Documentation change\"\n },\n {\n \"title\": \"test: plugin-0x test configuration and coverage\",\n \"prNumber\": 2807,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2806\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2804\\r\\n\\r\\nNo specific issue or ticket referenced.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\nLow \u2014 this PR primarily refines the parsing function\"\n },\n {\n \"title\": \"feat(new-plugin): create gelato plugin relay\",\n \"prNumber\": 2799,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\nNo linked issue. This PR introduces a Gelato Relay plugin with support for both `sponsoredCall` and `sponsoredCallERC2771` functionalities.\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Dependency\\r\\n\u2757 \u2757 **Must be merged with : https://github.com/elizaOS/agent-twitter-client/pull/57**\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n\"\n },\n {\n \"title\": \"chore(update-plugin-initialization): btcfun & trikon plugin\",\n \"prNumber\": 2643,\n \"type\": \"other\",\n \"body\": \"# btcfun Plugin for Eliza\\r\\n\\r\\n## Description\\r\\nBTC.Fun enables users to effortlessly launch and trade Runes/BRC20 tokens on the Bitcoin network in a permissionless environment. Through the platform, anyone can create their own Runes/BRC20 tok\"\n },\n {\n \"title\": \"feat(client-alexa): Basic Alexa skill notification\",\n \"prNumber\": 2564,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nMedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Integrate communication with \"\n },\n {\n \"title\": \"docs: Add \\\"What Did You Get Done This Week? #10\\\" notes\",\n \"prNumber\": 2558,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nDocumentation updates for community streams\\r\\n\\r\\n# Risks\\r\\nLow - This is a documentation-only change adding a new community stream summary.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds the summary and transcript for \\\"What Di\"\n },\n {\n \"title\": \"feat(new-plugin): quick intel plugin for token security analysis\",\n \"prNumber\": 2391,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - This plugin is isolated and:\\r\\n\\r\\n- Uses established API endpoints\\r\\n- Has proper error handling\\r\\n- Follows existing plugin patterns\\r\\n- No database changes required\\r\\n- No deployment risks\\r\\n\\r\\n# Background\\r\\n\"\n },\n {\n \"title\": \"feat(new-plugin): 0x plugin to swap on evms\",\n \"prNumber\": 2329,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2230\\r\\nCreated a plugin for 0x protocol, a feature request from \"\n },\n {\n \"title\": \"feat: custom s3 endpoint url for 'plugin-node'\",\n \"prNumber\": 2176,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2174, and builds upon https://github.com/elizaOS/eliza/pull/2379\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. This affects only the `plugin-node`, and it changes logic in a way that is backward compatible. \\r\\n\\r\\n\"\n },\n {\n \"title\": \"feat: Separate Knowledge system + Multi-Agent RAG Optimization\",\n \"prNumber\": 1620,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow Risk, as the new RAG system is completely separate, and must be enabled by the user to use as of now.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nImprovements (misc. ch\"\n },\n {\n \"title\": \"feat(new-plugin): deva client integration\",\n \"prNumber\": 1238,\n \"type\": \"feature\",\n \"body\": \"# Pull Request: Integrate Deva into Eliza\\r\\n\\r\\n## Relates to\\r\\n\\r\\nThis PR adds a new [Deva](https://www.deva.me/) client integration for the Eliza AI agent, enabling posting and scheduling posts to the [Deva](https://www.deva.me/) feed.\\r\\n\\r\\n## R\"\n },\n {\n \"title\": \"feat: Add Extra Multimedia Support for Telegram Client \",\n \"prNumber\": 2510,\n \"type\": \"feature\",\n \"body\": \"This PR is based on https://github.com/elizaOS/eliza/pull/1837\\r\\nI\u2019ve remade this PR because maintainer edit access was not enabled, making it difficult to make necessary changes directly.\\n\\n\\n\\n## Summary by Cod\"\n },\n {\n \"title\": \"chore: update createToken.ts\",\n \"prNumber\": 2493,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\ncreat -> create\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n\\r\\nImprovements (misc. changes to existing features)\\r\\n\\r\"\n },\n {\n \"title\": \"chore: corrected the link to the banner\",\n \"prNumber\": 2491,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2481\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n[Issue #2252](https://github.com/elizaOS/eliza/issues/2252)\\r\\n[Expands on #2328](https://github.com/eliz\"\n },\n {\n \"title\": \"fix: linting errors\",\n \"prNumber\": 2474,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: add openai env to smokeTests\",\n \"prNumber\": 2472,\n \"type\": \"feature\",\n \"body\": \"Reverts elizaOS/eliza#2459\"\n },\n {\n \"title\": \"test: adding test configuration and tests for redis adapter\",\n \"prNumber\": 2470,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2469\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2467\\r\\n\\r\\nThis pull request relates to resolving the issue where `animated.div` from `@react-spring/web` was not accepting the `children` prop in TypeScript, causing type errors.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**\"\n },\n {\n \"title\": \"chore: set openai as default character's provider\",\n \"prNumber\": 2460,\n \"type\": \"other\",\n \"body\": \"chore: set openai as default character's provider\"\n },\n {\n \"title\": \"revert: \\\"refactor: dockerize smoke tests\\\"\",\n \"prNumber\": 2459,\n \"type\": \"refactor\",\n \"body\": \"Reverts elizaOS/eliza#2420\"\n },\n {\n \"title\": \"feat: Add features to the Solana Agent Kit \",\n \"prNumber\": 2458,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1619\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2453\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2405 \\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\"\n },\n {\n \"title\": \"fix: conditional use of useQuery in AgentRoute component to prevent runtime errors.\",\n \"prNumber\": 2413,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nGeneral improvement; no specific issue linked.\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2406\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2403\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFix the Remote Attestation Action to prevent hallucination in Twitter and Discord clients when publishing\"\n },\n {\n \"title\": \"feat: add safe_mode (& cfg_scale) for venice image generation\",\n \"prNumber\": 2354,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nVery low\\r\\n\\r\\n# Background\\r\\n\\r\\nVenice has uncensored image generation which may create issues for agents running on platforms with strict terms of service related to nudity or graphic content.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nVenice r\"\n },\n {\n \"title\": \"fix: align base url in client if api runs on a different port\",\n \"prNumber\": 2353,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2344\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAction: DESCRIBE_IMAGE\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\nLow risks, the only risk is that someone hooks up this plugin with their Solana wallet and because it is so easy to use spends more tokens than\"\n },\n {\n \"title\": \"feat: Telegram autonomous agent enhancement\",\n \"prNumber\": 2338,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\n[PR 2335](https://github.com/elizaOS/eliza/pull/2335)\\r\\n# Risks\\r\\n\\r\\nLow risk, minimal changes to Discord client\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change wh\"\n },\n {\n \"title\": \"fix: formatting in Browser section of README.md\",\n \"prNumber\": 2336,\n \"type\": \"bugfix\",\n \"body\": \"Hey all! I saw strange formatting in the README.md and figured it was an extra three backticks ```\\r\\n\\r\\nSure enough, deleting those made the section render as intended. I also reworded one of the sentences that had three \\\"and\\\"s to make it a l\"\n },\n {\n \"title\": \"feat: Discord autonomous agent enhancement\",\n \"prNumber\": 2335,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow risk, minimal changes to Discord client\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change which adds functionality)\\r\\n\\r\\nThis feature add the \"\n },\n {\n \"title\": \"Update README_TR.md\",\n \"prNumber\": 2334,\n \"type\": \"other\",\n \"body\": \"Added WSL 2 link\"\n },\n {\n \"title\": \"fix: SwapAction in evm-plugin\",\n \"prNumber\": 2332,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nfix bugs & improvements in plugin-evm\\r\\n\\r\\n# Risks\\r\\n\\r\\nMedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\"\n },\n {\n \"title\": \"feat: Enable Multiple remote character urls\",\n \"prNumber\": 2328,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n[Issue #2252](https://github.com/elizaOS/eliza/issues/2252)\\r\\n[Expands on PR #2281](https://github.com/e\"\n },\n {\n \"title\": \"feat: dexscreener trending\",\n \"prNumber\": 2325,\n \"type\": \"feature\",\n \"body\": \"Adding code from https://github.com/elizaOS/eliza/pull/1584\\r\\nto DS plugin for fetching trending, boosted and latest tokens added to dexscreener\"\n },\n {\n \"title\": \"fix: correct OPENROUTER_API_KEY env in config\",\n \"prNumber\": 2324,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\n# Risks\\r\\nLOW\\r\\n\\r\\n# Background\\r\\nset private runtime envs for each character, eg: \\r\\n```\\r\\ncharacter.settings.secrets = {...privateEnvs};\\r\\n```\\r\\nuse openrouter as ModelProvider and set OPENROUTER_API_KEY as agent runtime secrects\"\n },\n {\n \"title\": \"feat: Onchain Agent Transformer - transform any Eliza agents into unstoppable Solidity smart contracts deployed on 10+ blockchains\",\n \"prNumber\": 2319,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nTransform any Eliza agents into unstoppable Solidity smart contracts deployed on 10+ blockchains\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nMore flexible than with env and support for\"\n },\n {\n \"title\": \"docs: Update README.md\",\n \"prNumber\": 2309,\n \"type\": \"docs\",\n \"body\": \"Remove duplicate in the readme\"\n },\n {\n \"title\": \"fix: farcaster memory\",\n \"prNumber\": 2307,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nRe-implements #2039 and updates Remote Attestations to have more content to ensure older generated RA Quo\"\n },\n {\n \"title\": \"fix: Update package.json of core package\",\n \"prNumber\": 2301,\n \"type\": \"bugfix\",\n \"body\": \"these packages are being used in prod build and generate errors if you decide to just use this package in a project.\\r\\n\\r\\n# Background\\r\\n\\r\\nThese packages are being used under src/ folder and needs to be part of the dependencies not dev depende\"\n },\n {\n \"title\": \"feat: coinbase agentkit plugin for eliza\",\n \"prNumber\": 2298,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAdding AgentKit EVM support to Eliza\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#2223 \\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2164\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2212\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nGives eliza agents their own abstract global wallets so they can use Abstract similar to how real users\"\n },\n {\n \"title\": \"docs: Add Greek translation for README_GR\",\n \"prNumber\": 2199,\n \"type\": \"feature\",\n \"body\": \"Relates to\\r\\nThis pull request relates to issue https://github.com/elizaOS/eliza/issues/2197.\\r\\n\\r\\nRisks\\r\\nLow: This PR only adds a Greek translation for the README file and updates the main README to include a link to the new translation. No f\"\n },\n {\n \"title\": \"fix(plugin-twitter): change prompt to ensure it returns json\",\n \"prNumber\": 2196,\n \"type\": \"bugfix\",\n \"body\": \"per masterdai https://discord.com/channels/1253563208833433701/1300025221834739744/1327947002943770705\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nPrompt improvement\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nBug fixes (non-\"\n },\n {\n \"title\": \"refactor: websearch into a service\",\n \"prNumber\": 2195,\n \"type\": \"refactor\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\n\\r\\nRemove Tavily from core https://github.com/elizaOS/eliza/issues/2123\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. While it touche\"\n },\n {\n \"title\": \"chore: 0.1.8.build.1 (dev => main)\",\n \"prNumber\": 2194,\n \"type\": \"other\",\n \"body\": \"Fixes docker build\\r\\nUnbotches version for npm publish/release\\r\\n\\r\\nChangelog\\r\\n- #2184\\r\\n- #2182\\r\\n- #2187\\r\\n- #2193\"\n },\n {\n \"title\": \"chore: Prep 0.1.8.build.1\",\n \"prNumber\": 2193,\n \"type\": \"other\",\n \"body\": \"- Bump version to 0.1.8.build.1\"\n },\n {\n \"title\": \"fix postgres adapter migration extension creation which already exists at this point\",\n \"prNumber\": 2188,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/2067\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nSuper low-risk, text mutation/scrub prior to sending Tweet.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does \"\n },\n {\n \"title\": \"feat: \ud83c\udf88 perf(vscode): Set file nesting for md and DockerFile\",\n \"prNumber\": 2177,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNone\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2172\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/pull/1620\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nNo issue\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow.\\r\\n\\r\\nThis is a brand new feature.\\r\\nIt is only effective when using dependency\"\n },\n {\n \"title\": \"refactor: farcaster client env configuration \",\n \"prNumber\": 2087,\n \"type\": \"refactor\",\n \"body\": \"# Relates to\\r\\nRefactoring Farcaster Client Implementation\\r\\n\\r\\n# Risks\\r\\nLow - This is primarily a refactoring change that improves code organization and configuration management without changing core functionality.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What \"\n },\n {\n \"title\": \"feat: atoma provider\",\n \"prNumber\": 2082,\n \"type\": \"feature\",\n \"body\": \"# Background\\r\\n\\r\\nAtoma is a decentralized private and verifiable AI execution network. It provides the infrastructure for developers and enterprises to use open-source AI models and build AI applications with full privacy.\\r\\n\\r\\n## What does th\"\n },\n {\n \"title\": \"feat: add external router path and new tweet generation\",\n \"prNumber\": 2081,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\nN/A - this is an issue and will be described below in the Backgroun\"\n },\n {\n \"title\": \"feat: full overhaul of client\",\n \"prNumber\": 2038,\n \"type\": \"feature\",\n \"body\": \"This PR replaces the entire `client` app with a refreshed look. From this base it's very easy to add additional features going forward.\\r\\n\\r\\n\\r\\n\\r\\n## Featu\"\n },\n {\n \"title\": \"chore(ci): add pnpm lockfile consistency check workflow\",\n \"prNumber\": 2015,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\nN/A - Direct improvement to CI process\\r\\n\\r\\n# Risks\\r\\nLow - This is a new CI workflow that doesn't affect the production code.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nCurrently, on the main branch, `pnpm install` fails to ru\"\n },\n {\n \"title\": \"feat: Adding plugin for B\u00b2 Network\",\n \"prNumber\": 2010,\n \"type\": \"feature\",\n \"body\": \"B\u00b2 Network is a Bitcoin Layer2 network. Add this plugin to integrate with Eliza so that users can interact with B\u00b2 Network through Eliza agent.\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAdd B\u00b2 Network plugin into Eliza system.\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\nMain implementa\"\n },\n {\n \"title\": \"feat: add instagram client\",\n \"prNumber\": 1964,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow, is a new client, does't have any impact on old code.\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nImplements a new Instagram client for ElizaOS that:\\r\\n\\r\\n1. Handles Instagram authentication and session management\\r\\n2. Provides media posting\"\n },\n {\n \"title\": \"chore(plugin-solana): replace console with elizaLogger\",\n \"prNumber\": 1888,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nInteracting with Injective chain\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nAdd cross-chain swaps to ElizaOS through Squid Router\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does t\"\n },\n {\n \"title\": \"feat: Add support for VoyageAI embeddings API\",\n \"prNumber\": 1442,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nA bug or change in behavior of embedding provider selection could cause an unexpected switch. This could cause pre-existing embeddings and new embeddings to be incompatible.\\r\\n\\r\\nI removed `isOllama` flag from the config. It seemed\"\n },\n {\n \"title\": \"feat: add birdeye plugin\",\n \"prNumber\": 1417,\n \"type\": \"feature\",\n \"body\": \"# Overview\\r\\n\\r\\n- This PR introduces a new plugin for the data provider [Birdeye](https://www.birdeye.so/). \\r\\n- The plugin includes API endpoints and related types for all [Birdeye API](https://docs.birdeye.so/) endpoints even though not all \"\n },\n {\n \"title\": \"feat: improve GOAT integration by allowing tool calling when using generateText\",\n \"prNumber\": 1403,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\nhttps://x.com/sunosuporno/status/1870967395780792741\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nTwo main things:\\r\\n1. Update `generateText` API to be able to pass through tool options to leverage the mo\"\n },\n {\n \"title\": \"fix: postgres-adapter - remove nonsensical schema check\",\n \"prNumber\": 1377,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\nCloses: https://github.com/elizaOS/eliza/issues/1376\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nN/A (No specific issue or ticket linked)\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n- This change only adds support for BNB cha\"\n },\n {\n \"title\": \"feat: Add devcontainer\",\n \"prNumber\": 1807,\n \"type\": \"feature\",\n \"body\": \"Hello from Hunter ($drpxbt) Team\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, no code is changed.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nEnables to open workspace in devcontainer (docker with vs code)\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nIm\"\n },\n {\n \"title\": \"fix: fix the chat stuck in infinite loop\",\n \"prNumber\": 1755,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\nthe chat stuck in infinite loop when using model_local https://github.com/elizaOS/eliza/issues/1213\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nhttps://github.com/elizaOS/eliza/issues/2169\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\"\n },\n {\n \"title\": \"add github to client enumerations\",\n \"prNumber\": 2157,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdding the github to the `Clients` enumeration due to error when trying to run. `Invalid enum value'\\r\\n\\r\\n<\"\n },\n {\n \"title\": \"fix: correct SUI/USD price calculation\",\n \"prNumber\": 2150,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to Eliza client-twitter/plugin/SttTtsSpacesPlugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAI function enhancement, similar with #1446, @odilitime \\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nbug fix typo\\r\\n\\r\\n\\r\\n\\r\\n# \"\n },\n {\n \"title\": \"feat: Lens Network Plugin\",\n \"prNumber\": 2101,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nN/A (No specific issue or ticket linked)\\r\\n\\r\\n---\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow \\r\\n- This change only adds support for the Lens Testnet network to enable transfers of Grass tokens between users. \\r\\n- Other features and functionalities of \"\n },\n {\n \"title\": \"Fix: Supabase updates\",\n \"prNumber\": 2100,\n \"type\": \"bugfix\",\n \"body\": \"Fixes an issue where missing rooms in the Supabase database caused errors when fetching them using `.single()`. Additionally, ensures that the database seed values contain valid timestamps and required non-null fields. Also fixes an issue w\"\n },\n {\n \"title\": \"Add gemini to image vision\",\n \"prNumber\": 2099,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow - This PR adds a new embedding model provider (Heurist) with BAAI/bge-large-en-v1.5 as the default model. Changes are additive and follow existing patterns.\\r\\n\\r\\n# Backgro\"\n },\n {\n \"title\": \"fix: Update clients.md to fix package name\",\n \"prNumber\": 2091,\n \"type\": \"bugfix\",\n \"body\": \"@eliza needs to be @elizaos in order for successful installation and imports\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nThere is no risk because only documentation is added.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n\\r\\n# Relates to\\r\\n- The Korean README file (`README_KOR.md`).\\r\\n\\r\\n# R\"\n },\n {\n \"title\": \"Update README_CN to match latest English README\",\n \"prNumber\": 2069,\n \"type\": \"tests\",\n \"body\": \"# Relates to\\r\\n\\r\\n- The Chinese README file (`README_CN.md`).\\r\\n\\r\\n# Risks\\r\\n\\r\\n- **Low**: This PR only updates documentation and does not affect code or functionality.\\r\\n- **Affected**: The Chinese README file (`README_CN.md`).\\r\\n\\r\\n# Background\\r\\n\\r\"\n },\n {\n \"title\": \"feat: pro api support, trending coins api\",\n \"prNumber\": 2068,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n- #1761\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low** - Adding new functionality and API support with proper error handling\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n1. Adds support for CoinGecko Pro API\\r\\n\\r\\n - Configurable through environment \"\n },\n {\n \"title\": \"fix: Bugfix in LetzAI Plugin -> missing named export and Plugin-type\",\n \"prNumber\": 2062,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n0002--feat-letzai-plugin tiny bugfix in the export of the module. Plugin was already merged to dev but \"\n },\n {\n \"title\": \"Galadriel docs and .env.example update\",\n \"prNumber\": 2061,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/pull/2011\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - no functional changes\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdd a tutorial on how to use the Galadriel provider.\\r\\nAlso update the `.env.example` to put \"\n },\n {\n \"title\": \"revert: #2048\",\n \"prNumber\": 2059,\n \"type\": \"other\",\n \"body\": \"Reverts elizaOS/Eliza#2048\\r\\n\\r\\n\\r\\nuntil further review\"\n },\n {\n \"title\": \"Fix: case-sensitive column reference in knowledge table CHECK constraint\",\n \"prNumber\": 2058,\n \"type\": \"bugfix\",\n \"body\": \"Resolves a SQL error (42703: column \\\"isshared\\\" does not exist) in the knowledge table's CHECK constraint. The issue was caused by an incorrect column reference due to PostgreSQL\u2019s case sensitivity when handling column names inside constrain\"\n },\n {\n \"title\": \"feat: solana transaction more lenient\",\n \"prNumber\": 2053,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFixes the Key Derive functionality, by using path for reliable key derivation. Subject is documented and \"\n },\n {\n \"title\": \"chore: add conditionals for supabase to agent directory\",\n \"prNumber\": 2032,\n \"type\": \"feature\",\n \"body\": \"Added Condional for Supabase to the initializeDatabase function to allow for ease of use for Supabase as well as keeping the postgres and sqlite functionality. In conjunction with https://github.com/elizaOS/eliza/pull/2031\\r\\n\\r\\n# Relates to\\r\"\n },\n {\n \"title\": \"Update .env.example\",\n \"prNumber\": 2031,\n \"type\": \"other\",\n \"body\": \"Added Supabase variables. In conjunction with https://github.com/elizaOS/eliza/pull/2032\\r\\n\\r\\n# Relates to\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do? \\r\\nAdds Supabase variables to the .env\\r\\n\\r\\n## What kind of change is t\"\n },\n {\n \"title\": \"fix: include schema.sql and seed.sql in package files\",\n \"prNumber\": 2030,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nFixes #2009 - @elizaos/adapter-postgres package does not bundle together schema.sql\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Adding missing SQL files to package bundling. Only affects package distribution, not functionality.\\r\\n\\r\\n# Background\\r\\n\\r\\n\"\n },\n {\n \"title\": \"Fix: fix starknet plugin by replacing walletProvider with portfolio provider\",\n \"prNumber\": 2029,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/2028\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates\\r\\nto readme.md rus\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nEliza currently supports various AI providers but lacks native integration with **nineteen.ai**, which \"\n },\n {\n \"title\": \"fix: letzAi build issues\",\n \"prNumber\": 2021,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nmultiversx-plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n- Minor bug fixed.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nAuto Client not working.\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n-Add client-telegram README.me file\\r\\n-Update comments to \"\n },\n {\n \"title\": \"feat: implement getKnowledge, searchKnowledge, createKnowledge, removeKnowledge and clearKnowledge methods\",\n \"prNumber\": 2005,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"Update plugins.md -- Allora README Fix\",\n \"prNumber\": 2003,\n \"type\": \"bugfix\",\n \"body\": \"- Fixed a comment-uncomment typo at the end of the Allora Documentation.\\r\\n- Added a link to more comprehensive documentation + examples at the bottom\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nNone\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n* None, just a chore\\r\\n\\r\\n# Risks\\r\\n\\r\\n* None\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n* Moves README\"\n },\n {\n \"title\": \"test: changing test structure for core package. Fixing failling outdated tests\",\n \"prNumber\": 1989,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1988\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow. Manually tested successfully. Purely additive in nature.\\r\\n\\r\\n# Background\\r\\nThe EVM plugin only had mainnet\"\n },\n {\n \"title\": \"chore: add debug logging for context\",\n \"prNumber\": 1980,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\nWhile playing with Eliza and using multiple clients, I noticed that the contexts are often assembled in a mess with many bugs. I want to solve these in my future pull requests, but first, I want to add Eliza, the simple modi\"\n },\n {\n \"title\": \"test: adding tests for twitter plugin\",\n \"prNumber\": 1976,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nChanging project structure, adding tests for twitter plugin in __tests__ directory.\\r\\n# Risks\\r\\nLow: adding\"\n },\n {\n \"title\": \"chore: Cleaner logs on agent startup\",\n \"prNumber\": 1973,\n \"type\": \"refactor\",\n \"body\": \"# Risks\\r\\n\\r\\nLow. Cleans up the logs shown during agent startup.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nCleaning up the logs so that instead of:\\r\\n\\r\\n```\\r\\nSUCCESS\\r\\nSUCCESS\\r\\nCreating runtime for character Eliza\\r\\n```\\r\\n\\r\\nit shows\\r\\n\\r\\n```\\r\\n[\"\n },\n {\n \"title\": \"fix: Fix db init race condition affecting builds\",\n \"prNumber\": 1968,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nhttps://github.com/elizaOS/eliza/issues/1914#\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nCorrects the info from the auto generated readme for the Abstract plugin\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIntegration of the Anyone Network within the Eliza repository\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot tied to particular issue. Adding tests for twitter client, since \"\n },\n {\n \"title\": \"feat: Add Allora plugin\",\n \"prNumber\": 1955,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\nN/A\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n[Allora Network](https://allora.network/) is an AI-powered inference platform that delivers real-time, self-improving predictions and insights for various use cases. By aggregating a\"\n },\n {\n \"title\": \"feat: Add fraxtal chain to evm\",\n \"prNumber\": 1954,\n \"type\": \"feature\",\n \"body\": \"add fraxtal to chains\"\n },\n {\n \"title\": \"fix: fixed error in C3PO and improved error handling feedback\",\n \"prNumber\": 1951,\n \"type\": \"bugfix\",\n \"body\": \"- Resolved an array in the c3po character file where the messageExamples were an object rather an 2D array.\\r\\n- Character validation handling has been improved\\r\\n\\r\\nBefore:\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/2a7fa7c8-d903-4\"\n },\n {\n \"title\": \"fix: Added Local Embedding Manager to reuse Local embed model - Fixes High Ram Issues\",\n \"prNumber\": 1950,\n \"type\": \"bugfix\",\n \"body\": \"# Fixes\\r\\n#1942 #866 #1623\\r\\n\\r\\n# Relates to\\r\\nMemory optimization for character file knowledge processing\\r\\n\\r\\n# Risks\\r\\nLow - This change optimizes the embedding model initialization without changing core functionality.\\r\\n\\r\\n# Background\\r\\n## What \"\n },\n {\n \"title\": \"feat: support for eternalai provider can write request/response log info\",\n \"prNumber\": 1948,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nConfig eternalai logging from env, change name in env for consistent format\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nMore flexible than with env\\r\\n\\r\\n## Why are we doing this? Any con\"\n },\n {\n \"title\": \"feat: improve twitter paragraph splitting if containing url\",\n \"prNumber\": 1947,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nNA\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot related to specific issue. Since we are improving packages struct\"\n },\n {\n \"title\": \"API route update\",\n \"prNumber\": 1923,\n \"type\": \"other\",\n \"body\": \"Update to the API route\"\n },\n {\n \"title\": \"Fix typo Update CHANGELOG.md\",\n \"prNumber\": 1922,\n \"type\": \"bugfix\",\n \"body\": \"# Fix Typo in CHANGELOG.md\\r\\n\\r\\n## Description:\\r\\n\\r\\nThis pull request fixes a typographical error in the `CHANGELOG.md` file. The word \\\"initital\\\" was corrected to \\\"initial.\\\"\\r\\n\\r\\n## Changes:\\r\\n- Corrected \\\"initital\\\" to \\\"initial\\\" in the `CHANGELOG\"\n },\n {\n \"title\": \"fix: handle empty input text to avoid memory content empty error\",\n \"prNumber\": 1919,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n- #1906 \\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\ncloses https://github.com/elizaOS/eliza/issues/1901\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nFixes #1448 \\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\nClosing #1796 in favor of this to avoid conflicts.\\r\\nTEE Plugin and Adding Remote Attestations to be uploade\"\n },\n {\n \"title\": \"Feat: Support wildcard in TWITTER_TARGET_USERS 1883\",\n \"prNumber\": 1884,\n \"type\": \"feature\",\n \"body\": \"# Support wildcard in TWITTER_TARGET_USERS\\r\\n\\r\\nFixes enhancement request #1883 \\r\\n## Summary\\r\\nAdded support for wildcard `*` in `TWITTER_TARGET_USERS` configuration to allow monitoring all users. This change enables broader interaction patter\"\n },\n {\n \"title\": \"feat: Use recommended settings in jupiter swap\",\n \"prNumber\": 1882,\n \"type\": \"feature\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\nNo issue\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow risk to introduce regression in jupiter swaps\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nUse similar api call as jup.ag to perform swaps with dynamic slippage and dynamic priority fee\\r\\n\\r\\n## W\"\n },\n {\n \"title\": \"Fixed broken API Documentation URL\",\n \"prNumber\": 1881,\n \"type\": \"bugfix\",\n \"body\": \"fixed broken API Documentation in local-development.md\\r\\n\\r\\nit's not a lot, but it's honest work.\"\n },\n {\n \"title\": \"feat: add OpenWeather plugin\",\n \"prNumber\": 1880,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow - This is an additive change that introduces a new plugin without modifying existing functionality. The main risks are:\\r\\n\\r\\n- Rate limiting from OpenWeather API (1000 free API calls per day)\\r\\n- Potential timeout issues when th\"\n },\n {\n \"title\": \"test: adding test setup for telegram client\",\n \"prNumber\": 1879,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nNot related to specific issue. Since we are improving project and fol\"\n },\n {\n \"title\": \"chore(core): enable strict null checks\",\n \"prNumber\": 1878,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nType safety\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\nIssue: #1809\\r\\n\\r\\n\\r\\n\\r\\n# \"\n },\n {\n \"title\": \"feat: add coin price plugin (CoinMarketCap, CoinGecko & CoinCap)\",\n \"prNumber\": 1808,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n#1773 & #1382\\r\\n\\r\\n\\r\\n\\r\\n#\"\n },\n {\n \"title\": \"fix: broken ci docs missed frozen pnpm file out-of-sync\",\n \"prNumber\": 1798,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# \u25c0\ufe0f Relates to:\\r\\n\\r\\nFixes the build related to the pnpm-lock not being in sync from the `docs/` dir\\r\\n\\r\\n# \u26a0\ufe0f Risks\\r\\n\\r\\n* low\"\n },\n {\n \"title\": \"feat: plugin new RabbiTrader\",\n \"prNumber\": 1785,\n \"type\": \"feature\",\n \"body\": \"# Rabbi Trader Plugin\\r\\n\\r\\nAn automated cryptocurrency trading plugin for Solana tokens with integrated trust scoring, market analysis, and Twitter notifications. Built on top of Goat, used actively with: https://x.com/rabbischlomo_ai\\r\\n\\r\\n## F\"\n },\n {\n \"title\": \"feat: Image descriptions into interaction.ts\",\n \"prNumber\": 1775,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to: Irys Plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow. README update.\\r\\n\\r\\n\\r\\n# Ba\"\n },\n {\n \"title\": \"Opacity Verifiable Interference zkTLS Plugin\",\n \"prNumber\": 1673,\n \"type\": \"other\",\n \"body\": \"Co-authored @Hmac512 @RonTuretzky @Gajesh2007 \\r\\n## Background\\r\\nA few weeks ago, issues with aixbt were observed, where users mistakenly believed the moderation was performed by humans. This misconception caused a public relations disaster \"\n },\n {\n \"title\": \"Add support for Movement Network\",\n \"prNumber\": 1621,\n \"type\": \"feature\",\n \"body\": \"# Relates to:\\r\\n\\r\\n\\r\\n# Risks\\r\\nLow - non-breaking changes made to the Aptos Plugin\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nAdds support for transacting on Movement Network Testnet and Mainnet\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nNew Pl\"\n },\n {\n \"title\": \"feat: add massa-plugin\",\n \"prNumber\": 1582,\n \"type\": \"feature\",\n \"body\": \"\\r\\n## What does this PR do?\\r\\n\\r\\nAdd Massa plugin with Transfer action\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\nFeatures (non-breaking change which adds functionality)\\r\\n\\r\\n## Screenshots\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/bcb1f\"\n },\n {\n \"title\": \"feat: added new plugin - zktls - reclaim\",\n \"prNumber\": 1558,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n# Background\\r\\n\\r\\nA few weeks ago, we observed issues with aixbt, where users mistakenly believed the moderation was performed by humans. This misconception caused a public relations disaster and raised concerns about the AI\"\n },\n {\n \"title\": \"feat: support TEE logging and support running eliza in Intel SGX\",\n \"prNumber\": 1470,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to: \\r\\nKeywords: TEE, Intel SGX, Logging, Attestation, Verification, Gramine.\\r\\n\\r\\n\"\n },\n {\n \"title\": \"feat: Make templates in composeContext dynamic\",\n \"prNumber\": 1467,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to:\\r\\n\\r\\n\\r\\n\\r\\n