Tyran

📖 Documentation · Getting started · Videos · Architecture · Releases

The more you use it, the better it gets.

What Tyran is

Your most expensive model just renamed a variable. In the same chat, it judged an authentication boundary.

One chat, one model, every job — that is why the bill is high and the work gets worse. The context fills up, the plan is somewhere in the scrollback, and "the tests pass" is a sentence rather than something you can check.

You didn't install a tool. You hired a manager. You describe the work once; he interviews you until the goal is unambiguous — batches of at most four questions, each with his recommendation — turns the plan into tickets on a board, and hands each piece to a dedicated subagent with fresh context and a model tier matched to how hard that piece actually is. A good manager doesn't put a principal engineer on a grep: a scout reads the repo on the cheap tier, implementers take one story each on their own branch, the reviewer can never bless a patch it wrote, and security review always gets the strongest tier — a floor no cost profile or flag can lower.

That is a cost lever and a quality lever at the same time. The conductor holds the plan and never accumulates its agents' transcripts, which is where the tokens in a long session actually go; and an agent that never saw the last six failed attempts cannot inherit them, so the second opinion is a real one.

Nothing you say is lost. Remember something halfway through a run and say it — it doesn't land in the scrollback, it becomes a ticket. Every decision, spawn, report, merge and open question is appended to a journal committed to your repo, so a restart, a compaction and a colleague on another branch all read the same thing.

It learns your repo while it works. Setup reads how the repo is really worked — stack, validation commands, how things get deployed — rather than asking you to describe it. After every initiative the team runs a retrospective on itself, and what it changes is Tyran, never your product code. The same failure three times becomes knowledge pasted into every matching handoff; five times and it becomes a rule in your CLAUDE.md, carrying the dates that earned it. That knowledge does not only grow: entries the counters have written off are retired on evidence, and two that say one thing are merged by appending a third that supersedes both — the originals stay on disk, so an unwanted merge is one file to delete. Most retros correctly change nothing.

All of it lands on one page — a board: what every agent is doing right now, which questions are waiting on you (answer them there and the run carries on), and what the work cost, in the tokens the platform itself reported, per model, per agent and per ticket. The conductor gets its own row, so its overhead never hides inside the total.

Underneath, a hook decides before the tool ever runs — none of this is a prompt asking nicely. A report with no raw command output is refused: it blocks silence, not forgery. Every write is classified against a policy file you own. And a commit carrying a secret is refused, even inside a markdown file. Mechanisms rather than instructions — which is the whole argument.

▶ Open the sandbox board — the real page with sample data, in your browser. Click the tabs, filter the lanes, select a card.

Watch it