Issues
Bugs and risks found by runs or reported by people, kept apart from results, and turned into tickets.
An issue is a problem in your product: a bug or a risk, reported by a person or found by Autonomy. Issues live in a project, on its Issues page.
Issues are kept apart from results. A step passes or fails on its outcome alone, and an issue never changes a step's or a run's result. A passing run can still report an issue, such as a console error it saw on the way, and a failed run doesn't create an issue by itself.
Kinds
| Kind | Meaning |
|---|---|
| Bug | Something is broken and should be fixed. |
| Risk | A gap or concern. Nothing is broken yet. |
Issues from before v0.5 may have the kind Note. They stay readable and can be resolved; new issues are always a Bug or a Risk.
Where issues come from
- Seen by the agent: during a run, the agent reports something wrong that isn't the outcome it was checking, such as a broken image next to the form it filled.
- Automatic check: Autonomy flags what the product signalled during the run, such as console errors, failed requests, and problems in emails.
- Added by a person: click New issue on the Issues page, or Add issue on a run.
A run lists what it found under Issues found.
One issue, many runs
When several runs hit the same problem, they're linked to one issue instead of creating new ones. A run that sees it again adds itself as evidence. A run that sees a resolved issue again reopens it.
Statuses
| Status | Meaning |
|---|---|
| Open | Needs attention. |
| Resolved | Fixed. If a run sees it again, it reopens. |
| Ignored | Known and accepted. Runs keep linking to it, but it never reopens. |
The Issues page lists issues newest first, ten to a page. The status tabs show how many issues each status has, and the kind and environment filters apply to the whole list, not only the page you're on.
Report an issue
Click New issue and fill in:
- Kind: Bug or Risk.
- Title and Details.
- Environment: where you saw it.
- Attach evidence: link the run that shows it, or upload a screenshot or log.
- Link a ticket: optional, if one already exists.
Context the agent should know, such as "the OTP email is slow on staging", belongs in Memory, not in an issue.
The issue page
An issue page shows its runs as Evidence, its Linked tickets, and its Activity: who created or edited it, status changes, reopenings, tickets and comments. Add a comment at the bottom.
Tickets
Turn an issue into a ticket in Linear or Jira with Create in Linear or Create in Jira under Linked tickets. The ticket goes to the team or Jira project chosen for the project. Status comes back: closing the ticket resolves the issue, and reopening it reopens the issue. You can also paste a link to an existing ticket; a pasted link is for reference only.
A project can also file a ticket automatically for every new bug. See Linear and Jira.
Issues outside Autonomy
- Digests: each environment's weekly digest lists its issues. See the project's Digests page.
- Pull requests: a project can make GitHub checks fail on bugs a run found. See Pull request testing.
- Notifications: webhooks and Slack can send new issues. See Notifications.
- API and MCP: list, create, comment on and resolve issues. See Operations.
Didn’t find it?