superharness — give opencode a team
Description: superharness sits on top of opencode and gives it the ability to spawn and coordinate a parallel team of agents — as many as it needs, automatically.

Autonomous · Rust · MIT

# Give opencode
a whole team.

superharness sits on top of opencode and lets it spawn parallel worker agents, manage them, and clean up — all on its own.

Install now
View on GitHub
your-project — opencode + superharness
$ superharness opencode starting — orchestrator mode You: build a REST API with JWT auth [orchestrator] Breaking into 3 parallel workstreams... [worker-1] spawned → implementing JWT middleware [worker-2] spawned → building user CRUD endpoints [worker-3] spawned → creating database schemas & migrations [worker-2] asks: allow file write to src/routes/users.ts? [orchestrator] approved ✓ [worker-1] done · [worker-3] done · [worker-2] 80%... [orchestrator] all workers finished — cleaning up

## How it works

Install once. Run instead of opencode. The rest is automatic.

1

### Install superharness

One command: `cargo install superharness`. Requires tmux and opencode already installed.

2

### Run `superharness` in your project

Navigate to your project directory and run `superharness`. You get a normal opencode session — the same interface you already know — but now the AI has access to a full team.

3

### Your AI spawns and manages a team

When the task warrants it, opencode spawns parallel worker agents — each in its own isolated git worktree. Workers run concurrently, report back, and are cleaned up automatically. The AI decides how many to spawn, when to spawn them, and when they're done. You just see results.

## What you gain

Everything opencode does, plus a team behind it.

⚡

### Parallel workers

The AI spawns as many worker agents as the task needs — each tackling an independent workstream simultaneously. What takes one agent 4 hours takes a team of 4 about an hour.

🔒

### Isolated workspaces

Every worker gets its own git worktree. No file conflicts. Workers commit their own branches; the orchestrator merges results when everything looks good.

✅

### Permission management

Workers ask for file writes and shell commands as usual. The orchestrating AI reviews them in context — approving safe operations automatically and surfacing anything that needs your eyes.

👁️

### Automatic cleanup

Stuck workers are detected and recovered. Finished workers are killed and their worktrees removed. The orchestrator keeps the workspace clean without you doing anything.

## opencode alone vs. opencode + superharness

Same opencode you love. Now with the ability to run a team.

opencode alone

- Single agent, one task at a time
- Sequential — slow on complex work
- All permissions come to you
- No awareness of parallel execution
- One context window for everything

superharness

- Orchestrator spawns workers as needed
- Parallel execution across isolated worktrees
- Safe permissions auto-handled by orchestrator
- Workers collaborate and merge results
- Each worker gets a fresh focused context

## Install

Requires Rust, tmux, and opencode.

Cargo
$ cargo install superharness
brew and AUR packages coming soon
then, in any project
$cd your-project
$superharness

## Going somewhere?

Leave the AI running. It handles things while you're gone.

### Away mode

The orchestrating AI can enter an away state when you step out. In away mode it keeps workers running and approves safe operations, but queues any real decision for your return — architecture choices, destructive operations, anything it isn't sure about. Come back to a full debrief of what happened and a short list of things that need your call.