Run Cursor's agent with your whole team, in the cloud
Published October 28, 2026 · by the AQ team
AQ runs Cursor (Cursor's coding agent CLI) in cloud workspaces your whole team shares: the same live terminal, editor and app preview in everyone's browser. Cursor runs on a machine that is yours, each work item gets its own isolated git worktree, and you sign in with your own Cursor account. AQ never marks up usage on your own subscription.
Two ways to use Cursor in AQ
- As an AQ thread. Pick Cursor 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 Cursor account.
- As a terminal tab. Open Cursor 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.
Cursor's model list in AQ is the one your own CLI reports, so the models on your plan show up in the composer, and Fast versions of a model appear as a Fast speed beside effort rather than as separate rows.
What running Cursor in AQ adds
- Sessions that outlive your laptop. Cursor runs on the machine, so a closed lid or a lost connection does not stop it.
- Parallel tasks, zero collisions. One isolated git worktree 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).
- A crew around it. Use Cursor as a builder in a crew and have another vendor review its work (see 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 Cursor 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 the Cursor CLI on a cloud VM and keep it running after you close your laptop.
Cursor alongside every other agent
AQ runs Cursor 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.
Frequently asked questions
Do I need an API key to run Cursor in AQ?
You sign in with your own Cursor account through Cursor's normal flow, once per person. AQ never marks up usage on your own subscription.
Does Cursor keep running when I close my laptop?
Yes. Cursor 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 Cursor 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.