# Tade

> Run Claude Code, Codex and pi coding agents in parallel in one terminal, with a queue that knows what waits on what, per-agent cost, checks and a judge. MIT.

Run a team of coding agents. Know exactly what each one did, and what it cost.

Tade is free software under the MIT licence: https://github.com/mujacica/tade. It is a terminal program, not a web app
or a service. There is no account, no server and no cloud component.

## What is only true of Tade

Many tools run coding agents in parallel in a terminal. These four are what Tade has that,
as of this writing, the others do not:

- **A queue, not a pile** — Every piece says what it waits on, and holds when that fails rather than running anyway.
- **Checks against a commit** — What ran, on which commit, and unknown where nothing did — never a blank that reads as green.
- **Money that is not guessed at** — A quoted price and an estimate are never added together, and a subscription is never totalled as dollars.
- **A finding somebody answers for** — The agent says it fixed it or why it is not real. You rule. Both are kept.

## What it will not do

These are the design rather than a backlog:

- **Nothing merges anything** — unless you asked for exactly that. merge is never by default.
- **A judge answers, it never decides** — It may only ever add caution — never approves, merges, closes, unholds or shortens anything.
- **There is no tool that deletes a branch, a worktree or a folder** — and asking explicitly does not produce one: that is a person with git in a terminal.
- **Closing Tade never stops your agents** — Closing the window and stopping the work are two different acts.
- **There is no daemon** — Schedules run only while a window is open. What came due while it was closed is caught up once, or skipped.
- **No server, no browser, no build step** — One terminal. git pull is the upgrade.
- **Being there is not being on** — An extension in the folder is listed and never imported until somebody turns it on.
- **Nothing installs anything behind your back** — The exact command is on the page before it runs.
- **Tade reports its own trouble, never your work** — What you said, what an agent wrote, task titles, prompts and notes are never in its telemetry. Paths are scrubbed to ~.
- **Tade never holds your sign-in** — Claude Code signs in as itself. A key you do paste is written to ~/.tade/config.yaml, and any agent you run can read it — agents run as you, and nothing sandboxes them. Export its variable instead and it is never written down.

## Install

```sh
npm i -g tade-sh
tade
```

- Node: ≥ 22.19
- git: any
- tmux: optional — agents that outlive the window
- whisper.cpp, ffmpeg: optional — speech
- gh: optional — pull request state

## What people say to it, and what it answers

Worked examples of the interface. The project names, figures and findings in them are invented.

### brief me

Morning. stripe-v15 is blocked on npm i stripe@15, 1 still working and Sentry has 3 new issues in checkout.

### how do I install it

`npm i -g tade-sh`
`tade`
That is the whole of it. There is no build step, so git pull is the upgrade.

### what won't it do?

Ten things, and they are the design rather than a backlog:
Nothing merges anything unless you asked for exactly that.
A judge answers, it never decides.
There is no tool that deletes a branch, a worktree or a folder.
The other seven are on the page.

### run the tests and tell me what broke

Opening a tests terminal first, then running it there.

### every Monday, update our dependencies

Done. It starts an agent each Monday at 09:00 and keeps a record of every run.
There is no daemon — what came due while Tade was closed is caught up when it opens.

### what does it cost?

Tade is MIT and costs nothing. What the agents cost is whatever your models cost.
A subscription is not money, and is never totalled with it.

### show me the queue

What can run now runs; the rest waits for exactly what it needs and starts by itself.
Looking at queued work is never starting it.

### is my code sent anywhere?

Not by Tade. It reports its own trouble, never your work.
What you said, what an agent wrote, task titles, prompts and notes are never in its telemetry.
Speech stays on your machine by default. A key you paste lives in ~/.tade/config.yaml, which any agent you run can read — export its variable instead to keep it out.

## More

- Repository and source: https://github.com/mujacica/tade
- How Tade is built, and every invariant it keeps: https://github.com/mujacica/tade/blob/main/AGENTS.md
- Package: https://www.npmjs.com/package/tade-sh
- This page: https://tade.sh/