{
  "server": "elizaOS Development",
  "title": "elizaOS Development Discord - 2025-03-18",
  "date": 1742256000,
  "stats": {
    "totalMessages": 136,
    "totalUsers": 31
  },
  "categories": [
    {
      "channelId": "1320246527268098048",
      "channelName": "💬｜general",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around Eliza V2 implementation issues and troubleshooting. Users are experiencing installation problems, particularly with SQLite bindings and plugin compatibility. Chris Troutner documented his process of connecting Eliza to local LLMs via Ollama, sharing environment variable configurations for the plugin-local-ai plugin. Jin shared updates about the new documentation and frontpage at eliza.how, along with a llms.txt file for V2 help. Several users reported issues with the CLI installation process, with error messages related to package dependencies. The team acknowledged these issues and prioritized fixing them, with Borko encouraging users to report bugs. There were also discussions about LLM performance, with Chris Troutner noting that deepseek-r1:14b works well with Eliza despite not being the fastest model, as it excels at following instructions.\n\n## 2. FAQ\nQ: Has anyone worked with multi agent setup where we have to create multi agent and each agent manage multi workers under it? (asked by Shiva M) A: Unanswered\nQ: Do we have any Eliza fork compatible with CommonJS? We have our product built in NextJS and Express. (asked by Shiva M) A: Unanswered\nQ: Is there a MCP client plugin built yet for eliza? (asked by Jungle) A: There is nothing about MCP in the plugins packages gallery (answered by chris.troutner)\nQ: Should we start using v2 or should we wait until merged to main? Is it stable enough to use in production? (asked by 0xn1c0) A: I don't think it's stable enough to be used in production for a business. It's officially in beta. But I'm using it for my new hobby project. (answered by chris.troutner)\nQ: Can Eliza answer with the first letter is uppercase? Do i need to config all lowercase for character settings? (asked by HarryRiddle.eth) A: Unanswered\nQ: How to install eliza? I used to clone it, then uninstalled but now there is different way of installation (asked by Beowoolf) A: Eliza.how (answered by jin)\nQ: What all chains can Eliza have create agent wallets on? Any EVM? (asked by Scooter) A: yes any evm, couple dozen chains supported (answered by jin)\nQ: is it fast? (asked by volenn) A: Yes. I'm getting around 35 tokens per second on a GeForce 3060 with 12GB of VRAM on the deepseek-r1:14b model. (answered by chris.troutner)\n\n## 3. Help Interactions\nHelper: La flame | Helpee: tamadekk, Omkar dixit | Context: SQLite module binding errors during installation | Resolution: Suggested running \"pnpm add better-sqlite3@latest --force\" and \"npm rebuild better-sqlite3\" to fix the issue\nHelper: tamadekk | Helpee: Omkar dixit | Context: SQLite binding errors | Resolution: Suggested using \"pnpm approve-builds\" and selecting better-sqlite3 to be built\nHelper: chris.troutner | Helpee: OwnedSK | Context: Finding the right plugin for connecting to local LLMs via Ollama | Resolution: Identified plugin-local-ai and shared environment variable configuration for deepseek models\nHelper: z1 | Helpee: volenn | Context: Looking for tools to scrape tweets on X | Resolution: Suggested self-hosting N8N with a tutorial on how to set up Twitter scraping\nHelper: chris.troutner | Helpee: Multiple users | Context: Shared experience with LLM models for Eliza | Resolution: Provided insights on deepseek-r1:14b model performance with Eliza framework\n\n## 4. Action Items\nTechnical: Fix CLI installation issues with SQLite bindings | Description: Users experiencing \"Could not locate the bindings file\" errors | Mentioned By: La flame, tamadekk, Omkar dixit\nTechnical: Fix npm package dependency issues | Description: Error \"No matching version found for @elizaos/plugin-sql@^0.25.6\" | Mentioned By: 4n7m4n\nTechnical: Address V2 start issues | Description: Multiple issues with starting Eliza V2 | Mentioned By: jin\nTechnical: Improve plugin-local-ai documentation | Description: Users struggling to find and configure local LLM connections | Mentioned By: chris.troutner\nDocumentation: Update CLI installation instructions | Description: Current docs suggest using npx which doesn't work correctly | Mentioned By: jin\nDocumentation: Create comprehensive getting started guide | Description: Need to map out all areas of getting started and verify steps work | Mentioned By: jin\nDocumentation: Document environment variables for local LLM integration | Description: Configuration for Ollama and other local models | Mentioned By: chris.troutner\nFeature: Support for Ollama API in V2 | Description: Enable connecting to LLMs on different machines via Ollama | Mentioned By: chris.troutner\nFeature: CommonJS compatibility | Description: Support for NextJS and Express applications | Mentioned By: Shiva M",
      "messageCount": 119,
      "userCount": 25
    },
    {
      "channelId": "1327493511406293016",
      "channelName": "🎤｜plug-your-projects",
      "summary": "Chris Troutner is planning to build a tech-support bot using the ElizaOS framework. His goals include:\n   - Creating an AI \"librarian\" that can retrieve code snippets and information via RAG\n   - Running models locally using Ollama on custom hardware (Linux desktop with NVIDIA GeForce 3060)\n   - Focusing on Telegram and Nostr as primary clients\n   - Separating knowledge base from bot code in different repositories\n   - Developing a Nostr plugin for the tech support bot",
      "messageCount": 4,
      "userCount": 4
    },
    {
      "channelId": "1324089429727514674",
      "channelName": "🤖｜agent-dev-school",
      "summary": "# Analysis of Discord Chat in 🤖｜agent-dev-school\n\n## 1. Summary\nThe chat segment contains a brief discussion about implementing a crypto trading agent. Behnam Mirzabeygi outlines a high-level approach involving three steps: establishing a crypto database (either creating one or using an existing one), converting this database into an Eliza provider to feed data to the agent, and defining actions to detect and act upon trading opportunities. Rick suggests a similar but slightly different approach, breaking the process into three stages: collecting data, storing data, and defining how to use the data. The user NB clarifies that their agent only needs to post to Twitter or answer Discord queries about opportunities. Behnam mentions that while he has worked on a similar client project, the code isn't available to share as an example. The conversation concludes with KaiserMerkle asking about upcoming dev-school streams.\n\n## 2. FAQ\nQ: When are the next dev-school streams? (asked by KaiserMerkle) A: Unanswered\n\n## 3. Help Interactions\nHelper: Behnam Mirzabeygi | Helpee: NB | Context: Implementation approach for a crypto trading agent | Resolution: Provided a three-step high-level approach (database creation, Eliza provider conversion, action definition)\nHelper: Rick | Helpee: NB | Context: Implementation approach for a crypto trading agent | Resolution: Suggested breaking the process into three stages (collect data, store data, define usage)\n\n## 4. Action Items\nTechnical: Create a database of crypto data or use an existing one | Description: First step in implementing a crypto trading agent | Mentioned By: Behnam Mirzabeygi\nTechnical: Convert crypto database to an Eliza provider | Description: Feed the agent with crypto data | Mentioned By: Behnam Mirzabeygi\nTechnical: Define actions to detect and act upon trading opportunities | Description: Enable agent to identify and respond to opportunities | Mentioned By: Behnam Mirzabeygi",
      "messageCount": 7,
      "userCount": 4
    },
    {
      "channelId": "1323745969115893780",
      "channelName": "📥｜pull-requests",
      "summary": "# Analysis of \"📥｜pull-requests\" Channel\n\n## 1. Summary\nThe chat segment is brief and contains minimal technical discussion. Two main topics were addressed: \n1) Daniel BNV reported a broken link issue with their plugin (bnv-me-id) on the plugin registry page and requested assistance from a specific user.\n2) fforbeck announced a new PR for adding a Distributed Storage Plugin to Eliza's Plugin Registry and requested review and feedback.\nAdditionally, jin mentioned setting up AI-news to aggregate and summarize content from several channels including pull-requests. The conversation was primarily about administrative matters rather than deep technical discussions, with users seeking help or announcing new contributions to the Eliza ecosystem.\n\n## 2. FAQ\nQ: What is the broken link issue? (asked by Odilitime) A: The link to the plugin https://github.com/elizaos-plugins/plugin-bnv-me-id on the plugin registry page is broken (answered by Daniel BNV)\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: Daniel BNV | Context: Asking for clarification about the broken link issue | Resolution: Daniel BNV provided the specific URL that was broken on the plugin registry page\n\n## 4. Action Items\nTechnical: Fix broken link for the bnv-me-id plugin on the plugin registry page | Mentioned By: Daniel BNV\nTechnical: Review and provide feedback on the Distributed Storage Plugin PR | Mentioned By: fforbeck\nTechnical: Set up AI-news aggregation for multiple channels including pull-requests | Mentioned By: jin",
      "messageCount": 6,
      "userCount": 4
    }
  ]
}