{ "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-01-15", "date": 1736899200, "stats": { "totalMessages": 184, "totalUsers": 55 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around technical issues and development of the Eliza platform. Users are experiencing various problems with the latest versions (v0.1.8 and v0.1.8+build.1), particularly with the Telegram client, Twitter integration, and RAG (Retrieval-Augmented Generation) functionality. A user named \"Founder\" reported a Telegram bot connection issue with ETIMEDOUT errors despite being able to curl the bot successfully. Several users discussed the RAG knowledge system, with questions about enabling it in character files and documentation. The Supabase adapter was mentioned as working with RAG functionality after some fixes. There were also discussions about Twitter client issues, with users experiencing problems with tweet processing and login challenges. Some developers are working on ARM64 compatibility, with Mike D. reporting success in getting Eliza running on ARM64. There were also questions about the availability of V2 core code and the status of eliza.gg, which appears to be down.\n\n## 2. FAQ\nQ: Anyone else having issues with the client since the 1.8+ update? (asked by 4n7m4n) A: Unanswered\nQ: Can I increase the threshold in the knowledge folder system to keep my agent from hallucinating? (asked by Mad) A: Unanswered\nQ: Is there any discord bot similar to the telegram bot for analyzing contract addresses? (asked by neo) A: Unanswered\nQ: Where can we find v2 core code? (asked by Mike D.) A: I believe it will be a V2 branch in the eliza repo (answered by Odilitime)\nQ: What's the latest stable version of the eliza repo? (asked by ICJR) A: v0.1.8+build.1 should be more stable (answered by Odilitime)\nQ: Where is the code for the chat client? (asked by 4n7m4n) A: in client/ (answered by Odilitime)\nQ: When does the knowledge get written to the DB? (asked by 4n7m4n) A: Unanswered\nQ: How to debug in plugin development? (asked by erylemba) A: Unanswered\nQ: How to use the RAG functionality in Eliza? (asked by 4n7m4n) A: You add it under secrets, check the documentation in the character file (answered by Mad)\nQ: Is there a way to retrieve retweeters from a given tweet? (asked by SlKzᵍᵐ) A: I would start by observing network requests in browser twitter client (answered by sayonara)\n\n## 3. Help Interactions\nHelper: ꧁Ninja_Dev꧂ | Helpee: 4n7m4n | Context: Enabling RAG knowledge in character settings | Resolution: Ninja_Dev confirmed it needs to be enabled in character settings\nHelper: Mad | Helpee: 4n7m4n | Context: Finding RAG documentation | Resolution: Mad shared a GitHub PR link (https://github.com/elizaOS/eliza/pull/1620) with the needed information\nHelper: Odilitime | Helpee: ICJR | Context: Confusion about stable versions | Resolution: Clarified that v0.1.8+build.1 is more stable than v0.1.8\nHelper: Odilitime | Helpee: 4n7m4n | Context: Looking for chat client code | Resolution: Informed that it's located in the client/ directory\nHelper: ꧁Ninja_Dev꧂ | Helpee: 4n7m4n | Context: Question about knowledge processing behavior | Resolution: Explained that files are only processed once unless they change\n\n## 4. Action Items\nType: Technical | Description: Fix Telegram bot connection issues with ETIMEDOUT errors | Mentioned By: Founder\nType: Technical | Description: Resolve Twitter client issues with tweet processing | Mentioned By: Beats\nType: Technical | Description: Fix Supabase adapter issues with memories | Mentioned By: 4n7m4n\nType: Technical | Description: Investigate why knowledge keeps being recreated on startup | Mentioned By: 4n7m4n\nType: Technical | Description: Fix eliza.gg service which appears to be down | Mentioned By: imtnf, cauerochinha, Kenzo\nType: Technical | Description: Resolve Twitter login issue with arkose challenge | Mentioned By: M I A M I\nType: Feature | Description: Develop a Zapper client/plugin | Mentioned By: KeyesCode.eth\nType: Feature | Description: Create Quick Intel plugin | Mentioned By: ꧁Ninja_Dev꧂\nType: Documentation | Description: Improve RAG functionality documentation | Mentioned By: 4n7m4n\nType: Documentation | Description: Document how to debug plugin development | Mentioned By: erylemba", "messageCount": 110, "userCount": 38 }, { "channelId": "1324098367416172665", "channelName": "📮｜feedback", "summary": "The chat segment is extremely brief, containing only a single message from Cesar Rodriguez. He mentions an issue with the size of node modules, which has reached 3GB. He identifies the cause as llama cpp and two versions of onnxruntime that are included due to different versions of the transformers package. This suggests a discussion about package dependencies and disk space optimization in a Node.js project that involves machine learning libraries.", "messageCount": 1, "userCount": 1 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Discord Chat Analysis for 🤖｜agent-dev-school\n\n## 1. Summary\nThe chat segment primarily revolves around discussions about Eliza OS and its version 2. Users are inquiring about accessing the new v2 core code, determining stable branches for development, and understanding the process for contributing plugins. There appears to be some confusion about the location of the v2 codebase, with Cesar Rodriguez clarifying that it's in a different private repository. A user named Mike D. shared links to what might be related to v2, including a GitHub pull request and a Twitter post. Another user asked about Telegram support in v2, but received no definitive answer. There was also a question about using goals in Eliza, referencing the goals.ts file in the core package. Additionally, a user named nusko asked about character knowledge persistence when updating character.json files, wondering if memory needs to be wiped after updates. CryptoFede shared an announcement about an AI agent founder school program.\n\n## 2. FAQ\nQ: Where can we find the new v2 core code? (asked by Mike D.) A: It's in a private different repo, so that's not v2 (answered by Cesar Rodriguez)\nQ: What's the most stable branch to build off of right now? Main? (asked by saccharinedreams) A: Unanswered\nQ: Which repo should I open a pull request to for my plugin to be available in the Eliza OS? (asked by Samidha) A: Unanswered\nQ: Does v2 have support for telegram? (asked by shmaven) A: Unanswered\nQ: Are there any resources for using goals? (asked by eric) A: Unanswered\nQ: Do I have to wipe her memory and restart whenever I update my .json file or will she keep the old and the new stuff I add? (asked by nusko) A: Unanswered\n\n## 3. Help Interactions\nHelper: Cesar Rodriguez | Helpee: Samidha | Context: Asking where to submit plugin for Eliza OS | Resolution: Shared GitHub repository link (https://github.com/elizaOS/eliza)\nHelper: sirprincess | Helpee: Samidha | Context: Developing a plugin using eliza-plugin-starter repo | Resolution: Suggested looking at eliza-starter repo as a good example\n\n## 4. Action Items\nTechnical: Investigate how character knowledge updates are handled when modifying character.json files | Description: Determine if memory needs to be wiped after updates | Mentioned By: nusko\nDocumentation: Create resources for using goals functionality | Description: Documentation needed for goals.ts in the core package | Mentioned By: eric\nTechnical: Clarify the location and access to Eliza v2 codebase | Description: Multiple users confused about where to find v2 code | Mentioned By: Mike D., Cesar Rodriguez\nDocumentation: Provide guidance on which branch is most stable for development | Description: Clarify if main branch is recommended | Mentioned By: saccharinedreams\nDocumentation: Document process for contributing plugins to Eliza OS | Description: Clear instructions for submitting plugins | Mentioned By: Samidha", "messageCount": 18, "userCount": 12 }, { "channelId": "1323745969115893780", "channelName": "📥｜pull-requests", "summary": "Solana plugin improvements: A user (suns) enhanced the legacy Solana plugin to properly handle native SOL and SPL transfers, submitting PR #2340. There was confusion about two Solana plugins existing simultaneously (plugin-solana and plugin-solana-agentkit).", "messageCount": 54, "userCount": 12 }, { "channelId": "1327493511406293016", "channelName": "🎤｜plug-your-projects", "summary": "Type: Technical | Description: Integration of Token Against Humanity components with ELIZA framework | Mentioned By: Lord BGR", "messageCount": 1, "userCount": 1 } ] }