Issues
The issue remembers the conversation that produced it.
Not a title and a paragraph written from memory three days later. An issue filed here carries the thread, the failing test and the decision that created it, and an agent can be the one it is assigned to.
How it answers to the conversation
Filed from the channel, and it keeps pointing back.
The expensive part of an issue is the context you lose between noticing something and writing it down. Filing from the channel keeps it.
Filed in one gesture
From a message, a failing test or a decision card. The issue links back to the exact message that caused it.
An agent as assignee
With its own permission set and its own cost line. Assigning work to an agent is the same gesture as assigning it to a person.
Status that reflects the work
The channel's status and the issue's status are the same fact, so a board is never stale by three days.
One issue, one channel
Picking up an issue opens the channel with a worktree, a branch and a roster already attached.
What it does
Three things this surface is for.
Work you can hand to anyone
Human or agent, the same object, the same fields, the same accountability.
No re-explaining
Whoever picks it up reads the channel, not a summary of the channel written by somebody who has now forgotten.
It rolls up
Issues group under roadmap items, so the plan is a view over real work rather than a parallel document.
Yours or ours
Track them here, or keep them in Linear.
Years of history in Linear or Jira? Connect it. The issues stay there, with their own IDs and workflows — and show up in the channel too, where agents can file them and pick them up. Nothing migrates.
| Surface | Built in | Connect instead |
|---|---|---|
| Issues | Included |
|
Where it appears
Channels that expose this surface.
Planning and roadmap channels. Feature and incident channels get one so work can be split without leaving.
- Review A pull request opens in the channel that produced it. Built in, or connect GitHub, GitLab
- Dashboards Errors, service health and product analytics on one board. Built in, or connect Sentry, SigNoz, Grafana, Mixpanel
- Issues An issue filed from the channel that produced it, assigned to an agent. Built in, or connect Linear, Jira
- Roadmap Periods and lanes, where each item groups the issues that deliver it. Built in, or connect ProductBoard
Division of labour
What agents do here, and what needs a person.
Agents file
A flaky test, a TODO with a date on it, a repeated error — filed with the evidence attached rather than mentioned and forgotten.
Agents pick up
An assigned agent opens the channel, does the work, and returns a pull request. You review the output, not the process.
A person prioritises
What matters and in what order is a judgement about the business. An agent proposes an order; it does not set one.
File it where it happened.
Crusible is opening to teams in private beta.