Plan before you act
Use /plan for work that needs several coordinated steps. The model investigates first, writes a plan and asks before implementing it.
/plan Add pagination to the search results and cover it with tests.Without an argument, /plan uses the work already discussed in your conversation. The plan is meant to be short: a handful of steps, with details only where they help. The model looks at the code just enough to choose an approach and asks what is open in a single round of questions; what it still does not know becomes an assumption written in the plan. For small work the plan is two or three lines.
Review the steps
Section titled “Review the steps”A plan includes a goal, steps, files, dependencies and checks. You can approve implementation, ask for adjustments or stop after planning. Until you approve, the plan stays unapproved: if you stop and then ask for changes in plain text, the revised plan is put to you again.
You do not need /plan to review a plan: if you ask the model for a plan to look at before it starts, it asks for the same approval, with the same choices. Without that request, the model keeps its own plan for big work and goes on without interrupting you.
When the plan is ready, Tatu prints it in the conversation, right above the question that asks what to do: the goal, then each step with what it depends on, its files, whether it runs in parallel, how to check it and its details. It scrolls like any other text, so read it before you choose. In the phone app the question has a View plan button that opens the whole plan on its own page; going back leaves your answer as it was. The plan is not reprinted when you resume the session later; it stays in the plan file and in the plan panel.
The plan panel shows progress and each step’s status, including dependencies it is waiting for. The panel only knows what the model reports, so if the model ends its turn with steps still open, Tatu reminds it once to close them or say why it stopped. Press Alt+T to fold it to one line or expand it again.
Tatu saves a Markdown plan file under ~/.tatu/plans/ (or $TATU_HOME/plans/). You can edit that file in your editor. Tell the model to read your changes and revise the plan before continuing; editing the file is not a live update to the panel.
A prompt, not a mode
Section titled “A prompt, not a mode”/plan asks the model not to edit files while planning. It does not lock tools or change permissions. Tatu still runs with your permissions, so review what the model proposes rather than treating planning as a safety boundary.