Planning & Review

For a non-trivial change, PawOS can propose a concrete plan — one step per file it intends to touch — before applying anything, so you can review the scope of a change before it happens.

Approval now has a dedicated visual Plan Review card for structured plans. The card is still intentionally plan-level: it records approval or rejection in the conversation and preserves the existing destructive-action confirmation boundary.

1. 1

   When a plan is created

   For non-trivial code edits, the model calls proposeCodeEditPlan with a description plus proposed edits. The plugin builds an ExecutionPlan and does not apply changes itself.

2. 2

   What the user sees

   The Task Card shows PAWOS PLAN, files affected, a numbered file list, each file rationale, estimated +/− line scope, and Approve Plan / Reject Plan buttons.

3. 3

   Per-file review

   Expanding a plan item shows file path, action, reason, affected area, proposed changes, and a View Diff section when applyCodeEdit hunk data exists.

4. 4

   Approve

   Approve Plan submits a normal user-visible message approving that plan id. The runtime can continue, but actual mutations still need their own confirmation.

5. 5

   Reject

   Reject Plan submits a normal user-visible rejection. Planned mutations are not executed, the conversation remains intact, and the user can request a revised plan.

6. 6

   Modify

   Ask for changes in chat after rejecting or before approving. PawOS should prepare a new plan rather than mutating the rejected one.

PAWOS PLAN
Add dark mode

Files affected: 4

1. src/theme.ts
   CHANGE - Add color tokens

2. src/App.tsx
   CHANGE - Wire theme state

Estimated scope:
4 files
+126 / -31 lines

[Approve Plan] [Reject Plan]

How it works

What you see

• Your task progress, plan review with affected files and proposed changes, permission questions, command output, diffs, test results, previews and the final Work Record.
• For multi-file work you see the plan, why each step is needed, and Approve, Reject and Revise controls.
• While work runs you can follow terminal output, running processes, build and test results, and preview screenshots.

What PawOS does

• PawOS reads your project structure, dependencies and related files before proposing changes.
• Edits are applied precisely against the current file contents.
• Checks can include syntax, imports, type checking, linting, builds, tests, running-app health and visual checks, depending on your project.

Permissions

• Approving a plan records your intent; each edit, overwrite, command, git change, install, system change, connection or deploy still asks for approval.
• Commands run under clear rules — PawOS is not an unrestricted shell.
• Diffs you see come from the real changes, never an illustration.

Records

• Finished coding work shows the files changed, commands run, their results and output, test results, and screenshots when the change is visual.
• If a check was skipped (for example, the project has no test script), the Work Record says so.
• A rejected plan makes no changes.

Good to know

• Deep project analysis is strongest for TypeScript and JavaScript; every language can be edited.

Plan review controls