{
  "server": "elizaOS Development",
  "title": "elizaOS Development Discord - 2025-03-19",
  "date": 1742342400,
  "stats": {
    "totalMessages": 252,
    "totalUsers": 40
  },
  "categories": [
    {
      "channelId": "1320246527268098048",
      "channelName": "💬｜general",
      "summary": "# Analysis of Discord Chat in 💬｜general Channel\n\n## 1. Summary\nThe chat primarily revolves around users trying to install and use Eliza v2 beta, which is currently experiencing various installation and setup issues. Users are struggling with the CLI commands, dependencies like bun, and getting agents to appear in their installations. Shaw and jin provide troubleshooting assistance throughout the conversation. The v2 version is officially in beta status and not yet considered stable for production business use, though some developers are using it for hobby projects. There are discussions about LLM models that work well with Eliza, with deepseek-r1:14b being highlighted as particularly good at following instructions despite not being the fastest. Several bugs are reported, including migration errors, missing default agents, and installation problems. The team acknowledges these issues and is prioritizing fixes for the beta release.\n\n## 2. FAQ\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: How to install eliza? (asked by Beowoolf) A: Eliza.how (answered by jin)\nQ: What all chains can Eliza have create agent wallets on? (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)\nQ: How do I import those agents into my terminal? (asked by 古奇 黑鬼) A: You gotta clone the repo to get the org: `git clone https://github.com/elizaos/eliza && cd eliza && bun install && bun run start` (answered by shaw)\nQ: What is the latest stable version and how to install it? (asked by Tiki) A: v2-develop branch (answered by yung_algorithm)\n\n## 3. Help Interactions\nHelper: shaw | Helpee: m4ss | Context: User couldn't figure out how to install and run Eliza | Resolution: Provided installation commands and explained that bun needs to be installed first\nHelper: shaw | Helpee: tuck | Context: User was getting errors when trying to run Eliza | Resolution: Suggested alternative commands and identified that the issue was related to missing bun dependency\nHelper: jin | Helpee: 4n7m4n | Context: User tried to install an old IRC bot package named \"eliza\" instead of the correct package | Resolution: Clarified the correct package name and commands\nHelper: 0xbbjoker | Helpee: jin | Context: User encountered database migration errors | Resolution: Explained the issue was due to schema changes and suggested wiping and starting again\nHelper: shaw | Helpee: 古奇 黑鬼 | Context: User couldn't get agents to appear in their installation | Resolution: Identified that the default agent creation wasn't working properly and promised a fix\n\n## 4. Action Items\nType: Technical | Description: Fix default agent creation in beta installation | Mentioned By: shaw\nType: Technical | Description: Fix startup issues identified in GitHub issue #3989 | Mentioned By: jin\nType: Technical | Description: Fix broken link on elizaos.ai/framework that 404s to .gg | Mentioned By: cjft\nType: Technical | Description: Address database migration errors with relation \"agents\" already exists | Mentioned By: jin\nType: Technical | Description: Increase chunk size for knowledge table to improve text similarity search | Mentioned By: Sabochee\nType: Technical | Description: Fix RAG search error with MongoDB: \"SyntaxError: unexpected token: '{'\" | Mentioned By: y`Sir bLack\nType: Feature | Description: Create an .exe installer for easier setup for non-developers | Mentioned By: shaw\nType: Documentation | Description: Map out all getting started areas and verify steps work | Mentioned By: jin\nType: Documentation | Description: Improve documentation for Discord plugin optional settings | Mentioned By: Humann",
      "messageCount": 237,
      "userCount": 34
    },
    {
      "channelId": "1327493511406293016",
      "channelName": "🎤｜plug-your-projects",
      "summary": "# Analysis of \"🎤｜plug-your-projects\" Channel\n\n## 1. Summary\nThe chat segment is very brief, containing only two messages. NaN announced a project called aigent.sh, which aims to make AI Agents accessible to non-technical users. The platform is built using ElizaOS technology. NaN mentioned that they are releasing daily updates and requested feedback, offering prioritized early access to those who send a direct message. Odilitime responded with a brief question about whether the project had been submitted to \"the registry\" (presumably an AI agent registry or catalog).\n\n## 2. FAQ\nQ: Did you submit it to the registry? (asked by Odilitime) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were present in this brief chat segment.\n\n## 4. Action Items\nFeature: Consider submitting aigent.sh to \"the registry\" | Description: Project may need to be registered in a community catalog or registry | Mentioned By: Odilitime",
      "messageCount": 2,
      "userCount": 2
    },
    {
      "channelId": "1324089429727514674",
      "channelName": "🤖｜agent-dev-school",
      "summary": "# Discord Chat Analysis for 🤖｜agent-dev-school\n\n## 1. Summary\nThe chat segment contains minimal technical discussion. Users are inquiring about upcoming dev-school streams, promotional materials, and experiencing technical issues. Two specific technical problems were mentioned: one user having trouble with the CoinGecko plugin, and another encountering a \"better-sqlite3\" error when trying to start a Twitter agent. There was also a brief exchange about an out-of-memory error, with a suggestion to check RAM availability. Overall, this segment represents a help-seeking environment with limited resolution of the issues presented.\n\n## 2. FAQ\nQ: When are the next dev-school streams? (asked by KaiserMerkle) A: Unanswered\nQ: Can someone help me out with the congecko plugin? (asked by La flame) A: Unanswered\nQ: How much ram do you have? (asked by Odilitime) A: Unanswered\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: Unknown | Context: Someone experiencing an \"out of memory\" error | Resolution: Odilitime suggested checking RAM availability, but no confirmation of resolution\n\n## 4. Action Items\nTechnical: Resolve CoinGecko plugin issues | Description: User experiencing unspecified trouble with the plugin | Mentioned By: La flame\nTechnical: Fix better-sqlite3 error | Description: Error occurs when starting a Twitter agent with \"pnpm start\" | Mentioned By: Chen0xA3\nDocumentation: Create promotional material | Description: Something to promote the next stream | Mentioned By: jin",
      "messageCount": 7,
      "userCount": 5
    },
    {
      "channelId": "1323745969115893780",
      "channelName": "📥｜pull-requests",
      "summary": "# Analysis of \"📥｜pull-requests\" Discord Channel\n\n## 1. Summary\nThe chat segment shows minimal activity in the pull-requests channel. Jin mentioned setting up an AI-news aggregation/summarization system for several channels including pull-requests, and shared a link to a GitHub pull request (PR #4032 in the elizaOS/eliza repository). Daniel BNV inquired about updates on a plugin situation, and fforbeck requested a review for an unspecified pull request. The conversation lacks detailed technical discussions or problem-solving, consisting primarily of brief status inquiries and link sharing.\n\n## 2. FAQ\nQ: Has there been any updates regarding our plugin situation? (asked by Daniel BNV) A: Unanswered\n\n## 3. Help Interactions\nNo significant help interactions were present in this chat segment.\n\n## 4. Action Items\nTechnical: Review pull request #4032 in elizaOS/eliza repository | Description: Jin shared this PR link but provided no details about its content | Mentioned By: jin\nTechnical: Review unspecified pull request | Description: fforbeck requested review of an unmentioned PR | Mentioned By: fforbeck\nTechnical: Set up AI-news aggregation for multiple channels | Description: Aggregate and summarize content from general, plug-your-projects, agent-dev-school, and pull-requests channels | Mentioned By: jin\nTechnical: Address plugin situation | Description: Follow up on plugin-related inquiry | Mentioned By: Daniel BNV",
      "messageCount": 5,
      "userCount": 3
    },
    {
      "channelId": "1324098367416172665",
      "channelName": "📮｜feedback",
      "summary": "# Analysis of Discord Chat in 📮｜feedback Channel\n\n## 1. Summary\nThe discussion centers on a technical issue encountered while building a crypto wallet with an Eliza agent. ShisukeUrahara describes a problem where the agent fails to recognize when a wallet has been funded after previously determining there were insufficient funds. Specifically, when the user requests to transfer ETH and the agent determines there are insufficient funds, the agent continues to reference this outdated information even after the wallet has been funded. The only workaround found was to delete the memories table from the database, forcing the agent to check the current balance instead of relying on conversation history. This highlights a significant limitation in how the agent handles state changes that occur outside its direct observation (like on-chain transactions) and suggests a need for improved context management for financial applications.\n\n## 2. FAQ\nQ: Is there any better way to deal with the issue of agents not recognizing external state changes like wallet funding? (asked by ShisukeUrahara) A: Unanswered\n\n## 3. Help Interactions\nNo help interactions were present in this chat segment.\n\n## 4. Action Items\nType: Technical | Description: Implement a mechanism for agents to recognize external state changes (like on-chain transactions) without requiring memory deletion | Mentioned By: ShisukeUrahara\nType: Feature | Description: Add functionality for crypto wallet agents to verify current balances rather than relying solely on conversation history | Mentioned By: ShisukeUrahara",
      "messageCount": 1,
      "userCount": 1
    }
  ]
}