`/usage` Ctrl+S silently fails to copy stats screenshot on Linux/X11

Resolved 💬 1 comment Opened Apr 29, 2026 by maxjoehnk Closed May 5, 2026

Summary

Pressing Ctrl+S in the /usage stats dialog does not place anything on the system clipboard. The changelog describes Ctrl+S as copying a screenshot of the stats screen to the clipboard ("Improved resolution of stats screenshots copied to clipboard (Ctrl+S) for crisper images", "Stats screenshot (Ctrl+S in /stats) now works in all builds and is 16× faster"), but on Linux/X11 it appears to be a no-op — neither an image nor a text fallback ends up on the clipboard.

There is no user-visible error; the dialog dismisses as if the copy succeeded.

Repro

  1. claude/usage
  2. Press Ctrl+S
  3. In another shell: xclip -selection clipboard -o -t TARGETS
  4. In another shell: xclip -selection clipboard -o

Expected

Either:

  • The clipboard TARGETS list contains image/png and pasting into an image-aware app yields the screenshot, or
  • A text representation of the stats lands on the clipboard.

Actual

TARGETS lists only text MIME types and no image target:

TARGETS
MULTIPLE
TIMESTAMP
text/plain;charset=UTF-8
text/plain;charset=utf-8
UTF8_STRING
text/plain;charset=ISO-10646-UCS-2
text/unicode
text/plain
STRING

xclip -selection clipboard -o returns empty / a single newline. The clipboard is whatever it was before pressing Ctrl+S — Claude Code did not modify it.

Environment

  • Claude Code: 2.1.122
  • OS: Arch Linux, kernel 6.19.14-arch1-1 (x86_64)
  • Display server: X11 (XDG_SESSION_TYPE=x11, DISPLAY=:0, WAYLAND_DISPLAY unset)
  • Shell: zsh
  • Terminal emulator: Alacritty
  • xclip 0.13 installed; wl-clipboard not installed (not needed on X11)
  • TERM=xterm-256color

Notes

  • xclip itself works fine for other apps — echo hi | xclip -selection clipboard followed by xclip -selection clipboard -o round-trips correctly, so the system clipboard is functional.
  • No screenshot file appears anywhere under ~/.claude/, ~/.cache/, /tmp/, or ~, so this is not "saved to disk in an unexpected location" — the copy step itself isn't happening.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗