{ "prompt_name": "weekly-newsletter", "category": "comms", "date": "2025-12-31", "generated_text": "# ElizaOS Weekly Newsletter (2025-12-28 \u2192 2025-12-31)\n\n## 1) Executive Summary\n\n**A big week for momentum, infrastructure, and developer plumbing.** Here are the top milestones:\n\n1. **Eliza Cloud moved into open beta + new production agents shipped.** Community members confirmed **open beta access is live (with light support)**, and the team also **released new agents to production**, signaling faster iteration from \u201cbuild\u201d to \u201cship.\u201d \n2. **Jeju\u2019s vision got much clearer: compute marketplace today, permissionless hardware tomorrow.** Shaw shared that the near-term launch is **on AWS**, with an explicit end-state goal of **self-owned, permissionless infrastructure (physical racks in data centers) by year-end**, and earlier in the week described a system running across **Jeju + Babylon** that behaves like a decentralized \u201cVercel alternative\u201d for agent compute. \n3. **Core reliability improvements landed (and more are queued).** The team merged a critical fix to ensure **streaming LLM calls are logged to the database**\u2014a must-have for debugging, analytics, and cost visibility\u2014while pushing forward on **unified hooks** that work across **HTTP/SSE/WebSocket** without duplicate events.\n\n---\n\n## 2) Development Updates\n\n### Core platform (elizaOS/eliza)\n\n- **Merged: Streaming model calls now log correctly to DB** \n PR **#6296** fixed a bug where streaming paths returned before logging occurred, causing missing entries in model-call logs. This should improve observability for anyone using streaming responses (especially during load testing and regressions).\n\n- **In progress: Unified hooks with multi-transport support (HTTP/SSE/WebSocket)** \n PR **#6300** introduces a unified hooks layer intended to work across transports while avoiding the \u201cduplicate events on the message bus\u201d class of issues Stan mentioned. This is a meaningful step toward \u201cwrite once, deploy anywhere\u201d agent integrations\u2014web apps, dashboards, embedded widgets, and services.\n\n- **Small but welcome polish: typo fix** \n PR **#6297** corrected \u201csaftey\u201d \u2192 \u201csafety\u201d. Tiny change, but it reflects ongoing cleanup and review attention.\n\n- **New issues opened (UI/UX + app structure)** \n - Issue **#6291**: agent cards resizing unexpectedly to match dashboard cards \n - Issue **#6299**: \u201cUnslop Apps\u201d (early signal of more UI/layout cleanup work to come)\n\n### Plugins & developer experience\n\n- **OpenAI plugin: image generation fixed + caching added** \n Odilitime shipped improvements (PR referenced in Discord as **plugin-openai #23**) that both **fix image generation** and add **caching to prevent redundant media processing**\u2014a practical cost + latency reduction for agent workflows that handle repeated assets.\n\n- **Discord plugin: better logging ergonomics under discussion** \n A PR was submitted (Discord plugin **PR #36**) focused on logging enhancements. A notable thread: logging by **character name** can be more readable than agent IDs, but a **fallback to agentId** is sensible for uniqueness.\n\n- **Database portability debate: SQLite support vs PGLite** \n A healthy discussion resurfaced around restoring **first-class SQLite** because it\u2019s a single-file, portable deployment target. This matters for hobby deployments, edge devices, demos, and reproducible testing environments.\n\n---\n\n## 3) Community Spotlight (Discord)\n\n**Builders shipped, helped, and unblocked each other repeatedly this week:**\n\n- **MemeBroker shared real code for agent skills + OpenSouls integration**\n - Skills repo: https://github.com/Merlinthewizord/Skills_elizaos \n - OpenSouls plugin: https://github.com/Merlinthewizord/plugin-opensouls \n These are exactly the kinds of \u201creference implementations\u201d that accelerate the long tail of community builders.\n\n- **ElizaCloud integration help: turning an agent into a website feature** \n sam walked BAOVERSE through retrieving an **agent ID via ElizaCloud API endpoints** (with an API key), then followed up via DM with more integration code. This is a strong signal that \u201cagents embedded in web experiences\u201d is quickly becoming a default expectation.\n\n- **Practical troubleshooting that saves hours**\n - Destiny helped resolve confusion around \u201cshare links\u201d by advising users to **copy the full browser URL containing the character ID**. \n - Irie_Rubz shared a workaround for a Python \u201cno module named src\u201d error by setting **PYTHONPATH** via PowerShell before running batch files.\n\n- **Deployment reality check: Twitter API costs are still a blocker** \n The community reiterated that Twitter\u2019s paid API tier (~$200/month) limits experimentation. Builders discussed alternative social surfaces (e.g., **Sentient Space**) and confirmed there\u2019s **no cookie-auth Twitter plugin** available anymore.\n\n---\n\n## 4) Token Economics (AI16Z \u2192 ElizaOS, $AI16z, auto.fun)\n\n### Price + sentiment\n\n- The **ElizaOS token jumped ~120%** after Shaw regained access to X, and sentiment in Discord flipped noticeably from defensive to optimistic. The community also highlighted the need to keep price talk in the right places (e.g., #price-action) to preserve signal in dev channels.\n\n### Migration status & clarity\n\n- **Migration from AI16Z \u2192 ElizaOS remains a primary support topic.** \n Key points repeated in chat:\n - **Snapshot has already occurred**. \n - Eligibility referenced as **holding AI16Z for 30+ days** (per community responses). \n - Users continue to hit edge cases (wallet connection issues, \u201cmax amount reached,\u201d tokens visible but not exchangeable), with support directing folks to **#migration-help**.\n\n### Token info improvements underway\n\n- Kenk added/updated token info at **https://docs.elizaos.ai/tokenomics** and acknowledged the website still needs a clearer \u201ctoken hub\u201d page. Short-term, the plan is to add **CoinGecko links in the site footer**, while longer-term suggestions include a dedicated token page containing **contract addresses, exchanges, and community links**.\n\n### Utility & gating\n\n- Access to gated groups (e.g., **Spartan**) depends on holdings, with verification handled through **#verify-wallet**. There\u2019s also an active to-do to update **Collabland** so it reflects **ElizaOS holdings** instead of legacy ai16z data.\n\n---\n\n## 5) Coming Soon\n\nWhat to watch for in the near term:\n\n- **Unified hooks (PR #6300)** landing + follow-on work to standardize event delivery across transports. \n- **Release/versioning automation for plugins** (community asked for \u201crelease please\u201d-style CI so maintainers aren\u2019t manually bumping versions every PR). \n- **Website refresh focused on token discoverability** (dedicated token page + CoinGecko shortcuts). \n- **Jeju infrastructure evolution**: AWS first, then progressively toward **permissionless, self-owned racks**; providers may introduce **SLA options**. \n- **Ecosystem clarity docs**: multiple requests to explain how ElizaOS, Jeju, and future \u201cappcoins\u201d relate\u2014ideally with visuals and concrete examples.\n\n---\n\n## 6) Resources\n\n**GitHub (Core)**\n- PR #6300 \u2014 Unified hooks (HTTP/SSE/WebSocket): https://github.com/elizaOS/eliza/pull/6300 \n- PR #6296 \u2014 Fix: log streaming LLM calls to database (merged): https://github.com/elizaOS/eliza/pull/6296 \n- PR #6297 \u2014 Typo fix: https://github.com/elizaOS/eliza/pull/6297 \n- Issue #6291 \u2014 Agent card resizing: https://github.com/elizaOS/eliza/issues/6291 \n- Issue #6299 \u2014 \u201cUnslop Apps\u201d: https://github.com/elizaOS/eliza/issues/6299 \n\n**Community code**\n- MemeBroker Skills: https://github.com/Merlinthewizord/Skills_elizaos \n- MemeBroker OpenSouls plugin: https://github.com/Merlinthewizord/plugin-opensouls \n\n**Docs**\n- Tokenomics: https://docs.elizaos.ai/tokenomics", "source_references": [ "2025-12-31\n---\n2025-12-30.md\n---\n# elizaOS Discord - 2025-12-30\n\n## Overall Discussion Highlights\n\n### Token & Price Movement\n- **Significant Price Increase**: ElizaOS token experienced approximately 120% growth following Shaw's return to X (formerly Twitter)\n- **Sentiment Shift**: Community sentiment dramatically improved after the price increase, with previously negative members becoming more optimistic\n- **Token Migration**: Ongoing discussions about migration from ai16z to ElizaOS, with many users seeking clarification on the process and timeline\n- **Token Information**: Kenk acknowledged the need for improved website accessibility regarding token information, adding details to docs.elizaos.ai/tokenomics\n\n### Technical Development\n- **Hooks Implementation**: Stan shared progress on unified hooks with multi-transport support (HTTP/SSE/WebSocket) and fixed issues with duplicate events\n- **Plugin Improvements**: Odilitime fixed image generation in the OpenAI plugin and added caching to prevent redundant media processing\n- **Agent Development**: MemeBroker shared GitHub repositories for Eliza agent skills and a plugin for OpenSouls framework integration\n- **ElizaCloud Integration**: Discussions about integrating ElizaCloud agents into websites using API endpoints\n\n### Infrastructure Plans\n- **Jeju Infrastructure**: Shaw outlined plans to initially launch on AWS with a goal to transition to self-owned permissionless infrastructure with physical racks in data centers by year-end\n- **Alternative Platforms**: Discussions about platforms for agent deployment that avoid Twitter API costs ($200/month barrier)\n\n### Community & Ecosystem\n- **Spartan Group**: Several users inquired about joining the Spartan group/channel, which requires holding a specific amount of tokens for access\n- **Related Projects**: Discussions about the relationship between ElizaOS, DegenAI, and Ruby tokens within the ecosystem\n- **Documentation Needs**: Suggestions to enhance documentation explaining ElizaOS's role as the first appcoin on Jeju and its relationship with future appcoins\n\n## Key Questions & Answers\n\n- **Q**: What are the plans for Jeju infrastructure? \n **A**: Initially launching on AWS with plans to transition to self-owned permissionless infrastructure in data centers by year-end (answered by Shaw)\n\n- **Q**: Where can users find token information? \n **A**: Currently at docs.elizaos.ai/tokenomics with plans to improve website accessibility (answered by Kenk)\n\n- **Q**: How can I join the Spartan group? \n **A**: Verify your holding in #verify-wallet (answered by Kenk)\n\n- **Q**: What's with the pump? \n **A**: Shaw returned to X (answered by chomppp)\n\n- **Q**: How do I get the correct character URL? \n **A**: Copy the URL directly from the browser instead of using the share link button; it should contain the character ID (answered by Destiny)\n\n- **Q**: How do I integrate an ElizaCloud agent into my website? \n **A**: You need to get the agent ID using the ElizaCloud API endpoint with your API key (answered by sam)\n\n- **Q**: Should I pump the version for every plugin PR I make? \n **A**: \"That's what I'm doing. But I guess we should have a CI like in monorepo like release please or something like that\" (answered by Stan)\n\n- **Q**: Is there a Twitter plugin which still uses cookie-based authentication? \n **A**: No (answered by Odilitime)\n\n## Community Help & Collaboration\n\n- **MemeBroker** created and shared GitHub repositories with skills for making Eliza agents (https://github.com/Merlinthewizord/Skills_elizaos) and a plugin for OpenSouls framework integration (https://github.com/Merlinthewizord/plugin-opensouls)\n\n- **Destiny** helped **Peter Gibbons** with getting the correct character URL by instructing to copy the URL directly from browser instead of using the share link\n\n- **sam** assisted **BAOVERSE** with integrating ElizaCloud agent into a website by providing API endpoint code to retrieve agent ID and DMing additional integration code\n\n- **Omid Sa** directed **Moto** to the #migration-help channel for step-by-step assistance with ai16z token migration\n\n- **Kenk** helped **MATTIOBOY** join the Spartan gated channel by instructing to verify holdings in #verify-wallet\n\n- **Odilitime** offered to cover Northern California for data center infrastructure in response to Shaw's infrastructure plans\n\n## Action Items\n\n### Technical\n- Fix action call log type registration (PR #6296) (Mentioned by Stan)\n- Implement unified hooks with multi-transport support (HTTP/SSE/WebSocket) (PR #6300) (Mentioned by Stan)\n- Fix image generation and add caching in OpenAI plugin (PR #23) (Mentioned by Odilitime)\n- Clean up cloud codebase by reducing duplications and improving type handling (Mentioned by Stan)\n- Update Collabland to properly reflect ElizaOS token holdings instead of ai16z (Mentioned by coinfucius.eth)\n- Implement ElizaOS for role verification (Mentioned by Kenk)\n- Complete web3 EVM signing for stack that's already built (Mentioned by Odilitime)\n- Update MCP status for Kaizen (Mentioned by Diamondhandwhiteboy)\n- Explore alternative platforms for agent deployment to avoid Twitter API costs (Mentioned by M I A M I)\n- Implement ElizaCloud agent integration with websites using API endpoints (Mentioned by sam)\n- Website refresh with improved token information accessibility (Mentioned by Kenk)\n- Add Coingecko links to website footer as short-term solution (Mentioned by Kenk)\n- Transition from AWS to self-owned permissionless infrastructure by end of year (Mentioned by Shaw)\n\n### Documentation\n- Create dedicated token page with CA addresses, exchanges, links to community hubs and tracking sites (Mentioned by Broccolex)\n- Add explanation of ElizaOS as first appcoin on Jeju and its relationship with future appcoins (Mentioned by DorianD)\n- Create visual aids to help explain new concepts related to Jeju and ElizaOS (Mentioned by DorianD)\n- Create a list of projects launching on Eliza Cloud (Mentioned by Cryptor)\n- Clarify the relationship between ElizaOS, DegenAI, and Ruby tokens (Mentioned by Jack)\n\n### Feature\n- Consider implementing action calls by embeddings for IoT plugins (Mentioned by Stan)\n- Create skills specifically for making Eliza agents (Mentioned by jin)\n- Integrate OpenSouls framework with Eliza via plugin (Mentioned by MemeBroker)\n- Develop proprietary fine-tune of Llama 3.2 optimized for social platform ecosystem (Mentioned by M I A M I)\n---\n2025-12-29.md\n---\n# elizaOS Discord - 2025-12-29\n\n## Overall Discussion Highlights\n\n### Product Updates & Releases\n- **New Agents Released**: ElizaOS has released new agents to production\n- **Eliza Cloud Beta**: Open beta access is now available with light support ahead of full launch\n- **Cross-Chain Availability**: ElizaOS is available on multiple chains (Solana, Base, Ethereum, and BSC)\n- **Migration from AI16Z**: Snapshot has already occurred for the migration from AI16Z to ElizaOS, with eligibility for those holding AI16Z tokens for more than 30 days\n\n### Development Progress\n- **Documentation Updates**: PR #81 with Cloud integration and 30% monorepo coverage is ready for review\n- **Discord Plugin**: PR #36 submitted for the Discord plugin with logging enhancements\n- **Database Discussions**: Debate about restoring SQLite support due to its portability and single-file approach versus PGLite\n- **Type Safety**: Discussion about implementing build-time checks for unused variables as a middle ground between full TypeScript checks and relying on tools like Copilot/Opus\n\n### DegenAI Features\n- **Autotrader Functionality**: Available for holders of 1M+ tokens\n- **Trading Wins**: Plans to showcase DegenAI trading wins on social media platforms\n\n### Technical Issues\n- **Python Module Imports**: User troubleshooting \"no module name src\" error when running batch files\n- **Agent Chat Errors**: User reporting unspecified errors when trying to chat with an agent via share link\n\n## Key Questions & Answers\n\n**Q: Where to submit a ticket?** \nA: The Light directed to a specific channel (#1425417640071139358)\n\n**Q: Is there anywhere I can stake my AI16Z to earn AI16Z or Babylon or Babylon points?** \nA: No, AI16Z is migrating to ELIZAOS.\n\n**Q: How can I earn on ElizaOS or Earn Babylon?** \nA: For staking, stay tuned for upcoming announcements. There is an airdrop of Babylon for ELIZAOS holders that will be announced in the future. Currently, you can sign up in Babylon and gain points by doing tasks.\n\n**Q: When could I get access to Eliza Cloud beta?** \nA: You can jump into cloud now, the open beta will offer some light support ahead of a full launch.\n\n**Q: What's the contract of ElizaOS?** \nA: DuMbhu7mvQvqQHGcnikDgb4XegXJRyhUBfdU22uELiZA\n\n**Q: How to bridge elizaos from BSC to Solana?** \nA: Can only bridge from Solana to other chains, not vice versa.\n\n**Q: Do snapshots not need to be taken for the migration? Or have the migration criteria changed?** \nA: Snapshot already occurred.\n\n**Q: Any issue with using character's name instead of agentId in logging?** \nA: We are currently using agent name but can implement fallback to agentId.\n\n**Q: Why bring back SQLite support?** \nA: SQLite is more portable and uses a single file, unlike PGLite.\n\n## Community Help & Collaboration\n\n1. **Environment Variable Troubleshooting**:\n - User Irie_Rubz found a workaround for Python module import errors by using PowerShell to set the PYTHONPATH environment variable before running batch files\n\n2. **Discord Plugin Logging Enhancement**:\n - Odilitime proposed using character names instead of agent IDs in logging\n - Stan confirmed this was feasible and suggested implementing a fallback to agentId\n\n3. **Contract Information Sharing**:\n - User 4tshnrq provided the Solana contract address for ElizaOS when another user requested it\n\n4. **DegenAI Information**:\n - Odilitime explained that 1M token holders get access to autotrader functionality and provided information about the staging instance\n\n## Action Items\n\n### Technical\n- Review and merge PR #6285 (Mentioned by Stan \u26a1)\n- Create PR for Branded UUIDs implementation (Mentioned by Stan \u26a1)\n- Implement character name with agentId fallback in Discord plugin logging (Mentioned by Odilitime)\n- Restore first-class SQLite support (Mentioned by sayonara)\n- Resolve Python module import error in Davinci Resolve MCP project (Mentioned by Irie_Rubz)\n- Investigate error when chatting with an agent via share link (Mentioned by Destiny)\n- Implement X (Twitter) integration with DegenAI trading engine (Mentioned by Odilitime)\n- Continue development of DegenAI autotrader functionality (Mentioned by Odilitime)\n\n### Documentation\n- Finalize documentation updates with Cloud integration and monorepo coverage (Mentioned by Stan \u26a1)\n- Create setup guide for Davinci Resolve MCP on Windows (Mentioned by Irie_Rubz)\n- Create pinned tweet with contract addresses to avoid confusion (Mentioned by Broccolex)\n\n### Feature\n- Enable DegenAI to market its trading wins on social media (Mentioned by Odilitime)\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-30.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-12-30\n---\nElizaOS Discord Activity Summary - December 30, 2025\n---\nThe ElizaOS community is experiencing renewed excitement as Shaw has regained access to his X (formerly Twitter) account. This has led to a significant price increase for the $elizaOS token, with many community members celebrating the return of visibility and momentum to the project. Shaw hosted a space on X where he discussed Jeju, which appears to be a new infrastructure project related to ElizaOS.\n---\nhttps://discord.com/channels/1253563208833433701/1253563209462448241, https://discord.com/channels/1253563208833433701/1301363808421543988\n---\nThe development team continues to make progress on various aspects of the ElizaOS platform. Stan shared updates about unified hooks with multi-transport support, fixed issues with streaming LLM calls, and is working on cleaning up the codebase. Odilitime is working on plugin improvements, including fixes for image generation and adding caching to prevent processing the same media repeatedly. Jin (dankvr) shared Remotion, a tool for making videos programmatically that could be integrated with ElizaOS skills.\n---\nhttps://discord.com/channels/1253563208833433701/1377726087789940836, https://discord.com/channels/1253563208833433701/1300025221834739744\n---\nThere's ongoing discussion about improving the project's web presence. Broccolex suggested creating a dedicated token page similar to Pippin's website that would include contract addresses, available exchanges, and links to community hubs. Kenk (k_carv) mentioned that he recently added tokenomics information to the docs and is working on getting links to CoinGecko added to the website footer as a short-term solution.\n---\nhttps://discord.com/channels/1253563208833433701/1301363808421543988\n---\nThe community is also discussing alternative platforms for agent deployment, as Twitter API costs remain a barrier for many builders. Miami0x shared a social platform called Sentient Space that could be used for deploying agents without the high costs associated with Twitter's API. Additionally, Merlinthewizord (MemeBroker) shared GitHub repositories with skills for making ElizaOS agents and a plugin to integrate the OpenSouls framework.\n---\nhttps://discord.com/channels/1253563208833433701/1300025221834739744\n---\nThere's significant interest in DegenAI, which appears to be an official ElizaOS meme project. Community members are discussing its potential and relationship to ElizaOS. Additionally, news broke that Manus, another AI agent company, was acquired by Meta for $2 billion, highlighting the growing interest in the AI agent space.\n---\nhttps://discord.com/channels/1253563208833433701/1253563209462448241, https://discord.com/channels/1253563208833433701/1301363808421543988\n---\ndiscordrawdata\n---\nRecent Pull Requests in elizaOS/eliza Repository\n---\nThree recent pull requests have been submitted to the elizaOS/eliza repository:\n\n1. PR #6300 by standujar introduces a new feature for unified hooks with multi-transport support, including HTTP, SSE (Server-Sent Events), and WebSocket protocols.\n\n2. PR #6296, also by standujar, fixes an issue in the core component by implementing logging of streaming LLM (Large Language Model) calls to the database.\n\n3. PR #6297 by efeecllk addresses a simple typo correction, changing 'saftey' to the correct spelling 'safety'.\n---\nhttps://github.com/elizaOS/eliza/pull/6300\n---\nhttps://github.com/elizaOS/eliza/pull/6296\n---\nhttps://github.com/elizaOS/eliza/pull/6297\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/pull/6300\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/pull/6296\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/pull/6297\n---\npull_request\n---\nGitHub Issues from borisudovicic\n---\nTwo issues have been opened by GitHub user borisudovicic in the elizaOS/eliza repository:\n\n1. Issue #6291: \"My agent cards resizing to match dashboard agent cards\" - This appears to be related to card sizing consistency between agent cards in different views.\n\n2. Issue #6299: \"Unslop Apps\" - This issue likely relates to application layout or positioning behavior.\n\nBoth issues were recently filed and are currently open in the repository's issue tracker.\n---\nhttps://github.com/elizaOS/eliza/issues/6291\n---\nhttps://github.com/elizaOS/eliza/issues/6299\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/issues/6291\n---\nhttps://opengraph.githubassets.com/1/elizaOS/eliza/issues/6299\n---\nissue\n---\nelizaos/eliza GitHub Activity (Dec 30-31, 2025)\n---\nFrom December 30 to December 31, 2025, the elizaos/eliza repository showed the following activity:\n\n- 3 new pull requests were created, with 1 of them being merged\n- 2 new issues were opened\n- 8 contributors were active during this period\n---\ntext\n---\ngithub_summary\n---\nBugfix: Log Streaming LLM Calls to Database\n---\nA bugfix was implemented to address an issue with logging streaming LLM (Large Language Model) calls to the database. This fix was merged through Pull Request #6296 in the elizaOS/eliza repository.\n---\nhttps://github.com/elizaOS/eliza/pull/6296\n---\ncompleted_items\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-30.md\n---\n# ElizaOS Activity Summary - December 30, 2025\n\n## Community Updates\n\n- Shaw regained access to his X account, leading to significant $elizaOS token price increase\n- Shaw hosted a space on X discussing Jeju, a new infrastructure project related to ElizaOS\n- Meta acquired Manus (AI agent company) for $2 billion, highlighting growing interest in AI agents\n- Community showing interest in DegenAI, an official ElizaOS meme project\n\n## Development Progress\n\n- Stan implemented unified hooks with multi-transport support (HTTP, SSE, WebSocket)\n- Fixed issues with streaming LLM calls and implemented database logging\n- Odilitime working on plugin improvements including image generation fixes and caching\n- Jin (dankvr) shared Remotion, a tool for making videos programmatically for ElizaOS skills\n\n## Web Presence & Community Resources\n\n- Kenk (k_carv) added tokenomics information to documentation\n- Work underway to add CoinGecko links to website footer\n- Discussion about creating a dedicated token page with contract addresses and exchange information\n- Miami0x shared Sentient Space as a platform for deploying agents without high Twitter API costs\n- Merlinthewizord shared GitHub repositories with skills for ElizaOS agents and OpenSouls integration\n\n## GitHub Activity (Dec 30-31, 2025)\n\n- 3 new pull requests created, 1 merged\n- 2 new issues opened\n- 8 active contributors during this period\n\n### Recent Pull Requests\n\n- PR #6300: Unified hooks with multi-transport support\n- PR #6296: Fixed logging of streaming LLM calls to database\n- PR #6297: Typo correction (saftey \u2192 safety)\n\n### Recent Issues\n\n- Issue #6291: \"My agent cards resizing to match dashboard agent cards\"\n- Issue #6299: \"Unslop Apps\"\n---\n2025-12-30.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-12-30\n---\n1253563209462448241\n---\n\ud83d\udcac-discussion\n---\n# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around the recent price movement of ElizaOS token, which experienced significant growth (reportedly 120%) after Shaw's return to X (formerly Twitter). Community members discussed the token migration from ai16z to ElizaOS, with many questions about the migration process and timeline. There were mentions of the ElizaCloud platform for building AI agents, and discussions about related tokens in the ecosystem like DegenAI and Ruby. Technical discussions were limited, though there was mention of role verification using ElizaOS and web3 EVM signing implementation. The chat shows a dramatic shift in sentiment following the price increase, with previously negative community members becoming more optimistic. Several users inquired about joining the Spartan group/channel, which requires holding a specific amount of tokens for access.\n\n## 2. FAQ\nQ: What is the real marketcap of ElizaOS? (asked by mosess01) A: Unanswered\nQ: Is it okay if I write in the X bio, powered by ElizaOS? (asked by Saske Uchiii) A: Unanswered\nQ: How to verify my nft role? (asked by KNOWN) A: Unanswered\nQ: What's with the pump? (asked by mangoaggro) A: Shaw returned to X (answered by chomppp)\nQ: How can I join the spartan group? (asked by MATTIOBOY \ud83c\udde6\ud83c\uddfa) A: Verify your holding in #verify-wallet (answered by Kenk)\nQ: Where to find projects launching on Eliza Cloud? (asked by Cryptor) A: Unanswered\nQ: Is DegenAI still an Eliza project? (asked by Mahditwentyfive) A: Unanswered\nQ: What happened with the lawsuit between Twitter and Shaw? (asked by hxf) A: Unanswered\nQ: When do you think token reach 1 dollar? (asked by 388125) A: Unanswered\nQ: Is it now 1m ElizaOS for partner? (asked by ElBru) A: Unanswered\n\n## 3. Help Interactions\nHelper: Omid Sa | Helpee: Moto | Context: Questions about ai16z token migration | Resolution: Directed user to #migration-help channel for step-by-step assistance\nHelper: Kenk | Helpee: MATTIOBOY \ud83c\udde6\ud83c\uddfa | Context: How to join the Spartan gated channel | Resolution: Instructed to verify holdings in #verify-wallet\nHelper: Omid Sa | Helpee: weedisgood | Context: New user asking where to buy ElizaOS | Resolution: Provided information about available chains and directed to contract addresses channel\nHelper: satsbased | Helpee: Error P015-A | Context: User posting price-related content in wrong channel | Resolution: Directed to #price-action channel for price discussions\nHelper: Biazs | Helpee: Bitpay | Context: User asking if project is dead | Resolution: Explained project is fine, only token had rough month but is healing\n\n## 4. Action Items\nType: Technical | Description: Update Collabland to properly reflect ElizaOS token holdings instead of ai16z | Mentioned By: coinfucius.eth\nType: Technical | Description: Implement ElizaOS for role verification | Mentioned By: Kenk\nType: Technical | Description: Complete web3 EVM signing for stack that's already built | Mentioned By: Odilitime\nType: Technical | Description: Update MCP status for Kaizen | Mentioned By: Diamondhandwhiteboy\nType: Documentation | Description: Create a list of projects launching on Eliza Cloud | Mentioned By: Cryptor\nType: Documentation | Description: Clarify the relationship between ElizaOS, DegenAI, and Ruby tokens | Mentioned By: @Jack\n---\n1300025221834739744\n---\n\ud83d\udcac-coders\n---\n# Discord Chat Analysis for \ud83d\udcac-coders Channel\n\n## 1. Summary:\nThe chat primarily focused on Eliza OS agent development and deployment. MemeBroker shared GitHub repositories for Eliza agent skills and a plugin for OpenSouls framework integration. A significant discussion occurred around Twitter API limitations, with users noting the $200/month cost barrier for the official API. As an alternative, M I A M I introduced a social platform for agent deployment without Twitter API costs. There was also a technical exchange about retrieving agent IDs from ElizaCloud using API endpoints. MemeBroker announced discontinuing work with a token deployer due to payment issues but plans to continue developing their agent independently. The chat included several instances of community members helping each other with technical implementation details.\n\n## 2. FAQ:\nQ: Is there a Twitter plugin which still uses cookie-based authentication? (asked by sheenjek) A: No. (answered by Odilitime)\nQ: How do I integrate an ElizaCloud agent into my website? (asked by BAOVERSE\ud83c\udf1f) A: You need to get the agent ID using the ElizaCloud API endpoint with your API key. (answered by sam)\nQ: How do I get the correct character URL? (asked by Peter Gibbons ($PGP)) A: Copy the URL directly from the browser instead of using the share link button; it should contain the character ID. (answered by Destiny)\n\n## 3. Help Interactions:\nHelper: MemeBroker | Helpee: jin | Context: Sharing Eliza agent skills | Resolution: Created and shared GitHub repository with skills for making Eliza agents (https://github.com/Merlinthewizord/Skills_elizaos)\nHelper: MemeBroker | Helpee: Community | Context: OpenSouls integration | Resolution: Shared GitHub repository with plugin for OpenSouls framework (https://github.com/Merlinthewizord/plugin-opensouls)\nHelper: Destiny | Helpee: Peter Gibbons ($PGP) | Context: Getting correct character URL | Resolution: Instructed to copy URL directly from browser instead of using share link\nHelper: sam | Helpee: BAOVERSE\ud83c\udf1f | Context: Integrating ElizaCloud agent into website | Resolution: Provided API endpoint code to retrieve agent ID and DMed additional integration code\n\n## 4. Action Items:\nType: Technical | Description: Explore alternative platforms for agent deployment to avoid Twitter API costs | Mentioned By: M I A M I\nType: Technical | Description: Implement ElizaCloud agent integration with websites using API endpoints | Mentioned By: sam\nType: Feature | Description: Create skills specifically for making Eliza agents | Mentioned By: jin\nType: Technical | Description: Integrate OpenSouls framework with Eliza via plugin | Mentioned By: MemeBroker\nType: Feature | Description: Develop proprietary fine-tune of Llama 3.2 optimized for social platform ecosystem | Mentioned By: M I A M I\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\n# Analysis of \ud83e\udd47-partners Discord Channel\n\n## 1. Summary\nThe discussion primarily revolves around ElizaOS, Jeju infrastructure, and token information. Shaw mentions working on a \"life-changing\" project and elaborates on Jeju's infrastructure plans, including launching initially on AWS with a goal to transition to self-owned permissionless infrastructure with physical racks in data centers by year-end. Kenk acknowledges the need for website improvements, particularly regarding token information accessibility, responding to Broccolex's suggestion for a dedicated token page with essential information (contract addresses, exchanges, etc.). Kenk mentions adding token documentation to docs.elizaos.ai/tokenomics and plans to add Coingecko links to the website footer as a short-term solution. DorianD suggests enhancing documentation to explain ElizaOS's role as the first appcoin on Jeju and its relationship with future appcoins, potentially with visual aids to help users understand the novel concepts.\n\n## 2. FAQ\nQ: What is the life-changing announcement? (asked by sayitaintso25) A: Shaw indicated he's working on something he considers \"pretty lifechanging\" (answered by shaw)\nQ: What are the plans for Jeju infrastructure? (asked by Odilitime) A: Initially launching on AWS with plans to transition to self-owned permissionless infrastructure in data centers by year-end (answered by shaw)\nQ: Where can users find token information? (asked by Broccolex) A: Currently at docs.elizaos.ai/tokenomics with plans to improve website accessibility (answered by Kenk)\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: Broccolex | Context: Need for accessible token information on website | Resolution: Kenk added token info to docs.elizaos.ai/tokenomics and plans to add Coingecko links to website footer\nHelper: Odilitime | Helpee: shaw | Context: Offering infrastructure support | Resolution: Odilitime offered to cover Northern California for data center infrastructure\n\n## 4. Action Items\nType: Documentation | Description: Create dedicated token page with CA addresses, exchanges, links to community hubs and tracking sites | Mentioned By: Broccolex\nType: Documentation | Description: Add explanation of ElizaOS as first appcoin on Jeju and its relationship with future appcoins | Mentioned By: DorianD\nType: Documentation | Description: Create visual aids to help explain new concepts related to Jeju and ElizaOS | Mentioned By: DorianD\nType: Technical | Description: Website refresh with improved token information accessibility | Mentioned By: Kenk\nType: Technical | Description: Add Coingecko links to website footer as short-term solution | Mentioned By: Kenk\nType: Technical | Description: Transition from AWS to self-owned permissionless infrastructure by end of year | Mentioned By: shaw\n---\n1377726087789940836\n---\ncore-devs\n---\n# Discord Chat Analysis for \"core-devs\" Channel\n\n## 1. Summary:\nThe conversation primarily focused on development updates and technical improvements to the Eliza platform. Stan shared progress on hooks implementation with multi-transport support (HTTP/SSE/WebSocket) and fixed issues where server package transports were emitting duplicate events on the message bus. He also submitted a PR (#6296) to fix action call log type registration that broke after streaming was added. Jin mentioned Remotion.dev as a tool for creating professional videos via CLI, suggesting it could be used with Playwright MCP for screenshots. There was brief discussion about using embeddings for action calls, particularly for IoT plugins. Odilitime addressed plugin versioning practices and submitted a PR (#23) to fix image generation in the OpenAI plugin while adding caching to prevent redundant media processing.\n\n## 2. FAQ:\nQ: Is there a dev build of elizacloud online for security testing? (asked by jin) A: Unanswered\nQ: Should I pump the version for every plugin PR I make? (asked by Odilitime) A: That's what I'm doing. But Ig we should have a CI like in monorepo like release please or something like that (answered by Stan \u26a1)\n\n## 3. Help Interactions:\nHelper: Stan \u26a1 | Helpee: Odilitime | Context: Question about version management for plugin PRs | Resolution: Stan confirmed his approach of incrementing versions with each PR and suggested implementing a CI solution similar to the monorepo\n\n## 4. Action Items:\nType: Technical | Description: Fix action call log type registration (PR #6296) | Mentioned By: Stan \u26a1\nType: Technical | Description: Implement unified hooks with multi-transport support (HTTP/SSE/WebSocket) (PR #6300) | Mentioned By: Stan \u26a1\nType: Technical | Description: Fix image generation and add caching in OpenAI plugin (PR #23) | Mentioned By: Odilitime\nType: Technical | Description: Clean up cloud codebase by reducing duplications and improving type handling | Mentioned By: Stan \u26a1\nType: Feature | Description: Consider implementing action calls by embeddings for IoT plugins | Mentioned By: Stan \u26a1\n---\n2025-12-30.md\n---\n# elizaOS Discord - 2025-12-30\n\n## Overall Discussion Highlights\n\n### Token & Price Movement\n- **Significant Price Increase**: ElizaOS token experienced approximately 120% growth following Shaw's return to X (formerly Twitter)\n- **Sentiment Shift**: Community sentiment dramatically improved after the price increase, with previously negative members becoming more optimistic\n- **Token Migration**: Ongoing discussions about migration from ai16z to ElizaOS, with many users seeking clarification on the process and timeline\n- **Token Information**: Kenk acknowledged the need for improved website accessibility regarding token information, adding details to docs.elizaos.ai/tokenomics\n\n### Technical Development\n- **Hooks Implementation**: Stan shared progress on unified hooks with multi-transport support (HTTP/SSE/WebSocket) and fixed issues with duplicate events\n- **Plugin Improvements**: Odilitime fixed image generation in the OpenAI plugin and added caching to prevent redundant media processing\n- **Agent Development**: MemeBroker shared GitHub repositories for Eliza agent skills and a plugin for OpenSouls framework integration\n- **ElizaCloud Integration**: Discussions about integrating ElizaCloud agents into websites using API endpoints\n\n### Infrastructure Plans\n- **Jeju Infrastructure**: Shaw outlined plans to initially launch on AWS with a goal to transition to self-owned permissionless infrastructure with physical racks in data centers by year-end\n- **Alternative Platforms**: Discussions about platforms for agent deployment that avoid Twitter API costs ($200/month barrier)\n\n### Community & Ecosystem\n- **Spartan Group**: Several users inquired about joining the Spartan group/channel, which requires holding a specific amount of tokens for access\n- **Related Projects**: Discussions about the relationship between ElizaOS, DegenAI, and Ruby tokens within the ecosystem\n- **Documentation Needs**: Suggestions to enhance documentation explaining ElizaOS's role as the first appcoin on Jeju and its relationship with future appcoins\n\n## Key Questions & Answers\n\n- **Q**: What are the plans for Jeju infrastructure? \n **A**: Initially launching on AWS with plans to transition to self-owned permissionless infrastructure in data centers by year-end (answered by Shaw)\n\n- **Q**: Where can users find token information? \n **A**: Currently at docs.elizaos.ai/tokenomics with plans to improve website accessibility (answered by Kenk)\n\n- **Q**: How can I join the Spartan group? \n **A**: Verify your holding in #verify-wallet (answered by Kenk)\n\n- **Q**: What's with the pump? \n **A**: Shaw returned to X (answered by chomppp)\n\n- **Q**: How do I get the correct character URL? \n **A**: Copy the URL directly from the browser instead of using the share link button; it should contain the character ID (answered by Destiny)\n\n- **Q**: How do I integrate an ElizaCloud agent into my website? \n **A**: You need to get the agent ID using the ElizaCloud API endpoint with your API key (answered by sam)\n\n- **Q**: Should I pump the version for every plugin PR I make? \n **A**: \"That's what I'm doing. But I guess we should have a CI like in monorepo like release please or something like that\" (answered by Stan)\n\n- **Q**: Is there a Twitter plugin which still uses cookie-based authentication? \n **A**: No (answered by Odilitime)\n\n## Community Help & Collaboration\n\n- **MemeBroker** created and shared GitHub repositories with skills for making Eliza agents (https://github.com/Merlinthewizord/Skills_elizaos) and a plugin for OpenSouls framework integration (https://github.com/Merlinthewizord/plugin-opensouls)\n\n- **Destiny** helped **Peter Gibbons** with getting the correct character URL by instructing to copy the URL directly from browser instead of using the share link\n\n- **sam** assisted **BAOVERSE** with integrating ElizaCloud agent into a website by providing API endpoint code to retrieve agent ID and DMing additional integration code\n\n- **Omid Sa** directed **Moto** to the #migration-help channel for step-by-step assistance with ai16z token migration\n\n- **Kenk** helped **MATTIOBOY** join the Spartan gated channel by instructing to verify holdings in #verify-wallet\n\n- **Odilitime** offered to cover Northern California for data center infrastructure in response to Shaw's infrastructure plans\n\n## Action Items\n\n### Technical\n- Fix action call log type registration (PR #6296) (Mentioned by Stan)\n- Implement unified hooks with multi-transport support (HTTP/SSE/WebSocket) (PR #6300) (Mentioned by Stan)\n- Fix image generation and add caching in OpenAI plugin (PR #23) (Mentioned by Odilitime)\n- Clean up cloud codebase by reducing duplications and improving type handling (Mentioned by Stan)\n- Update Collabland to properly reflect ElizaOS token holdings instead of ai16z (Mentioned by coinfucius.eth)\n- Implement ElizaOS for role verification (Mentioned by Kenk)\n- Complete web3 EVM signing for stack that's already built (Mentioned by Odilitime)\n- Update MCP status for Kaizen (Mentioned by Diamondhandwhiteboy)\n- Explore alternative platforms for agent deployment to avoid Twitter API costs (Mentioned by M I A M I)\n- Implement ElizaCloud agent integration with websites using API endpoints (Mentioned by sam)\n- Website refresh with improved token information accessibility (Mentioned by Kenk)\n- Add Coingecko links to website footer as short-term solution (Mentioned by Kenk)\n- Transition from AWS to self-owned permissionless infrastructure by end of year (Mentioned by Shaw)\n\n### Documentation\n- Create dedicated token page with CA addresses, exchanges, links to community hubs and tracking sites (Mentioned by Broccolex)\n- Add explanation of ElizaOS as first appcoin on Jeju and its relationship with future appcoins (Mentioned by DorianD)\n- Create visual aids to help explain new concepts related to Jeju and ElizaOS (Mentioned by DorianD)\n- Create a list of projects launching on Eliza Cloud (Mentioned by Cryptor)\n- Clarify the relationship between ElizaOS, DegenAI, and Ruby tokens (Mentioned by Jack)\n\n### Feature\n- Consider implementing action calls by embeddings for IoT plugins (Mentioned by Stan)\n- Create skills specifically for making Eliza agents (Mentioned by jin)\n- Integrate OpenSouls framework with Eliza via plugin (Mentioned by MemeBroker)\n- Develop proprietary fine-tune of Llama 3.2 optimized for social platform ecosystem (Mentioned by M I A M I)\n---\n2025-12-31.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 37 new PRs (21 merged), 67 new issues, and 24 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_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\": 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_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\": 15509,\n \"deletions\": 6345,\n \"files\": 295,\n \"commitCount\": 241\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 \"title\": \"fix(server): standardize message server route naming\",\n \"prNumber\": 6285,\n \"type\": \"bugfix\",\n \"body\": \"## fix(server): standardize message server route naming\\r\\n\\r\\n### Problem\\r\\n\\r\\nThe `api-client` package was calling `/message-servers/*` routes that didn't exist on the server. The server had inconsistent naming with `/servers/*` routes instead.\",\n \"files\": [\n \"packages/server/src/__tests__/unit/api/message-servers.test.ts\",\n \"packages/server/src/api/messaging/messageServers.ts\"\n ]\n },\n {\n \"title\": \"docs(plugin-dummy-services): add comprehensive README\",\n \"prNumber\": 6290,\n \"type\": \"docs\",\n \"body\": \"## Summary\\nAdded comprehensive README.md documentation for the `@elizaos/plugin-dummy-services` package.\\n\\n## Documentation Includes\\n- Package overview and purpose\\n- Installation instructions (using bun)\\n- Table of all 9 available dummy serv\",\n \"files\": [\n \"packages/plugin-dummy-services/README.md\"\n ]\n },\n {\n \"title\": \"fix(cli): replace execa and child_process with Bun.spawn and bun-exec utilities\",\n \"prNumber\": 6289,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\nPer project guidelines in CLAUDE.md, replaced prohibited process execution libraries with Bun-native alternatives.\\n\\n## Changes\\n- **docker-build.ts**: Replaced `execa` with `bunExec` for docker commands\\n- **phala-wrapper.ts**: Rep\",\n \"files\": [\n \"packages/cli/src/commands/deploy/utils/docker-build.ts\",\n \"packages/cli/src/commands/report/src/__tests__/integration.test.ts\",\n \"packages/cli/src/commands/tee/phala-wrapper.ts\"\n ]\n },\n {\n \"title\": \"docs: fix documentation inconsistencies and add missing test flags\",\n \"prNumber\": 6288,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\n- Change `npm install` to `bun add` in packages/server/README.md (project uses bun exclusively)\\n- Replace broken BUILD_SYSTEM.md link with inline explanation in packages/core/README.md\\n- Add `--port` and `--skip-type-check` flags\",\n \"files\": [\n \"CLAUDE.md\",\n \"packages/core/README.md\",\n \"packages/server/README.md\"\n ]\n },\n {\n \"title\": \"fix(core): log streaming LLM calls to database\",\n \"prNumber\": 6296,\n \"type\": \"bugfix\",\n \"body\": \"## Summary\\r\\n\\r\\nStreaming model calls were not being logged to the database because the logging code was placed after the `return` statement in the streaming path. This caused LLM calls (TEXT_SMALL, TEXT_LARGE) to not appear in the Model Call\",\n \"files\": [\n \"packages/client/src/components/agent-action-viewer.tsx\",\n \"packages/client/src/hooks/use-query-hooks.ts\",\n \"packages/core/src/__tests__/runtime-streaming.test.ts\",\n \"packages/core/src/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\": 890.5000159172415,\n \"prScore\": 831.0040159172415,\n \"issueScore\": 0,\n \"reviewScore\": 57,\n \"commentScore\": 2.496,\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\": \"wtfsayo\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n \"totalScore\": 413.4725792109669,\n \"prScore\": 410.2345792109669,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 1.238,\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\": \"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\": \"odilitime\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n \"totalScore\": 218.24058973839072,\n \"prScore\": 217.7005897383907,\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\": \"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\": \"ChristopherTrimboli\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4\",\n \"totalScore\": 135.67356870848266,\n \"prScore\": 111.17356870848266,\n \"issueScore\": 0,\n \"reviewScore\": 24.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\": 118,\n \"prScore\": 0,\n \"issueScore\": 118,\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\": \"prajwal-pl: This month, prajwal-pl focused on feature development, opening a pull request to improve message service handlers with asynchronous operations (elizaos/eliza#6279). This work represents a substantial effort, with a single commit modifying 8 files and adding over 700 lines of code. Their activity was concentrated entirely on this new feature.\"\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\": \"greptile-apps\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/in/867647?v=4\",\n \"totalScore\": 27.2,\n \"prScore\": 0,\n \"issueScore\": 0,\n \"reviewScore\": 27,\n \"commentScore\": 0.2,\n \"summary\": null\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\": \"efeecllk\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/98906252?u=2e61afdda01f49499ce519e4024e5f0a20fa091e&v=4\",\n \"totalScore\": 22.95669638293567,\n \"prScore\": 22.95669638293567,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\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\": \"tdnupe3\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/25161668?u=94680b6bcbcfce954c7a9dd09d667a3919953041&v=4\",\n \"totalScore\": 15.547573590279972,\n \"prScore\": 13.547573590279972,\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\": \"linear\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/in/20150?v=4\",\n \"totalScore\": 10,\n \"prScore\": 0,\n \"issueScore\": 10,\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\": \"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\": \"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\": \"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\": \"flaviobruno72: Contributed by identifying a potential performance issue in the `elizaos/eliza` repository, opening issue #6267 to report a long wait time.\"\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\": 37,\n \"mergedPRs\": 21,\n \"newIssues\": 67,\n \"closedIssues\": 85,\n \"activeContributors\": 24\n}\n---\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[\"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-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-31T02:16:55.297998Z\n---\n2025-12-31\n---\nelizaOS/knowledge\n---\nelizaOS\n---\nknowledge\n---\nai_news_elizaos_discord_md_2025-12-30\n---\nai_news_elizaos_discord_md_2025-12-29\n---\nai_news_elizaos_discord_md_2025-12-28\n---\nai_news_elizaos_daily_json_2025-12-30\n---\nai_news_elizaos_daily_md_2025-12-30\n---\nai_news_elizaos_daily_discord_json_2025-12-30\n---\nai_news_elizaos_daily_discord_md_2025-12-30\n---\ngithub_summaries_week_latest_2025-12-21.md\n---\ngithub_summaries_month_latest_2025-12-01.md\n---\ngithub_summaries_daily_2025-12-31" ] }