{
  "server": "elizaOS Development",
  "title": "elizaOS Development Discord - 2025-01-27",
  "date": 1737936000,
  "stats": {
    "totalMessages": 123,
    "totalUsers": 29
  },
  "categories": [
    {
      "channelId": "1320246527268098048",
      "channelName": "💬｜general",
      "summary": "# Analysis of Discord Chat\n\n## 1. Summary\nThe chat primarily revolves around technical discussions about Eliza's plugin system, model compatibility, and development challenges. There's an ongoing discussion about a $500 bounty for porting a Python app to v2 that can connect and retrieve data. Several members discuss model preferences, with specific mentions of DeepSeek integration, which has apparently been supported for weeks. SotoAlt shares negative experiences with DeepSeek-R1, noting it gets stuck during response generation despite being cost-effective. There are technical troubleshooting instances, including WarfreakzPlays resolving an Ollama connection issue by changing the server URL from localhost to the IP address. ICJR raises questions about the development roadmap, plugin architecture, and npm package management. Odilitime clarifies that v2 is building upon v1 rather than replacing it, with plans to backport features rather than starting fresh.\n\n## 2. FAQ\nQ: Has anyone tried running ElizaOS on an iPhone with Nodejs installed on it? (asked by DorianD) A: Unanswered\nQ: Is DeepSeek support planned? (asked by ST4RDUST) A: Yes, deepseek has been supported since weeks ago (answered by SotoAlt | BOSSU)\nQ: What model are you guys using for the best function calling capabilities? (asked by CriticalBarny) A: SecretRecipe uses llama3.2 storm but \"not hella functions\"; SotoAlt | BOSSU uses anthropic\nQ: Why is eliza-starter pinned to 0.1.7 instead of develop? (asked by ICJR) A: Broke build system has prevented releases which has left the npms broken (answered by Odilitime)\nQ: Are contributions to v2 accepted/open? (asked by ICJR) A: No, and the plan is not to scrap v1, we are building on v1 (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: WarfreakzPlays | Helpee: WarfreakzPlays | Context: Connection refused error when using Ollama locally | Resolution: Fixed by changing OLLAMA_SERVER_URL from http://localhost:11434 to http://127.0.0.1:11434\nHelper: SotoAlt | BOSSU | Helpee: ST4RDUST | Context: Question about DeepSeek support | Resolution: Confirmed DeepSeek has been supported for weeks, but noted performance issues\nHelper: Odilitime | Helpee: ICJR | Context: Questions about development direction and v1/v2 relationship | Resolution: Clarified that v2 is building on v1, not replacing it\n\n## 4. Action Items\nType: Technical | Description: Fix build system that's preventing npm package releases | Mentioned By: Odilitime\nType: Technical | Description: Implement port of Python app for v2 that connects and gets data (for $500 bounty) | Mentioned By: DorianD\nType: Technical | Description: Investigate why DeepSeek integration is returning AI_JSONParseError | Mentioned By: ek\nType: Documentation | Description: Document the relationship between v1 and v2 development paths | Mentioned By: ICJR\nType: Feature | Description: Modify news plugin to allow agent to tweet about news rather than only responding to specific queries | Mentioned By: Mad",
      "messageCount": 56,
      "userCount": 17
    },
    {
      "channelId": "1324098367416172665",
      "channelName": "📮｜feedback",
      "summary": "# Analysis of Discord Chat in 📮｜feedback Channel\n\n## 1. Summary\nThe chat segment reveals significant issues with the Client Twitter implementation that affect plugin functionality. User 0xSero identified two specific problems: repeated processing of old interactions and incompatibility with certain plugin actions, particularly with the EVM-plugin. The discussion highlights a need for better testing infrastructure, specifically unit tests for plugins, core components, and adapters. Agent Joshua suggested debugging steps including checking the database, restarting the agent, and enabling verbose logging. Shaw acknowledged these issues, confirming that \"the plugin situation has gotten out of control\" and implying that work is underway to address these problems. The conversation suggests these are ongoing issues that have persisted for at least a month, with potential improvements planned for a version 2 release.\n\n## 2. FAQ\nQ: Why doesn't the EVM-plugin work out of the box with client-twitter? (asked by Odilitime) A: Unanswered\nQ: Which version are you on and have you tried debugging steps like restarting your agent and setting VERBOSE=true? (asked by Agent Joshua ₱ | TEE) A: Running on develop branch with weekly updates, issues persist across the last month (answered by 0xSero)\n\n## 3. Help Interactions\nHelper: Agent Joshua ₱ | TEE | Helpee: 0xSero | Context: Debugging Client Twitter plugin issues | Resolution: Suggested checking DB cleanliness, restarting agent, and enabling verbose logging\n\n## 4. Action Items\nType: Technical | Description: Implement unit tests for plugin, core, and adapters | Mentioned By: 0xSero\nType: Technical | Description: Fix Client Twitter repeated processing of old interactions | Mentioned By: 0xSero\nType: Technical | Description: Resolve compatibility issues between EVM-plugin and client-twitter | Mentioned By: 0xSero\nType: Technical | Description: Address the overall \"out of control\" plugin situation | Mentioned By: shaw\nType: Technical | Description: Create more templated plugin structure | Mentioned By: 0xSero",
      "messageCount": 9,
      "userCount": 5
    },
    {
      "channelId": "1324089429727514674",
      "channelName": "🤖｜agent-dev-school",
      "summary": "# Analysis of Discord Chat in \"🤖｜agent-dev-school\"\n\n## 1. Summary\nThe chat segment is very brief and contains minimal technical discussion. There are mentions of a deepseek implementation, plugin integration with a character, and a reference to \"pnpm dev\" which appears to be a development command. One user mentions that something (unspecified) has been merged into the Eliza code base as announced by Shaw on X (Twitter). The conversation lacks detailed technical content or problem-solving discussions, with most messages being short questions or brief responses without extensive technical details.\n\n## 2. FAQ\nQ: Has anyone made a deepseek implementation? (asked by ben [τ, '] | BitMind) A: Unanswered\nQ: If I want to use a plugin, which I already finish coding, should I do something in default character? (asked by eliza.dev118) A: It's up to your plugin's features. You can set the personal adjectives, post examples, bio and some other characteristics to your character. Also specify the security key and plugins and clients. (answered by James)\nQ: What plugin did you build? (asked by dreadwulf) A: Unanswered\n\n## 3. Help Interactions\nHelper: James | Helpee: eliza.dev118 | Context: How to integrate a completed plugin with a character | Resolution: Explained that it depends on the plugin's features and provided guidance on setting character attributes and specifying security key, plugins, and clients\n\n## 4. Action Items\nTechnical: Use \"pnpm dev\" command for development | Description: Referenced as a development command without context | Mentioned By: Odilitime",
      "messageCount": 6,
      "userCount": 6
    },
    {
      "channelId": "1323745969115893780",
      "channelName": "📥｜pull-requests",
      "summary": "# Analysis of \"📥｜pull-requests\" Channel\n\n## 1. Summary\nThe channel primarily documents a systematic plugin maintenance effort by AIFlow.ML, who submitted numerous pull requests to fix issues across multiple plugins in the ElizaOS/eliza repository. These fixes addressed typing issues, missing exports, and other non-critical problems discovered during a comprehensive review of all plugins. The maintenance work appears to be part of a programmed maintenance run, with AIFlow.ML indicating they would continue monitoring all plugins for issues as new PRs come in. \n\nNotable contributions from other community members included xLuisCumbi's implementation of WhatsApp chat support for the Characterfile project, which was successfully approved, and an1muss's integration of the Deva.me client that required conflict resolution. Odilitime provided merge support and guidance, particularly regarding maintaining the default model configuration in defaultCharacter. The systematic plugin maintenance by AIFlow.ML demonstrates a methodical approach to improving code quality across the project.\n\n## 2. FAQ\nQ: What kind of conflicts were encountered with the Deva.me client integration? (asked by AIFlow.ML @ ElizaOS) A: It changes the default model in defaultCharacter, which we don't want (answered by Odilitime)\nQ: Was Starknet giving issues? (asked by AIFlow.ML @ ElizaOS) A: No, someone was asking how to test/use it (answered by Odilitime)\n\n## 3. Help Interactions\nHelper: Odilitime | Helpee: an1muss | Context: Needed help with PR for Deva.me client integration that had conflicts | Resolution: Odilitime merged the PR but requested a follow-up PR to fix defaultCharacter back to llama_local\nHelper: AIFlow.ML @ ElizaOS | Helpee: Community | Context: Systematic fixing of multiple plugins including typing issues and missing exports | Resolution: Submitted over 20 PRs addressing various plugin issues\n\n## 4. Action Items\nType: Technical | Description: Fix defaultCharacter to revert back to llama_local after Deva.me integration | Mentioned By: Odilitime\nType: Technical | Description: Complete remaining 20% of fixes needed for Starknet plugin | Mentioned By: AIFlow.ML @ ElizaOS\nType: Technical | Description: Test Sei plugin with a wallet after merge | Mentioned By: AIFlow.ML @ ElizaOS\nType: Technical | Description: Update readme for WhatsApp chat support in Characterfile | Mentioned By: xLuisCumbi\nType: Technical | Description: Diversify action names to avoid conflicts in future plugin maintenance | Mentioned By: AIFlow.ML @ ElizaOS",
      "messageCount": 52,
      "userCount": 5
    }
  ]
}