# OpenComputer vs AQ

AQ (aq.dev), originally called AgentQueue, and OpenComputer both run Claude Code and Codex on cloud machines for teams, so agents keep working after you close the laptop, and both let you use your own subscriptions without a markup. Both also call themselves multiplayer, in different ways.

AQ is a multiplayer coding harness in the browser: your team gets a dedicated machine where real agent CLIs run in persistent terminal sessions, one git worktree per task, and teammates can watch, comment and take control of the same terminal. OpenComputer is a coding agent you mention in Slack: each workspace gets its own cloud machine, the team steers the work in a shared thread, and the result is a pull request, billed per workspace for the minutes the agent works.

If you want a shared, always-on machine where people and many agent CLIs work side by side, AQ fits. If you want to hand requests to an agent in Slack and get pull requests back, OpenComputer fits.

## At a glance

| | AQ (aq.dev) | OpenComputer |
|---|---|---|
| Where the agent runs | One dedicated team machine, a worktree per task | Your workspace's cloud Linux machine |
| Agent and models | 11 agent CLIs plus AQ's built-in agent | Claude Code and Codex |
| How you hand it work | Browser workspace, iPhone beta app, Linear, bots, API | Slack mention or API |
| What you get back | Diff to review and merge, PR, live preview | A pull request with screenshot and preview for UI changes |
| Between tasks | Pro machine always on; free sandbox sleeps | Machine stays warm; repo and caches kept |
| Pricing model | Per seat, flat monthly machine | Per workspace, work minutes |
| Entry price | Pro, $50 per user per month (early access) | Pro, $20 per month for the workspace |
| Free option | Free plan for one person, no time limit | 3-day trial, 600 work minutes |

## What is AQ?

AQ, from BetterLeap, Inc., describes itself as [the multiplayer coding harness](https://aq.dev/llms.txt). Its docs note that it is [not affiliated with Amazon Q Developer](https://aq.dev/docs/what-is-aq.md). Teams run real agent CLIs in persistent tmux sessions, streamed live to the browser, and each task, or work item, gets [its own branch and git worktree](https://aq.dev/docs/workspaces.md) with dependencies installed. Teammates can open the same workspace, including terminal, editor and preview, and typing into someone else's terminal requires the owner's approval.

Everything runs on [one dedicated machine per team](https://aq.dev/docs/runners-and-infrastructure.md), with no shared multi-tenant execution tier. On the free plan that is a personal sandbox VM that sleeps when idle; on Pro it is an always-on AQ-managed VM or VMs you connect from your own cloud account. AQ supports [Claude Code, Codex, Cursor, Kimi Code, Grok, Antigravity, Devin, Muse Code, OpenCode, Command Code and Pi](https://aq.dev/pricing.md), plus its own built-in agent. Beyond tasks it has Bots for standing jobs, Crews where a lead agent delegates to others, and Pages for published reports.

## What is OpenComputer?

OpenComputer runs Claude Code and Codex in its own cloud, and you hand them work by mentioning @Computer in a Slack thread or calling the API from your code. Each Slack workspace gets its own cloud Linux machine, sized to its plan. Every thread works in its own copy of the repos on its own branch, so parallel requests don't collide. Workspaces resume warm, with the repository, dependencies and build caches already in place.

@Computer reads the code, runs the commands and tests, then opens a pull request that says what changed, why, and how it was checked, with a link back to the thread. UI changes come with a screenshot and a preview link. The same cloud runs [serverless agents](/agents) you write in TypeScript, on the minutes the team already pays for.

## Key differences

### Two kinds of multiplayer

On AQ, multiplayer means shared live sessions. Teammates and reviewers watch an agent's terminal as it works, leave comments pinned to a live app preview that can be sent to the agent as prompts, and take turns typing in the same terminal. It suits pairing and hands-on review.

On OpenComputer, multiplayer means a shared Slack thread. Everyone in it sees every file @Computer opens and every command it runs, anyone can redirect it, and conventions one person explains apply to the next person's requests. Nobody types in a terminal. You describe the change and review the pull request.

### One machine per team, sized differently

The two are built the same way here. AQ runs all of a team's workspaces on its dedicated machine, so isolation between tasks is a git worktree and parallelism is bounded by the machine's size. You can buy larger machines, up to 48 vCPU, or connect VMs in your own cloud. Sessions persist in tmux, so you can close your laptop and pick up from any device.

OpenComputer also gives each Slack workspace one cloud Linux machine, and every thread works in its own copy of the repos on its own branch. The machine is sized to your plan rather than bought separately, and the workspace resumes warm with the repo, dependencies and build caches in place. If you want to choose a bigger machine or run on VMs in your own cloud account, AQ gives you that control.

### Agent choice

AQ runs eleven agent CLIs, including Devin, Antigravity, Kimi Code and Grok, each signed in with the user's own account. [AQ never marks up usage on your own subscriptions](https://aq.dev/llms.txt), and its built-in agent can also use AQ models priced per token. OpenComputer runs only Claude Code and Codex, with your subscription, your own API key, or its tokens at API prices with no markup. When a subscription hits its limit, you choose whether it switches to OpenComputer tokens until the reset or stops and waits.

### Browser workspace or Slack

AQ is a web app with an editor, terminals, a diff view and previews, plus a mobile web app and an [iPhone app in beta](https://aq.dev/docs/mobile.md). Its REST API, MCP server and webhooks are [Pro only](https://aq.dev/docs/api.md). OpenComputer has no IDE, editor or mobile app: you work from Slack, including Slack on your phone, or from the API.

## Pricing compared

As of October 2026, AQ lists a [Free plan for one person and Pro at $50 per user per month](https://aq.dev/pricing.md) in early access, down from a standard $200. The rate is locked for 12 months, then becomes $100 per user per month. Pro includes unlimited seats, a dedicated always-on machine (2 vCPU, 8 GB), and $10 of AQ credits per seat each month; bigger machines cost from $51.36 to $2,358.75 a month more. Your own subscriptions are not metered. OpenComputer lists Pro at $20 a month with 2,000 work minutes and Max at $200 with 25,000, for the whole Slack workspace, and $0.01 per extra minute.

For a team of five, AQ Pro is $250 a month at the early-access rate and $500 a month after the first year. OpenComputer Pro is $20 a month for the same five people, covering about 33 hours of active agent work, and Max is $200 for about 417 hours. The models differ: AQ is a flat price for an always-on machine your agents can use around the clock, while OpenComputer charges only for the minutes the agent spends working. Teams that keep agents busy around the clock may get more from a flat machine; teams with bursty requests pay less on work minutes.

## When to choose AQ

- You want teammates to watch and take control of live agent terminals in the browser.
- You want to run agent CLIs beyond Claude Code and Codex, such as Devin, Cursor or Antigravity.
- You want an always-on machine at a flat monthly price, or agents on VMs in your own cloud.
- You want bots, crews and published pages built into the same workspace.

## When to choose OpenComputer

- Your team works in Slack and wants requests, steering and history in one shared thread.
- You want pull requests with the evidence attached, without anyone driving a terminal.
- You'd rather pay per workspace for active agent time than per seat.

## FAQ

### Is OpenComputer an AQ alternative?

Yes, for teams that mainly hand coding work to Claude Code or Codex. Both run agents on cloud machines with your own subscriptions. AQ is a browser workspace where people share live agent terminals on one team machine, while OpenComputer is a Slack agent that works on your workspace's cloud machine and returns a pull request.

### How much does aq.dev cost?

As of October 2026, AQ has a free plan for one person with no time limit, and Pro at $50 per user per month in early access, locked for 12 months and then $100. The standard Pro price is $200 per user per month. Larger machines cost extra.

### Is AQ the same as Amazon Q?

No. AQ at aq.dev, originally named AgentQueue, is made by BetterLeap, Inc. and is not affiliated with Amazon Q Developer.

### Can I use my Claude or ChatGPT subscription with both?

Yes. On AQ each user signs in to Claude Code, Codex and other CLIs with their own accounts, and AQ does not mark up that usage. OpenComputer accepts your Claude or ChatGPT subscription or an API key, and can switch to its own tokens at API prices when a subscription hits its limit, if you choose.

### Do AQ agents keep running when I close my laptop?

Yes. AQ sessions persist in tmux on the team's machine, and Pro machines are always on. OpenComputer also runs in the cloud, so @Computer keeps working on a request after you leave Slack.

## Sources

- [AQ llms.txt](https://aq.dev/llms.txt)
- [AQ pricing](https://aq.dev/pricing.md)
- [What is AQ](https://aq.dev/docs/what-is-aq.md)
- [Runners and infrastructure](https://aq.dev/docs/runners-and-infrastructure.md)
- [Workspaces](https://aq.dev/docs/workspaces.md)
- [API](https://aq.dev/docs/api.md)
- [Mobile](https://aq.dev/docs/mobile.md)