Usage
How PawOS meters what a request costs, at a glance.
PawOS measures usage as Paw Compute — a single weighted meter across every runtime, rather than a raw token count or a per-feature limit.
You see one number: Paw Compute used this period. See Billing & Usage → Paw Compute for the full model, and Autonomous Work → Autonomous Work Credits for the separate, success-gated dollar wallet that funds Autonomous Ticket completions specifically.
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