Autonomous Tickets
What one Autonomous Ticket run actually produces.
One run works through a single, well-scoped ticket end to end and is billed only once it genuinely, verifiably completes.
A run reads the ticket from Jira, Linear or GitHub, works on the fix, and can post its results as a comment on your GitHub pull request or GitLab merge request. See Connectors for what each service supports.
Note
A run that can’t genuinely resolve the ticket reports honestly what it found and what’s blocking it, and is not billed for that run.
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.