Skip to main content
A solution is one atomic, agent-scoped suggestion that addresses a set of findings — “rewrite the voicemail-detection branch of the prompt”, say, in response to a cluster of Voicemail not detected findings. Where a finding is the durable record of a problem, a solution is the record of the fix: what you’ll change, who owns it, and how far along it is. A solution is bound to a single agent. It inherits that agent from the findings you build it from — specifically the first agent on the seeding finding — so a finding with no agent can’t seed a solution.

​
Draft vs. published

Every solution starts life as a draft: a private idea with no workflow status, hidden from the main Solutions 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:
ActionResult
PublishMoves to the backlog status and joins the published list.
DiscardMoves to the cancelled status.
draft is a separate flag from status — a draft simply has no status yet. You can’t set a workflow status while a solution is still a draft; publish or discard it first.

​
Status workflow

Once published, a solution 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 solution

FieldWhat it is
TitleShort headline (optional, up to 255 characters).
DescriptionRich text (Tiptap / ProseMirror JSON) — the proposed change, rationale, links.
AgentThe agent the solution targets, derived from its findings.
FindingsOne or more linked findings the solution addresses.
AssigneeThe org member who owns the fix (must belong to the org).
Statusnull while a draft, then one of the five workflow states.
GeneratedWhen the solution was created — a solution can be drafted by a person or surfaced by AI.

​
Acting on a solution

From a solution’s detail page — or its card on a finding — a few actions sit alongside the title:
ActionWhat it does
SolveOpens the in-product assistant on a new chat with a prompt that links this solution and asks it to apply the change, keeping the solution’s status up to date as it makes progress.
Copy as promptCopies the full solution (title, summary, linked findings) to your clipboard as a ready-to-run prompt, to paste into any other tool.
Copy linkCopies a direct link to the solution.

​
Linking findings

A solution links to findings through the solution_findings join, and the relationship is many-to-many: one solution can address several findings, and you can link or unlink them as your understanding changes. Deleting a solution 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 solutions linked to it, so you can track the fix alongside the problem. See Findings.

​
Programmatic access

Solutions are MCP-only today — there is no /v1/solutions 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 solution. 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.
See the MCP reference for full tool schemas.
  • Findings — the problems a solution addresses.
  • Reports — written analyses of the operation a solution lives in.
  • Agents — every solution is scoped to one agent.
  • Triage findings — the workflow from a finding to a published solution.
  • MCP — draft and manage solutions programmatically.