Skip to content

fix(gateway): avoid duplicating typed status message in output (#254) - #279

Open
AntoineToussaint wants to merge 1 commit into
mainfrom
fix/gateway-status-output-dedup-254
Open

fix(gateway): avoid duplicating typed status message in output (#254)#279
AntoineToussaint wants to merge 1 commit into
mainfrom
fix/gateway-status-output-dedup-254

Conversation

@AntoineToussaint

Copy link
Copy Markdown
Contributor

Closes #254.

Summary

  • Gateway Build and Lint unconditionally prepended the typed runtime status message to raw agent output, so agents that already fold the actionable message into raw output (like Generic 0.0.16) surfaced it twice.
  • Compose through a new composeStatusOutput helper that only prepends the status message when the raw output does not already carry it — generically for all agents, no Generic special-casing. Distinct status context and native output are preserved when they differ.

Test plan

  • go test ./pkg/gateway/ passes
  • New regression tests: TestBuildDoesNotDuplicateStatusMessageInOutput, TestLintDoesNotDuplicateStatusMessageInOutput (identical status/output collapses to one copy), and TestBuildPrependsDistinctStatusMessage (distinct message still prepended)

🤖 Generated with Claude Code

Build and Lint unconditionally prepended the typed runtime status
message to the raw agent output. Agents that already fold the actionable
message into raw output (as Generic does) then surfaced it twice.

Compose via composeStatusOutput, which only prepends the status message
when the raw output does not already carry it, generically for all
agents. Distinct status context and native output are preserved.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gateway should not duplicate typed runtime status messages in dev-tool output

1 participant