Workspaces
The scoped project boundary PawOS operates inside.
A workspace is a real folder on disk that PawOS has been pointed at — the boundary its file, terminal, and coding actions are scoped to for a given task.
PawOS does not maintain a hidden global filesystem boundary; each request that touches files or runs commands carries an explicit working directory (cwd), and workspace-security checks (CodingRuntimeSecurity) verify a requested path actually falls inside the declared workspace root before any write or command executes.
Note
Selecting a workspace root is itself a required step — a coding action attempted with no workspace selected fails with an explicit "select a workspace root" message rather than guessing a location.
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.