01When you step away
Step away.
Autopilot keeps it moving.
Autopilot answers what would otherwise wait for you, so a session keeps working toward its goal while you are away. A completion goal decides when the work is done, and your permission rules still decide what may run.


Engage it with one command
/autopilot <goal>sets a completion goal and engages. Only you can engage it. Scripts, profiles, and the model cannot.--autopilotengages the session Caudra starts with.Answers what would wait for you
A separate model call, the delegate, answers permission prompts, the
questiontool, questions asked in prose, and a plan that is ready to implement. It never runs tools, and it leaves what it cannot decide safely to you.Approvals that end with the call
An approval covers one call and adds no rule. Protected files,
sudo, and tools that always ask are never approved, and nothing is approved after content screening flags a result or cannot screen one in full.Budgets and a log
An engagement ends after 100 continuations by default, and you can cap its spend and its minutes. Decision calls count toward that spend.
/autopilot loglists every decision, what the delegate was asked, its reason, and what followed.Goals that check evidence
After each work turn, a separate model call with no tools reads the transcript. An unmet goal starts another turn. A met goal clears itself. A goal that waits on CI or a deploy is checked again later, and three turns without progress end the run.
/goal loglists every check with its model, cost, and reason.Permissions that read the command
Shell chains and pipelines split into separate commands for approval. Approve once, for the conversation, the project, or every project, and accept patterns Caudra suggests from repeated approvals.
Plan first, then hear back
By default, new sessions open in Plan mode, where the agent edits only its plan and asks before commands it cannot prove read-only. Notifications tell you when a turn finishes or a prompt needs your answer.