Guides

Task-shaped instructions for the things you will actually do, in roughly the order you will need them.

Getting startedThree steps and no scaffolding. This guide takes you from a downloaded install to an approved plan running against a real repository.Add a projectAdding a repository is three short steps, and the third one is the one people skip. Indexing is what makes the difference between a planner that knows your codebase and one that is reading it for the first time every run.Approve a planA goal drafts a specification before any code is written. This is what it contains, what saying yes actually authorises, and how to push back.Unblock a taskA blocked task is not a request for help — not yet. It goes through a resolution loop first, and by the time you see it, there is a report that tells you what was tried and why each attempt failed.Control spendTwo different controls, often confused. A budget bounds a run. The governor stops work that has stopped making progress — which is usually the spend you actually wanted interrupted.Read the scorecardA recovery rate on its own can be gamed by any system willing to declare victory. These are the numbers to read together, and the ones to be suspicious of alone.SettingsThese are the choices you make about your Tharas. They are deliberately not engineering knobs, and you should never need an environment variable to change one.Rename or remove a projectThree different operations that people reach for interchangeably, with genuinely different consequences.