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
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
Closed Issues