Web App

The web app is Continuum in a browser tab. Sign in at continuumcode.ai/app on any machine and you get the full workbench — the same Code, Usage, and Settings surfaces as the desktop apps, with nothing to install. It is the same codebase the Windows and Linux desktop app wraps. There is no separate web-only UI that lags behind: a change to the workbench lands on both at once.

​

Sign in

Sign-in is a hosted browser flow backed by WorkOS AuthKit, with Google as a supported identity provider. On the marketing site, Google One Tap can sign you in without leaving the page. Signing out lands you on an account chooser rather than silently re-authenticating you as the same person, so switching between a personal and a work account actually sticks. Sign out from Settings → Session → Sign out. Signing out also clears this browser’s cached sidebar projection, so the next account to sign in here cannot see the previous account’s repos and sessions.

​

What you get

Three tabs, the same everywhere: Code, Usage, and Settings. Each tab is a real path — /app/code, /app/usage, /app/settings — so deep links and browser Back work the way you expect. Older /org, /people, and /me links redirect to their current homes.

​

It is a remote, not a host

This is the one thing to understand before you plan around the web app. The browser cannot run an agent process, clone a repo, or hold a git worktree. Something else has to host the compute. So the web app is a client: you pick a host, and the session runs there and streams into your tab. Your options are any of your enrolled execution hosts — a local or remote Mac, a Windows or Linux desktop, a VPS, a Tailscale-reachable box, a bring-your-own-cloud runner — or Continuum Cloud, which provisions the compute for you. Practically, that means:

• Pick a repo, type a prompt, and the run spawns on the host you chose, then streams back live — transcript, diffs, plan approvals, terminals, the lot.
• The Code tab shows a connect gate until a host is reachable, with the picker right there.
• The phone, the Watch, and the web app are all in the same tier here: they steer sessions, they do not run them.

If you want a machine of your own on the other end, install the desktop app on it and tick the enrollment box during first run.

​

Organization admin

Company administration lives inside Settings, at Settings → Organisation (/app/settings/organisation). It is a full admin console rather than a couple of toggles — thirteen sections, of which the ones you will actually live in are:

• Overview and People — who is in the org, and the rolled-up picture.
• Teams and Budgets — group developers and cap spend.
• Models — govern which models are available to whom.
• Inference — hosted-inference governance for the org. See Hosted inference.
• Requests — an approval inbox for things members have asked for.
• Analytics and Activity — spend and an audit trail.
• Keys — provisioning and credential management.

Several of these are role-gated. Keys, Requests, and Analytics are visible only to approvers and admins, and Activity is scoped by role — admins see everything, a team lead sees their team, a member sees their own events. Every section is routable regardless, so a deep link always resolves; it is the navigation that decides what you can see. For the full model — what an org collects, what it never collects, and how a personal org is upgraded to a real one — see Organization & Cloud.

​

Sharing a transcript

A shared transcript opens in a browser at continuumcode.ai/share/<id> — no sign-in, no install. See Sharing for what gets redacted before a transcript leaves your machine.

​

When to reach for it

The web app is the right client when you are not at your own machine — a borrowed laptop, a locked-down work desktop, a machine where you cannot install anything. It is also the fastest way to check on a long-running session or approve a plan without opening an app. It is not the right client when nothing of yours is enrolled and online. Without a reachable host there is nowhere for the work to run.