Devin CLI, now in AQ

Devin CLI is now a first-class harness in AQ. Open Connections, choose Connect harness, pick Devin CLI, and sign in with your own Devin account. From then on any workspace can start a Devin session the same way it starts Claude Code or Codex: in a real terminal, on a machine that does not sleep, inside a git worktree that belongs to that workspace alone.

What shipped

• Devin CLI in the harness list. It appears in Connections next to Claude Code, Codex, Cursor, Kimi Code, Grok, Antigravity, and Command Code, and in the new-terminal picker of every workspace once connected.
• Sign-in that works from a cloud machine. AQ runs Devin's manual token flow, so the approval link from app.devin.ai shows up as a clickable banner in the workspace instead of trying to open a browser on the server. Credentials stay in your own per-user home on your team's machine.
• A pinned, verified install on every machine. AQ installs Devin CLI from Cognition's official release artifact and checks its SHA-256 before it ever runs. New machines get it during provisioning; existing machines picked it up in the last update.
• No stalls on fresh worktrees. Devin asks you to trust each new folder. Every AQ workspace is a new folder, so AQ answers that for the worktree it just created and your session starts working immediately. By default AQ also launches Devin in its unrestricted permission mode: the isolated worktree on a machine you control is the boundary, the same posture AQ takes with Claude Code and Codex.

Why it matters

Devin CLI's own pitch is start local, hand off to the cloud. AQ gives the local half a permanent home. The session runs on your team's always-on machine (your own cloud, or a dedicated VM AQ manages), so closing the laptop changes nothing. Each workspace is an isolated worktree on a branch like ai/1234-fix-auth, so five Devin sessions on the same repo never collide. And the terminal is live for everyone on the team: a colleague opens the workspace, sees the same session, and can request control to steer it, or leave a comment on the preview that goes straight to the agent.

It also means Devin CLI now sits beside the other harnesses instead of competing for the same terminal. Run Devin on one branch and Codex on another, compare the diffs, and keep the better one. Your Devin subscription pays for Devin, your Anthropic or OpenAI subscription pays for the others, and AQ adds no markup on any of it.

Honest scope

Devin CLI runs in AQ as a terminal harness: the real CLI, in a real terminal, with everything the CLI can do, including its own model picker and its own cloud hand-off commands. It is not yet a native AQ Composer conversation. Composer threads need the structured session events that Claude Code and Codex expose, and Devin CLI does not publish that protocol today. If Cognition adds it, Devin joins Composer the same week.

Start in three steps

1. Sign in to AQ and open Connections. Choose Connect harness, then Devin CLI, and approve the link that appears.
2. Open any workspace, or create one from a branch or a Linear issue, and choose Devin CLI in the new-terminal picker.
3. Give it the task. Share the workspace link with whoever should be watching.

Frequently asked questions

Do I need a Devin subscription to use Devin CLI in AQ?

Yes. Devin CLI signs in with your own Devin account, exactly as it does on a laptop. AQ never proxies or bills that usage; it runs the CLI on your team's machine with your credentials in your own per-user home.

Can my teammates see and steer a Devin CLI session?

Yes. An AQ workspace is a live terminal that any teammate with access can open. They watch the same session in real time, and typing into it is delegated: they request control and the owner approves in one click.

Is Devin CLI available in AQ Composer?

Not yet. Composer's native conversations rely on structured session events that Devin CLI does not expose today. Devin CLI runs as a terminal harness in AQ workspaces, with everything the CLI itself supports.

Which Devin CLI version does AQ run?

AQ pins the Devin CLI build, installed from Cognition's official release artifact and verified by checksum on every machine. Pinned versions move forward with AQ updates, so every workspace on a team runs the same build.