Labels
Cross-cutting classification for issues, agents, and Skills — and the entry point for workflows.
Labels classify work across boundaries. A project says "these issues belong together"; a label says "these issues share a property" — a queue, a platform, a review requirement — no matter which project they sit in. The label system covers three resource types: issues, agents, and Skills.
Anatomy of a label
Every label has a name, a description, a color, and a scope. The scope determines which resource type the label applies to, so an issue label and an agent label can share a name without colliding.
The issue label page
Opening an issue label gives you a working view of everything carrying it, not just a flat list:
- Search across the label's issues.
- Filter by workspace or project.
- Sort by usage and by progress.
- Related issues — see what else is connected.
- Activity history — what happened on this label over time.
- Batch changes — replace labels, change assignees, or change statuses for many issues at once.
The batch operations are the quiet workhorse here: when a property moves (a feature ships, a platform migrates), one pass over the label page updates everything that carries it.
Labels and workflows
A label with workflows enabled is the entry point for workflows: the label's detail page is where its candidate issues become a dependency graph. This is the main reason to be deliberate about labels — they are classification and orchestration at once.