{
  "ai-news": {
    "elizaos": {
      "discord_md_last_3_days": [
        {
          "filename": "2025-04-29.md",
          "content": "# elizaOS Discord - 2025-04-29\n\n## Overall Discussion Highlights\n\n### ElizaOS Development\n- **ElizaOS v2 Progress**: Shaw mentioned that ElizaOS v2 with multi-agent capabilities will be wrapped up in the next couple of weeks.\n- **Technical Challenges**: Several users reported issues with the installation process, model compatibility, and API integration.\n- **RAM Limitations**: Users discussed hardware constraints when running local models, particularly that LLAMA 3 8B requires 20+ GB of VRAM.\n- **Node.js Compatibility**: Issues were reported with dynamic requires not being supported in Node.js 23+.\n- **Integration Options**: Discussions about integrating ElizaOS with other frontends, with references to agent API endpoints in the agent.ts file.\n\n### Auto.fun Platform\n- **Token Launches**: Several partner projects were launched through Auto.fun, including FightFi, SQUID by Allora Network, with discussions about upcoming launches like xfractal.\n- **Platform Issues**: Users reported problems with DexScreener not updating for some launches (FightAlgo and FightBrawl), causing loss of momentum.\n- **UI Improvements**: The platform team implemented timeframe options for charts during this period.\n- **LP Issues**: Some users experienced incorrect token amounts when purchasing through liquidity pools.\n- **Branding Challenges**: Discussions about consolidating ai16z (token) and ElizaOS (platform) under a single name for better brand recognition.\n\n### Community Projects\n- **Mental Health App**: Cliff shared details about a mental health application built on ElizaOS, featuring a mobile app that works with a smart ring to track physical activities and mood, with versions for both Android and iOS (iOS approval pending).\n- **OpenRouter Integration**: Jin shared positive feedback about using OpenRouter's web search feature to enhance content for elizaOS partners.\n- **Exchange Listings**: Bithumb exchange listed ai16z, according to community member Avanc.\n\n### Market Discussions\n- **ELI5 Token**: Community members discussed price targets between $10-50 million market cap by end of Q2, with some suggesting a more ambitious $30M target within the week.\n- **CEX Listings**: Brief discussion about potential centralized exchange listings for Degenai, with the note that such information is typically under NDAs.\n\n## Key Questions & Answers\n\n### Technical\n- **Q**: How to run local models to test Eliza when hitting RAM limits?  \n  **A**: \"Your macbook doesn't have the hardware capability to run the model you're using. Either quantize it, use a smaller model or use a cloud server.\" (answered by starlord)\n\n- **Q**: How to integrate Eliza AI framework to another chatting frontend demo?  \n  **A**: \"You can take reference of all the agents API endpoints from the agent.ts file.\" (answered by elldee)\n\n- **Q**: Can I adjust the supply of the tokens when creating?  \n  **A**: \"Token supply is fixed at 1 billion.\" (answered by ben)\n\n### Platform & Community\n- **Q**: How do you get verified (green check)?  \n  **A**: \"Verified are projects we are confident are legitimate agent builders.\" (answered by Kenk)\n\n- **Q**: What are the profile \"Points\" for?  \n  **A**: \"More will be revealed with points shortly.\" (answered by Kenk)\n\n- **Q**: Will image uploads be supported soon in AI Create?  \n  **A**: \"Yep, more features will be added to AI create over time.\" (answered by Kenk)\n\n- **Q**: Is there an actual plan for auto.fun's marketing?  \n  **A**: \"The head of marketing was in Spain with power/internet issues, but the team is working to improve engagement.\" (answered by whobody and eskender.eth)\n\n- **Q**: Price target for eli?  \n  **A**: \"Compared to many other AI agents, I think $10-50 mil mcap is doable before end of Q2. Long term, it depends on utility, community, mind share.\" (answered by MDMnvest)\n\n- **Q**: What's the status on consolidating ai16z and elizaOS under the same ticker?  \n  **A**: \"The team needs daos.fun to enable these changes and currently can't make them.\" (answered by Kenk)\n\n- **Q**: Were the partner projects launched on auto.fun specially chosen or did they apply on their own?  \n  **A**: \"Both - the team reached out to potential partnerships weeks ago while still building.\" (answered by jasyn_bjorn)\n\n- **Q**: Does Degenai have any listing plan on the cex?  \n  **A**: \"Most CEX listings are under NDA and can't be discussed.\" (answered by Odilitime)\n\n## Community Help & Collaboration\n\n1. **Model Compatibility Assistance**\n   - **Helper**: starlord\n   - **Helpee**: uedersonferreira\n   - **Context**: RAM limitations when running local models\n   - **Resolution**: Advised to quantize model, use smaller model, or use cloud server\n\n2. **Project Sharing Guidance**\n   - **Helper**: Kenk\n   - **Helpee**: Cliff ツ\n   - **Context**: Cliff wanted to know where to share his ElizaOS-based mental health project\n   - **Resolution**: Kenk shared a link to sign up for weekly demos (https://tally.so/r/nrYKXR)\n\n3. **New Developer Introduction**\n   - **Helper**: Osint (aka not_a_dev_ai)\n   - **Helpee**: BigBoss\n   - **Context**: Introducing a new developer to the community\n   - **Resolution**: Osint introduced BigBoss to the community, shared his credentials, and tipped him 30 ai16z tokens\n\n4. **Exchange Listing Information**\n   - **Helper**: Avanc\n   - **Helpee**: Multiple users\n   - **Context**: Sharing news about Bithumb exchange listing\n   - **Resolution**: Informed the community about ai16z being listed on Korea's second largest exchange\n\n5. **Integration Support**\n   - **Helper**: elldee\n   - **Helpee**: elldee (self-help shared with community)\n   - **Context**: Integrating Eliza AI framework with another frontend\n   - **Resolution**: Shared GitHub reference to agent API endpoints file\n\n## Action Items\n\n### Technical\n1. **Complete ElizaOS v2 with multi-agent capabilities** (Mentioned by shaw)\n2. **Improve auto.fun UI/UX for better mobile compatibility** (Mentioned by shaw)\n3. **Add \"ElizaOS Inside\" branding to auto.fun** (Mentioned by DorianD)\n4. **Create a staking mechanism for ai16z on auto.fun** (Mentioned by Spyros)\n5. **Investigate \"World not found for worldId null\" error** (Mentioned by elldee)\n6. **Fix Twitter client integration error (Maximum call stack size exceeded)** (Mentioned by elldee)\n7. **Resolve dynamic require of \"util\" not supported in Node.js 23+** (Mentioned by orayo)\n8. **Address memory issues causing crashes in GUI when getting responses** (Mentioned by elldee)\n9. **Resolve LP issue for Quill token** (Mentioned by fen sama)\n10. **Implement timeframe options for charts** (Mentioned by Simon | PEPELIZA creatooor 🐸)\n11. **Build a mental health infrastructure with AI therapist/coach functionality on ElizaOS** (Mentioned by Cliff ツ)\n12. **Integration of OpenRouter web search API to enrich elizaOS partner pages** (Mentioned by jin)\n13. **Improve DexScreener integration for token launches** (Mentioned by ryanthelad)\n14. **Investigate why OTTO and DOT lost verification status** (Mentioned by MDMnvest)\n\n### Documentation\n1. **Create guide for integrating ElizaOS with external frontends** (Mentioned by elldee)\n2. **Document hardware requirements for running different models locally** (Mentioned by elldee)\n3. **Improve explanation of how auto.fun agents differ from other bots** (Mentioned by 찌 G 跻 じ PrudentSpartan)\n4. **Create clearer documentation about the relationship between ai16z, ElizaOS, and auto.fun** (Mentioned by DorianD)\n5. **Clarify token minting process and visibility in wallets** (Mentioned by Skullcross)\n6. **Clarify token verification process** (Mentioned by Simon | PEPELIZA creatooor 🐸)\n7. **Explain profile points system** (Mentioned by Simon | PEPELIZA creatooor 🐸)\n\n### Feature\n1. **Implement token swap from ai16z to a simpler ticker like \"E\" or \"Eliza\"** (Mentioned by DorianD and Spyros)\n2. **Create an AI agent on Twitter that aggregates community feedback** (Mentioned by vincentpaul)\n3. **Integrate auto.fun with Hyperfy for 3D virtual environments** (Mentioned by Odilitime)\n4. **Implement AI safety tools/guardrails against prompt injections** (Mentioned by elldee)\n5. **Develop Deepseek plugin for Eliza v2** (Mentioned by elldee)\n6. **Improve compatibility with McP plugin for Notion** (Mentioned by Stan ⚡)\n7. **Add image upload support to AI Create** (Mentioned by Simon | PEPELIZA creatooor 🐸)\n8. **Support adjustable token supply** (Mentioned by Tocheee)\n9. **Address launch notification system** (Mentioned by anon)\n10. **Weekly demos for builders to share their projects** (Mentioned by Kenk)"
        }
      ],
      "dev_md_last_3_days": [
        {
          "filename": "2025-04-29.md",
          "content": "# elizaOS Development Discord - 2025-04-29\n\n## Overall Discussion Highlights\n\n### Plugin Integration & Configuration\n- Multiple users worked through issues with specific plugins including Twitter and Fleek MCP\n- Twitter plugin integration required explicit addition via CLI command: `elizaos plugins add @elizaos/plugin-twitter`\n- EVM integration challenges were discussed, particularly around ETH to USDC swaps on mainnet\n- Fleek MCP Plugin issues were resolved by properly specifying tool calls\n\n### LLM Provider Configuration\n- Significant discussion around configuring Gemini as an alternative LLM provider\n- Environment variable setup similar to OpenAI but with Gemini-specific endpoint URLs\n- Several users shared configuration attempts and troubleshooting steps\n\n### Technical Demonstrations\n- Live demonstration of Unreal Engine 5.5 integration with ElizaOS\n- The demo featured market analysis capabilities and Twitch client functionality\n- Discussion about using OpenRouter's web search feature to enhance ElizaOS partner pages\n\n### Agent Development\n- File structure for agent configuration was shared in the agent-dev-school channel\n- Key files discussed: config.yaml, character.yaml, and secrets.env\n\n## Key Questions & Answers\n\n**Q: How can I use Gemini as my LLM provider?** (asked by FaultyCarry)  \n**A:** Configure environment variables similar to OpenAI with the correct Gemini endpoint URL (answered by sayonara)\n\n**Q: When I want to swap ETH to USDC on mainnet using plugin-evm, this error happens. What else do I need?** (asked by OpsDev | Onyx)  \n**A:** You need to configure EVM_CHAINS in your .env file (answered by sam-developer)\n\n**Q: Why is my agent not tweeting despite adding Twitter credentials?** (asked by FaultyCarry)  \n**A:** You need to explicitly add the Twitter plugin with \"elizaos plugins add @elizaos/plugin-twitter\" (answered by sam-developer)\n\n## Community Help & Collaboration\n\n1. **Twitter Plugin Integration**\n   - **Helper:** sam-developer\n   - **Helpee:** FaultyCarry\n   - **Context:** Agent not tweeting despite Twitter credentials in .env\n   - **Resolution:** Instructed to add Twitter plugin explicitly with CLI command\n\n2. **EVM Configuration Support**\n   - **Helper:** sam-developer\n   - **Helpee:** OpsDev | Onyx\n   - **Context:** ETH to USDC swap failing on mainnet\n   - **Resolution:** Suggested adding EVM_CHAINS configuration to .env file\n\n3. **Gemini LLM Integration**\n   - **Helper:** sayonara\n   - **Helpee:** FaultyCarry\n   - **Context:** Configuring Gemini as LLM provider\n   - **Resolution:** Provided correct environment variable configuration for Gemini integration\n\n4. **Fleek MCP Plugin Troubleshooting**\n   - **Helper:** Scooter\n   - **Helpee:** Mel G\n   - **Context:** Issues with Fleek MCP Plugin\n   - **Resolution:** Scooter mentioned the need to specify tool calls, which resolved their issue\n\n## Action Items\n\n### Technical\n- Remove environment limitations for multi-room chat in GUI (Mentioned by: shaw)\n- Fix Gemini integration with ElizaOS to resolve configuration issues (Mentioned by: FaultyCarry)\n- Improve EVM plugin error handling with better error messages when configuration is incomplete (Mentioned by: OpsDev | Onyx)\n\n### Feature\n- Add support for posting to X communities to enable agents to post to communities on X platform (Mentioned by: Jon)\n- Enhance OpenRouter web search integration for partner pages (Mentioned by: multiple users)\n\n### Documentation\n- Create comprehensive guide for LLM provider configuration, including setup for different providers like Gemini (Mentioned by: sayonara)\n- Document proper plugin installation and configuration steps for common plugins (Twitter, EVM, Fleek MCP)\n- Develop standardized agent configuration templates with examples of config.yaml, character.yaml, and secrets.env"
        }
      ]
    }
  },
  "github": {
    "summaries": {
      "week": [
        {
          "filename": "2025-04-27.md",
          "content": "# ElizaOS Weekly Update (Week of Apr 27, 2025)\n\n## OVERVIEW\nThis week saw significant improvements to the ElizaOS framework with a focus on enhancing developer experience, fixing critical bugs, and improving plugin functionality. Key achievements include scopable knowledge implementation, Discord plugin enhancements, and comprehensive CLI command updates.\n\n## PROJECT METRICS\n- PRs: 29 merged PR's, 31 new PRs\n- Issues: 0 new issues, 0 closed issues\n- Unique Contributors: 23\n- Code Changes: +6059/-21763 lines across 140 files\n- Total Commits: 92\n- Most Active Contributors: wtfsayo, lalalune, 0xbbjoker, tcm390, samarth30\n\n## TOP ISSUES\n\n### Plugin Integration Challenges\n- Several issues related to plugin functionality were addressed, particularly with Discord, Anthropic, and Twitter integrations\n- Error handling improvements were needed for various edge cases, including disk space limitations\n\n### Developer Experience Friction\n- CLI command instructions required updates to improve clarity and usability\n- Documentation links and image paths needed fixing to ensure proper resource accessibility\n- Environment setup and configuration issues in Docker containers needed resolution\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Enhanced Plugin Functionality\n- Added typing indicator support in Discord plugin [#4364](https://github.com/elizaos/eliza/pull/4364)\n- Implemented API key validation for Anthropic plugin model calls [#4383](https://github.com/elizaos/eliza/pull/4383)\n- Fixed Discord plugin error handling when services are missing [#4375](https://github.com/elizaos/eliza/pull/4375)\n- Added model/plugin name logging when models are used [#4394](https://github.com/elizaos/eliza/pull/4394)\n\n### Improved Developer Experience\n- Implemented scopable knowledge functionality [#4390](https://github.com/elizaos/eliza/pull/4390)\n- Updated ElizaOS create command instructions [#4381](https://github.com/elizaos/eliza/pull/4381)\n- Added automatic rebuild of core and plugin-bootstrap in monorepo context [#4388](https://github.com/elizaos/eliza/pull/4388)\n- Added .env.example in project-starter for easier configuration [#4387](https://github.com/elizaos/eliza/pull/4387)\n- Fixed ESM type declarations in Core [#4341](https://github.com/elizaos/eliza/pull/4341)\n- Updated documentation with improved quick start and CLI commands [#4379](https://github.com/elizaos/eliza/pull/4379)\n\n### Infrastructure and Maintenance\n- Fixed Postgres database issues in Docker containers [#4363](https://github.com/elizaos/eliza/pull/4363)\n- Improved error handling for disk space limitations [#4389](https://github.com/elizaos/eliza/pull/4389)\n- Fixed agent deletion functionality [#4395](https://github.com/elizaos/eliza/pull/4395)\n- Removed plugin-evm from monorepo [#4386](https://github.com/elizaos/eliza/pull/4386), [#4399](https://github.com/elizaos/eliza/pull/4399)\n- Enhanced UI with cleaner design and minor improvements [#4393](https://github.com/elizaos/eliza/pull/4393)"
        }
      ],
      "month": [
        {
          "filename": "2025-04-01.md",
          "content": "# ElizaOS Monthly Update (April 2025)\n\n## OVERVIEW\nApril saw significant enhancements to ElizaOS with major improvements to the CLI, GUI, and plugin ecosystem. Key achievements include expanded AI model provider integrations, enhanced messaging capabilities, improved TTS functionality, and substantial fixes to core components and plugins.\n\n## PROJECT METRICS\n- PRs: 195 merged PR's, 232 new PRs\n- Issues: 43 new issues, 35 closed issues\n- Unique Contributors: 88\n- Code Changes: +55467/-37251 lines across 489 files\n- Total Commits: 828\n- Most Active Contributors: wtfsayo, tcm390, 0xbbjoker, Samarthsinghal28, HarshModi2005\n\n## TOP ISSUES\n\n### CLI Usability and Consistency\n- Command inconsistencies between v1 and v2\n- Installation and update workflow issues\n- Project creation and agent management challenges\n\n### Plugin Management\n- Plugin installation priority ordering issues\n- Dynamic loading and versioning problems\n- Plugin dependency conflicts\n\n### AI Model Integration\n- JSON parsing errors with Anthropic and OpenAI responses\n- Model validation and authentication issues\n- Embedding model selection and configuration\n\n### Database and Transaction Handling\n- Transaction deadlocks in database operations\n- Migration issues with PgLite\n- Entity relationship inconsistencies\n\n### Messaging and Communication\n- Duplicate message creation\n- Twitter interaction failures\n- Telegram data synchronization problems\n\n### User Interface\n- Knowledge manager scroll issues\n- Missing UI components after merge conflicts\n- Inconsistent character creation workflow\n\n### Performance and Resource Management\n- Disk space management and error handling\n- Memory leaks and caching issues\n- Runtime initialization sequence problems\n\n### Documentation and Onboarding\n- Inconsistent or outdated CLI documentation\n- Missing environment configuration examples\n- Broken documentation links\n\n## KEY TECHNICAL DEVELOPMENTS\n\n### Enhanced AI Model Provider Ecosystem\n- Added Kluster AI as a model provider [#3938](https://github.com/elizaos/eliza/pull/3938)\n- Added Mem0 as AI SDK Provider [#3927](https://github.com/elizaos/eliza/pull/3927)\n- Improved OpenAI plugin with ability to choose embedding models [#4140](https://github.com/elizaos/eliza/pull/4140)\n- Added model/plugin name logging when model is used [#4394](https://github.com/elizaos/eliza/pull/4394)\n\n### Voice and Speech Capabilities\n- Implemented OpenAI TTS functionality [#4255](https://github.com/elizaos/eliza/pull/4255)\n- Added testing for OpenAI TTS [#4259](https://github.com/elizaos/eliza/pull/4259)\n- Fixed speech-to-text transcription issues [#4236](https://github.com/elizaos/eliza/pull/4236)\n- Fixed OpenAI STT functionality [#4329](https://github.com/elizaos/eliza/pull/4329)\n\n### CLI Improvements\n- Added update-cli command for easier updates [#4170](https://github.com/elizaos/eliza/pull/4170)\n- Enhanced CLI update and plugin installation with package manager [#4176](https://github.com/elizaos/eliza/pull/4176)\n- Implemented CLI test suite [#4301](https://github.com/elizaos/eliza/pull/4301)\n- Updated ElizaOS create command instructions [#4381](https://github.com/elizaos/eliza/pull/4381)\n\n### Messaging and Interaction Enhancements\n- Added message API for improved communication [#4247](https://github.com/elizaos/eliza/pull/4247)\n- Added message buttons for interactive responses [#4187](https://github.com/elizaos/eliza/pull/4187)\n- Improved Reply Action to use pre-generated responses [#4213](https://github.com/elizaos/eliza/pull/4213)\n- Added typing indicators to Telegram [#4280](https://github.com/elizaos/eliza/pull/4280) and Discord [#4364](https://github.com/elizaos/eliza/pull/4364)\n\n### Plugin System Improvements\n- Better plugin installation management [#4177](https://github.com/elizaos/eliza/pull/4177)\n- Added test coverage for plugin-bootstrap [#4173](https://github.com/elizaos/eliza/pull/4173)\n- Enabled path params routes for plugins [#4335](https://github.com/elizaos/eliza/pull/4335)\n- Fixed plugin install priority order [#4256](https://github.com/elizaos/eliza/pull/4256)\n\n### GUI Enhancements\n- Added support for importing JSON to create or update agents [#4270](https://github.com/elizaos/eliza/pull/4270)\n- Enhanced GUI with various improvements [#4300](https://github.com/elizaos/eliza/pull/4300)\n- Added confirmation dialog for delete group [#4310](https://github.com/elizaos/eliza/pull/4310)\n- Implemented onboarding tour [#4293](https://github.com/elizaos/eliza/pull/4293)\n\n### Social Media Integration\n- Enhanced Telegram logic with middlewares [#4125](https://github.com/elizaos/eliza/pull/4125)\n- Added Telegram community manager [#4134](https://github.com/elizaos/eliza/pull/4134)\n- Improved Twitter plugin with support for long tweets [#4291](https://github.com/elizaos/eliza/pull/4291)\n- Added deleteTweet() functionality [#4320](https://github.com/elizaos/eliza/pull/4320)\n\n### Knowledge and Memory Management\n- Implemented scopable knowledge [#4390](https://github.com/elizaos/eliza/pull/4390)\n- Fixed knowledge types [#4243](https://github.com/elizaos/eliza/pull/4243)\n- Replaced fastembed with local embedding model [#4205](https://github.com/elizaos/eliza/pull/4205)\n- Fixed cache interaction cursor and duplicate memory creation [#4155](https://github.com/elizaos/eliza/pull/4155)\n\n### Logging and Monitoring\n- Added OpenAI model usage events [#4230](https://github.com/elizaos/eliza/pull/4230)\n- Restored support for Cloudflare LLM logging/tracking [#4354](https://github.com/elizaos/eliza/pull/4354)\n- Added docstrings to cloudflare-logging [#4355](https://github.com/elizaos/eliza/pull/4355)\n- Improved logging for transcription models [#4283](https://github.com/elizaos/eliza/pull/4283)\n\n## SUMMARY\nApril 2025 was a productive month for ElizaOS with significant improvements across the platform. The team expanded AI model provider integrations, enhanced messaging capabilities, improved voice and speech features, and fixed numerous issues in the core system and plugins. The CLI and GUI received substantial upgrades, making the platform more user-friendly and robust. These developments have strengthened ElizaOS's position as a versatile, modular AI agent framework capable of operating across diverse ecosystems."
        }
      ]
    }
  }
}