# Run Command Code with your whole team, in the cloud

> AQ runs the Command Code CLI in shared cloud workspaces: persistent sessions your team can watch and steer, on your own machine, signed in with your own key.

Published October 28, 2026 · by the AQ team · Canonical: https://aq.dev/agents/command-code/

AQ runs Command Code (the Command Code CLI) in cloud workspaces your whole team shares: the same live terminal, editor and app preview in everyone's browser. Command Code runs on a machine that is yours, each work item gets its own isolated git worktree, and you sign in with your own Command Code API key. AQ never marks up usage on your own subscription.

## Two ways to use Command Code in AQ

- **As an AQ thread.** Pick Command Code in the composer and talk to it like any AQ conversation: follow-ups queue for its next turn, and the transcript, Changes panel and pull request card sit beside it. It runs on your own Command Code API key.
- **As a terminal tab.** Open Command Code itself in a tab of the work item, exactly as it runs on your laptop, in a real terminal teammates can watch and type into.

Command Code keeps its own taste notes about how you like code written. AQ reads them into its shared memory so other agents in the same project can use them too (see [memory](https://aq.dev/docs/memory/)).

## What running Command Code in AQ adds

- **Sessions that outlive your laptop.** Command Code runs on the machine, so a closed lid or a lost connection does not stop it.
- **Parallel tasks, zero collisions.** One isolated [git worktree](https://aq.dev/guides/git-worktrees-for-ai-coding-agents/) per work item.
- **Review and merge in the tab.** The Changes panel, line comments and a merge that waits for checks (see [review and merge](https://aq.dev/product/review/)).
- **A crew around it.** Use Command Code as a builder in a crew and have another vendor review its work (see [Crews](https://aq.dev/product/crews/)).
- **Your team in the loop.** Teammates open the same work item, watch live and take the keyboard when you hand it over.

## How setup works

Connect Command Code once in Settings, Connections, with its normal sign-in. You can connect more than one account and pick which one a thread uses. Then connect a repository and start a work item. Related reading: [run several coding agents in parallel](https://aq.dev/guides/run-multiple-ai-coding-agents-in-parallel/).

## Command Code alongside every other agent

AQ runs Command Code next to Claude Code, Codex, Cursor, Kimi Code, Grok, Antigravity, Devin, Muse Code, OpenCode, Command Code and plain shells, on the same repository. See [every agent AQ runs](https://aq.dev/agents/).

## Frequently asked questions

### Do I need an API key to run Command Code in AQ?

You sign in with your own Command Code API key through Command Code's normal flow, once per person. AQ never marks up usage on your own subscription.

### Does Command Code keep running when I close my laptop?

Yes. Command Code runs on your AQ machine or a VM in your own cloud, not on your device, so the session keeps going and is where you left it from any browser.

### Can my team watch a Command Code session?

Yes. Teammates who open the work item see the same live session and can be handed the keyboard. Sharing with teammates is part of the Pro plan.

---

About AQ: AQ is the multiplayer coding harness where teams chat, build and run bots with every AI coding agent, like Claude Code and Codex: shared live terminals, review and merge, app previews and standing jobs, in your own cloud. Start at [aq.dev](https://aq.dev/).