Permissions
Why Autonomous Work cannot install software or repair PATH on its own.
Autonomous Work runs in a mode that auto-confirms only file edits (writeFile and applyCodeEdit) — every other destructive action, including running arbitrary commands, installing software, changing PATH, or committing to git, still requires a real confirmation nobody is present in an unattended run to give.
If the model attempts one of those other actions, the run reaches a real, structurally-enforced "waiting for permission" state and stops there — it does not silently skip the step, retry indefinitely, or fall back to auto-approving it.
Note
Installing software and repairing PATH always need your confirmation, so an unattended run pauses for them. Run that step in a normal chat where you can confirm it — see Coding → Software Installation.
How it works
What you see
- An unattended run for a ticket: investigation, plan, implementation, checks, completion and charge.
- Eligibility, connection status, your Ticket Wallet balance, ticket details, evidence and the final result.
- Before/after evidence and a summary of what was fixed, in your Ticket Wallet history.
What PawOS does
- PawOS investigates the ticket and repository, works in an isolated copy, applies and checks the fix, and records evidence.
- Ticket Wallet credits are separate from Paw Compute and are charged only when a ticket is successfully completed.
- Each ticket is charged at most once.
Permissions
- Autonomous Work never installs software, changes system settings or skips your organization’s approval rules.
- Each connected service offers specific actions — see Connectors for what each one supports.
- A blocked, failed or unverified run is never reported as completed.
Records
- Completion is backed by the repository state, check results, changed files and the charge record.
Good to know
- You need an eligible plan, a connected account, a repository and Ticket Wallet credits to start a run.