Skip to content
PawOS Docs

Code Editing

How file changes are actually applied — real patches, not rewrites.

Multi-file edits are applied as real, hunk-based patches (surrounding context plus the changed lines), computed against the file’s current on-disk content — not a whole-file overwrite.

Every edit that touches an existing file requires confirmation, following the same rule as every other destructive action in PawOS.

Text
-  const status = 'pending';
+  const status: TaskStatus = 'pending';
   return { id, status, createdAt: Date.now() };

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.

Related