{
"prompt_name": "discord-announcement",
"category": "comms",
"date": "2025-11-22",
"generated_text": "# \ud83d\ude80 Week of Victory: Server Tests Revamped & Token Migration Support Strengthened!\n\n## \ud83d\udd25 This Week in ElizaOS (Nov 16-22, 2025)\n\n* **Major Server Test Improvements** - Huge win this week as Stan's PR for MessageBusService integration tests was merged, completing our efforts to remove skipped tests and add proper helpers/fixtures across our server testing suite\n* **Plugin Format Flexibility** - We've expanded plugin dependency resolution to support both scoped package names and short names, making development smoother and more intuitive\n* **AI16z \u2192 ElizaOS Migration Support** - The team has committed to assisting users with manual migrations if exchanges don't implement automatic support before the February deadline\n* **Anthropic Integration Fixed** - Fixed an issue with Sonnet 4.0 model not properly closing XML tags, enhancing reliability of our AI responses\n* **Row-Level Security Optimized** - Server validation checks now correctly handle cases when RLS isolation is disabled\n\n## \ud83d\udcac Community Highlights\nThe community has been incredibly helpful with supporting each other through the token migration process. Special thanks to The Light for providing an excellent explanation about CEX token reserve dynamics and to jasyn_bjorn and Omid sa for their tireless support with migration questions.\n\n## \ud83d\udcb0 Token Updates\nMigration from ai16z to ElizaOS continues with a 90-day window (until February). All ElizaOS holders will be eligible for potential airdrops mentioned in relation to Babylon. If your tokens are on Kraken, the team will help with manual migration if needed!\n\n## \ud83d\udd2e Coming Next\nWe're continuing work on the Cloud project and exploring new integrations with Babylon. Stay tuned for more updates about the relationship between ElizaOS and Babylon tokens! Also watch for improved server tests as we eliminate more skipped tests.",
"source_references": [
"2025-11-22\n---\n2025-11-21.md\n---\n# elizaOS Discord - 2025-11-21\n\n## Overall Discussion Highlights\n\n### Token Migration (ai16z to ElizaOS)\n- The community is actively discussing the ongoing migration from ai16z to ElizaOS tokens\n- Users with tokens on centralized exchanges (particularly Kraken) are facing migration challenges\n- The migration period runs for 90 days (until February)\n- Team members have confirmed they will assist with manual migrations if exchanges fail to implement automatic migration\n- Some technical discussion about why CEXs might be slow to support token migrations, possibly related to insufficient token reserves\n\n### Development Updates\n- Stan mentioned splitting a large PR and improving server tests by removing skips and adding proper helpers\n- A Discord plugin PR (#23) was merged, potentially prematurely according to Odilitime\n- Issue identified with Anthropic's Sonnet 4.0 model not properly closing XML tags, possibly related to max token settings\n\n### Ecosystem Expansion\n- Brief mentions of Babylon waitlist and potential airdrops for ElizaOS holders\n- Questions about whether Babylon will have its own token and how it relates to ElizaOS\n- Discussion about a new game that received attention from notable Ethereum ecosystem figures (Vitalik, Davide from EF, and Tina from Flashbots)\n\n### Security Concerns\n- R0am raised a security concern regarding suspicious Zoom meeting requests\n\n## Key Questions & Answers\n\n**Q: When will Kraken migrate ai16z to ElizaOS?** \nA: Kraken has not announced anything yet (Serikiki)\n\n**Q: Was there a swap? Or people holding old token just lost?** \nA: There is a migration link available (validsyntax)\n\n**Q: Will airdrop be based on what you are holding or what you migrated?** \nA: All ElizaOS holders will be eligible (MDMnvest)\n\n**Q: Is ELIZAOS snapshot will happen for all chains?** \nA: Not confirmed, the team in #[channel] would know (The Light)\n\n## Community Help & Collaboration\n\n1. **CEX Migration Support**\n - jasyn_bjorn reassured Serikiki about tokens stuck on Kraken, confirming the team will help with manual migration if needed\n - Omid sa advised papa0901 about options for tokens withdrawn from Kraken: either deposit back and wait for migration announcement or contact support for manual migration\n - The Light provided a detailed explanation to Serikiki about how exchanges might operate with insufficient token reserves, creating complications during migrations\n\n2. **Development Assistance**\n - Loofi offered general development assistance to channel members, though no specific requests were made during this period\n\n## Action Items\n\n### Technical\n- Monitor Kraken's implementation of ai16z to ElizaOS migration (jasyn_bjorn)\n- Prepare for manual migration support if CEXs fail to implement (jasyn_bjorn)\n- Clarify token strategy regarding Babylon and its relationship to ElizaOS (pangolink)\n- Address issue with Anthropic's Sonnet 4.0 model not properly closing XML tags (mentioned in core-devs)\n\n### Documentation\n- Create clear guidelines for users with tokens stuck on exchanges (Omid sa)\n\n### Feature\n- Consider extending migration period if exchange issues persist (Bencus)\n- Restore X accounts for users (saypleaseno)\n- Improve server tests by removing skips and adding proper helpers and fixtures (Stan)\n---\n2025-11-20.md\n---\n# elizaOS Discord - 2025-11-20\n\n## Overall Discussion Highlights\n\n### Token Migration Issues\n- Users experiencing various problems with migration from AI16Z to ElizaOS\n- Migration cutoff date was November 11 at 11:40 UTC\n- Newly purchased AI16Z tokens after the cutoff cannot be migrated\n- \"Max amount reached\" errors reported by multiple users\n- Frustration from users who bought tokens after cutoff or had them on non-supporting exchanges\n- Community members repeatedly warning about scammers targeting users via DMs\n- Proper support channel is through the ticketing system\n- Some concerns about the team potentially selling migrated tokens (disputed by community)\n\n### Development Updates\n- PR #6135 under review - large code change that requires careful testing\n- PR #6164 approved and ready to be merged after branch update\n- Server tests now running in CI, helping detect issues earlier\n- Brief technical discussion about TEE (Trusted Execution Environment) vs. browser-based approaches\n- Reference to \"agent0\" as Marco's SDK for interacting with \"8004\" in \"Babylon\"\n\n### Community & Roles\n- Questions about partner and contributor roles\n- New developers introducing themselves (full-stack and blockchain developers)\n- Clarification that contributor role means they contributed to codebase but aren't team members\n\n### Future Features\n- Staking functionality mentioned but not yet implemented\n- Discussion about exchange listings\n\n## Key Questions & Answers\n\n**Q: How to open a ticket?** \nA: Use the support channel (Odilitime)\n\n**Q: Why was my partner role removed? I'm holding 1M Degenai in my wallet.** \nA: Use /verify command as Collab land was broken (Odilitime)\n\n**Q: Can I swap new buying of AI16z to ElizaOS?** \nA: No (satsbased)\n\n**Q: Why did the team create a new token?** \nA: The previous token is migrating because A16Z corp asked ELIZAOS to change its name for copyright issues (Omid sa)\n\n**Q: On which exchange is staking available for $ELIZAOS?** \nA: Staking has not started yet (MDMnvest)\n\n**Q: Should I buy AI16z or ElizaOS coins?** \nA: $elizaOS is the new token, AI16Z won't be supported anymore (MDMnvest)\n\n**Q: What does contributor role mean?** \nA: It means they have contributed to the codebase (jasyn_bjorn)\n\n**Q: Why are you selling users' migrated ai16z without permission?** \nA: LPers shouldn't be at risk, we're taking care of them manually (Odilitime)\n\n**Q: How should we handle the large PR #6135?** \nA: Have the user who experienced issues previously test it, and if it works on their system, merge it (Odilitime)\n\n## Community Help & Collaboration\n\n- **Migration Support**: Omid sa helped ryan67 who had tokens in Infinex during snapshot but couldn't migrate after transfer, directing them to the support channel\n- **Role Clarification**: jasyn_bjorn explained to velja that the contributor role means they contributed to codebase but aren't team members\n- **Migration Eligibility**: Omid sa explained to yyyy that tokens bought after November 11 cutoff can't be migrated\n- **Technical Explanation**: Shaw explained to DorianD that TEE and browser-based approaches have opposing security characteristics\n- **PR Review**: 0xbbjoker reviewed and approved Odilitime's PR #6164 with clear instructions for next steps\n\n## Action Items\n\n### Technical\n- Update branch and merge PR #6164 (mentioned by 0xbbjoker)\n- Have user test PR #6135 before merging (mentioned by Odilitime)\n- Continue ensuring server tests run in CI (mentioned by Stan \u26a1)\n- Fix \"max amount reached\" error in migration portal (mentioned by MATRIX)\n- Manual handling of liquidity providers affected by ai16z migration (mentioned by Odilitime)\n\n### Documentation\n- Create clear documentation about migration cutoff date and process (mentioned by multiple users)\n- Provide official foundation wallet addresses to counter misinformation (mentioned by Biazs)\n- Clarify the contributor role and its meaning (mentioned by velja)\n\n### Feature\n- Implement staking functionality for ElizaOS tokens (mentioned by \ud835\udde3\ud835\udde5\ud835\udddc\ud835\udde1\ud835\uddd6\ud835\uddd8)\n---\n2025-11-19.md\n---\n# elizaOS Discord - 2025-11-19\n\n**Date: November 19, 2025**\n\n## Overall Discussion Highlights\n\n### Token Migration\n- Migration from ai16z to elizaOS tokens is ongoing with a 6:1 conversion ratio\n- Migration portal will remain open until February 5, 2026\n- Eligibility is based on a snapshot from November 11, 2023 (11:40 UTC)\n- Several exchanges are handling migration automatically, though Kraken users reported delays\n- Manual migration via support tickets is available for users experiencing technical issues\n- Team tokens have a vesting schedule (3-month cliff + 9-month linear vest), but community tokens don't\n\n### Technical Development\n- Stan completed E2E authentication tests for Entity/server isolation\n- Added a real Postgres instance in CI for testing purposes\n- Work continues on PR #6135 with Stan taking over from Odilitime\n- Several PRs (#6143, #6142, #6114, #6107) are awaiting review\n- Discussions about running ElizaOS in browser-based TEEs on iOS devices\n- Questions raised about EIP-8004 support in Babylon's implementation\n- Plugin-twitter functionality appears to be experiencing issues\n\n### Developer Onboarding\n- ElizaOS is positioned as an agent framework rather than a traditional bot platform\n- TypeScript knowledge is essential for development, but React/Solidity aren't required initially\n- Official documentation at Eliza.how is recommended for proper onboarding\n- New developers are encouraged to learn the CLI tool and create their first agent\n\n### Security Concerns\n- Team is prioritizing security measures due to increased scammer activity\n- Some users expressed concerns about the legitimacy of manual migration instructions\n\n## Key Questions & Answers\n\n### Token Migration\n- **Q**: What happens to my ai16z tokens? \n **A**: You need to migrate them to elizaOS tokens through the official portal or wait for exchange announcements if held on exchanges\n\n- **Q**: What is the conversion ratio for ai16z to elizaOS? \n **A**: 1 ai16z equals 6 elizaOS tokens\n\n- **Q**: Until when can I migrate my tokens? \n **A**: The web portal is open until February 5, 2026\n\n- **Q**: Why don't my tokens appear in the migration portal? \n **A**: Only tokens held before November 11, 11:40 UTC are eligible; if experiencing technical issues, use the support ticket system\n\n- **Q**: Is there vesting for community tokens? \n **A**: No, the vesting schedule only applies to team tokens\n\n- **Q**: What if I had my tokens in farming pools? \n **A**: If your tokens were in a farm before the snapshot date, you need to proceed through manual migration via support ticket\n\n### Development\n- **Q**: Can ElizaOS runtime run in browser to make a dedicated iOS app using TEE tech for agent enclaves? \n **A**: In theory, yes\n\n- **Q**: How can I start developing using ElizaOS with my current JavaScript knowledge? \n **A**: You need to know TypeScript and learn ElizaOS. Start with Eliza.how and complete the framework guide\n\n- **Q**: Do I need Solidity or React to use ElizaOS? \n **A**: No, you don't need React nor Solidity to start\n\n- **Q**: Can I use ElizaOS for creating a trading bot and monetize it? \n **A**: First understand how it works, then create a trading agent (not bot). Check Eliza.how, learn CLI tool and create your first agent\n\n- **Q**: Can I continue your work on PR #6135? \n **A**: Please continue. That one took a long time, so it probably better to continue than to restart\n\n## Community Help & Collaboration\n\n1. **Migration Support**:\n - jasyn_bjorn helped Junaid Ali by confirming the legitimacy of the manual migration process\n - hns71 assisted F&M who was confused about the migration process and concerned about scams\n - Odilitime advised F&M about opening a support ticket when experiencing migration portal issues\n - Toni directed 0xYogi to the migration helper and support ticket system for technical assistance\n - Borko provided digitalalchemy with links to official token addresses documentation\n\n2. **Developer Guidance**:\n - vaipraonde helped amnesia understand the prerequisites for ElizaOS development, clarifying that TypeScript knowledge is needed but React/Solidity aren't required initially\n - Odilitime directed Issa_arts to post in a more appropriate channel for their art-related content\n\n3. **Team Collaboration**:\n - Stan offered to continue work on PR #6135 that Odilitime had started but hadn't completed\n - Stan provided a standup update about completed work and requested reviews for several PRs\n\n## Action Items\n\n### Technical\n- Fix migration portal issues where users' tokens aren't showing up after wallet connection (Mentioned by Multiple users)\n- Address indefinite loading issue on migration portal (Mentioned by F&M)\n- Improve support ticket response time (currently delayed due to Cloudflare outage) (Mentioned by Odilitime)\n- Investigate browser-based TEE implementation for ElizaOS on iOS (Mentioned by DorianD)\n- Resolve token migration issues for users whose tokens don't appear (Mentioned by 00bigmac, kil)\n- Continue work on PR #6135 (Mentioned by Stan \u26a1)\n- Review PRs #6143, #6142, #6114, and #6107 (Mentioned by Stan \u26a1)\n- Continue optimizing server tests (Mentioned by Stan \u26a1)\n- Fix plugin-twitter functionality (Mentioned by Odilitime)\n- Prioritize safety/security measures to address scammer activity (Mentioned by Kenk)\n\n### Documentation\n- Create clearer documentation about manual migration process for tokens in farming pools (Mentioned by Rainman)\n- Publish official manual migration instructions on website to prevent scam concerns (Mentioned by Junaid Ali)\n- Create FAQ about exchange-specific migration timelines (Mentioned by Serikiki)\n- Create clearer onboarding path for JavaScript developers (Mentioned by amnesia)\n\n### Feature\n- Develop farming options for elizaOS tokens (Mentioned by Rainman)\n- Clarify integration between Babylon's EIP-8004 implementation and ElizaOS (Mentioned by DorianD)\n- Continue exploring Cloud project (Mentioned by Stan \u26a1)\n---\n2025-11-21.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-11-21\n---\nGitHub Activity Summary\n---\nFrom November 21-22, 2025, the elizaOS/eliza repository showed active development with 2 new pull requests, both of which were successfully merged. There were no new issues reported during this period. The repository had 5 active contributors participating in development activities.\n---\nPull Requests\n---\nPR #6165 by @standujar titled 'fix(server): update MessageBusService integration tests' is merged\n---\nPR #6166 by @odilitime titled 'fix: topP support for anthropic PR' is open\n---\nhttps://github.com/elizaOS/eliza/pull/6166\n---\nPR #6164 titled 'feat: improve accepted formats for plugin names in plugin dependencies' is merged\n---\nhttps://github.com/elizaOS/eliza/pull/6164\n---\nSummary for github_other\n---\nThe repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-11-21.md\n---\n# Daily Report - 2025-11-21\n\n## GitHub Activity Summary\n- From November 21-22, 2025, the elizaOS/eliza repository showed active development with 2 new pull requests, both of which were successfully merged. There were no new issues reported during this period. The repository had 5 active contributors participating in development activities.\n\n## Pull Requests\n- PR #6165 by @standujar titled 'fix(server): update MessageBusService integration tests' is merged\n- PR #6166 by @odilitime titled 'fix: topP support for anthropic PR' is open (Source: https://github.com/elizaOS/eliza/pull/6166)\n- PR #6164 titled 'feat: improve accepted formats for plugin names in plugin dependencies' is merged (Source: https://github.com/elizaOS/eliza/pull/6164)\n\n## Summary for github_other\n- The repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-11-21.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-11-21\n---\n1253563209462448241\n---\n\ud83d\udcac-discussion\n---\n# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily revolves around the migration from ai16z to ElizaOS tokens and issues users are facing with centralized exchanges (CEXs), particularly Kraken. Users holding ai16z on Kraken are concerned about being unable to migrate their tokens, as Kraken hasn't yet implemented automatic migration. The team has advised these users to keep their tokens on Kraken and wait for the exchange to support the migration, with manual migration as a backup option. \n\nThere was an informative technical discussion about how CEXs might operate with insufficient token reserves, potentially explaining why some exchanges are slow to support the migration. The conversation suggests that exchanges might be selling tokens they don't fully possess, creating complications during migrations when they need to acquire the actual tokens.\n\nThe migration period appears to run for 90 days (until February), giving exchanges time to implement support. The team has indicated they will help with manual migrations if necessary, though they prefer exchanges handle it automatically to avoid overwhelming their support system.\n\nAdditionally, there were brief mentions of Babylon waitlist and potential airdrops for ElizaOS holders, though with limited technical details.\n\n## 2. FAQ\nQ: Does anyone have ElizaOS up and running? I just want to test chat with the ai (asked by alfirusahmad) A: Unanswered\nQ: When will Kraken migrate ai16z to ElizaOS? (asked by papa0901) A: Kraken did not announce anything yet (answered by Serikiki)\nQ: Was there a swap? Or people holding old token just lost? (asked by validsyntax) A: Oh ok I see migration link (answered by validsyntax)\nQ: Will airdrop be based on what you are holding or what you migrated? (asked by Natefrog) A: All ElizaOS holders! (answered by MDMnvest)\nQ: Is ELIZAOS snapshot will happen for all chains? (asked by Omid sa) A: Not sure, <#1425417640071139358> would know (answered by The Light)\nQ: How much time left for Babylon waitlist? (asked by Omid sa) A: Unanswered\n\n## 3. Help Interactions\nHelper: jasyn_bjorn | Helpee: Serikiki | Context: User concerned about tokens stuck on Kraken | Resolution: Confirmed team will help with manual migration if needed but prefers Kraken to auto-migrate\nHelper: Omid sa | Helpee: papa0901 | Context: User confused about what to do with tokens withdrawn from Kraken | Resolution: Advised to either deposit back to Kraken and wait for migration announcement or contact support for manual migration after Kraken completes the swap\nHelper: The Light | Helpee: Serikiki | Context: Explaining why CEXs might be slow to support token migrations | Resolution: Detailed explanation about how exchanges might operate with insufficient token reserves, creating complications during migrations\n\n## 4. Action Items\nTechnical: Monitor Kraken's implementation of ai16z to ElizaOS migration | Description: Track progress and ensure users' tokens are properly migrated | Mentioned By: jasyn_bjorn\nTechnical: Prepare for manual migration support if CEXs fail to implement | Description: Have systems ready to handle manual migration requests from CEX users | Mentioned By: jasyn_bjorn\nDocumentation: Create clear guidelines for users with tokens stuck on exchanges | Description: Document the process for users who need manual migration assistance | Mentioned By: Omid sa\nFeature: Consider extending migration period if exchange issues persist | Description: 90-day migration window might need extension if CEXs continue to delay support | Mentioned By: Bencus\n---\n1300025221834739744\n---\n\ud83d\udcac-coders\n---\n# Analysis of \ud83d\udcac-coders Discord Channel\n\n## 1. Summary\nThe chat segment shows minimal technical discussion. There are no substantive coding conversations, problem-solving, or technical implementations visible in this transcript. The messages consist primarily of greetings, a GIF share, a tool promotion (Greptile), a request for an activation code, and an offer from a user named Loofi to help with development. No specific technical topics, code snippets, or programming challenges were discussed during this period.\n\n## 2. FAQ\nQ: I need an activation code, I've been subscribed to your channel for 5 months, can I get an invite code for registration? (asked by salvadore7663) A: Unanswered\n\n## 3. Help Interactions\nHelper: Loofi | Helpee: Channel members | Context: Offered general development assistance | Resolution: No specific help was provided as no one requested assistance during this chat segment\n\n## 4. Action Items\nNo specific action items were identified in this chat segment.\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\n# Analysis of \ud83e\udd47-partners Discord Channel\n\n## 1. Summary\nThe chat segment is very brief and contains minimal technical discussion. There are mentions of a new game that received attention from notable figures in the Ethereum ecosystem (Vitalik, Davide from EF, and Tina from Flashbots). There's also a question about Babylon having its own token and its relationship to ElizaOS. The conversation lacks detailed technical discussions, problem-solving, or implementation details. One user inquires about restoring X accounts, but no resolution is provided in the transcript.\n\n## 2. FAQ\nQ: Any news about restoring the X accounts? (asked by saypleaseno) A: Unanswered\nQ: Babylon is going to have its own token? (asked by pangolink) A: Unanswered\nQ: Is the play to create a network of tokens that feed ElizaOS or are we just popping off tokens for fun? (asked by pangolink) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions are present in this chat segment.\n\n## 4. Action Items\nFeature: Restore X accounts | Description: Restoring X accounts for users | Mentioned By: saypleaseno\nTechnical: Clarify token strategy | Description: Clarify if Babylon will have its own token and how it relates to ElizaOS | Mentioned By: pangolink\n---\n1377726087789940836\n---\ncore-devs\n---\nThe chat segment shows minimal technical discussion among core developers. Stan mentioned splitting a large PR and improving server tests by removing skips and adding proper helpers and fixtures to reduce duplication. Odilitime referenced a PR (#23) for the Discord plugin that was merged, perhaps prematurely. There was also a brief mention of an issue with Anthropic's Sonnet 4.0 model not properly closing XML tags, potentially related to max token settings. A security concern was raised by R0am regarding suspicious Zoom meeting requests. Overall, this segment contains limited technical substance, focusing mainly on brief updates and a security warning rather than in-depth technical discussions.\n---\n2025-11-21.md\n---\n# elizaOS Discord - 2025-11-21\n\n## Overall Discussion Highlights\n\n### Token Migration (ai16z to ElizaOS)\n- The community is actively discussing the ongoing migration from ai16z to ElizaOS tokens\n- Users with tokens on centralized exchanges (particularly Kraken) are facing migration challenges\n- The migration period runs for 90 days (until February)\n- Team members have confirmed they will assist with manual migrations if exchanges fail to implement automatic migration\n- Some technical discussion about why CEXs might be slow to support token migrations, possibly related to insufficient token reserves\n\n### Development Updates\n- Stan mentioned splitting a large PR and improving server tests by removing skips and adding proper helpers\n- A Discord plugin PR (#23) was merged, potentially prematurely according to Odilitime\n- Issue identified with Anthropic's Sonnet 4.0 model not properly closing XML tags, possibly related to max token settings\n\n### Ecosystem Expansion\n- Brief mentions of Babylon waitlist and potential airdrops for ElizaOS holders\n- Questions about whether Babylon will have its own token and how it relates to ElizaOS\n- Discussion about a new game that received attention from notable Ethereum ecosystem figures (Vitalik, Davide from EF, and Tina from Flashbots)\n\n### Security Concerns\n- R0am raised a security concern regarding suspicious Zoom meeting requests\n\n## Key Questions & Answers\n\n**Q: When will Kraken migrate ai16z to ElizaOS?** \nA: Kraken has not announced anything yet (Serikiki)\n\n**Q: Was there a swap? Or people holding old token just lost?** \nA: There is a migration link available (validsyntax)\n\n**Q: Will airdrop be based on what you are holding or what you migrated?** \nA: All ElizaOS holders will be eligible (MDMnvest)\n\n**Q: Is ELIZAOS snapshot will happen for all chains?** \nA: Not confirmed, the team in #[channel] would know (The Light)\n\n## Community Help & Collaboration\n\n1. **CEX Migration Support**\n - jasyn_bjorn reassured Serikiki about tokens stuck on Kraken, confirming the team will help with manual migration if needed\n - Omid sa advised papa0901 about options for tokens withdrawn from Kraken: either deposit back and wait for migration announcement or contact support for manual migration\n - The Light provided a detailed explanation to Serikiki about how exchanges might operate with insufficient token reserves, creating complications during migrations\n\n2. **Development Assistance**\n - Loofi offered general development assistance to channel members, though no specific requests were made during this period\n\n## Action Items\n\n### Technical\n- Monitor Kraken's implementation of ai16z to ElizaOS migration (jasyn_bjorn)\n- Prepare for manual migration support if CEXs fail to implement (jasyn_bjorn)\n- Clarify token strategy regarding Babylon and its relationship to ElizaOS (pangolink)\n- Address issue with Anthropic's Sonnet 4.0 model not properly closing XML tags (mentioned in core-devs)\n\n### Documentation\n- Create clear guidelines for users with tokens stuck on exchanges (Omid sa)\n\n### Feature\n- Consider extending migration period if exchange issues persist (Bencus)\n- Restore X accounts for users (saypleaseno)\n- Improve server tests by removing skips and adding proper helpers and fixtures (Stan)\n---\n2025-11-22.md\n---\nFile not found\n---\n2025-11-16.md\n---\n# elizaos/eliza Weekly Report (Nov 16 - 22, 2025)\n\n## \ud83d\ude80 Highlights\nThis week's efforts balanced proactive technical debt reduction with responsiveness to critical user feedback. The most significant achievement was the migration of the core package away from a deprecated LangChain version, ensuring long-term stability. Concurrently, the team triaged a number of new user-reported issues, including a critical migration problem and several feature requests for new integrations and UI improvements. This activity highlights a healthy feedback loop between the development team and the project's active user base.\n\n## \ud83d\udee0\ufe0f Key Developments\nWork this week focused on modernizing dependencies and performing routine documentation maintenance.\n\n- **Core Dependency Modernization:** A major effort was completed to enhance the stability of `@elizaos/core` by migrating from the deprecated `langchain` v0.3 to `@langchain/textsplitters v1.0`. This involved updating dependencies, import paths, and removing outdated resolutions from plugin starter packages, resolving a long-standing deprecation issue ([#6152](https://github.com/elizaos/eliza/pull/6152)).\n\n- **Documentation & Maintenance:** To improve user experience and accuracy, outdated links in the `packages/cli/README.md` were corrected ([#6050](https://github.com/elizaos/eliza/pull/6050)). A new pull request was also opened to improve markdown spacing compactness ([#6159](https://github.com/elizaos/eliza/pull/6159)). Additionally, a minor dependency bump for `glob` from `11.0.3` to `11.1.0` was proposed ([#6157](https://github.com/elizaos/eliza/pull/6157)).\n\n## \ud83d\udc1b Issues & Triage\nThe week saw one key issue resolved while several new critical issues and feature requests were opened, indicating active community engagement.\n\n- **Closed Issues:** The primary issue closed this week concerned the deprecation of LangChain v0.3 ([#6145](https://github.com/elizaos/eliza/issues/6145)). This was resolved by the successful migration to `@langchain/textsplitters` in PR [#6152](https://github.com/elizaos/eliza/pull/6152).\n\n- **New & Active Issues:** Several important issues were reported by the community:\n - **Critical Migration Issue:** A user reported significant problems with the AI16Z \u2192 ElizaOS migration, including snapshot eligibility and unsupported Tangem Wallet connections. This is a high-priority issue tracked in [#6158](https://github.com/elizaos/eliza/issues/6158).\n - **Feature Requests:** The community proposed several enhancements, including potential integration of the DeepSeek API ([#6156](https://github.com/elizaos/eliza/issues/6156]), support for Farcaster and Base applications ([#6161](https://github.com/elizaos/eliza/issues/6161)), and a UI improvement to make addresses clickable hyperlinks ([#6160](https://github.com/elizaos/eliza/issues/6160)).\n\n## \ud83d\udcac Community & Collaboration\nWhile there were no reports of high-volume discussions on specific PRs, community engagement was evident through the influx of new issues. Users are actively testing the system and providing valuable feedback, from identifying critical bugs like the migration issue ([#6158](https://github.com/elizaos/eliza/issues/6158)) to suggesting future directions for the project with feature requests for new API integrations and ecosystem support. The report of a compromised Discord channel within an issue highlights the community's role in safeguarding the project's communication channels.\n---\n2025-11-01.md\n---\n# elizaos/eliza Monthly Report (November 2025)\n\n## \ud83d\ude80 Highlights\nNovember kicked off with a dual focus on enhancing system stability and laying the groundwork for significant new capabilities. A critical bug affecting agent settings persistence was resolved, directly improving the framework's reliability. Concurrently, new development was initiated to introduce entity-level security and enhance the core runtime. The opening of several strategic issues signals a forward-looking push towards improved performance through parallel actions and background tasks, as well as new user engagement features.\n\n## \ud83d\udee0\ufe0f Key Developments\nWork this month balanced immediate fixes with the introduction of new features.\n\n- **Agent Stability Improvement**\n A significant bug was fixed that prevented agent settings from persisting across restarts, ensuring that runtime-generated configurations are now correctly retained. This change, made to the core runtime initialization logic, enhances the overall reliability of agent operations ([#6106](https://github.com/elizaos/eliza/pull/6106)).\n\n- **New Feature Initiatives**\n Development began on several new fronts with the opening of new pull requests:\n - **Security:** A proposal was made to implement entity-level row-level security, aiming to add more granular data access controls ([#6107](https://github.com/elizaos/eliza/pull/6107)).\n - **Runtime Enhancements:** Work started on adding an ElizaOS reference directly to the runtime, likely to streamline framework interactions ([#6111](https://github.com/elizaos/eliza/pull/6111)).\n\n## \ud83d\udc1b Issues & Triage\nIssue tracking this month was focused on defining the next wave of development priorities.\n\n- **Closed Issues:** No issues were closed during this period.\n\n- **New & Active Issues:** Several key issues were opened, outlining major areas for future work:\n - **Core Functionality & Performance:** Discussions were initiated around implementing \"Parallel actions\" ([#6108](https://github.com/elizaos/eliza/issues/6108)) and \"Background tasks\" ([#6109](https://github.com/elizaos/eliza/issues/6109)), indicating a focus on scaling the system's operational capacity.\n - **Security & User Engagement:** New issues were created for \"Entity-level RLS\" ([#6112](https://github.com/elizaos/eliza/issues/6112)), which complements the ongoing PR, and a \"Points / Leaderboard\" system ([#6110](https://github.com/elizaos/eliza/issues/6110)) to enhance user interaction.\n - According to the reports, none of the active issues have generated more than three comments, suggesting discussions are still in their early stages.\n\n## \ud83d\udcac Community & Collaboration\nThe provided reports indicate a period of focused, heads-down development. While new pull requests and issues were opened, the data does not show any high-volume discussions or specific collaborative events. The alignment between the new pull request for RLS ([#6107](https://github.com/elizaos/eliza/pull/6107)) and the corresponding new issue ([#6112](https://github.com/elizaos/eliza/issues/6112)) suggests coordinated planning around new features.\n---\n{\n \"interval\": {\n \"intervalStart\": \"2025-11-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-12-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-11-01 to 2025-12-01, elizaos/eliza had 22 new PRs (14 merged), 38 new issues, and 24 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs7XCsUe\",\n \"title\": \"Bug: Disabling Web UI blocks all endpoints\",\n \"author\": \"humuhimi\",\n \"number\": 6138,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"\",\n \"createdAt\": \"2025-11-10T12:26:11Z\",\n \"closedAt\": \"2025-11-10T12:47:31Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 2\n },\n {\n \"id\": \"I_kwDOMT5cIs7V2H1G\",\n \"title\": \"Support Tasks\",\n \"author\": \"borisudovicic\",\n \"number\": 6131,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"* Collaborate with CJ on anonymous ID + free inference architecture.\",\n \"createdAt\": \"2025-11-04T18:16:47Z\",\n \"closedAt\": \"2025-11-08T12:37:51Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 1\n },\n {\n \"id\": \"I_kwDOMT5cIs7V2Hh0\",\n \"title\": \"Voice Infrastructure\",\n \"author\": \"borisudovicic\",\n \"number\": 6130,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"* Test browser-based voice generation (client-side).\\n* Prepare optional **server voice endpoint** for paid users.\\n* Support Compute embeddings integration.\",\n \"createdAt\": \"2025-11-04T18:16:25Z\",\n \"closedAt\": \"2025-11-14T13:34:37Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 1\n },\n {\n \"id\": \"I_kwDOMT5cIs7V2HTC\",\n \"title\": \"Plugin-Cloud Testing\",\n \"author\": \"borisudovicic\",\n \"number\": 6129,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"* Test plugin-cloud within Eliza Framework.\\n* Verify tool registration + documentation accuracy.\",\n \"createdAt\": \"2025-11-04T18:16:06Z\",\n \"closedAt\": \"2025-11-14T13:34:38Z\",\n \"state\": \"CLOSED\",\n \"commentCount\": 1\n },\n {\n \"id\": \"I_kwDOMT5cIs7V2Gw0\",\n \"title\": \"Docs\",\n \"author\": \"borisudovicic\",\n \"number\": 6128,\n \"repository\": \"elizaos/eliza\",\n \"body\": \"* Build new /docs UI (public, not auth-locked).\\n* Include:\\n * OpenAI-style API explorer.\\n * Character setup & API key usage examples.\\n * Overview of Cloud architecture.\",\n \"createdAt\": \"2025-11-04T18:15:26Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 1\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6xETJ-\",\n \"title\": \"feat: implement entity-level row level security\",\n \"author\": \"standujar\",\n \"number\": 6107,\n \"body\": \"\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-11-02T16:12:48Z\",\n \"mergedAt\": null,\n \"additions\": 11656,\n \"deletions\": 2228\n },\n {\n \"id\": \"PR_kwDOMT5cIs6vVL6j\",\n \"title\": \"feat: create @elizaos/react package with headless React hooks\",\n \"author\": \"wtfsayo\",\n \"number\": 6093,\n \"body\": \"## Overview\\n\\nThis PR introduces a new **** package containing headless, reusable React hooks extracted from the client package. This enables external developers to build custom UIs for ElizaOS agents while maintaining full type safety and React Query integration.\\n\\n## What's New\\n\\n### Package: \\n\\nA standalone package providing headless React hooks with:\\n- \u2705 Zero UI coupling (no toasts, navigation, or DOM dependencies)\\n- \u2705 Full TypeScript support with proper type declarations\\n- \u2705 TanStack React Query for caching and state management\\n- \u2705 Network-aware polling that adapts to connection quality\\n- \u2705 Composable lifecycle callbacks (onSuccess, onError, onMutate)\\n\\n### Hooks Included (30 total)\\n\\n**Agents (8 hooks)**\\n- `useAgents`, `useAgent`, `useStartAgent`, `useStopAgent`\\n- `useAgentActions`, `useDeleteLog`, `useAgentPanels`, `useAgentsWithDetails`\\n\\n**Runs (2 hooks)**\\n- `useAgentRuns`, `useAgentRunDetail`\\n\\n**Messaging (5 hooks)**\\n- `useServers`, `useChannels`, `useChannelDetails`, `useChannelParticipants`, `useDeleteChannel`\\n\\n**Messages (3 hooks)**\\n- `useChannelMessages` (stateful with pagination), `useDeleteChannelMessage`, `useClearChannelMessages`\\n\\n**Memories (6 hooks)**\\n- `useAgentMemories`, `useDeleteMemory`, `useDeleteAllMemories`, `useUpdateMemory`, `useDeleteGroupMemory`, `useClearGroupChat`\\n\\n**Internal/Agent-Perspective (6 hooks)**\\n- `useAgentInternalActions`, `useDeleteAgentInternalLog`, `useAgentInternalMemories`\\n- `useDeleteAgentInternalMemory`, `useDeleteAllAgentInternalMemories`, `useUpdateAgentInternalMemory`\\n\\n## Architecture\\n\\n```tsx\\nimport { QueryClient, QueryClientProvider } from '@tanstack/react-query';\\nimport { ElizaReactProvider, useAgents, useStartAgent } from '@elizaos/react';\\n\\nconst queryClient = new QueryClient();\\n\\nfunction App() {\\n return (\\n \\n \\n \\n \\n \\n );\\n}\\n\\nfunction AgentList() {\\n const { data: agents, isLoading } = useAgents();\\n const startAgent = useStartAgent({\\n onSuccess: () => toast.success('Agent started!'),\\n });\\n\\n if (isLoading) return
Loading...
;\\n\\n return (\\n
\\n {agents?.map((agent) => (\\n
\\n
{agent.name}
\\n \\n
\\n ))}\\n
\\n );\\n}\\n```\\n\\n## Benefits\\n\\n1. **Reusability**: External developers can build custom UIs using these hooks\\n2. **Type Safety**: Full TypeScript support with types from `@elizaos/api-client`\\n3. **Performance**: Smart polling adapts to network quality (2G \u2192 4G)\\n4. **Separation of Concerns**: UI logic stays in components, data logic in hooks\\n5. **Future-proof**: Ready for migration of `packages/client` to consume these hooks\\n\\n## Testing\\n\\n- \u2705 Package builds successfully with TypeScript declarations\\n- \u2705 All hooks properly typed with React Query v5 signatures\\n- \u2705 Zero build errors or type issues\\n- \u2705 Ready for integration into turbo build pipeline\\n\\n## Next Steps (Future PRs)\\n\\n- Migrate `packages/client` to consume `@elizaos/react`\\n- Add unit tests for hooks with mocked ElizaClient\\n- Publish to npm for external consumption\\n\\n## Files Changed\\n\\n- `packages/react/` - New package with provider, hooks, and documentation\\n- Comprehensive README with installation, API reference, and examples\\n\\n---\\n\\n**Ready for review!** \ud83d\ude80\\n\\n\\n---\\n\\n> [!NOTE]\\n> Introduces a new `@elizaos/react` package with headless, type-safe React hooks and provider (plus build/docs), integrates it into the workspace, and publishes comprehensive core type declarations.\\n> \\n> - **New package `@elizaos/react`**:\\n> - Headless React hooks and provider (`ElizaReactProvider`) built on `@tanstack/react-query` and `@elizaos/api-client`.\\n> - Hooks for: agents, runs, messaging (servers/channels), messages (stateful + pagination), memories, and internal agent-perspective operations.\\n> - Network-aware polling, composable mutation callbacks, TypeScript types, and index exports.\\n> - Build tooling (`build.ts`, bunfig, tsconfigs), and comprehensive README.\\n> - **Workspace integration**:\\n> - Added to lockfile/workspace with peer/dev deps.\\n> - **Type declarations**:\\n> - Added/updated numerous `@elizaos/core` `.d.ts` and source maps to expose APIs/types for consumers.\\n> \\n> Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 5a290e0071637d785858567d960ab7d1d5e54456. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-10-23T18:06:32Z\",\n \"mergedAt\": null,\n \"additions\": 8223,\n \"deletions\": 1753\n },\n {\n \"id\": \"PR_kwDOMT5cIs6xVUO6\",\n \"title\": \"feat: x402 middleware\",\n \"author\": \"odilitime\",\n \"number\": 6114,\n \"body\": \"pulled enhanced response & health check from Otaku\\r\\n\\r\\n\\n\\n---\\n\\n> [!NOTE]\\n> Introduces x402 payment protection for plugin routes (EVM/Solana), adds core payment types, integrates verification and x402scan 402 responses, plus config registry, docs, and tests.\\n> \\n> - **Server (x402 middleware)**:\\n> - Add payment middleware (`x402/`) with EVM (EIP-712/ERC-3009) and Solana verification, facilitator payment ID support, and x402scan-compliant 402 responses.\\n> - Integrate into plugin routing to auto-wrap routes with `x402` config (`createPaymentAwareHandler`, `applyPaymentProtection`).\\n> - Expose middleware/types via `middleware/index.ts` and `x402/index.ts`.\\n> - **Core Types**:\\n> - Add payment types (`PaymentEnabledRoute`, `X402Config`, validators, OpenAPI helpers) in `@elizaos/core` (`types/payment.ts` and export in `types/index.ts`).\\n> - **Config & Utilities**:\\n> - Add payment config registry (`payment-config.ts`) with built-in configs (`base_usdc`, `solana_usdc`, `polygon_usdc`), CAIP-19 generation, pricing helpers, health reporting.\\n> - Define strict x402 schemas (`x402-types.ts`) and request/response/runtime types (`types.ts`).\\n> - **API Integration**:\\n> - Update `api/index.ts` to use payment-aware handlers for plugin routes.\\n> - **Docs & Tests**:\\n> - Add comprehensive README for x402 usage.\\n> - Add extensive tests for amount conversion, verification logic, integration, config, and schema validation.\\n> - **Dependencies**:\\n> - Add `viem`, `@solana/web3.js`, and `cors` to server; lockfile updates.\\n> \\n> Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit d64e2a5e1045bc204ffb435d0ef74a044efe1287. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-11-04T06:10:07Z\",\n \"mergedAt\": null,\n \"additions\": 5434,\n \"deletions\": 10\n },\n {\n \"id\": \"PR_kwDOMT5cIs6xzKBP\",\n \"title\": \"fix: align server tests with ElizaOS API changes\",\n \"author\": \"odilitime\",\n \"number\": 6135,\n \"body\": \"\\n> [!NOTE]\\n> Aligns server tests and routers with new ElizaOS interfaces, clarifies plugin auto-injection behavior, and deflakes/modernizes middleware, loader, socket, and utility tests.\\n> \\n> - **Server/API alignment**:\\n> - Update `agentExistsMiddleware`, Socket.IO router, Jobs and Agent Runs routers to use `ElizaOS` getters instead of agent maps.\\n> - Adjust message flow and log streaming tests to new event/filter semantics.\\n> - **Plugin loading behavior**:\\n> - Clarify that server auto-injects `sql` plugin; bootstrap injection handled at character level; ensure deduping and order expectations.\\n> - **Test refactors/deflakes**:\\n> - Replace heavy `mock.module` with spies and lightweight mocks; remove brittle fs mocks.\\n> - Skip flaky/integration suites causing interference (version, DB ops, message bus, agent runs, some jobs tests).\\n> - **Utilities and middleware**:\\n> - Update tests for `authMiddleware`, validation, security headers, rate limits.\\n> - Adjust `sanitizeFilename` expectations and `resolvePgliteDir` behavior; strengthen path handling assertions.\\n> - **Misc**:\\n> - Minor type/interface tweaks (e.g., runtime methods) and improved express server boot/teardown in tests.\\n> \\n> Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit a988400e95a3efe7e9366332d18e83a99429c2f2. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).\\n\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **Bug Fixes**\\n * Improved plugin loading flexibility: server now recognizes both short and full bootstrap plugin identifiers during initialization.\\n * Enhanced SQL plugin auto-injection and plugin deduplication logic.\\n\\n* **Refactor**\\n * Removed internal loader APIs: `tryLoadFile` and `loadCharacterTryPath` functions are no longer available.\\n * Updated core routing infrastructure for improved agent management.\\n * Simplified test infrastructure by reducing mock dependencies and improving test reliability across environments.\\n\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-11-06T04:07:48Z\",\n \"mergedAt\": \"2025-11-20T23:02:50Z\",\n \"additions\": 4294,\n \"deletions\": 4383\n },\n {\n \"id\": \"PR_kwDOMT5cIs6zHHko\",\n \"title\": \"fix: plugin-mysql support, initPromise and other minor fixes\",\n \"author\": \"odilitime\",\n \"number\": 6143,\n \"body\": \"\\n> [!NOTE]\\n> Adds conditional MySQL vs SQL plugin selection (with URL validation and MySQL no-op migrations), introduces runtime initPromise, updates mocks, and adds comprehensive tests.\\n> \\n> - **Server**:\\n> - **Database plugin selection**: Dynamically load `@elizaos/plugin-mysql` when `MYSQL_URL` is set; otherwise use `@elizaos/plugin-sql`.\\n> - **Utilities**: Add `validateAndLogMySQLUrl` and `MySQLNoOpMigrationService` for MySQL.\\n> - **RLS**: Enable only for PostgreSQL; skip/cleanup when using MySQL.\\n> - **DB ops**: Parameterized default server creation with dialect-specific upsert (`ON DUPLICATE KEY UPDATE` vs `ON CONFLICT`).\\n> - **Logging**: Trim verbose route-matching logs; minor try/catch cleanup.\\n> - **CLI (Scenario)**:\\n> - Plugin selection prefers MySQL when `MYSQL_URL` or explicit plugin present; otherwise SQL.\\n> - Avoid loading both `plugin-sql` and `plugin-mysql`; only set `PGLITE_DATA_DIR` for SQL.\\n> - **Core**:\\n> - Add `initPromise: Promise` to `IAgentRuntime`.\\n> - **Test Utils**:\\n> - Mock runtime gains pending `initPromise` with `resolveInit`/`rejectInit`; mocks migrated to `bun:test`.\\n> - **Tests**:\\n> - New tests for scenario plugin selection, server MySQL compatibility/behavior, and runtime/mock `initPromise` semantics.\\n> \\n> Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 96c2b1df774f0e6c889e7ac22a33d9e03599c317. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).\\n\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n* **New Features**\\n * Added support for flexible database provider selection, allowing configuration with either MySQL or PostgreSQL through environment variables.\\n\\n* **Improvements**\\n * Updated security features to conditionally enable based on your database provider.\\n * Enhanced Content Security Policy configuration and database initialization flow.\\n\\n\",\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-11-13T01:58:45Z\",\n \"mergedAt\": null,\n \"additions\": 2015,\n \"deletions\": 369\n }\n ],\n \"codeChanges\": {\n \"additions\": 6972,\n \"deletions\": 5642,\n \"files\": 100,\n \"commitCount\": 238\n },\n \"completedItems\": [\n {\n \"title\": \"docs: fix old links to actual\",\n \"prNumber\": 6050,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n\\r\\n## What does thi\",\n \"files\": [\n \"packages/cli/README.md\"\n ]\n },\n {\n \"title\": \"fix: agent settings persistence across restarts\",\n \"prNumber\": 6106,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nFixes agent settings not persisting across restarts, causing runtime-generated configuration to be lost.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low risk**\\r\\n\\r\\n- Changes core runtime initialization logic for agent settings merge\\r\\n- All existing test\",\n \"files\": [\n \"packages/core/src/__tests__/ensure-agent-exists.test.ts\",\n \"packages/core/src/runtime.ts\"\n ]\n },\n {\n \"title\": \"feat: add ElizaOS reference to runtime\",\n \"prNumber\": 6111,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nRelates to #6095 - Unified messaging API\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low risk**\\r\\n\\r\\nThis change is non-breaking and \",\n \"files\": [\n \"packages/core/src/__tests__/elizaos.test.ts\",\n \"packages/core/src/elizaos.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/types/elizaos.ts\",\n \"packages/core/src/types/index.ts\",\n \"packages/core/src/types/runtime.ts\",\n \"packages/plugin-sql/src/__tests__/integration/postgres-init.test.ts\",\n \"packages/plugin-sql/src/__tests__/unit/index.test.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/server/src/__tests__/integration/jobs-message-flow.test.ts\",\n \"packages/core/src/__tests__/runtime-embedding.test.ts\"\n ]\n },\n {\n \"title\": \"fix(plugin-sql): correct types path in package.json exports\",\n \"prNumber\": 6134,\n \"type\": \"bugfix\",\n \"body\": \"- Fix incorrect types path from ./types/index.d.ts to ./dist/index.d.ts\\r\\n- Remove non-existent 'types' directory from files array\\r\\n- Resolves TypeScript import errors when using @elizaos/plugin-sql\\n\\n\\n---\\n\\n> [!NOTE]\\n> \",\n \"files\": [\n \"bun.lock\",\n \"packages/plugin-sql/package.json\"\n ]\n },\n {\n \"title\": \"fix: entity names array serialization for PostgreSQL\",\n \"prNumber\": 6133,\n \"type\": \"bugfix\",\n \"body\": \"Fix entity creation failures by normalizing the names field to ensure it's\\r\\nalways a proper array before database operations. Handles Set objects by\\r\\nconverting them with Array.from().\\r\\n\\r\\n- Add normalization in createEntities() and updateEn\",\n \"files\": [\n \"packages/plugin-sql/src/__tests__/integration/entity-array-fix.test.ts\",\n \"packages/plugin-sql/src/__tests__/integration/entity-methods.test.ts\",\n \"packages/plugin-sql/src/base.ts\"\n ]\n },\n {\n \"title\": \"feat(core): add skipMigrations option to runtime.initialize() for ser\u2026\",\n \"prNumber\": 6132,\n \"type\": \"feature\",\n \"body\": \"- Add optional skipMigrations parameter to initialize() method in IAgentRuntime interface\\r\\n- Implement skipMigrations logic in AgentRuntime.initialize() to conditionally skip plugin migrations\\r\\n- Default behavior unchanged - migrations run \",\n \"files\": [\n \"bun.lock\",\n \"packages/core/src/__tests__/runtime.test.ts\",\n \"packages/core/src/runtime.ts\",\n \"packages/core/src/types/runtime.ts\"\n ]\n },\n {\n \"title\": \"fix: align server tests with ElizaOS API changes\",\n \"prNumber\": 6135,\n \"type\": \"bugfix\",\n \"body\": \"\\n> [!NOTE]\\n> Aligns server tests and routers with new ElizaOS interfaces, clarifies plugin auto-injection behavior, and deflakes/modernizes middleware, loader, socket, and utility tests.\\n> \\n> - **Server/API alignment*\",\n \"files\": [\n \"bun.lock\",\n \"packages/server/src/__tests__/agent-plugin-reload.test.ts\",\n \"packages/server/src/__tests__/agent-server-database.test.ts\",\n \"packages/server/src/__tests__/agent-server-errors.test.ts\",\n \"packages/server/src/__tests__/agent-server-initialization.test.ts\",\n \"packages/server/src/__tests__/agent-server-management.test.ts\",\n \"packages/server/src/__tests__/agent-server-middleware.test.ts\",\n \"packages/server/src/__tests__/agents-runs.test.ts\",\n \"packages/server/src/__tests__/api.test.ts\",\n \"packages/server/src/__tests__/authMiddleware.test.ts\",\n \"packages/server/src/__tests__/basic-functionality.test.ts\",\n \"packages/server/src/__tests__/bootstrap-autoload.test.ts\",\n \"packages/server/src/__tests__/file-utils.test.ts\",\n \"packages/server/src/__tests__/integration/database-operations.test.ts\",\n \"packages/server/src/__tests__/integration/jobs-message-flow.test.ts\",\n \"packages/server/src/__tests__/loader.test.ts\",\n \"packages/server/src/__tests__/message-bus.test.ts\",\n \"packages/server/src/__tests__/middleware.test.ts\",\n \"packages/server/src/__tests__/simple-validation.test.ts\",\n \"packages/server/src/__tests__/socketio-router.test.ts\",\n \"packages/server/src/__tests__/ui-disable-feature.test.ts\",\n \"packages/server/src/__tests__/utils.test.ts\",\n \"packages/server/src/__tests__/validation.test.ts\",\n \"packages/server/src/api/system/__tests__/version.test.ts\",\n \".github/workflows/core-package-tests.yaml\",\n \"package.json\",\n \"packages/core/src/__tests__/secrets.test.ts\",\n \"packages/core/src/__tests__/settings.test.ts\",\n \"packages/core/src/elizaos.ts\",\n \"packages/core/src/secrets.ts\",\n \"packages/server/README.md\",\n \"packages/server/package.json\",\n \"packages/server/scripts/run-integration-tests.sh\",\n \"packages/server/src/__tests__/EventEmitter-Compatibility-README.md\",\n \"packages/server/src/__tests__/README.md\",\n \"packages/server/src/__tests__/agent-server-lifecycle.test.ts\",\n \"packages/server/src/__tests__/builders/channel.builder.ts\",\n \"packages/server/src/__tests__/builders/character.builder.ts\",\n \"packages/server/src/__tests__/builders/message.builder.ts\",\n \"packages/server/src/__tests__/compatibility/cli-compatibility.test.ts\",\n \"packages/server/src/__tests__/compatibility/cli-patterns.test.ts\",\n \"packages/server/src/__tests__/features/bootstrap-autoload.test.ts\",\n \"packages/server/src/__tests__/features/character-file-size-regression.test.ts\",\n \"packages/server/src/__tests__/features/server-core.test.ts\",\n \"packages/server/src/__tests__/features/socketio-router.test.ts\",\n \"packages/server/src/__tests__/features/ui-toggle.test.ts\",\n \"packages/server/src/__tests__/fixtures/agent.fixture.ts\",\n \"packages/server/src/__tests__/fixtures/database.fixture.ts\",\n \"packages/server/src/__tests__/fixtures/server.fixture.ts\",\n \"packages/server/src/__tests__/helpers/networking.ts\",\n \"packages/server/src/__tests__/helpers/retry.ts\",\n \"packages/server/src/__tests__/helpers/wait.ts\",\n \"packages/server/src/__tests__/index.ts\",\n \"packages/server/src/__tests__/integration/agent-server-interaction.test.ts\",\n \"packages/server/src/__tests__/integration/message-bus-service.test.ts\",\n \"packages/server/src/__tests__/integration/socketio-message-flow.test.ts\",\n \"packages/server/src/__tests__/run-working-tests.sh\",\n \"packages/server/src/__tests__/security/rls-server.test.ts\",\n \"packages/server/src/__tests__/spa-routing-fix.test.ts\"\n ]\n },\n {\n \"title\": \"fix: load environment variables from process.env instead of .env file\",\n \"prNumber\": 6141,\n \"type\": \"bugfix\",\n \"body\": \"## Relates to\\r\\n\\r\\nFixes the issue where `runtime.getSetting(\\\"ANY_VARIABLES\\\")` returns `undefined` when environment variables are exported on the host (`export VAR=value`) instead of being defined in a `.env` file, causing agents to use incor\",\n \"files\": [\n \"bun.lock\",\n \"packages/cli/src/commands/start/index.ts\",\n \"packages/core/src/__tests__/secrets.test.ts\",\n \"packages/core/src/__tests__/settings.test.ts\",\n \"packages/core/src/__tests__/utils/environment.test.ts\",\n \"packages/core/src/secrets.ts\",\n \"packages/core/src/utils/environment.ts\",\n \"packages/server/src/index.ts\"\n ]\n },\n {\n \"title\": \"fix: RLS (Row-Level Security) server_id validation checks blocking all users when RLS isolation is disabled.\",\n \"prNumber\": 6139,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nFix for RLS (Row-Level Security) server_id validation checks blocking all users when RLS isolation is disabled.\\r\\n\\r\\nMaybe: https://github.com/elizaOS/eliza/issues/6138\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**. Changes only affect RLS security c\",\n \"files\": [\n \"packages/server/src/__tests__/rls-server.test.ts\",\n \"packages/server/src/api/messaging/channels.ts\",\n \"packages/server/src/api/messaging/core.ts\",\n \"packages/server/src/utils/rls-validation.ts\"\n ]\n },\n {\n \"title\": \"fix: Add openrouter embedding option in CLI\",\n \"prNumber\": 6142,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nImproves OpenRouter integration in ElizaOS CLI by adding native embedding support, eliminating the need for users to configure a separate embedding provider when using OpenRouter.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low Risk** - Well-contained \",\n \"files\": [\n \"packages/cli/src/commands/create/actions/setup.ts\",\n \"packages/cli/src/commands/create/utils/selection.ts\",\n \"packages/cli/src/utils/get-config.ts\",\n \"packages/cli/tests/unit/utils/selection.test.ts\"\n ]\n },\n {\n \"title\": \"fix(build): resolve TypeScript declaration generation errors\",\n \"prNumber\": 6146,\n \"type\": \"bugfix\",\n \"body\": \"- Add missing hasElizaOS() method to test-utils mock runtime\\r\\n * Implements required type predicate from IAgentRuntime interface\\r\\n * Returns false by default for test scenarios\\r\\n\\r\\n- Fix plugin-sql TypeScript declaration generation\\r\\n * Ov\",\n \"files\": [\n \"bun.lock\",\n \"packages/plugin-sql/build.ts\",\n \"packages/plugin-sql/tsconfig.build.json\",\n \"packages/plugin-sql/tsconfig.build.node.json\",\n \"packages/test-utils/src/mocks/runtime.ts\"\n ]\n },\n {\n \"title\": \"fix: migrate from LangChain v0.3 to @langchain/textsplitters v1.0\",\n \"prNumber\": 6152,\n \"type\": \"bugfix\",\n \"body\": \"- Replace langchain dependency with @langchain/textsplitters in @elizaos/core\\r\\n- Update import from 'langchain/text_splitter' to '@langchain/textsplitters'\\r\\n- Remove outdated langchain resolutions from plugin starter packages\\r\\n- Add compreh\",\n \"files\": [\n \"bun.lock\",\n \"packages/core/package.json\",\n \"packages/core/src/__tests__/utils.test.ts\",\n \"packages/core/src/utils.ts\",\n \"packages/plugin-quick-starter/package.json\",\n \"packages/plugin-starter/package.json\"\n ]\n },\n {\n \"title\": \"feat: improve accepted formats for plugin names in plugin dependencies\",\n \"prNumber\": 6164,\n \"type\": \"feature\",\n \"body\": \"\\n> [!NOTE]\\n> Adds name normalization and enhanced dependency resolution to handle both scoped package names and short names, with deduped queuing and comprehensive tests.\\n> \\n> - **Core (`packages/core/src/plugin.ts`)*\",\n \"files\": [\n \"packages/core/src/__tests__/plugin.test.ts\",\n \"packages/core/src/plugin.ts\",\n \"packages/cli/tests/commands/plugins.test.ts\",\n \"packages/core/src/runtime.ts\"\n ]\n },\n {\n \"title\": \"fix(server): update MessageBusService integration tests\",\n \"prNumber\": 6165,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nUpdates to MessageBusService integration tests following architecture changes\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Test-only changes, no production code modified\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nUpdates MessageBusService integr\",\n \"files\": [\n \"bun.lock\",\n \"packages/server/package.json\",\n \"packages/server/scripts/run-integration-tests.sh\",\n \"packages/server/src/__tests__/integration/database-operations.test.ts\",\n \"packages/server/src/__tests__/integration/message-bus-service.test.ts\"\n ]\n }\n ],\n \"topContributors\": [\n {\n \"username\": \"odilitime\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n \"totalScore\": 395.297552760595,\n \"prScore\": 384.457552760595,\n \"issueScore\": 0,\n \"reviewScore\": 9.5,\n \"commentScore\": 1.34,\n \"summary\": \"odilitime: This month, odilitime made significant contributions to documentation and bug fixes, while also initiating new feature work. They landed a major documentation update in elizaos/spartan#21, which added over 5,000 lines, and also merged a fix for tasks in elizaos-plugins/plugin-birdeye#7. In addition to this merged work, they have several features in progress for the elizaos/eliza repository, including a new framework for adjusting prompts (#6113). Their activity shows a primary focus on general development and bug fixes, with contributions spread across code, tests, and documentation.\"\n },\n {\n \"username\": \"0xbbjoker\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n \"totalScore\": 335.61856114698304,\n \"prScore\": 305.718561146983,\n \"issueScore\": 0,\n \"reviewScore\": 29.5,\n \"commentScore\": 0.4,\n \"summary\": \"0xbbjoker: This month, 0xbbjoker focused on extending plugin capabilities by implementing a key feature in `elizaos-plugins/plugin-openrouter` via PR #17. This significant contribution added support for `TEXT_EMBEDDING` models, involving changes across code, tests, and configuration files. In addition to this feature work, they also contributed one pull request review.\"\n },\n {\n \"username\": \"standujar\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4\",\n \"totalScore\": 269.5717422393051,\n \"prScore\": 221.21374223930508,\n \"issueScore\": 0,\n \"reviewScore\": 46.5,\n \"commentScore\": 1.8579999999999999,\n \"summary\": \"standujar: Focused on developing several key features this month, with a significant amount of work in progress across multiple repositories. They opened pull requests to implement entity-level row-level security (elizaos/eliza#6107) and integrate a unified messaging API for the Discord plugin (elizaos-plugins/plugin-discord#24). This work, while not yet merged, involved substantial changes across 187 files (+4640/-1654 lines) and 25 commits. Based on their code changes, their effort was primarily centered on new feature development and refactoring.\"\n },\n {\n \"username\": \"Freytes\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/4147278?u=89aa9570e6f8b4a8e9e41e8f908c16fb69c5a43f&v=4\",\n \"totalScore\": 232.1658694828805,\n \"prScore\": 232.1658694828805,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"Freytes: Focused on adding substantial new features to the `elizaos/spartan` repository, merging four significant pull requests. Their most impactful contributions included introducing a new Chrome extension in PR #17 (+42042 lines) and a Farcaster miniapp in PR #19 (+13210 lines). Freytes also improved the developer experience by adding Docker support for an easier development setup in PR #20. In total, their work added over 67k lines of new code and tests to build out major new components for the project.\"\n },\n {\n \"username\": \"wtfsayo\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n \"totalScore\": 66.99339001321847,\n \"prScore\": 66.99339001321847,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"wtfsayo: This month, wtfsayo focused on maintenance within the `elizaos-plugins/plugin-mcp` repository. They merged a single pull request (#18) to update action names and dependencies, which involved a significant refactor that removed nearly 400 lines of code. Their commits were distributed across feature work, bug fixes, and tests, primarily modifying code, documentation, and configuration files.\"\n },\n {\n \"username\": \"borisudovicic\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31806472?u=8935f4d43fd7e4eb9bf5ff92d54d4d2f8ac8a786&v=4\",\n \"totalScore\": 50.2,\n \"prScore\": 0,\n \"issueScore\": 50,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"borisudovicic: Focused on planning and defining future work for the elizaos/eliza repository this month. They initiated discussions on several potential features by creating issues for \\\"Points / Leaderboard\\\" (#6110), \\\"Background tasks\\\" (#6109), and \\\"Parallel actions\\\" (#6108).\"\n },\n {\n \"username\": \"rferrari\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/495887?u=5a56d90f584ffc1827bb301541076597dca9cb3e&v=4\",\n \"totalScore\": 36.77887055267063,\n \"prScore\": 34.57887055267063,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"rferrari: This month, rferrari focused on initiating improvements to plugin functionality and developer tooling. They proposed enhancements to the Farcaster plugin's configuration and API handling in an open pull request (elizaos-plugins/plugin-farcaster#13). Additionally, rferrari opened an issue to improve debugging support in the core application (elizaos/eliza#6154).\"\n },\n {\n \"username\": \"LinuxIsCool\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31582215?u=b8eb5d3849bf877a3a0b686cf1632aca92e744ae&v=4\",\n \"totalScore\": 27.88213122712422,\n \"prScore\": 23.68213122712422,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"LinuxIsCool: This month, LinuxIsCool's contributions were focused on project maintenance within the elizaos/eliza repository. They identified and opened two issues regarding project health: #6122 about missing documentation and #6121 concerning an outdated changelog.\"\n },\n {\n \"username\": \"ai16x402\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/241517257?u=db5e37fbc5cfc2fc78bd2de767f7235704dc2b0f&v=4\",\n \"totalScore\": 25.22068353919891,\n \"prScore\": 24.78268353919891,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.43799999999999994,\n \"summary\": \"ai16x402: This month, ai16x402 focused on expanding the plugin ecosystem by opening three pull requests to add new plugins to the `elizaos-plugins/registry` (#237, #238, #239). This work, which is still in progress, involved 7 commits and modifications to configuration files (+80/-18 lines). They also participated in discussions with 3 comments on pull requests.\"\n },\n {\n \"username\": \"madjin\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n \"totalScore\": 23.146346309695485,\n \"prScore\": 23.146346309695485,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"madjin: This month, madjin focused on expanding the project's pipeline configuration. They merged a pull request in elizaos/elizaos.github.io (#169) that added 12 new active repositories to the system. This work consisted entirely of modifications to configuration files.\"\n },\n {\n \"username\": \"Neysixx\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/115616810?u=94c403172b4ffda30d6fc765f5997631fb7d1ef1&v=4\",\n \"totalScore\": 22.861633597686627,\n \"prScore\": 22.861633597686627,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"Neysixx: Focused on extending command-line functionality in the elizaos/eliza repository this month. They opened a pull request to add a new embedding option (elizaos/eliza#6142), which involved modifying 6 files with significant changes (+620/-545 lines). This work, which included new tests, was an even mix of feature development, bug fixing, and refactoring.\"\n },\n {\n \"username\": \"ChristopherTrimboli\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4\",\n \"totalScore\": 16,\n \"prScore\": 0,\n \"issueScore\": 0,\n \"reviewScore\": 16,\n \"commentScore\": 0,\n \"summary\": \"ChristopherTrimboli: Focused on supporting the team through code review this month, performing 3 reviews which included 2 approvals and 1 request for changes. He also made progress on a local refactoring effort, committing changes across 17 files.\"\n },\n {\n \"username\": \"tungpun\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/5058370?u=59cb956de322867be56c0abee49ab3f28f819e2f&v=4\",\n \"totalScore\": 13.943573590279971,\n \"prScore\": 13.943573590279971,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"tungpun: This month, tungpun focused on improving stability in the `elizaos/eliza` repository by addressing a potential race condition. They opened a pull request (#6137) to remove a message emit in the source API, a change that modified 24 files (+272/-57 lines). This work indicates a focus on bug prevention and code maintenance.\"\n },\n {\n \"username\": \"nguyennk92\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/30664183?u=d6e579cd25d50bc8e9ec4928d95909d759b841db&v=4\",\n \"totalScore\": 12.745835825288449,\n \"prScore\": 12.145835825288449,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.6000000000000001,\n \"summary\": \"nguyennk92: This month's work was focused on adding an authentication token to the Socket.io server, proposed in the open pull request elizaos/eliza#6144. The contribution consisted of 3 commits modifying 5 files. The changes touched application code, configuration, and tests, indicating a primary focus on feature work and its associated testing.\"\n },\n {\n \"username\": \"otaku-x402\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/242004857?u=1325b26d380eec4a0b8d84e8e249c523eebd28dc&v=4\",\n \"totalScore\": 11.897573590279972,\n \"prScore\": 11.897573590279972,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"otaku-x402: No activity this month.\"\n },\n {\n \"username\": \"skurzyp\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/98319381?v=4\",\n \"totalScore\": 7,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 5,\n \"commentScore\": 0,\n \"summary\": \"skurzyp: This month, skurzyp's activity was focused on identifying future technical debt by opening an issue in `elizaos/eliza` (#6145) to track the necessary migration from a deprecated version of Langchain.\"\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\": \"devbrett90-prog\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/241853504?v=4\",\n \"totalScore\": 4.5,\n \"prScore\": 0,\n \"issueScore\": 0,\n \"reviewScore\": 4.5,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"humuhimi\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/35215680?u=029a1ed6ea6a26ebf1cfd081cba6af2e6d32ef6d&v=4\",\n \"totalScore\": 4.3,\n \"prScore\": 0,\n \"issueScore\": 4.1,\n \"reviewScore\": 0,\n \"commentScore\": 0.2,\n \"summary\": \"humuhimi: Contributed to repository stability by identifying and reporting a significant bug in `elizaos/eliza` (#6138), where disabling the Web UI was incorrectly blocking all endpoints.\"\n },\n {\n \"username\": \"samarth30\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/48334430?u=1fc119a6c2deb8cf60448b4c8961cb21dc69baeb&v=4\",\n \"totalScore\": 4,\n \"prScore\": 0,\n \"issueScore\": 4,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"samarth30: This month, samarth30's contribution was focused on planning for new billing functionality in the Eliza Cloud product. They initiated this effort by creating an issue to track the integration of Stripe for settings and billing (elizaos/eliza#6118).\"\n },\n {\n \"username\": \"tdnupe3\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/25161668?u=94680b6bcbcfce954c7a9dd09d667a3919953041&v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"tdnupe3: This month, tdnupe3 contributed to the elizaos/eliza repository by opening an issue (#6148) to propose a new plugin submission for \\\"Coin Railz x402 Micropayment Services\\\".\"\n },\n {\n \"username\": \"nikatuz8-cell\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/243873833?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"nikatuz8-cell: Contributed to the elizaos/eliza repository by opening and closing an issue related to migration (#6149).\"\n },\n {\n \"username\": \"linear\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/in/20150?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"linear: This month's activity consisted of creating an issue to define entity-level row-level security in elizaos/eliza (#6112).\"\n },\n {\n \"username\": \"christophwallacher-web\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/233379771?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": \"christophwallacher-web: This month, christophwallacher-web's activity consisted of identifying and reporting a potential bug in the `elizaos/eliza` repository by opening issue #6140.\"\n },\n {\n \"username\": \"TommyVeit\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/244845549?v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"870171594\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/216127669?u=d4669261a63be8c0bcb69c4e497ed51ecc07776e&v=4\",\n \"totalScore\": 2,\n \"prScore\": 0,\n \"issueScore\": 2,\n \"reviewScore\": 0,\n \"commentScore\": 0,\n \"summary\": null\n },\n {\n \"username\": \"letmehateu\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/133153661?u=2217cec1ebd7bf22a8e4e3ace28b3183720dd444&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\": 22,\n \"mergedPRs\": 14,\n \"newIssues\": 38,\n \"closedIssues\": 23,\n \"activeContributors\": 24\n}\n---\n[\"wtfsayo_day_2025-11-16\", \"wtfsayo\", \"day\", \"2025-11-16\", \"wtfsayo: Focused on bugfix work, making a single commit that modified 1 file with a net change of 0 lines.\", \"2025-11-16T23:14:48.484Z\"]"
]
}