# Connect your agent tools

Pass the tools you use to `brigadestack init --harnesses`. In BrigadeStack docs, "harness" means one of these agent tools, and `--harnesses` is the flag that names them. Each tool gets its own handoff inbox at `.<id>/memory-handoffs/`, and every inbox uses the same format.

## Supported tools

| Tool | id | Handoff inbox |
|---|---|---|
| Codex CLI | `codex` | yes |
| Claude Code | `claude` | yes |
| OpenCode | `opencode` | yes |
| Antigravity | `antigravity` | yes |
| Pi | `pi` | yes |
| Cursor | `cursor` | yes |
| Grok CLI | `grok` | yes |
| Amp | `amp` | yes |
| Hermes | `hermes` | yes |
| OpenClaw | `openclaw` | no |
| Aider \* | `aider` | yes |
| Goose \* | `goose` | yes |
| Continue \* | `continue` | yes |
| GitHub Copilot CLI \* | `copilot` | yes |
| Qwen Code \* | `qwen` | yes |
| Kimi Code \* | `kimi` | yes |
| AdaL \* | `adal` | yes |
| OpenHands \* | `openhands` | yes |
| Crush \* | `crush` | yes |

\* Community-supported. These still install with `--harnesses`, but we don't actively track them as they change upstream. [PRs welcome](https://github.com/escoffier-labs/brigade/pulls) if you use one and want to keep it current.

`brigadestack init --harnesses antigravity` also installs silent, detached hooks that report Antigravity sessions to the backend when one is running. OpenClaw has no handoff inbox of its own. Hermes writes handoffs like the other tools.

## Common combos

| You use | Pass |
|---|---|
| Claude Code only | `--harnesses claude` |
| Claude Code and Codex | `--harnesses claude,codex` |
| Codex only | `--harnesses codex` |
| Hermes on its own | `--harnesses hermes` |

Mix as many tools as you use. They all write handoffs in the same format and read the same memory.

`--harnesses hermes` installs the `.hermes/memory-handoffs/` inbox and the `.brigade/hermes/` adapter fragments. Check both after setup:

```bash
brigadestack operator verify-harness --harness hermes --target .
brigadestack handoff list --target .
```

## Re-running init

Re-running `brigadestack init` is safe. It refuses to overwrite tracked files without `--force`, and it replaces only the managed block between its markers in `.gitignore`.

See the [Quickstart](/docs/getting-started/quickstart) for setup, verification, and the ingest flow.

Each logo belongs to its owner and appears here only to identify the tool. No owner is affiliated with or endorses BrigadeStack. The Pi logo is (c) Earendil Inc. & Contributors under the MIT License.