Skip to content
PawOS Docs

Plans

How PawOS proposes multi-step work before executing it.

For non-trivial coding requests, PawOS can propose a concrete, file-by-file edit plan before applying anything — review before mutation, not mutation with a narration after the fact.

A plan is a real, structured list of steps (one per affected file), not free text. Structured plans render in the Task Card as a visual Plan Review surface with approve/reject controls and expandable per-file details.

Note

You approve or reject the plan as a whole, right in the conversation. Each code edit still asks for its own confirmation when it runs.

ConceptMeaning
Plan proposedproposeCodeEditPlan or proposeExecutionPlan returned an ExecutionPlan. No mutation happened.
Plan approvedThe user approved the plan-level scope through the Plan Review UI or conversation.
Code edit authorizedA specific applyCodeEdit/writeFile action passed the existing confirmation gate and may mutate files.
Plan rejectedThe proposed mutations must not execute; the conversation remains available for revision.

How it works

What you see

  • Workspaces, tasks, plans, permission questions, Work Records, usage meters and connection status.
  • You use these through normal requests — there is no separate configuration console.

What PawOS does

  • A workspace scopes file and command work; a task groups one request; a plan proposes work; an action performs one concrete step; a Work Record captures what happened.
  • Work Records are built from the real results of each action, not written up afterwards.

Permissions

  • Naming something a workspace, plan or task never skips a permission question.
  • PawOS decides what to do, but every change to your machine goes through a dedicated, checked action.
  • Plan limits and permission questions are separate protections and can both apply.

Records

  • Each claim in a Work Record points to the command, file, check, screenshot or result behind it.
  • A Work Record shows partial success, skipped checks, rejected plans and failures just as clearly as successes.

Good to know

  • Work Records always show the timeline of what ran; many action types add detailed evidence on top.