Claude Code sandbox runtime

Every Claude Code session, in a sandbox of its own.

tokenman runs Claude Code and Codex on managed machines in the cloud. Each task gets its own session in its own git worktree, keeps going when you close your laptop, and comes back as a pull request.

Limited access: by invitation or request. Sessions run the official Claude Code and Codex CLIs.

Browser
Terminal
Phone

$ fleet ls
  ↻ K3F9  Claude  Add rate-limit headers  api     working
  ! B8D2  Codex   Fix export timeout      web-app needs you
  ✓ A7P4  Claude  Move sign-in to PKCE    hub     PR #219 merged
  ◷ C9W1  Claude  Upgrade dependencies    api     parked

# laptop closed overnight... the same sessions, still there
$ fleet

Sample data. The same list is in the web console and on your phone.

A runtime, not a chat window

Your sessions live on machines that stay up, so you can hand off the work and walk away.

One task, one sandbox

Each task gets its own session and, when it names a repository, its own git worktree and branch. Uncommitted changes never mix between sessions.

Survives your laptop

Sessions run on managed machines, not on your computer. Close the lid or go offline: they keep working. Reattach any time and the conversation is where you left it.

Browser, terminal or phone

Open the web console, run fleet in a terminal, or connect from a phone. Every device sees the same sessions, and the one waiting for you is listed first.

Lands as a pull request

A session working in a repository opens its own pull request and merges it only when CI is green. GitHub hosts the code and the PRs; nothing claims or closes your issues.

Pooled subscriptions, metered per person

Claude and ChatGPT (Codex) subscriptions form one pool behind a credential proxy; when one is full, the next request goes to another. Each person has a limit of their own, and a session never holds the subscription credential.

Your team, your pool

Sign in. A hosted hub is your team's own: admins invite colleagues by GitHub username, add subscriptions (ours, your own, or both) and decide who may use which.

From sign-in to a merged PR

Sign inInvited? You are in. Not yet? Request access and we will get back to you.
Say what you wantIn the web console, in fleet, or from your phone. The hub records the task and opens a session in a fresh worktree.
Review the pull requestThe session works, asks when it needs you, opens a PR and merges it on a green gate. You are told when it is done.