feat(cloud): optional Akeru Cloud account with a linked environment socket

[leoisadev1]

Summary

Akeru had no way to offer hosted services, such as one-click Slack setup or cloud sandboxes, because Slack and other platforms need a public HTTPS endpoint and Akeru environments are local. This adds an optional Akeru Cloud account. An environment links to it once with a device code, then keeps one outbound socket that the cloud uses to relay requests. Without a linked account, the app works exactly as before.

flowchart LR
  Browser -->|Clerk sign-in, approve code| Worker[apps/cloud Worker]
  Slack -->|HTTPS events| Worker
  Worker <-->|one outbound socket| Hub[EnvironmentHub Durable Object]
  Hub <--> Env[Environment server]
  Env --> Secrets[(ServerSecretStore: link token)]

Loading

• packages/contracts/src/cloud.ts: versioned socket protocol, device link, forwarded requests.
• apps/cloud: Cloudflare Worker with Clerk accounts, device link, the EnvironmentHub socket and the hosted Slack relay. apps/cloud/infra deploys it with Alchemy, which pins its own Effect version.
• Server: link, unlink and status, plus the outbound connection. A 401 or 410 handshake marks the link revoked and stops reconnecting.
• Settings → Akeru Cloud on web, desktop and mobile, with palette commands. Docs for users and maintainers.

Message content and Slack tokens stay on the environment. The cloud stores account and environment metadata only.

Evidence

After

• Live: on an isolated dev server, Connect requested a device code from the staging cloud ("YH5C-LR97") and showed it. Cancel returned to Not connected.
• Tests: vp test run apps/cloud passes 51 tests in 6 files. Focused server, contracts, web and client-runtime suites pass 261 tests in 26 files. Typecheck passes for cloud, cloud/web, cloud/infra, server, web, mobile, contracts and client-runtime.
• Review: an independent review found two problems carried over from the original branch, both fixed with regression tests. A socket upgrade could slip past a revocation (a876e6226), and mobile Connect and Disconnect failed silently (7cf888bc6).

Not tested: the Linked state, because approving needs a real Clerk sign-in. Native mobile rendering. A live hosted Slack event through the relay.

Merge Danger

Door: one-way. A push to main that touches apps/cloud/** or packages/contracts/** runs cloud-deploy.yml and redeploys the production Worker at cloud.akeru-bot.com. Production is already live from this branch: the Cloudflare for SaaS hostname, Vercel DNS records, Clerk production instance (email sign-in), and every required cloud-production secret are in place, so the merge only redeploys the same code. Staging stays on its workers.dev address and only allows Leo's account.

Blast radius: environments that link a cloud account, plus the Settings page. Unlinked environments never open the socket.

Created with Claude Opus 5.5 in Claude Code.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
akeru-bot-landing	Building	Preview	Oct 6, 2026 2:08am UTC

[devin-ai-integration]

Devin Review found 6 potential issues.

[greptile-apps]

Confidence Score: 5/5

[Critical risk] Adds a new hosted cloud service with authentication, database, and deployment infrastructure.

The PR appears safe to merge based on the changes since the previous review and the resolved prior threads.

Summary

The PR adds optional Akeru Cloud account linking, an outbound environment socket, hosted Slack routing, and settings interfaces. Since the previous review, it changes the cloud sign-in component to keep sign-up on the cloud page. No new actionable issue was established.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Client[Settings] -->|Device link| Worker[Akeru Cloud Worker]
  Worker <-->|Environment socket| Server[Environment server]
  Slack -->|Hosted events| Worker
  Worker -->|Relay| Server

Loading

_{Reviews (9) · Last reviewed commit: "fix(cloud): sign-up stays on Akeru Cloud..."}