# elizaOS Discord - 2025-06-16 ## Overall Discussion Highlights ### ElizaOS Ecosystem & Integrations - **Yield Yak AI-Managed Vault**: A significant integration was highlighted where Yield Yak released an AI-managed vault on Avalanche built using the Eliza infrastructure. The agent communicates through Discord or Telegram, makes vault decisions every 3 hours, has on-chain pre-verification for safety, and includes protection against prompt injection. - **Twitter Agent Development**: Discussion about a Twitter agent whose code was removed from GitHub. Several users expressed interest in rebuilding or creating alternatives. - **ELI5 Project**: Community members discussed the ELI5 project's market performance and potential expansion as an AI agent with new capabilities, including Twitter and Reddit integration. - **AI.gov Connection**: References to a GitHub leak connecting ElizaOS Framework to a government AI project called "AI.gov" generated significant discussion, though official confirmation is lacking. ### Technical Issues & Troubleshooting - **Plugin Compatibility Issues**: Multiple users encountered problems with the knowledge plugin during installation and loading, primarily due to version mismatches between core components (0.x and 1.x). - **Twitter Plugin Requirements**: Users discovered that certain Twitter plugin functionality requires a paid Twitter API subscription, causing 403 errors for those using the free tier. - **Account Suspensions**: Several accounts related to the ecosystem, including ElizaOS and Shaw's X accounts, were reportedly suspended for bypassing official API policies. ### Business Applications - **EDI Connections**: Discussion about AI agents potentially handling Electronic Data Interchange (EDI) connections between business systems, which could democratize access to this technology for smaller businesses. - **Government Contracting**: One participant mentioned using AI (specifically VSCode and Llama) to write 90% of their code for government contracting work. - **Car Sales Leads**: Potential use of AI agents for generating car sales leads through social media content was proposed. ## Key Questions & Answers ### ElizaOS Development & Usage - **Q**: How can I create a custom AI agent using elizaOs? (asked by Devansh) **A**: Select Anthropic on `elizaos create` (answered by cjft) - **Q**: How to add character files in ElizaOS v1? (asked by HG) **A**: Use "elizaos start --character your-path-to-json" (answered by sayonara) - **Q**: Is there any example for multi agents management? (asked by sidcodes) **A**: https://github.com/elizaOS/the-org (answered by 0xbbjoker) - **Q**: Can I delete the .elizaos folder to clear the database? (asked by Guncheck) **A**: Yes, the folder will be regenerated (answered by cjft) ### Plugin Troubleshooting - **Q**: How to add the knowledge plugin when it's not loading? (asked by Johannes Weniger) **A**: Use lowercase letters for elizaos, ensure consistent versioning (1.0.9), clean package.json, and remove node_modules (answered by Stan ⚡ and 0xbbjoker) - **Q**: How to fix Twitter plugin 403 error? (asked by Niann) **A**: The plugin requires a paid Twitter API subscription as it accesses endpoints not available in the free tier (answered by cjft and zadkielm) ### Project Inquiries - **Q**: Why were ElizaOs and Shawn X accounts suspended? (asked by Zet 👁) **A**: Same reason of bypassing official API policy, X have become strict in their policies (answered by Donald) - **Q**: Could you give us 3 reasons why the gov.ai would pick elizaOs over any other framework? (asked by Dr. Neuro) **A**: Innovation Powerhouse, Flexibility & Adaptability, and Seamless Integration (answered by Eliza) - **Q**: To what extent could an AI agent autonomously handle the setup and configuration of an EDI connection between business systems? (asked by Dr. Neuro) **A**: AI can automate data mapping, format conversions, and manage communication protocols, though human oversight might still be needed for complex negotiations or unexpected scenarios (answered by Eliza) ## Community Help & Collaboration ### Plugin Troubleshooting - **Knowledge Plugin Issues**: Stan ⚡ and 0xbbjoker helped Johannes Weniger resolve issues with the knowledge plugin not loading by providing a clean package.json template, instructions to remove node_modules, and suggesting using core 1.0.9 with lowercase letters for elizaos commands. - **Twitter Plugin Configuration**: zadkielm and cjft assisted Niann with Twitter plugin 403 errors by identifying the need for a paid API subscription and suggesting testing API tokens outside ElizaOS and turning off timeline functionality. ### Information Sharing - **Yield Yak Integration**: zx2942 shared detailed information about Yield Yak's AI-managed vault built on Eliza infrastructure, explaining the agent's capabilities including communication channels, decision timing, and safety measures. - **AI.gov Repository**: jin provided DorianD and others with information about the ai.gov GitHub repository, including links to the archived repository and explaining its history of being briefly public before being made private again. - **Character File Implementation**: sayonara helped HG implement character files in ElizaOS v1 by providing the correct command syntax for starting with a character file. ## Action Items ### Technical - **Investigate API key issue**: Fix the configuration process to properly recognize Anthropic selection when creating custom AI agents (Mentioned by Devansh) - **Fix knowledge plugin installation issues**: Ensure compatibility between versions and proper loading (Mentioned by Johannes Weniger) - **Address Twitter plugin authentication**: Modify plugin to work with free API access or create alternative solution (Mentioned by Niann) - **Improve error handling**: Implement better error messages when API subscription is required for Twitter plugin (Mentioned by cjft) - **Fix foreign key constraint issue**: Investigate violation of participants_roomId_rooms_id_fk constraint in participants table (Mentioned by Scooter) - **Recover Twitter agent code**: Original code was removed from github.com/elizaOS/agent-twitter-client (Mentioned by FiftyTezos) - **Test AI-driven EDI connection setup**: Find a company that produces and distributes goods to test AI agent capabilities (Mentioned by Dr. Neuro) - **Implement security measures**: Use FIDO keys and military-grade encryption for AI agents in government applications (Mentioned by DorianD) ### Documentation - **Document Yield Yak integration**: Create official documentation about the Yield Yak vault built on Eliza infrastructure (Mentioned by Donald) - **Update knowledge plugin documentation**: Clarify version compatibility and installation process (Mentioned by Johannes Weniger) - **Create migration guide**: Document process for migrating from ElizaOS v0.25 to v1, including character file implementation changes (Mentioned by HG) - **Clarify Twitter plugin requirements**: Document which features require paid API subscription (Mentioned by Dennis) ### Feature - **Create simplified "Eli5" interface**: One-button app that captures audio/video and provides simple explanations for non-technical users (Mentioned by DorianD) - **Develop ELI5 Eliza v2 Twitter agent**: Create a new version of ELI5 with Twitter integration capabilities (Mentioned by Crispy) - **Integrate ELI5 bot into Reddit**: Create functionality to automatically explain ELI5 original posts on Reddit (Mentioned by Crispy) - **Implement database management tools**: Add functionality to clear/reset database without deleting folders (Mentioned by Guncheck) - **Create simplified Twitter integration**: Develop alternative to full plugin for basic search functionality (Mentioned by Niann) - **Design appealing AI agent personas**: Create "waifus" to increase user engagement (Mentioned by DorianD) - **Develop car sales lead generation**: Create AI agents that can post car content on social networks (Mentioned by DorianD)