{ "prompt_name": "council-episodes", "category": "strategy", "date": "2025-12-29", "generated_text": "## Episode Overview (2025-12-29)\nEpisodes covered:\n- **S1E3 \u2014 \u201cThe Plugin Paradox\u201d**: Council assesses whether rapid plugin growth and high merge velocity strengthens ElizaOS ahead of v2 or risks fragmentation and degraded UX.\n- **S1E4 \u2014 \u201cThe Decentralized Paradox\u201d**: Council explores how **AI delegates** may reshape what \u201cdecentralization\u201d means in governance (Optimism context), and what design choices preserve decentralized ethos.\n- **RETRO-2025-07 \u2014 \u201cMonthly Retro: July 2025\u201d**: Retrospective on stabilization/refinement work (CLI, UI, action chaining, quality workflows), alongside persistent blockers (Windows compatibility, Twitter instability), and debate on shifting focus to **auto.fun activation** vs continued DX hardening.\n- **RETRO-2025-05 \u2014 \u201cMonthly Retro: May 2025\u201d**: Review of v1.0 release and major DX wins, contrasted with recurring reliability issues (Twitter integration, TEXT_EMBEDDING/RAG), documentation failures, and community trust/transparency concerns.\n\n---\n\n## Key Strategic Themes\n- **Controlled extensibility vs ecosystem fragmentation**\n - Rapid plugin proliferation is seen as both a growth engine (more use cases) and a risk (signal-to-noise decline, inconsistent UX).\n - Emerging need for clearer \u201cfoundational vs optional\u201d delineation: infrastructure primitives (persistence, caching, adapters) vs long-tail integrations.\n\n- **Reliability as a strategic moat (not just QA)**\n - Across retros, recurring integration fragility (especially **Twitter/X**) and platform-specific issues (notably **Windows**) are framed as adoption blockers and ecosystem fragility.\n - Multiple discussions converge on defining and measuring \u201creliability\u201d with explicit metrics rather than slogans.\n\n- **Platform dependency and ecosystem sovereignty**\n - Twitter/X instability and policy changes highlight a structural vulnerability: agents tethered to centralized platforms create single points of failure.\n - Strategic direction favors diversification and abstraction layers to reduce dependency without abandoning critical channels abruptly.\n\n- **AI delegates and hybrid governance design**\n - Decentralization is treated as **multidimensional** (control, diversity of implementations, transparency).\n - The council trends toward **hybrid governance** models: AI delegates scale participation and proposal throughput, with human override and accountability structures.\n\n- **Adoption flywheel: developer experience \u2192 stable deployments \u2192 compelling demos**\n - Retros emphasize that technical capability must be translated into repeatable, successful user journeys (onboarding, deployment, working integrations).\n - auto.fun is repeatedly positioned as the proving ground for real-world agent utility once stability is achieved.\n\n---\n\n## Important Decisions / Insights\n- **\u201cThe Plugin Paradox\u201d (S1E3)**\n - Strategic insight: plugin growth is acceptable\u2014even desirable\u2014if integrations are **purposeful** and paired with foundational infrastructure.\n - Identified infrastructure work (DB adapters, agent persistence, caching, multilingual TTS) as coherence-building, not random expansion.\n - Explicit risk acknowledged: fragmentation and declining signal-to-noise require stewardship (implied need for standards/curation).\n\n- **\u201cThe Decentralized Paradox\u201d (S1E4)**\n - Strategic position: AI delegates are not inherently centralizing or decentralizing; impact depends on:\n - **Diversity of delegate implementations**\n - **Decentralized / community-validated training data**\n - **Governance mechanisms** that include human oversight\n - Concrete governance design suggestion: **two-tier voting**\n - AI delegates can draft/propose at scale\n - Humans retain override (\u201ctrust but verify\u201d)\n\n- **RETRO-2025-07 (July 2025)**\n - Priority consensus: stabilize **Windows compatibility** and **Twitter plugin** first to stop user churn; then push auto.fun activation.\n - Measurable targets articulated:\n - 90% reduction in Windows-related support issues\n - Twitter plugin stable for 30 consecutive days\n - 50+ active 24/7 agents on auto.fun and 10+ showcased interactions\n - Architectural insight: platform dependency isn\u2019t just a bug\u2014signals need for platform independence strategy.\n\n- **RETRO-2025-05 (May 2025)**\n - Direction set: shift from feature expansion to **reliability + docs + transparency**\n - Key insight: internal tooling shipped well; external integrations failed repeatedly \u2192 abstraction layers and integration hardening needed.\n - Reputational risk called out: \u201cmost reliable\u201d positioning must be backed by explicit reliability metrics; otherwise credibility erodes.\n\n---\n\n## Community Impact (ElizaOS ecosystem)\n- **Builders gain power, but need guardrails**\n - Rapid plugin and PR velocity increases community contribution and use-case coverage, but raises the need for:\n - plugin quality standards\n - curated \u201crecommended\u201d stacks\n - documentation that keeps pace\n\n- **User trust is now tied to operational excellence**\n - Persistent Twitter instability, RAG/embedding issues, and doc gaps directly damage onboarding and retention; community is increasingly sensitive to mismatches between claims and reality.\n\n- **Governance discourse is maturing toward hybrid participation**\n - The AI delegate discussions suggest an evolution in how communities may scale governance without collapsing into monoculture:\n - multiple delegate \u201cclients\u201d\n - transparent reasoning\n - accountable incentive structures\n - human constitutional control\n\n- **auto.fun as the public proof layer**\n - Strategic narrative emerging: once reliability is solved, auto.fun becomes the demonstration surface where \u201cagents that work\u201d translate to adoption, community energy, and economic activity.\n\n---\n\n## Action Items (Next Steps Mentioned or Implied)\n- **Plugin ecosystem stewardship**\n - Define plugin standards (interfaces, versioning expectations, quality gates) and differentiate:\n - \u201ccore/foundational\u201d plugins\n - \u201cexperimental/edge\u201d integrations\n - Improve discoverability/curation to counter signal-to-noise degradation.\n\n- **Reliability and platform stabilization (high priority)**\n - Continue focused work on:\n - **Windows compatibility** (mainstream adoption blocker)\n - **Twitter/X integration stability** (ecosystem fragility)\n - **Embedding/RAG reliability** (agent intelligence foundation)\n - Establish and publish reliability KPIs (e.g., \u201c30 days without critical integration failures\u201d).\n\n- **Developer onboarding as a measurable funnel**\n - Close doc gaps and ensure end-to-end onboarding:\n - goal: \u201czero to deployed agent in under 30 minutes\u201d (from July retro)\n - Treat docs/search and examples as production infrastructure.\n\n- **Governance design for AI delegates (Optimism context)**\n - Encourage ecosystem diversity:\n - multiple delegate implementations\n - decentralized/community-validated datasets\n - Pilot hybrid mechanisms:\n - AI proposal tier + human override tier\n - transparency requirements for delegate reasoning and training provenance\n\n- **auto.fun activation (sequenced after stabilization)**\n - Showcase working, compelling always-on agents to provide community \u201cwins\u201d worth sharing.\n - Track success via active agents and demonstrated interactions (not just commit volume).", "source_references": [ "2025-12-29\n---\n2025-12-28.md\n---\n# elizaOS Discord - 2025-12-28\n\n## Overall Discussion Highlights\n\n### Cloud Marketplace Development\n- **Major Technical Breakthrough**: Shaw announced running cloud services on both Jeju and Babylon platforms\n- **Decentralized Vercel Alternative**: The system functions as a compute marketplace that automatically selects optimal resources\n- **Key Components**: Includes agents, inference capabilities, DNS services, distributed cache, and SQLite database with Upstash/Neon compatibility\n- **Value Proposition**: 40% reduction in cloud bills for web2 developers, with monetization through tokenization and network fees\n\n### Project Affiliations & Ecosystem\n- Clarification that Zora is not officially affiliated with elizaOS (unlike Spartan)\n- Discussion about projects labeled \"by elizaOS\" causing confusion about official relationships\n\n### Migration Issues\n- Multiple users reported problems with the migration process\n- Issues included wallet connection problems, token exchange limitations, and \"max amount reached\" errors\n- Support staff actively directed users to dedicated support channels\n\n## Key Questions & Answers\n\n**Q: Is Zora officially from elizaOS like Spartan?** \nA: \"Not official. Just random Koreans farming\" (answered by Diamondhandwhiteboy)\n\n**Q: Do you offer SLAs for the cloud marketplace? How good are they?** \nA: \"I do not, but providers can\" (answered by Shaw)\n\n## Community Help & Collaboration\n\n1. **Migration Support**\n - Omid Sa directed Fataliti to the support channel for migration questions\n - Borko helped \u0411\u0438\u0437\u043d\u0435\u0441 \u0413\u0443\u0441\u044c with questions about exchanging coins for Eliza\n - The Light assisted Emma with her \"max amount reached error\" issue\n\n2. **Technical Inspiration**\n - Sayonara shared POKT Network's poktroll GitHub repository with Shaw as potential inspiration for the cloud marketplace development\n\n## Action Items\n\n### Technical\n- Fix \"max amount reached error\" when users have large amounts of AI16Z (Mentioned by Emma)\n- Address issue with coins being visible but not exchangeable when connecting Phantom wallet (Mentioned by Fataliti)\n- Explore integration possibilities with POKT Network's poktroll (Mentioned by Sayonara)\n- Implement provider SLA capabilities in the cloud marketplace (Mentioned by Shaw)\n\n### Documentation\n- Create clear instructions for migration process beyond Ledger support (Mentioned by \u0411\u0438\u0437\u043d\u0435\u0441 \u0413\u0443\u0441\u044c)\n- Clarify official relationship between elizaOS and projects labeled \"by elizaOS\" (Mentioned by dududon1)\n---\n2025-12-27.md\n---\n# elizaOS Discord - 2025-12-27\n\n## Overall Discussion Highlights\n\n### Token Migration & Tokenomics\n- Users reported issues with AI16z token migration, including \"max amount reached\" errors\n- Only tokens held during a specific snapshot are eligible for migration; newly purchased tokens cannot be migrated\n- DorianD raised concerns about the project's tokenomics strategy, questioning whether ElizaOS would be the native token for the Jeju system\n- Borko indicated that token plans exist but are not being shared externally yet\n\n### Technical Development\n- **Jeju Platform**: Shaw revealed an ambitious distributed cloud platform called \"jeju\" that:\n - Is fully distributed and compatible with Vercel AI SDK, Kubernetes+Helm, S3, Redis+Upstash, and serverless SQLite\n - Uses Trusted Execution Environments (TEE) with protection against side-channel attacks\n - Combines proof-of-cloud and key sharding with a distributed KMS similar to lit protocol\n - Will have \"eliza cloud\" running on it\n\n- **Distributed SQLite**: Shaw is developing a distributed SQLite database needing a name (proposed options: \"sqlit\", \"sqliite\", \"ShawQLite\", \"sq-lit\")\n\n- **Agent Creation Issues**: DorianD reported problems when creating agents with specific names:\n - Names like \"null\" or numeric values (\"1\", \"69\", \"666\") either didn't save properly or caused client-side exceptions\n - \"null\" agents could be edited in the dashboard, but numeric-named agents produced application errors\n - An agent named \"$\" worked normally\n\n- **Streaming Functionality**: Sayonara added streaming functionality to a component but noted UI issues with multistep interactions compared to \"otaku\"\n\n### Community & Projects\n- A project called Zoria has \"bonded\" and is identified as an Eliza Cloud project\n- Community members discussed the importance of projects identifying themselves as built on \"elizaos cloud\" to help with distribution\n- Users requested access to Eliza Cloud API endpoints, which Odilitime confirmed are available on the site\n\n## Key Questions & Answers\n\n**Token Migration**\n- Q: What does 'max amount reached' mean on the migrator? \n A: It means that wallet is not in the snapshot. (Odilitime)\n\n- Q: Are we limited on migration to the amount we had in wallet at the time? \n A: As a policy we're not migrating any purchases after snapshot. (Odilitime)\n\n- Q: Is newly-purchased $ai16z eligible for migration ever? \n A: As a policy we're not migrating any purchases after snapshot. (Odilitime)\n\n**Development**\n- Q: Where can I find Eliza Cloud API endpoints? \n A: They're there on the site. (Odilitime)\n\n- Q: What would be a good name for a distributed SQLite database? \n A: \"ShawQLite\" or \"sq-lit\" were suggested. (sayonara)\n\n## Community Help & Collaboration\n\n1. **Token Migration Support**\n - Helper: Odilitime | Helpee: yikesawjeez\n - Context: User was confused about \"max amount reached\" error during token migration\n - Resolution: Explained it means the wallet wasn't in the snapshot and directed user to the appropriate channel for more information\n\n2. **Wallet Connection Issues**\n - Helper: Omid Sa | Helpee: Tengev\n - Context: User couldn't see AI16z tokens after connecting Phantom wallet to migration site\n - Resolution: Directed user to another channel for assistance\n\n3. **Agent Naming Bug Report**\n - Helper: DorianD | Helpee: Community\n - Context: Identified bug with agent naming restrictions\n - Resolution: Discovered that \"null\" and numeric values cause errors when used as agent names, while \"$\" works normally\n\n4. **UI Improvement Collaboration**\n - Helper: sayonara | Helpee: Stan \u26a1\n - Context: Added streaming functionality with UI issues for multistep compared to \"otaku\"\n - Resolution: Stan committed to checking how otaku shows things to improve client chat\n\n## Action Items\n\n### Technical\n- Fix bug where agent names \"null\" or numeric values cause application errors (DorianD)\n- Resolve ECR credentials error during deployment with elizaos deploy command (DorianD)\n- Test the streaming functionality added to component (sayonara)\n- Improve client chat UI for multistep interactions by examining \"otaku\" implementation (Stan \u26a1)\n- Continue development of distributed SQLite database (shaw)\n- Develop \"jeju\" distributed cloud platform compatible with multiple technologies (shaw)\n\n### Documentation\n- Provide clearer access to Eliza Cloud API endpoints (Zoopdrop)\n- Create a dedicated sub-channel for Eliza Cloud projects (MDMnvest)\n- Develop clearer documentation on token utility and how ElizaOS integrates with the project's infrastructure (DorianD)\n- Provide information about migration eligibility criteria and snapshot details (yikesawjeez)\n- Investigate why description field allows empty values despite being required at view level (DorianD)\n\n### Feature\n- Implement identification system for projects built on elizaos cloud to improve community distribution (satsbased)\n- Consider implementing a clearer tokenomics model where the native token is essential to the system's operation (DorianD)\n---\n2025-12-26.md\n---\n# elizaOS Discord - 2025-12-26\n\n## Overall Discussion Highlights\n\n### Project Status & Token Performance\n- ElizaOS is transitioning from a meme coin (AI16Z) to a utility-focused platform\n- Token price has declined 90-98% from ATH, causing investor frustration\n- Top 10 token holders decreased from 89% to 64% of total supply\n- Team is working to regain their X (Twitter) account, considered critical for marketing\n- Community sentiment is mixed - some maintain faith in technical merits while others question token value\n\n### ElizaOS Cloud Development\n- ElizaOS Cloud platform has launched, allowing developers to build and deploy AI agents\n- Several users shared examples of agents created on the platform\n- Some users reported deployment errors (username null error)\n- File upload optimization for agents is currently in development\n- Discussions about implementing a custom SSO solution to unify authentication\n\n### Jeju Network\n- Project appears focused on decentralized hosting and autonomous agents\n- Questions raised about whether Jeju network's token will be $elizaOS\n- A previously mentioned \"life-changing event\" expected around October is still pending\n\n### Technical Issues\n- Streaming functionality broken in the core due to wrong dependencies\n- Multiple PRs in progress to fix issues and improve code quality\n- Some users experiencing application errors when logging into ElizaCloud\n- Issues with Ollama model configuration for agents\n\n## Key Questions & Answers\n\n**Q: Why is ElizaOS token price continuously dropping?** \nA: Multiple factors including team management issues, whale manipulation, and lack of X (Twitter) presence for marketing.\n\n**Q: What happened with the token migration from AI16Z to ElizaOS?** \nA: The migration used a snapshot approach which split liquidity and caused confusion, especially for exchange users.\n\n**Q: How is ElizaOS Cloud being used?** \nA: Developers are building AI agents on it, with examples like a marijuana-themed agent and other projects being shared.\n\n**Q: Is the ElizaOS project dead?** \nA: No, development continues with ElizaOS Cloud gaining users despite token price issues.\n\n**Q: What's the difference between the project's technical merits and token value?** \nA: The token can be a bad investment while the technology/project remains valuable.\n\n**Q: Is it possible to upload multiple MD files for an agent?** \nA: Multiple files should work, and file upload optimization is currently in progress.\n\n**Q: Is one of the goals of Jeju for the agents to be truly decentralized and unstoppable?** \nA: Yes, decentralized hosting and agents are very much at the heart of the project.\n\n**Q: Can I plug in an AI agent to help me edit videos in DaVinci Resolve Studio?** \nA: Not directly yet; suggested workaround is to use Gemini's screen share capability for guidance.\n\n**Q: Is it possible to use npm instead of bun?** \nA: No, users need to continue using bun.\n\n## Community Help & Collaboration\n\n- **The Light** shared multiple examples of successful ElizaCloud deployments to encourage **DorianD** who was experiencing login errors\n- **Biazs** explained to **Serikiki** that significant price recovery is possible even after 90% drops at small market caps\n- **sayonara** suggested using Gemini screen share as an alternative for **Irie_Rubz** who wanted AI assistance with DaVinci Resolve, providing a YouTube link\n- **Odilitime** confirmed to **FenrirFawks** that their Ollama model configuration variable was correct and shared relevant GitHub code\n- **satsbased** suggested using the #build-showcase channel for community members to share their ElizaCloud projects\n\n## Action Items\n\n### Technical\n- Fix application errors when logging into ElizaCloud (DorianD)\n- Implement custom SSO solution to unify authentication and identity (Odilitime)\n- Fix OpenAI streaming functionality (PR #22) (Stan \u26a1)\n- Clean up code, fix issues, and add missing tests (PR #6285) (Stan \u26a1)\n- Address unspecified changes in PR #6286 (sayonara)\n- Fix plugin issues with parsing points and unruggable SDK (FenrirFawks)\n- Resolve agent deployment error with username null (DorianD)\n- Optimize file uploads for agents (Borko)\n- Improve exchange communication for token migrations (averma)\n- Regain X (Twitter) account to improve marketing (satsbased)\n- Develop truly decentralized agents for Jeju network (DorianD)\n\n### Documentation\n- Provide clearer documentation on token utility and value proposition (Alexei)\n- Create better guides for exchanges during migrations (Alexei)\n- Clarify whether Jeju network's token will be $elizaOS (DorianD)\n- Provide updates on the previously mentioned \"life-changing event\" (sayitaintso25)\n\n### Feature\n- Create a process for ElizaCloud developers to showcase their projects (satsbased)\n- Consider Instagram presence to reach younger crypto investors (Alexei)\n- Develop a sentiment analysis AI agent to monitor community feedback (The Light)\n- Integrate AI assistance with DaVinci Resolve (Irie_Rubz)\n---\n2025-12-28.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-12-28\n---\nElizaOS Discord Activity Summary - December 28, 2025\n---\nThe ElizaOS Discord was active with various discussions across different channels. In the general discussion channel, users were talking about staking for passive income, token liquidity comparisons between Spartan and ElizaOS, and questions about migration support. Several users needed help with exchanging coins and were directed to the support channel (#1425417640071139358).\n---\nhttps://discord.com/channels/1253563208833433701/1253563209462448241\n---\nThere was debate about whether certain projects (like Zora) were officially affiliated with ElizaOS, with some confusion about projects labeled as 'by ElizaOS'. Community members clarified that these are projects built on ElizaOS but not necessarily official projects.\n---\nhttps://discord.com/channels/1253563208833433701/1253563209462448241\n---\nIn the partners channel, a developer shared excitement about a trading bot they're developing, mentioning it could 'bulldoze spot markets in the right conditions' and referencing complexity-science informed bayesian inference technology.\n---\nhttps://discord.com/channels/1253563208833433701/1301363808421543988\n---\nThe core-devs channel featured an important technical discussion where Shaw (a core developer) announced a significant development: cloud running on Jeju and Babylon. He described it as a decentralized alternative to Vercel - a compute marketplace that automatically selects the cheapest and fastest compute resources based on needs. The system includes agents, inference capabilities, DNS, domain purchasing, and uses distributed cache and SQLite DB compatible with Upstash and Neon. While app builders pay for what they run, the system offers approximately 40% reduced cloud bills compared to traditional solutions.\n---\nhttps://discord.com/channels/1253563208833433701/1377726087789940836\n---\ndiscordrawdata\n---\nelizaos/eliza GitHub Activity (Dec 28-29, 2025)\n---\nBetween December 28-29, 2025, the elizaos/eliza repository showed minimal activity with no new pull requests (0 merged), no new issues, and only 1 active contributor during this period.\n---\ntext\n---\ngithub_summary\n---\nTop Contributors for elizaOS/eliza\n---\nThe provided source only mentions 'Top contributors for elizaOS/eliza' without providing any specific details about who these contributors are or what contributions they have made to the elizaOS/eliza project. Without additional information, it's not possible to provide a detailed summary of the top contributors, their contributions, or their impact on the project.\n---\ntext: Top contributors for elizaOS/eliza\n---\ncontributors\n---\n2025-12-28.md\n---\n# ElizaOS Discord Activity Summary - December 28, 2025\n\n## General Discussion Channel\n- Users discussed staking for passive income\n- Token liquidity comparisons between Spartan and ElizaOS\n- Questions about migration support\n- Users seeking help with coin exchanges were directed to support channels\n\n## Project Clarifications\n- Community members clarified that projects labeled \"by ElizaOS\" are built on ElizaOS but not necessarily official projects\n\n## Partners Channel\n- Developer shared progress on a trading bot development\n- Bot features complexity-science informed bayesian inference technology\n- Developer noted it could \"bulldoze spot markets in the right conditions\"\n\n## Core-Devs Channel\n- Shaw (core developer) announced cloud running on Jeju and Babylon\n- Described as a decentralized alternative to Vercel\n- Functions as a compute marketplace that automatically selects optimal resources\n- System includes:\n - Agents and inference capabilities\n - DNS and domain purchasing\n - Distributed cache\n - SQLite DB compatible with Upstash and Neon\n- Offers approximately 40% reduced cloud bills compared to traditional solutions\n\n# GitHub Activity (Dec 28-29, 2025)\n- 1 active contributor during this period\n---\n2025-12-28.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-12-28\n---\n1253563209462448241\n---\n\ud83d\udcac-discussion\n---\n# Analysis of \ud83d\udcac-discussion Discord Channel\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation primarily revolves around questions about Eliza OS and related projects, with users seeking clarification on whether certain projects (particularly Zora) are officially affiliated with Eliza OS. There are questions about migration issues, with users experiencing problems connecting wallets and exchanging tokens. Several users direct people with migration questions to what appears to be a dedicated support channel. The chat also includes casual greetings, brief market commentary, and some off-topic banter. No substantial technical discussions, decisions, or problem-solving occurred in this segment.\n\n## 2. FAQ\nQ: Is Zora officially from Eliza OS like Spartan? (asked by dududon1) A: Not official. Just random Koreans farming (answered by Diamondhandwhiteboy)\nQ: How do I exchange coins for Eliza? The migration website only has Ledger. (asked by \u0411\u0438\u0437\u043d\u0435\u0441 \u0413\u0443\u0441\u044c) A: Unanswered\nQ: I have a huge amount of AI16Z, and I am getting max amount reached error. (asked by Emma) A: Unanswered\nQ: Where is the branch for migration questions? Who should I contact? When connecting to the Phantom on the website, the coins are visible and cannot be exchanged. (asked by Fataliti) A: Unanswered\n\n## 3. Help Interactions\nHelper: Omid Sa | Helpee: Fataliti | Context: User asking about migration questions and contact for support | Resolution: Directed to what appears to be a support channel\nHelper: Borko | Helpee: \u0411\u0438\u0437\u043d\u0435\u0441 \u0413\u0443\u0441\u044c | Context: User asking how to exchange coins for Eliza | Resolution: Directed to what appears to be a support channel\nHelper: The Light | Helpee: Emma | Context: User experiencing \"max amount reached error\" with AI16Z | Resolution: Directed to what appears to be a support channel\n\n## 4. Action Items\nTechnical: Fix \"max amount reached error\" when users have large amounts of AI16Z | Mentioned By: Emma\nTechnical: Address issue with coins being visible but not exchangeable when connecting Phantom wallet | Mentioned By: Fataliti\nDocumentation: Create clear instructions for migration process beyond Ledger support | Mentioned By: \u0411\u0438\u0437\u043d\u0435\u0441 \u0413\u0443\u0441\u044c\nDocumentation: Clarify official relationship between Eliza OS and projects labeled \"by Eliza OS\" | Mentioned By: dududon1\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\nThe chat segment is extremely brief and contains no substantive technical discussion, problem-solving, or implementation details. The user \"yikesawjeez\" made three messages that reference a trading bot and mentions concepts like \"complexity-science informed bayesian inference over KL divergence in complex dynamical systems\" but explicitly states this is \"intentional obfuscation.\" No actual technical details, decisions, or concrete solutions were shared in this limited exchange.\n---\n1377726087789940836\n---\ncore-devs\n---\n# Discord Chat Analysis - \"core-devs\" Channel\n\n## 1. Summary\nShaw shared a significant technical breakthrough: running cloud services on both Jeju and Babylon platforms. He conceptualizes this as a decentralized, on-chain alternative to Vercel. The system functions as a compute marketplace that automatically selects the most cost-effective and efficient compute resources based on user requirements. Key technical components include agents, inference capabilities, DNS and domain purchasing services, a distributed cache, and a SQLite database with Upstash and Neon compatibility. The blockchain element enables permissionless access and creates a marketplace abstraction over cloud providers. Shaw positions the value proposition as a 40% reduction in cloud bills for web2 developers, while also offering monetization opportunities through tokenization and network fees. Sayonara suggested examining POKT Network's poktroll GitHub repository for potential ideas to incorporate.\n\n## 2. FAQ\nQ: Do you offer SLAs? How good are they? (asked by Odilitime) A: I do not, but providers can (answered by shaw)\n\n## 3. Help Interactions\nHelper: sayonara | Helpee: shaw | Context: Sharing relevant project for comparison/inspiration | Resolution: Provided GitHub link to poktroll repository for potential idea borrowing\n\n## 4. Action Items\nTechnical: Explore integration possibilities with POKT Network's poktroll | Description: Evaluate if concepts from this project can be borrowed for the cloud marketplace | Mentioned By: sayonara\nTechnical: Implement provider SLA capabilities | Description: Enable cloud providers to offer service level agreements within the marketplace | Mentioned By: shaw\n---\n2025-12-28.md\n---\n# elizaOS Discord - 2025-12-28\n\n## Overall Discussion Highlights\n\n### Cloud Marketplace Development\n- **Major Technical Breakthrough**: Shaw announced running cloud services on both Jeju and Babylon platforms\n- **Decentralized Vercel Alternative**: The system functions as a compute marketplace that automatically selects optimal resources\n- **Key Components**: Includes agents, inference capabilities, DNS services, distributed cache, and SQLite database with Upstash/Neon compatibility\n- **Value Proposition**: 40% reduction in cloud bills for web2 developers, with monetization through tokenization and network fees\n\n### Project Affiliations & Ecosystem\n- Clarification that Zora is not officially affiliated with elizaOS (unlike Spartan)\n- Discussion about projects labeled \"by elizaOS\" causing confusion about official relationships\n\n### Migration Issues\n- Multiple users reported problems with the migration process\n- Issues included wallet connection problems, token exchange limitations, and \"max amount reached\" errors\n- Support staff actively directed users to dedicated support channels\n\n## Key Questions & Answers\n\n**Q: Is Zora officially from elizaOS like Spartan?** \nA: \"Not official. Just random Koreans farming\" (answered by Diamondhandwhiteboy)\n\n**Q: Do you offer SLAs for the cloud marketplace? How good are they?** \nA: \"I do not, but providers can\" (answered by Shaw)\n\n## Community Help & Collaboration\n\n1. **Migration Support**\n - Omid Sa directed Fataliti to the support channel for migration questions\n - Borko helped \u0411\u0438\u0437\u043d\u0435\u0441 \u0413\u0443\u0441\u044c with questions about exchanging coins for Eliza\n - The Light assisted Emma with her \"max amount reached error\" issue\n\n2. **Technical Inspiration**\n - Sayonara shared POKT Network's poktroll GitHub repository with Shaw as potential inspiration for the cloud marketplace development\n\n## Action Items\n\n### Technical\n- Fix \"max amount reached error\" when users have large amounts of AI16Z (Mentioned by Emma)\n- Address issue with coins being visible but not exchangeable when connecting Phantom wallet (Mentioned by Fataliti)\n- Explore integration possibilities with POKT Network's poktroll (Mentioned by Sayonara)\n- Implement provider SLA capabilities in the cloud marketplace (Mentioned by Shaw)\n\n### Documentation\n- Create clear instructions for migration process beyond Ledger support (Mentioned by \u0411\u0438\u0437\u043d\u0435\u0441 \u0413\u0443\u0441\u044c)\n- Clarify official relationship between elizaOS and projects labeled \"by elizaOS\" (Mentioned by dududon1)\n---\n2025-12-29.md\n---\nFile not found\n---\n2025-12-21.md\n---\n# 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)).\n---\n2025-12-01.md\n---\n# 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)).\n---\n{\n \"interval\": {\n \"intervalStart\": \"2025-12-01T00:00:00.000Z\",\n \"intervalEnd\": \"2026-01-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-12-01 to 2026-01-01, elizaos/eliza had 30 new PRs (16 merged), 60 new issues, and 22 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs7V2Buf\",\n \"title\": \"Where did packages/docs/ go?\",\n \"author\": \"LinuxIsCool\",\n \"number\": 6122,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"There was always packages/docs/ where did it get moved to?\",\n \"createdAt\": \"2025-11-04T18:08:54Z\",\n \"closedAt\": \"2025-12-01T14:35:46Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 2\n },\n {\n \"id\": \"I_kwDOMT5cIs7cPNBC\",\n \"title\": \".eliza needed or plugin-sql crashes, should autocreate\",\n \"author\": \"lalalune\",\n \"number\": 6204,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"You can see here, I am building an Eliza agent from scratch\\n\\n```\\nimport { AgentRuntime, type Character, type Plugin } from \\\"@elizaos/core\\\";\\nimport { plugin } from \\\"@elizaos/plugin-sql\\\"\\nimport { openaiPlugin } from \\\"@elizaos/plugin-openai\\\"\\nimport fs from \\\"fs\\\";\\n\\n// if .eliza directory does not exist, create it\\nif (!fs.existsSync(\\\".eliza\\\")) {\\n fs.mkdirSync(\\\".eliza\\\");\\n}\\n\\nconst character: Character = {\\n name: \\\"Eliza\\\",\\n bio: \\\"You are a helpful assistant\\\",\\n};\\n\\nconst plugins: Plugin[] = [\\n plugin,\\n openaiPlugin,\\n];\\n\\nconst agent = new AgentRuntime({\\n character, // need a character to start the agent\\n plugins // bare minimum is db plugin and inference plugin\\n});\\n\\nagent.initialize().then(() => {\\n console.log(\\\"Agent initialized\\\");\\n\\n\\n});\\n```\\n\\nIn order to get it to work I have to add\\n```\\nimport fs from \\\"fs\\\";\\n\\n// if .eliza directory does not exist, create it\\nif (!fs.existsSync(\\\".eliza\\\")) {\\n fs.mkdirSync(\\\".eliza\\\");\\n}\\n```\\n\\nBut this should happen automatically\",\n \"createdAt\": \"2025-12-04T14:37:44Z\",\n \"closedAt\": \"2025-12-08T13:17:08Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 1\n },\n {\n \"id\": \"I_kwDOMT5cIs7cwyy7\",\n \"title\": \"Snapshot Eligibility Issue + Tangem Wallet Connection Not Supported (Discord Support Compromised)\",\n \"author\": \"pereslavlland\",\n \"number\": 6211,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"Hi ElizaOS team,\\n\\nI\u2019m trying to complete the AI16Z \u2192 ElizaOS migration, but I\u2019m running into two major issues and Discord support has become unreliable due to impersonators. I need help from the real development team to determine the correct path.\\n\\nMy situation:\\n\\n\u2022 I purchased AI16Z tokens on Oct 26 using my Phantom wallet.\\n\u2022 I then moved them to my Tangem wallet for safety.\\n\u2022 On Nov 11 (snapshot date), the tokens were held inside my Tangem wallet.\\n\u2022 The migration portal shows my Phantom wallet as \u201c0 eligible\u201d (expected since Phantom didn\u2019t hold them during snapshot).\\n\u2022 I cannot connect my Tangem wallet to the migration portal because WalletConnect does not support Tangem.\\n\u2022 My Tangem wallet was created using key cards only, so I do not have a seed phrase to export into Phantom.\\n\\nThe Discord server is currently compromised \u2014 multiple impersonators posing as support are entering tickets and attempting to direct users to send tokens manually. Because of this, I cannot rely on Discord support or email responses that appear to be spoofed.\\n\\nWhat I need from the real team:\\n\\nConfirmation of whether Tangem-held tokens during the snapshot are eligible for migration.\\nWhether a manual backend whitelist update is possible so my Phantom wallet can perform migration safely.\\nIf not, what the official and safe method is for users whose eligible snapshot wallet cannot connect to the portal (Tangem case).\\nAny announcements regarding potential whitelist updates or support for non-exportable wallets.\\nI have NOT sent my tokens anywhere and I have NOT interacted with any unofficial links. My tokens are safe. I\u2019m only seeking official guidance from the verifiable team here on GitHub.\\n\\nThank you \u2014 I appreciate your time. I prefer to resolve this safely through GitHub to avoid Discord impersonation issues.\\n\\nActivity\\n\",\n \"createdAt\": \"2025-12-07T18:00:25Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 1\n },\n {\n \"id\": \"I_kwDOMT5cIs7f1hdp\",\n \"title\": \"Create Agent Button should be same in My Agents and Dashboard\",\n \"author\": \"borisudovicic\",\n \"number\": 6274,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"\",\n \"createdAt\": \"2025-12-22T22:00:52Z\",\n \"closedAt\": \"2025-12-23T14:53:55Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 1\n },\n {\n \"id\": \"I_kwDOMT5cIs7f1hHH\",\n \"title\": \"Move avatar button to #4 in agent builder\",\n \"author\": \"borisudovicic\",\n \"number\": 6273,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"\",\n \"createdAt\": \"2025-12-22T22:00:19Z\",\n \"closedAt\": \"2025-12-23T14:53:55Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 1\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs64E0uE\",\n \"title\": \"Eliza Cloud Integration, add MCP + A2A service starter, integrate CLI and starter projects tight\",\n \"author\": \"lalalune\",\n \"number\": 6216,\n \"body\": \"The goal of this PR is to tightly integrate the elizaos cloud plugin, which now can use cloud as a db and storage provider, and encourage users through the CLI to get up and running with elizaos cloud. CLI should auto log them in, provision API key and make sure project is set up.\\r\\n\\r\\nPlease thoroughly review and understand the create -> deploy -> publish and monetize flow, may still need some work\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-12-10T07:26:45Z\",\n \"mergedAt\": null,\n \"additions\": 9989,\n \"deletions\": 101\n },\n {\n \"id\": \"PR_kwDOMT5cIs630tVJ\",\n \"title\": \"Shaw/chore/deslop\",\n \"author\": \"lalalune\",\n \"number\": 6213,\n \"body\": \"This PR removes a lot of slop\\r\\n\\r\\n- Fixes any and unknown and cast types with real types\\r\\n- Removes try catch\\r\\n- Removes sloppy comments\\r\\n- Removes dead files and code\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-12-09T03:59:26Z\",\n \"mergedAt\": \"2025-12-09T06:22:34Z\",\n \"additions\": 9246,\n \"deletions\": 7105\n },\n {\n \"id\": \"PR_kwDOMT5cIs64kuni\",\n \"title\": \"Main\",\n \"author\": \"DevGruGold\",\n \"number\": 6220,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\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\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-12-12T14:04:11Z\",\n \"mergedAt\": null,\n \"additions\": 6952,\n \"deletions\": 840\n },\n {\n \"id\": \"PR_kwDOMT5cIs620Si3\",\n \"title\": \"feat(auth): implement JWT authentication and user management\",\n \"author\": \"standujar\",\n \"number\": 6200,\n \"body\": \"## Relates to\\r\\n\\r\\n- Data isolation / multi-entity support\\r\\n- External JWT provider integration (Privy, Auth0, Clerk, Supabase, Google, Embbeded)\\r\\n\\r\\n## Risks\\r\\n\\r\\n**Low**\\r\\n\\r\\n- Requires `ENABLE_DATA_ISOLATION=true` to activate JWT auth mode\\r\\n\\r\\n## Background\\r\\n\\r\\n### What does this PR do?\\r\\n\\r\\nImplements a complete JWT authentication system for ElizaOS with support for multiple verification strategies:\\r\\n\\r\\n1. **JWT Verifier Factory** - Priority-based verifier selection:\\r\\n - Ed25519 (highest priority) - For self-signed JWTs with Ed25519 keys\\r\\n - JWKS (medium priority) - For external providers (Auth0, Clerk, Privy, Supabase, Google)\\r\\n - Secret (lowest priority) - For simple HS256 symmetric key verification\\r\\n\\r\\n2. **Entity ID derivation from JWT `sub` claim**:\\r\\n - `entityId = stringToUuid(payload.sub)`\\r\\n - Compatible with ANY JWT provider since `sub` is a standard claim\\r\\n - No custom claims needed in external JWTs\\r\\n\\r\\n3. **Dual authentication modes**:\\r\\n - `ENABLE_DATA_ISOLATION=true` \u2192 JWT authentication required\\r\\n - `ENABLE_DATA_ISOLATION=false` \u2192 X-Entity-Id header (legacy mode)\\r\\n\\r\\n4. **Internal service bypass** - Process-local UUID secret for service-to-service calls\\r\\n\\r\\n5. **Credentials-based auth endpoints** (`/api/auth/*`) - only in custom - JWT-SECRET mode:\\r\\n - `POST /register` - User registration with bcrypt password hashing\\r\\n - `POST /login` - User login with JWT generation\\r\\n - `POST /refresh` - Token refresh\\r\\n - `GET /me` - Current user info\\r\\n\\r\\n6. **Client UI default implementation using self mode (Secret)\\r\\n\\r\\n### What kind of change is this?\\r\\n\\r\\n**Features** (non-breaking change which adds functionality)\\r\\n\\r\\n## Architecture\\r\\n\\r\\n```\\r\\n\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\\r\\n\u2502 JWT Verification Flow \u2502\\r\\n\u251c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\\r\\n\u2502 Request with Bearer token \u2502\\r\\n\u2502 \u2193 \u2502\\r\\n\u2502 JWTVerifierFactory.create() \u2502\\r\\n\u2502 \u2193 \u2502\\r\\n\u2502 Priority: Ed25519 > JWKS > Secret > Disabled \u2502\\r\\n\u2502 \u2193 \u2502\\r\\n\u2502 verifier.verify(token) \u2502\\r\\n\u2502 \u2193 \u2502\\r\\n\u2502 Extract payload.sub \u2502\\r\\n\u2502 \u2193 \u2502\\r\\n\u2502 entityId = stringToUuid(sub) \u2190 Derived, NOT stored in JWT \u2502\\r\\n\u2502 \u2193 \u2502\\r\\n\u2502 req.entityId = entityId \u2502\\r\\n\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\\r\\n```\\r\\n\\r\\n## Environment Variables\\r\\n\\r\\n| Variable | Description | Example |\\r\\n|----------|-------------|---------|\\r\\n| `ENABLE_DATA_ISOLATION` | Enable JWT auth mode | `true` |\\r\\n| `JWT_SECRET` (optional) | HS256 symmetric secret | `your-secret-key` |\\r\\n| `JWT_PUBLIC_KEY_ED25519` (optional) | Ed25519 public key (base64) | `MCowBQYDK2Vw...` |\\r\\n| `JWT_JWKS_URI` (optional) | JWKS endpoint URL | `https://auth0.com/.well-known/jwks.json` |\\r\\n| `JWT_ISSUER_WHITELIST` (optional) | Allowed issuers (comma-separated) | `https://auth0.com/,https://clerk.dev` |\\r\\n\\r\\n## Documentation changes needed?\\r\\n\\r\\nYes - Documentation should be added for:\\r\\n- Environment variable configuration\\r\\n- External provider setup (Auth0, Clerk, Privy examples)\\r\\n\\r\\n## Testing\\r\\n\\r\\n### Where should a reviewer start?\\r\\n\\r\\n1. `packages/server/src/services/jwt-verifiers/factory.ts` - Core factory logic\\r\\n2. `packages/server/src/middleware/jwtMiddleware.ts` - HTTP middleware\\r\\n3. `packages/server/src/socketio/index.ts` - SocketIO authentication\\r\\n\\r\\n### Detailed testing steps\\r\\n\\r\\n**Unit Tests:**\\r\\n```bash\\r\\ncd packages/server\\r\\nbun run test:unit\\r\\n```\\r\\n\\r\\n**Integration Tests:**\\r\\n```bash\\r\\ncd packages/server\\r\\nbun run test:integration\\r\\n```\\r\\n\\r\\n**Results:** 489 unit tests pass, 6 integration test files pass\\r\\n\\r\\n### Manual Testing\\r\\n\\r\\n1. **Test with JWT_SECRET (HS256):**\\r\\n```bash\\r\\nENABLE_DATA_ISOLATION=true JWT_SECRET=test-secret bun run dev\\r\\n```\\r\\n\\r\\n2. **Register a user:**\\r\\n```bash\\r\\ncurl -X POST http://localhost:3000/api/auth/register \\\\\\r\\n -H \\\"Content-Type: application/json\\\" \\\\\\r\\n -d '{\\\"email\\\":\\\"test@example.com\\\",\\\"username\\\":\\\"testuser\\\",\\\"password\\\":\\\"password123\\\"}'\\r\\n```\\r\\n\\r\\n3. **Use returned token:**\\r\\n```bash\\r\\ncurl http://localhost:3000/api/agents \\\\\\r\\n -H \\\"Authorization: Bearer \\\"\\r\\n```\\r\\n\\r\\n## External Provider Compatibility\\r\\n\\r\\nTested JWT formats:\\r\\n- **Auth0**: `sub: \\\"auth0|1234567890\\\"`\\r\\n- **Clerk**: `sub: \\\"user_2abcdefgh123456\\\"`\\r\\n- **Google**: `sub: \\\"1234567890\\\"` with `email`, `email_verified`\\r\\n- **Supabase**: `sub: \\\"uuid\\\"` with `role: \\\"authenticated\\\"`\\r\\n- **Privy**: `sub: \\\"did:privy:...\\\"`\\r\\n\\r\\nAll providers work because we only require the standard `sub` claim.\\r\\n\\r\\n## Next Idea Steps: Access Control Layer (ACL)\\r\\n\\r\\nThe next phase will add access control on agents and rooms: \\r\\n\\r\\nAgents:\\r\\n- Each user can create their own agents (ownerId = entityId)\\r\\n- Visibility: public or private\\r\\n- Private = only the owner can chat with it\\r\\n- Public = everyone can chat, but only the owner can modify/delete\\r\\n\\r\\nRooms:\\r\\n- Each room has an owner\\r\\nOnly the owner can:\\r\\n- Delete the room (DELETE /rooms/:id)\\r\\n- Clear message history (DELETE /rooms/:id/messages)\\r\\n- Change visibility\\r\\n\\r\\nThis will enable true multi-tenant mode where each user manages their resources in isolation.\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-12-03T11:55:47Z\",\n \"mergedAt\": null,\n \"additions\": 6072,\n \"deletions\": 354\n },\n {\n \"id\": \"PR_kwDOMT5cIs64fjY5\",\n \"title\": \"Main\",\n \"author\": \"DevGruGold\",\n \"number\": 6219,\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\n\\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\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-12-12T05:13:08Z\",\n \"mergedAt\": null,\n \"additions\": 5104,\n \"deletions\": 662\n }\n ],\n \"codeChanges\": {\n \"additions\": 14208,\n \"deletions\": 6084,\n \"files\": 287,\n \"commitCount\": 206\n },\n \"completedItems\": [\n {\n \"title\": \"fix: markdown spacing compact\",\n \"prNumber\": 6159,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nFixes excessive vertical spacing in AI-generated markdown responses in the ElizaOS client UI.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low Risk**\\r\\n\\r\\n- Only CSS changes affecting markdown content rendering\\r\\n- Uses well-supported CSS features (Chrome \",\n \"files\": [\n \"packages/client/src/components/ai-elements/response.tsx\",\n \"packages/client/src/index.css\"\n ]\n },\n {\n \"title\": \"refactor(server): optimization and reorganization\",\n \"prNumber\": 6199,\n \"type\": \"refactor\",\n \"body\": \"# Risks\\r\\n\\r\\n**Low to Medium**\\r\\n\\r\\n- Socket.IO configuration changes may affect existing client connections (tested with multiple browsers)\\r\\n- Code reorganization changes import paths - all imports have been updated and verified\\r\\n\\r\\n# Backgroun\",\n \"files\": [\n \"bun.lock\",\n \"packages/server/src/__tests__/builders/channel.builder.ts\",\n \"packages/server/src/__tests__/builders/message.builder.ts\",\n \"packages/server/src/__tests__/integration/agent-server-interaction.test.ts\",\n \"packages/server/src/__tests__/integration/database-operations.test.ts\",\n \"packages/server/src/__tests__/integration/message-bus-service.test.ts\",\n \"packages/server/src/__tests__/unit/api/crud-uuid.test.ts\",\n \"packages/server/src/__tests__/unit/api/jobs.test.ts\",\n \"packages/server/src/__tests__/unit/features/socketio-router.test.ts\",\n \"packages/server/src/__tests__/unit/services/message-bus-compatibility.test.ts\",\n \"packages/server/src/__tests__/unit/utils/loader-uuid.test.ts\",\n \"packages/server/src/__tests__/unit/utils/loader.test.ts\",\n \"packages/server/src/api/index.ts\",\n \"packages/server/src/api/messaging/channels.ts\",\n \"packages/server/src/api/messaging/core.ts\",\n \"packages/server/src/api/messaging/jobs.ts\",\n \"packages/server/src/api/messaging/messageServers.ts\",\n \"packages/server/src/api/messaging/sessions.ts\",\n \"packages/server/src/api/shared/uploads/index.ts\",\n \"packages/server/src/index.ts\",\n \"packages/server/src/services/index.ts\",\n \"packages/server/src/services/loader.ts\",\n \"packages/server/src/services/message-bus.ts\",\n \"packages/server/src/services/message.ts\",\n \"packages/server/src/socketio/index.ts\",\n \"packages/server/src/types/server.ts\",\n \"packages/server/src/utils/config.ts\",\n \"packages/server/src/utils/index.ts\",\n \"packages/server/src/utils/media-transformer.ts\",\n \"packages/server/src/utils/upload.ts\"\n ]\n },\n {\n \"title\": \"fix(client): improve markdown content spacing\",\n \"prNumber\": 6197,\n \"type\": \"bugfix\",\n \"body\": \"This PR includes two fixes for markdown content spacing in the client:\\n\\n1. Add missing heading and separator spacing to markdown-content\\n2. Reduce blockquote vertical spacing for more compact display\\n\\nThese changes improve the visual consis\",\n \"files\": [\n \"packages/client/src/index.css\"\n ]\n },\n {\n \"title\": \"feat: Unified API - serverless - nodejs\",\n \"prNumber\": 6201,\n \"type\": \"feature\",\n \"body\": \"\",\n \"files\": [\n \"bun.lock\",\n \"packages/core/src/__tests__/elizaos-sendmessage.test.ts\",\n \"packages/core/src/__tests__/elizaos.test.ts\",\n \"packages/core/src/elizaos.ts\",\n \"packages/core/src/types/elizaos.ts\"\n ]\n },\n {\n \"title\": \"fix(examples): respect user LOG_LEVEL in standalone-cli-chat\",\n \"prNumber\": 6203,\n \"type\": \"bugfix\",\n \"body\": \"\",\n \"files\": [\n \"examples/standalone-cli-chat.ts\"\n ]\n },\n {\n \"title\": \"fix(plugin-sql): migrate to messageService API and auto-create PGLite directories\",\n \"prNumber\": 6202,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n\\nThis PR modernizes the standalone example files and improves the SQL plugin's directory handling by:\\n1. Migrating examples from the deprecated `MESSAGE_RECEIVED` event system to the new `messageService.handleMessage()` API\\n2. Ad\",\n \"files\": [\n \"examples/standalone-cli-chat.ts\",\n \"examples/standalone.ts\",\n \"packages/plugin-sql/src/__tests__/unit/directory-creation.test.ts\",\n \"packages/plugin-sql/src/index.node.ts\",\n \"packages/plugin-sql/src/index.ts\"\n ]\n },\n {\n \"title\": \"feat: Add ElizaOS Cloud as Default AI Provider in CLI\",\n \"prNumber\": 6208,\n \"type\": \"feature\",\n \"body\": \"## Add ElizaOS Cloud as Default AI Provider in CLI\\n\\n### Summary\\n- Add **ElizaOS Cloud** as the first/recommended option in `elizaos create` AI model selection\\n- Integrate browser-based login flow for seamless API key setup\\n- Fix env variabl\",\n \"files\": [\n \"bun.lock\",\n \"packages/cli/src/commands/create/actions/setup.ts\",\n \"packages/cli/src/commands/create/utils/selection.ts\",\n \"packages/cli/src/commands/deploy/utils/api-client.ts\",\n \"packages/cli/src/commands/login/README.md\",\n \"packages/cli/src/commands/login/actions/login.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/tests/commands/create.test.ts\",\n \"packages/cli/tests/unit/utils/elizacloud-config.test.ts\",\n \"packages/cli/tests/unit/utils/selection.test.ts\"\n ]\n },\n {\n \"title\": \"fix(cli): correct startAgents API signature in e2e-tests\",\n \"prNumber\": 6207,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\r\\n\\r\\n- Fixed `startAgents` API signature mismatch in CLI's e2e-tests.ts\\r\\n- Fixed unit test mock function name (`getElizaCharacter` \u2192 `getDefaultCharacter`)\\r\\n\\r\\n## Problem\\r\\n\\r\\nThe CLI's `elizaos test` command was failing with:\\r\\n```\\r\\nu\",\n \"files\": [\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/tests/unit/commands/test/e2e-tests.test.ts\"\n ]\n },\n {\n \"title\": \"feat: bump deps, fix drizzle-kit across ecosystem\",\n \"prNumber\": 6210,\n \"type\": \"feature\",\n \"body\": \"## \ud83d\udd04 Update All Dependencies to Latest Versions\\n\\n### Problem\\n\\nFound conflicting `drizzle-orm` versions across the monorepo causing compatibility issues:\\n\\n- `drizzle-orm@0.45.0` (root)\\n- `drizzle-orm@0.44.7` (from `@elizaos/plugin-sql`)\\n- `\",\n \"files\": [\n \".github/workflows/cli-tests.yml\",\n \".github/workflows/client-cypress-tests.yml\",\n \".github/workflows/jsdoc-automation.yml\",\n \".github/workflows/release.yaml\",\n \".github/workflows/tauri-ci.yml\",\n \".github/workflows/update-news.yml\",\n \"bun.lock\",\n \"package.json\",\n \"packages/api-client/package.json\",\n \"packages/app/package.json\",\n \"packages/cli/package.json\",\n \"packages/cli/tests/commands/agent.test.ts\",\n \"packages/cli/tests/commands/create.test.ts\",\n \"packages/cli/tests/commands/dev.test.ts\",\n \"packages/cli/tests/commands/env.test.ts\",\n \"packages/cli/tests/commands/monorepo.test.ts\",\n \"packages/cli/tests/commands/plugins.test.ts\",\n \"packages/cli/tests/commands/publish.test.ts\",\n \"packages/cli/tests/commands/start.test.ts\",\n \"packages/cli/tests/commands/tee.test.ts\",\n \"packages/cli/tests/commands/test.test.ts\",\n \"packages/cli/tests/commands/update.test.ts\",\n \"packages/cli/tests/unit/utils/elizacloud-config.test.ts\",\n \"packages/client/package.json\",\n \"packages/config/package.json\",\n \"packages/core/package.json\",\n \"packages/plugin-bootstrap/package.json\",\n \"packages/plugin-dummy-services/package.json\",\n \"packages/plugin-quick-starter/package.json\",\n \"packages/plugin-sql/build.ts\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-starter/package.json\",\n \"packages/project-starter/package.json\",\n \"packages/project-tee-starter/package.json\",\n \"packages/server/package.json\",\n \"packages/service-interfaces/package.json\",\n \"packages/test-utils/package.json\"\n ]\n },\n {\n \"title\": \"feat: enhance streaming support in text generation\",\n \"prNumber\": 6212,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\r\\n\\r\\n- Streaming support for text generation models\\r\\n- CLI test runner improvements\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**. Changes are additive and backward-compatible:\\r\\n- New streaming API is opt-in via `stream: true` parameter\\r\\n\\r\\n# Background\\r\",\n \"files\": [\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/src/utils/test-runner.ts\",\n \"packages/cli/tests/unit/commands/test/e2e-tests.test.ts\",\n \"packages/client/src/components/ChatMessageListComponent.tsx\",\n \"packages/client/src/components/chat.tsx\",\n \"packages/client/src/hooks/use-query-hooks.ts\",\n \"packages/client/src/hooks/use-socket-chat.ts\",\n \"packages/client/src/lib/socketio-manager.ts\",\n \"packages/core/src/__tests__/message-service.test.ts\",\n \"packages/core/src/__tests__/runtime.test.ts\",\n \"packages/core/src/__tests__/utils.test.ts\",\n \"packages/core/src/elizaos.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/services/default-message-service.ts\",\n \"packages/core/src/services/message-service.ts\",\n \"packages/core/src/types/elizaos.ts\",\n \"packages/core/src/types/model.ts\",\n \"packages/core/src/types/primitives.ts\",\n \"packages/core/src/types/runtime.ts\",\n \"packages/core/src/utils.ts\",\n \"packages/server/src/api/messaging/core.ts\",\n \"packages/server/src/services/message.ts\",\n \"packages/server/src/socketio/index.ts\",\n \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n \"packages/api-client/src/services/sessions.ts\",\n \"packages/api-client/src/types/sessions.ts\",\n \"packages/core/src/__tests__/elizaos-handlemessage.test.ts\",\n \"packages/core/src/__tests__/elizaos.test.ts\",\n \"packages/core/src/__tests__/messaging-types.test.ts\",\n \"packages/core/src/types/messaging.ts\",\n \"packages/core/src/types/plugin.ts\",\n \"packages/server/src/__tests__/integration/message-bus-service.test.ts\",\n \"packages/server/src/__tests__/unit/api/channels-mode.test.ts\",\n \"packages/server/src/__tests__/unit/api/response-handlers.test.ts\",\n \"packages/server/src/__tests__/unit/api/sessions.test.ts\",\n \"packages/server/src/__tests__/unit/services/message-stream-events.test.ts\",\n \"packages/server/src/api/messaging/channels.ts\",\n \"packages/server/src/api/messaging/sessions.ts\",\n \"packages/server/src/api/shared/constants.ts\",\n \"packages/server/src/api/shared/response-handlers.ts\",\n \"packages/server/src/api/shared/validation.ts\",\n \"packages/server/src/types/server.ts\",\n \"packages/cli/src/commands/scenario/src/UserSimulator.ts\",\n \"packages/core/src/__tests__/e2e/core-runtime.test.ts\",\n \"packages/core/src/__tests__/integration/character-runtime.test.ts\",\n \"packages/core/src/__tests__/integration/memory-runtime.test.ts\",\n \"packages/core/src/__tests__/runtime-embedding.test.ts\",\n \"packages/core/src/__tests__/runtime-streaming.test.ts\",\n \"packages/core/src/__tests__/streaming-context.test.ts\",\n \"packages/core/src/__tests__/test-helpers.ts\",\n \"packages/core/src/index.browser.ts\",\n \"packages/core/src/index.node.ts\",\n \"packages/core/src/index.ts\",\n \"packages/core/src/streaming-context.browser.ts\",\n \"packages/core/src/streaming-context.node.ts\",\n \"packages/core/src/streaming-context.ts\",\n \"packages/plugin-bootstrap/src/actions/reply.ts\",\n \"packages/core/src/__tests__/utils/streaming.test.ts\",\n \"packages/core/src/types/index.ts\",\n \"packages/core/src/types/streaming.ts\",\n \"packages/core/src/utils/streaming.ts\",\n \"packages/plugin-bootstrap/src/__tests__/actions.test.ts\"\n ]\n },\n {\n \"title\": \"Shaw/chore/deslop\",\n \"prNumber\": 6213,\n \"type\": \"other\",\n \"body\": \"This PR removes a lot of slop\\r\\n\\r\\n- Fixes any and unknown and cast types with real types\\r\\n- Removes try catch\\r\\n- Removes sloppy comments\\r\\n- Removes dead files and code\",\n \"files\": [\n \"build-utils.ts\",\n \"bun.lock\",\n \"packages/api-client/src/__tests__/integration/no-content-fix.test.ts\",\n \"packages/api-client/src/__tests__/services/agents.test.ts\",\n \"packages/api-client/src/__tests__/services/audio.test.ts\",\n \"packages/api-client/src/__tests__/services/jobs.test.ts\",\n \"packages/api-client/src/__tests__/services/media.test.ts\",\n \"packages/api-client/src/__tests__/services/memory.test.ts\",\n \"packages/api-client/src/__tests__/services/messaging.test.ts\",\n \"packages/api-client/src/__tests__/services/server.test.ts\",\n \"packages/api-client/src/__tests__/services/system.test.ts\",\n \"packages/api-client/src/lib/base-client.ts\",\n \"packages/api-client/src/services/agents.ts\",\n \"packages/api-client/src/services/audio.ts\",\n \"packages/api-client/src/services/jobs.ts\",\n \"packages/api-client/src/services/media.ts\",\n \"packages/api-client/src/services/memory.ts\",\n \"packages/api-client/src/services/messaging.ts\",\n \"packages/api-client/src/services/sessions.ts\",\n \"packages/api-client/src/services/system.ts\",\n \"packages/api-client/src/types/agents.ts\",\n \"packages/api-client/src/types/jobs.ts\",\n \"packages/api-client/src/types/media.ts\",\n \"packages/api-client/src/types/memory.ts\",\n \"packages/api-client/src/types/server.ts\",\n \"packages/api-client/src/types/system.ts\",\n \"packages/app/README.md\",\n \"packages/app/eslint.config.js\",\n \"packages/app/index.html\",\n \"packages/app/package.json\",\n \"packages/app/src-tauri/Cargo.toml\",\n \"packages/app/src-tauri/src/lib.rs\",\n \"packages/app/src/__tests__/main.test.ts\",\n \"packages/app/src/main.tsx\",\n \"packages/app/src/types/bun-test.d.ts\",\n \"packages/app/vite.config.ts\",\n \"packages/cli/src/commands/agent/actions/crud.ts\",\n \"packages/cli/src/commands/agent/actions/lifecycle.ts\",\n \"packages/cli/src/commands/create/actions/creators.ts\",\n \"packages/cli/src/commands/create/index.ts\",\n \"packages/cli/src/commands/create/utils/validation.ts\",\n \"packages/cli/src/commands/deploy/actions/deploy-ecs.ts\",\n \"packages/cli/src/commands/deploy/types.ts\",\n \"packages/cli/src/commands/dev/actions/dev-server.ts\",\n \"packages/cli/src/commands/publish/types.ts\",\n \"packages/cli/src/commands/report/generate.ts\",\n \"packages/cli/src/commands/report/src/analysis-engine.ts\",\n \"packages/cli/src/commands/scenario/docs/README.md\",\n \"packages/cli/src/commands/scenario/docs/file-format-spec.md\",\n \"packages/cli/src/commands/scenario/docs/matrix-testing.md\"\n ]\n },\n {\n \"title\": \"fix: resolve TypeScript build errors in every packages - first step\",\n \"prNumber\": 6218,\n \"type\": \"bugfix\",\n \"body\": \"\",\n \"files\": [\n \"packages/api-client/src/lib/base-client.ts\",\n \"packages/api-client/src/services/audio.ts\",\n \"packages/api-client/src/types/agents.ts\",\n \"packages/client/src/components/agent-action-viewer.tsx\",\n \"packages/client/src/components/chat.tsx\",\n \"packages/client/src/config/agent-templates.ts\",\n \"packages/client/src/hooks/__tests__/use-agent-update.test.tsx\",\n \"packages/client/src/hooks/use-character-convert.ts\",\n \"packages/client/src/hooks/use-partial-update.ts\",\n \"packages/client/src/hooks/use-query-hooks.ts\",\n \"packages/client/src/hooks/use-socket-chat.ts\",\n \"packages/client/src/lib/api-type-mappers.ts\",\n \"packages/client/src/lib/socketio-manager.ts\",\n \"packages/core/src/entities.ts\",\n \"packages/core/src/logger.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/types/events.ts\",\n \"packages/core/src/types/index.ts\",\n \"packages/core/src/types/plugin.ts\",\n \"packages/core/src/types/runtime.ts\",\n \"packages/core/src/types/state.ts\",\n \"packages/core/src/utils.ts\",\n \"packages/plugin-bootstrap/src/actions/choice.ts\",\n \"packages/plugin-bootstrap/src/actions/followRoom.ts\",\n \"packages/plugin-bootstrap/src/actions/ignore.ts\",\n \"packages/plugin-bootstrap/src/actions/imageGeneration.ts\",\n \"packages/plugin-bootstrap/src/actions/muteRoom.ts\",\n \"packages/plugin-bootstrap/src/actions/reply.ts\",\n \"packages/plugin-bootstrap/src/actions/roles.ts\",\n \"packages/plugin-bootstrap/src/actions/sendMessage.ts\",\n \"packages/plugin-bootstrap/src/actions/unfollowRoom.ts\",\n \"packages/plugin-bootstrap/src/actions/unmuteRoom.ts\",\n \"packages/plugin-bootstrap/src/actions/updateEntity.ts\",\n \"packages/plugin-bootstrap/src/evaluators/reflection.ts\",\n \"packages/plugin-bootstrap/src/index.ts\",\n \"packages/plugin-bootstrap/src/providers/actionState.ts\",\n \"packages/plugin-dummy-services/src/browser/service.ts\",\n \"packages/plugin-dummy-services/src/e2e/test-utils.ts\",\n \"packages/plugin-sql/src/base.ts\",\n \"packages/plugin-sql/src/index.node.ts\",\n \"packages/plugin-sql/src/index.ts\",\n \"packages/plugin-sql/src/migrations.ts\",\n \"packages/plugin-sql/src/pg/adapter.ts\",\n \"packages/plugin-sql/src/rls.ts\",\n \"packages/plugin-sql/src/runtime-migrator/runtime-migrator.ts\",\n \"packages/plugin-sql/src/runtime-migrator/storage/journal-storage.ts\",\n \"packages/plugin-sql/src/runtime-migrator/storage/migration-tracker.ts\",\n \"packages/plugin-sql/src/types.ts\",\n \"packages/server/src/api/agents/runs.ts\",\n \"packages/server/src/api/audio/conversation.ts\",\n \"packages/cli/src/commands/scenario/src/EvaluationEngine.ts\",\n \"packages/cli/src/commands/scenario/src/LocalEnvironmentProvider.ts\",\n \"packages/cli/src/commands/scenario/src/TrajectoryReconstructor.ts\",\n \"packages/cli/src/commands/scenario/src/UserSimulator.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-orchestrator.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-runner.ts\",\n \"packages/cli/src/commands/scenario/src/matrix-schema.ts\",\n \"packages/cli/src/commands/scenario/src/parameter-override.ts\",\n \"packages/cli/src/commands/scenario/src/run-isolation.ts\",\n \"packages/cli/src/commands/scenario/src/runtime-factory.ts\",\n \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n \"packages/cli/src/utils/spinner-utils.ts\",\n \"packages/core/src/__tests__/settings.test.ts\",\n \"packages/core/src/__tests__/utils.test.ts\",\n \"packages/core/src/elizaos.ts\",\n \"packages/core/src/schemas/character.ts\",\n \"packages/core/src/settings.ts\",\n \"packages/plugin-bootstrap/src/__tests__/logic.test.ts\"\n ]\n },\n {\n \"title\": \"fix: encryption for character secrets in correct order\",\n \"prNumber\": 6217,\n \"type\": \"bugfix\",\n \"body\": \"\",\n \"files\": [\n \"packages/core/src/__tests__/elizaos.test.ts\",\n \"packages/core/src/elizaos.ts\",\n \"packages/server/src/api/agents/crud.ts\",\n \"packages/server/src/index.ts\"\n ]\n },\n {\n \"title\": \"fix(plugin-sql): optimize pre-1.6.5 migration, RLS handling and SQL organisation\",\n \"prNumber\": 6215,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\n**Low** - All changes are backwards compatible and idempotent. Comprehensive test coverage added. Nothing is destructive\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Adds smooth migration from pre-1.6.5 (camelCase) to 1.6.5+ \",\n \"files\": [\n \".github/workflows/plugin-sql-tests.yaml\",\n \"examples/test-addagents-auto.ts\",\n \"packages/plugin-sql/docker-compose.test.yml\",\n \"packages/plugin-sql/package.json\",\n \"packages/plugin-sql/scripts/init-test-db.sql\",\n \"packages/plugin-sql/scripts/run-integration-tests.sh\",\n \"packages/plugin-sql/src/__tests__/fixtures/test-plugin-schema.ts\",\n \"packages/plugin-sql/src/__tests__/integration/pglite-e2e.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres/pg-adapter-integration.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres/pglite-adapter.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres/postgres-init.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres/rls-entity.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres/rls-logs.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres/rls-message-server-agents.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres/rls-server.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/dynamic-migration.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/e2e/docker-compose.yml\",\n \"packages/plugin-sql/src/__tests__/migration/e2e/run-upgrade-test.sh\",\n \"packages/plugin-sql/src/__tests__/migration/migration-before-1.6.5.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/production-scenario.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/runtime-migrator.test.ts\",\n \"packages/plugin-sql/src/__tests__/unit/directory-creation.test.ts\",\n \"packages/plugin-sql/src/__tests__/unit/index.test.ts\",\n \"packages/plugin-sql/src/__tests__/unit/pg/adapter.test.ts\",\n \"packages/plugin-sql/src/__tests__/unit/pglite/adapter.test.ts\",\n \"packages/plugin-sql/src/base.ts\",\n \"packages/plugin-sql/src/migrations.ts\",\n \"packages/plugin-sql/src/pg/manager.ts\",\n \"packages/plugin-sql/src/rls.ts\",\n \"packages/plugin-sql/src/runtime-migrator/runtime-migrator.ts\",\n \"packages/plugin-sql/src/schema/component.ts\",\n \"packages/plugin-sql/src/schema/log.ts\",\n \"packages/plugin-sql/src/schema/memory.ts\",\n \"packages/plugin-sql/src/schema/participant.ts\",\n \"packages/plugin-sql/src/schema/relationship.ts\",\n \"packages/plugin-sql/src/schema/room.ts\",\n \"packages/plugin-sql/src/schema/tasks.ts\",\n \"packages/plugin-sql/src/schema/world.ts\",\n \"packages/core/src/__tests__/logger-browser-node.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/rls-entity.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/actual-runtime-scenario.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/initialization-with-plugin.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/runtime-simulation.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/schema-evolution-tests/06-index-evolution.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/schema-evolution-tests/07-foreign-key-evolution.test.ts\",\n \"packages/plugin-sql/src/__tests__/migration/transaction-and-concurrency.test.ts\",\n \"packages/plugin-sql/src/__tests__/test-helpers.ts\",\n \"packages/plugin-sql/src/pglite/manager.ts\",\n \"packages/plugin-sql/src/runtime-migrator/storage/migration-tracker.ts\",\n \"packages/server/src/__tests__/fixtures/database.fixture.ts\"\n ]\n },\n {\n \"title\": \"fix: bootstrap action/provide format change fix + initPromise fix\",\n \"prNumber\": 6261,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\n\\r\\nLow, just fixes\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- exposes initPromise so plugins can actually use it (duplicates some of #5718 but smaller and simpler)\\r\\n- fixes message format (we dropped serverId in favor of messa\",\n \"files\": [\n \"packages/core/src/types/runtime.ts\",\n \"packages/plugin-bootstrap/src/__tests__/test-utils.ts\",\n \"packages/plugin-bootstrap/src/actions/settings.ts\",\n \"packages/plugin-bootstrap/src/providers/roles.ts\",\n \"packages/plugin-bootstrap/src/providers/settings.ts\",\n \"packages/plugin-quick-starter/src/__tests__/test-utils.ts\",\n \"packages/plugin-starter/src/__tests__/test-utils.ts\",\n \"packages/project-starter/src/__tests__/utils/core-test-utils.ts\",\n \"packages/project-tee-starter/src/__tests__/utils/core-test-utils.ts\",\n \"packages/test-utils/src/mocks/runtime.ts\",\n \"packages/plugin-bootstrap/src/__tests__/providers.test.ts\"\n ]\n },\n {\n \"title\": \"fix(core): add generic type support for custom event handlers\",\n \"prNumber\": 6277,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- Add generic type parameter to `registerEvent` for custom events\\n- Allows plugins to define typed event payloads that extend `EventPayload`\\n- Includes unit test\\n\\n## Example usage\\n```typescript\\ninterface MyCustomPayload extends E\",\n \"files\": [\n \"packages/core/src/__tests__/register-event.test.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/types/runtime.ts\"\n ]\n }\n ],\n \"topContributors\": [\n {\n \"username\": \"standujar\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4\",\n \"totalScore\": 724.1082130313846,\n \"prScore\": 698.9522130313846,\n \"issueScore\": 0,\n \"reviewScore\": 23,\n \"commentScore\": 2.1559999999999997,\n \"summary\": \"standujar: This month, standujar made substantial contributions across the `elizaos` ecosystem, focusing on core system stability, refactoring, and introducing new capabilities. They implemented a new Unified API for serverless Node.js environments (elizaos/eliza#6201) and delivered several complex fixes, most notably optimizing the pre-1.6.5 migration and RLS handling in the SQL plugin (elizaos/eliza#6215), which involved over 28k lines of changes. In addition to merging seven pull requests, they have eight open PRs that introduce significant new features like JWT authentication and widespread streaming support. Their work was distributed across bug fixes, feature development, and refactoring, with a strong emphasis on code and test files.\"\n },\n {\n \"username\": \"madjin\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n \"totalScore\": 325.1444101641285,\n \"prScore\": 307.8684101641285,\n \"issueScore\": 16.4,\n \"reviewScore\": 0,\n \"commentScore\": 0.8759999999999999,\n \"summary\": \"madjin: Focused on enhancing core functionality and maintaining project dependencies this month, merging three pull requests in the `elizaos/elizaos.github.io` repository. They implemented and fixed a new RSS feed feature (#172, #175) and also managed a substantial dependency update by upgrading the AI SDKs in a large PR (#170) with over 3300 new lines. Their work was a mix of bug fixes, feature implementation, and significant maintenance, touching both code and configuration files.\"\n },\n {\n \"username\": \"wtfsayo\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n \"totalScore\": 276.4179723270648,\n \"prScore\": 275.61797232706476,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.8,\n \"summary\": \"wtfsayo: Focused on client-side fixes and plugin migrations this month, merging two pull requests in the elizaos/eliza repository. They improved the user experience by fixing markdown content spacing (#6197) and migrated the SQL plugin to the new messageService API (#6202). Additionally, they have begun work on a new core feature for parallel action execution (#6209), with their overall contributions reflecting a primary focus on bug fixes and refactoring.\"\n },\n {\n \"username\": \"0xbbjoker\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n \"totalScore\": 212.90477621970334,\n \"prScore\": 165.40477621970334,\n \"issueScore\": 2,\n \"reviewScore\": 45.5,\n \"commentScore\": 0,\n \"summary\": \"0xbbjoker: This month, 0xbbjoker's work was primarily focused on bug fixes, contributing a significant volume of code changes across 68 files (+3655/-1134 lines). They merged one feature enhancement to the MCP provider (elizaos-plugins/plugin-mcp#19) and proactively opened an issue to improve the agent creator's file handling (elizaos/eliza#6245). In addition to their direct code contributions, they were an active collaborator, providing 6 code reviews for their peers.\"\n },\n {\n \"username\": \"odilitime\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n \"totalScore\": 193.21956638904118,\n \"prScore\": 192.67956638904118,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.54,\n \"summary\": \"odilitime: Undertook a substantial amount of work this month, reflected in 25 commits across 25 files (+2146/-592 lines). While this work has not yet been merged via a pull request, their coding activity shows a focus on bugfixes and refactoring. They also contributed by creating an issue in elizaos-plugins/plugin-mysql (#1).\"\n },\n {\n \"username\": \"ChristopherTrimboli\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4\",\n \"totalScore\": 130.67356870848266,\n \"prScore\": 111.17356870848266,\n \"issueScore\": 0,\n \"reviewScore\": 19.5,\n \"commentScore\": 0,\n \"summary\": \"ChristopherTrimboli: Focused on core feature development and dependency management, introducing ElizaOS Cloud as the default AI provider in the CLI (elizaos/eliza#6208) and executing a significant dependency update across the ecosystem (elizaos/eliza#6210). In addition to merging these two PRs, he supported the team by providing 4 code reviews. His work primarily involved modifications to configuration and test files, reflecting a focus on system health and testing alongside feature work.\"\n },\n {\n \"username\": \"borisudovicic\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31806472?u=8935f4d43fd7e4eb9bf5ff92d54d4d2f8ac8a786&v=4\",\n \"totalScore\": 108,\n \"prScore\": 0,\n \"issueScore\": 108,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"borisudovicic: Focused entirely on product definition and quality assurance for the elizaos/eliza repository this month. They created 41 issues, identifying a wide range of bugs, user experience enhancements, and new feature proposals. This work included documenting critical fixes like the container deployment bug (#6187) and proposing significant UX changes such as redesigning the dashboard (#6222) and consolidating navigation (#6173). All activity was concentrated on identifying and scoping improvements for the elizaos/eliza application.\"\n },\n {\n \"username\": \"lalalune\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/18633264?u=e2e906c3712c2506ebfa98df01c2cfdc50050b30&v=4\",\n \"totalScore\": 88.7855477931522,\n \"prScore\": 84.7855477931522,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"lalalune: Made a substantial contribution this month by merging a large-scale chore/refactor in the elizaos/eliza repository (PR #6213), which involved over 16,000 lines of code changes. They also began work on a major new feature with the \\\"Eliza Cloud Integration\\\" pull request (#6216) and identified a crash condition that was subsequently resolved (elizaos/eliza#6204). Their activity shows a primary focus on a mix of bugfixes, feature work, and refactoring across the codebase.\"\n },\n {\n \"username\": \"DevGruGold\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/181147699?u=4258e430ad766ca1d11778ab9e7d91ecfa0e110c&v=4\",\n \"totalScore\": 80.8515477931522,\n \"prScore\": 80.8515477931522,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"DevGruGold: This month, DevGruGold initiated new work in the elizaos/eliza repository, opening two pull requests (#6220, #6219). While no contributions were merged, these open PRs represent a substantial effort, containing over 1900 lines of code changes across 13 commits. This work, a mix of bug fixes and other tasks, was primarily focused on modifying configuration, documentation, and test files.\"\n },\n {\n \"username\": \"prajwal-pl\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/150137841?u=dd1ae31ec1ca9909364231a779dcb2af30c5e792&v=4\",\n \"totalScore\": 41.430056250181565,\n \"prScore\": 41.430056250181565,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"0xtechdean\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16443050?u=d1347a48b94a4c011e872424ea1940f3a0a8331d&v=4\",\n \"totalScore\": 35.89159695492178,\n \"prScore\": 35.89159695492178,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"0xtechdean: This month, 0xtechdean's efforts were directed toward documentation, opening a pull request to add AVS docs for the cursor/twitter agent (elizaos/eliza#6265).\"\n },\n {\n \"username\": \"AntoineVergne\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/151149734?v=4\",\n \"totalScore\": 33.983573590279974,\n \"prScore\": 29.28357359027997,\n \"issueScore\": 0,\n \"reviewScore\": 4.5,\n \"commentScore\": 0.2,\n \"summary\": \"AntoineVergne: This month, AntoineVergne's work focused on expanding the plugin ecosystem by adding the new 'plugin-farcaster-local-hub' to the registry (elizaos-plugins/registry#243). This feature contribution consisted of a single-line update to a configuration file. They also provided one comment on a pull request.\"\n },\n {\n \"username\": \"todoencadena\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/198127898?u=4c012fe538dffffc28d03890eda7d63746ae1ff2&v=4\",\n \"totalScore\": 24.27972435596375,\n \"prScore\": 24.27972435596375,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"todoencadena: Activity this month was focused on bot integration, opening a pull request to fix the Telegram bot for Railway (elizaos/eliza#6214). This work involved a single commit with minor changes to a configuration file.\"\n },\n {\n \"username\": \"Tonyflam\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/150600391?u=0c905a5f627ff99389fc79e9978f1dc47546456e&v=4\",\n \"totalScore\": 22.218573590279973,\n \"prScore\": 22.218573590279973,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"Tonyflam: This month, their contribution focused on expanding the plugin ecosystem by adding the new `@tonyflam/plugin-openchat` plugin to the registry via PR elizaos-plugins/registry#242. This work consisted of a minor update to a configuration file.\"\n },\n {\n \"username\": \"nguyennk92\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/30664183?u=d6e579cd25d50bc8e9ec4928d95909d759b841db&v=4\",\n \"totalScore\": 8.902606672028108,\n \"prScore\": 8.902606672028108,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"nguyennk92: This month, their focus was on refactoring database connection logic in the `elizaos/eliza` repository. They opened a pull request (#6262) proposing to remove the reassignment of the runtime database to individual connections. This work represents a targeted effort to improve connection management.\"\n },\n {\n \"username\": \"linear\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/in/20150?v=4\",\n \"totalScore\": 6,\n \"prScore\": 0,\n \"issueScore\": 6,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"linear: Focused on server reliability by identifying and documenting an issue related to concurrent connection timeouts in elizaos/eliza (#6198).\"\n },\n {\n \"username\": \"github-advanced-security\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/in/57789?v=4\",\n \"totalScore\": 4.5,\n \"prScore\": 0,\n \"issueScore\": 0,\n \"reviewScore\": 4.5,\n \"commentScore\": 0,\n \"summary\": \"github-advanced-security: No activity this month.\"\n },\n {\n \"username\": \"pereslavlland\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/247946180?v=4\",\n \"totalScore\": 2.2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"pereslavlland: This month, pereslavlland's activity was focused on bug reporting within the elizaos/eliza repository. They identified and opened issue #6211 to document a problem with snapshot eligibility and Tangem wallet connections, and also contributed one comment to an issue.\"\n },\n {\n \"username\": \"tdnupe3\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/25161668?u=94680b6bcbcfce954c7a9dd09d667a3919953041&v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"tdnupe3: This month, tdnupe3's efforts were directed towards planning new payment functionalities. They initiated this work by creating issue elizaos/eliza#6244, which proposes an implementation guide for integrating Circle and Coinbase APIs for AI agent payments.\"\n },\n {\n \"username\": \"flaviobruno72\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/168378940?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"otaku-x402\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/242004857?u=1325b26d380eec4a0b8d84e8e249c523eebd28dc&v=4\",\n \"totalScore\": 0.2,\n \"prScore\": 0,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": null\n }\n ],\n \"newPRs\": 30,\n \"mergedPRs\": 16,\n \"newIssues\": 60,\n \"closedIssues\": 78,\n \"activeContributors\": 22\n}\n---\n[\"linear_day_2025-12-24\", \"linear\", \"day\", \"2025-12-24\", \"linear: Focused on documentation improvements, creating an issue to \\\"Fix monorepo docs\\\" in elizaos/eliza (#6284).\", \"2025-12-28T23:16:12.986Z\"]\n[\"0xbbjoker_day_2025-12-24\", \"0xbbjoker\", \"day\", \"2025-12-24\", \"0xbbjoker: Focused on feature work, merging a significant PR in elizaos-plugins/plugin-knowledge#49 (+293/-276 lines) that added configurable rate limits, demonstrating a primary focus on other work and feature development.\", \"2025-12-28T23:16:13.048Z\"]\n[\"odilitime_day_2025-12-24\", \"odilitime\", \"day\", \"2025-12-24\", \"odilitime: Focused on refactoring and documentation work, making 2 commits that modified 2 files with a net addition of 19 lines.\", \"2025-12-28T23:16:13.050Z\"]\n[\"lalalune_day_2025-12-24\", \"lalalune\", \"day\", \"2025-12-24\", \"lalalune: Focused on bugfix work and other tasks, making 4 commits that modified 6994 files with a net change of -45384 lines across various file types.\", \"2025-12-28T23:16:13.072Z\"]\n[\"0xbbjoker_day_2025-12-23\", \"0xbbjoker\", \"day\", \"2025-12-23\", \"0xbbjoker: Focused on resolving TypeScript type errors, as evidenced by their open PR elizaos-plugins/plugin-discord#37, and contributed to significant code changes across 49 files with a net addition of over 1700 lines, primarily in bugfix and other work.\", \"2025-12-28T23:16:13.111Z\"]\n[\"odilitime_day_2025-12-23\", \"odilitime\", \"day\", \"2025-12-23\", \"odilitime: Focused on significant feature development, evidenced by an open PR in elizaos-plugins/plugin-discord#36 to add multi-bot voice architecture, alongside substantial code changes across 50 files (+7851/-538 lines) primarily focused on bug fixes, feature work, and tests.\", \"2025-12-28T23:16:13.127Z\"]\n[\"prajwal-pl_day_2025-12-23\", \"prajwal-pl\", \"day\", \"2025-12-23\", \"prajwal-pl: Focused on feature development, initiating a significant pull request in elizaos/eliza (#6279) to enhance message service handlers for asynchronous operations, involving substantial code changes across 8 files (+740/-210 lines).\", \"2025-12-28T23:16:13.137Z\"]\n[\"standujar_day_2025-12-23\", \"standujar\", \"day\", \"2025-12-23\", \"standujar: Focused on bug fixes and refactoring, merging two significant PRs including a large fix for TypeScript type errors in `elizaos-plugins/plugin-discord#38` (+3131/-1504 lines) and adding generic type support in `elizaos/eliza#6277`, demonstrating a primary focus on code quality and stability.\", \"2025-12-28T23:16:13.223Z\"]\n[\"lalalune_day_2025-12-25\", \"lalalune\", \"day\", \"2025-12-25\", \"lalalune: Focused on extensive code modifications, touching 19956 files with a net reduction of over 86,000 lines across 114 commits, primarily addressing bug fixes (44%), other work (42%), and refactoring (12%).\", \"2025-12-28T23:16:13.225Z\"]\n[\"lalalune_day_2025-12-26\", \"lalalune\", \"day\", \"2025-12-26\", \"lalalune: With 62 commits, lalalune made substantial code changes across 7920 files (+662700/-322374 lines), primarily focusing on other work (65%) and bug fixes (23%).\", \"2025-12-28T23:16:13.226Z\"]\n[\"borisudovicic_day_2025-12-24\", \"borisudovicic\", \"day\", \"2025-12-24\", \"borisudovicic: Focused on identifying and reporting user experience issues within the ElizaOS platform, creating five issues including \\\"Web Search\\\" (elizaos/eliza#6246) and \\\"Agent response smoothness\\\" (elizaos/eliza#6269), with four of these issues already closed, demonstrating a proactive approach to improving product quality.\", \"2025-12-28T23:16:13.297Z\"]\n[\"borisudovicic_day_2025-12-23\", \"borisudovicic\", \"day\", \"2025-12-23\", \"borisudovicic: Demonstrated a strong focus on product development and user experience by creating 21 issues, 19 of which were closed, covering a wide range of enhancements from \\\"Streaming & State\\\" (elizaos/eliza#5930) and \\\"Implement Inline Image/Video Generation\\\" (elizaos/eliza#6189) to significant UI/UX redesigns like \\\"Redesign dashboard as primary landing experience\\\" (elizaos/eliza#6222) and \\\"Refine agent builder\\\" (elizaos/eliza#6268), indicating a primary focus on feature definition and product improvement.\", \"2025-12-28T23:16:13.447Z\"]\n[\"standujar_day_2025-12-26\", \"standujar\", \"day\", \"2025-12-26\", \"standujar: Focused on bugfix work, merging a PR in elizaos-plugins/plugin-openai#22 to update core for streaming support, and opened a PR to standardize message server route naming in elizaos/eliza#6285. Their code changes primarily involved bugfixes, with additional work on other tasks and tests, touching code, tests, and config files.\", \"2025-12-28T23:16:13.466Z\"]\n[\"0xbbjoker_day_2025-12-26\", \"0xbbjoker\", \"day\", \"2025-12-26\", \"0xbbjoker: Focused on feature development, successfully merging a significant PR in elizaos-plugins/plugin-knowledge (#50) that added batch embeddings, contributing to new functionality with 231 additions and 101 deletions across 6 files. Their work primarily involved feature development and other tasks, touching both code and configuration files.\", \"2025-12-28T23:16:13.496Z\"]\n[\"wtfsayo_day_2025-12-26\", \"wtfsayo\", \"day\", \"2025-12-26\", \"wtfsayo: Focused on expanding media processing capabilities, delivering a significant feature in elizaos-plugins/plugin-farcaster#16 to add embed/media processing support for Farcaster casts, involving a substantial +746/-12 lines of code. Their work today primarily centered on feature development and bug fixes, with a focus on code and tests.\", \"2025-12-28T23:16:13.605Z\"]\n[\"wtfsayo_day_2025-12-28\", \"wtfsayo\", \"day\", \"2025-12-28\", \"wtfsayo: No activity today.\", \"2025-12-28T23:16:19.196Z\"]\n[\"lalalune_day_2025-12-27\", \"lalalune\", \"day\", \"2025-12-27\", \"lalalune: With 61 commits, lalalune made extensive code changes across 12536 files (+948271/-319483 lines), primarily focusing on bugfix work (44%) and other work (43%) across various file types.\", \"2025-12-28T23:16:19.350Z\"]\n[\"wtfsayo_day_2025-12-24\", \"wtfsayo\", \"day\", \"2025-12-24\", \"wtfsayo: Focused on refactoring and improving code quality, merging a significant PR in `elizaos-plugins/plugin-farcaster#15` which involved substantial DRY improvements and consistent logging across 1100 added and 1043 deleted lines, demonstrating a primary focus on other work, bug fixes, and refactoring.\", \"2025-12-28T23:16:13.963Z\"]\n[\"wtfsayo_day_2025-12-27\", \"wtfsayo\", \"day\", \"2025-12-27\", \"wtfsayo: Focused on bugfix work and other tasks, making 2 commits that modified 3 files with a net addition of 124 lines of code.\", \"2025-12-28T23:16:19.297Z\"]\n[\"lalalune_day_2025-12-28\", \"lalalune\", \"day\", \"2025-12-28\", \"lalalune: Today, lalalune made 9 commits, modifying 1396 files with a net addition of over 100,000 lines of code, primarily focusing on other work, bug fixes, refactoring, and tests.\", \"2025-12-28T23:16:19.316Z\"]\n---\n2025-12-29T02:17:13.272108Z\n---\n2025-12-29\n---\nai_news_elizaos_discord_md_2025-12-28\n---\nai_news_elizaos_discord_md_2025-12-27\n---\nai_news_elizaos_discord_md_2025-12-26\n---\nai_news_elizaos_daily_json_2025-12-28\n---\nai_news_elizaos_daily_md_2025-12-28\n---\nai_news_elizaos_daily_discord_json_2025-12-28\n---\nai_news_elizaos_daily_discord_md_2025-12-28\n---\ngithub_summaries_week_latest_2025-12-21.md\n---\ngithub_summaries_month_latest_2025-12-01.md\n---\ngithub_summaries_daily_2025-12-29" ] }