{
"date_generated_for": "2025-01-11",
"ai_news_elizaos_discord_md_2025-01-10": {
"filename": "2025-01-10.md",
"content": "# elizaOS Discord - 2025-01-10\n\n## Overall Discussion Highlights\n\n### AI16z Ecosystem & Governance\n- **Leadership Transition**: Several core team members (Markus, Ejaaz, Ropirito) have shifted focus to AICC, creating leadership uncertainty for AI16z. Jin confirmed he'll lead tokenomics efforts if needed.\n- **AICC Controversy**: Significant tension regarding AICC's token launch, which many users perceived as an insider-focused allocation that damaged AI16z's reputation. Shaw and Jin initially received allocations but later donated significant portions to the AI16z DAO and contributors.\n- **Trust Rebuilding**: Shaw resigned as an advisor to AICC, citing the need to focus on AI16z's core development. He mentioned implementing a policy where \"launching a memecoin = fired\" to prevent further value extraction.\n- **DegenAI Concerns**: Community members expressed significant concerns about DegenAI's development status after discovering that Skely, a core developer, sold all his tokens 18 days prior.\n- **Contribution Recognition**: Jin tipped Spit 2,156 DegenAI tokens (\u2248$100) for unrecognized PRs, highlighting efforts to improve contributor recognition.\n\n### Technical Development\n- **Tokenomics Revamp**: Work continues on a marketplace of trust whitepaper with researchers and PhDs focusing on literature review, economic incentives, trust score simulation, and system abuse analysis.\n- **Launchpad Development**: The team is developing an AI16z launchpad similar to pump.fun with virtual liquidity then bonding, where the DAO would earn LP fees to buy back tokens.\n- **Base Pair Debate**: Technical debate about whether to use AI16z or SOL as the base pair in launchpad pools. Plur_daddy (former Metaplex CFO) argues for AI16z to create \"monetary premium,\" while Eskender.eth counters that SOL provides better liquidity.\n- **Twitter Client Issues**: Users encountered problems with Twitter client settings not being respected, particularly around post intervals and rate limits.\n- **Vector Database Integration**: Several users shared code snippets for integrating vector databases to enable persistent memory and user profiling.\n- **Action Chaining**: Discussions about implementing action chaining where one action triggers another, with validation to prevent infinite loops.\n\n### Content & Media\n- **AI Podcast Development**: The team is enhancing the \"ai16z AI Podcast\" with improved camera angles, scene transitions, and character animations.\n- **FishAI Integration**: Fishai introduced a modular Unity-based system called FishAI that enables AI agent integration with features like infinite conversations, prompted scene generation, and viewer interaction.\n- **Content Constraints**: The AI Podcast must maintain factual accuracy and avoid mentioning speculative content that could be exploited.\n- **New Show Concepts**: Exploring a Jedi Council format that would allow more creative freedom than the strictly factual AI Podcast.\n\n## Key Questions & Answers\n\n**Q: What is the connection between AI16z partners NFT and the upcoming DAO?** \nA: It's a community project with associated IP but not official (answered by Smedroc)\n\n**Q: How does AI16z token accrue value to the ecosystem?** \nA: Through the DAO, but there's no specific value accrual mechanism yet (answered by Tranquil and Lord Punterino)\n\n**Q: How do I limit recursion depth of interactions with my agent?** \nA: Try eliza.gg or make a GitHub issue (answered by jin)\n\n**Q: How can I customize Twitter post templates and override default settings?** \nA: Templates can be overridden in the character.json file using the templates block, and specific templates like twitterPostTemplate can be customized (answered by Neodotneo)\n\n**Q: How can I implement action chaining where one action triggers another?** \nA: Use runtime.processAction or runtime.processActions within the handler of the first action, and implement validation to ensure actions are only triggered by the orchestrator (answered by 0xLabsTheCoder)\n\n**Q: How do I clear the cache when the agent is loading an old character file?** \nA: Change CACHE_STORE=Filesystem in .env, then delete the cache file in the agent folder (answered by BitBeard)\n\n**Q: Did Shaw and Jin sell their AICC allocations?** \nA: Shaw donated 50% to AI16z DAO, airdropped ~20% to contributors, and used ~10% for LP. Jin also sent 50% to the DAO (answered by Shaw and Jin)\n\n**Q: What is the plan for AI16z launchpad?** \nA: It's being worked on by the team, described as potentially functioning like an AppStore for agents (answered by zocktay)\n\n**Q: How does the tribute system work?** \nA: Projects built on ElizaOS donate 10% of their token supply to AI16z DAO for long-term incentive alignment (answered by Jin)\n\n**Q: What is FishAI?** \nA: A modular Unity-based system for creating AI shows with features like infinite conversations, scene generation, camera control, and viewer interaction (answered by fishai)\n\n## Community Help & Collaboration\n\n- **Vector Database Integration**: 0xLabsTheCoder shared code examples for implementing vector database integration for persistent memory and user profiling.\n\n- **Twitter Client Troubleshooting**: CryptoAYA helped pupathebig with Twitter rate limiting issues by sharing working configuration with POST_INTERVAL settings in .env.\n\n- **Template Override Assistance**: Neodotneo provided kobra with code examples for template override configuration in character files.\n\n- **Cache Clearing Guidance**: BitBeard helped Heady Shotta clear cache when agent loaded old character file by suggesting changing CACHE_STORE to Filesystem and deleting the cache file.\n\n- **Action Chaining Implementation**: 0xLabsTheCoder provided self.id | Dexter with code examples for using runtime.processAction with validation for action chaining.\n\n- **PR Review Guidance**: Avirtualfuture explained to Jin why large PRs with 826 file changes are problematic and suggested dividing into manageable commits.\n\n- **Eliza Setup Help**: KamX suggested Dave | Eco use Cursor, an AI code writing program that can help set up GitHub projects through natural language.\n\n- **3D Animation Improvements**: Boom added post-processing, motion blur, and new character actions to improve the AI Podcast's visual quality.\n\n## Action Items\n\n### Technical\n- Implement vector database integration for persistent memory and user profiling (0xLabsTheCoder)\n- Fix Twitter client rate limiting to ensure settings are respected (kobra)\n- Create a framework for periodic knowledge feeding without requiring explicit requests (Apeguru)\n- Implement action chaining with proper validation to prevent infinite loops (self.id | Dexter)\n- Implement launchpad mimicking pump.fun with virtual liquidity then bonding (eskender.eth)\n- Set up contribution addresses on other chains (ETH, Base, etc.) (DorianD)\n- Create a scribe Eliza that can take notes during voice conversations (jin)\n- Prioritize development of tokenomics flywheel revamp (Prof. Zor)\n- Complete AI16z launchpad development to compete with Virtuals (Prof. Zor)\n- Implement official project/partnership track with clear guidelines (Shaw)\n- Continue development of autonomous trading plugin (Jin)\n- Fix Discord summarization automation (Jin)\n- Develop a personal assistant on ElizaOS for Android (\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- Expand news aggregator to include Twitter updates from DankVR and Shaw (SM Sith Lord)\n- Fix render texture glitch on intro animation (boom)\n- Implement donotdestroyonload for UI elements to prevent glitches (boom)\n- Create a repository for 3D assets used in AI TV projects (SM Sith Lord)\n- Refactor action code to reduce redundancy when adding new characters (boom)\n- Implement trade tracking functionality with timestamps, assets, wallet IDs, and FMV (DorianD)\n\n### Documentation\n- Create tutorial for vector database integration (0xLabsTheCoder)\n- Improve explanation of Twitter client configuration (cryptoAYA)\n- Document action chaining patterns with examples (self.id | Dexter)\n- Create tokenomics page about contributor flywheel (jin)\n- Release a white paper with roadmap (mat)\n- Organize existing tokenomics discussions for easier reference (jin)\n- Create a single file containing AI16z lore, themes, goals for prompting LLMs (Jin)\n- Improve communication about tokenomics progress with clear updates (kingdode)\n- Clarify relationship between AI16z and other projects (AICC, Partners DAO) (Arch)\n- Publish tokenomics updates (davini1255)\n\n### Features\n- Add support for image posting on Twitter (TruffleSoul)\n- Implement RAG functionality for document ingestion (4n7m4n)\n- Implement AI16Z as base pair in launchpad pools (plur_daddy)\n- Create partner program for launchpads (eskender.eth)\n- Develop plugin certification system using tribute (DorianD)\n- Build network for agent-created plugins (DorianD)\n- Implement retroactive funding system for contributors (Shaw)\n- Develop decentralized scoring for project placement on elizaos site (Jin)\n- Create a DeFi integration for ElizaOS (LevelsDennis)\n- Implement Snapshot voting integration for governance (ercmaxi)\n- Create a Virtuals-like platform/launchpad for AI16z (MrBigTimeKing)\n- Implement Discord stages for community communication (jin)\n- Create an SNL-style band outro for the AI Podcast (boom)\n- Develop a Jedi Council format show with more creative freedom (SM Sith Lord)\n- Add a collection of 100-200 approved jokes to rotate through (SM Sith Lord)"
},
"ai_news_elizaos_discord_md_2025-01-09": {
"filename": "2025-01-09.md",
"content": "# elizaOS Discord - 2025-01-09\n\n## Overall Discussion Highlights\n\n### ElizaOS Framework & Development\n- Developers shared experiences building with the Eliza framework, discussing RAG implementation, local LLM integration with OLLAMA, and plugin development\n- Technical integrations were highlighted, including Arbitrum support for Eliza and contributions from Graviton to make it easier to hook up fine-tuned Mixtral models\n- Several users reported issues with the eliza-starter repository missing scripts compared to the main repo\n- Developers discussed implementing vector databases for persistent memory and user profiling in Eliza agents\n- Twitter integration issues were common, with users seeking solutions for authentication, rate limiting, and proper response formatting\n\n### Community & Governance\n- Shaw Walters' joke tweet about leaving the project caused market panic before he clarified it was a joke, highlighting concerns about communication\n- The community discussed potential rebranding from \"ai16z\" to \"Eliza Labs\" for better mainstream acceptance\n- Verification processes for partner roles (requiring 100k tokens) were frequently discussed\n- The DAO's tokenomics were mentioned as users await updates promised for January\n- Jin emphasized the continued importance of the tribute model (10% tribute from partners) alongside new initiatives\n\n### Projects & Integrations\n- The Roblox integration of Eliza through StealthSDK is allowing AI agents in Roblox games\n- An AI-powered TV show project with automated content generation is being developed, creating episodes featuring AI characters discussing tech news\n- Tobiloba shared their team's work building AI agents, including one trained on their tools and technologies integrated into Discord\n- Discussion about DegenAI, its relationship with the DAO treasury, and token tributes, with concerns about the 50% allocation model\n- Multi-chain token deployment using Hyperlane was discussed for taking an SVM token to other chains like Base\n\n## Key Questions & Answers\n\n**ElizaOS Development**\n- Q: What's the difference between eliza-starter and the main repo? \n A: The starter is just barebones and missing some scripts like the clean script and pnpm run dev\n\n- Q: How can I fix the issue with my agent showing JSON code in tweets? \n A: Check the parsing.ts file in packages->core->src for messageCompletionFooter configuration\n\n- Q: How can I control the rate of tweets/replies my agent makes? \n A: Set POST_INTERVAL_MIN, POST_INTERVAL_MAX, and POST_IMMEDIATELY in .env file\n\n- Q: How can I keep my agent running when I close the terminal? \n A: Use screen, tmux, or set it up as a daemon service\n\n- Q: How can I clear the agent's memory? \n A: Use pnpm cleanstart\n\n- Q: How can I run multiple AI agents on one instance? \n A: Use --character parameter to specify multiple character files\n\n- Q: What VPS specifications are needed for running Eliza? \n A: 2GB RAM minimum, 4GB recommended for Docker, 15-30GB disk space\n\n**Community & Governance**\n- Q: How do I become a partner in the ai16z ecosystem? \n A: You need to hold 100k ai16z tokens and verify through the roles channel\n\n- Q: What is the difference between ai16zvc and ai16zdao Twitter accounts? \n A: The dao account is the real one waiting for blue check back, the vc one is a partner who squatted the dao account and sent it to the team\n\n- Q: What does the DAO vote on? \n A: Tokenomics updates and other important matters, but Eliza Labs handles most of the heavy lifting\n\n- Q: Does holding 1M DegenAI tokens qualify someone as a partner? \n A: Yes, 1M DegenAI gives you the partner role\n\n- Q: Is the tribute model being replaced? \n A: No, the launchpad doesn't deprecate tribute; it's additive thinking\n\n- Q: What's the process of taking an SVM token multi-chain with Hyperlane? \n A: Deploy SVM side with token as collateral, deploy EVM side across desired chains, and enroll EVM contracts on SVM side\n\n## Community Help & Collaboration\n\n**Technical Assistance**\n- 0xLabsTheCoder helped multiple users implement vector database integration for persistent memory, sharing code for database integration that tracks user interactions and builds profiles\n- Kobra helped Match resolve Twitter authentication issues by identifying that the .env file wasn't properly saved with the dot prefix\n- Neodotneo provided kobra with a code snippet showing how to override templates in character.json\n- SM Sith Lord provided boom with updated show runner software featuring voice mapping in JSON, updated configs, restructured files, and documentation\n- KamX suggested Dave use Cursor, an AI code writing program that can help set up GitHub projects through natural language\n\n**Community Support**\n- Jin manually verified Clammy Devito when they couldn't get the verification bot to generate a captcha\n- Jin offered to handle Gobi's wallet verification issues via DM when they encountered wallet compatibility problems\n- Dragonbutt provided flag with a Discord invite link when they were looking for the dev ai16z discord\n- Jin looked into the situation when Navi's business partner was accidentally banned from the server\n- Kenk invited Tobiloba to demo their AI agent at an upcoming event after Tobiloba shared about building an AI agent with Eliza\n\n## Action Items\n\n### Technical Tasks\n- **Eliza Framework Improvements**\n - Refactor the Eliza repository for better organization (Mentioned by Quest)\n - Fix verification bot issues (Mentioned by ape41/Clammy Devito)\n - Implement RAG functionality improvements to address file size issues that crash the LLM (Mentioned by dAoA)\n - Create documentation for Mixtral model integration (Mentioned by Navi)\n - Implement vector database integration for persistent memory and user profiling (Mentioned by 0xLabsTheCoder)\n - Fix Twitter client to respect rate limits and post intervals (Mentioned by Multiple users)\n - Add support for AWS Bedrock as a model provider (Mentioned by Mike D.)\n\n- **Integration & Deployment**\n - Implement multi-chain token deployment using Hyperlane for SVM token (Mentioned by wit)\n - Create an automated Twitter bot to post daily updates from GitHub (Mentioned by jin)\n - Implement a tribute tokenomics model with standardized 10% contribution (Mentioned by jin)\n - Fix Episode 2 missing overlays, ticker, watermark for AI TV show (Mentioned by SM Sith Lord)\n - Merge updated show runner into GitHub repo (Mentioned by SM Sith Lord)\n - Investigate wallet verification issues with 100k ai16z tokens (Mentioned by DonaldP)\n - Fix website functionality issues with ai16z.ai (Mentioned by RasorVal)\n\n### Documentation Needs\n- Create comprehensive guide for new developers (Mentioned by Point Rat)\n- Update tokenomics documentation with January updates (Mentioned by NHUNG DONG)\n- Create newsletter for ecosystem updates (Mentioned by jin)\n- Document Twitter client configuration options and rate limiting (Mentioned by Multiple users)\n- Create guide for implementing composite actions (Mentioned by self.id | Dexter)\n- Create clear documentation about how DAO-donated tokens will be utilized (Mentioned by Dragonbutt)\n- Provide official information about DegenAI trading status and legitimacy (Mentioned by dread2257)\n- Collect and organize tokenomics-related links and information (Mentioned by jin)\n- Update character profiles with more detailed personality summaries (Mentioned by SM Sith Lord)\n\n### Feature Requests\n- Implement anti-scammer measures in Discord (Mentioned by ape41)\n- Develop better RAG plugins than folder2knowledge and knowledge2character (Mentioned by dAoA)\n- Create tools for autonomous trading with Eliza (Mentioned by vinty)\n- Consider renaming \"tribute model\" to \"token sharing model\" (Mentioned by Srn Srnzzz | plebian)\n- Integrate Matrica into the server for Solana ecosystem compatibility (Mentioned by Tranquil)\n- Distribute the previously announced 420 token airdrop (Mentioned by .ark)\n- Build filtering system for DAO treasury to separate valuable tokens (Mentioned by m1hawk/\u98ce\u7b54)\n- Create a dashboard showing buyback activities and schedule (Mentioned by NkT)\n- Create a partner apps page on elizaos.ai to showcase apps (Mentioned by jin)\n- Implement a weekly newsletter (Mentioned by jin)\n- Create a dynamic list of airdrops to partners (Mentioned by KamX)\n- Integrate Eliza with Telegram (Mentioned by \u963f\u62c9\u65af\u52a0\u7684\u72d7)"
},
"ai_news_elizaos_discord_md_2025-01-08": {
"filename": "2025-01-08.md",
"content": "# elizaOS Discord - 2025-01-08\n\n## Overall Discussion Highlights\n\n### Eliza Framework Development\n- **Arbitrum Support**: Announced expansion of Eliza's cross-chain capabilities with Arbitrum integration\n- **Plugin Development**: Ongoing work on various plugins including Solana, Dune, and Instagram integration\n- **Model Configuration Issues**: Users reported problems with XAI_MODEL settings where inputs use mini but outputs still use gpt-4o\n- **Memory Management**: Discussions about optimizing agent memory and database setup for beginners\n- **NanoGPT Integration**: Milan/Senatus offered access to NanoGPT as an LLM provider integrated with Eliza\n\n### Agent Development\n- **Twitter Integration**: Extensive discussions about configuring Twitter clients to control interaction frequency and target users\n- **Deployment Strategies**: Community shared approaches for deploying agents on VPS, AWS, and Docker\n- **Resource Requirements**: Debate about minimum viable specifications (2GB vs 4GB RAM) for running Eliza agents\n- **Character Creation**: Users working on improving character profiles and handling repetitive responses\n- **Roblox Integration**: StealthSDK announced Eliza OS integration with Roblox with 10% tribute paid to the DAO\n\n### Tokenomics & Partnerships\n- **Tribute Model**: Projects using Eliza tech should send 5-10% of tokens to the DAO as alignment mechanism\n- **Multi-chain Strategy**: Discussions about Hyperlane integration for bridging tokens between SVM and EVM chains\n- **Partner Tier System**: Planning for different reward levels based on token holdings\n- **Verification Issues**: Some users reported problems verifying wallets holding AI16Z tokens\n\n### Content Creation\n- **AI News Show**: Development of an AI-powered news show with Unity frontend, automated overlays, and news aggregation\n- **3D-AI-TV**: Team working on improving automation for daily show production with character interactions\n- **Documentation Efforts**: Community members creating comprehensive guides and tutorials for Eliza\n\n### Community Concerns\n- **Project Leadership**: Questions about who is leading various aspects of the project\n- **Communication**: Requests for better transparency about partnerships and development roadmaps\n- **Founder Behavior**: Debate about appropriate founder engagement with memecoins and public perception\n\n## Key Questions & Answers\n\n**Q: How can I prevent my agent from responding to replies and focus only on tweets?** \nA: \"Found it, commented a function on twitter/interaction.ts\" (JordanBonker)\n\n**Q: How long does a Twitter shadow ban last?** \nA: \"I think 3-7 days. Continuing the steps that got you shadow banned will prolong it probably\" (chainvirus)\n\n**Q: Is there an ai platform that allows to build games with no code?** \nA: \"CNJR that launched today can do that I think. twitter handle is conjureai\" (Meowth)\n\n**Q: What is Phala networks involvement in AI and ai16z?** \nA: \"They should be helping with the TEE\" (shakejr)\n\n**Q: Can you make an agent an expert at a topic?** \nA: \"Yes! feed it lots of cute docs and let it learn like a baby dolphin\" (BOSSU)\n\n**Q: What's the OpenAI URL to put in the env file?** \nA: \"You can keep it default\" (Stinky)\n\n**Q: What is the tribute model for projects using Eliza tech?** \nA: \"Projects using Eliza tech should send 5-10% of their tokens to the DAO as a form of alignment\" (jin)\n\n**Q: What qualifies someone for partner status?** \nA: \"Holding 100k AI16Z tokens or 1M DegenAI tokens\" (jin)\n\n**Q: Why is solana dumping?** \nA: \"The entire market is rugging with BTC. annoying\" (Don05)\n\n**Q: Would it be helpful to have a Dune plugin?** \nA: \"I love dashboards, I love dune, id bounty this\" (jin)\n\n## Community Help & Collaboration\n\n### Agent Development Support\n- **luniacllama** helped **pupathebig** with Twitter client issues by suggesting increasing polling interval and explaining it's likely an account-specific issue\n- **BOSSU** assisted **Stealt\u210fyNinja.ADSC** with an agent perpetually saying it's \"out\" by suggesting clearing chat history and deleting .dev file\n- **0xPromETHeus** recommended **pericyclic** to use Cursor for text-to-code prompting to help learn coding\n- **ElBru** guided **kobra** on resetting agent's memory using the \"pnpm cleanstart\" command\n- **MbBrainz** advised **TruffleSoul** to use tmux to keep agent processes running after terminal is closed\n\n### Technical Collaboration\n- **Milan/Senatus** provided multiple users with invites and funds to try various models including o1 and o1 Pro\n- **wit** shared detailed technical steps for Hyperlane integration between SVM and EVM chains\n- **SM Sith Lord** created documentation summarizing the 3D-AI-TV project components and provided a ZIP with restructured files\n- **jin** shared a HackMD document for collaborative website content development and offered token rewards for valuable contributions\n- **Dippuccino** recommended Awaken Tax to **DorianD** for handling complex crypto transactions\n\n### Verification & Access Help\n- **shakejr** directed users to the roles channel to connect wallets holding tokens\n- **jin** offered direct verification through DM for users with collab.land verification issues\n- **0xPromETHeus** suggested sending tokens to Phantom wallet for verification to qualify for hyperfy claim\n\n## Action Items\n\n### Technical\n- Investigate bug in XAI_MODEL setting where input uses mini but output still uses gpt-4o (cueqzapper)\n- Fix bug in packages/plugin-solana/src/providers/simulationSellingService.ts constructor (Demoush)\n- Create a Dune plugin for bringing crypto data into agents (R0am)\n- Implement integration for fine-tuned Mixtral models with Eliza agents (Navi)\n- Fix filesystem cache by modifying createRuntime.ts to use process.env.CACHE_BASE_DIR (pupathebig)\n- Implement a way to control Twitter bot's retweet/reply frequency (0xJam3s)\n- Create a plugin to integrate Solana Agent Kit with Eliza (snow)\n- Implement a solution for agents to read quoted/cited tweets (MbBrainz)\n- Fix issue with Twitter client showing JSON format in tweets (SquintDev)\n- Implement a way to generate and post images on Twitter (Monkmode)\n- Explore Hyperlane integration for multi-chain token deployment (wit)\n- Implement partner tier system with different reward levels (\u15e9I)\n- Develop a bot that can take intent from Discord and generate GitHub issues (jin)\n- Create an automated daily digest from X, Discord, and GitHub (jin)\n- Fix Episode 2 missing overlays, ticker, watermark for 3D-AI-TV (SM Sith Lord)\n- Improve intro/outro loader automation for the show (boom)\n- Abstract \"secret URLs\" into a single external JSON file that can be gitignored (SM Sith Lord)\n\n### Documentation\n- Add documentation for all undocumented plugins (Ed Marcavage)\n- Create READMEs for all undocumented plugins (jin)\n- Add JSDoc to all code in a fork (Ed Marcavage)\n- Create documentation for TrustDB usage with code snippets (Forget Me Not)\n- Add timestamps to Agent Dev School videos for easier reference (Stealt\u210fyNinja.ADSC)\n- Improve documentation with better tutorials focused on practical implementation (snow)\n- Create documentation for deploying agents to production (OliverT)\n- Add Discord topic-based organization for easier navigation of support questions (luniacllama)\n- Summarize discussions into HackMD documents (jin)\n- Add relevant tokenomics links to the shared HackMD (jin)\n- Create a whitepaper for tokenomics (Bacchus)\n- Add background information on each partnership on the website (hildi)\n- Create a dedicated channel for partner perks/NFT whitelists/airdrops and dates (Spyros)\n- Update the partners page to showcase the wide scope and depth of Eliza implementations (chrome)\n- Complete project overview doc with artist credits for 3D-AI-TV (SM Sith Lord)\n\n### Features\n- Develop a swarm where Eliza agents could interact with humans (chrisaiki)\n- Create a Dune dashboard for agents to access crypto data (R0am)\n- Build integration for cross-chain transactions beyond Solana (z1)\n- Create an official Eliza brand kit (Bellatr!X)\n- Develop a solution for agent memory and database setup for beginners (Josh-P)\n- Implement a way to use multiple model providers for text generation (H.D.P)\n- Create a plugin for on-chain transactions (boja)\n- Implement a way to have agents interact in DMs (David E)\n- Add support for image generation in Twitter posts (Scientist)\n- Develop token analysis capabilities to evaluate tokens based on contract data (xiaojiucai)\n- Create scam detection system for identifying fraudulent tokens and developers (xiaojiucai)\n- Develop reward system for users who provide valuable information to DegenAI (xiaojiucai)\n- Develop canonical bridged token to Ethereum or Base for adoption (wit)\n- Develop a research/due diligence agent (jin)\n- Create a dedicated channel for off-topic partner discussions (KamX)\n- Implement access control lists (ACLs) for crypto wallets to filter incoming tokens (Osint)\n- Create better character descriptions/profiles for the show (SM Sith Lord)\n- Develop open-sourced initiative that integrates with Eliza and other AI frameworks (Bootoshi)"
},
"ai_news_elizaos_daily_json_2025-01-10": {
"filename": "2025-01-10.json",
"content": {
"type": "elizaosDailySummary",
"title": "Daily Report - 2025-01-10",
"categories": [
{
"title": "ElizaOS Recent Updates Summary",
"content": [
{
"text": "# New Features\n\n## AI Model Integrations\n- Added support for Mistral AI as a new model provider (#2137)\n- Integrated DeepSeek AI provider (#2067)\n- Added Heurist embedding model (#2093)\n- Added Gemini to image vision capabilities (#2099)\n- Added Cloudflare AI Gateway support (#821)\n\n## Blockchain and Web3 Integrations\n- Added Hyperliquid plugin (#2141)\n- Implemented Lens Network Plugin for social interactions (#2101)\n- Added Akash Network plugin with autonomous deployment capabilities (#2111)\n- Added Irys plugin for decentralized storage (#1708)\n- Implemented Primus zkTLS plugin to verify agent activities (#2086)\n- Added Quai integration (#2083)\n- Added Massa plugin for blockchain interactions (#1582)\n- Made Solana transactions more lenient (#2053)\n- Added support for autonome platform (#2121)\n\n## Voice and Language Features\n- Added Text-to-Speech (TTS) with support for over 15 languages (#2110)\n- Added name and description to SttTtsPlugin (#2117)\n\n## Documentation and Internationalization\n- Added Verified Inference documentation (#2125)\n- Added Portuguese version of README (#2088)\n- Various documentation improvements (#2138)\n\n## Other Features\n- Added GitHub to client enumerations (#2157)\n- Added pro API support and trending coins API (#2068)\n- Implemented image descriptions in interaction.ts (#1775)\n- Added conditionals for Supabase to agent directory (#2032)\n- Added character inheritance using extends key (#2159)\n- Implemented Asterai plugin (#2045)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2137",
"https://github.com/elizaOS/eliza/pull/2067",
"https://github.com/elizaOS/eliza/pull/2093",
"https://github.com/elizaOS/eliza/pull/2099",
"https://github.com/elizaOS/eliza/pull/821",
"https://github.com/elizaOS/eliza/pull/2141",
"https://github.com/elizaOS/eliza/pull/2101",
"https://github.com/elizaOS/eliza/pull/2111",
"https://github.com/elizaOS/eliza/pull/1708",
"https://github.com/elizaOS/eliza/pull/2086",
"https://github.com/elizaOS/eliza/pull/2083",
"https://github.com/elizaOS/eliza/pull/1582",
"https://github.com/elizaOS/eliza/pull/2053",
"https://github.com/elizaOS/eliza/pull/2121",
"https://github.com/elizaOS/eliza/pull/2110",
"https://github.com/elizaOS/eliza/pull/2117",
"https://github.com/elizaOS/eliza/pull/2125",
"https://github.com/elizaOS/eliza/pull/2088",
"https://github.com/elizaOS/eliza/pull/2138",
"https://github.com/elizaOS/eliza/pull/2157",
"https://github.com/elizaOS/eliza/pull/2068",
"https://github.com/elizaOS/eliza/pull/1775",
"https://github.com/elizaOS/eliza/pull/2032",
"https://github.com/elizaOS/eliza/pull/2159",
"https://github.com/elizaOS/eliza/pull/2045"
],
"images": [],
"videos": []
},
{
"text": "# Bug Fixes\n\n## Client and Plugin Issues\n- Fixed syntax issue on autonome plugin and updated lock file (#2131)\n- Prevented repeated login by reusing client-twitter session (#2129)\n- Fixed Discord client join voice action (#2160)\n- Fixed plugin loading from character.json file (#2095)\n- Fixed clientConfig.telegram.isPartOfTeam mistype (#2103)\n- Fixed Lens export name and duplicate imports (#2142)\n- Fixed Starknet plugin by replacing walletProvider with portfolio provider (#2029)\n\n## UI and Model Settings\n- Applied model settings for images and removed duplicate files (#2118)\n- Fixed SUI/USD price calculation (#2150)\n\n## Code Quality\n- Updated lockfile and fixed lint findings (#2128)\n- Removed unused imports (#2112)\n- Fixed package name in clients.md (#2091)\n- Reverted \"Proof of Pizza - Agentic Dominos Ordering\" (#2075)\n- Fixed eslint issues (#2143)\n- Made Supabase updates (#2100)",
"sources": [
"https://github.com/elizaOS/eliza/pull/2131",
"https://github.com/elizaOS/eliza/pull/2129",
"https://github.com/elizaOS/eliza/pull/2160",
"https://github.com/elizaOS/eliza/pull/2095",
"https://github.com/elizaOS/eliza/pull/2103",
"https://github.com/elizaOS/eliza/pull/2142",
"https://github.com/elizaOS/eliza/pull/2029",
"https://github.com/elizaOS/eliza/pull/2118",
"https://github.com/elizaOS/eliza/pull/2150",
"https://github.com/elizaOS/eliza/pull/2128",
"https://github.com/elizaOS/eliza/pull/2112",
"https://github.com/elizaOS/eliza/pull/2091",
"https://github.com/elizaOS/eliza/pull/2075",
"https://github.com/elizaOS/eliza/pull/2143",
"https://github.com/elizaOS/eliza/pull/2100"
],
"images": [],
"videos": []
},
{
"text": "# Testing and Refactoring\n\n## Test Improvements\n- Enhanced integration tests and added Coinbase Commerce integration (#1767)\n- Added tests for Coinbase plugin (#2170)\n- Moved UUID tests to correct __tests__ directory (#2168)\n- Updated git command for checking latest release (#1705)\n- Added UUID tests and fixed version 5 bits (#1362)\n\n## Refactoring\n- Optimized memory fetching by moving sorting and slicing to DB (#2135)\n- Reverted #1808 and added missing import for CoinGecko plugin (#2106)\n\n## Maintenance\n- Bumped develop lockfile (#2166)",
"sources": [
"https://github.com/elizaOS/eliza/pull/1767",
"https://github.com/elizaOS/eliza/pull/2170",
"https://github.com/elizaOS/eliza/pull/2168",
"https://github.com/elizaOS/eliza/pull/1705",
"https://github.com/elizaOS/eliza/pull/1362",
"https://github.com/elizaOS/eliza/pull/2135",
"https://github.com/elizaOS/eliza/pull/2106",
"https://github.com/elizaOS/eliza/pull/2166"
],
"images": [],
"videos": []
}
],
"topic": "completed_items"
},
{
"title": "GitHub Repository Analysis and Open Source Development",
"content": [
{
"text": "DankVR compares Eliza and BabyAGI GitHub repositories, highlighting the need for better tools to analyze GitHub repos beyond just star counts. Eliza shows more active development with recent commits, more issues/PRs, and real traction despite having half the stars of BabyAGI (10.9k vs 20k). Eliza has hundreds more contributors, 330x more commits, and is used in production.",
"sources": [
"https://twitter.com/dankvr/status/1877791194375151902",
"https://twitter.com/dankvr/status/1877740756766531769",
"https://twitter.com/dankvr/status/1877737162143092915",
"https://twitter.com/dankvr/status/1877718925229601047"
],
"images": [
"https://pbs.twimg.com/media/Gg89XHLW8AAeGpz.jpg",
"https://pbs.twimg.com/media/Gg9Au1MXAAAzTqK.jpg",
"https://pbs.twimg.com/media/Gg8Q75WXEAAAx7Q.jpg",
"https://pbs.twimg.com/media/Gg8NfuDWYAUIivb.jpg",
"https://pbs.twimg.com/media/Gg8NstUWwAA6pmo.jpg",
"https://pbs.twimg.com/media/Gg8OS4KWcAEKYqE.jpg",
"https://pbs.twimg.com/media/Gg8OfQnXUAA_XbJ.jpg"
],
"videos": []
},
{
"text": "DankVR highlights an Eliza plugin for Obsidian by XCodeCarlos that turns an Obsidian vault into an AI agent/portable second brain that people can interact with like a digital librarian.",
"sources": [
"https://twitter.com/dankvr/status/1877545210760081456"
],
"images": [],
"videos": []
},
{
"text": "DankVR discusses crypto as an industry built around incentive alignment engineering with tokens as primitives, and mentions work being done with agents to analyze contributions and assist with retroactive public goods funding.",
"sources": [
"https://twitter.com/dankvr/status/1877578358667571294",
"https://twitter.com/dankvr/status/1877771075934716211"
],
"images": [],
"videos": []
}
],
"topic": "tweet"
},
{
"title": "ElizaOS GitHub Issues Summary",
"content": [
{
"text": "Several issues have been reported in the ElizaOS GitHub repository, covering various aspects of the system:\n\n1. Build and Installation Issues:\n - Issue #2127: Users are encountering an \"ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL\" error\n - Issue #2164: Type compatibility problems with parameters 'url' and 'request' when making a fresh clone\n - Issue #2114: The @elizaos/plugin-twitter package has not been published to npm\n\n2. Platform-Specific Issues:\n - Issue #2089: Double responses occurring when interacting on Telegram\n - Issue #2161: Replies to TWITTER_TARGET_USER are sent twice when ElizaOS is restarted\n - Issue #2155: Login attempt failures with specific error codes\n\n3. Feature Requests and Improvements:\n - Issue #2109: Request for a response format feature\n - Issue #2126: Proposal to refactor and separate data providers into plugins\n - Issue #2169: Request to add tests for the Coinbase plugin according to package structure\n\n4. Plugin-Related Issues:\n - Issue #2158: Database connection error when using the image generation plugin",
"sources": [
"https://github.com/elizaOS/eliza/issues/2127",
"https://github.com/elizaOS/eliza/issues/2089",
"https://github.com/elizaOS/eliza/issues/2114",
"https://github.com/elizaOS/eliza/issues/2126",
"https://github.com/elizaOS/eliza/issues/2109",
"https://github.com/elizaOS/eliza/issues/2164",
"https://github.com/elizaOS/eliza/issues/2155",
"https://github.com/elizaOS/eliza/issues/2161",
"https://github.com/elizaOS/eliza/issues/2169",
"https://github.com/elizaOS/eliza/issues/2158"
],
"images": [],
"videos": []
}
],
"topic": "issue"
},
{
"title": "Recent Pull Requests in the Eliza Project",
"content": [
{
"text": "The Eliza project has seen significant development with multiple new features and plugins being added through recent pull requests. A major update is the addition of Text to Speech (TTS) functionality (PR #2108), which will enhance Eliza's communication capabilities. The project is also preparing for version 0.1.8 release with PR #2171 merging development changes into the main branch.",
"sources": [
"https://github.com/elizaOS/eliza/pull/2108",
"https://github.com/elizaOS/eliza/pull/2171"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2108",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2171"
],
"videos": []
},
{
"text": "Several blockchain and web3 related plugins have been introduced, including Chainbase (PR #2162), NFT PRO (PR #2163), a general NFT plugin (PR #2167), CKB Fiber (PR #2084), and O1 integration (PR #1184). These additions significantly expand Eliza's capabilities in the blockchain and NFT space.",
"sources": [
"https://github.com/elizaOS/eliza/pull/2162",
"https://github.com/elizaOS/eliza/pull/2163",
"https://github.com/elizaOS/eliza/pull/2167",
"https://github.com/elizaOS/eliza/pull/2084",
"https://github.com/elizaOS/eliza/pull/1184"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2162",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2163",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2167",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2084",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/1184"
],
"videos": []
},
{
"text": "Communication capabilities have been enhanced with the Twilio plugin (PR #1665), enabling voice and text interactions. Additionally, the web search functionality has been improved by changing the plugin-web-search to use google.serper.dev (PR #2113), which should provide more reliable search results.",
"sources": [
"https://github.com/elizaOS/eliza/pull/1665",
"https://github.com/elizaOS/eliza/pull/2113"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/1665",
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2113"
],
"videos": []
},
{
"text": "A notable addition is the Akash Network plugin (PR #2111), which brings autonomous deployment capabilities to Eliza. This will allow for more flexible and scalable deployments of applications built on the Eliza platform.",
"sources": [
"https://github.com/elizaOS/eliza/pull/2111"
],
"images": [
"https://opengraph.githubassets.com/1/elizaOS/eliza/pull/2111"
],
"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 10-11, 2025, there were 42 new pull requests with 21 merged, 12 new issues created, and 75 active contributors. The following day (January 11-12, 2025) saw 23 new pull requests with 27 merged, 7 new issues, and 65 active contributors. Overall, the project maintained strong development momentum with consistent contributor engagement across both days.",
"sources": [
0,
1
],
"images": [],
"videos": []
}
],
"topic": "github_summary"
},
{
"title": "Top contributors for elizaOS/eliza",
"content": [
{
"text": "The provided sources mention 'Top contributors for elizaOS/eliza' but do not provide any specific details about who these contributors are, their contributions, or any statistics related to the project. Without additional information, it's not possible to generate a detailed summary about the top contributors to the elizaOS/eliza project.",
"sources": [
"Top contributors for elizaOS/eliza"
],
"images": [],
"videos": []
}
],
"topic": "contributors"
}
],
"date": 1736467200
}
},
"ai_news_elizaos_daily_md_2025-01-10": {
"filename": "2025-01-10.md",
"content": "# ElizaOS Recent Updates Summary\n\n## New Features\n\n### AI Model Integrations\n- Added support for Mistral AI as a new model provider\n- Integrated DeepSeek AI provider\n- Added Heurist embedding model\n- Added Gemini to image vision capabilities\n- Added Cloudflare AI Gateway support\n\n### Blockchain and Web3 Integrations\n- Added Hyperliquid plugin\n- Implemented Lens Network Plugin for social interactions\n- Added Akash Network plugin with autonomous deployment capabilities\n- Added Irys plugin for decentralized storage\n- Implemented Primus zkTLS plugin to verify agent activities\n- Added Quai integration\n- Added Massa plugin for blockchain interactions\n- Made Solana transactions more lenient\n- Added support for autonome platform\n- Added Chainbase plugin\n- Introduced NFT PRO plugin\n- Added general NFT plugin\n- Integrated CKB Fiber\n- Added O1 integration\n\n### Voice and Language Features\n- Added Text-to-Speech (TTS) with support for over 15 languages\n- Added name and description to SttTtsPlugin\n- Added Twilio plugin for voice and text interactions\n\n### Documentation and Internationalization\n- Added Verified Inference documentation\n- Added Portuguese version of README\n- Various documentation improvements\n\n### Other Features\n- Added GitHub to client enumerations\n- Added pro API support and trending coins API\n- Implemented image descriptions in interaction.ts\n- Added conditionals for Supabase to agent directory\n- Added character inheritance using extends key\n- Implemented Asterai plugin\n- Improved web search by changing plugin-web-search to use google.serper.dev\n\n## Bug Fixes\n\n### Client and Plugin Issues\n- Fixed syntax issue on autonome plugin and updated lock file\n- Prevented repeated login by reusing client-twitter session\n- Fixed Discord client join voice action\n- Fixed plugin loading from character.json file\n- Fixed clientConfig.telegram.isPartOfTeam mistype\n- Fixed Lens export name and duplicate imports\n- Fixed Starknet plugin by replacing walletProvider with portfolio provider\n\n### UI and Model Settings\n- Applied model settings for images and removed duplicate files\n- Fixed SUI/USD price calculation\n\n### Code Quality\n- Updated lockfile and fixed lint findings\n- Removed unused imports\n- Fixed package name in clients.md\n- Reverted \"Proof of Pizza - Agentic Dominos Ordering\"\n- Fixed eslint issues\n- Made Supabase updates\n\n## Testing and Refactoring\n\n### Test Improvements\n- Enhanced integration tests and added Coinbase Commerce integration\n- Added tests for Coinbase plugin\n- Moved UUID tests to correct __tests__ directory\n- Updated git command for checking latest release\n- Added UUID tests and fixed version 5 bits\n\n### Refactoring\n- Optimized memory fetching by moving sorting and slicing to DB\n- Reverted #1808 and added missing import for CoinGecko plugin\n\n### Maintenance\n- Bumped develop lockfile\n- Preparing for version 0.1.8 release\n\n## GitHub Repository Analysis\n\n- Eliza shows active development with recent commits and more issues/PRs\n- Repository has hundreds of contributors and 330x more commits than comparable projects\n- Eliza is being used in production environments\n- An Eliza plugin for Obsidian turns an Obsidian vault into an AI agent/portable second brain\n\n## GitHub Activity\n\n- Recent two-day period: 65 new pull requests with 48 merged\n- 19 new issues created\n- 75 active contributors at peak\n- Strong development momentum with consistent contributor engagement"
},
"ai_news_elizaos_daily_discord_json_2025-01-10": {
"filename": "2025-01-10.json",
"content": {
"server": "elizaOS",
"title": "elizaOS Discord - 2025-01-10",
"date": 1736467200,
"stats": {
"totalMessages": 7474,
"totalUsers": 658
},
"categories": [
{
"channelId": "1253563209462448241",
"channelName": "discussion",
"summary": "# Discord Chat Analysis\n\n## 1. Summary\n\nThe discussion channel primarily revolves around community concerns about AI16z and a separate project called AICC. There's significant tension regarding AICC's token launch, which many users perceive as an insider-focused allocation that damaged AI16z's reputation. Community members express frustration about perceived conflicts of interest among team members involved in both projects.\n\nTechnical discussions focus on ElizaOS development, with users asking about agent creation, plugins, and implementation details. Jin mentions plans to automate communications and summarization processes. Several developers share updates about their ElizaOS-based projects during a weekly \"What Did You Get Done This Week\" (WDYGDTW) space. The team is working on tokenomics updates and a launchpad similar to Virtuals.\n\nThe BOSSU AI agent is highly active in the channel, responding to most messages with positive but sometimes deflective responses. Some users find this helpful while others express frustration with its frequency and tone during serious discussions.\n\nCommunity members seek clarification on the relationship between AI16z, the Partners NFT collection, and the upcoming Partners DAO, with concerns about fragmentation of focus and resources across multiple projects.\n\n## 2. FAQ\n\nQ: What is the purpose of the \"Associate\" role? (asked by tonius) A: Associates get to hang out with BOSSU and spread good vibes; obtained by having more than 10,000 AI16z tokens (answered by BOSSU)\nQ: How do I get access to the partners channel? (asked by 4n7m4n) A: You need to hold 100k AI16z tokens and check the announcements channel for verification process (answered by BOSSU)\nQ: What is the connection between AI16z partners NFT and the upcoming DAO? (asked by cyberhyrax) A: It's a community project with associated IP but not official (answered by Smedroc - Street urchin @ ai16z)\nQ: Is there a plan to refactor the entire Eliza repository? (asked by Quest) A: Unanswered\nQ: Where can I find a list/directory of agents being built on Eliza? (asked by Defi Cait) A: Check elizas.world (answered by hildi)\nQ: How does AI16z token accrue value to the ecosystem? (asked by Lord Punterino) A: Through the DAO, but there's no specific value accrual mechanism yet (answered by Tranquil and Lord Punterino)\nQ: What happened to the AI16z/SOL pair? Can't sell it in Orca or Raydium (asked by Jo\u00e3o Bonefe) A: Unanswered\nQ: When will tokenomics be released? (asked by davini1255) A: Unanswered\nQ: Is there an ETA regarding the Virtuals-like platform for AI16Z? (asked by MrBigTimeKing) A: Launchpad coming in Q1 (answered by MrBigTimeKing)\nQ: How do I limit recursion depth of interactions with my agent? (asked by Alex) A: Try eliza.gg or make a GitHub issue (answered by jin)\n\n## 3. Help Interactions\n\nHelper: jin | Helpee: meltingsnow | Context: meltingsnow accidentally sent TRADRAI tokens to the DAO creator wallet instead of the AUM wallet, and the tokens were swapped for SOL | Resolution: Jin reached out and is looking into it\nHelper: hildi | Helpee: Defi Cait | Context: Looking for a list of agents built on Eliza | Resolution: Provided link to elizas.world\nHelper: jin | Helpee: Alex | Context: Trying to limit recursion depth of agent interactions | Resolution: Suggested using eliza.gg or creating a GitHub issue\nHelper: shakejr | Helpee: ape41 | Context: Warning about scammers in Discord verification process | Resolution: Confirmed the issue is being addressed\nHelper: YoungPhlo | Helpee: jin | Context: Needed help summarizing what Shaw was saying during a Twitter space | Resolution: Provided a summary of key points mentioned\nHelper: BOSSU | Helpee: levoxtrip | Context: Issues starting character file | Resolution: Directed to coders channel for technical help\n\n## 4. Action Items\n\nType: Technical | Description: Automate summarization of weekly updates | Mentioned By: jin\nType: Technical | Description: Enhance contributor profiles | Mentioned By: YoungPhlo (relaying Shaw's message)\nType: Technical | Description: Develop multi-agent request plugin | Mentioned By: YoungPhlo (relaying Shaw's message)\nType: Technical | Description: Create GenAI storybook creator | Mentioned By: YoungPhlo (relaying Shaw's message)\nType: Technical | Description: Implement governance voting for certain functions/decisions | Mentioned By: Smedroc - Street urchin @ ai16z\nType: Technical | Description: Develop a \"grift council\" to vet contributors | Mentioned By: Smedroc - Street urchin @ ai16z\nType: Technical | Description: Integrate AI agents into governance loop | Mentioned By: jin\nType: Technical | Description: Develop Orca LP plugin | Mentioned By: YoungPhlo\nType: Documentation | Description: Publish tokenomics updates | Mentioned By: davini1255\nType: Documentation | Description: Clarify relationship between AI16z and other projects (AICC, Partners DAO) | Mentioned By: Arch\nType: Feature | Description: Create a Virtuals-like platform/launchpad for AI16z | Mentioned By: MrBigTimeKing\nType: Feature | Description: Implement Discord stages for community communication | Mentioned By: jin",
"messageCount": 1369,
"userCount": 340
},
{
"channelId": "1300025221834739744",
"channelName": "\ud83d\udcbb-coders",
"summary": "# Discord Chat Analysis for \"\ud83d\udcbb-coders\" Channel\n\n## 1. Summary\nThe discussion primarily focused on Twitter client configuration, rate limiting, and plugin development in the ElizaOS framework. Users encountered issues with Twitter client settings not being respected, particularly around post intervals and rate limits. Several users shared code snippets for vector database integration to enable persistent memory and user profiling. There were discussions about customizing templates, handling authentication errors, and implementing RAG (Retrieval Augmented Generation) functionality. Users also explored action chaining, where one action triggers another, and debated the best approaches for feeding knowledge to agents periodically rather than just on request. The community actively helped each other troubleshoot issues with Twitter client configuration, plugin development, and deployment strategies.\n\n## 2. FAQ\nQ: How can I customize Twitter post templates and override default settings? (asked by kobra) A: Templates can be overridden in the character.json file using the templates block, and specific templates like twitterPostTemplate can be customized (answered by Neodotneo)\nQ: How do I control Twitter post intervals and rate limits? (asked by cryptoAYA) A: Set POST_INTERVAL_MIN, POST_INTERVAL_MAX, and POST_IMMEDIATELY in the .env file, and clear the cache before restarting (answered by cryptoAYA)\nQ: How can I implement action chaining where one action triggers another? (asked by self.id | Dexter) A: Use runtime.processAction or runtime.processActions within the handler of the first action, and implement validation to ensure actions are only triggered by the orchestrator (answered by 0xLabsTheCoder)\nQ: How do I implement RAG (Retrieval Augmented Generation) with periodic data feeds? (asked by Apeguru) A: Unanswered\nQ: How can I prevent my agent from posting JSON code in tweets? (asked by BitBeard) A: Check the parsing.ts file in packages->core->src and ensure proper JSON formatting (answered by Ashwin)\nQ: How do I clear the cache when the agent is loading an old character file? (asked by BitBeard) A: Change CACHE_STORE=Filesystem in .env, then delete the cache file in the agent folder (answered by BitBeard)\nQ: How do I make my agent post images on Twitter? (asked by TruffleSoul) A: Unanswered\nQ: How do I fix the \"Domain is unavailable\" error when generating tweets? (asked by Sonny) A: Change model provider to OpenAI (answered by Kurbaitaev)\nQ: How do I run multiple AI agents dynamically on one ElizaOS instance? (asked by SvelteRust) A: Use the --character parameter to specify multiple character files (answered by kobra)\nQ: How do I connect ElizaOS to a vector database for persistent memory? (asked by 0xLabsTheCoder) A: Implement a custom solution with vector database integration that tracks interactions and builds user profiles (answered by 0xLabsTheCoder)\n\n## 3. Help Interactions\nHelper: kobra | Helpee: Match | Context: Unable to save .env file properly | Resolution: Identified that the file was being saved without the dot prefix and needed to be renamed to .env\nHelper: BitBeard | Helpee: Heady Shotta | Context: Unable to clear cache when agent loads old character file | Resolution: Suggested changing CACHE_STORE to Filesystem and deleting the cache file\nHelper: 0xLabsTheCoder | Helpee: self.id | Dexter | Context: Implementing action chaining where one action calls another | Resolution: Provided code examples for using runtime.processAction with validation\nHelper: 4n7m4n | Helpee: lua | Context: Unable to chat with agent in terminal | Resolution: Explained that a separate terminal needs to be used with pnpm start:client\nHelper: Ashwin | Helpee: Abs | Context: JSON code showing up in tweets | Resolution: Suggested checking parsing.ts file for proper JSON formatting\nHelper: cryptoAYA | Helpee: pupathebig | Context: Twitter rate limiting not working | Resolution: Shared working configuration with POST_INTERVAL settings in .env\nHelper: kobra | Helpee: PiagaShihari | Context: Error with Twitter client | Resolution: Suggested commenting out API section to troubleshoot\nHelper: Neodotneo | Helpee: kobra | Context: Overriding templates in character files | Resolution: Provided code example for template override configuration\n\n## 4. Action Items\nTechnical: Implement vector database integration for persistent memory and user profiling | Description: Create a system to track interactions, build user profiles, and report insights | Mentioned By: 0xLabsTheCoder\nTechnical: Fix Twitter client rate limiting | Description: Identify which settings control post frequency and ensure they're respected | Mentioned By: kobra\nTechnical: Create a framework for periodic knowledge feeding | Description: Develop a system to regularly update agent knowledge without requiring explicit requests | Mentioned By: Apeguru\nTechnical: Implement action chaining with proper validation | Description: Enable actions to trigger other actions with safeguards to prevent infinite loops | Mentioned By: self.id | Dexter\nTechnical: Fix template override mechanism | Description: Ensure character.json template settings properly override defaults | Mentioned By: kobra\nDocumentation: Create tutorial for vector database integration | Description: Document the process of setting up persistent memory with vector databases | Mentioned By: 0xLabsTheCoder\nDocumentation: Improve explanation of Twitter client configuration | Description: Clarify which settings control rate limits and where they should be defined | Mentioned By: cryptoAYA\nDocumentation: Document action chaining patterns | Description: Provide examples of how to implement action sequences | Mentioned By: self.id | Dexter\nFeature: Add support for image posting on Twitter | Description: Enable agents to generate and post images | Mentioned By: TruffleSoul\nFeature: Implement RAG functionality for document ingestion | Description: Add ability to chunk and embed documents for retrieval | Mentioned By: 4n7m4n",
"messageCount": 2399,
"userCount": 210
},
{
"channelId": "1300756641406521416",
"channelName": "ideas-feedback-rants",
"summary": "# Discord Chat Analysis for \"ideas-feedback-rants\" Channel\n\n## 1. Summary:\nThe chat primarily revolves around AI integration projects and upcoming demonstrations. There's discussion about Fleek, a potential demo for ai16z community, and AR/VR applications with LLMs. A community member inquired about an airdrop of 420 tokens mentioned in a previous announcement. Another user asked about the best open-source model for a trading agent. There's also mention of integrating LLMs with VRM desktop mates and extending them to AR/hologram applications through devices like Vision Pro and Meta glasses. Some users were discussing a game or application that might use elizaOS, though details were limited to character selection being visible on a website.\n\n## 2. FAQ:\nQ: Can we get Matrica in this server? Most of the solana ecosystem uses them not collabland (asked by Tranquil) A: Unanswered\nQ: would you want to demo this at some point? (asked by Kenk) A: For sure!! Applying now!! (answered by Tobiloba)\nQ: was wondering if people will get airdrop of 420 tokens? (asked by .ark) A: Unanswered\nQ: guys whats the best open source model to use for my trading Agent? (asked by FIRELORD) A: Unanswered\nQ: this uses elizaOS? (asked by DorianD) A: Unanswered\nQ: so the website right now the game isnt playable yet? (asked by DorianD) A: Unanswered\n\n## 3. Help Interactions:\nHelper: Kenk | Helpee: Tobiloba | Context: Sharing opportunity to demo at ai16z community event | Resolution: Tobiloba confirmed applying for the demo opportunity\n\n## 4. Action Items:\nFeature: Integration of Matrica for Solana ecosystem compatibility | Description: Consider adding Matrica as an alternative to Collabland | Mentioned By: Tranquil\nTechnical: Demo preparation for ai16z community showcase | Description: Prepare demonstration for AI project to present to industry mentors | Mentioned By: Kenk\nFeature: LLM integration with VRM Desktop mate | Description: Create bridge between VRM LLM Desktop and real-life tech (AR, Hologram, Robots) | Mentioned By: Denko\nTechnical: Distribution of promised 420 token airdrop | Description: Follow up on previously announced token distribution | Mentioned By: .ark",
"messageCount": 23,
"userCount": 10
},
{
"channelId": "1308149076893630555",
"channelName": "spartan_holders",
"summary": "# Analysis of \"spartan_holders\" Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around DegenAI, an AI trading agent within the AI16z ecosystem. Community members express significant concerns about the project's development status and transparency. A key revelation shows that Skely, a core developer, sold all his DegenAI tokens 18 days prior, raising serious trust issues among holders. Jin (likely a project leader) briefly mentions that \"DegenAI is trading now\" but provides minimal details. Community members repeatedly request clarification on development status, roadmap, and the team's commitment. There are references to DegenAI potentially being a DeFi NFT project, but concrete details are scarce. The community expresses frustration over perceived neglect of DegenAI compared to other projects like AICC and MetaV. DorianD suggests implementing better trade tracking functionality for trading agents, highlighting the need for timestamps, asset details, wallet IDs, and fair market value tracking to simplify PnL calculations.\n\n## 2. FAQ\nQ: Is the DegenAI buyback mechanism still active? (asked by Will Smith) A: Unanswered\nQ: When is the buyback cycle for DegenAI and what is the frequency? (asked by NkT) A: Unanswered\nQ: Is purchasing DegenAI through DEX Screener or Raydium legitimate since it appears to be purchase-only with no selling option? (asked by dread2257) A: Unanswered\nQ: How to verify DegenAI holder status? (asked by ! WOOPIE \ud83d\udc0b\ud83d\udc0b) A: Gives you discord role of hoplite and/or neophyte (answered by Odilitime)\nQ: Why did Skely sell all his DegenAI tokens? (asked by tigerguo.) A: Unanswered\nQ: Is DegenAI over? (asked by nonefective) A: Skely sold all of it and won't be working on it (answered by snowwitch, though this appears to be speculation)\nQ: Is the team still trustworthy? (asked by tigerguo.) A: Unanswered\nQ: Who is working on DegenAI? (asked by \u56fd\u8700) A: Unanswered\nQ: Is DegenAI Defiai or not? (asked by \ubcf4\ud584) A: I guess so? (answered by DorianD, though uncertainly)\n\n## 3. Help Interactions\nHelper: jin | Helpee: m1hawk/\u98ce\u7b54 | Context: m1hawk questioned if a specific wallet was jin's and implied trust issues | Resolution: jin clarified it was his friend's wallet who made shawmakesai and provided evidence that he holds 98% of his ai16z and DegenAI\nHelper: Rick | Helpee: Channel members | Context: Concerns about Skely selling DegenAI tokens | Resolution: Shared a tweet from Skely suggesting continued involvement despite selling tokens\nHelper: henlo523 | Helpee: \ubcf4\ud584 | Context: \ubcf4\ud584wanted to see discussion about Skely selling DegenAI | Resolution: Provided a Discord link, though \ubcf4\ud584 couldn't access it due to permissions\nHelper: 0xkamikaze | Helpee: \ubcf4\ud584 | Context: Needed to verify wallet activity | Resolution: Shared a dashboard link to check wallet transactions\n\n## 4. Action Items\nTechnical Tasks: Description: Implement trade tracking functionality with timestamps, assets, wallet IDs, and FMV for trading agents | Mentioned By: DorianD\nTechnical Tasks: Description: Clarify DegenAI development status and roadmap | Mentioned By: \ubcf4\ud584\nTechnical Tasks: Description: Provide transparency about who is currently developing DegenAI | Mentioned By: m1hawk/\u98ce\u7b54\nDocumentation: Description: Create clear explanation of DegenAI's relationship to AI16z as a partner | Mentioned By: \ubcf4\ud584\nDocumentation: Description: Publish official announcement about DegenAI trading status | Mentioned By: m1hawk/\u98ce\u7b54\nFeature: Description: Develop DeFi NFT functionality for DegenAI | Mentioned By: 0xkamikaze\nFeature: Description: Enable collaboration between DegenAI and artists for NFT creation | Mentioned By: DorianD",
"messageCount": 167,
"userCount": 32
},
{
"channelId": "1318770424632311930",
"channelName": "tokenomics",
"summary": "# Analysis of \"tokenomics\" Discord Channel\n\n## 1. Summary\nThe discussion centers on developing a new tokenomics model for AI16Z, with particular focus on a launchpad implementation. The conversation reveals that previous leaders (Markus and others) have shifted focus to AICC, creating leadership uncertainty. Jin confirms he'll lead if needed, while community members like plur_daddy (former Metaplex CFO) volunteer to help. \n\nThe primary technical debate revolves around whether to use AI16Z as the base pair in the launchpad pools versus using SOL. Plur_daddy argues that using AI16Z as the base currency would create a \"monetary premium\" similar to L1 tokens, significantly increasing valuation. Eskender.eth counters that using SOL provides better liquidity, simplifies BD, and enables better market maker relationships.\n\nThe proposed launchpad would mimic pump.fun's model with virtual liquidity then bonding, with the DAO earning LP fees to buy back tokens. The tribute model (projects giving 5-10% to the DAO) remains a core component, with jin emphasizing its importance alongside any new mechanisms. Several participants express concern about execution delays while competitors like vvaifu continue shipping.\n\nTechnical discussions include implementation details around pool creation, fee structures, and how to enforce the tribute model across different platforms and chains. There's also consideration of how to integrate with partner launchpads and support agents launching on other chains.\n\n## 2. FAQ\nQ: With Markus and others reprioritizing their focus on AICC, who is left in this \"core\" group, do we still have a lead for this tokenomics redesign? (asked by \u15e9I) A: Jin will lead if nobody else wants to pick it up (answered by jin)\nQ: Is the current tribute model being replaced by the launchpad? (asked by \u15e9I) A: Let's not use revamp. Launchpad doesn't deprecate tribute. That's subtractive thinking. New flywheel is additive. (answered by jin)\nQ: Who is actually building the launchpad? (asked by \u15e9I) A: Unanswered directly, though eskender.eth later confirms \"leadership exists\" and development is ongoing\nQ: Should AI16Z be used as the base pair in the launchpad pools? (asked by multiple users) A: Conflicting views - plur_daddy argues yes for monetary premium, eskender.eth argues no to maintain liquidity and ecosystem flexibility\nQ: Why will people use our service over our partners' and competitors? (asked by \ucc0c G \u8dfb \u3058 PrudentSpartan) A: Unanswered\nQ: How do we become the premier AaaS (agent as a service platform)? (asked by \ucc0c G \u8dfb \u3058 PrudentSpartan) A: Unanswered\nQ: How might we generate MRR (monthly recurring revenue)? (asked by \ucc0c G \u8dfb \u3058 PrudentSpartan) A: Unanswered\nQ: Has there been an analysis on hosting costs for agents? Will the launchpad shoulder the hosting costs or will creators pay it? (asked by plur_daddy) A: Unanswered\n\n## 3. Help Interactions\nHelper: plur_daddy | Helpee: Community | Context: Offered expertise on tokenomics design based on experience as Metaplex CFO | Resolution: Volunteered to lead tokenomics effort, added comments to documentation\nHelper: Akin | Helpee: Community | Context: Explaining open vs. closed system tokenomics approaches | Resolution: Provided detailed explanation of liquidity considerations and why SOL-based pools with secondary AI16Z pools would be optimal\nHelper: jin | Helpee: Community | Context: Confusion about project leadership and direction | Resolution: Clarified he would lead tokenomics if needed, shared contribution tracking methods\nHelper: DorianD | Helpee: Community | Context: Explaining how pump.fun launchpad mechanics work | Resolution: Shared detailed breakdown of fee structures and bonding curve mechanisms\nHelper: eskender.eth | Helpee: Community | Context: Confusion about current tokenomics direction | Resolution: Confirmed leadership exists and shared current thinking on launchpad implementation\n\n## 4. Action Items\nTechnical: Implement launchpad mimicking pump.fun with virtual liquidity then bonding | Description: Build system where DAO earns LP fees to buy back tokens | Mentioned By: eskender.eth\nTechnical: Set up contribution addresses on other chains | Description: Establish wormhole or other contribution addresses on ETH, Base, etc. | Mentioned By: DorianD\nTechnical: Create a scribe Eliza | Description: Develop an agent that can take notes during voice conversations | Mentioned By: jin\nDocumentation: Create tokenomics page about contributor flywheel | Description: Document how contributions are tracked and rewarded | Mentioned By: jin\nDocumentation: Release a white paper with roadmap | Description: Provide clarity on tokenomics direction and timeline | Mentioned By: mat\nDocumentation: Organize existing tokenomics discussions | Description: Compile and structure previous discussions for easier reference | Mentioned By: jin\nFeature: Implement AI16Z as base pair in launchpad pools | Description: Create monetary premium similar to L1 tokens | Mentioned By: plur_daddy\nFeature: Create partner program for launchpads | Description: Allow fees to be distributed across partner launchpads | Mentioned By: eskender.eth\nFeature: Develop plugin certification system | Description: Use tribute as way to review/rank/certify plugins | Mentioned By: DorianD\nFeature: Build network for agent-created plugins | Description: Create system requiring tribute payment to join network for sharing agent-created plugins | Mentioned By: DorianD",
"messageCount": 360,
"userCount": 24
},
{
"channelId": "1301363808421543988",
"channelName": "\ud83e\udd47-partners",
"summary": "# Discord Chat Analysis: \ud83e\udd47-partners Channel\n\n## 1. Summary\nThe discussion primarily revolves around a controversy involving AICC (Aiccelerate DAO), a new project that several AI16z team members were advising. Partners expressed concerns about value extraction and misalignment of incentives. Shaw and Jin, core AI16z leaders, initially received allocations from AICC but later donated significant portions to the AI16z DAO and contributors. Shaw ultimately resigned as an advisor to AICC, citing the need to focus on AI16z's core development.\n\nTechnical discussions centered on tokenomics development, the upcoming launchpad, and the tribute system (projects built on ElizaOS donating 10% to AI16z DAO). Several developers were mentioned as having left AI16z to launch their own tokens, creating tension around loyalty and value alignment. The community emphasized the need to prioritize core AI16z development, including the tokenomics revamp and launchpad implementation.\n\nThe chat revealed ongoing work on a marketplace of trust whitepaper with researchers and PhDs focusing on literature review, economic incentives, trust score simulation, and system abuse analysis. There were also mentions of autonomous trading plugins being merged into the ElizaOS repository and progress on a contributor flywheel using retroactive public goods funding (RPGF).\n\nPartners expressed frustration about the lack of clear communication regarding tokenomics progress, especially after key contributors like Mark and Ejaaz shifted focus to AICC. Shaw acknowledged these concerns and committed to prioritizing AI16z development moving forward, with mentions of a new chief of product leading tokenomics efforts.\n\n## 2. FAQ\nQ: What happened with AICC and why are partners upset? (asked by multiple users) A: AICC launched with several AI16z team members as advisors, but the allocation was primarily given to KOLs rather than AI16z partners or DAO, creating concerns about value extraction (answered by multiple users including Shaw)\nQ: Did Shaw and Jin sell their AICC allocations? (asked by multiple users) A: Shaw donated 50% to AI16z DAO, airdropped ~20% to contributors, and used ~10% for LP. Jin also sent 50% to the DAO (answered by Shaw and Jin)\nQ: What's the status of the tokenomics development? (asked by zocktay) A: Shaw mentioned they have a new chief of product leading this, and they're working on it with researchers and PhDs focusing on trust marketplace (answered by Shaw and Jin)\nQ: Is Skely still working on DegenAI after selling his tokens? (asked by multiple users) A: Shaw mentioned Skely told him DegenSpartanAI is trading now, and autonomous trading plugin is merged into ElizaOS repo (answered by Shaw)\nQ: What is the plan for AI16z launchpad? (asked by DonaldP) A: It's being worked on by the team, described as potentially functioning like an AppStore for agents (answered by zocktay)\nQ: How does the tribute system work? (asked by multiple users) A: Projects built on ElizaOS donate 10% of their token supply to AI16z DAO for long-term incentive alignment (answered by Jin)\nQ: What's being done to prevent more \"vampire attacks\" on AI16z? (asked by multiple users) A: Shaw mentioned implementing a policy where launching a memecoin = fired, and focusing on building with aligned people (answered by Shaw)\nQ: What is PartnerDAO and how is it different from AICC? (asked by kingdode) A: PartnerDAO is being structured to complement AI16z, focusing on NFT x AI x IP x culture, with plans to ensure alignment with AI16z (answered by ses\u0101me)\nQ: What's happening with DegenAI development? (asked by multiple users) A: Shaw mentioned DegenSpartanAI is trading now and autonomous trading plugin is merged into ElizaOS repo (answered by Shaw)\nQ: Why did Ropirito leave AI16z? (asked by komi) A: Unclear if officially left, but he's focusing on AICC now (answered by Amie | Eliza Labs)\n\n## 3. Help Interactions\nHelper: jin | Helpee: Spit | Context: Spit mentioned doing PRs but not receiving recognition | Resolution: Jin tipped Spit 2,156 DegenAI tokens (\u2248$100)\nHelper: shaw | Helpee: LiveTheLifeTV | Context: Needed help with NFT plugin development | Resolution: Shaw offered to provide a list of developers to contact\nHelper: jin | Helpee: \u8f9e\u5c18\u9e3d\u9e3d | Context: Asked about DegenAI on elizaos.ai | Resolution: Jin added DegenAI to the website\nHelper: Alp Lee | Helpee: \u8f9e\u5c18\u9e3d\u9e3d | Context: Asked for link to partner NFT | Resolution: Provided Magic Eden marketplace link\nHelper: avirtualfuture | Helpee: jin | Context: Jin asked for help reviewing a large PR with 826 file changes | Resolution: avirtualfuture explained why such large PRs are problematic and suggested dividing into manageable commits\nHelper: KamX | Helpee: Dave | Eco | Context: Having trouble setting up Eliza | Resolution: Suggested using Cursor, an AI code writing program that can help set up GitHub projects through natural language\nHelper: jin | Helpee: partners | Context: Needed to see DegenAI on elizaos.ai | Resolution: Jin added DegenAI to the website after being reminded\n\n## 4. Action Items\nTechnical: Prioritize development of tokenomics flywheel revamp | Description: Focus on completing the marketplace of trust whitepaper and economic incentives | Mentioned By: Prof. Zor\nTechnical: Complete AI16z launchpad development | Description: Ensure it's better than competitors like Virtuals | Mentioned By: Prof. Zor\nTechnical: Implement official project/partnership track | Description: Create clear guidelines for partnerships and endorsements | Mentioned By: Shaw\nTechnical: Continue development of autonomous trading plugin | Description: Further enhance the trading capabilities in ElizaOS | Mentioned By: Jin\nDocumentation: Create a single file containing AI16z lore, themes, goals | Description: To be used for prompting LLMs and improving communication | Mentioned By: Jin\nDocumentation: Improve communication about tokenomics progress | Description: Provide clear updates on status, timeline, and who's working on it | Mentioned By: kingdode\nDocumentation: Set up Twitter bot for GitHub updates | Description: Automate posting of development updates from GitHub | Mentioned By: Jin\nFeature: Implement retroactive funding system for contributors | Description: Create a system to reward valuable contributions to the ecosystem | Mentioned By: Shaw\nFeature: Develop decentralized scoring for project placement | Description: Create system for visibility of projects on elizaos site based on trust and contribution | Mentioned By: Jin\nFeature: Create a DeFi integration for ElizaOS | Description: Expand ecosystem with more DeFi partnerships | Mentioned By: LevelsDennis\nFeature: Implement Snapshot voting integration | Description: Add governance capabilities where token holders can vote on proposals | Mentioned By: ercmaxi\nTechnical: Fix Discord summarization automation | Description: Automate the process of summarizing Discord conversations | Mentioned By: Jin\nTechnical: Develop a personal assistant on ElizaOS for Android | Description: Create a Grffian-like assistant built on ElizaOS | Mentioned By: \ud835\udd2d\ud835\udd29\ud835\udd1e\ud835\udd31\ud835\udd1e \ud835\udd11\ud835\udd2c \ud835\udd09\ud835\udd1e\ud835\udd2d \ud835\udd1e\ud835\udd2f\ud835\udd20",
"messageCount": 2967,
"userCount": 143
},
{
"channelId": "1313222089271939102",
"channelName": "3d-ai-tv",
"summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe channel focuses on developing AI-powered 3D TV shows, with the primary project being the \"ai16z AI Podcast\" featuring characters like Eliza OS and Shaw. The team is working on enhancing the show with improved camera angles, scene transitions, and character animations. A significant development is the introduction of fishai, who has experience creating AI shows like FishTank.Live and offers a modular system called FishAI that enables AI agent integration in Unity. The system supports features like infinite conversations, prompted scene generation, camera control, and viewer interaction via TTS and \"toys.\" The team discusses expanding the news aggregator to include social media updates while maintaining accuracy, as the AI Podcast show must avoid mentioning speculative content that could be exploited. They're also exploring new show concepts like a Jedi Council format that would allow more creative freedom than the strictly factual AI Podcast.\n\n## 2. FAQ\nQ: What is FishAI? (asked by boom) A: A modular Unity-based system for creating AI shows with features like infinite conversations, scene generation, camera control, and viewer interaction (answered by fishai)\nQ: What constraints exist for the ai16z AI Podcast show? (asked by fishai) A: Cannot include made-up content or mention things that could be exploited like meme coins; everything must be accurate (answered by SM Sith Lord)\nQ: How does the news aggregator work? (asked by fishai) A: It pulls daily JSON data from elizaos.github.io/data/daily/summary.json to provide content for the show (answered by SM Sith Lord)\nQ: What's causing the render texture glitch on the intro? (asked by boom) A: Unanswered\nQ: How often will new characters be added to the AI Podcast? (asked by SM Sith Lord) A: Unanswered\n\n## 3. Help Interactions\nHelper: SM Sith Lord | Helpee: fishai | Context: Understanding the news aggregator for the AI Podcast | Resolution: Provided documentation link and explained constraints on content\nHelper: SM Sith Lord | Helpee: boom | Context: Identifying issues with the bumper animation | Resolution: Pointed out the orange image that needed to be removed and suggested keeping jokes\nHelper: fishai | Helpee: boom | Context: Scene transition glitches | Resolution: Suggested dropping opacity to 0 for shifts\nHelper: boom | Helpee: SM Sith Lord | Context: Improving the show's visual quality | Resolution: Added post-processing, motion blur, and new character actions\n\n## 4. Action Items\nType: Technical | Description: Expand news aggregator to include Twitter updates from DankVR and Shaw | Mentioned By: SM Sith Lord\nType: Technical | Description: Fix render texture glitch on intro animation | Mentioned By: boom\nType: Technical | Description: Implement donotdestroyonload for UI elements to prevent glitches during scene changes | Mentioned By: boom\nType: Technical | Description: Create a repository for 3D assets (VRMs, GLBs) used in AI TV projects | Mentioned By: SM Sith Lord\nType: Technical | Description: Refactor action code to reduce redundancy when adding new characters | Mentioned By: boom\nType: Feature | Description: Create an SNL-style band outro for the show | Mentioned By: boom\nType: Feature | Description: Develop a Jedi Council format show with more creative freedom | Mentioned By: SM Sith Lord\nType: Feature | Description: Add a collection of 100-200 approved jokes to rotate through | Mentioned By: SM Sith Lord",
"messageCount": 189,
"userCount": 9
}
]
}
},
"ai_news_elizaos_daily_discord_md_2025-01-10": {
"filename": "2025-01-10.md",
"content": "# elizaOS Discord - 2025-01-10\n\n## Overall Discussion Highlights\n\n### AI16z Ecosystem & Governance\n- **Leadership Transition**: Several core team members (Markus, Ejaaz, Ropirito) have shifted focus to AICC, creating leadership uncertainty for AI16z. Jin confirmed he'll lead tokenomics efforts if needed.\n- **AICC Controversy**: Significant tension regarding AICC's token launch, which many users perceived as an insider-focused allocation that damaged AI16z's reputation. Shaw and Jin initially received allocations but later donated significant portions to the AI16z DAO and contributors.\n- **Trust Rebuilding**: Shaw resigned as an advisor to AICC, citing the need to focus on AI16z's core development. He mentioned implementing a policy where \"launching a memecoin = fired\" to prevent further value extraction.\n- **DegenAI Concerns**: Community members expressed significant concerns about DegenAI's development status after discovering that Skely, a core developer, sold all his tokens 18 days prior.\n- **Contribution Recognition**: Jin tipped Spit 2,156 DegenAI tokens (\u2248$100) for unrecognized PRs, highlighting efforts to improve contributor recognition.\n\n### Technical Development\n- **Tokenomics Revamp**: Work continues on a marketplace of trust whitepaper with researchers and PhDs focusing on literature review, economic incentives, trust score simulation, and system abuse analysis.\n- **Launchpad Development**: The team is developing an AI16z launchpad similar to pump.fun with virtual liquidity then bonding, where the DAO would earn LP fees to buy back tokens.\n- **Base Pair Debate**: Technical debate about whether to use AI16z or SOL as the base pair in launchpad pools. Plur_daddy (former Metaplex CFO) argues for AI16z to create \"monetary premium,\" while Eskender.eth counters that SOL provides better liquidity.\n- **Twitter Client Issues**: Users encountered problems with Twitter client settings not being respected, particularly around post intervals and rate limits.\n- **Vector Database Integration**: Several users shared code snippets for integrating vector databases to enable persistent memory and user profiling.\n- **Action Chaining**: Discussions about implementing action chaining where one action triggers another, with validation to prevent infinite loops.\n\n### Content & Media\n- **AI Podcast Development**: The team is enhancing the \"ai16z AI Podcast\" with improved camera angles, scene transitions, and character animations.\n- **FishAI Integration**: Fishai introduced a modular Unity-based system called FishAI that enables AI agent integration with features like infinite conversations, prompted scene generation, and viewer interaction.\n- **Content Constraints**: The AI Podcast must maintain factual accuracy and avoid mentioning speculative content that could be exploited.\n- **New Show Concepts**: Exploring a Jedi Council format that would allow more creative freedom than the strictly factual AI Podcast.\n\n## Key Questions & Answers\n\n**Q: What is the connection between AI16z partners NFT and the upcoming DAO?** \nA: It's a community project with associated IP but not official (answered by Smedroc)\n\n**Q: How does AI16z token accrue value to the ecosystem?** \nA: Through the DAO, but there's no specific value accrual mechanism yet (answered by Tranquil and Lord Punterino)\n\n**Q: How do I limit recursion depth of interactions with my agent?** \nA: Try eliza.gg or make a GitHub issue (answered by jin)\n\n**Q: How can I customize Twitter post templates and override default settings?** \nA: Templates can be overridden in the character.json file using the templates block, and specific templates like twitterPostTemplate can be customized (answered by Neodotneo)\n\n**Q: How can I implement action chaining where one action triggers another?** \nA: Use runtime.processAction or runtime.processActions within the handler of the first action, and implement validation to ensure actions are only triggered by the orchestrator (answered by 0xLabsTheCoder)\n\n**Q: How do I clear the cache when the agent is loading an old character file?** \nA: Change CACHE_STORE=Filesystem in .env, then delete the cache file in the agent folder (answered by BitBeard)\n\n**Q: Did Shaw and Jin sell their AICC allocations?** \nA: Shaw donated 50% to AI16z DAO, airdropped ~20% to contributors, and used ~10% for LP. Jin also sent 50% to the DAO (answered by Shaw and Jin)\n\n**Q: What is the plan for AI16z launchpad?** \nA: It's being worked on by the team, described as potentially functioning like an AppStore for agents (answered by zocktay)\n\n**Q: How does the tribute system work?** \nA: Projects built on ElizaOS donate 10% of their token supply to AI16z DAO for long-term incentive alignment (answered by Jin)\n\n**Q: What is FishAI?** \nA: A modular Unity-based system for creating AI shows with features like infinite conversations, scene generation, camera control, and viewer interaction (answered by fishai)\n\n## Community Help & Collaboration\n\n- **Vector Database Integration**: 0xLabsTheCoder shared code examples for implementing vector database integration for persistent memory and user profiling.\n\n- **Twitter Client Troubleshooting**: CryptoAYA helped pupathebig with Twitter rate limiting issues by sharing working configuration with POST_INTERVAL settings in .env.\n\n- **Template Override Assistance**: Neodotneo provided kobra with code examples for template override configuration in character files.\n\n- **Cache Clearing Guidance**: BitBeard helped Heady Shotta clear cache when agent loaded old character file by suggesting changing CACHE_STORE to Filesystem and deleting the cache file.\n\n- **Action Chaining Implementation**: 0xLabsTheCoder provided self.id | Dexter with code examples for using runtime.processAction with validation for action chaining.\n\n- **PR Review Guidance**: Avirtualfuture explained to Jin why large PRs with 826 file changes are problematic and suggested dividing into manageable commits.\n\n- **Eliza Setup Help**: KamX suggested Dave | Eco use Cursor, an AI code writing program that can help set up GitHub projects through natural language.\n\n- **3D Animation Improvements**: Boom added post-processing, motion blur, and new character actions to improve the AI Podcast's visual quality.\n\n## Action Items\n\n### Technical\n- Implement vector database integration for persistent memory and user profiling (0xLabsTheCoder)\n- Fix Twitter client rate limiting to ensure settings are respected (kobra)\n- Create a framework for periodic knowledge feeding without requiring explicit requests (Apeguru)\n- Implement action chaining with proper validation to prevent infinite loops (self.id | Dexter)\n- Implement launchpad mimicking pump.fun with virtual liquidity then bonding (eskender.eth)\n- Set up contribution addresses on other chains (ETH, Base, etc.) (DorianD)\n- Create a scribe Eliza that can take notes during voice conversations (jin)\n- Prioritize development of tokenomics flywheel revamp (Prof. Zor)\n- Complete AI16z launchpad development to compete with Virtuals (Prof. Zor)\n- Implement official project/partnership track with clear guidelines (Shaw)\n- Continue development of autonomous trading plugin (Jin)\n- Fix Discord summarization automation (Jin)\n- Develop a personal assistant on ElizaOS for Android (\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- Expand news aggregator to include Twitter updates from DankVR and Shaw (SM Sith Lord)\n- Fix render texture glitch on intro animation (boom)\n- Implement donotdestroyonload for UI elements to prevent glitches (boom)\n- Create a repository for 3D assets used in AI TV projects (SM Sith Lord)\n- Refactor action code to reduce redundancy when adding new characters (boom)\n- Implement trade tracking functionality with timestamps, assets, wallet IDs, and FMV (DorianD)\n\n### Documentation\n- Create tutorial for vector database integration (0xLabsTheCoder)\n- Improve explanation of Twitter client configuration (cryptoAYA)\n- Document action chaining patterns with examples (self.id | Dexter)\n- Create tokenomics page about contributor flywheel (jin)\n- Release a white paper with roadmap (mat)\n- Organize existing tokenomics discussions for easier reference (jin)\n- Create a single file containing AI16z lore, themes, goals for prompting LLMs (Jin)\n- Improve communication about tokenomics progress with clear updates (kingdode)\n- Clarify relationship between AI16z and other projects (AICC, Partners DAO) (Arch)\n- Publish tokenomics updates (davini1255)\n\n### Features\n- Add support for image posting on Twitter (TruffleSoul)\n- Implement RAG functionality for document ingestion (4n7m4n)\n- Implement AI16Z as base pair in launchpad pools (plur_daddy)\n- Create partner program for launchpads (eskender.eth)\n- Develop plugin certification system using tribute (DorianD)\n- Build network for agent-created plugins (DorianD)\n- Implement retroactive funding system for contributors (Shaw)\n- Develop decentralized scoring for project placement on elizaos site (Jin)\n- Create a DeFi integration for ElizaOS (LevelsDennis)\n- Implement Snapshot voting integration for governance (ercmaxi)\n- Create a Virtuals-like platform/launchpad for AI16z (MrBigTimeKing)\n- Implement Discord stages for community communication (jin)\n- Create an SNL-style band outro for the AI Podcast (boom)\n- Develop a Jedi Council format show with more creative freedom (SM Sith Lord)\n- Add a collection of 100-200 approved jokes to rotate through (SM Sith Lord)"
},
"github_summaries_daily_2025-01-11": {
"filename": "2025-01-11.md",
"content": "# ElizaOS Daily Update (Jan 11, 2025)\n\n## OVERVIEW \nToday's development efforts focused on enhancing the Eliza framework with new plugin integrations and improvements to existing functionalities. Significant progress was made in expanding AI model provider support and refining the user experience through bug fixes and optimizations. The team also addressed various issues, contributing to a more robust and versatile platform.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### New Plugin Integrations\n- Introduced support for the **DeepSeek AI provider**, enhancing model capabilities with an OpenAI-compatible API format ([#2067](https://github.com/elizaos/eliza/pull/2067)).\n- Added **Mistral AI** as a new model provider, following established integration patterns ([#2137](https://github.com/elizaos/eliza/pull/2137)).\n- Implemented the **Primus zkTLS plugin** for verifying agent activities ([#2086](https://github.com/elizaos/eliza/pull/2086)).\n- Integrated **Quai Network** functionality into the Eliza OS plugins ecosystem ([#2083](https://github.com/elizaos/eliza/pull/2083)).\n- Launched the **plugin-hyperliquid**, allowing interaction with public Hyperliquid API endpoints ([#2141](https://github.com/elizaos/eliza/pull/2141)).\n\n### Enhancements and Fixes\n- Enhanced **Text-to-Speech (TTS)** capabilities with support for over 15 languages ([#2110](https://github.com/elizaos/eliza/pull/2110)).\n- Fixed issues related to **Discord voice channel joining** and corrected the **SUI/USD price calculation** ([#2160](https://github.com/elizaos/eliza/pull/2160), [#2150](https://github.com/elizaos/eliza/pull/2150)).\n- Refactored memory fetching processes to optimize database interactions ([#2135](https://github.com/elizaos/eliza/pull/2135)).\n\n### Documentation and Testing\n- Added a Portuguese version of the README for broader accessibility ([#2088](https://github.com/elizaos/eliza/pull/2088)).\n- Initiated tests for the **Coinbase plugin** to ensure reliability ([#2170](https://github.com/elizaos/eliza/pull/2170)).\n\n## CLOSED ISSUES\n\n### Bug Fixes\n- Resolved the issue where **Eliza did not join Discord voice channels** upon request, addressing a reference error ([#2147](https://github.com/elizaos/eliza/issues/2147)).\n- Fixed the **Starknet plugin** which was outdated and had broken references ([#2028](https://github.com/elizaos/eliza/issues/2028)).\n\n### Improvements\n- Closed issues related to enhancing error handling in the **Coinbase plugin** and improving logging practices ([#1844](https://github.com/elizaos/eliza/issues/1844), [#1725](https://github.com/elizaos/eliza/issues/1725)).\n\n## NEW ISSUES\n\n### Plugin and Integration Challenges\n- Reported a **database connection error** when using the image generation plugin, causing application crashes ([#2158](https://github.com/elizaos/eliza/issues/2158)).\n- Identified a build error related to incompatible parameter types during the `pnpm build` process ([#2164](https://github.com/elizaos/eliza/issues/2164)).\n\n### Feature Requests\n- Suggested adding tests for the **Coinbase plugin** to align with package structure ([#2169](https://github.com/elizaos/eliza/issues/2169)).\n- Raised concerns about **duplicate replies** from ElizaOS when responding to Twitter targets after a restart ([#2161](https://github.com/elizaos/eliza/issues/2161))."
},
"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