Skip to content

fix(viewer): preserve semantic response chunks - #184

Draft
Lint111 wants to merge 1 commit into
Ark0N:masterfrom
Lint111:agent/split-response-viewer
Draft

fix(viewer): preserve semantic response chunks#184
Lint111 wants to merge 1 commit into
Ark0N:masterfrom
Lint111:agent/split-response-viewer

Conversation

@Lint111

@Lint111 Lint111 commented Jul 29, 2026

Copy link
Copy Markdown

Summary

Make the response viewer preserve semantic reply boundaries and support lossless whole-chunk copy on desktop and mobile.

Changes

  • Remove terminal-buffer fallback from Last Response.
    • An empty structured transcript now shows the existing empty-state message.
    • It no longer presents the entire terminal history as if it were one agent reply.
  • Store each reply's raw transcript text on its owning response node.
  • Double-click or double-tap a reply to copy that complete raw chunk.
  • Ignore copy gestures that originate from buttons, links, fields, or editable content.
  • Keep existing one-click code-block copy and diagram wrap controls unchanged.
  • Show brief visual confirmation after a successful whole-chunk copy.
  • Use mobile terminal feedback when that optional control layer is present.

Behavior

  • Last Response remains a single structured reply.
  • More remains the explicit path to the full conversation.
  • Raw Markdown, whitespace, and code fences survive whole-reply copy without depending on rendered HTML.

Validation

  • npx vitest run --config config/vitest.config.ts test/response-viewer.test.ts
    • 2 tests passed
  • npm run check:frontend-syntax
    • 26 frontend files passed
  • npm run build
    • passed

Scope

This PR does not add click-to-collapse for response messages. That interaction was discussed but is not implemented in the audited change set and should be reviewed independently from copy/source correctness.

Keep Last Response transcript-only so terminal history is never presented as one reply. Store raw message sources for lossless double-click or double-tap copy with visible feedback.
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.

1 participant