Ask your code, your data and your tools. Get answers. What should your agents build today? Give an agent a standing job.

A chat that runs queries, reads your repos and connected accounts, and answers with tables, charts and pages.

Claude Code, Codex, Cursor and the rest, each task in its own worktree, reviewed by a separate agent, merged from the tab.

A bot wakes on a schedule or an event, does its job in its own thread, asks before anything outward and stays inside a monthly cap.

Press Enter to sign in with Google. What you typed is waiting when you land. Free sandbox, no card.

  • Claude Code
  • Codex
  • Kimi Code
  • Grok
  • Cursor
  • Antigravity
  • Command Code
  • Devin
  • Muse Code
  • OpenCode
  • Pi
An AQ chat answering a question about signups with a chart and a table, after running queries against a read-only database
An AQ work item: the Ship crew planned the change, Claude Code built it, Codex reviewed it, the Changes panel shows the diff with a teammate's line comment, and the pull request card is ready to merge
An AQ bot's morning briefing: it woke at 9:00, read mail, calendar and Linear, and listed what needs attention today
8,800+workspaces opened
1,000+pull requests merged
14,000+terminal sessions

Counted across every team on AQ, as of October 2026.

What AQ is

Chat to find out. Build to change it. Bots to keep at it. On infrastructure that is yours.

Chat

Ask about your code, your data and your tools.

A chat runs queries, reads your repositories and your connected accounts, and answers with tables, charts and pages. When it is time to change code, it proposes the work item.

  • Opens its own copy of a repository, refreshed to main every turn
  • Your saved secrets arrive as environment variables, so a read-only database URL just works
An AQ chat answering with a chart and a table after running queries
Build

Give every task its own worktree, and watch it live.

Each work item is an isolated git worktree with its own branch and live preview, so parallel agents never collide. Teammates open the same terminal and see the agent type, and take the keyboard with one click.

  • Label a Linear issue ai-task and a work item appears, status syncing both ways
  • Agents open pull requests with each person's own GitHub account
Two teammates in the same AQ terminal while an agent works, with presence avatars and a control request
Bots

Give an agent a standing job.

A bot wakes on a schedule, a Linear label, a failing check or a review comment, works in its own thread and, by default, asks you before it starts new work. Every bot has a monthly spend cap.

  • A morning briefing from your mail, meetings and AQ work
  • A bot tied to a pull request fixes failing checks until it merges
An AQ bot's header with its schedule and month spend, above a wake that read mail and calendar
Crews

A team of agents, with a reviewer that did not write the code.

Pick the Ship, Review or Fix crew like a model. A Lead plans, you approve, builders work in their own worktrees, and Auto prefers another vendor and account for the review.

A crew in an AQ thread: the Lead's plan, a builder on Claude Code and a reviewer on Codex that caught two issues
Review and merge

From diff to merged, without leaving the tab.

The Changes panel shows this turn, uncommitted work or the whole branch. A comment on a line rides your next message. Merge waits, and says why, while checks fail or the review is stale.

The AQ Changes panel with a diff and a line comment, beside a pull request card with passing checks and a Merge button
Auto

The right model for every turn, and you see why.

Auto routes each turn across AQ models and the subscriptions you connected that still have room. The choice, its price and its confidence sit right on the transcript.

Auto decision rows in an AQ thread naming the model, its price per million tokens, the confidence and the kind of task
Integrations

Your agents can read your tools. You decide what they may do.

Connect Linear, Slack, Gmail, Google Calendar, Granola, Sentry, Mercury, Vanta or Stripe once and it works in every thread on every agent. Each tool is Allow, Ask or Off, and Ask works in the middle of a turn.

An AQ thread asking permission before an agent drafts an email: Allow once, Always allow, Don't allow
Memory

What one agent learns, every agent can use.

AQ reads the memory Claude Code, Codex and other CLIs keep on your machines and makes it searchable from any agent. Edit a note once, and share project notes with the team when you want to.

The AQ memory page listing notes read from Claude Code and Codex, grouped by project
Visual replies and pages

Answers as charts, tables and pages you can share.

An agent can answer with a page above its text, and publish it at a stable link for your team or a guest.

A chart an agent rendered inside an AQ thread
Phone

Your agents in your pocket.

The same threads, previews and terminals on any phone. The iPhone app, in beta, adds push notifications, a Live Activity for running work and widgets.

AQ on a phone: a work item thread in the mobile web app, with the crew's progress and the pull request
Genie

A personal assistant that knows your work.

A morning briefing, what needs you from mail and meetings, and where your AQ work stands. It drafts, and waits for you before anything goes out. Voice where it's enabled.

The Genie thread answering what needs attention before lunch
Machines

As much machine as the work needs.

On the Pro plan, make your machine bigger or add machines from Settings, and pick a disk up to 2 TB. Each size has its monthly price on the pricing page.

Machine sizes on the Pro plan
SizevCPUMemory
Standard28 GB
Performance416 GB
Power832 GB
Max1664 GB
Ultra32128 GB
Mega48192 GB
Mega Memory48384 GB
Where your code runs

Your machine, your accounts, your boundary.

  • Code stays on a machine dedicated to you. Your checkout, worktrees, shell sessions and agent credentials live on a VM in your own cloud or one AQ runs for you. There is no shared execution infrastructure.
  • Agents sign in with your accounts. Claude Code, Codex and the rest use the subscriptions your team already has, and those stay unmetered.
  • Model traffic goes where you point it. Prompts go to the provider you chose. Only AQ's built-in agent, on AQ's models, routes through AQ's gateway.
Your teamBrowsersPhonesAny OSaq.devSign-inPresenceStreamingYour machineYour cloud, or a VM dedicated to youCheckout and worktreesTerminals and dev serversAgent credentialsClaude Code, Codex, Cursor...Never shared with another teamModel providers, via your own accounts
The browser sees the session. The machine holds the code. Providers see only what the agent sends.
How it works

Up and running in three steps.

  1. 01

    Connect an environment

    Start free in a sandbox AQ creates for you, or run in your own cloud with an always-on machine for your team.

  2. 02

    Sign in to your agents

    Claude Code, Codex, Cursor and every other coding agent, with the accounts you already have. Or skip this: AQ's built-in agent works with nothing connected.

  3. 03

    Chat, build, or make a bot

    Ask a question in a chat, start a work item with its own branch and live preview, or give a bot a standing job. Your team joins any of them with a link.

Questions

Before you start.

What is the difference between Chat, Build and Bots?
A chat has no branch of its own: it reads, runs queries and reports, and proposes code changes as work items. Build is a work item: a branch, an agent that edits, a live preview and a pull request. A bot is a chat with a standing job that wakes on a schedule or an event. See Chat, Build and Bots.
What is included in the Free plan?
A private, AQ-managed sandbox for one person with nothing to install, and no seat charge. Use your own agent subscriptions, or use AQ's built-in agent at published per-token prices. The Pro plan adds teammates, sharing, AQ credits every month, and your choice of machines in your own cloud or a dedicated VM managed by AQ. Details are on the pricing page.
Do I need my own Claude or OpenAI subscription?
No. Connect the subscriptions your team already has and they stay unmetered, or use AQ's built-in agent on AQ's models. Every model shows its own price before you pick it. See pricing.
Where does my code run?
On the Free plan, on a private AQ-managed VM dedicated to you. On the Pro plan, on machines you connect from your own cloud account or on a dedicated AQ-managed VM. Your checkout, worktrees, shell sessions and agent credentials stay on that machine; AQ does not use shared multi-tenant execution infrastructure. Model inference is separate: prompts go directly to the model provider, or through AQ's gateway when you use AQ's built-in agent.
What happens when I click Start free?
You accept the Terms of Service and continue with a work Google account. If you are not already approved, AQ adds you to the review queue. Requests are reviewed personally, usually within a day or two, and AQ emails you when your workspace is ready. Then sign in, connect an agent, and start a chat, a work item or a bot.

Bring your whole team into the session.

Start free in a sandbox AQ creates for you. Move to your own cloud when the team is ready.