pastilhasandClaude Opus 5
fc40beca68
Five Bash rows in a trace read `cd /home/…/platform && git status…`, `echo "=== server-side…`, `echo "=== opencode handler…` — cut, every one of them, exactly where they started being useful. Two things conspired. The summary showed the head of a compound command, which is usually scaffolding: a `cd` into the repo, or an `echo` labelling output for a human. And both `slice()` and CSS `truncate` drop the tail, which is where the identity lives — the filename that distinguishes ten Reads sharing a directory, the target a command acts on. So skip a leading `cd`/`echo` up to its `&&`, and pin the tail as its own non-shrinking span so the head ellipsises and the cut lands in the middle at whatever width the panel is. Both are display only: expanding the row, and the copy button, still give the command verbatim. The right margin traded `done` for what the call found. Success was the loudest colour on the row and reported the least interesting fact about it, once per row; a failure still earns its red. In its place the count that used to cost an expand to learn — `no matches`, `12 lines`, `3 files`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>