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 alocal_command_run(also calledcommandRun) 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/CommandOutputcomponent 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.