{
  "server": "elizaOS",
  "title": "elizaOS Discord - 2025-06-01",
  "date": 1748736000,
  "stats": {
    "totalMessages": 98,
    "totalUsers": 32
  },
  "categories": [
    {
      "channelId": "1253563209462448241",
      "channelName": "discussion",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe discussion primarily revolves around ElizaOS (also referred to as ai16z by ticker symbol), an AI-driven DAO framework project. Community members sought clarification about the relationship between ElizaOS and ai16z, with Kenk explaining that ElizaOS is the framework/brand name while ai16z is the token ticker. The project aims to leverage AI agents for DAO operations including communications, contribution, and governance insights, though governance functionality is not yet live. There were mentions of a launchpad called auto.fun that appears to be in development with staking functionality coming. Some users expressed frustration about the project's pace and perceived lack of utility, while others defended the long-term building approach. There were references to \"v2\" being released but not officially announced, and mentions of specific AI agents including \"eli5\" and \"The Org\" that appear to be part of the ecosystem.\n\n## 2. FAQ\nQ: Can someone clear some things up for me, since I think I might be confusing ai16z and ElisaOS. Which of these projects goal was an AI driven DAO? (asked by mjelly.01) A: $ai16z is the ticker, elizaOS is the name of the framework and the brand name of the project. Governance is not live but the goal is to leverage AI agents for DAO operations (answered by Kenk)\nQ: Is the DAO live yet? How to take part in it, if possible yet? (asked by mjelly.01) A: We haven't implemented governance yet (answered by Kenk)\nQ: Also I was under the impression that holding more than 100 ai16z gives voting rights to the DAO? (asked by mjelly.01) A: ai16z partners have a holding of 100k $ai16z to access some areas, daos.fun just introduced a governance space where you need to hold 1 SOL of ai16z to discuss (answered by Kenk)\nQ: will we change ticker from $ai16z to $eliza? (asked by HERF) A: Unanswered\nQ: Why is autofun so unpopular and no one uses it? And how do you plan to market it in the future? (asked by cloudAI) A: Unanswered\n\n## 3. Help Interactions\nHelper: Kenk | Helpee: mjelly.01 | Context: Confusion about the relationship between ai16z and ElizaOS | Resolution: Kenk clarified that ai16z is the token ticker while ElizaOS is the framework/brand name\nHelper: Kenk | Helpee: mjelly.01 | Context: Questions about governance and staking functionality | Resolution: Kenk explained that governance isn't implemented yet and there's no DAO staking currently\nHelper: xell0x | Helpee: Unspecified | Context: Technical assistance needed for eli5 eliza v2 twitter agent | Resolution: xell0x reached out to another user to provide assistance\n\n## 4. Action Items\nType: Technical | Description: Implement auto.fun staking functionality (PR exists) | Mentioned By: xell0x\nType: Technical | Description: Address the sequential processing limitation where 15 concurrent users must wait for responses in order | Mentioned By: DirtyCajunRice\nType: Feature | Description: Introduce \"The Org\" component to the ecosystem | Mentioned By: xell0x\nType: Feature | Description: Officially announce v2 which is already released | Mentioned By: xell0x\nType: Documentation | Description: Clarify the relationship between ai16z token and ElizaOS framework for community members | Mentioned By: mjelly.01",
      "messageCount": 58,
      "userCount": 17
    },
    {
      "channelId": "1300025221834739744",
      "channelName": "💻-coders",
      "summary": "# Discord Chat Analysis for 💻-coders Channel\n\n## 1. Summary:\nThe discussion primarily revolves around ElizaOS v2 development, focusing on custom UI integration, plugin development, and agent configuration. Shaw shared information about client-side code and a NextJS starter for custom UIs. AIFlow.ML mentioned roadtesting plugins and agents using elizaos_mcp. Several technical questions arose about agent configuration, including how to find agent IDs and prevent agents from talking to each other on Discord. There were also discussions about plugin development challenges, with users seeking guidance on making local plugins available to agents. Other topics included parallelism concerns in ElizaOS v2 and the possibility of adding git repository references as valid plugin strings. The community appears active with members helping each other troubleshoot implementation issues.\n\n## 2. FAQ:\nQ: Does the heurist mcp's work for external dapps like on websites or telegram bots? (asked by 0x5AM) A: Unanswered\nQ: How do i find NEXT_PUBLIC_AGENT_ID=your_agent_id? (asked by 0x5AM) A: On your local eliza frontend; go to that agent and copy UUID from url bar chat/<agent-uuid> (answered by sayonara)\nQ: Hey how can i make agents on discord dont talk with each other and dont send more than 1 message at a time? (asked by Jimmy) A: You need to really prompt your characters with these instructions. The more effort you put into tuning the character file, the less code you will need to work around the implicit ai behavior (answered by shaw)\nQ: Has parallelism been addressed in v2? For \"fundamental\" configurations like twitter, discord, telegram, direct chat (asked by DirtyCajunRice) A: Unanswered\nQ: How do I access my local plugin from an agent? (asked by ack129) A: If you run bun run start in a plugin it should be testable, but it will need to be registered to the registry to be available via string (answered by shaw)\n\n## 3. Help Interactions:\nHelper: sayonara | Helpee: 0x5AM | Context: Finding agent ID for configuration | Resolution: Instructed to copy UUID from the URL bar in the chat interface\nHelper: shaw | Helpee: Jimmy | Context: Preventing Discord agents from talking to each other | Resolution: Advised to focus on tuning character files with specific instructions\nHelper: jonas | Helpee: Jimmy | Context: Preventing Discord agents from responding to bots | Resolution: Shared configuration setting: `settings: { discord: { shouldIgnoreBotMessages: true }}`\nHelper: shaw | Helpee: ack129 | Context: Testing local plugins | Resolution: Explained that running \"bun run start\" in a plugin makes it testable, but registry registration is needed for string access\n\n## 4. Action Items:\nTechnical: Add capability to insert `git:myorg/plugin#branch` as a valid plugin string | Mentioned By: shaw\nTechnical: Support loading plugins from workspace in CLI | Mentioned By: Odilitime\nTechnical: Address parallelism for handling multiple simultaneous chat messages | Mentioned By: DirtyCajunRice\nDocumentation: Create up-to-date hello world plugin walkthrough | Mentioned By: ack129\nDocumentation: Clarify process for integrating modified plugins into projects | Mentioned By: MatteoB\nFeature: Implement solution for preventing agents from talking to each other on Discord | Mentioned By: Jimmy",
      "messageCount": 31,
      "userCount": 15
    },
    {
      "channelId": "1361442528813121556",
      "channelName": "fun",
      "summary": "No significant technical discussions, decisions, or problem-solving occurred in this chat segment. The conversation briefly mentioned a site being down with a \"server can't be found\" error. One user mentioned finding \"eliza how docs\" which resolved their issue. The rest of the messages were brief comments about \"eli5\" and \"EDDY\" without technical context.",
      "messageCount": 7,
      "userCount": 4
    },
    {
      "channelId": "1301363808421543988",
      "channelName": "🥇-partners",
      "summary": "The chat segment is extremely brief, containing only two messages from a user named Rick. The first message announces \"Trending 𝕏 Posts\" and the second shares a tweet from user \"cichen1314\" that was posted 2 hours prior. There are no technical discussions, problem-solving activities, or implementations mentioned in this limited exchange.",
      "messageCount": 2,
      "userCount": 1
    }
  ]
}