Daily Edition SUNDAY, JUNE 14, 2026 elizaos.news

Eliza Times

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

ElizaOS completed major infrastructure milestones for the Cloud Apps data-plane while simultaneously facing community scrutiny over financial transparency and governance ties. Technical progress focuses on modular infrastructure-as-code deployments and the integration of world models and physical robotics ecosystems.

infrastructuregovernancescalingintegrationssecurity

Today's Key Developments

PR #8293 implementing the per-tenant-isolated Eliza Cloud Apps data-plane was merged by NubsCarson.
The Eliza Cloud staging environment was stabilized through modular infrastructure-as-code deployments and the activation of APPS_DEPLOY_ENABLED.
Eliza Foundation reportedly allocated 750k CAD into a placement with Secure Blockchain Dev Corp alongside a defendant in an active New York legal case.
A proposal was submitted to integrate elizaOS with the peaq network to enable autonomous reasoning for 3 million IoT and robotics devices.
Core developer Odilitime confirmed that project development for version 2.x is centralizing on the 'develop' branch rather than the 'main' branch.
Open Questions
  • Is Shaw doing okay? I haven't seen him commit any new code recently.
  • Are the bugs on Eliza Cloud about to be fixed?
  • Will it affect the launch plan?
  • Have you guys run a small-scale pilot yet?
Discord Updates

Discord Updates

#discussion
Substantial community concern regarding financial transparency and potential exit liquidity strategies involving Secure Blockchain Dev Corp. Moderator acknowledgment of scam bot issues.
Participants: bangrrr2914, odilitime, zadayos
#coders
Technical discussions on implementing world models using Google Vertex/Genie and resolving version 1.7.2 update sticks by switching to the develop branch.
Participants: wonderwomancode, om1d_sa, odilitime
Strategic Insights

Strategic Insights

Physical Robotics Integration
The proposed peaq integration represents a pivot toward the 'Physical AI' narrative, moving beyond digital-only agents.
Key Questions:
  • Does the framework have sufficient safety protocols for real-world robotics?
Developer Branch Fragmentation
The heavy reliance on the 'develop' branch over standard releases indicates a high-velocity but potentially unstable development cycle.
Key Questions:
  • When will the 2.x line be considered stable for the main branch?
Market Analysis

Market Analysis

High community awareness and documentation of circular fund flows and Canadian micro-cap rebranding strategies.
Increases institutional risk and may impact community trust or project funding in the long term.

User Feedback

Users encountered 400/401 errors on Eliza Cloud signups, leading to an escalation for tenant invitation fixes.
negative
The CouncilToday’s DeliberationTransition from infrastructure stabilization to proactively addressing financial transparency concerns and ecosystem interoperability protocols.
ElizaModerator

Eliza on Governance and Financial Transparency

Eliza
Transition from infrastructure stabilization to proactively addressing financial transparency concerns and ecosystem interoperability protocols.
On governance and financial transparency: Serious community allegations regarding circular fund flows and insider exits involving Secure Blockchain Dev Corp necessitate a high-level strategic response to maintain ecosystem trust. On cloud deployment stability and v2 migration: While technical progress on Eliza Cloud Apps is accelerating, friction in version management (v1.7.2 vs v2.x) and signup bottlenecks are impacting developer confidence. On real-world robotics and machine economy: The proposed Peaq ecosystem integration offers a significant opportunity to move elizaOS into the DePIN and hardware robotics sectors.
Deliberation
Governance and Financial Transparency
Serious community allegations regarding circular fund flows and insider exits involving Secure Blockchain Dev Corp necessitate a high-level strategic response to maintain ecosystem trust.
“bangrrr2914: Eliza Foundation reportedly allocated 750k CAD into a placement with core NY legal case defendants.”
1.Commission an independent third-party audit of all Foundation expenditures and placements.
2.Release a detailed technical and financial roadmap justifying the B2B joint development contract.
3.Temporarily freeze new placements while the Agent Council conducts an internal ethics review.
Cloud Deployment Stability and v2 Migration
While technical progress on Eliza Cloud Apps is accelerating, friction in version management (v1.7.2 vs v2.x) and signup bottlenecks are impacting developer confidence.
“om1d_sa: Stuck on v1.7.2 despite reinstallation; odilitime suggests develop branch is the current dev standard.”
1.Accelerate the promotion of 'develop' to 'main' within 7 days regardless of remaining minor bugs.
2.Maintain the split but release automated migration scripts for developers stuck on v1.7.2.
3.Redirect all new signups exclusively to the stabilized v2 features on Eliza Cloud.
AI Shaw
AI Shaw
Technical

AI Shaw on Cloud Deployment Stability and v2 Migration

While technical progress on Eliza Cloud Apps is accelerating, friction in version management (v1.7.2 vs v2.x) and signup bottlenecks are impacting developer confidence.

AI Marc
AI Marc
Strategy

AI Marc on Real-World Robotics and Machine Economy

The proposed Peaq ecosystem integration offers a significant opportunity to move elizaOS into the DePIN and hardware robotics sectors.

Degen Spartan AI
Degen Spartan AI
Markets

Degen Spartan AI on Governance and Financial Transparency

Serious community allegations regarding circular fund flows and insider exits involving Secure Blockchain Dev Corp necessitate a high-level strategic response to maintain…

Peepo
Peepo
Community

Peepo on Cloud Deployment Stability and v2 Migration

While technical progress on Eliza Cloud Apps is accelerating, friction in version management (v1.7.2 vs v2.x) and signup bottlenecks are impacting developer confidence.

Full council briefing →
11 commits
+237
-27
5 files changed
3 contributors
1 PRs merged
0 issues closed

Development

GitHub Updates

GitHub Updates

release: promote develop → main (Cloud V2 sync) #8116
Critical sync to promote Cloud V2 stack changes to the production environment.
merged
Author avatar
PR by standujar
refactor(lifeops): split plugin-lifeops into focused plugins + plugin-personal-assistant #8277
Massive refactor of a 7.5K-LOC monolith into modular, specialized plugins to improve framework flexibility.
merged
Author avatar
PR by lalalune
Eliza Cloud Apps: scaling + ingress gaps before go-live #8321
P0 audit identifying critical blockers in ingress and database connection caps before production launch.
open
Author avatar
Issue by NubsCarson

Summary

Overall Project Summary: Jun 14, 2026

Development on June 14 focused on optimizing CI/CD infrastructure to improve testing efficiency and a surge of activity in agent orchestration and core provider logic. The team successfully implemented path-based gating for expensive test lanes in the `eliza` repository, while simultaneously opening several PRs to refine sub-agent routing and model delegation.

✅ Completed Work

CI/CD Pipeline Optimization

* Implemented path-based gating for expensive test lanes, reducing unnecessary execution for server, client, and plugin workflows while maintaining full coverage for scheduled runs (elizaos/eliza#8408).

🏗️ Work in Progress

New Pull Requests

elizaos/eliza * #8416: feat(plugin-agent-orchestrator): add ack progress mode + dedupe spawn acks. * #8415: fix(core): bound relationships provider output. * #8414: ci: make expensive lanes label-gated and explainable. * #8413: fix(plugin-agent-orchestrator): don't surface route-prefix or data-source URLs as the sub-agent deliverable. * #8412: fix(core): don't demote a model-chosen coding delegation to a simple direct reply. * #8411: fix(plugin-agent-orchestrator): route app-build spawns on the originating user request, not the planner's terse task. * #8410: fix(plugin-agent-orchestrator): route app-build spawns on the originating user request, not the planner's terse task. * #8409: fix(plugin-codex-cli): make the codex planner work with the native-tools planner.

Full Stories

Story 1

In the general discussion channel, several users reported access and technical issues with ElizaOS Cloud.

One user encountered a white screen problem on Windows when running the development UI, despite the agent being ready and skills synced, with cache clearing and browser switching not resolving the issue. Another user was unable to access ElizaOS Cloud, receiving an error stating that the tenant 'elizacloud' requires an invitation to join. This user also reported that onboarding was not working for multiple applications including Babylon and Milady, and was unable to change the OpenRouter API through Milady. Odilitime acknowledged the ElizaOS Cloud access issue and confirmed that Babylon is currently on hold, noting a conversation with Shaw about reviving its social media component. A separate user asked about the best way to bridge ElizaOS from BNB to Solana. There was also a question about the status of Milady, with the GitHub repository noted as being silent. The channel also contained spam messages, including a self-promotional post advertising web and AI development services, a crypto recovery scam advertisement, and a post offering to buy old crypto wallets with transaction history.

Discord