AQ Build

A worktree per task,any agent, merged

Every task gets its own branch and live preview. Run Claude Code, Codex and the rest side by side, have a second agent on another vendor review it, and merge from the tab.

An AQ work item: the conversation with a Ship crew, the Changes panel with a diff and a line comment, and a pull request card ready to merge

AQ Build is where code changes happen. Each work item is an isolated git worktree on a machine that is yours, with every coding agent CLI you use, AQ's built-in agent, a shell, an editor and the running app beside the conversation. Teammates open the same work item and see the same live session.

How a task becomes a pull request

Label a Linear issue ai-task

Linear in, PR out

A work item appears in the team sidebar and the issue moves to In Progress. Status follows the issue both ways.

Pick the Ship crew

Plan, build, review

A Lead plans the steps, you approve, builders work in their own worktrees and a separate agent reviews them, with Auto preferring another vendor.

Pin a comment on the preview

Review the running app

Comments on the page itself go to the agent as its next message.

Every agent, in parallel, without collisions

Each work item is its own git worktree, so ten agents on ten tasks never touch each other's files. Open Claude Code, Codex, Cursor, Kimi Code, Grok, Antigravity, Devin, Muse Code, OpenCode, Command Code or a plain shell as tabs in the same work item, or talk to AQ's built-in agent. Sessions run on the machine, not your laptop: close the lid and the work keeps going.

The Changes panel with scopes, a file list, a diff and a comment pinned to a line
The Changes panel: this turn, uncommitted, the whole branch, or one commit. Comments on a line ride your next message.

Review and merge without leaving the tab

The Changes panel shows exactly what the agent did this turn. Start a review thread on the diff and its findings come back pinned to the lines they are about. The pull request card carries the checks, and Merge says in words why it is not ready while checks are failing or the review is older than the latest commit. More on review and merge.

A teammate requests control of a live terminal and the owner grants it
Live together: teammates watch the same terminal and take the keyboard when you hand it over.

Built for a team

Share a work item with a teammate, give them the keyboard, or send a guest link to someone outside the company to review the running preview. Agents commit and open pull requests with each person's own GitHub account. Everything runs on a private machine in your own cloud or one AQ runs for you.

Start free in a private sandbox. Bring your team on the Pro plan.

Start buildingSee pricing

Frequently asked questions

What is a work item in AQ?

A work item is one task: an isolated git worktree and branch, the agent sessions working on it, its live preview, and the pull requests it opens.

Can I run Claude Code and Codex on the same task?

Yes. Open both as tabs in one work item, or give each its own work item on the same repository and compare the results before you choose a pull request.

Does the agent keep running when I close my laptop?

Yes. Sessions run on the machine AQ manages for you or the one in your own cloud, so a closed laptop or a lost connection does not stop them.

Whose GitHub account opens the pull request?

The person driving the work item. Agents use each person's own GitHub sign-in, so commits and pull requests are attributed to them.