{ "server": "elizaOS", "title": "elizaOS Discord - 2025-03-14", "date": 1741910400, "stats": { "totalMessages": 306, "totalUsers": 72 }, "categories": [ { "channelId": "1253563209462448241", "channelName": "discussion", "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat segment from the \"discussion\" channel contains minimal substantive technical discussion. The primary technical question raised was about customizing a client using the eliza-starter project, which appears outdated compared to the current ElizaOS version (0.25.9). There was a brief mention of hosting the chat interface on Phala's TEE cloud server. The conversation also touched on the upcoming ElizaOS V2 release scheduled for March 17th (Monday). Other topics included comparisons between ElizaOS, manusAI, and deepSeekAI, as well as some discussion about token requirements for partner entry in different projects (DegenAI and ai16z). The chat contained several greetings and some off-topic messages, including a self-promotion from a blockchain developer.\n\n## 2. FAQ\nQ: When will ElizaOS V2 be released? (asked by [SAI]Colomb) A: Monday, March 17th, if nothing changes (answered by anon)\nQ: What is the difference between ElizaOS, manusAI, and deepSeekAI? Are they competitors? (asked by NoName) A: Unanswered\nQ: Why hasn't the eliza-starter project been updated to match ElizaOS version 0.25.9? (asked by lay.qin) A: Unanswered\nQ: Is there a way to host the chat interface on Phala's TEE cloud server? (asked by Gris) A: Unanswered\nQ: Why does it always disconnect? (asked by CC) A: Unanswered\n\n## 3. Help Interactions\nHelper: boolkeys | Helpee: OwnedSK | Context: User asking about access and disconnection issues | Resolution: Suggested looking at plugin-tee and asking in the coders channel for technical help\nHelper: Patt | Helpee: wlt 🧩 | Context: User confused about a non-working spaces link for \"WDYGDTW\" | Resolution: Explained that the event is on hiatus and should be taken down until it returns\n\n## 4. Action Items\nTechnical: Update the eliza-starter project to be compatible with ElizaOS version 0.25.9 | Mentioned By: lay.qin\nTechnical: Investigate hosting the chat interface on Phala's TEE cloud server | Mentioned By: Gris\nTechnical: Address disconnection issues with the client | Mentioned By: CC\nDocumentation: Remove or update the event listing for \"WDYGDTW\" since it's currently on hiatus | Mentioned By: Patt", "messageCount": 42, "userCount": 30 }, { "channelId": "1300025221834739744", "channelName": "💻-coders", "summary": "# Analysis of 💻-coders Discord Channel\n\n## 1. Summary\nThe discussions primarily focused on ElizaOS development, with emphasis on Twitter client integration issues, API documentation, and the upcoming v2 release. Many users reported problems with Twitter clients stopping responses after a period of activity, likely due to rate limiting. There were questions about connecting to ElizaOS via websockets and SSE for custom interfaces. Several developers sought guidance on adding knowledge to agents through PDFs and folders. Shaw announced that a v2 beta release is coming next week with significant improvements including easier CLI commands, better agent collaboration, and improved API endpoints. The folder2knowledge and knowledge2character tools were mentioned as ways to add information to agents. Documentation gaps were highlighted by multiple users struggling with plugin installation and configuration.\n\n## 2. FAQ\nQ: Is there any documentation on the agent chat API? (asked by 🧧ThanosDaSith24🧧) A: jin shared a link to https://elizaos.github.io/eliza/docs/rest/set-agent and mentioned they would keep updating it.\nQ: Is it possible to host the chat interface on Phala's TEE cloud server? (asked by Gris) A: Unanswered\nQ: Can we connect to the ElizaOS server using websockets to interact with the agent? (asked by winded4752) A: Shaw suggested looking at how the client parses it in packages/client.\nQ: How do you add a local plugin to your character? (asked by $algalon) A: Rosario Borgesi explained to add it in the plugin field of the AgentRuntime object in agent/src/index.ts.\nQ: What is the latest, stable release for a new Eliza project? (asked by chris.troutner) A: Rosario Borgesi confirmed they are using 0.25.9.\nQ: Has anyone gotten folder2knowledge working? (asked by Midas) A: Shaw suggested it might need a \"../\" or \"../../\" path prefix, and Midas confirmed \"../\" worked.\nQ: Is there a simple process for adding PDFs to convert to text for an agent's knowledge/memory? (asked by SMA) A: Phoenix suggested using the Eliza character generator website at https://elizagen.howieduhzit.best/ to upload and process PDFs.\nQ: Is it possible to build with ELIZA OS without any coding knowledge? (asked by blueeyesmoki) A: Phoenix mentioned they have a quick start guide on their website, and Shaw noted the upcoming beta will make this very easy.\nQ: What's the best database to use with Eliza? (asked by Dean) A: Unanswered\n\n## 3. Help Interactions\nHelper: shaw | Helpee: Midas | Context: folder2knowledge not finding folder | Resolution: Suggested adding \"../\" or \"../../\" to path, which Midas confirmed fixed the issue.\nHelper: Phoenix | Helpee: SMA | Context: Adding PDFs to agent knowledge | Resolution: Directed to Eliza character generator website with PDF processing capabilities.\nHelper: Rosario Borgesi | Helpee: bradtheaverage | Context: Setting up Twitter client | Resolution: Shared a tutorial video on using Eliza to tweet on X.\nHelper: jin | Helpee: 🧧ThanosDaSith24🧧 | Context: Documentation for agent chat API | Resolution: Provided link to REST API documentation.\nHelper: Midas | Helpee: blueeyesmoki | Context: Adding knowledge to agents | Resolution: Explained using folder2knowledge and knowledge2character tools.\nHelper: shadows.13 | Helpee: nhandl3 | Context: Twitter client installation | Resolution: Provided steps for installing Twitter plugins, though there was confusion about exact syntax.\n\n## 4. Action Items\nType: Technical | Description: Fix Twitter client issues with stopping replies after period of activity | Mentioned By: Ordinal Watches, Abderahman\nType: Documentation | Description: Update documentation for Twitter client installation and configuration | Mentioned By: nhandl3\nType: Documentation | Description: Create guide for connecting to agent via websockets | Mentioned By: winded4752\nType: Feature | Description: Improve Twitter client to handle rate limiting better | Mentioned By: Ordinal Watches\nType: Technical | Description: Implement action for Discord client to post tweets when requested | Mentioned By: Nooters\nType: Documentation | Description: Document how to pass information from a client to a plugin | Mentioned By: Okul\nType: Feature | Description: Create method to call image generator plugin action from within another action | Mentioned By: Rosario Borgesi\nType: Technical | Description: Optimize response time for deepseek model provider | Mentioned By: Alejo0x.eth\nType: Documentation | Description: Create guide for running agents on local machines | Mentioned By: chris.troutner\nType: Feature | Description: Develop Nostr interface for ElizaOS | Mentioned By: chris.troutner", "messageCount": 177, "userCount": 34 }, { "channelId": "1300756641406521416", "channelName": "ideas-feedback-rants", "summary": "The chat segment contains minimal technical discussion. One user reported a build issue with image generation using pnpm build, while another made a brief comment about a Twitter-related tool. There were no detailed technical discussions, decisions, or problem-solving exchanges in this limited segment.", "messageCount": 2, "userCount": 2 }, { "channelId": "1308149076893630555", "channelName": "spartan_holders", "summary": "The chat segment is extremely brief with no substantive technical discussions, decisions, or problem-solving. It contains only four messages: a question about potential DegenAI updates coinciding with ElizaOS v2 release on March 17th, a brief comment about social engagement, and two messages containing only a GIF and an emoji. No technical content, solutions, or implementations were discussed in this limited exchange.", "messageCount": 4, "userCount": 4 }, { "channelId": "1301363808421543988", "channelName": "🥇-partners", "summary": "# Discord Chat Analysis for 🥇-partners Channel\n\n## 1. Summary:\nThe chat primarily revolves around the upcoming V2 release, scheduled for Monday. Technical discussions focus on composite trust scores, with DorianD sharing a detailed implementation concept that leverages social graphs of trusted agents. The system could potentially monetize AI16z tokens and integrate with existing Eliza trading system trust scores. There's significant discussion about a text-to-speech model on Huggingface (csm-1b) that community members have tested, though yikesawjeez notes it's \"barebones and kneecapped\" with audio-only output and missing components. The V2 deployment appears to be designed for one-click AWS free tier installation. Members also discussed visual design elements for a virtual boardroom environment, with some preferring a \"Jedi council vibe\" while others prefer different aesthetics. A marketing platform called \"Automative the Web3 Narrative\" was mentioned, which would leverage Eliza OS Brain for content creation across multiple platforms.\n\n## 2. FAQ:\nQ: Assuming v2 goes live Monday, will everyone have access to the source code then? (asked by Conan) A: Unanswered\nQ: We not gonna roll out v2 and just drop it on Monday? (asked by anon) A: Unanswered\nQ: V2 in 2 days? Any roll out plans? (asked by anon) A: V2's shaping up to look like it should one-click to aws free tier & I know first plugin imma build is mcp, personally my roll out plan is 'rig up dope elizas and do dope shit with them'&&agent dev school to teach everybody else to do the same (answered by yikesawjeez)\nQ: Any thoughts on what a good rollout plan looks like 2 ppl? (asked by yikesawjeez) A: I guess what would be good for me is an announcement that showcase in layman's terms what v2 does differently. So like a thread and each post in the thread is one major feature of v2, maybe a before and after comparison. (answered by Patt)\nQ: How much did the domain cost you? (asked by sesāme 🧩) A: Unanswered\nQ: What sort of boardroom do we want? (asked by jin) A: Jin can we do something with glass windows and a view? (answered by vincentpaul)\n\n## 3. Help Interactions:\nHelper: yikesawjeez | Helpee: vincentpaul | Context: Inquiring about the quality of the csm-1b TTS model compared to initial demos | Resolution: Explained technical limitations - audio-only output, missing emotional detection components, slow processing due to 32 codebooks per forward pass\nHelper: yikesawjeez | Helpee: Patt | Context: Discussion about V2 rollout strategy | Resolution: Agreed to draft an overview thread for the weekend explaining V2's features\nHelper: shaw | Helpee: yikesawjeez | Context: Alternative deployment options for V2 | Resolution: Shared that he has it working in Replit and as an app\n\n## 4. Action Items:\nType: Technical | Description: Implement composite trust scores based on social graph of trusted agents | Mentioned By: DorianD\nType: Technical | Description: Build MCP as first plugin for V2 | Mentioned By: yikesawjeez\nType: Technical | Description: Set up one-click AWS free tier deployment for V2 | Mentioned By: yikesawjeez\nType: Documentation | Description: Create a thread explaining V2 features with before/after comparisons | Mentioned By: yikesawjeez\nType: Feature | Description: Integrate Eliza with humanoid robotics | Mentioned By: anon\nType: Feature | Description: Create \"Automative the Web3 Narrative\" marketing platform leveraging Eliza OS Brain | Mentioned By: DorianD\nType: Feature | Description: Design virtual boardroom environment with glass windows and a view | Mentioned By: vincentpaul\nType: Technical | Description: Develop \"agent dev school\" to teach others how to build Elizas | Mentioned By: yikesawjeez", "messageCount": 59, "userCount": 15 }, { "channelId": "1313222089271939102", "channelName": "3d-ai-tv", "summary": "# Analysis of 3d-ai-tv Discord Channel\n\n## 1. Summary\nThe discussion centers around integrating AI-driven show runners and NPC interactions in game engines, particularly Unreal. SM Sith Lord describes implementing a show runner in Source engine using an embedded web browser with postMessage interface, which took only one day. The approach loads the \"shmotime\" site in an embedded web tab that communicates with the engine through events. Alternative implementation involves parsing JSON show configs and using TTS for dialogue playback. PENDINGREALITY mentions working on the Eliza plugin (available on FAB) for NPC interactions, primarily using API-based models rather than local ones due to performance concerns when running alongside game engines. There's interest in potential demonstrations and implementations, with whobody noting that high-end studios are building closed Unreal/Comfy workflows that could benefit from agent integration, mentioning Lightcraft.pro as an example of innovative Unreal technology for on-set production.\n\n## 2. FAQ\nQ: Can you run Sith show runner in Unreal? (asked by boom) A: Not directly addressed, but SM Sith Lord described implementation via embedded web browser with postMessage interface in Source engine (answered by SM Sith Lord)\nQ: What's the performance like running AI and Unreal engine simultaneously? (asked by SM Sith Lord) A: Local models likely won't perform well in-game; APIs like OpenAI are preferred for response generation (answered by PENDINGREALITY)\n\n## 3. Help Interactions\nHelper: SM Sith Lord | Helpee: boom | Context: Implementation of show runner in game engines | Resolution: Detailed two approaches - embedded web browser with postMessage interface for quick integration, or custom implementation using JSON structure for show configs\nHelper: PENDINGREALITY | Helpee: boom | Context: Information about Eliza plugin for NPC interactions | Resolution: Directed to documentation and GitHub on FAB, mentioned focusing on direct NPC interaction\n\n## 4. Action Items\nTechnical: Implement show runner in Unreal using embedded web browser approach | Description: Use postMessage interface to handle events between web browser and engine | Mentioned By: SM Sith Lord\nTechnical: Explore JSON structure for custom show runner implementation | Description: Study sample JSON from show config and episode to understand playback structure | Mentioned By: SM Sith Lord\nFeature: Integrate Eliza plugin with Sith show runner | Description: Combine NPC interaction capabilities with show running functionality | Mentioned By: PENDINGREALITY\nDocumentation: Prepare demo day presentation for Eliza plugin | Description: Create demonstration of NPC interaction capabilities | Mentioned By: PENDINGREALITY\nFeature: Explore on-set production applications with tools like Lightcraft.pro | Description: Investigate agent integration with real-time greenscreen to 3D previz technology | Mentioned By: whobody", "messageCount": 22, "userCount": 5 } ] }