{
  "version": "1.0",
  "type": "repository",
  "interval": "week",
  "date": "2026-04-26",
  "generatedAt": "2026-05-14T23:36:28.448Z",
  "sourceLastUpdated": "2026-05-14T23:36:28.448Z",
  "contentFormat": "markdown",
  "contentHash": "76cfb67470371b19aa2a4b5c42f35d2872da7eb75c637a5306ff999f565bda41",
  "entity": {
    "repoId": "elizaos/cloud",
    "owner": "elizaos",
    "repo": "cloud"
  },
  "content": "# elizaos/cloud Weekly Report (Apr 26 - May 2, 2026)\n\n## 🚀 Highlights\nThis week, the ElizaOS Cloud project underwent a major architectural transformation, shifting from a Next.js-based stack to a Vite SPA with Hono Workers. Development was characterized by a aggressive push toward infrastructure modernization, including the removal of Vercel AI Gateway in favor of OpenRouter and a migration to R2 storage. Alongside these structural changes, the team made significant progress on monetization infrastructure and runtime stability, ensuring that the platform remains robust as it scales toward a more decentralized, modular framework.\n\n## 🛠️ Key Developments\n\n### Architecture & Infrastructure Migration\nThe project completed a significant architectural pivot to improve performance and deployment flexibility.\n*   **Vite & Hono Migration:** The codebase was successfully migrated from Next.js to a Vite SPA with Hono Workers ([#484](https://github.com/elizaos/cloud/pull/484)).\n*   **Cloudflare & Storage:** Preparations for the Cloudflare cutover included implementing a shadow stack ([#487](https://github.com/elizaos/cloud/pull/487)) and migrating image generation storage from `@vercel/blob` to R2 ([#489](https://github.com/elizaos/cloud/pull/489)).\n*   **AI Provider Refactor:** The Vercel AI Gateway dependency was fully removed, with OpenRouter established as the primary provider, supported by OpenAI and Anthropic failovers ([#482](https://github.com/elizaos/cloud/pull/482)).\n\n### Monetization & Billing\nNew infrastructure was implemented to support organizational credit management and pay-as-you-go hosting.\n*   **Earnings-Based Funding:** Systems were updated to allow hosting bills to be settled via `redeemable_earnings` before tapping into `credit_balance` ([#477](https://github.com/elizaos/cloud/pull/477)).\n*   **Service Updates:** The `appCreditsService` was reworked to support monetized applications, including new database schema updates for credit conversion ledgers ([#474](https://github.com/elizaos/cloud/pull/474), [#478](https://github.com/elizaos/cloud/pull/478)).\n\n### Milady LifeOps & Authentication\n*   **Calendar Integration:** Added support for listing managed Google calendars to improve connectivity for secondary calendars ([#472](https://github.com/elizaos/cloud/pull/472)).\n*   **Auth Stability:** Resolved CLI login hangs caused by stale Steward or Privy tokens by implementing an auto-clear mechanism on 401 errors ([#480](https://github.com/elizaos/cloud/pull/480)).\n\n## 🐛 Issues & Triage\n\n### Closed Issues\nThe team addressed several critical runtime and integration bugs:\n*   **Runtime Stability:** Introduced `NoModelProviderConfiguredError` for better feedback ([#7203](https://github.com/elizaos/cloud/issues/7203)) and decoupled the `@elizaos/agent` server from hard-coded imports to improve plugin lifecycle management ([#7204](https://github.com/elizaos/cloud/pull/484)).\n*   **Telegram:** Optimized read receipts to eliminate inefficient nested lookups ([#7009](https://github.com/elizaos/cloud/issues/7009)).\n\n### Active Issues & Blockers\n*   **Dependency Dashboard ([#79](https://github.com/elizaos/cloud/issues/79)):** This remains the primary blocker for dependency updates (Node v24, TypeScript v6). Development is currently stalled by a transitive dependency issue in `@elizaos/plugin-todo` and requires the merging of a rolodex override ([#7146](https://github.com/elizaOS/eliza/pull/7146)).\n*   **CI/CD:** Contributors identified that CI workflows on the `develop` branch require updates to correctly invoke `bun install` and `tsc` to prevent typecheck failures and dependency breakages from reaching production.\n\n## 💬 Community & Collaboration\nCollaboration this week was heavily focused on technical debt reduction and infrastructure hardening. The transition to Vite and the removal of legacy Vercel dependencies indicate a concerted effort to move toward a more vendor-agnostic, high-performance architecture. The documentation of a design spec for the Claude/Codex sub-agent to Milady runtime bridge ([#481](https://github.com/elizaos/cloud/pull/481)) suggests active planning for future agent-to-agent interoperability, reflecting the project's commitment to modular, open-source AI frameworks."
}