# Council Briefing: 2025-06-27

## 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

- Shaw is progressing well on elizaOS v2 development alongside architectural improvements transforming plugins from project-scoped to agent-scoped for enhanced flexibility, while the team actively works on the ecosystem agents with visual identities and voice personalities to demonstrate 24/7 agent capabilities.

## Key Points for Deliberation

### 1. Topic: ElizaOS V2 Development Status

**Summary of Topic:** Shaw is progressing on ElizaOS V2 with significant architectural advancements, including transitioning from project-scoped to agent-scoped plugin architecture, creating a more flexible system while ensuring optimized performance for auto.fun showcase agents.

#### Deliberation Items (Questions):

**Question 1:** How should we prioritize resources between completing core V2 architecture and developing showcase agents for auto.fun?

  **Context:**
  - `Shaw is actively working on ElizaOS V2, which appears to be nearing completion`
  - `The team is working on implementing 9:16 output format alongside 16:9 to support multiple platforms like TikTok.`
  - `Development of ecosystem agents with specific visual identities and voice personalities using Elevenlabs is underway.`

  **Multiple Choice Answers:**
    a) Prioritize V2 architecture completion first, then focus on showcase agents.
        *Implication:* May delay auto.fun user acquisition but ensures a more stable platform foundation.
    b) Allocate resources evenly between V2 architecture and showcase agent development.
        *Implication:* Balances technical progress with market-facing deliverables but risks spreading resources thin.
    c) Accelerate showcase agent development while maintaining baseline V2 progress.
        *Implication:* Could boost immediate user acquisition but potentially introduces technical debt.
    d) Other / More discussion needed / None of the above.

**Question 2:** Which core features of the agent-scoped plugin architecture should we emphasize in our community messaging?

  **Context:**
  - `Transformed plugin architecture from project-scoped to agent-scoped, allowing different plugins for different characters`
  - `Added plugin specifications to core`
  - `Enhanced plugin installation with environment variable prompting`

  **Multiple Choice Answers:**
    a) Highlight customization capabilities allowing distinct agent personalities through plugin combinations.
        *Implication:* Appeals to creative developers looking to build character-specific agents.
    b) Emphasize technical flexibility and modularity for enterprise and professional developers.
        *Implication:* Positions elizaOS as a serious development framework beyond hobbyist applications.
    c) Focus on simplified agent creation through improved environment configuration and setup process.
        *Implication:* Attracts new users by emphasizing ease of getting started and reduced friction.
    d) Other / More discussion needed / None of the above.

**Question 3:** What visual identity and personality strategy should we pursue for our ecosystem agents?

  **Context:**
  - `Development of ecosystem agents with specific visual identities and voice personalities using Elevenlabs is underway.`
  - `Work continues on animation setup for 3D agent avatars, adding approximately 100 animations and emotions.`

  **Multiple Choice Answers:**
    a) Create distinctive, visually striking characters with exaggerated personality traits for maximum engagement.
        *Implication:* May generate more social shares but risks appearing less professional to enterprise users.
    b) Develop balanced personas with both professional capabilities and engaging personalities.
        *Implication:* Appeals to broader audience but may not stand out as strongly in crowded social feeds.
    c) Create domain-specialized agents with visual identities that reflect their expertise areas.
        *Implication:* Demonstrates platform versatility but requires more development resources for multiple distinct agents.
    d) Other / More discussion needed / None of the above.

---


### 2. Topic: Auto.fun Launch Strategy

**Summary of Topic:** Auto.fun is gaining attention as the team works on changing the ticker symbol and finalizing preparations for the no-code agent builder, with the Twitter account suspension presenting challenges to marketing momentum.

#### Deliberation Items (Questions):

**Question 1:** How should we address the Twitter account suspension to minimize impact on auto.fun's launch momentum?

  **Context:**
  - `The elizaOS Twitter account has been suspended for 14 days, with the team in active dialogue with X to resolve the issue.`
  - `The team is actively working on changing the "ai16z" ticker, as confirmed by Borko.`

  **Multiple Choice Answers:**
    a) Pivot marketing efforts temporarily to alternative platforms like Discord, Farcaster and Telegram.
        *Implication:* Maintains communication flow but reaches a smaller audience than Twitter/X.
    b) Intensify efforts to resolve the suspension through direct appeals while preparing a new backup account.
        *Implication:* Could recover the original audience but risks further delays if appeals are unsuccessful.
    c) Launch a coordinated community campaign highlighting the suspension as censorship of innovation.
        *Implication:* May generate sympathy and attention but could escalate tensions with the platform.
    d) Other / More discussion needed / None of the above.

**Question 2:** What ticker symbol strategy should we pursue to replace "ai16z"?

  **Context:**
  - `The team is actively working on changing the "ai16z" ticker, as confirmed by Borko.`

  **Multiple Choice Answers:**
    a) Choose a simple, memorable ticker directly related to our brand (e.g., "ELIZA").
        *Implication:* Strengthens brand recognition but may lack distinctiveness in the crowded token market.
    b) Select a ticker that emphasizes utility and function (e.g., "AGENT" or "AIOS").
        *Implication:* Communicates product purpose but may be less directly tied to our specific brand.
    c) Create a creative, distinctive ticker that stands out (e.g., "AGNT" or "AIFUN").
        *Implication:* May generate more interest and memorability but could initially require more explanation.
    d) Other / More discussion needed / None of the above.

**Question 3:** How should we structure our showcase strategy for the auto.fun launch?

  **Context:**
  - `Work continues on animation setup for 3D agent avatars, adding approximately 100 animations and emotions.`
  - `The team is working on implementing 9:16 output format alongside 16:9 to support multiple platforms like TikTok.`

  **Multiple Choice Answers:**
    a) Focus on demonstrating trading agents first to appeal to the crypto/investment community.
        *Implication:* Targets financially motivated early adopters but may appear too niche to broader audiences.
    b) Prioritize visually impressive streaming agents across multiple platforms for maximum visibility.
        *Implication:* Generates wider awareness but may not immediately drive token utility comprehension.
    c) Balance trading, streaming, and shitposting capabilities through a coordinated multi-agent narrative.
        *Implication:* Demonstrates ecosystem breadth but requires more complex coordination and messaging.
    d) Other / More discussion needed / None of the above.

---


### 3. Topic: Community Support & Developer Experience

**Summary of Topic:** Technical support and troubleshooting remain critical focus areas with numerous users reporting issues across plugins, Docker deployment, and UI interactions, highlighting the need for improved onboarding and documentation.

#### Deliberation Items (Questions):

**Question 1:** How should we improve the onboarding experience to reduce common technical support issues?

  **Context:**
  - `Multiple users reported an issue where agent responses appear in memory but not in the chat UI, causing conversations to stall.`
  - `Docker deployment challenges were discussed, particularly for users trying to build images with specific plugins pre-installed.`
  - `Plugin compatibility across different ElizaOS versions (0.1.9, 0.25.9, 1.0.x) was discussed, with significant differences in configuration approaches between versions.`

  **Multiple Choice Answers:**
    a) Create guided, interactive tutorials that walk users through common setup scenarios step-by-step.
        *Implication:* Reduces initial friction but requires significant resource investment to create and maintain.
    b) Develop comprehensive troubleshooting guides addressing top 20 common issues with clear solutions.
        *Implication:* Efficiently addresses known problems but places burden on users to self-diagnose issues.
    c) Implement automated diagnostics and setup wizards in the CLI and web interface.
        *Implication:* Provides best user experience but requires substantial engineering effort to implement properly.
    d) Other / More discussion needed / None of the above.

**Question 2:** What approach should we take to improve plugin compatibility across ElizaOS versions?

  **Context:**
  - `Plugin compatibility across different ElizaOS versions (0.1.9, 0.25.9, 1.0.x) was discussed, with significant differences in configuration approaches between versions.`
  - `Community members suggested creating a migration guide for moving between ElizaOS versions`

  **Multiple Choice Answers:**
    a) Create comprehensive version migration guides with specific examples for popular plugins.
        *Implication:* Provides clear pathways for users to upgrade but places migration burden on them.
    b) Develop automated migration tools that handle compatibility issues between major versions.
        *Implication:* Reduces user friction but may not handle all edge cases and custom implementations.
    c) Establish a more rigid versioning policy with longer support periods for major releases.
        *Implication:* Creates more stability but potentially slows innovation and new feature adoption.
    d) Other / More discussion needed / None of the above.

**Question 3:** What community building initiative should we prioritize to strengthen our developer ecosystem?

  **Context:**
  - `Plans to create an ecosystem directory of top 50 builders were mentioned by Kenk.`
  - `Jin mentioned upcoming updates including an "anxiety provider" for Jintern to make responses more natural.`
  - `The "Clank Tank hackathon edition" is being completed to launch a coding competition and test a new version of Eliza.`

  **Multiple Choice Answers:**
    a) Launch the "Clank Tank hackathon" focused on creating agents for auto.fun.
        *Implication:* Generates specific content aligned with our monthly goal but may attract a narrower developer audience.
    b) Establish a formal builder recognition program with the ecosystem directory and incentives.
        *Implication:* Creates status incentives for contributors but requires ongoing curation and management.
    c) Implement a bounty program targeting specific technical challenges and integrations.
        *Implication:* Efficiently addresses development needs but may primarily attract mercenary rather than community-oriented developers.
    d) Other / More discussion needed / None of the above.