Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.271 ·

Command execution now records a commandRun marker on transcript messages

Command execution now attaches a commandRun marker to transcript messages

Under the hood Internal Changes
JSON All of v2.1.271
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TranscriptArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release

Unclear What consumes this new field, and how it changes what a user sees, is not specified in the finding.

What

When a command is run, whether immediately in the local session or via a bridge, the resulting transcript message now carries a commandRun field alongside its existing text and error content.

Why

This appears to record which command produced a given transcript entry, likely for tracking or displaying command-run history more precisely.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat consumes this new field, and how it changes what a user sees, is not specified in the finding.

See this entry in the whole of v2.1.271 →

Feedback