Connectors
Which real integrations Autonomous Work can use, and their real capability.
| Connector | Reads | Posts |
|---|---|---|
| GitHub | Issues and pull requests | Comments on a pull request |
| GitLab | Merge requests | Comments on a merge request |
| Jira | Tickets | — |
| Linear | Tickets | — |
Note
This table reflects the actual connector implementation, confirmed by direct code review, not the tracker-agnostic framing used in some marketing copy — see Autonomous Tickets.
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.
Related