Sequential tool dispatch with per-result previews and error handling #707

Closed
opened 2026-10-27 13:37:25 +00:00 by sam · 0 comments
Owner

Build the sequential tool dispatch pipeline: invoke tools one-at-a-time, capture per-result previews (truncated output for context-feed), and implement error classification with graceful fallback. Each result should produce a short preview snippet for inclusion in the conversation context.

Notes

2026-09-19 analysis: exact-title duplicate pair. Each 'Verify: X' bead has a non-prefixed twin (167->146, 157->163, 159->182) from a doubled import. The implementation twin of 167 (archie-core-...-146) is verified complete and closed. Resolve each pair to one bead.
CORRECTION to the previous note: these are implementation/verification PAIRS linked by VALIDATES/VALIDATED BY (an upstream 'Verify:' discipline), not duplicate imports. Only the impl side needs an open bead once the impl has landed; the Verify side is the adversarial-review pass.
2026-09-19 analysis: per-result previews + error classification ARE present in internal/gateway/stream.go (toolPreview, toolProgressBlock, cleanToolError -> done/failed/stopped, RenderToolCall/FailureKey). Whether the dispatch loop is strictly one-at-a-time and whether error fallback matches the bead's wording was not verified; confirm before closing.
Design: docs/prds/mcp-tool-completion.md#sequential-tool-dispatch-with-per-result-previews-182. Coexists with closed #183 concurrent dispatch as a separate DispatchMode. Suggested council lens: lens-maintainer.

Close reason

Closed


Imported from beads archie-core-1786637494559-182-410c3c4c · GitHub #203 · type task · priority P2 · created 2026-08-08 · closed 2026-10-01

Build the sequential tool dispatch pipeline: invoke tools one-at-a-time, capture per-result previews (truncated output for context-feed), and implement error classification with graceful fallback. Each result should produce a short preview snippet for inclusion in the conversation context. ### Notes 2026-09-19 analysis: exact-title duplicate pair. Each 'Verify: X' bead has a non-prefixed twin (167->146, 157->163, 159->182) from a doubled import. The implementation twin of 167 (archie-core-...-146) is verified complete and closed. Resolve each pair to one bead. CORRECTION to the previous note: these are implementation/verification PAIRS linked by VALIDATES/VALIDATED BY (an upstream 'Verify:' discipline), not duplicate imports. Only the impl side needs an open bead once the impl has landed; the Verify side is the adversarial-review pass. 2026-09-19 analysis: per-result previews + error classification ARE present in internal/gateway/stream.go (toolPreview, toolProgressBlock, cleanToolError -> done/failed/stopped, RenderToolCall/FailureKey). Whether the dispatch loop is strictly one-at-a-time and whether error fallback matches the bead's wording was not verified; confirm before closing. Design: docs/prds/mcp-tool-completion.md#sequential-tool-dispatch-with-per-result-previews-182. Coexists with closed #183 concurrent dispatch as a separate DispatchMode. Suggested council lens: lens-maintainer. ### Close reason Closed --- _Imported from beads `archie-core-1786637494559-182-410c3c4c` · GitHub #203 · type task · priority P2 · created 2026-08-08 · closed 2026-10-01_
sam added the mediumtask labels 2026-10-27 13:37:25 +00:00
sam self-assigned this 2026-10-27 13:37:25 +00:00
sam closed this issue 2026-10-27 13:37:25 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#707