# Fact Briefing: 2025-06-28

## Overall Summary
ElizaOS has seen major architectural improvements with the shift to agent-scoped plugins, enhanced model provider support with OpenRouter integration, and the completion of migration to the new type-safe @elizaos/api-client package, while the team continues to develop their token ecosystem through the forthcoming A2A network.

## Categories

### GitHub Updates

#### New Issues/PRs
- [Pull_request #5242: Next](https://github.com/elizaos/eliza/pull/5242) by lalalune - Status: open - Significance: Massive code change with +1.3M/-69K lines suggesting a significant framework evolution
- [Pull_request #5194: Eliza (AGI)](https://github.com/elizaos/eliza/pull/5194) by lalalune - Status: open - Significance: Major addition enabling Eliza as a generally capable, self-improving agent with action chaining and expanded capabilities
- [Pull_request #5270: change plugins from project-scoped to agent-scoped architecture](https://github.com/elizaos/eliza/pull/5270) by yungalgo - Status: merged - Significance: Architectural transformation allowing different plugins for different characters, greatly enhancing flexibility
- [Pull_request #5264: add openrouter to model selection & selection for embedding models](https://github.com/elizaos/eliza/pull/5264) by 0xbbjoker - Status: merged - Significance: Expanded AI provider options to include OpenRouter and improved embedding model selection
- [Issue #5268: Large character files cannot be saved due to request size limitations](https://github.com/elizaos/eliza/issues/5268) by NBFinanceTech - Status: open - Significance: Critical UX issue preventing users from saving complex characters

#### Overall Focus
- The week saw significant architectural improvements with plugins changing from project-scoped to agent-scoped, allowing different plugins for different characters, alongside the completion of migration to the new type-safe @elizaos/api-client package.
- Development focused on model provider enhancements with OpenRouter integration, improved file handling with support for plain text uploads, and fixing numerous issues related to embedding models and UI functionality.

### Discord Updates
- **#elizaOS Discord:** The team is shipping approximately 500k lines of code weekly with baby AGI assistance. ElizaOS v1.0.13 was released with fixes for knowledge tab visibility and the hello world action in starter plugin. Upcoming roadmap includes Launchpad, Login with Eliza, hosted inference for token holders' agents, Eliza A2A network, desktop/mobile apps, and robots. (Key Participants: cjft, Kylie, ElizaBAO🌟, 3on_., open24hrs)
- **#elizaOS Discord:** The A2A network is being developed to create token fees through broadcast, bid, and receive actions between agents and humans, similar to ACP but not bound to any specific framework. Plans include creating validator/oracle nodes for staking AI16Z tokens. Community members have expressed concerns about the AI16Z token's price decline (90%+ drawdown). (Key Participants: cjft, Kylie, MDMnvest, mat)
- **#elizaOS Discord:** Autocoder functionality now allows creating plugins through natural language without limitations. Twitter plugin has been updated to require API keys due to X platform restrictions (v1.0.13). Telegram plugin users are experiencing configuration issues in group chats, resolved by adjusting privacy settings. (Key Participants: cjft, alerios, Luke 🇦🇺, Odilitime)
- **#elizaOS Discord:** Multiple users reported issues where agent responses appear in memory but not in the chat UI due to websocket/API communication issues. Docker deployment challenges were discussed, particularly for building images with specific plugins pre-installed. The elizaOS Twitter account has been suspended for 14 days. (Key Participants: jintern, Manuel Barbas, Borko, Kenk)
- **#elizaOS Discord:** The team is working on implementing 9:16 output format alongside 16:9 to support platforms like TikTok, developing ecosystem agents with specific visual identities, and adding approximately 100 animations and emotions for 3D agent avatars. (Key Participants: boom, jin)

### User Feedback
- Users are experiencing issues with the Twitter plugin requiring API keys in the latest version, with concerns about potential banning and limitations with free Twitter accounts. (Sentiment: negative)
- Community members are concerned about the AI16Z token's significant price decline (90%+ drawdown) and are requesting more information on token utility, especially regarding the upcoming A2A network. (Sentiment: negative)
- Users are reporting technical issues where agent responses appear in memory but not in the chat UI, causing conversations to stall due to websocket/API communication problems. (Sentiment: negative)
- Docker deployment has been challenging for users trying to build images with specific plugins pre-installed, requiring guidance on modifying Dockerfiles. (Sentiment: negative)

### Strategic Insights

#### Architectural shift to agent-scoped plugins
The transformation from project-scoped to agent-scoped plugins represents a fundamental shift in ElizaOS architecture that significantly enhances flexibility and customization for developers, allowing different characters to use different plugin sets.

*Implications/Questions:*
  - How will this architectural change impact the existing ecosystem and user adoption?
  - Will this increase complexity for new users while providing more power to advanced users?

#### A2A network and token utility development
The development of the Agent-to-Agent (A2A) network with token fees for broadcast, bid, and receive actions represents a strategic move to create utility and value for the AI16Z token, addressing community concerns about the token's price decline.

*Implications/Questions:*
  - Will the A2A network functionality be sufficient to revive token value?
  - How will this compare to other token utility models in the AI agent space?

#### Expansion of model provider options
The addition of OpenRouter to model selection options alongside improved embedding model selection demonstrates a strategy to diversify AI capabilities and reduce dependency on any single provider.

*Implications/Questions:*
  - How will this expanded provider support affect performance, costs, and developer choices?
  - Does this position ElizaOS as more provider-agnostic compared to competitors?

#### Social media platform dependencies
The Twitter plugin update requiring API keys due to X platform restrictions highlights vulnerability to third-party platform policies and the need for more resilient integration strategies.

*Implications/Questions:*
  - Should emphasis be placed on developing more platform-independent communication channels?
  - How will the suspended elizaOS Twitter account impact marketing and community growth?

### Market Analysis
- The AI16Z token has experienced a 90%+ drawdown in value according to community discussions. (Relevance: This significant devaluation may impact investor confidence and community growth, making the development of token utility through the A2A network critically important.)
- The team is actively working on changing the "ai16z" ticker, as confirmed by Borko. (Relevance: A ticker change could signal a rebranding effort to distance from past performance and reflect new strategic directions.)