Completion & Charging
What "genuinely completes" means, and how billing is protected against double-charging.
A run is only billed once it transitions through a server-side completion check — idempotent, so a duplicate completion signal can never charge twice.
- A failed, cancelled, retry-exhausted, or approval-denied run is never charged.
- A stale run (left in progress for more than 24 hours with no further activity) is automatically reconciled as abandoned, never billed, never left silently "in progress" forever.
- Completion requires the run’s own checks (tests, build, type checks where the project has them) to pass.
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.