Cloud

Run Command Code in the cloud instead of on your computer. It is the same interface you use locally, with the agent working against your GitHub repo on its own branch. When there is something to review, it opens a draft pull request. Close your laptop and the task keeps going.

Beta

Cloud is in beta, so you may still run into bugs or rough edges. We recommend reviewing its pull requests before you merge and keeping an eye on usage.

Report any issues on GitHub.

Usage

Cloud sessions

cmd --cloud                                          # New session on this repo
cmd --cloud "Fix the flaky date test"                # New session with a first message
cmd --cloud <session-id>                             # Reopen a session
cmd --cloud --base develop                           # New session from another branch

cmd -p --cloud "Fix the flaky date test"             # Headless: one task, prints the session id
cmd -p --cloud <session-id> "Update the changelog"   # Headless follow-up

cmd cloud list                                       # Your sessions, newest first
cmd cloud status <session-id>                        # Status, pull request link, reopen command
cmd cloud stop <session-id>                          # Stop a running session

-m <model> and --effort <level> work with all of them.

Before your first session

Update Command Code

Run cmd update. Cloud needs a recent version.

Link your GitHub account

Open commandcode.ai/settings and connect GitHub under Connected accounts.

Install the Command Code GitHub App on the repo

Install it from github.com/apps/command-code-ai and give it access to the repository you want to work on.

Run it from a clone of the repo

Cloud uses the repo's origin remote on GitHub, and you need push access to it. It starts from what is on GitHub: local changes that are not pushed are not included.

Working in the cloud

cmd --cloud opens the same interface you use locally. While it connects you see each step: creating the session, cloning the repo, checking out the branch, starting Command Code. You can type while it connects; your message is sent as soon as it is ready.

Steer while it works. Type while the agent is working. Your message waits in the queue until the agent picks it up, the same as a local session.
Esc interrupts the current turn. Queued messages come back to your input.
Ctrl+C twice leaves. Command Code prints the command to reopen the session.
/model and /effort switch what the cloud session runs.
Reopen any session with cmd --cloud <session-id>. The conversation so far is shown, and a task that is still running streams in live.

Headless mode

With headless mode, cmd -p --cloud "task" starts a session, prints its id, and returns. The agent finishes the task on its own, pushes, and opens a draft pull request. Send a follow-up to the same branch and pull request with cmd -p --cloud <session-id> "task". A follow-up is refused while the previous task is still running.

Branches and pull requests

The agent works on its own branch, command-code/<id>. It never pushes to your base branch.
A headless task ends with a draft pull request describing what changed, how to test it, and what is left.
In an interactive session it opens or updates a pull request when you ask for one.
A question, or a turn with no changes, ends without a pull request.
Images it adds to a pull request, issue or comment are committed under .github/pr-assets/ on its branch, so GitHub can show them.
Starting a session on a brand-new, empty repository creates a first commit with a README on the default branch, so the agent has something to branch from.

Note

The agent is told never to push to your base branch, and a guard blocks it. A GitHub ruleset on your default branch is still the strongest protection: block direct pushes and require a pull request. Set one on repositories you use with Cloud.

Sessions

An idle session stops on its own and picks up again with your next message. You only pay while it runs.
Long runs have a time limit. Near it, the agent wraps up, pushes, and notes what is left.
Sessions you have not used in a while are archived. They take a little longer to reopen.
The agent runs with permissions bypassed, inside its own machine.

Not in the cloud yet

We are actively adding support for more of these. Tell us what you need most on GitHub.

Commands that act on your computer or on a local session, such as ! shell commands or /resume, print a short notice instead.
Plan mode and permission modes are not available yet.
Previews: a dev server the agent starts in the cloud cannot be opened from your browser yet.
Taste learning is off in cloud sessions.

Pricing and limits

Cloud is included on the GOAT plan and above. During the beta, cloud time is billed per second of running time at $0.10 per hour, from your usual credits, on top of model usage. A stopped session costs nothing. Your usage shows under Cloud on commandcode.ai/settings/usage and in /usage.

Each plan limits how many cloud sessions can run at once and how many new ones can start per day, with higher limits on higher plans. If you hit one, Command Code tells you which and what to do. To request higher limits, contact us with your use case.

Troubleshooting

Message	What to do
Link your GitHub account … to use cloud sessions.	Connect GitHub at commandcode.ai/settings, then try again.
Command Code GitHub App is not installed on owner/repo.	Install the app on that repository from the link in the message.
Your GitHub account … cannot push to this repository.	You need write access to the repository.
Branch "…" does not exist on this repository.	Push the branch, or pass an existing one with `--base`.
Couldn't clone owner/repo …	The reason is git's own. Try again, or send us the session id.
The cloud session stopped reporting progress while starting.	Reopen it with the printed command.
You have N cloud sessions running …	Stop one with `cloud stop`, or wait for it to finish.
Cloud sessions are available on the GOAT plan and above.	Upgrade your plan at commandcode.ai/pricing.
insufficient credits	Top up. Cloud time is billed like model usage.

Anything else: send us the session id from cloud list or the reopen line Command Code prints when you leave.

Does it use my local changes?

No. A cloud session starts from what is on GitHub. Push first if you want it to see your work.

Can I close my laptop?

Yes. The task keeps running in the cloud. Reopen it later with cmd --cloud <session-id>.

Will it push to main?

No. It works on its own command-code/<id> branch and opens a pull request for you to review. For an extra guarantee, add a GitHub ruleset on your default branch that blocks direct pushes and requires a pull request. Then nothing reaches it without your review.