Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Local CommandsArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release
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.
