Taso
Your harness. Any agent.
Taso wraps Claude Code, Codex or Copilot unchanged. The task, the rules and the record are yours; the agent is an interchangeable part. One check in CI asks whether the code being merged came through a declared piece of work, with a record for every step. No record, no merge.
Talk to us about Taso
In active development.
01 / how it works
How it works
taso / the gateverifying
The envelope is around the work, not the agent. Taso prepares the world, watches the launch and judges the merge; the agent lives in between and never meets Taso: no prompt, no tool, no hook, no plugin, no fork.
02 / what it does · what it never does
What it does and what it never does
- Prepares
- The world the agent enters: the declared task, the rules, the roots, what may leave. Declared before launch, owned by you.
- Watches
- The launch. Every leg of the work leaves a signed record from the witness underneath, whichever vendor's agent did the work.
- Judges
- The merge. Did the code come through a declared piece of work? Does every recorded leg meet policy? Do those legs account for the exact code being merged? Otherwise, no merge.
- Speaks
- About coverage, not guilt. The gate says what is accounted for. It never guesses who did what it cannot see.
- Never
- Talks to the agent, replaces the vendor harness, records, contains, or compares. Selko sees, Vartio runs the fleet. Taso is the gate.
Selko sees. Vartio runs the fleet. Taso is the gate.
03 / start
Own the gate before you need it.
Taso is in active development against the Behaviour Commit contract, and the rule it enforces already works in the CI you run today. If your organization runs more than one vendor's agent, we want to talk.