One binary, no runtime
Go builds it; the terminal runs it. Classic TUI out of the box, an optional opentui interface when you want the framed inspector and live preview.
A general-purpose agent. In your terminal. Finishes the job.
Edit, run, verify, browse and research with one binary that keeps its tool registry small and its research bounded — then hands back when the work is done, not when it runs out of ideas.
curl -fsSL https://raw.githubusercontent.com/ramsterr/Wombat/main/install.sh | bash benchmarks
Same model, same tasks, same skill and MCP server, fresh workspace per run. Wombat passes 18/18 with the lean profile, uses 41% fewer prompt tokens, and finishes the research task Pi times out on. The comparison page also shows where Pi is still the lighter harness — small, single-file work.
Not a feature list for its own sake: each of these changes how a run behaves, and each one is documented with the exact commands in the docs.
Go builds it; the terminal runs it. Classic TUI out of the box, an optional opentui interface when you want the framed inspector and live preview.
The coding profile exposes read, write, edit, bash, glob, grep, apply_patch, tool_search and request_capability. Web, LSP, verify and media load mid-run when the task needs them.
Quick gives 2 searches and 1 fetch, standard 5 and 3, deep 10 and 6 — each with a hard ceiling. When the budget is spent the model is told to synthesize, not to keep looping.
Plan a ledger, run scouts and writers in isolated git worktrees, pass reports down the dependency graph, and merge only what passes its checks.
JSONL transcripts per project, resume by id or last, and shadow-git snapshots so a bad edit is one command from gone.
stdio and HTTP servers with OAuth and per-server gates, skills as markdown, and specialists with their own prompt, tools, permissions and model.
quick start
The installer gives you the latest tagged release. If you want the capability profiles,
research budgets and custom agents described on this site, install from
main — the tag is behind the branch.
# current main
go install github.com/ramsterr/Wombat/cmd/wombat@main
wombat setup # provider, key, model
wombat doctor # one small request, errors surfaced
wombat # open the chat
# or the tagged release
curl -fsSL https://raw.githubusercontent.com/ramsterr/Wombat/main/install.sh | bash cd tui && npm install && npm run build
once (Node 26.4+), then run Wombat from that checkout. Without it you get the classic
TUI, which has every feature except the rendering. Switch back with
wombat classic.
The lead plans, workers execute, checks decide. Nothing about the fleet is implicit: a one-step plan is a single agent.
Free slots start newly-ready work, long chains are scheduled first, and a slow scout never holds up an independent writer.
Writers declare the files they may change. Writes outside that set are refused, which is what makes automatic merges safe.
Work happens in a git worktree; checks run once, review policy decides who reads the patch, and the merge is three-way.
A worker that needs a decision returns needs_input; resume_worker continues the same session and worktree.
Eight guides, matched to main after v0.2.6, with the exact commands quoted
from the repository.
Install, choose a provider, build the optional UI, and run a first task.
open → 02The nine-tool coding profile, capability loading, and research budgets.
open → 03Custom agents, the plan scheduler, worktrees and review policy.
open → 04The benchmarks, the method, the caveats, and the raw data path.
open →install
One binary. One config file. Start with the docs, then decide about the fleet.