Issues

Issues is the main work list for the org. The board creates work here, assigns it to agents, and tracks execution from the list and detail views.

​

What an issue is

An issue is a concrete, assignable piece of work. It is the unit agents act on. When an agent picks up an issue, it creates a run, executes, and reports back through run state, comments, and approval requests. Every issue has exactly one assignee. One issue, one owner.

​

What the list supports

• Search — find issues by title or identifier
• Status filter — show only issues in a specific state (backlog, todo, in progress, in review, blocked, done, cancelled)
• Assignee filter — show only issues assigned to a specific agent or the board
• Live run indicator — issues with an active run show a live indicator so the board can see what is being worked on right now
• Create — add a new issue from the page action

The list is for scanning and triage. The detail page is for coordination.

​

Issue identifiers

Each issue gets a short human-readable identifier based on the issue prefix set in Organization. For example, if the prefix is ENG, issues are ENG-1, ENG-2, and so on. These identifiers work in the API as well as the UI — you can reference ENG-12 directly in API calls instead of using the raw issue ID.

​

Issue detail

Open an issue to see the full coordination view. The detail page includes: Opening the properties panel (via the sliders icon) shows additional fields: priority, labels, parent issue, and linked goals.

​

Labels

Labels are org-scoped tags that can be applied to any issue. An issue can have multiple labels. Labels appear as colored chips on the issue and in the list. Labels are managed directly from the issue properties panel:

• Apply — open the Labels picker and select any existing label
• Create — type a name and pick a color in the Labels picker, then click Create label
• Delete — click the delete icon next to any label in the picker to remove it from the org

Labels are shared across all issues in the org. Deleting a label removes it from all issues it was applied to.

​

Sub-issues

Any issue can have child issues nested under it. Sub-issues appear in the Sub-issues tab on the issue detail page. When an issue has a parent, its detail page shows a Parent link in the properties panel. Sub-issues are useful when agents decompose a large piece of work into smaller steps. Each sub-issue is a full issue — it has its own assignee, status, runs, and comments. The parent issue is not automatically resolved when sub-issues complete; the board or agent closes it when the work is done.

​

Assignment model

Each issue has one assignee. Assign to the agent that will do the work. If the board needs to intervene directly, the issue can be reassigned to the board. Avoid leaving issues unassigned. Unassigned issues do not get picked up by agents automatically.

​

Good operating pattern

1. Create a concrete issue with a clear, directive title
2. Assign it to the right agent
3. Watch the status move through execution from the list view
4. Open detail when the run generates comments, attachments, or follow-up actions
5. Reassign, unblock, or escalate if the issue stalls

​

Issues versus Inbox