26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# Bugs
|
|
|
|
# M1 — One agent end to end
|
|
|
|
# M2 — Seeing the work
|
|
|
|
# M3 — Second vendor and review
|
|
|
|
# M4 — Merging and history
|
|
|
|
# M5 — Workflows
|
|
|
|
# M6 — Fan-out
|
|
|
|
- Cross-vendor handoffs
|
|
Forking a snapshot into a different vendor: the new session starts from a handoff bundle from `export_context` instead of the vendor's native fork, and the UI labels it a handoff, not a true fork. Same-vendor forks from a snapshot exist (see "Forking" in `docs/operations.md`).
|
|
- Fork-and-compare
|
|
A fan-out of N forks with different vendors or prompts from one snapshot, followed by a judge stage that produces a comparison with visuals.
|
|
- Just-in-time fan-out
|
|
`spawn_stages(stages[])` and `collect(stage_ids[])` MCP tools let agents build workflows on the fly, using the same stage definition format. An optional per-workflow human gate on spawning. Spawned stages show in the task's UI tree marked as just-in-time, and a just-in-time structure can be saved as a reusable workflow.
|
|
|
|
# M7 — Inbox triage
|
|
|
|
- Inbox triage agent
|
|
An agent that answers questions resolvable from the repo or docs and escalates the rest with its reasoning attached. Tune it on real inbox data.
|