Working History
The flat, per-request list of everything PawOS has done.
Working History is a single, flat list of every request PawOS has processed — one entry per conversation turn, whether or not it did anything destructive.
Each entry links to that request’s Work Record. Status is derived honestly from what actually happened — Completed, Failed, Blocked, or Stopped — never fabricated as complete for unfinished work.
| Status | Meaning |
|---|---|
| Completed | The request finished and every action it took succeeded |
| Failed | An action ran and genuinely failed |
| Blocked | Refused before running — entitlement, usage limit, or a security boundary |
| Stopped | Ended mid-way (interrupted, or a pending confirmation nobody answered) |
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.
Related