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

> AQ runs Moonshot's Kimi Code CLI in shared cloud workspaces: persistent sessions your team can watch and steer, on your own machine, with your own Kimi plan.

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

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

## Two ways to use Kimi Code in AQ

- **As an AQ thread.** Pick Kimi Code in the composer and talk to it like any AQ conversation: messages queue, follow-ups reach it mid-turn, and the transcript, Changes panel and pull request card sit beside it. It runs on your own Kimi account.
- **As a terminal tab.** Open Kimi 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.

AQ lists the models your Kimi account actually has, not only the ones bundled with the CLI release, so a model Moonshot turns on for your subscription shows up in the composer and runs without waiting for a CLI update.

## What running Kimi Code in AQ adds

- **Sessions that outlive your laptop.** Kimi 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 Kimi 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 Kimi 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/).

## Kimi Code alongside every other agent

AQ runs Kimi 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 Kimi Code in AQ?

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

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

Yes. Kimi 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 Kimi 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/).