What operator control means here
The current app does not hide repository actions behind silent automation. You choose whether a session is read-only or write-enabled, select the target checkout explicitly, inspect terminal output live, and review changed files and diffs before deciding what should happen next.
How to use it in practice
Use read-only mode for exploration, use write mode only when the session should edit, and prefer new worktrees for risky or parallel tasks. After a run, open the changes panel and inspect the diff before creating a pull request, merging a branch, or asking another session to continue.
Where the review checkpoints live
The review checkpoints are the launch dialog, the focused terminal panel, and the changes panel. Together they tell you what command is running, where it is running, and what files changed, which is enough to keep the operator in control of the workflow even before a richer approval system exists.