{ "server": "elizaOS Development", "title": "elizaOS Development Discord - 2025-03-30", "date": 1743292800, "stats": { "totalMessages": 92, "totalUsers": 23 }, "categories": [ { "channelId": "1320246527268098048", "channelName": "💬｜general", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around technical issues with ElizaOS, particularly regarding plugin import errors on Linux and macOS. Several users reported problems with module resolution in the CLI, with one user finding a workaround by replacing the @import with a hardcoded path to the module's index.js file. There were also discussions about running ElizaOS on WSL (Windows Subsystem for Linux). A user named Sashimikun promoted their GitHub-Chat product built on ElizaOS. Additionally, there were questions about RAG (Retrieval-Augmented Generation) usability, which had previously experienced issues. The chat also contained some off-topic discussions, including cryptocurrency-related conversations and potential scam attempts that were quickly identified by community members. One user inquired about pinning GitHub dependency versions in their project configuration.\n\n## 2. FAQ\nQ: Anyone got this to work on linux yet? I still get plugin import errors, no matter how I run the cli (asked by Tiki) A: Unanswered\nQ: What method to start it works for you? (asked by Tiki) A: Unanswered\nQ: I know RAG was having issues a month or so ago.... is there any update on RAG usability? (asked by Mr. Stark) A: Unanswered\nQ: Anyone know how to pin a version of the github dependency? (asked by DefiniteOptimist) A: Unanswered\nQ: what vector databases are peeps using these days? Is Pinecone a standard? (asked by Hidden Forces) A: pg-vector for me! (answered by DefiniteOptimist)\nQ: is anyone using Eliza to do airdrop farming? is that even possible? (asked by Samwise) A: Unanswered\n\n## 3. Help Interactions\nHelper: Tiki | Helpee: NnrbzZ | Context: Plugin import errors in ElizaOS | Resolution: Tiki shared a workaround by replacing @import with hardcoded path to index.js\nHelper: Veight | Helpee: ElizaBAO🌟 | Context: Warning about potential scam link | Resolution: Successfully warned user who then moved crypto to another wallet\nHelper: DefiniteOptimist | Helpee: Hidden Forces | Context: Question about vector databases | Resolution: Recommended pg-vector as an alternative to Pinecone\nHelper: Odilitime | Helpee: Yuto | Context: Confusion about which Discord server to use | Resolution: Provided the link to the ai16z Discord server\n\n## 4. Action Items\nTechnical: Fix plugin import resolution issues in the CLI | Description: Module imports failing on Linux/WSL/macOS | Mentioned By: Tiki\nTechnical: Investigate RAG usability issues | Description: Follow up on previously reported RAG problems | Mentioned By: Mr. Stark\nTechnical: Document GitHub dependency version pinning | Description: How to pin versions for dependencies using the github: pattern | Mentioned By: DefiniteOptimist\nDocumentation: Create guide for running ElizaOS on different platforms | Description: Address recurring issues with Linux/WSL/macOS | Mentioned By: NnrbzZ", "messageCount": 54, "userCount": 18 }, { "channelId": "1324089429727514674", "channelName": "🤖｜agent-dev-school", "summary": "# Discord Chat Analysis for 🤖｜agent-dev-school\n\n## 1. Summary\nThe chat segment reveals confusion around Eliza documentation and installation processes. Users are struggling with differences between v1 and v2 versions, particularly regarding agent creation and storage. One user (worldestroy) initially reported documentation inaccuracies but later claimed to understand the process, only to continue struggling. Another user (mindxploit) expressed frustration about being unable to locate agents created via CLI in the codebase, suggesting they might be stored in a database rather than as code files. G2 suggested that agents might be stored in `/packages/the-org`, but mindxploit clarified this only contains premade agents. The chat also reveals that agent dev school sessions have been temporarily paused for 1-2 weeks while the team focuses on releasing v2 and auto.fun.\n\n## 2. FAQ\nQ: What is the currently agreed way of doing things in regards to installation and configuration? (asked by worldestroy) A: Partially answered by jin who pointed to https://eliza.how/docs/quickstart and mentioned testing it recently\nQ: Where are the actual agents stored in the v2dev version? (asked by mindxploit) A: Partially answered by G2 who suggested \"/packages/the-org\", though mindxploit clarified this only contains premade agents\nQ: How is it possible that info about agents created with CLI can't be found in the code? (asked by mindxploit) A: Unanswered\nQ: Where should new agents be created in v2? (asked by mindxploit) A: Unanswered\nQ: Can we expect an agent dev school tomorrow? (asked by Jacob Homanics) A: Paused until v2 and auto.fun are released, approximately 1-2 weeks (answered by shaw)\n\n## 3. Help Interactions\nHelper: jin | Helpee: worldestroy | Context: Documentation accuracy concerns for Eliza installation | Resolution: Provided quickstart documentation link that was recently tested\nHelper: G2 | Helpee: mindxploit | Context: Locating where agents are stored in v2dev | Resolution: Suggested \"/packages/the-org\" but was partially incorrect as this only contains premade agents\n\n## 4. Action Items\nTechnical: Update documentation to accurately reflect v2 installation and configuration processes | Mentioned By: worldestroy\nTechnical: Clarify where user-created agents are stored in v2 and how to access them | Mentioned By: mindxploit\nDocumentation: Update documentation to explain differences between v1 and v2 | Mentioned By: mindxploit\nDocumentation: Create clear instructions for creating and managing agents in v2 | Mentioned By: mindxploit\nFeature: Improve visibility of user-created agents in the codebase | Mentioned By: mindxploit", "messageCount": 17, "userCount": 6 }, { "channelId": "1323745969115893780", "channelName": "📥｜pull-requests", "summary": "# Analysis of \"📥｜pull-requests\" Discord Channel\n\n## 1. Summary\nThe chat segment primarily revolves around questions about npm package management for ElizaOS plugins. AIFlow.ML inquires about changing names and versions in npm, though the specific context is somewhat unclear. Odilitime explains that there's no official versioning system for ElizaOS plugins and that descriptions are hardcoded in some plugin directories but not standardized across all four known plugin directories. There's also a brief mention of a Farcaster plugin, with mekpans asking about its development status and Odilitime later sharing a GitHub repository link to the client-farcaster plugin.\n\n## 2. FAQ\nQ: How to change the name and version on npm? (asked by AIFlow.ML @ ElizaOS) A: There is no versioning afaik. For names, it depends on what specifically needs to be changed. (answered by Odilitime)\nQ: How is the farcaster plugin coming along? (asked by mekpans) A: Odilitime shared a link to the GitHub repository: https://github.com/elizaos-plugins/client-farcaster\nQ: What is everyone else using for farcaster? (asked by mekpans) A: Unanswered\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: AIFlow.ML @ ElizaOS | Context: Questions about changing npm package details for ElizaOS plugins | Resolution: Explained that there's no official versioning system and descriptions are hardcoded in some directories\n\n## 4. Action Items\nTechnical: Investigate standardizing plugin versioning and descriptions | Description: Currently no official way to set descriptions, with hardcoded values in some directories | Mentioned By: Odilitime\nFeature: Implement proper versioning system for ElizaOS plugins | Description: Currently no versioning system exists for plugins | Mentioned By: Odilitime\nDocumentation: Document the four plugin directories mentioned | Description: Odilitime mentioned knowing of four plugin directories, which should be documented | Mentioned By: Odilitime", "messageCount": 21, "userCount": 3 } ] }