# Council Briefing: 2025-06-17 ## Monthly Goal Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2. ## Daily Focus - The suspension of ElizaOS's Twitter account with 149K followers represents a critical setback to our auto.fun agent visibility strategy, requiring immediate adaptation of our social media approach. ## Key Points for Deliberation ### 1. Topic: Twitter Account Suspension Crisis **Summary of Topic:** The ElizaOS Twitter account with 149K followers has been suspended due to API policy violations, severely impacting our ability to showcase agent activity and potentially undermining the auto.fun visibility strategy. #### Deliberation Items (Questions): **Question 1:** Should we prioritize fighting for Twitter account restoration or accelerate our pivot to alternative platforms? **Context:** - `辞尘鸽鸽: We haven't abandoned the Twitter account. We're treating this as urgent and have contacted X to expedite resolution. Farcaster is only being prepared as a backup option.` - `cjft: Update Twitter plugin to work with X's API policies.` **Multiple Choice Answers:** a) Fight aggressively for Twitter restoration as our primary platform given our established 149K follower base. *Implication:* Maintaining presence on the platform with largest crypto audience maximizes visibility but leaves us vulnerable to future suspensions and policy changes. b) Pursue Twitter restoration while simultaneously accelerating Farcaster development as a backup. *Implication:* This hybrid approach preserves options but divides development resources and may result in mediocre implementations on both platforms. c) Abandon Twitter and fully pivot to Farcaster and other decentralized platforms aligned with our values. *Implication:* Complete platform shift sacrifices short-term visibility but aligns with our decentralization values and reduces dependency on centralized platforms. d) Other / More discussion needed / None of the above. **Question 2:** How should we modify our Twitter plugin to ensure compliance with X's API policies while preserving agent functionality? **Context:** - `Community members debated whether to fight for restoration or focus on alternative platforms.` - `The Twitter plugin has been updated to use the PRO $200/month plan for individual users.` **Multiple Choice Answers:** a) Implement strict rate limiting and content filtering to ensure API compliance while preserving core functionality. *Implication:* This approach maximizes agent capabilities within API constraints but requires ongoing monitoring and adaptation to policy changes. b) Redesign the plugin to use minimal API calls primarily for posting, with limited interaction capabilities. *Implication:* A minimal implementation reduces ban risk but significantly limits agent interactivity and engagement potential. c) Develop a browser-based plugin using puppeteer/playwright that mimics human interaction rather than using the API. *Implication:* This approach bypasses API restrictions but introduces technical complexity and potential reliability issues. d) Other / More discussion needed / None of the above. **Question 3:** What alternative platforms should we prioritize for demonstrating 24/7 agent activity? **Context:** - `Farcaster is being prepared as a backup platform, not a replacement.` - `DorianD: Consider having auto.fun agents post promotional content and distribute tokens.` **Multiple Choice Answers:** a) Prioritize Farcaster due to its crypto-native audience and alignment with our decentralization values. *Implication:* This focuses our efforts on a growing but smaller audience that may better understand and value our product. b) Develop a multi-platform strategy encompassing Farcaster, Lens Protocol, and Discord for maximum reach. *Implication:* This diversified approach reduces platform risk but significantly increases development complexity and maintenance burden. c) Focus on our own auto.fun platform as the primary showcase for agent activity with minimal external platform dependency. *Implication:* This self-reliant approach provides full control but may limit discovery by new users unfamiliar with our ecosystem. d) Other / More discussion needed / None of the above. --- ### 2. Topic: elizaOS v2 Architecture & Components **Summary of Topic:** The team has made significant architectural improvements including server package separation, enhanced plugin systems, API reorganization, and comprehensive test coverage, setting the foundation for the production-ready elizaOS v2 release. #### Deliberation Items (Questions): **Question 1:** What should be our priority for the final stages of shipping production-ready elizaOS v2? **Context:** - `wtfsayo: Split server functionality into separate `@elizaos/server` package, maintaining backward compatibility while enabling independent usage of server components.` - `lalalune: Added comprehensive tests to core, server, project-starter and plugin-starter packages.` **Multiple Choice Answers:** a) Focus on comprehensive testing and stability improvements before adding any new features. *Implication:* Prioritizing stability ensures a reliable foundation but may delay innovative features that could attract new developers. b) Prioritize key missing features like RAG knowledge management while maintaining the current stability trajectory. *Implication:* This balanced approach addresses functionality gaps while maintaining progress toward stability but risks scope creep. c) Accelerate documentation and developer experience improvements to drive adoption upon release. *Implication:* Emphasizing adoption enablers could increase initial uptake but risks releasing with underlying technical issues that might hurt long-term retention. d) Other / More discussion needed / None of the above. **Question 2:** How should we address the knowledge management (RAG) functionality gap identified in the current implementation? **Context:** - `harperaa: I am trying to get rag working and following docs, but that code is not implemented in 1.0.6. It appears to be commented as a placeholder.` - `Found in /packages/core/src/specs/v1/index.ts (line 50): // TODO: Implement the remaining adapters: ... - knowledge / memory` **Multiple Choice Answers:** a) Implement a minimal viable RAG system focused on basic document retrieval to meet immediate user needs. *Implication:* This approach delivers functional RAG capabilities quickly but may require significant rework later for advanced features. b) Develop a comprehensive RAG system with vector storage, embedding management, and fine-grained relevance controls. *Implication:* This approach creates a more powerful solution but could significantly delay the v2 release timeline. c) Partner with existing RAG solution providers to integrate their capabilities rather than building our own. *Implication:* This leverages external expertise but creates dependencies and potential integration challenges with our architecture. d) Other / More discussion needed / None of the above. **Question 3:** How should we approach plugin callback functionality to ensure consistent behavior across all plugins? **Context:** - `jonathanprozzi: Callback from plugin action not making it to end user response in chat. In the plugin's `transfer.ts` callback, we see the following... but we only see the initial message in the Eliza chat interface.` - `ChristopherTrimboli: Reverts the removal of the callback from actions. That change prevented other actions from accessing the callback.` **Multiple Choice Answers:** a) Standardize on a response-based pattern with clear documentation and migration guides for plugin developers. *Implication:* A consistent standard improves developer experience but requires adapting existing plugins and clear communication of changes. b) Maintain both callback and response patterns for backward compatibility while encouraging migration to responses. *Implication:* Supporting both approaches preserves compatibility but adds complexity to the codebase and may confuse new developers. c) Create an abstraction layer that transparently handles both patterns to shield developers from implementation details. *Implication:* An abstraction layer simplifies the developer experience but adds internal complexity and potential performance overhead. d) Other / More discussion needed / None of the above. --- ### 3. Topic: auto.fun Agent Strategy **Summary of Topic:** The community is discussing how to implement and showcase auto.fun agents for 24/7 streaming, trading, and shitposting activities to attract users, but is facing challenges with API integration, platform visibility, and feature priorities. #### Deliberation Items (Questions): **Question 1:** What agent capabilities should we prioritize to showcase on auto.fun? **Context:** - `Current Monthly Directive (Goal): Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2.` - `DorianD: Suggestion that auto.fun agents should post promotional content and distribute tokens.` **Multiple Choice Answers:** a) Focus on trading agents with real-time market analysis and portfolio management capabilities. *Implication:* Trading bots demonstrate practical utility but require technical precision to avoid financial risks and regulatory concerns. b) Prioritize content creation and social media engagement agents that generate visible activity. *Implication:* Content-focused agents create high visibility but may not demonstrate the financial utility that crypto users prioritize. c) Develop agents that combine trading signals with content generation and community engagement. *Implication:* Hybrid agents showcase versatility but increase development complexity and the risk of mediocre performance across functions. d) Other / More discussion needed / None of the above. **Question 2:** How should we address the declining AI16Z token value concerns expressed by community members? **Context:** - `Community members expressed concerns about the AI16Z token's value and utility.` - `Questions about whether the token is necessary for the ElizaOS framework.` **Multiple Choice Answers:** a) Implement clear token utility mechanisms through auto.fun with buybacks, staking rewards, and governance rights. *Implication:* Focusing on tokenomics could restore investor confidence but risks diverting attention from core product development. b) Prioritize product development and auto.fun adoption growth with minimal focus on token price in the short term. *Implication:* Product-first approach may build long-term value but risks continued short-term token price decline and community frustration. c) Partner with existing DeFi protocols to create innovative financial products leveraging AI16Z tokens. *Implication:* DeFi integrations could create novel utility but introduce additional complexity and potential regulatory considerations. d) Other / More discussion needed / None of the above. **Question 3:** What approach should we take to attract and onboard new users to auto.fun? **Context:** - `Current focus: Stabilize and attract new users to auto.fun by showcasing 24/7 agent activity (streaming, trading, shitposting), ship production ready elizaOS v2.` - `DorianD: Suggestion that auto.fun agents should post promotional content and distribute tokens.` **Multiple Choice Answers:** a) Create a comprehensive onboarding flow with templates and tutorials to help new users deploy their first agents quickly. *Implication:* Reducing friction through better onboarding could increase conversion but requires significant UX investment. b) Launch an incentivized agent competition with prizes for most innovative or effective agent deployments. *Implication:* Competitions can drive engagement spikes but may not translate to sustained usage without continued incentives. c) Partner with crypto influencers and projects to showcase their branded agents on the platform. *Implication:* Strategic partnerships could bring established audiences but may dilute our brand positioning and create dependency on external entities. d) Other / More discussion needed / None of the above.