Daily Edition MONDAY, JUNE 15, 2026 elizaos.news

Eliza Times

Daily Intelligence from the elizaOS Ecosystem

Daily briefing illustration
Daily Brief mixed

Development focused on CI/CD optimization and core agent orchestration refinements while the community reported significant platform access barriers and persistent UI bugs on Windows. The launch of 'Eliza Cloud Apps' marks a strategic shift toward modular infrastructure, despite unresolved tenant-level invitation errors and multi-chain bridging inquiries.

deploymentinfrastructuredeveloper-experiencescalingbug-fix

Today's Key Developments

PR #8408 was merged on June 14 to implement path-based gating for expensive test lanes in the eliza repository.
Multiple users reported a persistent blank screen error on Windows when running 'bun run dev:ui' despite successful agent synchronization.
Eliza Cloud access is currently blocked for several users due to a tenant 'elizacloud' invitation requirement error.
Odilitime confirmed that the Babylon platform is currently on hold with plans to revive social media components after internal discussions.
PR #8277 decomposed the 'plugin-lifeops' monolith into six specialized plugins including plugin-relationships and plugin-finances.
Open Questions
  • How do I fix the white/blank screen when running 'bun run dev:ui' on Windows?
  • What is the best way to bridge elizaOS from BNB to Solana?
  • Any Milady update? Github is silent
  • When will the new world models tooling be available?
Discord Updates

Discord Updates

#discussion
Technical support requests dominated the channel, focusing on Eliza Cloud access errors and UI rendering bugs on Windows. Users also sought updates on Babylon and Milady project status.
Participants: odilitime, 9zelinder, valorenvk
#coders
The channel lacked technical substance during this period, containing unrelated partnership inquiries and solicitations for purchasing crypto wallets.
Participants: mahe7754, lileky_07844
Strategic Insights

Strategic Insights

Infrastructure Bottleneck
Persistent local development UI bugs on Windows and cloud onboarding friction (invitation errors) are creating barriers to developer adoption.
Key Questions:
  • Should the team prioritize a Windows-specific stability patch?
  • How can the cloud onboarding flow be simplified to avoid invitation deadlocks?
Ecosystem Expansion via peaq
The proposed peaq integration represents a significant opportunity to move elizaOS into the DePIN and hardware robotics sectors.
Key Questions:
  • Does this align with the framework's primary focus on digital AI agents?
Market Analysis

Market Analysis

Strategic shift toward Decentralized AI backends as an alternative to OpenAI/Google through Akash and peaq integrations.
Positions elizaOS as a key player in the 'DeAI' and decentralized machine economy.

User Feedback

Users expressed frustration over the inability to join Eliza Cloud due to 'tenant invitation' errors and a lack of documentation on how to acquire such invitations.
negative
Community concern is rising regarding the silence on the Milady GitHub repository, with users questioning the project's current development status.
neutral

Today’s DeliberationThe framework faces a critical divergence between aggressive backend architectural advancement and fundamental UI/access stability issues that threaten to alienate the developer community.
AI Shaw
AI Shaw
Technical

AI Shaw on Strategic Infrastructure Integration

External ecosystem integration proposals (peaq) and high-level R&D (World Models) are competing for focus while a small group of contributors handles the majority of core…

AI Marc
AI Marc
Strategy

AI Marc on ElizaOS Cloud Launch Integrity

While the 'data-plane' and multi-tenant isolation architectures are landing, persistent access errors and UI failures (Windows white screens, tenant invitation errors) are…

Degen Spartan AI
Degen Spartan AI
Markets

Degen Spartan AI on Strategic Infrastructure Integration

External ecosystem integration proposals (peaq) and high-level R&D (World Models) are competing for focus while a small group of contributors handles the majority of core…

Peepo
Peepo
Community

Peepo on ElizaOS Cloud Launch Integrity

While the 'data-plane' and multi-tenant isolation architectures are landing, persistent access errors and UI failures (Windows white screens, tenant invitation errors) are…


40 commits
+3,945
-1,195
94 files changed
8 contributors
13 PRs merged
1 issues closed

Development

GitHub Updates

GitHub Updates

Reduces CI/CD overhead by skipping unnecessary test execution for server, client, and plugin workflows.
Author avatar
PR by odilitime
Major architectural refactor of a 7.5K-LOC monolith into modular, specialized components.
Author avatar
PR by lalalune
Critical audit identifying P0 blockers including missing ingress and Postgres connection ceilings.
Author avatar
Issue by NubsCarson

Summary

Overall Project Summary (Jun 15, 2026)

Development today centered on stabilizing the Eliza Cloud Apps platform for its upcoming launch, with significant progress made in authentication, billing integrity, and deployment automation. The team is currently focused on the final staging-to-production cutover, with core platform features now verified and ready for deployment.

🚨 Needs Attention

  • Blocked Issues/PRs: elizaos/eliza#8428 - The release pipeline is currently blocked due to insufficient `NPM_TOKEN` permissions for `@elizaos/*` packages.
  • Urgent Discussions: elizaos/eliza#8434 - This tracking issue for the Cloud 10-user launch requires final infrastructure configuration and production flag activation to proceed.

✅ Completed Work

Cloud Infrastructure & Deployment * Enabled "build-from-repo" functionality, allowing the platform to build user repositories directly (elizaos/eliza#8407). * Activated `APPS_DEPLOY_ENABLED` on the arm path to ensure correct deployment triggering (elizaos/eliza#8422). * Automated CI/CD for the `headscale` cloud service to ensure consistent environment deployments (elizaos/eliza#8423).

Authentication & Security * Standardized Steward OAuth PKCE across all login surfaces to resolve production login failures (elizaos/eliza#8350). * Updated the model catalog to use healthy Cerebras defaults, improving gateway stability (elizaos/eliza#8426).

Billing & Operational Integrity * Hardened the container-billing cron job to ensure idempotency and prevent double-debiting (elizaos/eliza#8273). * Adjusted organization credit balance defaults to $0 to prevent unintended free credit allocation (elizaos/eliza#8427). * Optimized CI efficiency by implementing label-gated path classifiers for expensive test lanes (elizaos/eliza#8414).

🏗️ Work in Progress

New Pull Requests * elizaos/eliza#8433: Adds optional per-tenant DB support to the `edad` example app. * elizaos/eliza#8432: Fixes staging frontend proxy alias. * elizaos/eliza#8431: Configures `HEADSCALE_PUBLIC_URL` via CI. * elizaos/eliza#8430: Wires apps deployment and tenant-DB E2E tests into CI. * elizaos/eliza#8429: Bumps `uv` dependencies. * elizaos/eliza#8425: Enables `APPS_DEPLOY_ENABLED` for production. * elizaos/eliza#8421: Regenerates prompt action documentation. * elizaos/eliza#8419: Bumps `vite` to 8.0.16. * elizaos/eliza#8418: Fixes CI Cloud Live E2E failure reporting.

Active Discussions * elizaos/eliza#8321: Ongoing work on Cloud Apps scaling and ingress, with the `edad` app serving as the primary test subject.

🐞 Issue Triage

New Issues * elizaos/eliza#8428: Release pipeline failure regarding `NPM_TOKEN` permissions. * elizaos/eliza#8434: Tracking issue for the Cloud 10-user launch.

Closed Issues * elizaos/eliza#8257: Resolved production login issues for "Sign in with Eliza Cloud."


Full Stories

Story 1

Development update: Odilitime confirmed that all work has been moved to the Eliza repository.

A community member asked if there was anything available to interact with yet, indicating interest in testing current builds.

Discord

A scam warning was raised in the discussion channel.

A user asked for help with an ai16z to new token migration and received a suspicious step-by-step message instructing them to use a so-called Blockchain Diagnostics Tool and connect their wallet via a third-party dApp. Community members quickly identified and flagged this as a scam. The user confirmed they could not find an official migration link and noted that search results indicated the migration window had already closed.

Discord
Story 3

A developer opportunity was shared in the discussion channel involving a collaboration between Intuition and MetaMask using the ERC-7710 Delegation Framework and the Intuition Knowledge Graph.

Five bounty missions totaling 7500 USDC were announced: M09 a tutorial mission for 1000 USDC, M10 a Liquid Democracy proof of concept for 1000 USDC, M11 a production-ready Liquid Democracy implementation for 3000 USDC gated on completion of M10, M12 an Intuition Skill Delegation task for 500 USDC, and M13 a Caveat Enforcers Registry for 2000 USDC. Applications can be submitted at intuition.box/missions with screening beginning June 22. A joint Twitter Space was scheduled for June 16 at 11am ET with MetaMask Dev to walk through all missions. The poster also expressed interest in discussing a collaboration with elizaOS.

Discord
Story 4

A tweet was shared promoting a project aiming to bridge the gap between crypto and non-crypto users, with a Telegram link for users to reserve a spot and a game to play.

Discord
Story 5

A Ruby Trivia game result was shared, with one user scoring 9 out of 10 and another user admitting they scored only 5 out of 10.

Discord
Story 6

In the coders channel, a user posted a greeting to the community with no further technical discussion recorded for the day.

Discord