Torque GitHub

Open source agent orchestration

Torque

Run a coordinated team of Claude Code, Codex, Gemini CLI, and shell agents from the terminal you already use.

Install Torque View source
Local daemon SQLite state Git worktrees No build step UI
Terminal-native control

Why now

When direct agent APIs get fragile, use the CLI.

Torque does not need a hosted control plane or a private agent API. It launches and supervises real terminal sessions, then adds the missing orchestration layer: board state, dispatch actions, live digests, worktree isolation, and review gates.

Your prompts, branches, task history, and agent state stay on your machine. Torque is the command center around the tools developers already reach for when they want code shipped.

Use your seats

Torque runs on top of the agent tools you already pay for.

Claude Code and Codex already know how to authenticate your account. Torque launches those tools as real terminal sessions, then adds orchestration around them: tasks, worktrees, digests, and review flow.

That means your existing subscriptions stay useful. Torque is the local command center around those CLIs, not a separate hosted agent API you have to meter, proxy, or re-buy.

Torque workspace showing the agent grid, engineer workload, task board, and a live terminal session.

Operating model

A local command center for many agents.

Torque turns scattered coding sessions into a system you can inspect, steer, and merge without losing track of who changed what.

01

Dispatch from actions

Reusable Jinja prompt templates convert tasks into precise worker instructions, with transitions for review, follow-up, and done.

02

Isolate every worker

Each agent can run in its own git worktree with branch boundaries, diff summaries, checkpoints, rollback, and merge detection.

03

Coordinate the wave

Optional engineer agents watch the board, route work, monitor digests, ask for decisions, and keep the next task moving.

04

Review with context

Tasks, threads, events, artifacts, and terminal history stay tied together so you can review results instead of reconstructing them.

Screens

Built for operators who keep multiple agents hot.

The same UI runs in iTerm2's Toolbelt, a standalone browser window, or the native desktop shell.

Worktree boundaries

Know exactly what each agent changed.

Torque tracks per-agent branches and worktree diffs so review starts with the actual code boundary, not a pile of terminal logs.

Torque worktree diff view showing changed files and branch state.

Local first

The persistent source of truth is your machine.

Python daemon

A long-running local server owns state, command dispatch, terminal integration, and WebSocket updates.

SQLite by default

Tasks, groups, schedules, memory, and settings persist locally and remain readable by the CLI.

Terminal adapters

Torque works with iTerm2 today and has provider adapters for Claude Code, Codex, Gemini CLI, and generic shells.

Plain frontend

No framework, no bundle, no cloud dependency. The UI is HTML, CSS, and JavaScript served by the daemon.

What changes

From scattered terminals to a coordinated team.

Without Torque

  • Multiple agent tabs with unclear ownership
  • Prompts rewritten from memory
  • Branches and worktrees managed by hand
  • Review starts after context is already stale

With Torque

  • Groups, workers, engineers, and terminals in one grid
  • Reusable actions for repeatable dispatch
  • Per-agent isolation and merge-boundary tracking
  • Tasks, digests, artifacts, and diffs stay linked

Install

Clone it, install it, launch the Toolbelt.

The canonical experience runs on macOS inside iTerm2. Standalone browser and beta native desktop modes are included for wider views.

GitHub repo Documentation 
git clone https://github.com/runtorque/torque.git
cd torque
make deps
make install
make cli

FAQ

Practical answers.

Is Torque a hosted service?

No. Torque is a local open source workspace. The daemon, database, frontend, and terminal sessions run on your machine.

Does it require an agent API key?

Torque itself does not require a hosted agent API. It orchestrates terminal-native tools and regular shells that you authenticate separately.

Which agents does it support?

Torque has adapters for Claude Code, Codex, Gemini CLI, and a generic terminal fallback, plus regular terminal cells.

What platforms are ready?

macOS with iTerm2 is the strongest path today. Browser-only and native desktop shells exist, with broader terminal support planned.