{
  "server": "elizaOS Development",
  "title": "elizaOS Development Discord - 2025-01-16",
  "date": 1736985600,
  "stats": {
    "totalMessages": 198,
    "totalUsers": 59
  },
  "categories": [
    {
      "channelId": "1320246527268098048",
      "channelName": "💬｜general",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around technical issues with Eliza, a framework for building AI agents. Key discussions include:\n\n- RAG (Retrieval-Augmented Generation) functionality implementation, with users seeking documentation and troubleshooting the feature. A PR for adapter-supabase with RAG capabilities was mentioned.\n- Plugin development, particularly the Quick Intel plugin that requires an API key from developer.quickintel.io.\n- Deployment issues where users experienced connection problems with the backend defaulting to localhost:3000, requiring configuration changes.\n- Twitter integration challenges, including login issues with Arkose challenges and X Spaces functionality errors related to ICE connection failures.\n- Knowledge system updates that simplify the process of adding information to agents.\n- Concerns about impersonation and a potentially unauthorized token launch using a team member's identity.\n- The eliza.gg service experienced downtime, affecting multiple users.\n\n## 2. FAQ\nQ: How to debug in plugin development? (asked by erylemba) A: Unanswered\nQ: How to use the RAG functionality in Eliza? Any documentation? (asked by 4n7m4n) A: Check https://github.com/elizaOS/eliza/pull/1620 (answered by Mad)\nQ: Will it keep adding the same knowledge to the RAG every time you startup Eliza? (asked by 4n7m4n) A: Nope, it won't reprocess it every time. Just once, unless the file changes. (answered by ꧁Ninja_Dev꧂)\nQ: Is there any example out there how to use rag or other features? (asked by platodev) A: Unanswered\nQ: After deploying an agent on the server, the page keeps showing \"Disconnected\". Where can the localhost address be modified? (asked by Leo) A: Look for base_url in client/src/lib/api.ts (answered by platodev)\nQ: Is anyone working on a Zapper client/plugin? (asked by KeyesCode.eth) A: Unanswered\nQ: How to make the agent run an action every 5 min? (asked by User) A: Unanswered\nQ: Is pdf text extraction for knowledge RAG setup? (asked by 4n7m4n) A: No, currently only TXT or MD files. (answered by ꧁Ninja_Dev꧂)\nQ: Does anyone know if the X Spaces feature is working? (asked by 0xn1c0) A: Unanswered\n\n## 3. Help Interactions\nHelper: Mad | Helpee: 4n7m4n | Context: Looking for RAG functionality documentation | Resolution: Provided link to GitHub PR with implementation details\nHelper: ꧁Ninja_Dev꧂ | Helpee: 4n7m4n | Context: Question about RAG reprocessing files on startup | Resolution: Explained that files are only processed once unless changed\nHelper: platodev | Helpee: Leo | Context: Deployment issue with backend connection | Resolution: Pointed to the location of base_url in the codebase\nHelper: Santi | Helpee: Leo | Context: Backend connection configuration | Resolution: Provided code snippet to update the BASE_URL variable\nHelper: ꧁Ninja_Dev꧂ | Helpee: Mad | Context: Setting up Quick Intel plugin API key | Resolution: Directed to check the profile section in the developer portal\n\n## 4. Action Items\nTechnical: Fix issue with adapter-supabase repeatedly processing the same files for RAG | Mentioned By: 4n7m4n\nTechnical: Implement PDF text extraction for knowledge RAG | Mentioned By: 4n7m4n\nTechnical: Fix X Spaces feature ICE connection failure | Mentioned By: 0xn1c0\nTechnical: Resolve agent-twitter-client login issues with Arkose challenge | Mentioned By: M I A M I\nTechnical: Fix eliza.gg service downtime | Mentioned By: multiple users\nTechnical: Implement functionality to remove documents from RAG database | Mentioned By: ꧁Ninja_Dev꧂\nTechnical: Fix client connection reliability to server | Mentioned By: platodev\nTechnical: Update BASE_URL configuration to handle port changes properly | Mentioned By: Santi\nFeature: Develop Zapper client/plugin | Mentioned By: KeyesCode.eth\nFeature: Create functionality for agents to run scheduled actions | Mentioned By: User\nDocumentation: Create comprehensive guide for RAG functionality | Mentioned By: 4n7m4n\nDocumentation: Provide examples of using tools with generateText | Mentioned By: Blocknaut",
      "messageCount": 128,
      "userCount": 37
    },
    {
      "channelId": "1327493511406293016",
      "channelName": "🎤｜plug-your-projects",
      "summary": "# Analysis of \"🎤｜plug-your-projects\" Channel\n\n## 1. Summary\nThe chat segment contains a single message from Lord BGR introducing Token Against Humanity ($TAH), a memecoin project that combines AI technology with community profit-sharing. The project features CC, described as a \"Rogue AI Agent\" with advanced voice capabilities that can autonomously engage on social platforms. The project includes the Legion Protocol framework and a profit-sharing model where 50% of revenue goes to token holders. The planned launch date is January 17, 2025. Lord BGR is seeking assistance with integrating parts of the project into the ELIZA framework and provided website, manifesto, documentation, and social media links for further information.\n\n## 2. FAQ\nNo questions were asked or answered in this chat segment.\n\n## 3. Help Interactions\nNo help interactions occurred in this chat segment.\n\n## 4. Action Items\nType: Technical | Description: Integration of Token Against Humanity project components with ELIZA framework | Mentioned By: Lord BGR",
      "messageCount": 1,
      "userCount": 1
    },
    {
      "channelId": "1324089429727514674",
      "channelName": "🤖｜agent-dev-school",
      "summary": "# Discord Chat Analysis for 🤖｜agent-dev-school\n\n## 1. Summary\nThe chat primarily revolves around ElizaOS framework questions and troubleshooting. Key technical discussions include:\n\n- Telegram integration with ElizaOS, with users seeking information about API tokens and implementation details\n- Character knowledge management in ElizaOS, specifically how to update knowledge in character.json files and the need to delete db.sqlite to refresh character knowledge\n- Goals functionality in ElizaOS, with users examining the codebase to understand implementation details\n- A user noted that the createGoal function exists in the codebase but appears unused, suggesting the feature might be under development\n- One user mentioned they would use phi data instead of ElizaOS for workflows as they felt the framework was too early for their specific needs\n- Resources were shared including Chinese development guides for ElizaOS\n\nThe discussions highlight that ElizaOS is still in development with some features potentially not fully implemented yet, but users appreciate its approach to agent development.\n\n## 2. FAQ\nQ: Does v2 have support for telegram? (asked by shmaven) A: It's in a private different repo, not v2 (answered by Cesar Rodriguez)\nQ: Are there any resources for using goals? (asked by eric) A: Looking at the goal evaluator in the bootstrap plugin is a good place to start (answered by User)\nQ: Do I have to wipe memory and restart whenever I update my character.json file? (asked by nusko) A: You need to delete db.sqlite from agent directory and rerun (answered by fiction)\nQ: How to obtain the API token for ElizaOS for Telegram Bot integration? (asked by Alise) A: First google hit: https://communalytic.org/tutorials/obtaining-telegram-api-key/ (answered by tehsoul)\n\n## 3. Help Interactions\nHelper: fiction | Helpee: nusko | Context: User needed to know how to refresh character knowledge after updating character.json | Resolution: Advised to delete db.sqlite from agent directory and rerun\nHelper: User | Helpee: eric | Context: User needed resources for using goals functionality in ElizaOS | Resolution: Provided GitHub links to relevant code and explained that the feature might still be under development\nHelper: tehsoul | Helpee: Alise | Context: User needed help obtaining Telegram API token for ElizaOS integration | Resolution: Provided a link to a tutorial for obtaining Telegram API keys\nHelper: m1hawk/风答 | Helpee: General audience | Context: Need for ElizaOS development resources | Resolution: Shared YouTube playlist with Chinese development guides for ElizaOS\n\n## 4. Action Items\nTechnical: Implement proper character knowledge updating without requiring db.sqlite deletion | Description: Current workflow requires deleting database file when updating character knowledge | Mentioned By: nusko\nTechnical: Complete goals functionality implementation | Description: The createGoal function exists but appears unused in the codebase | Mentioned By: User\nFeature: Add workflow capabilities to ElizaOS | Description: Framework needs better support for workflows | Mentioned By: eric\nFeature: Implement agents group thinking | Description: Add support for collaborative agent reasoning | Mentioned By: eric\nFeature: Add environment learning capabilities | Description: Improve agent's ability to learn from environment | Mentioned By: eric\nFeature: Improve goal setting functionality | Description: Make goal setting easier for users | Mentioned By: eric\nFeature: Add Python integration | Description: Integrate Python support into the framework | Mentioned By: eric\nFeature: Add scheduling capabilities | Description: Implement task scheduling for agents | Mentioned By: eric\nDocumentation: Create comprehensive guide for Telegram integration | Description: Users are struggling with Telegram bot setup | Mentioned By: Alise",
      "messageCount": 19,
      "userCount": 14
    },
    {
      "channelId": "1323745969115893780",
      "channelName": "📥｜pull-requests",
      "summary": "# Discord Channel Analysis: 📥｜pull-requests\n\n## 1. Summary\nThe channel primarily serves as a notification and discussion space for pull requests to the ElizaOS repository. Multiple PRs were shared, including improvements to Squid router throttle intervals (PR #2386), converting classes to interfaces for AgentRuntime injection (PR #2388), and a fix for image provider issues (PR #2430). Community members requested reviews for their contributions, with some expressing desire to have their work included in the upcoming 0.1.9 release. There were discussions about PR size guidelines for new plugins, with one contributor asking if their draft PR based on plugin-evm was appropriate for review. Several members mentioned using AI tools to assist with code reviews, with AIFlow.ML offering to help with reviews and suggesting tools like CodeRabbit to speed up the process. Odilitime expressed commitment to releasing version 0.1.9-alpha.1, while other members discussed integrating tools like Devin for development assistance and creating bots to connect Telegram with Linear for ticket tracking.\n\n## 2. FAQ\nQ: Is there a recommended max size of PR for new plugin based on plugin-evm? (asked by Bertux) A: Unanswered\nQ: Did you test with and without the supported image provider? (asked by AIFlow.ML @ ElizaOS) A: Yes (answered by tcm390)\nQ: Can I use some tool to speed up [reviews]? (asked by AIFlow.ML @ ElizaOS) A: Human + agent seems to work well (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: AIFlow.ML @ ElizaOS | Helpee: tcm390 | Context: Review of PR #2430 for image provider issue fix | Resolution: PR was approved after confirmation of testing\nHelper: AIFlow.ML @ ElizaOS | Helpee: Unknown | Context: Created PR #2434 to help with an unspecified issue | Resolution: Successfully created PR and later fixed conflicts\nHelper: Odilitime | Helpee: Unknown | Context: Guidance on PR readiness | Resolution: Advised to \"fix the conflicts and it's good to go\"\n\n## 4. Action Items\nTechnical: Release version 0.1.9-alpha.1 | Description: Complete the release process | Mentioned By: Odilitime\nTechnical: Review PR #2340 for repository integration | Description: Review requested multiple times | Mentioned By: suns\nTechnical: Create Telegram <=> Linear bot | Description: Bot to fetch Linear ticket data in Telegram | Mentioned By: Odilitime\nTechnical: Review PR #2154 for Livepeer LLM provider integration | Description: Adds Livepeer as LLM provider with free inference services | Mentioned By: DeFine\nTechnical: Review PR #2235 for potential inclusion in 0.1.9 | Description: Contributor wants inclusion in upcoming release | Mentioned By: jonathan\nTechnical: Review PR #2139 for Twilio plugin | Description: New version of Twilio plugin ready for feedback | Mentioned By: boolkeys\nTechnical: Review PR #2341 for new plugin based on plugin-evm | Description: Draft PR with multiple file changes | Mentioned By: Bertux",
      "messageCount": 45,
      "userCount": 15
    },
    {
      "channelId": "1324098367416172665",
      "channelName": "📮｜feedback",
      "summary": "# Analysis of Discord Channel \"📮｜feedback\"\n\n## 1. Summary\nThe chat segment contains feedback about the platform's documentation, technical challenges, and support issues. Users express frustration about information being scattered across videos rather than consolidated in documentation. There are specific concerns about understanding core system functionality, particularly regarding providers, plugins, and goals. One user mentions difficulty in getting technical support and responses to questions. Another user suggests using GitHub Copilot as a potential solution for finding information within repositories. There's also a brief mention of interest in connecting agents to Twitter DMs without using the official API. The conversation highlights gaps in documentation, challenges with TypeScript for Python developers, and the need for better technical support and communication channels.\n\n## 2. FAQ\nQ: Would it be possible to get an agent to respond to Twitter DMs without the official Twitter API? (asked by nusko) A: Unanswered\nQ: Does using GitHub Copilot help with finding specific information in repositories? (asked by Display Name) A: Unanswered\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: 0xn1c0 | Context: Complaint about lack of technical support and responsiveness | Resolution: Acknowledgment of need to be more present and mention of issues with \"the bridge\"\n\n## 4. Action Items\nType: Documentation | Description: Improve documentation on plugins to reduce reliance on video tutorials | Mentioned By: eric\nType: Documentation | Description: Provide more information about the core system, especially how/when agents select items and providers | Mentioned By: eric\nType: Documentation | Description: Clarify how providers work, especially for generating information from actions | Mentioned By: eric\nType: Feature | Description: Implement workflow and multi-agent orchestration capabilities | Mentioned By: eric\nType: Feature | Description: Improve TypeScript compatibility for Python developers or reduce boilerplate code | Mentioned By: eric\nType: Documentation | Description: Add documentation on how to use goals | Mentioned By: eric\nType: Documentation | Description: Document how to make the system learn from environment interactions | Mentioned By: eric\nType: Documentation | Description: Clarify how to feed back content information resulting from actions | Mentioned By: eric\nType: Technical | Description: Fix issues with \"the bridge\" | Mentioned By: Odilitime\nType: Feature | Description: Establish better technical support channels and DevRel position | Mentioned By: 0xn1c0",
      "messageCount": 5,
      "userCount": 5
    }
  ]
}