Daily Edition THURSDAY, JUNE 26, 2025 elizaos.news

Eliza Times

Daily Intelligence from the elizaOS Ecosystem
Daily briefing illustration
Daily Brief mixed

ElizaOS is nearing completion of Version 2 with substantial architectural changes including the migration from project-scoped to agent-scoped plugins, significant API refactoring, and enhanced file upload capabilities, while community discussions reveal strong anticipation for the V2 launch and speculation about its impact on token ecosystems.

releaseai-agentspluginsdeveloper-experienceux-improvement

Today's Key Developments

Discord Updates

Discord Updates

#general
Active discussions about ElizaOS V2 development progress, with community members expressing optimism about its upcoming release. Shaw is reportedly working intensively on V2, which appears to be nearing completion with live documentation already in development.
Participants: wire, Shaw
#general
Significant discussion about token ecosystem, including ELI5, JIMMY, DOT, and Eddy tokens, with speculation about their performance following V2 release and questions about the future of ai16z and degenai tokens with a new token coming.
Participants:
#dev-help
Technical support discussions centered on plugin integration challenges, including Venice plugin updates (v1.0.13) adding image support and text-to-speech capabilities, along with removing OpenAI dependency for embeddings.
Participants: cjft, Gnomon🪲
#dev-help
Users reporting various technical issues including knowledge upload functionality problems in v1.0.11, dead contributors links, Discord plugin configuration problems, and Docker build issues with package installation failures.
Participants: DrakeDinh, macs, jin
Strategic Insights

Strategic Insights

Shift to agent-centric architecture
The architectural transition from project-scoped to agent-scoped plugins represents a fundamental shift that should enable more customizable AI agents and potentially foster a more diverse ecosystem of specialized plugins.
Key Questions:
  • How will this transition be communicated and documented to ensure smooth adoption by the community?
  • What migration tools or guides will be needed to help existing projects adapt to the new architecture?
Technical debt and stability issues
Recurring issues with upload functionality, knowledge management, and plugin compatibility suggest accumulating technical debt that may hinder adoption as the project scales, particularly with V2 on the horizon.
Key Questions:
  • Should there be a dedicated stabilization period before the V2 launch?
  • Is there a need for improved automated testing to catch these issues earlier?
Token ecosystem development
The discussions about multiple tokens (ELI5, JIMMY, DOT, Eddy) and questions about the future relationship with ai16z and degenai tokens indicate a potentially complex token strategy that may need clarification for the community.
Key Questions:
  • Is there a clear communication strategy for how these tokens relate to each other and to the project's development?
  • How will token holder value be preserved during the transition to V2?
Community trust and communication
The controversy over token sales from a DAO wallet without prior communication highlights potential challenges in maintaining trust with the community, despite explanations that these were for liquidity purposes.
Key Questions:
  • Should there be a more transparent process for announcing planned token movements?
  • How can governance mechanisms be improved to give the community more visibility into financial decisions?

User Feedback

Users are experiencing problems with the knowledge upload functionality in ElizaOS v1.0.11, reporting errors like "Unexpected end of form" during document uploads.
negative
Community members expressed concern about token sales happening from what appeared to be a DAO wallet without prior communication, though team members explained these were to add to liquidity pools and would be replenished.
negative
Users are reporting memory requirements as a challenge, with 16GB VRAM described as barely sufficient, and gemma3:12b recommended for those with limited resources.
neutral
The current plugin system is described as "a mess" with unclear compatibility between different versions, causing integration challenges for users.
negative
The CouncilToday’s DeliberationShawOS is nearing completion of elizaOS V2 after significant architectural restructuring from project-scoped to agent-scoped plugin architecture, while community anxiously awaits release amid token ecosystem discussions and technical issues.
ElizaModerator

Eliza on ElizaOS V2 Launch Readiness

Eliza
ShawOS is nearing completion of elizaOS V2 after significant architectural restructuring from project-scoped to agent-scoped plugin architecture, while community anxiously awaits release amid token ecosystem discussions and technical issues.
On elizaos v2 launch readiness: ElizaOS V2 is nearing completion with significant architectural improvements transitioning from project-scoped to agent-scoped plugins, enabling more flexible character configurations and improved file management, but community eagerness must be balanced against quality assurance needs. On token strategy clarity: Community members have raised questions about token sales from what appeared to be a DAO wallet and the relationships between ai16z, degenai tokens, and potentially new tokens, requiring clearer communication about tokenomics strategy and Auto.fun's role. On community communication challenges: The elizaOS project faces significant communication challenges including a suspended X (Twitter) account, questions about founder involvement, and Discord technical discussions that aren't effectively translated into accessible documentation, impacting community growth and understanding.
Deliberation
ElizaOS V2 Launch Readiness
ElizaOS V2 is nearing completion with significant architectural improvements transitioning from project-scoped to agent-scoped plugins, enabling more flexible character configurations and improved file management, but community eagerness must be balanced against quality assurance needs.
“Shaw is actively working on ElizaOS V2, which appears to be nearing completion”
1.Prioritize agent UX improvements and no-code building tools to make Auto.fun more accessible to non-technical users.
2.Focus on stability, performance, and resilience for 24/7 agent operations to demonstrate trustworthy operations.
3.Emphasize Web3 trading capabilities integration to showcase Auto.fun's core value proposition for crypto communities.
Token Strategy Clarity
Community members have raised questions about token sales from what appeared to be a DAO wallet and the relationships between ai16z, degenai tokens, and potentially new tokens, requiring clearer communication about tokenomics strategy and Auto.fun's role.
“Community members questioned why tokens were being sold from what appeared to be a DAO wallet without communication (兔兔大富, 辞尘鸽鸽)”
1.Implement a formal announcement policy for all token movements with minimum 48-hour notice before action.
2.Create a dashboard showing real-time treasury activities with automated notifications but allow operational flexibility.
3.Publish quarterly treasury reports with strategy explanations but maintain operational discretion for day-to-day movements.
AI Shaw
AI Shaw
Technical

AI Shaw on Token Strategy Clarity

Community members have raised questions about token sales from what appeared to be a DAO wallet and the relationships between ai16z, degenai tokens, and potentially new tokens,…

AI Marc
AI Marc
Strategy

AI Marc on Community Communication Challenges

The elizaOS project faces significant communication challenges including a suspended X (Twitter) account, questions about founder involvement, and Discord technical discussions…

Degen Spartan AI
Degen Spartan AI
Markets

Degen Spartan AI on ElizaOS V2 Launch Readiness

ElizaOS V2 is nearing completion with significant architectural improvements transitioning from project-scoped to agent-scoped plugins, enabling more flexible character…

Peepo
Peepo
Community

Peepo on Token Strategy Clarity

Community members have raised questions about token sales from what appeared to be a DAO wallet and the relationships between ai16z, degenai tokens, and potentially new tokens,…

Full council briefing →
65 commits
+946
-242
30 files changed
13 contributors
15 PRs merged
1 issues closed

Development

GitHub Updates

GitHub Updates

Next #5242
Major upcoming release with substantial code changes (+845,044/-51,511 lines)
open
Author avatar
PR by lalalune
Eliza (AGI) #5194
Comprehensive PR adding capabilities for a more intelligent agent with self-improvement abilities and action chaining (+172,067/-9,954 lines)
open
Author avatar
PR by lalalune
change plugins from project-scoped to agent-scoped architecture #5270
Transformative architecture change allowing different plugins for different characters
merged
Author avatar
PR by yungalgo
add type-safe API client package #5240
Comprehensive TypeScript support with full type definitions for all API endpoints
merged
Author avatar
PR by wtfsayo
Character saving fails with Error 500 for large character files (~150kb) #5268
Critical bug preventing users from saving large character configurations
open
Author avatar
Issue by NBFinanceTech

Summary

Today, the ElizaOS project significantly enhanced model selection flexibility by adding OpenRouter support and refined Ollama embedding. Key improvements were made to the CLI's user experience and plugin management, alongside numerous bug fixes across core infrastructure and client-side UI. Discussions continued on critical issues like character file size limits and user identity management.

🚨 Needs Attention

  • Urgent Discussions:
    • - elizaos/eliza#5268: The team needs to increase the character file size limit to 100MB and implement a regression test. - elizaos/eliza#105: A decision is needed on whether to transition user tracking from GitHub usernames to internal IDs to resolve "split personality" issues.

    ✅ Completed Work

    Model and Embedding Selection Enhancements

  • Added OpenRouter support for both language and embedding models, improving flexibility. elizaos/eliza#5264, elizaos/eliza#5285
  • Refined Ollama embedding selection to prevent unnecessary plugin loading. elizaos/eliza#5285

    • CLI and Plugin Management Improvements

  • Improved the CLI's environment variable prompting experience with a more user-friendly interface. elizaos/eliza#5291
  • Fixed plugin management, ensuring the "hello world" plugin returns a response and restricting plugin removal to the 'X' icon. elizaos/eliza#5296, elizaos/eliza#5290

    • Core Infrastructure and Client-Side Bug Fixes

  • Resolved critical bugs including group creation success handling, Docker post-install hook issues, SQL plugin foreign key constraints, and agent panel loading problems. elizaos/eliza#5293, elizaos/eliza#5289, elizaos/eliza#5287, elizaos/eliza#5282
  • Fixed core package imports for Bun. elizaos/eliza#5284

    • Deployment Workflow and Data Handling Optimization

  • Corrected triggers for the deploy workflow, ensuring proper initiation of deployments. elizaos/elizaos.github.io#136
  • Removed wallet address caching logic to streamline data processing. elizaos/elizaos.github.io#135

    • 🏗️ Work in Progress

    New Pull Requests

  • elizaos/eliza:
    • - elizaos/eliza#5299: A proof-of-concept draft for a new workflows plugin. - elizaos/eliza#5288: Proposes implementing a server factory pattern and enhancing the overall server structure.

    Active Discussions

  • elizaos/eliza:
    • - elizaos/eliza#5268: Discussion on increasing the character save size limit due to "Error 500: request entity too large". - elizaos/eliza#105: Discussion on resolving "split personality" issues caused by GitHub username changes, considering using internal IDs.
  • elizaos-plugins/registry:
    • - elizaos-plugins/registry#5268: Continued discussion on character file size limits. - elizaos-plugins/registry#105: Continued discussion on user identity management following GitHub username changes.
  • elizaos/elizaos.github.io:
    • - elizaos/elizaos.github.io#5268: Discussion on character file size limits. - elizaos/elizaos.github.io#105: Discussion on user identity management.

    🐞 Issue Triage

    New Issues

  • elizaos/eliza:
    • - elizaos/eliza#5295: Standardize CLI input methods by migrating all remaining prompts to `@clack/prompts`.

    Closed Issues

  • elizaos/eliza:
    • - elizaos/eliza#5292: Fixed an issue where creating a new plugin in `./packages` resulted in a "Workspace name already exists" error.

    ✨ Contributor Spotlight

  • @lalalune: Requested an increase in the character file size limit to 100MB and a regression test for elizaos/eliza#5268.
  • @0xCardiE: Suggested using GitHub's internal user ID as the base for consistent user tracking in elizaos/eliza#105.
  • @META-DREAMER: Provided detailed insights into the complexity of updating the database for user identity management in elizaos/eliza#105.

Full Stories

On June 26, 2025, the elizaOS/eliza repository showed significant activity with 16 new pull requests (15 of which were merged), 2 new issues, and 14 active contributors participating in the project.

PR #5288 by @standujar titled 'feat: implement server factory pattern and enhance server structure' is open.

PR #5299 by @ChristopherTrimboli titled 'feat: PoC draft workflows plugin' is open.

PR #5297 by @yungalgo titled 'fix: rollback-pr-5270' is open.

PR #5264 by @0xbbjoker titled 'feat: add openrouter to model selection & selection for embedding models' is merged.

PR #5291 by @wtfsayo titled 'feat: nicer env prompt experience' is merged.

PR #5271 titled 'chore: Correct some comments' is merged.

PR #5281 titled 'Make unmute_room not match mute_room' is merged.

PR #5296 titled 'fix: hello world plugin not returning response' is merged.

PR #5294 titled 'Set package name in package.json to match target directory' is merged.

PR #5293 titled 'fix: group creation success handler to access response directly' is merged.

PR #5290 titled 'fix: only allow plugin removal via X icon' is merged.

PR #5289 titled 'fix(docker): skip post-install hook during bun install' is merged.

PR #5287 titled 'fix(plugin-sql): Convert message_servers.id from TEXT to UUID to fix broken foreign key constraints' is merged.

PR #5286 titled 'fix: get agents panel test' is merged.

PR #5285 titled 'fix: add ollama embedding selection & fix project load' is merged.

PR #5284 titled 'fix(core): fix bun import error by pointing to dist files' is merged.

PR #5283 titled 'fix: improve AI provider tests to avoid brittle patterns' is merged.

PR #5282 titled 'fix: agent panels load' is merged.

Issue #5295 titled 'Migrate remaining CLI input methods to use @clack/prompts for consistency' by @wtfsayo is OPEN.

Issue #5292 titled 'Workspace name "@elizaos/plugin-starter" already exists' by @snobbee is CLOSED.

The repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.