Changes are included in the Improve plan. On other plans the Changes page shows what changes do and which plan unlocks them. See Plans, limits and retention.
Draft vs. published
Every change starts life as a draft: a private idea with no workflow status, hidden from the main Changes list. The list has three views — Published, Drafts, and All — so drafts stay out of the shared worklist until someone signs off. A draft leaves draft state one of two ways:draft is a separate flag from status — a draft simply has no status yet.
You can’t set a workflow status while a change is still a draft; publish or
discard it first.
Status workflow
Once published, a change carries one of five statuses:backlog, todo,
in_progress, done, and cancelled for work you abandon. They’re ordinary
workflow states — set whichever reflects reality, there’s no forced
progression.
Anatomy of a change
Change types
Every change carries a type that categorises the kind of work it involves. Five types are built in and available to every org:
Owners and admins can define custom types for the org under
Settings → Organization → Change types — give each a name and a color. A
change defaults to Generic; set its type from the change detail page or when
drafting it. Deleting a custom type reverts any change using it back to Generic.
Acting on a change
From a change’s detail page — or its card on a finding — a few actions sit alongside the title:Linking findings
A change links to findings through thesolution_findings join, and the
relationship is many-to-many: one change can address several findings, and
you can link or unlink them as your understanding changes. Deleting a change
removes its finding links by cascade but never deletes the underlying
findings — the problems outlive any single proposed fix.
A finding’s detail page surfaces the changes linked to it, so you can track
the fix alongside the problem. See Findings.
Programmatic access
Changes are MCP-only today — there is no/v1/changes REST
endpoint. Over MCP an agent can draft and manage them end to end:
list_solutions/get_solution/list_solution_findings— read.create_solution— draft one change (optionally with atype). It inserts exactly one draft per call, so never bundle several ideas into one body — call it again for each distinct suggestion.publish_solution(→backlog) /discard_solution(→cancelled) — move out of draft.update_solution— edit title, description, status, or assignee.link_finding_to_solution/unlink_finding_from_solution— manage linked findings.
Related
- Findings — the problems a change addresses.
- Reports — written analyses of the operation a change lives in.
- Agents — every change is scoped to one agent.
- Triage findings — the workflow from a finding to a published change.
- MCP — draft and manage changes programmatically.

