Forge Cloud
Forge Cloud is optional. Everything in Forge Code works without it.
| Feature | In Forge Code | Runs on |
|---|---|---|
| Model usage on a plan, no API key | forge/<model> after /login |
AI proxy (Forge Cloud API) |
| Plan, usage and credits | /usage-credits, /upgrade, /rate-limit-options |
Neon Postgres, Redis |
| Share a conversation | /share |
Cloudflare R2 |
| Move a session between machines | /teleport push, /teleport pull <id> |
Cloudflare R2 |
| Cloud sessions | /teleport cloud <prompt>, /session |
E2B sandboxes |
| Cloud schedules | /schedule cloud 1d <prompt> |
BullMQ on Redis, E2B |
| Remote Control | /remote-control |
Cloudflare Durable Objects |
| Voice input | /voice |
Deepgram |
| Marketplace plugins in cloud sessions | /cloud-plugins |
Marketplace index |
Signing in
Section titled “Signing in”/login → Forge Cloud account starts a device sign-in. Forge shows a code like BKQT-MWZR and opens the
console; you approve it after signing in with your Forge account. Forge Code then holds a token (fk_live_…) that
works only for your account. Revoke it in the console under Tokens; /logout revokes it too.
Quotas
Section titled “Quotas”Each plan has a monthly token allowance (input, output and cached tokens, reset on the first of the month, UTC), a
requests-per-minute limit, and limits on concurrent cloud sessions and schedules. Past the allowance, prepaid usage
credits are spent at list price. When a limit is reached, the API answers with a 429 that Forge Code shows as a
rate-limit message.