claude-code - 💡(How to fix) Fix Transcript viewer: add feedback after saving with 's' — currently looks half-broken [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46730Fetched 2026-04-12 13:34:33
View on GitHub
Comments
1
Participants
1
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×3closed ×1commented ×1

In the transcript viewer (Ctrl+R), pressing s to save the transcript produces no visible feedback. The viewer just sits there afterwards, which makes it feel like the save didn't work — or like the UI is in a half-broken state.

Root Cause

In the transcript viewer (Ctrl+R), pressing s to save the transcript produces no visible feedback. The viewer just sits there afterwards, which makes it feel like the save didn't work — or like the UI is in a half-broken state.

RAW_BUFFERClick to expand / collapse

Summary

In the transcript viewer (Ctrl+R), pressing s to save the transcript produces no visible feedback. The viewer just sits there afterwards, which makes it feel like the save didn't work — or like the UI is in a half-broken state.

Current behavior

  1. Open the transcript viewer
  2. Press s to save
  3. …nothing visibly changes

There's no confirmation that the save succeeded, no indication of where the file was written, and no hint about what to do next.

Expected / requested behavior

After saving, the viewer should at minimum show a brief confirmation. Ideally it would include:

  • A clear success indicator (e.g. ✓ Saved)
  • The absolute path the transcript was written to
  • Optionally: file size, or a hint like "press o to open" / "copied path to clipboard"

A transient status line at the bottom of the viewer (that clears after a few seconds or on next keypress) would be enough — the key thing is that the user gets some acknowledgement that the action landed, rather than silence.

Why it matters

The current silent-on-success behavior is a small UX cut but a repeated one: every time you save a transcript, you're left wondering whether it worked, and you end up dropping to a shell to ls the output directory to confirm. A one-line confirmation removes that friction entirely.

Environment

  • Claude Code CLI
  • macOS (Darwin 23.4.0)

extent analysis

TL;DR

Implement a transient status line in the transcript viewer to display a confirmation message after saving a transcript.

Guidance

  • Modify the save functionality to display a brief confirmation message, including a success indicator and the absolute path of the saved file.
  • Consider adding optional information, such as file size or a hint to open the file.
  • Use a transient status line at the bottom of the viewer that clears after a few seconds or on the next keypress.
  • Ensure the confirmation message is visible and provides clear feedback to the user.

Example

No specific code example is provided due to the lack of implementation details in the issue.

Notes

The solution assumes that the Claude Code CLI has the capability to display a transient status line and modify the save functionality. The exact implementation may vary depending on the underlying technology and framework used.

Recommendation

Apply a workaround by modifying the existing save functionality to display a confirmation message, as upgrading to a fixed version is not mentioned in the issue. This approach addresses the user's need for feedback after saving a transcript.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING