Coding Workspace
The live status surface for an in-progress coding task.
While a coding task runs, PawOS surfaces a live canvas of what’s happening — current step, running processes, terminal output, build status, and test results — rather than a single chat bubble at the end.
- Project understanding and coding memory are visible on every tier (read-only).
- Running processes, terminal output, build status, live diff summary, and browser preview require execution access (Pro or higher).
Agent Activity
The Coding Workspace exposes concise operational activity such as analyzing repository, planning changes, editing files, running tests, checking browser, retrying, and verifying. This is execution status and evidence, not hidden chain-of-thought.
| Visible item | What it means | What it is not |
|---|---|---|
| Running | An action has started and no result has returned yet. | A transcript of private model reasoning. |
| Waiting | A confirmation, connector, or capability requirement is blocking progress. | A failed task. |
| Done | The action returned ok:true and may include structured evidence. | A promise that unrelated checks also passed. |
| Failed | The action returned a real failure result or launch/readiness problem. | A fabricated diagnosis. |
| Retried | The execution trail recorded recovery attempts. | Unlimited self-healing. |
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