Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.271 ·

Local command output now records which command produced it, enabling live rendering

Output from local slash commands now carries the command and arguments that produced it, so it can render live instead of as static text

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaTranscriptwhat it touches
KindInternal Changesin v2.1.271,
Group of 6 Under the hood

Output from local slash commands now carries the command and arguments that produced it, so it can render live instead of as static text

What

  • Local command result messages (local-command-stdout/local-command-stderr) and their internal/wrapper-level equivalents now carry a local_command_run (also called commandRun) field recording {command, args} — the command name and arguments that produced that output — with sensitive arguments redacted as ***.
  • This field round-trips through history replay (toInternalMessages), so it survives session resumption.
  • When this data is present, transcript rendering now uses a new CommandOutputSite/CommandOutput component instead of the static text renderer, enabling progressive, live display of a command's output as it runs.

Why Tracking which command produced a given output line lets Claude Code render that output live, updating as the command runs, instead of only showing it once the command finishes, and preserves that association through session history and replay.

See this entry in the whole of v2.1.271 →