{ "date_generated_for": "2025-04-11", "ai_news_elizaos_discord_md_2025-04-10": { "filename": "2025-04-10.md", "content": "# elizaOS Discord - 2025-04-10\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Issues\n- Users are experiencing various installation and dependency issues with ElizaOS, particularly when building different versions\n- Version 0.25.9 appears to be the most stable according to some users, though plugin compatibility varies across versions\n- The \"hapi__shot\" error is commonly reported when building different versions\n- Users are trying different package managers (npm, pnpm, bun) to resolve dependency issues\n- A common fix for the \"Dynamic require of 'child_process'\" error is adding `\"types\": [\"node\"]` to tsconfig.json\n- Twitter plugin functionality is a common pain point, with users trying to get autonomous posting working\n\n### ElizaDAO Organization\n- The community is establishing ElizaDAO alongside existing entities ElizaLabs and ElizaStudios\n- Five working groups have been formed: Community/Governance/Events, Dev/Knowledge, Comms/Social, Partnerships/Outreach, and Tokens/Funding\n- Consensus that a separate DAO treasury is essential for true decentralized governance\n- Discussion about balancing autonomous action with coordination with ElizaLabs to avoid duplication of efforts\n- Plans to create a DAO charter with clear values and establish alignment with ElizaLabs' roadmap while maintaining independence\n\n### Agent Development\n- SpartanV2 is being developed as a flagship agent for V2, while V1 is currently running\n- Discussion about optimal posting frequency for social media agents (currently twice per hour for Spartan)\n- The team is exploring ways to recover 25,000 followers that were previously lost\n- Contract address has been added to the Spartan account profile\n\n### MCP (Model Context Protocol) Ecosystem\n- Gap identified in the MCP server ecosystem: lack of efficient discovery and evaluation mechanisms for AI agents\n- Multiple registry solutions emerging (smithery.ai, mcp.so, mcpmarket.com) but they lack agent-centric feedback\n- Proposal for registry.fun as a whitelabel version of auto.fun for MCP server operators\n- Concept of an \"Eliza Diary Network\" mentioned as a forum for AI agents\n\n### Product Launches\n- Auto.fun launch initially delayed to April 14th, now coming \"very very soon\" without a specific date\n- Clank Tank Episode 3 released, with discussions about improvements including Tally integrations and Discord webhooks\n- Virtual token reportedly got listed\n\n## Key Questions & Answers\n\n### Technical Implementation\n- **Q**: How can I fix the \"Dynamic require of 'child_process' is not supported\" error? \n **A**: Add `\"types\": [\"node\"]` to tsconfig.json\n\n- **Q**: How can I call plugin to the agent? \n **A**: Yes, it's possible (though the answer lacks details)\n\n- **Q**: Can I change the language of Eliza? \n **A**: Yes, if you define your character in Chinese, LLM should respond that way\n\n- **Q**: Is the task functionality working? \n **A**: It's only on v2 and not tested too much yet\n\n### ElizaDAO Structure\n- **Q**: Do we need a separate treasury for the DAO? \n **A**: Yes, without a treasury and collective decision-making, it's not truly a DAO\n\n- **Q**: How should we manage DAO spending? \n **A**: Set a budget for each group with 1-2 members as \"CFO\" to approve spending\n\n- **Q**: How do we balance autonomy with alignment with Labs/Studios? \n **A**: Codify values in the DAO charter that balance \"you can just do things\" with coordination principles\n\n- **Q**: What should be the name of the DAO? \n **A**: ElizaDAO, to go with ElizaLabs and ElizaStudios\n\n### Agent Development\n- **Q**: Not on v2 now? \n **A**: No, still working on v2, we'll upgrade when it's ready\n\n- **Q**: Thoughts on if he's posting too often? Twice an hour seems on the high side \n **A**: Yes, planning to slow it down after improving post quality\n\n- **Q**: Did degenspartanai move to another handle or is the project stopped? \n **A**: Twitter account was suspended. It's being re-built as a flagship agent for V2\n\n## Community Help & Collaboration\n\n### Technical Support\n- **notorious_d_e_v** helped **hotcode101** with debugging by suggesting setting `DEFAULT_LOG_LEVEL=\"debug\"` in .env file and checking Twitter settings in .env.example\n- **wookosh** helped **apoorva99** fix an error with MongoDB adapter by suggesting adding `\"types\": [\"node\"]` to tsconfig.json\n- **notorious_d_e_v** advised **0xLabsTheCoder** to use `pnpm` instead of other package managers for build issues\n- **Kimani** helped multiple users with v1 setup issues by suggesting navigating to node_modules\\better-sqlite3 directory and running pnpm run build\n- **CSC35** advised **0xLabsTheCoder** on Twitter posting issues by setting `TWITTER_ENABLE_POST_GENERATION=true` in the .env for v2\n\n### Governance & Organization\n- **Patt** helped **vincentpaul** locate an introduction message from a user\n- **accelxr** corrected **HoneyBadger's** misidentification of a wallet thought to belong to Labs\n- **vincentpaul** organized the DAO structure by creating and updating a list of 5 working groups with assigned leaders\n- **yikesawjeez** offered to connect the group with governance experts from rndao and Hats protocol\n\n### Product Development\n- **hubert** confirmed to **DorianD** they were spinning up \"the\" registry for MCPs with better voting mechanisms\n- **Odilitime** clarified for **찌 G 跻 じ PrudentSpartan** about the auto.fun release timeline\n- **jin** acknowledged **Toni's** feedback about Clank Tank episode length and committed to shorter episodes\n\n## Action Items\n\n### Technical\n- Fix the hapi__shot error that occurs in newer versions (Mentioned by CSC35, 0xLabsTheCoder)\n- Fix compatibility issues between different package managers (Mentioned by 0xChainBrain)\n- Resolve the \"Dynamic require of 'child_process'\" error on WSL2 (Mentioned by Bundinho)\n- Fix Twitter plugin autonomous posting functionality (Mentioned by hotcode101, 0xLabsTheCoder)\n- Fix Discord plugin compatibility with version 0.25.9 (Mentioned by wookosh)\n- Establish a separate treasury for ElizaDAO (Mentioned by HoneyBadger, yikesawjeez)\n- Create a budget allocation system for each working group (Mentioned by HoneyBadger)\n- Develop token engineering for DAO governance (Mentioned by yikesawjeez)\n- Align DAO roadmap with ElizaLabs' plans for Q3-Q4 (Mentioned by HoneyBadger)\n- Schedule coordination call with ElizaLabs to establish initial steps (Mentioned by HoneyBadger)\n- Slow down posting frequency of SpartanV1 from twice per hour (Mentioned by Odilitime)\n- Continue development of SpartanV2 (Mentioned by Odilitime)\n- Explore path to recover 25,000 lost followers (Mentioned by Odilitime)\n- Implement Tally integrations and Discord webhooks for Clank Tank submissions (Mentioned by jin)\n- Reduce Clank Tank episode length to 6-7 minutes maximum (Mentioned by jin)\n\n### Documentation\n- Create clear deployment guides for VPS and cloud services (Mentioned by stanleymarch)\n- Improve plugin development and testing documentation for v2 (Mentioned by Tobiloba)\n- Update task functionality documentation (Mentioned by hotcode101)\n- Create troubleshooting guide for common errors (Mentioned by 0xChainBrain)\n- Draft a DAO charter with clear values balancing autonomy and coordination (Mentioned by vincentpaul)\n- Create a sign-up process for core contributors with proper verification (Mentioned by HoneyBadger)\n- Define coordination protocols between ElizaDAO and ElizaLabs/Studios (Mentioned by accelxr)\n- Rewrite the Eliza Diary Network concept to better serve as a forum for agents (Mentioned by DorianD)\n- Develop community and governance protocol for fair access to announcement channels (Mentioned by vincentpaul)\n\n### Feature\n- Add support for scheduled actions in v1 (Mentioned by martincontact101)\n- Implement incentive mechanisms for sustainable contributor participation (Mentioned by vincentpaul, Zolo)\n- Develop builder support program within the DAO structure (Mentioned by Kenk)\n- Add contract address to account profile (Mentioned by Zolo)\n- Create an MCP Server Agent that handles customer service, promotion, and registry registration (Mentioned by DorianD)\n- Develop a registry for MCP servers that collects reviews and feedback from agents (Mentioned by DorianD)\n- Create a whitelabel version of auto.fun at registry.fun for MCP server operators (Mentioned by DorianD)\n- Implement a voting system for AI judges in Clank Tank that includes token holders (Mentioned by jin)" }, "ai_news_elizaos_discord_md_2025-04-09": { "filename": "2025-04-09.md", "content": "# elizaOS Discord - 2025-04-09\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Updates\n- **ElizaOS Version Status**: The team is maintaining v1 while actively developing v2. Some users reported reverting to v1 due to functionality issues in v2, particularly with Twitter plugin integration.\n- **Grok3 API Availability**: 7etsuo announced that \"Grok3 API is up\" without providing further details.\n- **Common Build Error**: Multiple users encountered \"hapi__shot\" type definition errors across different versions, with a solution identified (adding `\"types\": [\"node\"]` to tsconfig.json).\n- **Twitter Plugin Issues**: Several users reported problems with Twitter interactions functionality not working properly in v2. A workaround was identified by enabling `TWITTER_SEARCH_ENABLE=true`.\n- **SpartanAI Reactivation**: Odilitime shared that SpartanAI (also called \"DegenAI\") has been restarted on Twitter using v1 while v2 development continues.\n\n### Agent-to-Agent Communication & Protocols\n- **Model Context Protocol (MCP)**: Discussed as a bridge between LLMs and current software paradigms. Odilitime suggested that while APIs remain efficient for high-volume or low-latency applications, the future will see fewer static APIs as dynamic agents become more prevalent.\n- **Agent Registry Concept**: DorianD proposed an \"Eliza agent registry\" where agents could advertise capabilities via JSON \"Agent Cards\" and utilize trust scores to facilitate agent selection for specific tasks.\n- **Plugin Integration**: Questions raised about how to call plugins to agents and whether folder structures are required for plugin imports.\n\n### DAO Organization & Governance\n- **\"Supermind\" Structure**: Vincent Paul initiated organizing ElizaDAO as a \"Supermind\" with five working circles: Community/Governance/Events, Dev/Knowledge, Comms/Social, Partnerships/Outreach, and Tokens/Funding.\n- **Contribution Tracking**: Jin shared development of a reputation/contribution tracking system that monitors engagement across channels, analyzes sentiment, scores GitHub contributions, and generates reports to support both token rewards and non-financial incentives.\n- **DAO Treasury**: Multiple participants emphasized the need for DAO treasury independence and incentive mechanisms to sustain participation beyond initial enthusiasm.\n- **Ecosystem Coordination**: Discussion of coordination with ElizaLabs and ElizaStudios while maintaining the DAO's autonomy (\"Eliza is Ours\").\n\n### Community Initiatives\n- **Clank Tank**: Jin discussed the development of \"Clank Tank,\" a show featuring project pitches, and shared details about using AI workflows to create avatars for participants.\n- **Builder Support**: Kenk introduced builder support initiatives including an invite-only Telegram group (200+ members) and YouTube tutorials for plugin developers.\n\n## Key Questions & Answers\n\n### Technical Implementation\n- **Q**: How can I fix the hapi__shot type error when building ElizaOS? \n **A**: Add `\"types\": [\"node\"],` to tsconfig.json (answered by wookosh)\n\n- **Q**: How can I get more verbose debugging output in v1? \n **A**: Set DEFAULT_LOG_LEVEL=debug in your .env file or use DEFAULT_LOG_LEVEL=\"debug\" pnpm start (answered by wookosh and notorious_d_e_v)\n\n- **Q**: How can I get Twitter interactions (mentions, replies) working in ElizaOS v2? \n **A**: Enable TWITTER_SEARCH_ENABLE=true in your configuration (answered by notorious_d_e_v)\n\n- **Q**: Which version of ElizaOS is most stable? \n **A**: Version 0.25.9 (answered by notorious_d_e_v)\n\n### DAO Organization\n- **Q**: What are the immediate priorities for ElizaDAO? \n **A**: Align on Road to Solana Accelerate NYC Plan, form working circles, and schedule weekly/monthly rituals (answered by vincentpaul)\n\n- **Q**: What working groups are being formed? \n **A**: Community/Governance/Events, Dev/Knowledge, Comms/Social, Partnerships/Outreach, and Tokens/Funding (answered by vincentpaul)\n\n- **Q**: How will the DAO measure participation and contributions? \n **A**: Jin is developing a system that passively observes engagement, analyzes sentiment, scores GitHub contributions, and generates reports (answered by jin)\n\n- **Q**: Does the DAO need its own treasury? \n **A**: Yes, for the DAO to function properly it needs a separate treasury and collective decision-making (answered by yikesawjeez)\n\n### Future of AI & Protocols\n- **Q**: Do you think odds are high that MCP becomes standard for API layer for LLM-native tools? \n **A**: It's a bridge between LLMs and the current software paradigm, but software is changing. APIs remain efficient for high-volume or low-latency applications. (answered by Odilitime)\n\n- **Q**: What's the timing on the transition from static APIs to dynamic agents? \n **A**: Gradual, as software takes time to build. Once builders have frameworks with great docs, it'll be competitive with existing software stacks. (answered by Odilitime)\n\n- **Q**: Is an official elizaOS agent registry likely to happen? \n **A**: I'd say an official elizaOS agent registry is likely to happen. (answered by Odilitime)\n\n## Community Help & Collaboration\n\n### Technical Troubleshooting\n- **notorious_d_e_v** helped **0xLabsTheCoder** with Twitter plugin interactions not working in ElizaOS v2 by suggesting enabling TWITTER_SEARCH_ENABLE=true and sharing a custom Twitter client fork using API access instead of scraping.\n\n- **wookosh** helped **[elizaos] ** resolve the hapi__shot type error when building ElizaOS by suggesting adding \"types\": [\"node\"] to tsconfig.json.\n\n- **notorious_d_e_v** assisted **[elizaos] ** with getting more verbose debugging output in v1 by suggesting setting DEFAULT_LOG_LEVEL=\"debug\" in .env file.\n\n### DAO Organization\n- **jin** explained to **hubert** how the reputation/contribution tracking system observes engagement, analyzes sentiment, and scores contributions for both token and non-token rewards.\n\n- **Patt** helped **vincentpaul** find Zolo's introduction that was missed by locating and linking to it in the chat.\n\n- **accelxr** corrected **HoneyBadger** regarding misinformation about a wallet, clarifying that the identified wallet was not an ElizaLabs wallet.\n\n### Product Improvement\n- **Zolo** suggested to **Odilitime** adding the contract address to SpartanAI's Twitter profile, which Odilitime implemented.\n\n- **DorianD** provided **jin** with specific feedback on Clank Tank episode audio issues including voice directionality problems and difficulty distinguishing speakers.\n\n- **yikesawjeez** advised **jin** on pitch duration for Clank Tank, suggesting following hackathon presentation format with ~5min for finalists and 1-2min for runners-up.\n\n## Action Items\n\n### Technical\n- Fix hapi__shot type error by adding \"types\": [\"node\"] to tsconfig.json (Mentioned by wookosh)\n- Enable TWITTER_SEARCH_ENABLE=true to make Twitter interactions work (Mentioned by notorious_d_e_v)\n- Set DEFAULT_LOG_LEVEL=\"debug\" for better debugging output (Mentioned by notorious_d_e_v)\n- Consider using pnpm instead of npm for installation (Mentioned by notorious_d_e_v)\n- Investigate memory issues with Supabase DB after 30-35 prompts (Mentioned by Mohit)\n- Implement Twitter API access instead of scraping for more reliable operation (Mentioned by notorious_d_e_v)\n- Continue development of SpartanAI v2 (Mentioned by Odilitime)\n- Develop and test the reputation/contribution tracking system (Mentioned by jin)\n- Establish a DAO treasury with budget allocation for working groups (Mentioned by HoneyBadger)\n- Improve audio quality in Clank Tank episodes, specifically fixing voice directionality issues (Mentioned by DorianD)\n- Reduce Clank Tank episode length by at least 50% (Mentioned by jin)\n- Investigate how to send markup buttons with Eliza in Telegram client (Mentioned by egoarka)\n- Explore plugin integration with agents (Mentioned by Ved Mohan)\n- Investigate wallet compatibility issue between Solflare and Phantom for verification purposes (Mentioned by ✨☎ MomoChan)\n\n### Documentation\n- Create a DAO charter with clear values including \"you can just do things\" (Mentioned by vincentpaul)\n- Build a member directory, potentially using character creator (Mentioned by vincentpaul)\n- Develop roadmap for Q3-Q4 aligned with ElizaLabs plans (Mentioned by HoneyBadger)\n- Create a way to easily share contents of popular plugins with cursor (Mentioned by elizaos-bridge-odi)\n\n### Feature\n- Implement weekly investor newsletter for token holders (Mentioned by Odilitime)\n- Create badges/NFTs for achievements tied to reputation system (Mentioned by jin)\n- Set up monthly AMA/Town Hall with core team (Mentioned by vincentpaul)\n- Implement voting system for token holders alongside AI judges (Mentioned by jin)\n- Develop an Eliza agent registry with capability discovery (Mentioned by DorianD)\n- Implement agent trust scores/ratings system (Mentioned by DorianD)\n- No-code agent launcher (Mentioned by groggs)\n- Explore path to recover 25k Twitter followers for SpartanAI (Mentioned by Odilitime)" }, "ai_news_elizaos_discord_md_2025-04-08": { "filename": "2025-04-08.md", "content": "# elizaOS Discord - 2025-04-08\n\n## Overall Discussion Highlights\n\n### Technical Development\n- **ElizaOS V2 Architecture**: The upcoming V2 release will feature architectural improvements enabling cross-platform presence, no chain switching, workflows, and dynamic characters. Spartan in V2 will include three exclusive plugins: community-investor, autonomous trader, and intel, with reduced dependencies on external systems.\n- **Twitter Integration Issues**: Multiple users reported problems with the Twitter plugin in ElizaOS, particularly around interactions like mentions, replies, and quote reposts. Some users found v1 more functional than v2 for certain implementations.\n- **Model Selection Challenges**: Users discussed LLM model selection issues, with OpenRouter being considered as an alternative to local LLMs. Some reported problems with models defaulting to local LLMs despite OpenRouter configuration.\n- **AI Video Generation**: Jin shared progress on programmatically generating videos using Remotion framework, demonstrating both Unity-based and pure AI approaches (using Hedra for character animations).\n- **Model Context Protocol (MCP)**: Discussions about MCP servers as a bridge between static APIs and dynamic agents, with Odilitime predicting \"gradual then sudden adoption.\"\n- **Agent Registry Concept**: Several members discussed an \"ElizaOS agent registry\" that would allow agents to advertise capabilities via JSON format and establish trust scores.\n- **Grok3 API**: Brief announcement that \"Grok3 API is up.\"\n\n### Community & Organization\n- **ElizaDAO Reboot**: Vincent Paul introduced a plan to reboot ElizaDAO as a \"Supermind\" focused on collective intelligence, with proposed working circles including Communications, Community & Governance, Development, Documentation, Partnerships, and Events.\n- **Reputation System**: Jin is developing a reputation/contribution measurement system that passively monitors engagement across channels, analyzes sentiment, and scores GitHub contributions, with both token and non-monetary rewards.\n- **Community Demo Session**: A community demo session for elizaOS agents was mentioned, featuring projects like xNomad (tools for tokenizing Web3 AI agents), Growth Terminal (AI marketing co-pilot), Kudo Network (framework for AI agent covenants), and Crucible Network (Unreal Engine plugin).\n- **Auto.fun Launch**: The upcoming Auto.fun launch was frequently mentioned as an anticipated product with 15 partners, scheduled to launch after April 14th.\n\n### Spartan (Previously DegenAI)\n- **Development Status**: Odilitime clarified that Spartan's development milestones are being decoupled from V2 milestones.\n- **Marketing Plans**: Plans include cross-promotion between Spartan and the auto.fun launch, development of a web presence, and restoration of Spartan's Twitter presence.\n- **Twitter Presence**: The Spartan Twitter account (@SpartanVersus) is now active again on V1, addressing community concerns about perceived inactivity.\n\n### Content Creation\n- **Clank Tank Episodes**: Jin shared a preview of a Clank Tank episode and received feedback on length and audio quality issues, deciding to cut content by 50%.\n\n## Key Questions & Answers\n\n**ElizaOS Implementation**\n- Q: Is it possible to import Eliza as a module in my own backend and create an agent that way? \n A: Yes, and you can use the REST API too for that kind of thing. (DeFine)\n\n- Q: How can I fix the issue where plugin-tee generates the same key regardless of parameters? \n A: Review implementation for consistent parameters and check for version-specific issues. (jonathanmann)\n\n- Q: Why is my agent selecting wrong actions (e.g., checking weather instead of transferring funds)? \n A: It could be a memory issue when using Supabase DB after 30-35 prompts. (jonathanmann)\n\n- Q: How can I get more verbose debugging output in v1? \n A: Use DEFAULT_LOG_LEVEL=debug pnpm start (wookosh)\n\n**AI Video Generation**\n- Q: Which approach feels more watchable long term for AI videos - Unity or Pure AI? \n A: Both have strengths, but Unity offers more variety and tweakability while Pure AI (Hedra) will only improve over time. (Odilitime)\n\n**Spartan Development**\n- Q: Is it going to be postponed to match the schedule for Degen v2? \n A: Odilitime is trying to keep Spartan milestones decoupled with v2 milestones.\n\n- Q: What's different about spartan in V2? \n A: Spartan in V2 has 3 exclusive plugins: community-investor, autonomous trader, and intel with reduced dependencies on external systems, plus architectural improvements. (Odilitime)\n\n- Q: What is the team's marketing plan for spartan? \n A: Cross-promotion with auto.fun launch, developing web presence, and working to get Spartan posting on Twitter again. (Odilitime)\n\n- Q: Will the cross promotion between spartan and auto.fun start on April 14th? \n A: More like after the 14th, definitely won't be at launch. (Odilitime)\n\n**DAO Organization**\n- Q: How will DAO participation be incentivized? \n A: Jin is developing a system to measure participation/contributions, with rewards including both tokens and status/reputation elements like badges and NFTs. (jin)\n\n- Q: Can the reputation system be tested in the working group before DAO-wide rollout? \n A: Jin confirmed it could be used for early feedback, noting the system is mostly passive. (jin)\n\n## Community Help & Collaboration\n\n**Twitter Plugin Issues**\n- Helper: notorious_d_e_v | Helpee: 0xLabsTheCoder \n Context: Twitter plugin interactions not working \n Resolution: Suggested enabling TWITTER_SEARCH_ENABLE=true and shared a custom Twitter client using API access instead of scraping\n\n**TypeScript Configuration**\n- Helper: wookosh | Helpee: jonathanmann \n Context: TypeScript error with hapi__shot types \n Resolution: Fixed by adding \"types\": [\"node\"] to tsconfig.json\n\n**Custom Chatbot Issues**\n- Helper: notorious_d_e_v | Helpee: SkyBLUE \n Context: Custom chatbot responding with LLM responses instead of custom answers \n Resolution: Suggested removing the downloaded llama model by searching for files >400MB and deleting the SQLite database from ./agent/data/\n\n**Discord Channel Management**\n- Helper: Kenk | Helpee: Multiple users \n Context: Cleaning up spam in the channel \n Resolution: Kenk mentioned \"cleaned it up but strangely i couldn't ban them...\"\n\n**MCP Understanding**\n- Helper: Odilitime | Helpee: hubert \n Context: Understanding MCP servers and their future role \n Resolution: Explained MCP as a bridge between static APIs and dynamic agents, predicting gradual then sudden adoption\n\n**Content Feedback**\n- Helper: jin | Helpee: Channel members \n Context: Sharing Clank Tank episode preview for feedback \n Resolution: Received feedback on audio issues and episode length, decided to cut content by 50%\n\n## Action Items\n\n### Technical\n- Fix Twitter plugin interactions in v1.0.0-beta.27 for retweets, quote reposts, and message replies (0xLabsTheCoder)\n- Resolve issue with plugin-tee generating the same key regardless of parameters (ShisukeUrahara)\n- Fix TypeScript error with hapi__shot types in new projects (jonathanmann)\n- Address API endpoint 404 error for /api/agents/:agentId/message despite documentation (Newt)\n- Fix RAG functionality that appears to not be working (jonathanmann)\n- Resolve issue with model selection defaulting to local LLM despite OpenRouter configuration (Trixi)\n- Implement three exclusive plugins for Spartan V2 (community-investor, autonomous trader, and intel) (Odilitime)\n- Reduce dependencies on external systems in V2 (Odilitime)\n- Implement architectural improvements for cross-platform presence (Odilitime)\n- Create an ElizaOS agent registry with capability discovery and trust scores (DorianD)\n- Optimize Clank Tank episode length by reducing by at least 50% (jin)\n- Launch Auto.fun with 15 partners (anon)\n- Develop and test the reputation/contribution measurement system (jin)\n- Develop web-based character creator with wallet integration (jin)\n\n### Documentation\n- Clarify why GitHub token is needed and if users can opt out (jonathanmann)\n- Update documentation to match actual code structure (directory discrepancy noted) (jonathanmann)\n- Add canonical character descriptions to docs with thumbnails (jin)\n- Create cookbook/recipes section in documentation (jin)\n- Create a member directory for the DAO (vincentpaul)\n- Create short-term web presence for Spartan (Odilitime)\n- Finalize working circle structure and leadership (vincentpaul)\n\n### Feature\n- Support for UVX MCP servers integration with ElizaOS (jonathanmann)\n- Add way to easily share contents of popular plugins with cursor (jonathanmann)\n- Enable no chain switching in V2 (Odilitime)\n- Implement workflows and dynamic characters in V2 (Odilitime)\n- Cross-promotion between Spartan and auto.fun (Odilitime)\n- Develop agentic Vtubers using character animation (Odilitime)\n- Launch crypto news agent for the platform (Zolo)\n- Implement weekly investor newsletter for token holders (Odilitime)\n- Secure regular monthly AMA/Town hall sessions (vincentpaul)" }, "ai_news_elizaos_dev_md_2025-04-10": { "filename": "2025-04-10.md", "content": "# elizaOS Development Discord - 2025-04-10\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Migration and Implementation\n- The community is actively working on migrating plugins from v1 to v2\n- V2 rollout is still in progress, not yet fully stable\n- Users are utilizing the monorepo setup command (`npx @elizaos/cli@beta setup-monorepo`) for migration\n- Some users are experiencing package management errors when installing plugins in v2\n- A critical bug in v1 related to a dependency update is causing problems\n\n### Recurring Tasks Implementation\n- Discussion about implementing recurring tasks for posting messages to Discord channels\n- Clarification that the `createTask` function is a v2 feature (available in `v2-develop` branch)\n- Alternative approaches for v1 users were suggested, involving custom service classes with timer functionality\n\n### Twitter Integration Issues\n- Users reported problems with Twitter integration not connecting to their Characters\n- Discussion about Twitter API access and credentials not being recognized by the dashboard\n\n## Key Questions & Answers\n\n**Q: How do I migrate a plugin to be used in v2?** (asked by LemonS) \n**A:** Use `npx @elizaos/cli@beta setup-monorepo`, check package/plugin-starter/index.ts for structure, or look at other plugins like openai and twitter (answered by sayonara)\n\n**Q: Is v2 fully out and stable, or is the rollout still happening?** (asked by Matthew Liu) \n**A:** Roll out is still happening (answered by Odilitime)\n\n**Q: Is task working in ElizaOS? AgentRuntime class does not have `createTask` function** (asked by Martin Rivera) \n**A:** It's a v2 feature, you need to use `git checkout origin/v2-develop` (answered by shaw)\n\n**Q: Is there alternative in V1? I want to run action every hour to post messages in Discord Channel** (asked by Martin Rivera) \n**A:** You can make a service that gets the runtime discord client (runtime.getClient) and calls post on a loop. Look at other Service type classes, you just need one that starts a timer in constructor (answered by shaw)\n\n**Q: Service is also `v2` feature.** (asked by Martin Rivera) \n**A:** Should be in v1 as well, I consolidated services and clients, but for example, a pdf service, but its just some class on runtime that can call other stuff (answered by shaw)\n\n## Community Help & Collaboration\n\n### Plugin Migration Assistance\n- **sayonara** helped **LemonS** with migrating a plugin to v2 by providing CLI command for monorepo setup and suggesting checking plugin-starter structure\n- **Nisita** reinforced sayonara's advice and shared a video resource with disclaimer about possible changes\n- **Ξ2T** acknowledged successful help from another user with getting v2 set up\n\n### Recurring Tasks Implementation\n- **shaw** guided **Martin Rivera** through implementing recurring tasks in ElizaOS v1, suggesting a custom service with timer functionality as an alternative to the v2 `createTask` function\n\n## Action Items\n\n### Technical\n- Fix v1 bug related to dependency update in PR #4232 (mentioned by shaw)\n- Complete the v2 rollout to address package management errors when installing plugins (mentioned by Matthew Liu)\n- Implement a custom service class with timer functionality for recurring Discord messages in ElizaOS v1 (mentioned by shaw)\n\n### Documentation\n- Update documentation for tasks in ElizaOS v2 as the AgentRuntime class doesn't have createTask function (mentioned by Martin Rivera)\n- Document differences between v1 and v2 features in ElizaOS to clarify which features like tasks and services are available in which versions (mentioned by shaw)" }, "ai_news_elizaos_dev_md_2025-04-09": { "filename": "2025-04-09.md", "content": "# elizaOS Development Discord - 2025-04-09\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Migration & Architecture\n- The architecture has significantly changed from v1 to v2:\n - The \"agent\" package has been moved into \"cli\" with REST API integration\n - Agents are now database-driven rather than client-driven, enabling programmatic creation\n - REST API is now natively integrated into the system\n- Users are actively working through the beta CLI setup process\n- GitHub authentication is now required during fresh installation before interacting with the default character\n\n### Plugin Development\n- Community members are collaborating on plugin migration strategies for v2\n- The `setup-monorepo` command is being recommended as a starting point\n- The plugin-starter structure is being referenced as a template for new plugin development\n- Several users are looking for guidance on how to adapt existing plugins to the new architecture\n\n### API Integration\n- Questions about REST API availability in v2 are emerging\n- At least one user reported difficulties with message endpoints returning 404 errors despite agent showing active status\n- Google Generative AI enterprise version configuration support is being questioned\n\n## Key Questions & Answers\n\n**Q: How has the architecture changed from v1 to v2?** (asked by standard) \n**A:** The \"agent\" package moved into \"cli\" with REST API integration, and agents are now database-driven for programmatic creation (answered by shaw)\n\n**Q: How do I migrate a plugin to be used in v2?** (asked by LemonS) \n**A:** Use `npx @elizaos/cli@beta setup-monorepo`, check package/plugin-starter/index.ts structure or other plugins like openai and twitter (answered by sayonara)\n\n**Q: Should I watch the existing AI Agent Dev School videos or wait for new content after v2?** \n**A:** It's recommended to wait, especially for those completely new to the subject\n\n## Community Help & Collaboration\n\n- **shaw** helped **standard** understand the new architecture by explaining how the agent package moved to CLI, REST API integration, and database-driven agents\n- **sayonara** assisted **LemonS** with plugin migration to v2 by providing the CLI command for setup-monorepo and suggesting reference points\n- **Nisita** reinforced advice to **LemonS** about plugin migration and shared a video resource (with disclaimer about possible changes)\n- An unnamed community member successfully helped **Ξ2T** set up v2 late at night\n\n## Action Items\n\n### Technical\n- Fix REST API message endpoint for v2 (message endpoint returns 404 despite agent showing active status) | Mentioned by: Titan | Livepeer-Eliza.com\n- Address GitHub authentication requirement during fresh installation (CLI requires GitHub credentials before allowing interaction with default character) | Mentioned by: Titan | Livepeer-Eliza.com\n- Resolve installation issues with error message shown in screenshot (user encountering errors when trying to start Eliza) | Mentioned by: AbdelazizElbagdadi\n- Investigate support for Google Generative AI enterprise version configuration | Mentioned by: lay.qin\n\n### Documentation\n- Create migration guide for v1 to v2 (users struggling to understand architectural changes) | Mentioned by: standard\n- Document plugin migration process for v2 (clear steps needed for converting existing plugins) | Mentioned by: LemonS\n- Update or create new AI Agent Dev School content for v2 | Implied by discussion in agent-dev-school channel" }, "ai_news_elizaos_dev_md_2025-04-08": { "filename": "2025-04-08.md", "content": "# elizaOS Development Discord - 2025-04-08\n\n## Overall Discussion Highlights\n\n### ElizaOS V2 Architecture & Implementation\n- The architecture in V2 has undergone significant changes with the \"agent\" package moving into \"cli\" and REST API being merged\n- V2 represents a paradigm shift from V1's client-driven model to a database-driven approach, allowing programmatic agent creation\n- Users are adapting to the new AgentRuntime as the key code for standalone builds\n- GitHub token requirements during installation have been a point of confusion for users\n\n### Integration & Configuration\n- OpenRouter integration with Eliza V2 can be achieved by configuring the OpenAI plugin with custom settings\n- Configuration includes setting OPENAI_BASE_URL, models, and embedding configurations\n- Questions arose about Google Generative AI enterprise version configuration support\n\n### Community Events\n- A weekly demo session was announced for 3pm UTC where builders can showcase their agents or plugins\n- Community members were invited to register for future demo sessions via a Tally form\n\n### Pull Requests & Code Updates\n- A pull request for the BNB plugin was merged (https://github.com/elizaos-plugins/plugin-bnb/pull/3/files)\n\n## Key Questions & Answers\n\n**Q: How should I use OpenRouter with Eliza V2?** \nA: Use the OpenAI plugin with custom settings in the character file including OPENAI_BASE_URL, models, and embedding configurations (answered by 0xavp.eth)\n\n**Q: Why does Eliza V2 need GitHub token access?** \nA: It's only required to publish plugins and download plugins from GitHub (answered by sayonara)\n\n**Q: What are the architectural changes in V2?** \nA: The agent package moved to CLI, agents are now database-driven instead of client-driven, and the REST API has been merged (answered by shaw)\n\n## Community Help & Collaboration\n\n### V2 Architecture Guidance\n- **Helper:** shaw\n- **Helpee:** standard\n- **Context:** Understanding the new architecture in V2\n- **Resolution:** Explained that the agent package moved to CLI, agents are now database-driven, and pointed to \"new AgentRuntime\" as the key code to adapt for standalone builds\n\n### GitHub Token Requirements\n- **Helper:** yung_algorithm\n- **Helpee:** Titan | Livepeer-Eliza.com\n- **Context:** Issues with GitHub token requirements\n- **Resolution:** Mentioned a PR is up to address the issue and will notify when merged\n\n## Action Items\n\n### Technical\n- Fix GitHub token requirement during ElizaOS V2 installation (mentioned by yung_algorithm)\n- Address REST API message endpoint returning 404 errors (mentioned by Titan | Livepeer-Eliza.com)\n\n### Documentation\n- Document the architectural changes from V1 to V2 for custom client developers (mentioned by standard)\n- Provide guidance on whether to watch existing AI Agent Dev School videos or wait for V2 content (raised by superblob)\n\n### Feature\n- Investigate support for Google Generative AI enterprise version configuration (mentioned by lay.qin)\n\n### Community\n- Follow up on weekly demo session registrations (organized by Kenk)" }, "ai_news_elizaos_daily_json_2025-04-10": { "filename": "2025-04-10.json", "content": { "type": "elizaosDailySummary", "title": "Daily Report - 2025-04-10", "categories": [ { "title": "Twitter Conversations on Crypto, AI, and Tech Culture", "content": [ { "text": "The tweets cover various discussions about cryptocurrency, AI technology, and tech culture. @dankvr discusses wallet security concerns, calling ENS domains 'practically a honeypot for your wallet' since owners must keep them for life to prevent scammers from sniping them. They also mention AI compressing the 3D production pipeline and recommend compartmentalizing which LLMs to use for different purposes, suggesting local AI for real-life matters for better operational security.", "sources": [ "https://twitter.com/dankvr/status/1910391791934648800", "https://twitter.com/dankvr/status/1910431544675545314", "https://twitter.com/dankvr/status/1910182023328571478" ], "images": [ "https://pbs.twimg.com/media/GoJT-IRW0AAScYV.jpg" ], "videos": [] }, { "text": "@shawmakesmagic discusses the nature of successful tech founders, noting that 'People who think that founders should be nice haven't met Steve Jobs, Palmer Luckey, Peter Thiel, Elon Musk, Linus Torvalds or literally anyone who built the modern internet. Confrontational people don't make shitty products by committee.' He observes there's 'something about the quality of a person who is willing to violate social rules that leads to outsize success in rare cases.'", "sources": [ "https://twitter.com/shawmakesmagic/status/1910398462685774224", "https://twitter.com/shawmakesmagic/status/1910408117839684044" ], "images": [], "videos": [] }, { "text": "Shaw also contrasts two crypto cultures: 'One is on Twitter, one is on LinkedIn,' noting that LinkedIn crypto people are 'Nice people, nicer than CT tbh.' He expresses frustration at being called a grifter while working hard on projects like ai16z, stating 'My entire net worth is my ai16z bag' and 'I haven't sold a single token since we started.' He mentions constantly choosing between coding and communicating, working without days off, even on his birthday.", "sources": [ "https://twitter.com/shawmakesmagic/status/1910388870958493870", "https://twitter.com/shawmakesmagic/status/1910388334918242492", "https://twitter.com/shawmakesmagic/status/1910387503321805123" ], "images": [], "videos": [] }, { "text": "On AI development, Shaw advocates for open-sourcing models, noting 'Sam [Altman] said they were getting on it and next release would be an open one.' He suggests OpenAI is revising their approach after 'getting their ass kicked by deepseek' and mentions that while 'Sam seems very pro open source,' many at OpenAI are 'captured by the fearmongering doomer contingent and feel like they risk giving away nukes.'", "sources": [ "https://twitter.com/shawmakesmagic/status/1910294404390174734", "https://twitter.com/shawmakesmagic/status/1910303068047974685", "https://twitter.com/shawmakesmagic/status/1910303367101808827" ], "images": [], "videos": [] } ], "topic": "tweet" }, { "title": "Recent ElizaOS GitHub Pull Requests", "content": [ { "text": "Several UI improvements have been implemented, including replacing text input with dropdown for voice model selection (#4262) and adding message buttons (#4187). A new message API has also been introduced (#4247).", "sources": [ "https://github.com/elizaOS/eliza/pull/4262", "https://github.com/elizaOS/eliza/pull/4187", "https://github.com/elizaOS/eliza/pull/4247" ], "images": [], "videos": [] }, { "text": "OpenAI TTS (Text-to-Speech) functionality has been added to the platform with both implementation (#4255) and testing (#4259) pull requests merged.", "sources": [ "https://github.com/elizaOS/eliza/pull/4255", "https://github.com/elizaOS/eliza/pull/4259" ], "images": [], "videos": [] }, { "text": "Multiple Discord-related fixes have been applied, addressing issues with Discord actions (#4264) and Discord voice join/leave functionality (#4265).", "sources": [ "https://github.com/elizaOS/eliza/pull/4264", "https://github.com/elizaOS/eliza/pull/4265" ], "images": [], "videos": [] }, { "text": "Plugin system improvements include adding a missing bootstrap plugin to the list (#4267), fixing plugin installation priority order (#4256), and removing dead code around plugin installation (#4263).", "sources": [ "https://github.com/elizaOS/eliza/pull/4267", "https://github.com/elizaOS/eliza/pull/4256", "https://github.com/elizaOS/eliza/pull/4263" ], "images": [], "videos": [] }, { "text": "Several bug fixes have been implemented, including resolving a cyclic error (#4266), replacing a deprecated vision model (#4254), moving initialization after adapter.init in runtime (#4253), and removing duplicate declaration in api.ts (#4246).", "sources": [ "https://github.com/elizaOS/eliza/pull/4266", "https://github.com/elizaOS/eliza/pull/4254", "https://github.com/elizaOS/eliza/pull/4253", "https://github.com/elizaOS/eliza/pull/4246" ], "images": [], "videos": [] }, { "text": "CLI and code improvements have been made to enhance the developer experience, including improved CLI and start code (#4250) and using console log for non-error cases (#4248).", "sources": [ "https://github.com/elizaOS/eliza/pull/4250", "https://github.com/elizaOS/eliza/pull/4248" ], "images": [], "videos": [] }, { "text": "A reflections agent has been implemented that asks all other deployed agents how it's doing (#4257).", "sources": [ "https://github.com/elizaOS/eliza/pull/4257" ], "images": [], "videos": [] } ], "topic": "completed_items" }, { "title": "Discord Channel Historical Summary", "content": [ { "text": "# Eliza OS Development and Issues\n\nThe Discord chat focused on technical issues and updates related to Eliza OS, particularly around version compatibility, plugin development, and deployment challenges.\n\n## Key Points:\n\n- **Version Compatibility**: Users reported issues with Eliza OS v2, with many finding v0.25.9 to be the most stable version. Twitter plugin functionality was particularly problematic in v2, with users discovering that setting `TWITTER_ENABLE_POST_GENERATION=true` in the .env file was necessary.\n\n- **Plugin Development**: Significant confusion exists around plugin compatibility across versions. For example, @elizaos/client-discord only works on 0.1.9, while @elizaos/plugin-discord is compatible with v1.0.0. Users also faced MongoDB adapter issues, which could be resolved by adding `\"types\": [\"node\"]` to tsconfig.json.\n\n- **Build Errors**: Multiple users reported build failures and dependency conflicts, particularly when using different package managers (npm/bun/pnpm). Common errors included issues with hapi-shot and dynamic require errors when using bun install on WSL2.\n\n- **Language Support**: Discussions confirmed that non-English languages like Chinese are supported in Twitter bots if the character is defined in the appropriate language and Twitter parsing is adjusted accordingly.\n\n- **Documentation Gaps**: Users highlighted poor documentation and lack of working examples, especially for Windows/WSL users, with suggestions for better tutorials and community best practices.", "sources": [ "https://discord.com/channels/1253563208833433701/1300025221834739744" ], "images": [], "videos": [] }, { "text": "# Trading and Analysis on Pump.fun\n\nThe Discord chat primarily revolves around real-time trading and analysis of meme coins on the Solana-based platform Pump.fun. Users actively share contract addresses, track market caps, and discuss token performance metrics.\n\n## Key Points:\n\n- **Token Performance**: Retard Finance (ReFi/SOL) was the standout performer, with users tracking its rise from 349K to 2.9M market cap (10.6K% gain). Other notable tokens included MASTERTARD (MT/SOL), AGiXT (AGiXT/SOL), StupidCoin (Stupid/SOL), and Physical Bitcoin (Birkin/SOL).\n\n- **Technical Analysis**: Users employed RSI indicators, wallet tracking, and bundling percentages to assess entry points and risk. For example, StupidCoin was flagged for breaking above 50 RSI on the daily chart, suggesting a potential breakout post-consolidation.\n\n- **Trading Strategies**: Discussions included leveraged perp trading using platforms like Axiom with Hyperliquid, with users sharing position sizing strategies (e.g., \"a couple G's at 5x leverage\"). Some users utilized NFT loans to fund positions.\n\n- **Market Trends**: ChatGPT image-based meme coins (e.g., Ghibli, Figure) were identified as the current meta, though no new standout had emerged at the time of discussion.", "sources": [ "https://discord.com/channels/1253563208833433701/1299989396874854440" ], "images": [], "videos": [] }, { "text": "# AI Infrastructure and Decentralized Registries\n\nThe chat focused on technical discussions around AI agent infrastructure, decentralized registries, and upcoming product launches.\n\n## Key Points:\n\n- **MCP Server Registry**: doriand0963 and notrickfox discussed the need for a decentralized, on-chain registry that aggregates Model Context Protocol (MCP) servers and includes agent-generated feedback, reviews, and usage data. notrickfox mentioned their team is already building a \"registry of registries\" with a voting system to surface reputable servers.\n\n- **Auto.fun Launch**: The community discussed the upcoming launch of auto.fun, with a tentative release date of April 14. There was some confusion about the exact date, but odilitime and delimorte confirmed it was still on track.\n\n- **Governance Improvements**: vincentpaul8 emphasized the need for a fair governance protocol to allow community members to post in announcement channels. yikesawjeez and others discussed the need for better proposal submission tools and governance artifacts beyond informal DMs.\n\n- **Clank Tank Development**: dankvr shared progress on Clank Tank, a DAO pitch show, exploring Tally integrations and Discord webhooks to streamline submission reviews.", "sources": [ "https://discord.com/channels/1253563208833433701/1301363808421543988" ], "images": [], "videos": [] }, { "text": "# SpartanV2 Development\n\nThe chat segment primarily revolves around the ongoing development of SpartanV2, a new version of an agent.\n\n## Key Points:\n\n- **Development Status**: odilitime confirmed that the team is still working on SpartanV2 and has not yet upgraded from v1. However, they agreed to allow the current agent to remain active (\"yapping\") on v1 while development continues.\n\n- **Feature Implementation**: zolo_go suggested adding a contract address to the account profile, which odilitime promptly implemented and confirmed with a \"Done\" message.\n\n- **User Base Recovery**: There was a brief discussion about the potential to recover a previously lost follower base (25k followers), which odilitime suggested may be possible, though no technical details were provided.", "sources": [ "https://discord.com/channels/1253563208833433701/1308149076893630555" ], "images": [], "videos": [] }, { "text": "# Grok 3 and Eliza OS Integrations\n\nThe Discord chat focused on technical issues and updates related to OpenRouter and Eliza OS integrations, particularly around the new Grok 3 and Grok 3 Mini models, Twitter plugin functionality, and Eliza OS version stability.\n\n## Key Points:\n\n- **Grok Models**: Grok 3 and Grok 3 Mini were launched with distinct strengths. Grok 3 excels in structured tasks and benchmarks (GPQA, LCB, MMLU-Pro), while Grok 3 Mini performs better in reasoning tasks (AIME'24/25) and supports transparent reasoning traces. Both support a 131,072-token context window, with Grok 3 Mini being significantly cheaper.\n\n- **Eliza OS Issues**: Users reported issues with Eliza OS v2, particularly with the Twitter plugin not functioning autonomously. A workaround involved reverting to v1, though that introduced build errors (e.g., hapi-shot). The most stable version reported was 0.25.9.\n\n- **MongoDB Adapter**: Users encountered issues with the MongoDB adapter, which were resolved by adding `\"types\": [\"node\"]` to tsconfig.json.\n\n- **Plugin Compatibility**: A major recurring issue was the incompatibility of plugins across Eliza OS versions. For example, @elizaos/client-discord only works on 0.1.9, while @elizaos/plugin-discord is compatible with v1.0.0.\n\n- **New Models**: Optimus Alpha, a new stealth model with a 1M token context window, was announced. It is optimized for general tasks and coding, available for free during the preview period.", "sources": [ "https://discord.com/channels/1253563208833433701/1300025221834739744" ], "images": [], "videos": [] } ], "topic": "discordchannelhistoricalsummary" }, { "title": "Recent Pull Requests in elizaOS/eliza Repository", "content": [ { "text": "Several pull requests have been submitted to the elizaOS/eliza repository recently. Contributors Y4NK33420, wtfsayo, and tcm390 have been active in submitting changes. wtfsayo has focused on CLI improvements with PRs #4248, #4250, and #4256, addressing console logging for non-error cases, improving CLI and start code, and fixing plugin installation priority order respectively. Meanwhile, tcm390 has submitted multiple PRs (#4264, #4265, and #4266), and Y4NK33420 contributed PR #4262. These pull requests represent ongoing development efforts to enhance the eliza project.", "sources": [ "https://github.com/elizaOS/eliza/pull/4262", "https://github.com/elizaOS/eliza/pull/4263", "https://github.com/elizaOS/eliza/pull/4264", "https://github.com/elizaOS/eliza/pull/4265", "https://github.com/elizaOS/eliza/pull/4266", "https://github.com/elizaOS/eliza/pull/4248", "https://github.com/elizaOS/eliza/pull/4250", "https://github.com/elizaOS/eliza/pull/4256" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4262", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4263", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4264", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4265", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4266", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4248", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4250", "https://opengraph.githubassets.com/1/elizaOS/eliza/pull/4256" ], "videos": [] } ], "topic": "pull_request" }, { "title": "Recent GitHub Issues in the elizaOS/eliza Repository", "content": [ { "text": "The elizaOS/eliza repository has several open issues that need attention. These include technical problems like the Discord client not loading on pnpm start (issue #4258) and the Anthropic plugin not registering for TEXT_EMBEDDING (issue #4251). There's also a community-related issue requesting an update to the community section (issue #4260). Other issues include #3491 by roninjin10, #2919 by LinuxIsCool, #3664 by suryanshkushwaha, and #4269 by jiggyjo11, though specific details about these issues aren't provided in the sources.", "sources": [ "https://github.com/elizaOS/eliza/issues/4258", "https://github.com/elizaOS/eliza/issues/4251", "https://github.com/elizaOS/eliza/issues/4260", "https://github.com/elizaOS/eliza/issues/3491", "https://github.com/elizaOS/eliza/issues/2919", "https://github.com/elizaOS/eliza/issues/3664", "https://github.com/elizaOS/eliza/issues/4269" ], "images": [ "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4258", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4251", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4260", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/3491", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/2919", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/3664", "https://opengraph.githubassets.com/1/elizaOS/eliza/issues/4269" ], "videos": [] } ], "topic": "issue" }, { "title": "ElizaOS GitHub Activity Update", "content": [ { "text": "The elizaos/eliza repository has shown consistent activity over the past two days. From April 10-11, there were 13 new pull requests with 11 merged, 4 new issues, and 14 active contributors. Activity slightly decreased the following day (April 11-12) with 6 new pull requests (all merged), 1 new issue, and 8 active contributors.", "sources": [ "From 2025-04-11 to 2025-04-12, elizaos/eliza had 6 new PRs (6 merged), 1 new issues, and 8 active contributors.", "From 2025-04-10 to 2025-04-11, elizaos/eliza had 13 new PRs (11 merged), 4 new issues, and 14 active contributors." ], "images": [], "videos": [] } ], "topic": "github_summary" }, { "title": "Top contributors for elizaOS/eliza", "content": [ { "text": "The provided sources mention 'Top contributors for elizaOS/eliza' but do not provide any specific details about who these contributors are or their contributions to the project. Without additional information, it's not possible to generate a detailed summary about the individual contributors, their roles, or the nature of their contributions to the elizaOS/eliza project.", "sources": [ "Top contributors for elizaOS/eliza" ], "images": [], "videos": [] } ], "topic": "contributors" } ], "date": 1744243200 } }, "ai_news_elizaos_daily_md_2025-04-10": { "filename": "2025-04-10.md", "content": "# Twitter Conversations on Crypto, AI, and Tech Culture\n\n## Wallet Security and AI Technology\n- @dankvr discussed ENS domains as potential security risks for wallets\n- Highlighted AI's role in compressing 3D production pipelines\n- Recommended compartmentalizing LLMs for different purposes, with local AI for personal matters\n\n## Tech Founder Characteristics\n- @shawmakesmagic observed that successful tech founders often have confrontational personalities\n- Noted that \"people who think founders should be nice\" haven't met figures like Jobs, Luckey, Thiel, Musk, or Torvalds\n- Identified a correlation between willingness to violate social rules and outsized success\n\n## Crypto Culture Contrasts\n- Shaw distinguished between Twitter and LinkedIn crypto communities\n- Shared personal experiences working on ai16z project\n- Described balancing coding and communication responsibilities\n\n## AI Development Perspectives\n- Shaw advocated for open-sourcing models\n- Reported that Sam Altman indicated OpenAI's next release would be open\n- Noted OpenAI's competitive response to deepseek\n- Described internal tensions at OpenAI between open-source advocates and those concerned about safety risks\n\n# Recent ElizaOS GitHub Pull Requests\n\n## UI Improvements\n- Replaced text input with dropdown for voice model selection (#4262)\n- Added message buttons (#4187)\n- Introduced new message API (#4247)\n\n## Text-to-Speech Integration\n- Added OpenAI TTS functionality (#4255)\n- Implemented TTS testing (#4259)\n\n## Discord Functionality\n- Fixed Discord actions (#4264)\n- Resolved Discord voice join/leave functionality (#4265)\n\n## Plugin System Enhancements\n- Added missing bootstrap plugin to the list (#4267)\n- Fixed plugin installation priority order (#4256)\n- Removed dead code around plugin installation (#4263)\n\n## Bug Fixes\n- Resolved cyclic error (#4266)\n- Replaced deprecated vision model (#4254)\n- Moved initialization after adapter.init in runtime (#4253)\n- Removed duplicate declaration in api.ts (#4246)\n\n## Developer Experience\n- Improved CLI and start code (#4250)\n- Used console log for non-error cases (#4248)\n\n## New Features\n- Implemented reflections agent that asks all other deployed agents for feedback (#4257)\n\n# Discord Channel Historical Summary\n\n## Eliza OS Development and Issues\n- Users reported version compatibility issues, with v0.25.9 identified as most stable\n- Twitter plugin functionality required specific environment variable configuration\n- Plugin compatibility varied across versions with specific version requirements\n- Build errors occurred with different package managers\n- Non-English language support confirmed for Twitter bots\n\n## Trading and Analysis on Pump.fun\n- Retard Finance (ReFi/SOL) showed significant performance (10.6% gain)\n- Users employed technical analysis including RSI indicators and wallet tracking\n- Trading strategies included leveraged perp trading and NFT loans\n- ChatGPT image-based meme coins identified as current market trend\n\n## AI Infrastructure and Decentralized Registries\n- Discussions on MCP Server Registry with decentralized, on-chain capabilities\n- Auto.fun launch planned for April 14\n- Governance improvements proposed for community participation\n- Progress shared on Clank Tank DAO pitch show development\n\n## SpartanV2 Development\n- Confirmed ongoing development while maintaining v1 functionality\n- Implemented contract address feature in account profile\n- Discussed potential recovery of previously lost follower base\n\n## Grok 3 and Eliza OS Integrations\n- Launched Grok 3 and Grok 3 Mini models with distinct strengths\n- Reported Eliza OS v2 issues, particularly with Twitter plugin\n- Resolved MongoDB adapter issues with tsconfig.json modification\n- Identified plugin compatibility challenges across versions\n- Announced Optimus Alpha model with 1M token context window\n\n# GitHub Activity Update\n\n## Repository Activity\n- April 10-11: 13 new pull requests (11 merged), 4 new issues, 14 active contributors\n- April 11-12: 6 new pull requests (all merged), 1 new issue, 8 active contributors\n\n## Recent Pull Requests\n- Contributors Y4NK33420, wtfsayo, and tcm390 actively submitting changes\n- wtfsayo focused on CLI improvements (PRs #4248, #4250, #4256)\n- tcm390 submitted multiple PRs (#4264, #4265, #4266)\n- Y4NK33420 contributed PR #4262\n\n## Open Issues\n- Discord client not loading on pnpm start (issue #4258)\n- Anthropic plugin not registering for TEXT_EMBEDDING (issue #4251)\n- Request to update community section (issue #4260)\n- Additional issues: #3491, #2919, #3664, #4269" }, "ai_news_elizaos_daily_discord_json_2025-04-10": { "filename": "2025-04-10.json", "content": { "server": "elizaOS", "title": "elizaOS Discord - 2025-04-10", "date": 1744243200, "stats": { "totalMessages": 317, "totalUsers": 71 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThis Discord chat segment from the \"discussion\" channel contains minimal substantive technical discussion. The conversation primarily consists of greetings (\"gm\", \"hi\"), brief questions, and administrative messages. There is a question about calling plugins to agents, suggesting the channel may be related to AI agent development. There's mention of \"Eliza studio ai\" with a timer counting down to something happening in 4 days. A user asked about \"v2\" being online and tokenomics changes. There's confusion about Grayscale potentially investing in \"$ELIZA\" and discussion about a suspended Twitter account for \"degenspartanai\" that's being rebuilt as a flagship agent for V2. The chat also contains some administrative messages directing users to other channels and removing spam.\n\n## 2. FAQ\nQ: How can I call plugin to the agent? Do we have to create a folder for plugin and then import them there? (asked by Ved Mohan) A: Unanswered\nQ: Is it true that Grayscale is investing in $ELIZA or is the ticker just wrong? (asked by cloudAI) A: Unanswered\nQ: Is v2 already online? The tokenomics changes came with it? (asked by Choranão) A: Unanswered\nQ: Did degenspartanai move to another handle or is the project stopped? (asked by cryptokevin2011) A: Twitter acct was suspended. It's being re-built as a flagship agent for V2. (answered by Osint (aka not_in_a_dao_ai) and Kenk)\nQ: May I know why there is a timer in Eliza studio ai that page? Something happen after 4 days later? (asked by Mez) A: Unanswered\nQ: How to verify? (asked by zxcv) A: Check your DMs (answered by Kenk)\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: cryptokevin2011 | Context: User asking about status of degenspartanai Twitter account | Resolution: Explained it's being re-built as a flagship agent for V2\nHelper: Patt | Helpee: cryptokevin2011 | Context: Concern about suspended Twitter account | Resolution: Explained team is pursuing both restoring old account and claiming alternate account\nHelper: Kenk | Helpee: zxcv | Context: User asking how to verify | Resolution: Directed user to check DMs for verification instructions\n\n## 4. Action Items\nTechnical: Fix DAOS FUN issue | Description: An unspecified problem with DAOS FUN that needs fixing | Mentioned By: Poloethr\nTechnical: Rebuild degenspartanai as flagship agent for V2 | Description: Rebuilding suspended project as part of V2 | Mentioned By: Kenk\nTechnical: Restore or replace Twitter account | Description: Team pursuing restoration of suspended account or claiming alternate | Mentioned By: Patt\nFeature: Use alternative platform for voting to change ticker | Description: Suggestion to use different platform for ticker change voting | Mentioned By: Poloethr", "messageCount": 47, "userCount": 25 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary\n\nThe chat primarily revolves around issues with Eliza OS, an agent framework with various versions (v1, v2, beta) causing compatibility problems. Users struggle with installation errors, particularly related to dependencies and build processes. The Twitter plugin functionality is a common pain point, with users trying to get autonomous posting working. Several users report the \"hapi__shot\" error when building different versions. \n\nThe chat reveals that v0.25.9 appears to be the most stable version according to some users, though plugin compatibility varies across versions. There are discussions about using different package managers (npm, pnpm, bun) to resolve dependency issues. Some users share workarounds like adding `\"types\": [\"node\"]` to tsconfig.json to fix specific errors.\n\nOpenRouter made several announcements about new models (Grok 3, Grok 3 Mini, Optimus Alpha) and service updates. The community seems frustrated with the lack of comprehensive documentation and the difficulty in getting a stable, working implementation of Eliza OS with desired plugins.\n\n## 2. FAQ\n\nQ: How can I fix the \"Dynamic require of 'child_process' is not supported\" error? (asked by Bundinho) A: Add `\"types\": [\"node\"]` to tsconfig.json (answered by wookosh and tsk0yo)\nQ: Is it possible to get discord working on 0.25.9? (asked by wookosh) A: Unanswered\nQ: How can I call plugin to the agent? (asked by Ved Mohan) A: Yes (answered by notorious_d_e_v)\nQ: How do you test your plugins in v2? (asked by Tobiloba) A: Unanswered\nQ: Can I change the language of Eliza? (asked by buttercup) A: Yes, if you define your character in Chinese, LLM should respond that way (answered by _.sayonara)\nQ: Is the task functionality working? (asked by hotcode101) A: It's only on v2 and not tested too much yet (answered by _.sayonara)\nQ: Is mock-eliza not available in the starter of v1? (asked by hotcode101) A: Unanswered\nQ: How to get Eliza OS v2 beta agent running with character card and vector database in Coolify or VPS? (asked by stanleymarch) A: Unanswered\n\n## 3. Help Interactions\n\nHelper: notorious_d_e_v | Helpee: hotcode101 | Context: Setting up environment for debugging | Resolution: Suggested setting `DEFAULT_LOG_LEVEL=\"debug\"` in .env file and checking Twitter settings in .env.example\nHelper: wookosh | Helpee: apoorva99 | Context: Error with MongoDB adapter | Resolution: Suggested adding `\"types\": [\"node\"]` to tsconfig.json which fixed the issue\nHelper: notorious_d_e_v | Helpee: 0xLabsTheCoder | Context: Build issues | Resolution: Suggested using `pnpm` instead of other package managers\nHelper: Kimani | Helpee: Multiple users | Context: Setup issues with v1 | Resolution: Suggested navigating to node_modules\\better-sqlite3 directory and running pnpm run build, then building from root\nHelper: CSC35 | Helpee: 0xLabsTheCoder | Context: Twitter posting issues | Resolution: Advised setting `TWITTER_ENABLE_POST_GENERATION=true` in the .env for v2\n\n## 4. Action Items\n\nTechnical: Fix the hapi__shot error that occurs in newer versions | Description: Multiple users reporting this error when building | Mentioned By: CSC35, 0xLabsTheCoder\nTechnical: Fix compatibility issues between different package managers | Description: Users experiencing conflicts between npm, pnpm, and bun | Mentioned By: 0xChainBrain\nTechnical: Resolve the \"Dynamic require of 'child_process'\" error on WSL2 | Description: Error occurs when running bun install | Mentioned By: Bundinho\nTechnical: Fix Twitter plugin autonomous posting functionality | Description: Not working as expected in different versions | Mentioned By: hotcode101, 0xLabsTheCoder\nTechnical: Fix Discord plugin compatibility with version 0.25.9 | Description: Current plugins only work with specific versions | Mentioned By: wookosh\nDocumentation: Create clear deployment guides for VPS and cloud services | Description: Users struggle with deploying to production environments | Mentioned By: stanleymarch\nDocumentation: Improve plugin development and testing documentation for v2 | Description: Developers unsure how to properly test plugins | Mentioned By: Tobiloba\nDocumentation: Update task functionality documentation | Description: Current docs reference methods that don't exist | Mentioned By: hotcode101\nDocumentation: Create troubleshooting guide for common errors | Description: Many users face similar issues with little guidance | Mentioned By: 0xChainBrain\nFeature: Add support for scheduled actions in v1 | Description: Need to run actions at regular intervals | Mentioned By: martincontact101", "messageCount": 77, "userCount": 24 }, { "channelId": "1308149076893630555", "channelName": "spartan_holders", "summary": "# Analysis of spartan_holders Discord Chat\n\n## 1. Summary\nThe chat discusses the development and deployment of a social media agent called SpartanV2. The team is currently running version 1 while working on version 2. There's discussion about the agent's posting frequency (currently twice per hour), which some members feel is too high. The team added the contract address to the account profile upon request. There's also mention of potentially recovering 25,000 followers that were previously lost, though details aren't specified. The team appears to be keeping some aspects of the project private, instructing members not to share information with users asking in other channels.\n\n## 2. FAQ\nQ: Not on v2 now? (asked by human_nalejzpa) A: No, still working on v2, we'll upgrade when it's ready. (answered by Odilitime)\nQ: Can add this? (asked by human_nalejzpa) A: Yes (answered by Odilitime)\nQ: Will SpartanV2 be the most outstanding agent in the market? (asked by human_nalejzpa) A: Unanswered\nQ: Is there really a way to get followers back? That would be awesome. (asked by human_nalejzpa) A: Unanswered\nQ: Thoughts on if he's posting too often? Twice an hour seems on the high side (asked by kalshnikov) A: Yea, I wanted to slow it down after we can make him make better posts. (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: Zolo | Helpee: Odilitime | Context: Suggesting to add contract address to account profile | Resolution: Odilitime implemented the suggestion\n\n## 4. Action Items\nTechnical: Slow down posting frequency of SpartanV1 from twice per hour | Description: Adjust after improving post quality | Mentioned By: Odilitime\nTechnical: Continue development of SpartanV2 | Description: Upgrade when ready | Mentioned By: Odilitime\nFeature: Add contract address to account profile | Description: Include contract information in profile | Mentioned By: Zolo\nTechnical: Explore path to recover 25,000 lost followers | Description: Potential recovery of previous follower base | Mentioned By: Odilitime", "messageCount": 16, "userCount": 5 }, { "channelId": "1351627860351258685", "channelName": "dao-organization", "summary": "# Discord Channel Analysis: dao-organization\n\n## 1. Summary\nThe discussion centers on establishing the ElizaDAO structure alongside existing entities ElizaLabs and ElizaStudios. Participants organized into five working groups: Community/Governance/Events, Dev/Knowledge, Comms/Social, Partnerships/Outreach, and Tokens/Funding. Key technical discussions focused on treasury management, with consensus that a separate DAO treasury is essential for true decentralized governance. Members emphasized the need for budget allocation across working groups with designated approvers for spending. The group debated the balance between autonomous action (\"you can just do things\") and coordination with ElizaLabs to avoid duplication of efforts. Several members volunteered for specific roles based on their expertise, including event coordination, token engineering, and builder support. There was agreement on creating a DAO charter with clear values and establishing alignment with ElizaLabs' roadmap while maintaining independence. The conversation highlighted the importance of incentivizing contributors to ensure sustainability and the need for proper coordination mechanisms between the DAO and other Eliza entities.\n\n## 2. FAQ\nQ: Do we need a separate treasury for the DAO? (asked by HoneyBadger) A: Yes, without a treasury and collective decision-making, it's not truly a DAO (answered by yikesawjeez)\nQ: How should we manage DAO spending? (asked by HoneyBadger) A: Set a budget for each group with 1-2 members as \"CFO\" to approve spending (answered by HoneyBadger)\nQ: How do we balance autonomy with alignment with Labs/Studios? (asked by vincentpaul) A: Codify values in the DAO charter that balance \"you can just do things\" with coordination principles (answered by vincentpaul)\nQ: Is https://solscan.io/account/2cmQVSZuCg7MXh3XbD8vHYnKx3WDtkdZGY4t7Vi2QqSY the team's wallet? (asked by HoneyBadger) A: No, that's not a Labs wallet (answered by accelxr)\nQ: What should be the name of the DAO? (asked by hubert) A: ElizaDAO, to go with ElizaLabs and ElizaStudios (answered by vincentpaul)\n\n## 3. Help Interactions\nHelper: Patt | Helpee: vincentpaul | Context: Needed to find an introduction message from a user | Resolution: Successfully located and shared the link to the introduction\nHelper: accelxr | Helpee: HoneyBadger | Context: Incorrect identification of a wallet | Resolution: Corrected the misidentification of a wallet that was thought to belong to Labs\nHelper: vincentpaul | Helpee: Group | Context: Organizing DAO structure | Resolution: Created and updated a list of 5 working groups with assigned leaders\nHelper: yikesawjeez | Helpee: Group | Context: Governance expertise needed | Resolution: Offered to connect the group with governance experts from rndao and Hats protocol\n\n## 4. Action Items\nType: Technical | Description: Establish a separate treasury for ElizaDAO | Mentioned By: HoneyBadger, yikesawjeez\nType: Technical | Description: Create a budget allocation system for each working group | Mentioned By: HoneyBadger\nType: Technical | Description: Develop token engineering for DAO governance | Mentioned By: yikesawjeez\nType: Documentation | Description: Draft a DAO charter with clear values balancing autonomy and coordination | Mentioned By: vincentpaul\nType: Documentation | Description: Create a sign-up process for core contributors with proper verification | Mentioned By: HoneyBadger\nType: Feature | Description: Implement incentive mechanisms for sustainable contributor participation | Mentioned By: vincentpaul, Zolo\nType: Technical | Description: Align DAO roadmap with ElizaLabs' plans for Q3-Q4 | Mentioned By: HoneyBadger\nType: Documentation | Description: Define coordination protocols between ElizaDAO and ElizaLabs/Studios | Mentioned By: accelxr\nType: Feature | Description: Develop builder support program within the DAO structure | Mentioned By: Kenk\nType: Technical | Description: Schedule coordination call with ElizaLabs to establish initial steps | Mentioned By: HoneyBadger", "messageCount": 75, "userCount": 9 }, { "channelId": "1301363808421543988", "channelName": "🥇-partners", "summary": "# Analysis of 🥇-partners Discord Channel\n\n## 1. Summary\nThe channel discussions primarily focused on upcoming launches and technical developments in the AI agent ecosystem. Key topics included:\n\n- Auto.fun launch: Community members discussed the imminent release of auto.fun, initially delayed to April 14th, with team members confirming it's coming \"very very soon\" without specifying an exact date.\n\n- MCP (Model Context Protocol) servers: Several members identified a gap in the current MCP server ecosystem - the lack of an efficient way for AI agents to discover and evaluate servers. Multiple registry solutions are emerging (smithery.ai, mcp.so, mcpmarket.com), but they lack agent-centric feedback mechanisms.\n\n- Clank Tank: Jin shared Episode 3 of Clank Tank and discussed potential improvements including Tally integrations and webhooks into Discord for new submissions to make the review process more collaborative.\n\n- Registry.fun concept: DorianD proposed a whitelabel version of auto.fun that would allow MCP server operators to register, get an agent, and create a token, suggesting registry.fun as a domain.\n\n- Eliza Diary Network: DorianD mentioned a concept for giving AI agents a forum, though noted it needed rewriting.\n\nThe discussions highlight the community's focus on building infrastructure for AI agents, with particular attention to discovery mechanisms, feedback systems, and governance protocols.\n\n## 2. FAQ\nQ: Where is the best place to find updated information about the upcoming auto.fun release on 4/14? (asked by 찌 G 跻 じ PrudentSpartan) A: Partial answer from ben: \"we're not delayed more on autofun, it'll be live very very soon!\"\nQ: How do we post about our community project in announcements like Jin does for his cartoon? (asked by 찌 G 跻 じ PrudentSpartan) A: Partial answer from vincentpaul: \"We're working on fleshing out our community and governance protocol as we speak.\"\nQ: Is bio protocol launching on auto fun? (asked by anon) A: Partial answer from Kenk: \"not 100% if there's a short-term launch. their hackathon sees a plugin underpin a research cause, or in the world bioDAO a piece of scientific IP. there could be a future project that lauches on auto.fun from the hack..!\"\nQ: Did virtual get listed today? (asked by anon) A: Yes! (answered by Avanc)\nQ: Is spot still happening? I thought there were issues re: insufficient supply (asked by Smore) A: Unanswered\n\n## 3. Help Interactions\nHelper: hubert | Helpee: DorianD | Context: DorianD identified a gap in MCP server discovery where agents can't efficiently determine which servers are best for various tasks | Resolution: hubert confirmed they were spinning up \"the\" registry for MCPs with better voting mechanisms to highlight reputable servers\nHelper: Odilitime | Helpee: 찌 G 跻 じ PrudentSpartan | Context: Spartan was seeking information about auto.fun release date | Resolution: Odilitime clarified that it would be \"roughly two weeks still just like Shaw said\" and later clarified this didn't mean an additional delay\nHelper: jin | Helpee: Toni | Context: Toni commented on the 53-minute length of Clank Tank Episode 3 | Resolution: jin acknowledged it was too long due to max token output and noted future episodes should be 6-7 minutes max\n\n## 4. Action Items\nType: Technical | Description: Implement Tally integrations and Discord webhooks for Clank Tank submissions to improve collaboration | Mentioned By: jin\nType: Technical | Description: Create an MCP Server Agent that handles customer service, promotion, and registry registration for MCP servers | Mentioned By: DorianD\nType: Feature | Description: Develop a registry for MCP servers that collects reviews and feedback from agents | Mentioned By: DorianD\nType: Feature | Description: Create a whitelabel version of auto.fun at registry.fun for MCP server operators | Mentioned By: DorianD\nType: Feature | Description: Implement a voting system for AI judges in Clank Tank that includes token holders | Mentioned By: jin\nType: Documentation | Description: Rewrite the Eliza Diary Network concept to better serve as a forum for agents | Mentioned By: DorianD\nType: Technical | Description: Reduce Clank Tank episode length to 6-7 minutes maximum | Mentioned By: jin\nType: Documentation | Description: Develop community and governance protocol for fair access to announcement channels | Mentioned By: vincentpaul", "messageCount": 101, "userCount": 21 }, { "channelId": "1300756641406521416", "channelName": "ideas-feedback-rants", "summary": "The chat segment is extremely brief, containing only a single message from user \"Mavi | Ω\" offering help. There is no technical discussion, problem-solving, or implementation details present in this limited exchange. Without additional context about what help is being offered or what problem is being addressed, no meaningful technical analysis can be provided.", "messageCount": 1, "userCount": 1 } ] } }, "ai_news_elizaos_daily_discord_md_2025-04-10": { "filename": "2025-04-10.md", "content": "# elizaOS Discord - 2025-04-10\n\n## Overall Discussion Highlights\n\n### ElizaOS Development & Technical Issues\n- Users are experiencing various installation and dependency issues with ElizaOS, particularly when building different versions\n- Version 0.25.9 appears to be the most stable according to some users, though plugin compatibility varies across versions\n- The \"hapi__shot\" error is commonly reported when building different versions\n- Users are trying different package managers (npm, pnpm, bun) to resolve dependency issues\n- A common fix for the \"Dynamic require of 'child_process'\" error is adding `\"types\": [\"node\"]` to tsconfig.json\n- Twitter plugin functionality is a common pain point, with users trying to get autonomous posting working\n\n### ElizaDAO Organization\n- The community is establishing ElizaDAO alongside existing entities ElizaLabs and ElizaStudios\n- Five working groups have been formed: Community/Governance/Events, Dev/Knowledge, Comms/Social, Partnerships/Outreach, and Tokens/Funding\n- Consensus that a separate DAO treasury is essential for true decentralized governance\n- Discussion about balancing autonomous action with coordination with ElizaLabs to avoid duplication of efforts\n- Plans to create a DAO charter with clear values and establish alignment with ElizaLabs' roadmap while maintaining independence\n\n### Agent Development\n- SpartanV2 is being developed as a flagship agent for V2, while V1 is currently running\n- Discussion about optimal posting frequency for social media agents (currently twice per hour for Spartan)\n- The team is exploring ways to recover 25,000 followers that were previously lost\n- Contract address has been added to the Spartan account profile\n\n### MCP (Model Context Protocol) Ecosystem\n- Gap identified in the MCP server ecosystem: lack of efficient discovery and evaluation mechanisms for AI agents\n- Multiple registry solutions emerging (smithery.ai, mcp.so, mcpmarket.com) but they lack agent-centric feedback\n- Proposal for registry.fun as a whitelabel version of auto.fun for MCP server operators\n- Concept of an \"Eliza Diary Network\" mentioned as a forum for AI agents\n\n### Product Launches\n- Auto.fun launch initially delayed to April 14th, now coming \"very very soon\" without a specific date\n- Clank Tank Episode 3 released, with discussions about improvements including Tally integrations and Discord webhooks\n- Virtual token reportedly got listed\n\n## Key Questions & Answers\n\n### Technical Implementation\n- **Q**: How can I fix the \"Dynamic require of 'child_process' is not supported\" error? \n **A**: Add `\"types\": [\"node\"]` to tsconfig.json\n\n- **Q**: How can I call plugin to the agent? \n **A**: Yes, it's possible (though the answer lacks details)\n\n- **Q**: Can I change the language of Eliza? \n **A**: Yes, if you define your character in Chinese, LLM should respond that way\n\n- **Q**: Is the task functionality working? \n **A**: It's only on v2 and not tested too much yet\n\n### ElizaDAO Structure\n- **Q**: Do we need a separate treasury for the DAO? \n **A**: Yes, without a treasury and collective decision-making, it's not truly a DAO\n\n- **Q**: How should we manage DAO spending? \n **A**: Set a budget for each group with 1-2 members as \"CFO\" to approve spending\n\n- **Q**: How do we balance autonomy with alignment with Labs/Studios? \n **A**: Codify values in the DAO charter that balance \"you can just do things\" with coordination principles\n\n- **Q**: What should be the name of the DAO? \n **A**: ElizaDAO, to go with ElizaLabs and ElizaStudios\n\n### Agent Development\n- **Q**: Not on v2 now? \n **A**: No, still working on v2, we'll upgrade when it's ready\n\n- **Q**: Thoughts on if he's posting too often? Twice an hour seems on the high side \n **A**: Yes, planning to slow it down after improving post quality\n\n- **Q**: Did degenspartanai move to another handle or is the project stopped? \n **A**: Twitter account was suspended. It's being re-built as a flagship agent for V2\n\n## Community Help & Collaboration\n\n### Technical Support\n- **notorious_d_e_v** helped **hotcode101** with debugging by suggesting setting `DEFAULT_LOG_LEVEL=\"debug\"` in .env file and checking Twitter settings in .env.example\n- **wookosh** helped **apoorva99** fix an error with MongoDB adapter by suggesting adding `\"types\": [\"node\"]` to tsconfig.json\n- **notorious_d_e_v** advised **0xLabsTheCoder** to use `pnpm` instead of other package managers for build issues\n- **Kimani** helped multiple users with v1 setup issues by suggesting navigating to node_modules\\better-sqlite3 directory and running pnpm run build\n- **CSC35** advised **0xLabsTheCoder** on Twitter posting issues by setting `TWITTER_ENABLE_POST_GENERATION=true` in the .env for v2\n\n### Governance & Organization\n- **Patt** helped **vincentpaul** locate an introduction message from a user\n- **accelxr** corrected **HoneyBadger's** misidentification of a wallet thought to belong to Labs\n- **vincentpaul** organized the DAO structure by creating and updating a list of 5 working groups with assigned leaders\n- **yikesawjeez** offered to connect the group with governance experts from rndao and Hats protocol\n\n### Product Development\n- **hubert** confirmed to **DorianD** they were spinning up \"the\" registry for MCPs with better voting mechanisms\n- **Odilitime** clarified for **찌 G 跻 じ PrudentSpartan** about the auto.fun release timeline\n- **jin** acknowledged **Toni's** feedback about Clank Tank episode length and committed to shorter episodes\n\n## Action Items\n\n### Technical\n- Fix the hapi__shot error that occurs in newer versions (Mentioned by CSC35, 0xLabsTheCoder)\n- Fix compatibility issues between different package managers (Mentioned by 0xChainBrain)\n- Resolve the \"Dynamic require of 'child_process'\" error on WSL2 (Mentioned by Bundinho)\n- Fix Twitter plugin autonomous posting functionality (Mentioned by hotcode101, 0xLabsTheCoder)\n- Fix Discord plugin compatibility with version 0.25.9 (Mentioned by wookosh)\n- Establish a separate treasury for ElizaDAO (Mentioned by HoneyBadger, yikesawjeez)\n- Create a budget allocation system for each working group (Mentioned by HoneyBadger)\n- Develop token engineering for DAO governance (Mentioned by yikesawjeez)\n- Align DAO roadmap with ElizaLabs' plans for Q3-Q4 (Mentioned by HoneyBadger)\n- Schedule coordination call with ElizaLabs to establish initial steps (Mentioned by HoneyBadger)\n- Slow down posting frequency of SpartanV1 from twice per hour (Mentioned by Odilitime)\n- Continue development of SpartanV2 (Mentioned by Odilitime)\n- Explore path to recover 25,000 lost followers (Mentioned by Odilitime)\n- Implement Tally integrations and Discord webhooks for Clank Tank submissions (Mentioned by jin)\n- Reduce Clank Tank episode length to 6-7 minutes maximum (Mentioned by jin)\n\n### Documentation\n- Create clear deployment guides for VPS and cloud services (Mentioned by stanleymarch)\n- Improve plugin development and testing documentation for v2 (Mentioned by Tobiloba)\n- Update task functionality documentation (Mentioned by hotcode101)\n- Create troubleshooting guide for common errors (Mentioned by 0xChainBrain)\n- Draft a DAO charter with clear values balancing autonomy and coordination (Mentioned by vincentpaul)\n- Create a sign-up process for core contributors with proper verification (Mentioned by HoneyBadger)\n- Define coordination protocols between ElizaDAO and ElizaLabs/Studios (Mentioned by accelxr)\n- Rewrite the Eliza Diary Network concept to better serve as a forum for agents (Mentioned by DorianD)\n- Develop community and governance protocol for fair access to announcement channels (Mentioned by vincentpaul)\n\n### Feature\n- Add support for scheduled actions in v1 (Mentioned by martincontact101)\n- Implement incentive mechanisms for sustainable contributor participation (Mentioned by vincentpaul, Zolo)\n- Develop builder support program within the DAO structure (Mentioned by Kenk)\n- Add contract address to account profile (Mentioned by Zolo)\n- Create an MCP Server Agent that handles customer service, promotion, and registry registration (Mentioned by DorianD)\n- Develop a registry for MCP servers that collects reviews and feedback from agents (Mentioned by DorianD)\n- Create a whitelabel version of auto.fun at registry.fun for MCP server operators (Mentioned by DorianD)\n- Implement a voting system for AI judges in Clank Tank that includes token holders (Mentioned by jin)" }, "ai_news_elizaos_daily_dev_json_2025-04-10": { "filename": "2025-04-10.json", "content": { "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-04-10", "date": 1744243200, "stats": { "totalMessages": 41, "totalUsers": 14 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS v2 migration and implementation issues. Users are discussing how to migrate plugins from v1 to v2, with community members providing guidance on using the monorepo setup command and referencing available resources. There appears to be an ongoing rollout of v2, with some users experiencing package management errors when installing plugins. A critical bug in v1 is mentioned, related to a dependency update that's causing problems for users. The `createTask` function in the AgentRuntime class is noted as missing or not working properly. Community members are actively helping each other with setup and migration issues, sharing resources like GitHub PRs and documentation links.\n\n## 2. FAQ\nQ: How do I migrate a plugin to be used in v2? (asked by LemonS) A: Use `npx @elizaos/cli@beta setup-monorepo`, check package/plugin-starter/index.ts for structure, or look at other plugins like openai and twitter (answered by sayonara)\nQ: Is v2 fully out and stable, or is the rollout still happening? (asked by Matthew Liu) A: Roll out is still happening (answered by Odilitime)\nQ: Is task working in ElizaOS? AgentRuntime class does not have `createTask` function (asked by Martin Rivera) A: Unanswered\n\n## 3. Help Interactions\nHelper: sayonara | Helpee: LemonS | Context: Migrating a plugin to v2 | Resolution: Provided CLI command for monorepo setup and suggested checking plugin-starter structure\nHelper: Nisita | Helpee: LemonS | Context: Plugin migration to v2 | Resolution: Reinforced sayonara's advice and shared a video resource with disclaimer about possible changes\nHelper: Ξ2T | Helpee: Unspecified | Context: Getting v2 set up early morning | Resolution: Acknowledged successful help from user 573475033515819009\n\n## 4. Action Items\nType: Technical | Description: Fix v1 bug related to dependency update in PR #4232 | Mentioned By: shaw\nType: Documentation | Description: Update documentation for tasks in ElizaOS v2 as the AgentRuntime class doesn't have createTask function | Mentioned By: Martin Rivera\nType: Technical | Description: Complete the v2 rollout to address package management errors when installing plugins | Mentioned By: Matthew Liu", "messageCount": 25, "userCount": 12 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat segment discusses implementing recurring tasks in ElizaOS. Martin Rivera inquired about using the `createTask` function from the AgentRuntime class to run an action hourly for posting messages to a Discord channel. Shaw clarified that this functionality is part of v2 (available in the `v2-develop` branch) and not in v1. For v1, Shaw suggested creating a service that uses the runtime Discord client (`runtime.getClient`) with a timer loop as an alternative approach. When Martin noted that Service is also a v2 feature, Shaw clarified that services should exist in v1 as well, mentioning that he had consolidated services and clients, and referenced PDF service as an example.\n\n## 2. FAQ\nQ: Is task working in ElizaOS? (asked by Martin Rivera) A: It's a v2 feature, you need to use `git checkout origin/v2-develop` (answered by shaw)\nQ: Is there alternative in V1? I want to run action every hour. This action posts message in Discord Channel (asked by Martin Rivera) A: You can make a service that gets the runtime discord client (runtime.getClient) and calls post on a loop. Look at other Service type classes, you just need one that starts a timer in constructor (answered by shaw)\nQ: Service is also `v2` feature. (asked by Martin Rivera) A: Should be in v1 as well, I consolidated services and clients, but for example, a pdf service, but its just some class on runtime that can call other stuff (answered by shaw)\n\n## 3. Help Interactions\nHelper: shaw | Helpee: Martin Rivera | Context: Martin needed to implement recurring tasks in ElizaOS v1 to post Discord messages hourly | Resolution: Shaw suggested creating a service with a timer that uses runtime.getClient to post messages in a loop\n\n## 4. Action Items\nTechnical: Implement a custom service class with timer functionality for recurring Discord messages in ElizaOS v1 | Description: Create a class that uses runtime.getClient with a loop timer to post hourly messages | Mentioned By: shaw\nDocumentation: Document differences between v1 and v2 features in ElizaOS | Description: Clarify which features like tasks and services are available in which versions | Mentioned By: shaw", "messageCount": 12, "userCount": 3 }, { "channelId": "1327493511406293016", "channelName": "🎤｜plug-your-projects", "summary": "The chat segment is extremely brief, consisting of only a single message from user \"shaw\" stating \"this is cool\" without any specific technical context. There are no technical discussions, decisions, problem-solving, solutions, or implementations present in this limited exchange.", "messageCount": 1, "userCount": 1 }, { "channelId": "1324098367416172665", "channelName": "📮｜feedback", "summary": "The chat segment is very brief, containing only three messages between two users discussing issues with Twitter integration. User rchak007 reports that while the system is tweeting, it's not connecting to their Character despite using the free version. They express frustration about being stuck and waiting for Dev school guidance. Several hours later, Pr⭕f. J mentions attempting to reconnect as their dashboard indicates lack of Twitter access despite having correct API credentials. rchak007 later asks if Pr⭕f. J is using \"version 2,\" presumably referring to Twitter API versions.", "messageCount": 3, "userCount": 2 } ] } }, "ai_news_elizaos_daily_dev_md_2025-04-10": { "filename": "2025-04-10.md", "content": "# elizaOS Development Discord - 2025-04-10\n\n## Overall Discussion Highlights\n\n### ElizaOS v2 Migration and Implementation\n- The community is actively working on migrating plugins from v1 to v2\n- V2 rollout is still in progress, not yet fully stable\n- Users are utilizing the monorepo setup command (`npx @elizaos/cli@beta setup-monorepo`) for migration\n- Some users are experiencing package management errors when installing plugins in v2\n- A critical bug in v1 related to a dependency update is causing problems\n\n### Recurring Tasks Implementation\n- Discussion about implementing recurring tasks for posting messages to Discord channels\n- Clarification that the `createTask` function is a v2 feature (available in `v2-develop` branch)\n- Alternative approaches for v1 users were suggested, involving custom service classes with timer functionality\n\n### Twitter Integration Issues\n- Users reported problems with Twitter integration not connecting to their Characters\n- Discussion about Twitter API access and credentials not being recognized by the dashboard\n\n## Key Questions & Answers\n\n**Q: How do I migrate a plugin to be used in v2?** (asked by LemonS) \n**A:** Use `npx @elizaos/cli@beta setup-monorepo`, check package/plugin-starter/index.ts for structure, or look at other plugins like openai and twitter (answered by sayonara)\n\n**Q: Is v2 fully out and stable, or is the rollout still happening?** (asked by Matthew Liu) \n**A:** Roll out is still happening (answered by Odilitime)\n\n**Q: Is task working in ElizaOS? AgentRuntime class does not have `createTask` function** (asked by Martin Rivera) \n**A:** It's a v2 feature, you need to use `git checkout origin/v2-develop` (answered by shaw)\n\n**Q: Is there alternative in V1? I want to run action every hour to post messages in Discord Channel** (asked by Martin Rivera) \n**A:** You can make a service that gets the runtime discord client (runtime.getClient) and calls post on a loop. Look at other Service type classes, you just need one that starts a timer in constructor (answered by shaw)\n\n**Q: Service is also `v2` feature.** (asked by Martin Rivera) \n**A:** Should be in v1 as well, I consolidated services and clients, but for example, a pdf service, but its just some class on runtime that can call other stuff (answered by shaw)\n\n## Community Help & Collaboration\n\n### Plugin Migration Assistance\n- **sayonara** helped **LemonS** with migrating a plugin to v2 by providing CLI command for monorepo setup and suggesting checking plugin-starter structure\n- **Nisita** reinforced sayonara's advice and shared a video resource with disclaimer about possible changes\n- **Ξ2T** acknowledged successful help from another user with getting v2 set up\n\n### Recurring Tasks Implementation\n- **shaw** guided **Martin Rivera** through implementing recurring tasks in ElizaOS v1, suggesting a custom service with timer functionality as an alternative to the v2 `createTask` function\n\n## Action Items\n\n### Technical\n- Fix v1 bug related to dependency update in PR #4232 (mentioned by shaw)\n- Complete the v2 rollout to address package management errors when installing plugins (mentioned by Matthew Liu)\n- Implement a custom service class with timer functionality for recurring Discord messages in ElizaOS v1 (mentioned by shaw)\n\n### Documentation\n- Update documentation for tasks in ElizaOS v2 as the AgentRuntime class doesn't have createTask function (mentioned by Martin Rivera)\n- Document differences between v1 and v2 features in ElizaOS to clarify which features like tasks and services are available in which versions (mentioned by shaw)" }, "ai_news_hyperfy_daily_json_2025-04-10": { "filename": "2025-04-10.json", "content": { "type": "dailySummary", "title": "Daily Report - 2025-04-10", "categories": [ { "title": "Hyperfy Development Updates: App Features, Physics, and V2 Enhancements", "content": [ { "text": "Recent discussions in the Hyperfy community have centered around technical improvements in app development, physics integration, and the transition from Hyperfy V1 to V2. Developers are actively enhancing user interaction, UI/UX, and multimedia capabilities within 3D/VR environments.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412", "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "In app development, contributors like gertjanakerboom and voxvienne focused on improving object manipulation and user interface. Enhancements include a toggleable crosshair mesh for easier app grabbing, fading ring effects using scrolling textures, and plans to support elevated object collision. Suggestions were made to reintroduce editable bounding boxes and loc/rot input fields for better positioning, and pinning was confirmed as a method to lock apps in place.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412" ], "images": [], "videos": [] }, { "text": "Physics and raycasting were key topics, with bear7483 troubleshooting rigidbody and collider setups. Community members clarified that dynamic rigidbodies must be convex and that collider.radius should be used for spheres. A critical fix involved using world.attach(body) to enable proper physics and raycasting behavior. The importance of minimal reproducible examples for debugging was emphasized.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412" ], "images": [], "videos": [] }, { "text": "Texture scrolling issues were addressed with help from crufro, who provided a reference project using a grid-based seamless texture. This helped resolve UV cropping problems in animated textures. Additionally, discussions around Android-specific audio behavior and environment variable access highlighted the need for better documentation and platform-specific support.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412" ], "images": [], "videos": [] }, { "text": "Hyperfy V2 development introduced major features like geometry-based video projection, enabling immersive environments such as 360° video spheres and curved screens. This supports advanced use cases like VRChat streaming and animated skyboxes. Ashxn.eth confirmed that screen sharing is now possible, completing the video projection pipeline.", "sources": [ "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "The Hyperfy Blender add-on was highlighted as a key tool for V2, simplifying collision setup and asset integration. Cluny_the_scourge is contributing modular sci-fi assets with snap points and matching VRM avatars to the public library. These assets are designed for V2 and will enhance world-building capabilities.", "sources": [ "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "Community members discussed the pros and cons of V1 vs V2. While V1 is easier to use, it lacks performance and future support. V2 offers better mobile compatibility and scalability but requires more technical setup. Hosting options include self-hosting or using services like hyperworld.host. VR support is still under development.", "sources": [ "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "Feature requests and action items include improving Android audio routing, adding app/model locking, expanding texture scrolling support, enabling Twitch integration, and supporting anonymous access for events. Documentation updates are also needed to clarify physics setup, tag behavior, and V1 vs V2 differences.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412", "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] } ], "topic": "blender" }, { "title": "Hyperfy Development Updates and Community Discussions", "content": [ { "text": "The Hyperfy community has been actively discussing technical improvements and feature development across both V1 and V2 platforms. Key topics include app development in 3D/VR environments, video projection capabilities, and asset integration using Blender.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412", "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "In app development, users explored scripting and Blender workflows for object manipulation, physics, and UI enhancements. Notable improvements include the addition of a toggleable crosshair mesh, fading ring effects, and better app grabbing mechanics. Physics integration was clarified, with emphasis on using convex dynamic rigidbodies and the world.attach(body) method for enabling raycasting.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412" ], "images": [], "videos": [] }, { "text": "UI/UX suggestions included reintroducing editable bounding boxes and loc/rot input fields for precise app positioning. App locking to prevent accidental movement was confirmed to be available via pinning in newer builds. Texture scrolling issues were addressed with help from community members, highlighting the importance of correct UV mapping.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412" ], "images": [], "videos": [] }, { "text": "Hyperfy V2 introduced geometry-based video projection, allowing video textures on curved or paneled GLB meshes. This enables immersive environments such as 360° video spheres and animated skyboxes. Screen sharing and VRChat streaming into Hyperfy were also discussed as emerging use cases.", "sources": [ "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "The Hyperfy Blender add-on was highlighted as a key tool for V2, simplifying collision setup and asset integration. Community members are contributing modular sci-fi assets and VRM avatars to the public library, with features like snap points and collision pre-configured.", "sources": [ "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "V1 remains easier to build on but lacks performance and future support. V2 offers better performance and mobile compatibility but requires more technical setup, including self-hosting or third-party services like hyperworld.host. VR support is still under development.", "sources": [ "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "Community feature requests include Twitch integration, anonymous event access, avatar customization stands, and support for large-scale events through horizontal scaling. Documentation updates and clearer guidance on physics, raycasting, and asset setup were also identified as priorities.", "sources": [ "https://discord.com/channels/958209073277456457/994775534733115412", "https://discord.com/channels/958209073277456457/958209074045026327" ], "images": [], "videos": [] }, { "text": "A lighter moment in the community included a humorous remark by voxvienne calling the FBX format 'boomerformat', suggesting it's outdated compared to modern 3D asset workflows. No technical discussion followed.", "sources": [ "https://discord.com/channels/958209073277456457/1031058655581323324" ], "images": [], "videos": [] }, { "text": "As of the latest update, the price of SOL (Solana) is $119.05.", "sources": [], "images": [], "videos": [] } ], "topic": "Misceleanous" } ], "date": 1744243200 } }, "ai_news_hyperfy_daily_md_2025-04-10": { "filename": "2025-04-10.md", "content": "# Hyperfy Development Report – April 10, 2025\n\n## 1. App Development and UI/UX Enhancements\n\n### Object Manipulation and Interface Improvements\n- Toggleable crosshair mesh for improved app grabbing\n- Fading ring effects using scrolling textures\n- Editable bounding boxes and loc/rot input fields suggested for precise positioning\n- App pinning confirmed to lock objects in place\n\n### Texture and Audio Fixes\n- UV cropping issues resolved using grid-based seamless textures\n- Android-specific audio behavior discussed; need for better platform documentation\n\n## 2. Physics and Raycasting\n\n### Key Fixes and Best Practices\n- Dynamic rigidbodies must be convex\n- Use `collider.radius` for spheres\n- `world.attach(body)` required for proper physics and raycasting\n- Emphasis on minimal reproducible examples for debugging\n\n## 3. Hyperfy V2 Enhancements\n\n### Geometry-Based Video Projection\n- Supports 360° video spheres, curved screens, and animated skyboxes\n- Enables VRChat streaming and screen sharing\n\n### Blender Add-on and Asset Integration\n- Simplifies collision setup and asset import for V2\n- Modular sci-fi assets with snap points and VRM avatars added to public library\n\n### Platform Comparison: V1 vs V2\n- V1: Easier to use, but lacks performance and future support\n- V2: Better performance and mobile compatibility, but requires technical setup\n - Hosting options: self-hosting or services like hyperworld.host\n - VR support still in development\n\n## 4. Community Feature Requests and Action Items\n\n### Requested Features\n- Android audio routing improvements\n- App/model locking\n- Expanded texture scrolling support\n- Twitch integration\n- Anonymous access for events\n- Avatar customization stands\n- Horizontal scaling for large events\n\n### Documentation Needs\n- Clarify physics setup and tag behavior\n- Explain differences between V1 and V2\n- Improve guidance on raycasting and asset setup\n\n## 5. Community Highlights\n\n- Voxvienne humorously referred to FBX as \"boomerformat\"\n- SOL (Solana) price update: $119.05\n\n## Sources\n- Hyperfy Discord: [App Dev](https://discord.com/channels/958209073277456457/994775534733115412), [General](https://discord.com/channels/958209073277456457/958209074045026327), [Humor](https://discord.com/channels/958209073277456457/1031058655581323324)" }, "github_summaries_daily_2025-04-11": { "filename": "2025-04-11.md", "content": "# ElizaOS Daily Update (Apr 11, 2025)\n\n## OVERVIEW \nToday, significant progress was made in enhancing the ElizaOS framework, particularly in the Discord plugin functionality and JSON serialization. Key features were added, including a missing bootstrap plugin, while several bugs were addressed to improve overall stability. The team also initiated a new issue related to deployment challenges on Google Cloud Run.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Feature Enhancements\n- Added a missing bootstrap plugin to the list ([#4267](https://github.com/elizaos/eliza/pull/4267)).\n- Replaced text input with a dropdown for voice model selection, improving user interface and experience ([#4262](https://github.com/elizaos/eliza/pull/4262)).\n\n### Bug Fixes\n- Implemented a `safeReplacer` function to handle circular references in JSON serialization, resolving a cyclic error ([#4266](https://github.com/elizaos/eliza/pull/4266)).\n- Fixed issues related to Discord voice join/leave actions ([#4265](https://github.com/elizaos/eliza/pull/4265)).\n- Made small fixes to Discord actions to enhance functionality ([#4264](https://github.com/elizaos/eliza/pull/4264)).\n- Removed dead code around plugin installation to streamline the codebase ([#4263](https://github.com/elizaos/eliza/pull/4263)).\n\n## CLOSED ISSUES\n\n### Discord Client Issues\n- Resolved an issue where the Discord client was not loading on `pnpm start`, despite correct settings in `character.json` ([#4258](https://github.com/elizaos/eliza/issues/4258)).\n- Fixed the registration issue for the anthropic plugin concerning TEXT_EMBEDDING, ensuring proper model registration ([#4251](https://github.com/elizaos/eliza/issues/4251)).\n\n## NEW ISSUES\n\n### Deployment Challenges\n- A new issue was reported regarding the Discord bot not replying when deployed with Docker on Google Cloud Run, despite being active and receiving messages ([#4269](https://github.com/elizaos/eliza/issues/4269))." }, "github_summaries_week_latest_2025-05-18.md": { "filename": "2025-05-18.md", "content": "# ElizaOS Weekly Update (May 18 - 24, 2025)\n\n## OVERVIEW\nThis week saw significant expansion of ElizaOS's API capabilities with new endpoints for worlds, rooms, and agent messaging. The team enhanced plugin infrastructure with registry integration and timeout handling, while fixing critical UI responsiveness issues. Major progress was made on the Polygon plugin, bringing blockchain functionality to the framework. Test reliability was improved across CLI commands and integration tests.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### API Expansion and World Management\n- Added new API endpoints for creating and managing worlds and rooms ([#4667](https://github.com/elizaos/eliza/pull/4667), [#4647](https://github.com/elizaos/eliza/pull/4647))\n- Enhanced message API with world selection capabilities, allowing messages to be associated with specific worlds ([#4637](https://github.com/elizaos/eliza/pull/4637))\n- Improved agent creation API to return agent ID in the initial response, eliminating the need for subsequent calls ([#4634](https://github.com/elizaos/eliza/pull/4634))\n\n### Plugin Infrastructure Improvements\n- Implemented registry integration for plugins with 30-second timeout protection ([#4641](https://github.com/elizaos/eliza/pull/4641), [#4678](https://github.com/elizaos/eliza/pull/4678))\n- Added channel ID filtering capability to Discord plugin ([#4665](https://github.com/elizaos/eliza/pull/4665))\n- Removed global environment variable support in favor of local environment management ([#4666](https://github.com/elizaos/eliza/pull/4666))\n- Integrated Sentry logging for core logger errors ([#4650](https://github.com/elizaos/eliza/pull/4650))\n\n### Blockchain Integration Progress\n- Made significant progress on Polygon plugin implementation, including core EVM RPC wrappers and basic read operations ([#4575](https://github.com/elizaos/eliza/pull/4575))\n- Added Polygon Gas Oracle integration for transaction fee estimation ([#4574](https://github.com/elizaos/eliza/pull/4574))\n- Started work on Jupiter Swap plugin for cryptocurrency trading functionality ([#4593](https://github.com/elizaos/eliza/pull/4593))\n\n### Bug Fixes and Test Improvements\n- Fixed UI responsiveness issue with agent start button not updating status in real-time ([#4642](https://github.com/elizaos/eliza/pull/4642))\n- Resolved issues with dynamic providers in reply actions ([#4651](https://github.com/elizaos/eliza/pull/4651), [#4670](https://github.com/elizaos/eliza/pull/4670))\n- Improved test reliability by fixing flakiness in bats tests and addressing integration test failures ([#4663](https://github.com/elizaos/eliza/pull/4663), [#4654](https://github.com/elizaos/eliza/pull/4654))\n\n## CLOSED ISSUES\n\n### Documentation and Community Improvements\n- Updated community section documentation with improved navigation flowcharts for both technical and non-technical users ([#4260](https://github.com/elizaos/eliza/issues/4260))\n- Enhanced project documentation with updated blog posts and comprehensive partner documentation ([#4586](https://github.com/elizaos/eliza/pull/4586))\n- Implemented automatic documentation deployment workflow for changes to the docs folder ([#4640](https://github.com/elizaos/eliza/pull/4640), [#4631](https://github.com/elizaos/eliza/pull/4631))\n\n### Technical Debt and Architecture Improvements\n- Addressed platform interface needs in core package for ElizaOS v2 ([#3491](https://github.com/elizaos/eliza/issues/3491))\n- Resolved agent hanging issues after core initialization with specific configurations ([#4486](https://github.com/elizaos/eliza/issues/4486))\n- Improved dependency management with request to publish to npm for better version compatibility ([#4562](https://github.com/elizaos/eliza/issues/4562))\n\n## NEW ISSUES\n\nNo new issues were reported during this period. The team focused on addressing existing issues and implementing planned features." }, "github_summaries_month_latest_2025-05-01.md": { "filename": "2025-05-01.md", "content": "# ElizaOS Monthly Update (May 2025)\n\n## OVERVIEW\nMay was a transformative month for ElizaOS with significant enhancements to the framework's core architecture and plugin ecosystem. The team focused on improving CLI functionality, refining agent interactions, and streamlining the plugin management system. Major strides were made in database operations, authentication mechanisms, and documentation, while several plugins were moved to standalone repositories to support the new plugin sharing system between v0.x and v1.x.\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### CLI Enhancements and Command Refinements\n- Improved CLI commands with better documentation and consistent behavior across platforms ([#4646](https://github.com/elizaos/eliza/pull/4646), [#4583](https://github.com/elizaos/eliza/pull/4583))\n- Consolidated update commands for better user experience ([#4592](https://github.com/elizaos/eliza/pull/4592), [#4591](https://github.com/elizaos/eliza/pull/4591))\n- Enhanced environment variable management with better system information display ([#4610](https://github.com/elizaos/eliza/pull/4610), [#4445](https://github.com/elizaos/eliza/pull/4445))\n- Improved dev command with better character file handling ([#4618](https://github.com/elizaos/eliza/pull/4618))\n\n### Plugin System Restructuring\n- Prepared v0.x for sharing plugins with v1.x ([#4384](https://github.com/elizaos/eliza/pull/4384))\n- Added support for third-party plugin installation directly from GitHub URLs ([#4568](https://github.com/elizaos/eliza/pull/4568), [#4577](https://github.com/elizaos/eliza/pull/4577))\n- Implemented plugin specification submodule for better standardization ([#4553](https://github.com/elizaos/eliza/pull/4553))\n- Moved several plugins out of the monorepo to standalone repositories ([#4669](https://github.com/elizaos/eliza/pull/4669), [#4511](https://github.com/elizaos/eliza/pull/4511))\n\n### Database and Storage Improvements\n- Enhanced PGLite database management with per-project directories ([#4423](https://github.com/elizaos/eliza/pull/4423), [#4497](https://github.com/elizaos/eliza/pull/4497))\n- Added comprehensive integration tests for database operations ([#4518](https://github.com/elizaos/eliza/pull/4518))\n- Fixed foreign key constraint violations when deleting agents ([#4510](https://github.com/elizaos/eliza/pull/4510))\n- Improved semantic text splitting for better RAG knowledge retrieval ([#4235](https://github.com/elizaos/eliza/pull/4235))\n\n### Authentication and API Enhancements\n- Added authentication middleware and API key dialog for unauthorized access ([#4420](https://github.com/elizaos/eliza/pull/4420))\n- Created new API endpoints for rooms and worlds management ([#4647](https://github.com/elizaos/eliza/pull/4647), [#4667](https://github.com/elizaos/eliza/pull/4667))\n- Optimized agent loading for improved performance with multiple agents ([#4519](https://github.com/elizaos/eliza/pull/4519))\n- Added world selection capability in message API ([#4637](https://github.com/elizaos/eliza/pull/4637))\n\n### Model and Provider Improvements\n- Extended OpenAI plugin to support custom embedding endpoints ([#4421](https://github.com/elizaos/eliza/pull/4421))\n- Added model usage events tracking for embeddings and image descriptions ([#4438](https://github.com/elizaos/eliza/pull/4438))\n- Optimized reply functionality to use small models for faster responses ([#4416](https://github.com/elizaos/eliza/pull/4416))\n- Refactored model handling in AgentRuntime to support provider and priority ([#4507](https://github.com/elizaos/eliza/pull/4507))\n\n### Social Media Integration\n- Implemented Twitter timeline functionality ([#4429](https://github.com/elizaos/eliza/pull/4429))\n- Added comprehensive tutorial for Twitter AI agent setup ([#4425](https://github.com/elizaos/eliza/pull/4425))\n- Fixed issues with Twitter post templates ([#4595](https://github.com/elizaos/eliza/pull/4595))\n- Enhanced Discord plugin with channel ID filtering ([#4665](https://github.com/elizaos/eliza/pull/4665))\n\n### Error Handling and Logging\n- Integrated Sentry logging for core logger errors ([#4650](https://github.com/elizaos/eliza/pull/4650))\n- Fixed JSON parsing issues with nested objects ([#4198](https://github.com/elizaos/eliza/pull/4198))\n- Improved error handling in message processing ([#4508](https://github.com/elizaos/eliza/pull/4508))\n- Enhanced logging with time tracking in tests ([#4621](https://github.com/elizaos/eliza/pull/4621))\n\n### Documentation and Code Quality\n- Added comprehensive docstrings to multiple components ([#4446](https://github.com/elizaos/eliza/pull/4446), [#4469](https://github.com/elizaos/eliza/pull/4469), [#4498](https://github.com/elizaos/eliza/pull/4498))\n- Updated documentation with improved CLI command instructions ([#4448](https://github.com/elizaos/eliza/pull/4448), [#4493](https://github.com/elizaos/eliza/pull/4493))\n- Implemented automated documentation deployment workflow ([#4631](https://github.com/elizaos/eliza/pull/4631))\n- Fixed broken links and improved formatting in documentation ([#4433](https://github.com/elizaos/eliza/pull/4433), [#4597](https://github.com/elizaos/eliza/pull/4597))\n\n## CLOSED ISSUES\n\n### Documentation and Tutorials\n- Fixed broken links and improved tutorial content ([#4260](https://github.com/elizaos/eliza/issues/4260), [#3880](https://github.com/elizaos/eliza/issues/3880))\n- Tested and verified CLI command documentation for accuracy ([#4143](https://github.com/elizaos/eliza/issues/4143))\n- Clarified plugin compatibility with Eliza v2 ([#4164](https://github.com/elizaos/eliza/issues/4164))\n\n### Twitter Integration Issues\n- Resolved media generation and attachment for Twitter posts ([#4241](https://github.com/elizaos/eliza/issues/4241), [#4224](https://github.com/elizaos/eliza/issues/4224))\n- Fixed formatting issues with line breaks in tweets ([#3897](https://github.com/elizaos/eliza/issues/3897))\n- Addressed Twitter space functionality problems ([#4180](https://github.com/elizaos/eliza/issues/4180))\n- Implemented solutions for Twitter interactions and reactions ([#4181](https://github.com/elizaos/eliza/issues/4181))\n\n### Platform Compatibility\n- Resolved Windows build issues ([#4094](https://github.com/elizaos/eliza/issues/4094))\n- Improved remote debugging capabilities for v2 ([#3978](https://github.com/elizaos/eliza/issues/3978))\n- Fixed CLI functionality and error handling ([#4107](https://github.com/elizaos/eliza/issues/4107), [#4159](https://github.com/elizaos/eliza/issues/4159))\n\n### Service Integration\n- Addressed Discord message persistence issues ([#3952](https://github.com/elizaos/eliza/issues/3952))\n- Fixed API key handling for Anthropic integration ([#4049](https" }, "github_extracted_data_monthly_stats_text_2025-04": "{\n \"interval\": {\n \"intervalStart\": \"2025-04-01T00:00:00.000Z\",\n \"intervalEnd\": \"2025-05-01T00:00:00.000Z\",\n \"intervalType\": \"month\"\n },\n \"repository\": \"elizaos/eliza\",\n \"overview\": \"From 2025-04-01 to 2025-05-01, elizaos/eliza had 241 new PRs (199 merged), 45 new issues, and 89 active contributors.\",\n \"topIssues\": [\n {\n \"id\": \"I_kwDOMT5cIs6zmLBG\",\n \"title\": \"the local model on plugin dev not work\",\n \"author\": \"cxp-13\",\n \"number\": 4339,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-23T08:25:43Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 5\n },\n {\n \"id\": \"I_kwDOMT5cIs6xo9Zj\",\n \"title\": \"Provider Data Not Used When Posting to Twitter\",\n \"author\": \"levsagiv\",\n \"number\": 4224,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-08T16:19:29Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs6zjFcA\",\n \"title\": \"Quickstart doc issues\",\n \"author\": \"eduardoPauloPanstein\",\n \"number\": 4336,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-22T23:13:59Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 3\n },\n {\n \"id\": \"I_kwDOMT5cIs6w2eyG\",\n \"title\": \"How to run Eliza CLI?\",\n \"author\": \"LinuxIsCool\",\n \"number\": 4159,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-02T17:20:34Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 2\n },\n {\n \"id\": \"I_kwDOMT5cIs60B0QJ\",\n \"title\": \"Cannot read properties of undefined (reading 'sendStandartTweet')\",\n \"author\": \"srpiroliro\",\n \"number\": 4365,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-25T15:25:56Z\",\n \"closedAt\": null,\n \"state\": \"OPEN\",\n \"commentCount\": 2\n }\n ],\n \"topPRs\": [\n {\n \"id\": \"PR_kwDOMT5cIs6UUVjY\",\n \"title\": \"Scoped knowledgefixes\",\n \"author\": \"lalalune\",\n \"number\": 4391,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-29T10:02:52Z\",\n \"mergedAt\": null,\n \"additions\": 372438,\n \"deletions\": 183811\n },\n {\n \"id\": \"PR_kwDOMT5cIs6Sgk4O\",\n \"title\": \"fix: expose telegram types\",\n \"author\": \"ncale\",\n \"number\": 4286,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-14T15:42:11Z\",\n \"mergedAt\": null,\n \"additions\": 317476,\n \"deletions\": 183752\n },\n {\n \"id\": \"PR_kwDOMT5cIs6RTQuv\",\n \"title\": \"Plugin-Bootstrap Test Suite\",\n \"author\": \"HarshModi2005\",\n \"number\": 4171,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-03T18:26:01Z\",\n \"mergedAt\": null,\n \"additions\": 308954,\n \"deletions\": 183752\n },\n {\n \"id\": \"PR_kwDOMT5cIs6Q-mLn\",\n \"title\": \"fix: browserify-stream import\",\n \"author\": \"wtfsayo\",\n \"number\": 4138,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-01T18:33:13Z\",\n \"mergedAt\": null,\n \"additions\": 297297,\n \"deletions\": 183751\n },\n {\n \"id\": \"PR_kwDOMT5cIs6ShQi0\",\n \"title\": \"Feature/v2/dbml\",\n \"author\": \"jmikedupont2\",\n \"number\": 4288,\n \"repository\": \"elizaos/eliza\",\n \"createdAt\": \"2025-04-14T17:07:26Z\",\n \"mergedAt\": null,\n \"additions\": 296767,\n \"deletions\": 183874\n }\n ],\n \"codeChanges\": {\n \"additions\": 58627,\n \"deletions\": 40923,\n \"files\": 548,\n \"commitCount\": 919\n },\n \"completedItems\": [\n {\n \"title\": \"Clarify Terminology and Required Fields in Agent Settings\",\n \"prNumber\": 4274,\n \"type\": \"other\",\n \"body\": \"\\r\\n# Relates to\\r\\n\\r\\n- https://linear.app/eliza-labs/issue/ELI2-222/uiux-clarify-terminology-and-required-fields-in-agent-settings\\r\\n- https://linear.app/eliza-labs/issue/ELI2-239/bug-uiux-avatar-preview-overlaps-uploadaction-area\\r\\n\\r\\n# Risks\\r\\n\\r\"\n },\n {\n \"title\": \" UI Changes\",\n \"prNumber\": 4273,\n \"type\": \"other\",\n \"body\": \"UI changes for Ticket 220 and 221\"\n },\n {\n \"title\": \"Merge branch\",\n \"prNumber\": 4271,\n \"type\": \"other\",\n \"body\": \"Solving the resolve conflicts\"\n },\n {\n \"title\": \"feat: gui- support for importing JSON to create or update agents\",\n \"prNumber\": 4270,\n \"type\": \"feature\",\n \"body\": \"Allow users to import JSON for agent creation and updates\"\n },\n {\n \"title\": \"Update .env.example to support twitter post generation\",\n \"prNumber\": 4268,\n \"type\": \"other\",\n \"body\": \"add TWITTER_ENABLE_POST_GENERATION environment variable\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n](https://github.com/elizaOS/eliza/issues/4238)\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - This is a simple fix that moves the initialization flag setting after the adapter initialization. The change is minimal and\"\n },\n {\n \"title\": \"chore: improve cli and start code\",\n \"prNumber\": 4250,\n \"type\": \"other\",\n \"body\": \"This PR implements significant code cleanup and improvements across the CLI components of the Eliza project. Key changes include:\\r\\n\\r\\nRefactored the start command with improved plugin loading logic and error handling\\r\\nEnhanced package manage\"\n },\n {\n \"title\": \"chore(cli): use console log for non error cases\",\n \"prNumber\": 4248,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: message api\",\n \"prNumber\": 4247,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"Bug: Remove Duplicate Declaration in api.ts\",\n \"prNumber\": 4246,\n \"type\": \"bugfix\",\n \"body\": \"## Fix duplicate variable declaration in api.ts\\r\\n\\r\\n### Problem\\r\\n\\r\\nThe build was failing with the following error:\\r\\n\\r\\nThis was happening because in the json parsing error handler, the `text` variable was being declared twice:\\r\\n\\r\\n- First at l\"\n },\n {\n \"title\": \"fix knowledge types\",\n \"prNumber\": 4243,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nWhen adding rag knowledge, the editor reports an error\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow – This change only removes a `postscript` entry from the `plugin-bootstrap` package. Since the script it was referring to no longer exists, removing the reference reduces t\"\n },\n {\n \"title\": \"fix: twitter interaction\",\n \"prNumber\": 4192,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/4181\\r\\n\\r\\nThis PR eliminates the duplicate fetchSearchTweets call previously used to retrieve Twitter interactions (likes, retweets, quotes). Instead, it reuses the already-fetched mentionCandi\"\n },\n {\n \"title\": \"chore: use camelCase on plugin export (local-ai)\",\n \"prNumber\": 4186,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: remove import logic from core\",\n \"prNumber\": 4184,\n \"type\": \"other\",\n \"body\": \"1. plugin import logic is already handled in cli's `start` command\\r\\n2. runtime is init again when there are changes to agent\\r\\nso this code is redundant (also it wouldnt be able to add plugins that are not locally available)\"\n },\n {\n \"title\": \"fix: version tag when importing plugins dynamically during runtime\",\n \"prNumber\": 4183,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: space action\",\n \"prNumber\": 4182,\n \"type\": \"bugfix\",\n \"body\": \"This PR gets the Space join action working.\"\n },\n {\n \"title\": \"handle dynamic-runtime import error gentler\",\n \"prNumber\": 4179,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"attempt: module path issues\",\n \"prNumber\": 4178,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"feat: better plugin install management\",\n \"prNumber\": 4177,\n \"type\": \"feature\",\n \"body\": \"# CLI Update Improvements\\r\\n\\r\\nThis PR enhances the ElizaOS CLI update and plugin installation mechanisms with more robust functionality:\\r\\n\\r\\n## What's Changed\\r\\n\\r\\n### Package Management System Improvements\\r\\n- Added a centralized `executeInstal\"\n },\n {\n \"title\": \"feat: Enhance CLI update and plugin installation with package manager…\",\n \"prNumber\": 4176,\n \"type\": \"feature\",\n \"body\": \"# Fix Plugin Loading in Global CLI Installations\\r\\n\\r\\n## Problem\\r\\nWhen the ElizaOS CLI is installed globally, it fails to load required plugins with errors like:\\r\\n```\\r\\nCannot find package '@elizaos/plugin-sql' imported from /usr/local/lib/nod\"\n },\n {\n \"title\": \"fix: knowledge manager scroll issue\",\n \"prNumber\": 4175,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\r\\n\\r\\nKnowledge tab scroll functionality issue\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - Only affects UI rendering of the knowledge tab\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nFixes an issue with the scrolling functionality in the Knowledge tab \"\n },\n {\n \"title\": \"feat: add update-cli command\",\n \"prNumber\": 4170,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: Refactor openai plugin\",\n \"prNumber\": 4169,\n \"type\": \"refactor\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - This is a code refactoring with no functional changes to the OpenAI plugin.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nRefactors the OpenAI plugin code to improve main\"\n },\n {\n \"title\": \"feat: add id to metadata source\",\n \"prNumber\": 4168,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: Failed to create Twitter client\",\n \"prNumber\": 4167,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/4146\\r\\n\\r\\nThe issue occurs because the service starts before the agent is created. I think the service should be started after the runtime is set up.\"\n },\n {\n \"title\": \"fix: tg get world\",\n \"prNumber\": 4166,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: twitter interaction\",\n \"prNumber\": 4165,\n \"type\": \"bugfix\",\n \"body\": \"I don't think we need to call shouldRespond here. bootstrap already handles that for us.\"\n },\n {\n \"title\": \"Filter out ignored Farcaster mentioned\",\n \"prNumber\": 4163,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\nLow. This PR fixes a bug in the Farcaster integration where non-responding decisions weren't being properly recorded.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nFixes a bug in the Farcaster interaction manager where mentions that\"\n },\n {\n \"title\": \"feat: enhance avatar stack\",\n \"prNumber\": 4162,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"add node_modules to .gitignore\",\n \"prNumber\": 4161,\n \"type\": \"feature\",\n \"body\": \"node_modules wasnt in the gitignore in plugin-starter template, resulting in trouble pushing the plugin repo to github. added it so it works well.\"\n },\n {\n \"title\": \"fixed: Pglite Migration issue\",\n \"prNumber\": 4158,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to \\r\\n \\r\\n\\r\\n# Risks \\r\\n**Medium** – Fixing the `pglite` migration issue due to inconsistent usage of `Datadir`. Could impact database migrations if not handled correctly. \\r\\n\\r\\n# Background \\r\\n\\r\\n## W\"\n },\n {\n \"title\": \"Improve Farcaster configuration handling\",\n \"prNumber\": 4156,\n \"type\": \"other\",\n \"body\": \"# Risks\\r\\n\\r\\nLow\\r\\n- Configuration changes could affect Farcaster client initialization\\r\\n- Environment variable fallback might introduce unexpected behavior if both runtime settings and env vars are set\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR \"\n },\n {\n \"title\": \"fix: cache interaction cursor + duplicate memory creation\",\n \"prNumber\": 4155,\n \"type\": \"bugfix\",\n \"body\": \"related: \\r\\nhttps://github.com/elizaOS/eliza/issues/4127\\r\\nhttps://github.com/elizaOS/eliza/issues/4115\\r\\n\\r\\nThis PR caches the cursor of the interaction to avoid repeatedly checking the same interaction or mentioned tweets. \\r\\n\\r\\nThis PR also ad\"\n },\n {\n \"title\": \"chore: update temp. hardcoded v2 registry\",\n \"prNumber\": 4153,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"tests: fixed test file according to the comments in the PR #4130 \",\n \"prNumber\": 4152,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to \\r\\nPR #4130 \\r\\n\\r\\n# Risks \\r\\n**Low** – Minor refactoring to use a constant variable. No functionality change. \\r\\n\\r\\n# Background \\r\\n\\r\\n## What does this PR do? \\r\\nFixes the test file by incorporating the suggested changes from PR \"\n },\n {\n \"title\": \"fix: twitter, double memory creation attempt & server crash\",\n \"prNumber\": 4151,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: project plugin loading first, related to starter project\",\n \"prNumber\": 4150,\n \"type\": \"bugfix\",\n \"body\": \"fixes- (sample) project plugin attaching first; imp for first time DX\"\n },\n {\n \"title\": \"feat: use Evt instead of eventEmitter3\",\n \"prNumber\": 4149,\n \"type\": \"feature\",\n \"body\": \"replaces 'eventEmitter3' with 'evt' (more typesafe, works in more runtimes)\\r\\nhttps://www.evt.land/\"\n },\n {\n \"title\": \"docs: removed an extra `~`\",\n \"prNumber\": 4148,\n \"type\": \"docs\",\n \"body\": \"## What does this PR do?\\r\\n\\r\\nNoticed an unnecessary `~` in the code, which could potentially cause issues.\\r\\nRemoved it to keep things clean.\"\n },\n {\n \"title\": \"feat: clean api\",\n \"prNumber\": 4144,\n \"type\": \"feature\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/4119\\r\\n\\r\\n@wtfsayo Could you take a look and see if there are any other APIs you created that are no longer in use?\"\n },\n {\n \"title\": \"fix: resolve database transaction deadlock\",\n \"prNumber\": 4142,\n \"type\": \"bugfix\",\n \"body\": \"# Database Transaction Deadlock Fix\\r\\n\\r\\n## Issue\\r\\nDatabase connections getting stuck in \\\"idle in transaction\\\" state, causing unresponsiveness.\\r\\n\\r\\n## Root Cause\\r\\nThe `getWorld` method inside `createWorld` wasn't supposed to be merged. This co\"\n },\n {\n \"title\": \"chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates\",\n \"prNumber\": 4141,\n \"type\": \"other\",\n \"body\": \"Bumps the npm_and_yarn group with 2 updates in the / directory: [dompurify](https://github.com/cure53/DOMPurify) and [katex](https://github.com/KaTeX/KaTeX).\\n\\nUpdates `dompurify` from 3.2.3 to 3.2.4\\n
\\nRelease notes\\r\\n\\r\\n# Relates to\\r\\n\\r\\nAdding ability to set the embedding model to the openAI plugin\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow, just adds the ability\"\n },\n {\n \"title\": \"fix: starter project and audio util imports\",\n \"prNumber\": 4139,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"fix: telegram to elizaos data model sync\",\n \"prNumber\": 4137,\n \"type\": \"bugfix\",\n \"body\": \"# Telegram Plugin Service Refactoring\\r\\n\\r\\n## Relates to\\r\\n\\r\\n- Telegram integration stability\\r\\n- Forum topics support / rooms in ElizaOS system\\r\\n\\r\\n## Risks\\r\\n\\r\\n- Medium\\r\\n\\r\\n## Background\\r\\n\\r\\nThe Telegram service implementation requires refactorin\"\n },\n {\n \"title\": \"docs: added raiinmaker to .env.example\",\n \"prNumber\": 4136,\n \"type\": \"docs\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nEnvironment only, adding variables for Raiinmaker plugin\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nplugin-browser Package\\r\\n1. AWS S3 Service Tests (10 tests)\\r\\n* Coverag\"\n },\n {\n \"title\": \"chore: Fix missing comma in section headers list\",\n \"prNumber\": 4038,\n \"type\": \"bugfix\",\n \"body\": \"## What does this PR do?\\r\\n\\r\\nNoticed a missing comma in the `section_headers` list, which caused the last regex pattern to be concatenated incorrectly. This could lead to `New Contributors` headers not being processed as expected. \\r\\n\\r\\nFixed\"\n },\n {\n \"title\": \"chore: removed duplicate JSON import\",\n \"prNumber\": 4030,\n \"type\": \"other\",\n \"body\": \"## What does this PR do?\\r\\n\\r\\nI noticed that the `json` module is imported twice in the code.\\r\\nI removed the second import to clean up the code and improve readability.\"\n },\n {\n \"title\": \"fix: Fix template variable inconsistency in `twitterPostTemplate`\",\n \"prNumber\": 4029,\n \"type\": \"bugfix\",\n \"body\": \"## What does this PR do?\\r\\n\\r\\nI noticed a inconsistency in the `twitterPostTemplate` where `{{agentName}}` was used instead of `{{AGENT_NAME}}`. This caused the `replaceAgentValues` function to miss replacing the placeholder, as it specifical\"\n },\n {\n \"title\": \"feat: Add Kluster AI as model provider\",\n \"prNumber\": 3938,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n# Risks\\r\\nLow\\r\\n\\r\\n# Background\\r\\nKluster AI is a cloud service to host LLMs.\\r\\n\\r\\n## What does this PR do?\\r\\nA\"\n },\n {\n \"title\": \"feat: Add Mem0 as AI SDK Provider\",\n \"prNumber\": 3927,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nN/A\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\nhttps://linear.app/eliza-labs/issue/ELI2-78/implement-world-state-pro\"\n },\n {\n \"title\": \"improve logging for transcription models\",\n \"prNumber\": 4283,\n \"type\": \"other\",\n \"body\": \"\"\n },\n {\n \"title\": \"chore: update docs\",\n \"prNumber\": 4281,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n# Relates to\\r\\nFixes Remote Attestation Action.\\r\\n\\r\\n\\r\\n\\r\\n[ELI2-227 – UI/UX: Implement confirmation modals for destructive actions](https://linear.app/eliza-labs/issue/ELI2-227/uiux-implement-confirmation-modals-for-destructive-actions)\\r\\n\\r\\n\\r\\n# Risk\"\n },\n {\n \"title\": \"deleted duplicate README_NL.md\",\n \"prNumber\": 4321,\n \"type\": \"other\",\n \"body\": \"thanks ! \"\n },\n {\n \"title\": \"feat: Add deleteTweet()\",\n \"prNumber\": 4320,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n- Request to add same changes as in https://github.com/elizaOS/agent-twitter-client from @tcm390 \\r\\n\\r\\n# \"\n },\n {\n \"title\": \"fix: Use utils-based UUID for broader browser support\",\n \"prNumber\": 4318,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/4315\\r\\n\\r\\nFallback to a custom UUID generator for browsers that don't support crypto.randomUUID().\"\n },\n {\n \"title\": \"fix: persistent beacon by handling tour close action\",\n \"prNumber\": 4317,\n \"type\": \"bugfix\",\n \"body\": \"related: https://github.com/elizaOS/eliza/issues/4316\\r\\n\\r\\nMark onboarding as complete when the tour is closed manually to prevent lingering blue beacon.\"\n },\n {\n \"title\": \"Added Default Agents based on the org\",\n \"prNumber\": 4323,\n \"type\": \"other\",\n \"body\": \"# Relates to\\r\\n\\r\\nhttps://linear.app/eliza-labs/issue/ELI2-236/uiux-implement-agent-templates-via-dropdown-in-creation-form\\r\\n\\r\\n# Risks\\r\\nLow. This PR only adds new agent templates based on the existing client documentation. No functional chang\"\n },\n {\n \"title\": \"Fix Typos and Improve Documentation in Changelog\",\n \"prNumber\": 4322,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n**Description:**\\r\\n\\r\\nThis pull request addresses several minor issues in the changelog documentation:\\r\\n\\r\\n- Corrected typos such as \\\"toghether\\\" to \\\"together\\\" and \\\"misstype\\\" to \\\"mistype\\\".\\r\\n- Improved consistency by using strict types to av\"\n },\n {\n \"title\": \"fix: Plugin command normalize across v1 / v2\",\n \"prNumber\": 4327,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"Fix hapi types issue\",\n \"prNumber\": 4333,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n - Removed an unused dependency to streamline the application.\\r\\n \\r\\nI've already merged this recently: https://github.c\"\n },\n {\n \"title\": \"fix: Prevent repetitive agent replies\",\n \"prNumber\": 4331,\n \"type\": \"bugfix\",\n \"body\": \"This PR fix the issue where agents were repeatedly sending the same canned response during ongoing conversations in group chat\\r\\n\"\n },\n {\n \"title\": \"fix: openai stt\",\n \"prNumber\": 4329,\n \"type\": \"bugfix\",\n \"body\": \"This PR aims to fix a transcription issue in plugin-openai. Externalizing node-fetch was causing failures during transcription requests. This update replaces node-fetch with undici for both FormData and the fetch function.\\r\\n\\r\\n@0xbbjoker @od\"\n },\n {\n \"title\": \"fix: gui - sync envs state with updated characterValue props\",\n \"prNumber\": 4328,\n \"type\": \"bugfix\",\n \"body\": \"Previously, envs was initialized only once from characterValue and did not update when characterValue changed. This caused the panel to display stale data unless manually rerendered.\"\n },\n {\n \"title\": \"Feat: enable path params routes for plugins\",\n \"prNumber\": 4335,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\nLow - This change adds functionality for handling route parameters in plugin routes without affecting existing functionality.\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\nAdds support for dynamic route parameters (like `:id`) in pl\"\n },\n {\n \"title\": \"docs: deploy Eliza to TEE with Oasis ROFL app\",\n \"prNumber\": 4334,\n \"type\": \"docs\",\n \"body\": \"# Relates to\\r\\n\\r\\n\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow\\r\\n- Documentation changes only\\r\\n- No code changes\\r\\n- No impact on existing functionality\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\nThis PR updates the documentation \"\n },\n {\n \"title\": \"added bc .gitignore wasnt getting copied from plugin-starter\",\n \"prNumber\": 4345,\n \"type\": \"other\",\n \"body\": \"added this small change because .gitignore wasnt getting copied over on plugin-starter copying via the cli.\"\n },\n {\n \"title\": \"feat: skip display banner if not utf-8\",\n \"prNumber\": 4344,\n \"type\": \"feature\",\n \"body\": \"\"\n },\n {\n \"title\": \"Fix ESM type declarations in Core\",\n \"prNumber\": 4341,\n \"type\": \"bugfix\",\n \"body\": \"Discord for better coordination: @michavie\\r\\n\\r\\n# Relates to\\r\\n\\r\\nTypeScript type resolution issues in `@elizaos/core` package\\r\\n\\r\\nFixes: https://github.com/elizaOS/eliza/issues/3191\\r\\n\\r\\n# Risks\\r\\n\\r\\nLow - This is a build configuration change that \"\n },\n {\n \"title\": \"fix: agent not found error after GUI creation and resolve merge conflict\",\n \"prNumber\": 4337,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes an issue where starting an agent created via the GUI using the same agent name would result in an error: Agent does not exist in database after ensureAgentExists call.\\r\\n\\r\\nThe issue occurred because multiple agents with the sam\"\n },\n {\n \"title\": \"fix: agent unregistration process with service stop handling\",\n \"prNumber\": 4360,\n \"type\": \"bugfix\",\n \"body\": \"# Relates to\\n\\nUpdate agent service management during unregistration\\n\\n# Risks\\n\\nLow. This change improves resource management when unregistering agents by ensuring all services are properly stopped.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nTh\"\n },\n {\n \"title\": \"fix: small GUI fix\",\n \"prNumber\": 4358,\n \"type\": \"bugfix\",\n \"body\": \"This PR fixes several issues:\\r\\n\\r\\n**1. Removed poor contrast background color for the voice required plugin label**\\r\\n\\r\\n![image](https://github.com/user-attachments/assets/3ebf4b7a-63de-4f84-aa37-f5c3a7c7c8f4)\\r\\n\\r\\n**2. Removed the white/blue b\"\n },\n {\n \"title\": \"chore: add-any-provider-blog\",\n \"prNumber\": 4356,\n \"type\": \"other\",\n \"body\": \"## PR Summary: Improve and Expand OpenAI Plugin Provider Environment Guide\\r\\n\\r\\n### What’s Changed\\r\\n\\r\\n- **Expanded Provider Coverage:** \\r\\n Added a new section for LM Studio, a popular local LLM desktop app, with clear instructions and examp\"\n },\n {\n \"title\": \"chore: 📝 Add docstrings to `cloudflare-logging`\",\n \"prNumber\": 4355,\n \"type\": \"feature\",\n \"body\": \"Docstrings generation was requested by @wtfsayo.\\n\\n* https://github.com/elizaOS/eliza/pull/4354#issuecomment-2827117984\\n\\nThe following files were modified:\\n\\n* `packages/core/src/cloudflare.ts`\\n* `packages/plugin-anthropic/src/index.ts`\\n* `pa\"\n },\n {\n \"title\": \"feat: bring back support for cloudflare llm logging/tracking\",\n \"prNumber\": 4354,\n \"type\": \"feature\",\n \"body\": \"\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added support for routing AI provider requests through Cloudflare AI Gateway when enabled and properly configured.\\n\\n\"\n },\n {\n \"title\": \"chore: refactor sidebar + general ui improvements\",\n \"prNumber\": 4353,\n \"type\": \"refactor\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Refactor**\\n - Improved modularity and readability of the sidebar with new internal components and optimized rendering.\\n - Updated \"\n },\n {\n \"title\": \"fix: tts api\",\n \"prNumber\": 4352,\n \"type\": \"bugfix\",\n \"body\": \"This PR addresses an issue where plugin-openai TTS wasn't working because it returns a Web ReadableStream. The fix properly handles all types of stream responses for TTS APIs\"\n },\n {\n \"title\": \"fix: cli start agent\",\n \"prNumber\": 4351,\n \"type\": \"bugfix\",\n \"body\": \"Currently, when a file path is provided to start an agent with cli, the agent gets created but doesn't automatically start.\"\n },\n {\n \"title\": \"feat: suggest upgrade cli\",\n \"prNumber\": 4350,\n \"type\": \"feature\",\n \"body\": \"## PR: Notify users of new CLI version and code organization improvements\\r\\n\\r\\n### Summary\\r\\n\\r\\nThis PR improves the user experience and maintainability of the ElizaOS CLI by:\\r\\n\\r\\n- **Notifying users when a new version of the CLI is available:**\"\n },\n {\n \"title\": \"feat: support relative char path + other issues\",\n \"prNumber\": 4349,\n \"type\": \"feature\",\n \"body\": \"## PR Description \\r\\n\\r\\nThis PR implements support for loading character configurations using paths that are relative to the current working directory. It also includes several test improvements and adds helpful logging messages.\\r\\n\\r\\n### Key C\"\n },\n {\n \"title\": \"feat: V2 QoL improvements\",\n \"prNumber\": 4348,\n \"type\": \"feature\",\n \"body\": \"# Risks\\r\\n\\r\\nMedium\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n- general logging clean up\\r\\n- cli: fix how plugins are loaded so org-level plugins can be loaded after plugin-sql so we can start tasks in a plugin's init\\r\\n- client: fix cloudfl\"\n },\n {\n \"title\": \"fix: agent null check\",\n \"prNumber\": 4347,\n \"type\": \"bugfix\",\n \"body\": \"\"\n },\n {\n \"title\": \"Feat(plugin-discord): enable typing indicator\",\n \"prNumber\": 4364,\n \"type\": \"feature\",\n \"body\": \"# Relates to\\n\\nFix typing indicator for Discord messages\\n\\n# Risks\\n\\nLow risk - This PR only affects the visual feedback of typing indicators in Discord and doesn't change any core functionality.\\n\\n# Background\\n\\n## What does this PR do?\\n\\nImplem\"\n },\n {\n \"title\": \"fix: issue with postgres db for docker containers. update gh action f…\",\n \"prNumber\": 4363,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nDocker setup for Postgres+ pgvector container.\\r\\nGH action for TEE CI/CD\\r\\n\"\n },\n {\n \"title\": \"Fix broken image paths\",\n \"prNumber\": 4362,\n \"type\": \"bugfix\",\n \"body\": \"Replaced incorrect image paths that caused 404 errors in README_CN.md, README_DE.md, and README_FR.md.\\r\\n\\r\\nOld path: ./docs/static/img/eliza_banner.jpg\\r\\nNew path: static/img/eliza_banner.jpg\\r\\n\\r\\nThis fixes broken banner images that were not d\"\n },\n {\n \"title\": \"Fix: Correct broken Pump.fun link\",\n \"prNumber\": 4367,\n \"type\": \"bugfix\",\n \"body\": \"This pull request updates a broken Pump.fun link \\r\\nThe old link was missing the /coin/ path, leading to a 404 error. The new link correctly directs to the intended resource.\"\n },\n {\n \"title\": \"(chore)plugin anthropic - test coverage and setup\",\n \"prNumber\": 4370,\n \"type\": \"tests\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Updated internal provider usage for improved compatibility. No changes to user-facing features.\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Style**\\n - Updated user-facing command instructions to remove the use of the npx prefix. Commands now appear as elizaos dev, elizao\"\n },\n {\n \"title\": \"docs: updated quick start and intro cli commands\",\n \"prNumber\": 4379,\n \"type\": \"docs\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\r\\nDoc updation\\r\\n\\r\\n\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n - Removed the package metadata and configuration for the EVM plugin.\\r\\n - plugin-evm moved to registry -> https://gi\"\n },\n {\n \"title\": \"chore: remove plugin from monorepo\",\n \"prNumber\": 4398,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n - Removed the video understanding plugin and all related files, including documentation, configuration, build scripts,\"\n },\n {\n \"title\": \"chore: fix local llm throwing undefined error\",\n \"prNumber\": 4396,\n \"type\": \"bugfix\",\n \"body\": \"fixes local ai throwing\\r\\n\\r\\n```\\r\\n[2025-04-29 15:06:40] DEBUG: API request: GET /ping\\r\\n[2025-04-29 15:06:40] DEBUG: API request: GET /agents/b850bc30-45f8-0041-a00a-83df46d8555d/logs\\r\\n[2025-04-29 15:06:40] DEBUG: Skipping plugin handler for s\"\n },\n {\n \"title\": \"fix: agent deletion\",\n \"prNumber\": 4395,\n \"type\": \"bugfix\",\n \"body\": \"Currently, we cannot delete an agent if they own worlds, because it causes a foreign key constraint error on the logs table (logs_roomId_rooms_id_fk).\\r\\n\\r\\nThis PR fixes the issue by first checking for an existing agent to reassign the worlds\"\n },\n {\n \"title\": \"feat: add model/plugin name logging when model is used\",\n \"prNumber\": 4394,\n \"type\": \"feature\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n\\t- Added detailed logging across multiple plugins to display which AI model is being used at runtime, improving trans\"\n },\n {\n \"title\": \"chore: cleaner ui + other minor ui enhancements\",\n \"prNumber\": 4393,\n \"type\": \"refactor\",\n \"body\": \"## PR Description: **UI Improvements, Naming Updates, and Bug Fixes**\\r\\n\\r\\nThis PR introduces several enhancements, fixes, and updates across the codebase:\\r\\n\\r\\n#### **1. Naming Updates**\\r\\n- Replaced references to `room` with `group` across mul\"\n },\n {\n \"title\": \"feat: scopable knowledge\",\n \"prNumber\": 4390,\n \"type\": \"feature\",\n \"body\": \"Right now, knowledge is memories scoped to the agent's UUID, so global only\\r\\n\\r\\nThis PR allows knowledge to be searchable by entityId, worldId, or roomId\"\n },\n {\n \"title\": \"fix : error handling for no space left in disk to users\",\n \"prNumber\": 4389,\n \"type\": \"bugfix\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\n\\\"Screenshot_2025-04-28_at_2\\n## Summary by CodeRabbit\\n\\n- **New Features**\\n - Added detection of Eliza monorepo context and automatic building of core monorepo packages during development work\"\n },\n {\n \"title\": \"feat: added .env.example in project-starter\",\n \"prNumber\": 4387,\n \"type\": \"feature\",\n \"body\": \"\\r\\n\\r\\n# Relates to\\r\\nAdded .env.example in project-template as some users were facing confusion while setting up keys for proj\"\n },\n {\n \"title\": \"chore: remove plugin evm from monorepo\",\n \"prNumber\": 4386,\n \"type\": \"other\",\n \"body\": \"\\n\\n\\n\\n## Summary by CodeRabbit\\n\\n- **Chores**\\n - Removed the EVM plugin package, including all related features, documentation, configuration files, smart contracts, an\"\n },\n {\n \"title\": \"chore: Update docs, changing to docs.eliza.how\",\n \"prNumber\": 4403,\n \"type\": \"other\",\n \"body\": \"## PR Summary: chore: Update docs, changing to docs.eliza.how\\r\\n\\r\\nThis PR includes a series of documentation updates, fixes, and enhancements across the `packages/docs` and `packages/core` directories.\\r\\n\\r\\n**Key Changes:**\\r\\n\\r\\n1. **Documentat\"\n },\n {\n \"title\": \"fix: copy migrations to CLI\",\n \"prNumber\": 4401,\n \"type\": \"bugfix\",\n \"body\": \"# Risks\\r\\nLow. This is a simple fix to ensure database migrations are properly copied to the CLI directory, which affects initial database setup but doesn't pose significant risks to existing installations.\\r\\n\\r\\n# Background\\r\\n## What does this\"\n },\n {\n \"title\": \"chore: remove plugin-pdf from monorepo\",\n \"prNumber\": 4400,\n \"type\": \"other\",\n \"body\": \"\\r\\n\\r\\n\\r\\n## Summary by CodeRabbit\\r\\n\\r\\n- **Chores**\\r\\n - Removed the PDF plugin package and all its related files and documentation.\\r\\n - Updated dependencies in another p\"\n }\n ],\n \"topContributors\": [\n {\n \"username\": \"wtfsayo\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n \"totalScore\": 1739.4607351507161,\n \"prScore\": 1679.6667351507162,\n \"issueScore\": 4,\n \"reviewScore\": 53,\n \"commentScore\": 2.7939999999999996\n },\n {\n \"username\": \"tcm390\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/60634884?u=c6c41679b8322eaa0c81f72e0b4ed95e80f0ac16&v=4\",\n \"totalScore\": 1248.62295481201,\n \"prScore\": 1052.5309548120101,\n \"issueScore\": 28.2,\n \"reviewScore\": 164,\n \"commentScore\": 3.892\n },\n {\n \"username\": \"0xbbjoker\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n \"totalScore\": 872.7938173598334,\n \"prScore\": 860.9378173598334,\n \"issueScore\": 0,\n \"reviewScore\": 9.5,\n \"commentScore\": 2.356\n },\n {\n \"username\": \"HarshModi2005\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/142230924?u=64e337bbdb6b3aded5943b7e297759e7a3cfc0f0&v=4\",\n \"totalScore\": 476.3018349029459,\n \"prScore\": 403.70183490294596,\n \"issueScore\": 0,\n \"reviewScore\": 72,\n \"commentScore\": 0.6000000000000001\n },\n {\n \"username\": \"Samarthsinghal28\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/120447590?v=4\",\n \"totalScore\": 467.5468509776701,\n \"prScore\": 440.5468509776701,\n \"issueScore\": 0,\n \"reviewScore\": 27,\n \"commentScore\": 0\n },\n {\n \"username\": \"odilitime\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n \"totalScore\": 311.8063418606137,\n \"prScore\": 160.9263418606137,\n \"issueScore\": 0,\n \"reviewScore\": 150,\n \"commentScore\": 0.8799999999999999\n },\n {\n \"username\": \"monilpat\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/15067321?v=4\",\n \"totalScore\": 296.87273589759246,\n \"prScore\": 18.692735897592478,\n \"issueScore\": 0,\n \"reviewScore\": 275.5,\n \"commentScore\": 2.68\n },\n {\n \"username\": \"Y4NK33420\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/112804719?v=4\",\n \"totalScore\": 293.58200653555355,\n \"prScore\": 261.28200653555353,\n \"issueScore\": 0,\n \"reviewScore\": 31.5,\n \"commentScore\": 0.8\n },\n {\n \"username\": \"yungalgo\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/113615973?u=92e0f29f7e2fbb8ce46ed13c51f692ca803de02d&v=4\",\n \"totalScore\": 225.13011304605666,\n \"prScore\": 206.93011304605668,\n \"issueScore\": 0,\n \"reviewScore\": 18,\n \"commentScore\": 0.2\n },\n {\n \"username\": \"ncale\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/106794061?u=3269bddd86da2efe1784076e485a5466ad96cb62&v=4\",\n \"totalScore\": 200.10939594487633,\n \"prScore\": 195.00939594487633,\n \"issueScore\": 0,\n \"reviewScore\": 4.5,\n \"commentScore\": 0.6000000000000001\n },\n {\n \"username\": \"lalalune\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/18633264?u=e2e906c3712c2506ebfa98df01c2cfdc50050b30&v=4\",\n \"totalScore\": 182.9700955863044,\n \"prScore\": 167.79209558630438,\n \"issueScore\": 0,\n \"reviewScore\": 14,\n \"commentScore\": 1.178\n },\n {\n \"username\": \"michavie\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/39144548?u=3496eb82a60d2a8e88bf5e22c3ffe5eb2b37d816&v=4\",\n \"totalScore\": 161.46549861415127,\n \"prScore\": 147.76549861415128,\n \"issueScore\": 0,\n \"reviewScore\": 13.5,\n \"commentScore\": 0.2\n },\n {\n \"username\": \"standujar\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4\",\n \"totalScore\": 142.5858095785972,\n \"prScore\": 137.54580957859721,\n \"issueScore\": 4.1,\n \"reviewScore\": 0,\n \"commentScore\": 0.94\n },\n {\n \"username\": \"samarth30\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/48334430?u=1fc119a6c2deb8cf60448b4c8961cb21dc69baeb&v=4\",\n \"totalScore\": 128.12922241295038,\n \"prScore\": 128.12922241295038,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0\n },\n {\n \"username\": \"madjin\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n \"totalScore\": 124.13654779315219,\n \"prScore\": 114.93654779315219,\n \"issueScore\": 4,\n \"reviewScore\": 5,\n \"commentScore\": 0.2\n },\n {\n \"username\": \"hishboy\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/340982?u=3201dbd7bc2c194744a093db20c0c35c7afc96d4&v=4\",\n \"totalScore\": 108.69412084805441,\n \"prScore\": 103.75612084805441,\n \"issueScore\": 0,\n \"reviewScore\": 4.5,\n \"commentScore\": 0.43799999999999994\n },\n {\n \"username\": \"PixelPil0t1\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/161360836?u=cb7120a58d61284a5b7a23ed184b773043ec5123&v=4\",\n \"totalScore\": 108.45195387624292,\n \"prScore\": 108.25195387624292,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0.2\n },\n {\n \"username\": \"avp1598\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/24447702?u=61a032460dcb42f018c54fae76247c6bf49b7b9a&v=4\",\n \"totalScore\": 102.69619275423804,\n \"prScore\": 102.69619275423804,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0\n },\n {\n \"username\": \"ai16z-demirix\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/188117230?u=424cd5b834584b3799da288712b3c4158c8032a1&v=4\",\n \"totalScore\": 91.7902783384985,\n \"prScore\": 91.7902783384985,\n \"issueScore\": 0,\n \"reviewScore\": 0,\n \"commentScore\": 0\n },\n {\n \"username\": \"HashWarlock\",\n \"avatarUrl\": \"https://avatars.githubusercontent.com/u/64296537?u=1d8228a93c06c603e08d438677b3f736d6b1ab22&v=4\",\n \"totalScore\": 90.93310326569872,\n \"prScore\": 81.43310326569872,\n \"issueScore\": 0,\n \"reviewScore\": 9.5,\n \"commentScore\": 0\n }\n ],\n \"newPRs\": 241,\n \"mergedPRs\": 199,\n \"newIssues\": 45,\n \"closedIssues\": 37,\n \"activeContributors\": 89\n}", "github_extracted_data_user_summaries_text_last_7_days_for_2025-04-11": "[\"LongJeongS_week_2025-04-06\", \"LongJeongS\", \"week\", \"2025-04-06\", \"LongJeongS: Created issue #4210 regarding a problem with the OpenAI Plugin using the `gpt-4-vision-preview` model, which has since been closed.\", \"2025-05-13T22:06:46.421Z\"]\n[\"MehmoodSheikh_week_2025-04-06\", \"MehmoodSheikh\", \"week\", \"2025-04-06\", \"MehmoodSheikh: Opened a single issue (#4241) requesting help with enabling tweet functionality with media on platform X. No other contributions or code changes were made during this period.\", \"2025-05-13T22:06:46.696Z\"]\n[\"0xbbjoker_week_2025-04-06\", \"0xbbjoker\", \"week\", \"2025-04-06\", \"0xbbjoker: Merged 3 PRs this week, including fixing an Anthropic JSON parsing issue (#4222, +1097/-794), replacing fastembed with a local embedding model (#4205, +439/-284), and removing deprecated types (#4275, +88/-106). Additionally maintained 3 open PRs focused on feature work and fixes, with significant code changes across 72 files (+12264/-3555) while being active on 3 days of the week.\", \"2025-05-13T22:06:47.775Z\"]\n[\"HarshModi2005_week_2025-04-06\", \"HarshModi2005\", \"week\", \"2025-04-06\", \"HarshModi2005: Merged 5 PRs this week with significant UI improvements, including major UI changes in #4273 (+7014/-2571 lines) and darkened borders/focus states in #4201 (+2308/-1710 lines). Also contributed documentation updates for the telegram plugin in #4219 and provided 2 code reviews with comments, maintaining consistent activity across 5 days of the week.\", \"2025-05-13T22:06:47.250Z\"]\n[\"Samarthsinghal28_week_2025-04-06\", \"Samarthsinghal28\", \"week\", \"2025-04-06\", \"Samarthsinghal28: Merged 4 significant PRs this week, with the most substantial being #4261 \\\"Added: Instrumentation\\\" (+60924/-8347 lines), while also addressing agent subcommands (#4220) and resolving documentation and port availability issues (#4200, #4199). Maintained very consistent work across 5 days, with contributions primarily focused on code changes (+15538/-2271 lines across 169 files) and provided 4 review comments on other PRs.\", \"2025-05-13T22:06:47.826Z\"]\n[\"Titan-Node_week_2025-04-06\", \"Titan-Node\", \"week\", \"2025-04-06\", \"Titan-Node: Created issue #4238 regarding a \\\"V2 - `getTasks` error\\\" which was subsequently closed. No other activity was observed during this period.\", \"2025-05-13T22:06:48.012Z\"]\n[\"Valcyclovir_week_2025-04-06\", \"Valcyclovir\", \"week\", \"2025-04-06\", \"Valcyclovir: Opened issue #4272 regarding a problem with the X bot not responding to mentions. No other activity this week.\", \"2025-05-13T22:06:48.240Z\"]\n[\"avp1598_week_2025-04-06\", \"avp1598\", \"week\", \"2025-04-06\", \"avp1598: Fixed an OpenAI object JSON parse error through PR #4207 (+58/-55 lines), which was merged after 21 hours.\", \"2025-05-13T22:06:49.870Z\"]\n[\"boorich_week_2025-04-06\", \"boorich\", \"week\", \"2025-04-06\", \"boorich: Created issue #4249 regarding duplicate variable declaration in client API error handling, which has since been closed. No other activity this week.\", \"2025-05-13T22:06:49.930Z\"]\n[\"arandaschimpf_week_2025-04-06\", \"arandaschimpf\", \"week\", \"2025-04-06\", \"arandaschimpf: Fixed a JSON parsing issue with nested objects through PR #4198 (+3/-3 lines), which was merged after a significant review period of 767 hours. Activity was limited to a single day this week, with the contribution focused on this specific bugfix.\", \"2025-05-13T22:06:50.232Z\"]\n[\"Y4NK33420_week_2025-04-06\", \"Y4NK33420\", \"week\", \"2025-04-06\", \"Y4NK33420: Merged two significant PRs this week: #4274 clarifying terminology in Agent Settings (+346/-152 lines) and #4262 replacing text inputs with dropdowns for voice model selection (+781/-316 lines). Contributed substantial code changes across 131 files (+17128/-2210 lines) with consistent activity on 6 out of 7 days. Provided 6 review comments and 2 PR comments while maintaining a steady workflow with an average PR merge time of 13 hours.\", \"2025-05-13T22:06:50.667Z\"]\n[\"jinbangyi_week_2025-04-06\", \"jinbangyi\", \"week\", \"2025-04-06\", \"jinbangyi: Opened one pull request (#4206) titled \\\"feat: client -twitter\\\" which is currently still open.\", \"2025-05-13T22:06:56.772Z\"]\n[\"chris35469_week_2025-04-06\", \"chris35469\", \"week\", \"2025-04-06\", \"chris35469: Merged PR #4268 updating the .env.example file to support Twitter post generation, with modest code changes (+2/-1 lines). This was their only contribution during the period, showing sporadic activity.\", \"2025-05-13T22:06:51.915Z\"]\n[\"jiggyjo11_week_2025-04-06\", \"jiggyjo11\", \"week\", \"2025-04-06\", \"jiggyjo11: Reported two Discord-related issues (#4269 and #4258) which were both subsequently closed. Engaged in discussions on these issues with 2 comments, focusing on deployment and startup problems with the Discord client.\", \"2025-05-13T22:06:52.851Z\"]\n[\"hishboy_week_2025-04-06\", \"hishboy\", \"week\", \"2025-04-06\", \"hishboy: Fixed a runtime initialization issue with PR #4253 (+6/-5 lines), which addressed proper sequencing of initialization steps. Made substantial code changes across 72 files (+14,090/-1,477 lines) in 4 commits, while also providing 1 code review and 7 PR comments. Active on 2 days this week, with contributions evenly split between bugfix work and other development tasks.\", \"2025-05-13T22:06:52.877Z\"]\n[\"ai16z-demirix_week_2025-04-06\", \"ai16z-demirix\", \"week\", \"2025-04-06\", \"ai16z-demirix: Merged a significant PR (#4233) focused on video understanding plugin tests, adding over 9,000 lines and removing about 3,000 lines of code. Contributed 7 commits across 40 files, with 80% of changes in test files and 20% in configuration files. Active on 2 days this week, primarily working on test improvements.\", \"2025-05-13T22:06:50.419Z\"]\n[\"jmikedupont2_week_2025-04-06\", \"jmikedupont2\", \"week\", \"2025-04-06\", \"jmikedupont2: Provided one code review with approval this week. No other activity observed.\", \"2025-05-13T22:06:52.311Z\"]\n[\"levsagiv_week_2025-04-06\", \"levsagiv\", \"week\", \"2025-04-06\", \"levsagiv: Created issue #4224 regarding \\\"Provider Data Not Used When Posting to Twitter\\\" and added one comment to an issue. No code contributions or PR activity this week.\", \"2025-05-13T22:06:54.105Z\"]\n[\"madjin_week_2025-04-06\", \"madjin\", \"week\", \"2025-04-06\", \"madjin: Created one issue (#4260) related to updating the community section and made a single PR comment. No code changes or other significant activity this period.\", \"2025-05-13T22:06:54.434Z\"]\n[\"michavie_week_2025-04-06\", \"michavie\", \"week\", \"2025-04-06\", \"michavie: Merged two significant PRs this week: #4230 \\\"Add OpenAi model usage events\\\" (+8813/-2793 lines) and #4223 \\\"Fix relationship between entities and agents\\\" (+5390/-2070 lines), with both involving substantial code changes. Also has one open PR (#4229) on the same OpenAI model usage topic, showing focused work in this area.\", \"2025-05-13T22:06:55.667Z\"]\n[\"monilpat_week_2025-04-06\", \"monilpat\", \"week\", \"2025-04-06\", \"monilpat: Conducted extensive code reviews this week with 21 reviews (6 approvals, 6 change requests, 8 comments) and added 5 PR comments. Made significant code changes across 253 files (+6288/-3233 lines) in 10 commits, showing very consistent work activity on 5 out of 7 days.\", \"2025-05-13T22:07:00.080Z\"]\n[\"odilitime_week_2025-04-06\", \"odilitime\", \"week\", \"2025-04-06\", \"odilitime: Conducted 14 code reviews providing comments, while making substantial code changes across 50 files (+3755/-218 lines) in 11 commits. Activity was concentrated on a single day, with work primarily focused on other tasks (73%) and bug fixes (27%).\", \"2025-05-13T22:06:59.726Z\"]\n[\"nitzansaar_week_2025-04-06\", \"nitzansaar\", \"week\", \"2025-04-06\", \"nitzansaar: Opened PR #4232 to resolve a Hapi shot error, with significant code changes across 30 files (+52617/-3754 lines). Active on 3 days this week, with work split evenly between feature development and other tasks, primarily modifying configuration and code files.\", \"2025-05-13T22:06:58.065Z\"]\n[\"ngmachado_week_2025-04-06\", \"ngmachado\", \"week\", \"2025-04-06\", \"ngmachado: Merged a significant PR #4235 \\\"Semantic splitText\\\" with substantial code changes (+52540/-24045 lines) and made one PR comment during the week. Active on only one day this period, focusing entirely on this major text processing feature implementation.\", \"2025-05-13T22:06:57.240Z\"]\n[\"ncale_week_2025-04-06\", \"ncale\", \"week\", \"2025-04-06\", \"ncale: Made code contributions across 11 files (+231/-23 lines) over 8 commits, while also providing 1 code review and 2 PR comments. Activity was spread across 3 days with a mixed focus on feature development (38%), bug fixes (25%), and smaller amounts of refactoring and documentation work.\", \"2025-05-13T22:06:57.542Z\"]\n[\"pierce403_week_2025-04-06\", \"pierce403\", \"week\", \"2025-04-06\", \"pierce403: Merged a single substantial PR #4214 \\\"Feature/plugin venice\\\" that added 742 lines and removed 34 lines across 8 files. The contribution was focused on feature work and configuration changes, with some code, test, and documentation updates.\", \"2025-05-13T22:06:59.742Z\"]\n[\"tskoyo_week_2025-04-06\", \"tskoyo\", \"week\", \"2025-04-06\", \"tskoyo: Created issue #4234 regarding a missing type definition file for 'hapi__shot', which has since been closed.\", \"2025-05-13T22:07:01.182Z\"]\n[\"piperTang_week_2025-04-06\", \"piperTang\", \"week\", \"2025-04-06\", \"piperTang: Merged a single PR (#4243) focused on fixing knowledge types, which involved substantial code changes (+6727/-2207 lines). Active on only one day during this period.\", \"2025-05-13T22:07:00.837Z\"]\n[\"vamostibor03_week_2025-04-06\", \"vamostibor03\", \"week\", \"2025-04-06\", \"vamostibor03: Created issue #4221 regarding agent setup problems, which has since been closed. No other activity this period.\", \"2025-05-13T22:07:01.699Z\"]\n[\"xeroc_week_2025-04-06\", \"xeroc\", \"week\", \"2025-04-06\", \"xeroc: Reported one issue (#4251) regarding a plugin registration problem, which has since been closed. Engaged with the community by commenting on one issue.\", \"2025-05-13T22:07:02.674Z\"]\n[\"yungalgo_week_2025-04-06\", \"yungalgo\", \"week\", \"2025-04-06\", \"yungalgo: Merged 3 PRs this week, focusing entirely on bug fixes including PR #4242 that fixed GitHub authentication during CLI start commands (+80/-43 lines) and PR #4246 that removed duplicate declarations in api.ts. Contributed to discussions on 2 issues while maintaining an occasional activity pattern, being active on 2 days of the week.\", \"2025-05-13T22:07:09.618Z\"]\n[\"wtfsayo_week_2025-04-06\", \"wtfsayo\", \"week\", \"2025-04-06\", \"wtfsayo: Led a significant CLI improvement effort with 13 merged PRs (+4753/-2379 lines), focusing on plugin installation enhancements (#4256, #4202), code cleanup (#4248, #4240, #4239), and dependency management (#4204, #4218). Contributed consistently throughout the week with 42 commits across 264 files, while also providing 7 code reviews to support team progress.\", \"2025-05-13T22:07:03.213Z\"]\n[\"tcm390_week_2025-04-06\", \"tcm390\", \"week\", \"2025-04-06\", \"tcm390: Merged 15 PRs this week with significant feature additions including OpenAI TTS support (#4255, #4259), message API implementation (#4247), and improved reply actions (#4213), alongside numerous bug fixes for Discord actions, transcription, and UI issues. Consistently active across 6 days, contributing substantial code changes (+1489/-682 lines) with a balanced focus between new features (55%) and bug fixes (32%). Created 3 issues (all now closed) and participated in code reviews, demonstrating comprehensive involvement in both development and quality assurance.\", \"2025-05-13T22:07:03.577Z\"]\n[\"Imsharad_day_2025-04-05\", \"Imsharad\", \"day\", \"2025-04-05\", \"Imsharad: Made significant code changes by modifying 1 file, resulting in a net change of +24 lines and -191 lines, with a primary focus on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:15.266Z\"]\n[\"emmanuel-ferdman_day_2025-04-05\", \"emmanuel-ferdman\", \"day\", \"2025-04-05\", \"emmanuel-ferdman: Opened 1 PR (#4193) focused on updating the local development guide and made modifications to 1 file (+1/-1 lines), demonstrating consistent documentation work today.\", \"2025-05-14T07:28:15.287Z\"]\n[\"monilpat_day_2025-04-05\", \"monilpat\", \"day\", \"2025-04-05\", \"monilpat: Made significant code changes by modifying 114 files, resulting in a net addition of 6024 lines and a reduction of 1854 lines, with a primary focus on other work. Actively engaged in the review process with 3 total reviews, including 2 approvals and 1 change request.\", \"2025-05-14T07:28:15.564Z\"]\n[\"Samarthsinghal28_day_2025-04-05\", \"Samarthsinghal28\", \"day\", \"2025-04-05\", \"Samarthsinghal28: Merged 2 PRs, including #4196 which fixed the issue with the elizaos test command (+82/-354 lines) and #4194 addressing the bun installation issue for plugin-bootstrap (+0/-1 lines). Focused entirely on bugfix work, modifying 5 files with a total of +82/-355 lines across 2 commits.\", \"2025-05-14T07:28:15.757Z\"]\n[\"Y4NK33420_day_2025-04-05\", \"Y4NK33420\", \"day\", \"2025-04-05\", \"Y4NK33420: Merged 1 PR (#4197) focused on fixing the delete character button, contributing a significant change of +16815/-2099 lines. Modified 6 files with a total of +510/-110 lines, demonstrating consistent bugfix work today.\", \"2025-05-14T07:28:16.055Z\"]\n[\"tcm390_day_2025-04-05\", \"tcm390\", \"day\", \"2025-04-05\", \"tcm390: Merged 1 pull request (#4192) addressing Twitter interaction with significant code changes (+338/-354 lines), demonstrating consistent activity with a focus on other work.\", \"2025-05-14T07:28:16.461Z\"]\n[\"urgarcia_day_2025-04-05\", \"urgarcia\", \"day\", \"2025-04-05\", \"urgarcia: Created 1 issue (#4191 \\\"Issue when running elizaos start on Windows (Node/NVM v23.3)\\\", CLOSED), demonstrating sporadic activity today with no other contributions.\", \"2025-05-14T07:28:16.504Z\"]\n[\"wtfsayo_day_2025-04-06\", \"wtfsayo\", \"day\", \"2025-04-06\", \"wtfsayo: Merged 3 PRs in the local-ai project, including #4204 (+802/-53 lines) and #4202 (+196/-227 lines), with a total of +1010/-424 lines modified across 9 files. Maintained a consistent activity pattern with 3 commits today, focusing entirely on other work.\", \"2025-05-14T07:28:17.233Z\"]\n[\"HarshModi2005_day_2025-04-06\", \"HarshModi2005\", \"day\", \"2025-04-06\", \"HarshModi2005: Merged 1 PR (#4201) focused on darkening borders and focus states in UI components (+2308/-1710 lines), while modifying 46 files with a total of +1192/-894 lines across 3 commits. Maintained a consistent activity pattern, contributing primarily to code changes.\", \"2025-05-14T07:28:17.234Z\"]\n[\"Samarthsinghal28_day_2025-04-06\", \"Samarthsinghal28\", \"day\", \"2025-04-06\", \"Samarthsinghal28: Merged 2 significant PRs today, including #4200 which addressed documentation issues (+1040/-467 lines) and #4199 resolving the elizaos port issue (+1081/-468 lines). The contributions were evenly split between bug fixes and other work, with modifications made to 6 files (+46/-6 lines).\", \"2025-05-14T07:28:17.285Z\"]\n[\"voronor_day_2025-04-05\", \"voronor\", \"day\", \"2025-04-05\", \"voronor: Merged 1 PR (#4195) focused on making the cleanup script compatible across platforms, resulting in significant changes of +52126/-24087 lines. Demonstrated consistent activity with 1 file modified (+1/-1 lines) and a primary focus on refactor work.\", \"2025-05-14T07:28:17.296Z\"]\n[\"monilpat_day_2025-04-06\", \"monilpat\", \"day\", \"2025-04-06\", \"monilpat: Made significant code changes by modifying 109 files (+3191/-1745 lines) with a primary focus on other work, while also providing 8 reviews (2 approvals, 2 change requests, 4 comments) and 2 comments on PRs. Active today, demonstrating a consistent work pattern with 3 commits.\", \"2025-05-14T07:28:17.473Z\"]\n[\"arandaschimpf_day_2025-04-06\", \"arandaschimpf\", \"day\", \"2025-04-06\", \"arandaschimpf: Merged 1 pull request (#4198) addressing a JSON parse problem with nested objects (+3/-3 lines) and made modifications to 2 files with a total of 3 lines changed. The work was evenly split between bugfix efforts and other contributions, maintaining a consistent activity pattern.\", \"2025-05-14T07:28:17.525Z\"]\n[\"LongJeongS_day_2025-04-07\", \"LongJeongS\", \"day\", \"2025-04-07\", \"LongJeongS: Created 1 issue today (#4210 \\\"OpenAI Plugin using `gpt-4-vision-preview` model leading to 4...\\\") which has been closed, showing sporadic activity with no other contributions.\", \"2025-05-14T07:28:18.323Z\"]\n[\"avp1598_day_2025-04-07\", \"avp1598\", \"day\", \"2025-04-07\", \"avp1598: Merged 1 PR (#4207) addressing a JSON parse error with code changes of +58/-55 lines, demonstrating a consistent focus on bugfix work. Active today, contributing to the codebase with a single commit.\", \"2025-05-14T07:28:18.348Z\"]\n[\"HarshModi2005_day_2025-04-08\", \"HarshModi2005\", \"day\", \"2025-04-08\", \"HarshModi2005: Merged 1 PR (#4219) focused on updating the README.md for the telegram plugin, contributing a total of +80/-55 lines. Maintained consistent activity with a primary focus on documentation changes.\", \"2025-05-14T07:28:18.375Z\"]\n[\"Y4NK33420_day_2025-04-07\", \"Y4NK33420\", \"day\", \"2025-04-07\", \"Y4NK33420: Made significant code changes by modifying 2 files with a total of +254/-4 lines, focusing on ensuring tests work (100%). Additionally, contributed 1 comment on a pull request and maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:18.530Z\"]\n[\"Samarthsinghal28_day_2025-04-08\", \"Samarthsinghal28\", \"day\", \"2025-04-08\", \"Samarthsinghal28: Merged 1 pull request (#4220) focused on bug fixes, contributing a total of +29/-12 lines across 3 modified files. Demonstrated consistent activity with a commitment to resolving issues, remaining active every day.\", \"2025-05-14T07:28:18.547Z\"]\n[\"ai16z-demirix_day_2025-04-08\", \"ai16z-demirix\", \"day\", \"2025-04-08\", \"ai16z-demirix: Merged 1 PR (#4233) focused on video understanding plugin tests, contributing a significant +9032/-3063 lines across 5 modified files. The primary emphasis was on testing work, reflecting consistent activity with an average PR complexity of +462/-3 lines.\", \"2025-05-14T07:28:18.577Z\"]\n[\"boorich_day_2025-04-10\", \"boorich\", \"day\", \"2025-04-10\", \"boorich: Created 1 issue (#4249 \\\"Duplicate variable declaration in client API error handling\\\", CLOSED) today, showing sporadic activity with no other contributions.\", \"2025-05-14T07:28:18.593Z\"]\n[\"0xbbjoker_day_2025-04-07\", \"0xbbjoker\", \"day\", \"2025-04-07\", \"0xbbjoker: Merged 1 pull request (#4205) addressing a bug fix by replacing fastembed with a local embedding model, contributing +439/-284 lines. Currently, 1 pull request (#4211) is open, focusing on ensuring responses for direct messages and private messages.\", \"2025-05-14T07:28:18.609Z\"]\n[\"0xbbjoker_day_2025-04-08\", \"0xbbjoker\", \"day\", \"2025-04-08\", \"0xbbjoker: Merged 1 PR (#4222) addressing the anthropic json parse issue with significant changes (+1097/-794 lines) and opened another PR (#4227) focused on testing adapters. Active today with modifications across 5 files, primarily enhancing test functionality (+2846/-0 lines).\", \"2025-05-14T07:28:18.630Z\"]\n[\"0xbbjoker_day_2025-04-10\", \"0xbbjoker\", \"day\", \"2025-04-10\", \"0xbbjoker: Made significant code changes by modifying 41 files with a total of 6 commits, contributing +6782 lines of code while focusing primarily on feature work (67%). Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:18.647Z\"]\n[\"Y4NK33420_day_2025-04-09\", \"Y4NK33420\", \"day\", \"2025-04-09\", \"Y4NK33420: Made significant code changes by modifying 27 files with a total of 921 additions and 598 deletions across 2 commits, demonstrating a consistent work pattern with activity every day. Conducted 2 reviews, providing comments but no approvals or change requests.\", \"2025-05-14T07:28:18.668Z\"]\n[\"MehmoodSheikh_day_2025-04-09\", \"MehmoodSheikh\", \"day\", \"2025-04-09\", \"MehmoodSheikh: Created 1 issue today (#4241 \\\"I want to enable tweet with media on platform X. Can anyone g...\\\") and has shown sporadic activity, being active on 0 out of 1 days this period.\", \"2025-05-14T07:28:18.684Z\"]\n[\"hishboy_day_2025-04-10\", \"hishboy\", \"day\", \"2025-04-10\", \"hishboy: Merged 1 PR (#4253) with code changes of +6/-5 lines, focusing primarily on other work (67%) and bugfix work (33%). Maintained a consistent activity pattern with 3 commits and 1 review comment today.\", \"2025-05-14T07:28:18.730Z\"]\n[\"Titan-Node_day_2025-04-09\", \"Titan-Node\", \"day\", \"2025-04-09\", \"Titan-Node: Created 1 issue today, specifically #4238 titled \\\"V2 - `getTasks` error,\\\" which has been closed. The activity pattern shows sporadic engagement, being active on only 1 out of 1 days.\", \"2025-05-14T07:28:18.746Z\"]\n[\"Y4NK33420_day_2025-04-08\", \"Y4NK33420\", \"day\", \"2025-04-08\", \"Y4NK33420: Made significant code changes by modifying 90 files, resulting in a total of +15,130 lines added and -1,387 lines removed, with a primary focus on other work. Maintained a consistent activity pattern, being active on 1 out of 1 days.\", \"2025-05-14T07:28:18.764Z\"]\n[\"Samarthsinghal28_day_2025-04-10\", \"Samarthsinghal28\", \"day\", \"2025-04-10\", \"Samarthsinghal28: Merged 1 pull request (#4261) with significant changes of +60924/-8347 lines, while modifying 47 files across 4 commits (+1224/-363 lines). Maintained a consistent activity pattern, focusing entirely on other work today.\", \"2025-05-14T07:28:18.829Z\"]\n[\"HarshModi2005_day_2025-04-07\", \"HarshModi2005\", \"day\", \"2025-04-07\", \"HarshModi2005: Merged 1 pull request (#4209 \\\"Starting Agent Fix\\\") with a contribution of +129/-51 lines, while modifying 6 files for a total of +177/-136 lines across 3 commits, focusing entirely on bugfix work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:18.877Z\"]\n[\"0xbbjoker_day_2025-04-11\", \"0xbbjoker\", \"day\", \"2025-04-11\", \"0xbbjoker: Made significant contributions with modifications to 26 files, resulting in a total of +2636/-576 lines, focusing entirely on feature work. Active today and maintaining a consistent work pattern with 2 commits.\", \"2025-05-14T07:28:18.898Z\"]\n[\"Samarthsinghal28_day_2025-04-09\", \"Samarthsinghal28\", \"day\", \"2025-04-09\", \"Samarthsinghal28: Opened 1 PR (#4245) titled \\\"added : plugin-gtk\\\" and made significant code changes by modifying 21 files with a total of +10,561 lines. Demonstrating consistent activity, Samarthsinghal28 focused entirely on other work today.\", \"2025-05-14T07:28:18.914Z\"]\n[\"0xbbjoker_day_2025-04-09\", \"0xbbjoker\", \"day\", \"2025-04-09\", \"0xbbjoker: Opened 1 pull request (#4244) focused on adding a compatibility runtime, with no code changes or merged contributions today. Activity remains sporadic, being active on only 1 out of the last 1 days.\", \"2025-05-14T07:28:18.931Z\"]\n[\"HarshModi2005_day_2025-04-11\", \"HarshModi2005\", \"day\", \"2025-04-11\", \"HarshModi2005: Made significant code changes by modifying 5 files, resulting in a net change of +93/-56 lines across 2 commits, with a primary focus on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:18.952Z\"]\n[\"chris35469_day_2025-04-11\", \"chris35469\", \"day\", \"2025-04-11\", \"chris35469: Merged 1 PR (#4268) with significant changes to the .env.example file, contributing +762/-160 lines, and maintained a consistent activity pattern with a focus on feature work.\", \"2025-05-14T07:28:19.191Z\"]\n[\"jiggyjo11_day_2025-04-11\", \"jiggyjo11\", \"day\", \"2025-04-11\", \"jiggyjo11: Created 2 issues today, both of which were closed: #4269 regarding Discord not replying when deployed with Docker on Google Cloud, and #4258 about the Discord client not loading on pnpm start. Additionally, commented on 1 issue, showing sporadic activity with a focus on troubleshooting.\", \"2025-05-14T07:28:19.464Z\"]\n[\"monilpat_day_2025-04-08\", \"monilpat\", \"day\", \"2025-04-08\", \"monilpat: Engaged in the review process with 1 comment on a pull request, demonstrating sporadic activity today.\", \"2025-05-14T07:28:19.512Z\"]\n[\"Y4NK33420_day_2025-04-11\", \"Y4NK33420\", \"day\", \"2025-04-11\", \"Y4NK33420: Made significant code changes by modifying 4 files, resulting in a net change of +323 lines and -105 lines, with a primary focus on other work. Additionally, contributed 1 comment on a pull request, maintaining a consistent activity pattern with engagement on all active days.\", \"2025-05-14T07:28:19.615Z\"]\n[\"jiggyjo11_day_2025-04-10\", \"jiggyjo11\", \"day\", \"2025-04-10\", \"jiggyjo11: Created 1 issue (#4258 \\\"discord client not loading on pnpm start\\\") which has been closed, showing sporadic activity today.\", \"2025-05-14T07:28:19.665Z\"]\n[\"hishboy_day_2025-04-07\", \"hishboy\", \"day\", \"2025-04-07\", \"hishboy: Made significant code changes by modifying 69 files with a total of +14,084/-1,472 lines, focusing entirely on bugfix work. Active today, demonstrating a consistent work pattern with daily contributions.\", \"2025-05-14T07:28:19.692Z\"]\n[\"Y4NK33420_day_2025-04-10\", \"Y4NK33420\", \"day\", \"2025-04-10\", \"Y4NK33420: Merged 1 pull request (#4262) focused on replacing the text input with a dropdown for voice model selection, resulting in significant code changes of +781/-316 lines. Maintained a consistent activity pattern with 4 comments in reviews, primarily working on code modifications across 3 files (+260/-14 lines).\", \"2025-05-14T07:28:19.700Z\"]\n[\"jinbangyi_day_2025-04-07\", \"jinbangyi\", \"day\", \"2025-04-07\", \"jinbangyi: Opened 1 pull request (#4206) titled \\\"feat: client -twitter\\\" but has not merged any PRs today. Activity remains sporadic with no other contributions noted.\", \"2025-05-14T07:28:19.734Z\"]\n[\"madjin_day_2025-04-10\", \"madjin\", \"day\", \"2025-04-10\", \"madjin: Created 1 issue today, specifically #4260 \\\"chore: Update community section\\\" (OPEN), reflecting sporadic activity with no other contributions.\", \"2025-05-14T07:28:19.748Z\"]\n[\"ncale_day_2025-04-09\", \"ncale\", \"day\", \"2025-04-09\", \"ncale: Contributed to feature and documentation work by modifying 2 files (+38/-1 lines) across 2 commits, and provided 1 comment on a pull request. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:19.771Z\"]\n[\"levsagiv_day_2025-04-08\", \"levsagiv\", \"day\", \"2025-04-08\", \"levsagiv: Created 1 issue today, titled \\\"Provider Data Not Used When Posting to Twitter\\\" (#4224), and remains sporadically active with no merged pull requests or code changes.\", \"2025-05-14T07:28:19.821Z\"]\n[\"tcm390_day_2025-04-07\", \"tcm390\", \"day\", \"2025-04-07\", \"tcm390: Merged 1 pull request (#4212 \\\"feat: skip should respond for dm\\\") with significant changes of +111/-39 lines, while modifying 6 files across 4 commits (+84/-32 lines). Maintained a consistent activity pattern, contributing actively today.\", \"2025-05-14T07:28:19.935Z\"]\n[\"monilpat_day_2025-04-10\", \"monilpat\", \"day\", \"2025-04-10\", \"monilpat: Made significant code changes by modifying 56 files, resulting in a total of +1529/-857 lines, with a primary focus on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:20.081Z\"]\n[\"odilitime_day_2025-04-09\", \"odilitime\", \"day\", \"2025-04-09\", \"odilitime: Engaged in code reviews with a total of 14 comments across various pull requests, demonstrating a commitment to collaboration despite no merged or open pull requests today. Activity remains sporadic, with no contributions in other areas.\", \"2025-05-14T07:28:20.133Z\"]\n[\"monilpat_day_2025-04-09\", \"monilpat\", \"day\", \"2025-04-09\", \"monilpat: Made significant code changes by modifying 31 files, resulting in a total of +393/-171 lines, with a primary focus on other work. Actively engaged in the review process with 2 total reviews, including 1 approval and 1 change request, demonstrating consistent daily activity.\", \"2025-05-14T07:28:20.180Z\"]\n[\"ngmachado_day_2025-04-08\", \"ngmachado\", \"day\", \"2025-04-08\", \"ngmachado: Merged 1 PR (#4235 \\\"Semantic splitText\\\") with significant changes of +52540/-24045 lines, while modifying 1 file (+84/-9 lines) in a focused effort on other work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:20.201Z\"]\n[\"ai16z-demirix_day_2025-04-09\", \"ai16z-demirix\", \"day\", \"2025-04-09\", \"ai16z-demirix: Made significant code changes by modifying 35 files with a total of 1688 additions and 661 deletions, focusing entirely on tests work. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:20.230Z\"]\n[\"ncale_day_2025-04-08\", \"ncale\", \"day\", \"2025-04-08\", \"ncale: Made significant code changes by modifying 6 files (+28/-21 lines) with a focus on bugfix work (50%), alongside feature and refactor efforts (25% each), and contributed 1 review with a comment. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:20.231Z\"]\n[\"monilpat_day_2025-04-11\", \"monilpat\", \"day\", \"2025-04-11\", \"monilpat: Made significant code changes by modifying 43 files with a total of 764 additions and 299 deletions across 2 commits, demonstrating a consistent work pattern with activity every day. Additionally, contributed to the review process with 1 comment on a pull request.\", \"2025-05-14T07:28:20.246Z\"]\n[\"michavie_day_2025-04-08\", \"michavie\", \"day\", \"2025-04-08\", \"michavie: Merged 2 significant PRs (#4230 with +8813/-2793 lines and #4223 with +5390/-2070 lines) and opened 1 PR (#4229), demonstrating a strong focus on feature development. Modified 8 files with a total of +67/-24 lines across 5 commits, maintaining consistent activity.\", \"2025-05-14T07:28:20.248Z\"]\n[\"nitzansaar_day_2025-04-11\", \"nitzansaar\", \"day\", \"2025-04-11\", \"nitzansaar: Made significant code changes by modifying 13 files with a total of +51,654/-3,746 lines, focusing entirely on feature work. Active today, demonstrating a consistent work pattern with daily contributions.\", \"2025-05-14T07:28:20.444Z\"]\n[\"monilpat_day_2025-04-07\", \"monilpat\", \"day\", \"2025-04-07\", \"monilpat: Reviewed 1 pull request, issuing 1 change request, but did not merge any PRs or make any code changes today. Activity remains sporadic, with engagement on only 1 out of the last 1 days.\", \"2025-05-14T07:28:20.561Z\"]\n[\"piperTang_day_2025-04-09\", \"piperTang\", \"day\", \"2025-04-09\", \"piperTang: Merged 1 PR (#4243) focused on fixing knowledge types, contributing a significant change of +6727/-2207 lines. Maintained consistent activity with 1 file modified in bugfix work, demonstrating a strong commitment to resolving issues.\", \"2025-05-14T07:28:20.567Z\"]\n[\"ncale_day_2025-04-11\", \"ncale\", \"day\", \"2025-04-11\", \"ncale: Made significant code changes by modifying 3 files with a total of +165/-1 lines across 2 commits, focusing equally on feature work and other tasks. Maintained a consistent activity pattern, being active every day.\", \"2025-05-14T07:28:20.582Z\"]\n[\"xeroc_day_2025-04-10\", \"xeroc\", \"day\", \"2025-04-10\", \"xeroc: Created 1 issue (#4251) regarding the registration of \\\"@elizaos/plugin-anthropic@1.0.0-beta.28,\\\" which has since been closed, showing sporadic activity today.\", \"2025-05-14T07:28:20.709Z\"]\n[\"tcm390_day_2025-04-10\", \"tcm390\", \"day\", \"2025-04-10\", \"tcm390: Merged 4 PRs, including significant features like #4247 \\\"feat: message api\\\" (+130/-0 lines) and #4259 \\\"feat: openai tts test\\\" (+465/-276 lines), while also commenting on 1 issue and providing 6 comments on PRs. Active today with 8 commits, focusing primarily on other work (63%) and tests (25%), modifying 39 files (+642/-285 lines).\", \"2025-05-14T07:28:21.029Z\"]\n[\"wtfsayo_day_2025-04-07\", \"wtfsayo\", \"day\", \"2025-04-07\", \"wtfsayo: Merged 1 pull request (#4208) focused on updating the CLI readme, contributing a total of +363/-213 lines. Maintained a consistent activity pattern, with a primary focus on documentation changes.\", \"2025-05-14T07:28:21.101Z\"]\n[\"tskoyo_day_2025-04-08\", \"tskoyo\", \"day\", \"2025-04-08\", \"tskoyo: Created 1 issue (#4234 \\\"Cannot find type definition file for 'hapi__shot'.\\\") which has been closed, showing sporadic activity today.\", \"2025-05-14T07:28:21.329Z\"]\n[\"vamostibor03_day_2025-04-08\", \"vamostibor03\", \"day\", \"2025-04-08\", \"vamostibor03: Created 1 issue today, titled \\\"Setting up agent doesn't work\\\" (#4221), which has been closed. Activity remains sporadic with no merged pull requests or code changes.\", \"2025-05-14T07:28:21.354Z\"]\n[\"yungalgo_day_2025-04-10\", \"yungalgo\", \"day\", \"2025-04-10\", \"yungalgo: Merged 2 PRs today, including #4257 (+1/-1 lines) and #4246 (-5 lines), with a primary focus on bugfix work. Consistently active, modifying 2 files with a total of +1/-6 lines across 2 commits.\", \"2025-05-14T07:28:21.392Z\"]\n[\"nitzansaar_day_2025-04-08\", \"nitzansaar\", \"day\", \"2025-04-08\", \"nitzansaar: Opened 1 PR (#4232) focused on resolving a hapi shot error, while modifying 15 files with a total of +955/-8 lines across 2 commits, demonstrating consistent daily activity.\", \"2025-05-14T07:28:21.436Z\"]\n[\"tcm390_day_2025-04-09\", \"tcm390\", \"day\", \"2025-04-09\", \"tcm390: Merged 2 PRs focused on bug fixes, including #4237 \\\"fix: gui tts\\\" (+9/-1 lines) and #4236 \\\"fix: transcription\\\" (+45/-16 lines), while modifying 6 files with a total of +54/-17 lines across 6 commits. Consistently active with a strong emphasis on addressing bugs, having created 2 issues that were both closed today.\", \"2025-05-14T07:28:21.479Z\"]\n[\"yungalgo_day_2025-04-09\", \"yungalgo\", \"day\", \"2025-04-09\", \"yungalgo: Merged 1 PR (#4242) focused on fixing the GitHub authentication prompt during the start CLI command, contributing a total of +80/-43 lines. Maintained a consistent activity pattern, actively contributing to bugfix work today.\", \"2025-05-14T07:28:21.624Z\"]\n[\"wtfsayo_day_2025-04-11\", \"wtfsayo\", \"day\", \"2025-04-11\", \"wtfsayo: Merged 2 PRs today, including #4267 \\\"add missing bootstrap plugin to list\\\" (+2/-0 lines) and #4263 \\\"remove dead-code around plugin install\\\" (+67/-103 lines), while modifying 8 files overall (+71/-103 lines) with a focus on feature work (67%). Active consistently, wtfsayo has demonstrated a strong commitment to code quality with an average PR complexity of +35/-52 lines.\", \"2025-05-14T07:28:21.683Z\"]\n[\"tcm390_day_2025-04-11\", \"tcm390\", \"day\", \"2025-04-11\", \"tcm390: Merged 3 PRs focused on bug fixes, including #4266 \\\"fix: cyclic error\\\" (+19/-2 lines), #4265 \\\"fix: discord voice join/leave action\\\" (+5/-6 lines), and #4264 \\\"fix: discord actions small fix\\\" (+20/-2 lines), while modifying 10 files with a total of +63/-12 lines across 6 commits. Actively engaged with the community by commenting on 1 issue and providing 2 comments on PRs, demonstrating consistent daily contributions.\", \"2025-05-14T07:28:21.730Z\"]\n[\"wtfsayo_day_2025-04-10\", \"wtfsayo\", \"day\", \"2025-04-10\", \"wtfsayo: Merged 3 PRs, including #4248 with significant refactoring work (+1559/-701 lines), and made a total of 10 commits modifying 38 files (+1922/-601 lines). Maintained a consistent activity pattern with a focus on refactoring (40%) and other improvements (40%).\", \"2025-05-14T07:28:21.816Z\"]\n[\"pierce403_day_2025-04-08\", \"pierce403\", \"day\", \"2025-04-08\", \"pierce403: Merged 1 PR (#4214 \\\"Feature/plugin venice\\\") with significant contributions of +742/-34 lines, demonstrating a balanced focus on feature work and other tasks. Active today with modifications across 8 files, maintaining a consistent work pattern.\", \"2025-05-14T07:28:22.258Z\"]\n[\"wtfsayo_day_2025-04-09\", \"wtfsayo\", \"day\", \"2025-04-09\", \"wtfsayo: Merged 2 PRs (#4240 \\\"chore: cli cleanup-2\\\" +162/-109 lines, #4239 \\\"chore: cli clean ups\\\" +298/-166 lines), with a total of 6 commits modifying 56 files (+1239/-941 lines). The primary focus was on other work (67%), demonstrating consistent activity with significant contributions to code and documentation.\", \"2025-05-14T07:28:22.315Z\"]\n[\"wtfsayo_day_2025-04-08\", \"wtfsayo\", \"day\", \"2025-04-08\", \"wtfsayo: Merged 2 PRs (#4218 and #4216) with a total of +373/-216 lines, while modifying 152 files across 19 commits, focusing primarily on other work (68%). Maintained a consistent activity pattern, contributing significantly to the codebase today.\", \"2025-05-14T07:28:22.501Z\"]\n[\"tcm390_day_2025-04-08\", \"tcm390\", \"day\", \"2025-04-08\", \"tcm390: Merged 4 PRs, including a significant UI fix in #4217 (+372/-216 lines) and improved reply actions in #4213 (+42/-11 lines), while also creating 3 issues related to bugs and errors, all of which were closed. Demonstrated consistent activity with 12 commits, focusing primarily on bug fixes (25%) and other work (67%), modifying 15 files with a total of +476/-304 lines.\", \"2025-05-14T07:28:22.871Z\"]" }