Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Tool-use messages now record ingest context for input normalization

Assistant messages now carry a wire_ingest_context field recording what process state was used to normalize tool inputs

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaTelemetrywhat it touches
KindInternal Changesin v2.1.265,
Group of 3 Under the hood No documentation found

Assistant messages now carry a wire_ingest_context field recording what process state was used to normalize tool inputs

What

Assistant message serialization now carries a new wireIngestContext/wire_ingest_context field alongside the existing wire_tool_inputs, filtered to only the keys present in a given tool's inputs. This records what client-side input normalization read from process state when producing a tool input, such as the current working directory a leading cd prefix was stripped against, or the timestamp stamped on a Slack send.

As part of this, the Bash tool's logic for stripping a cd <cwd> && prefix (previously two separate, ad-hoc find-and-replace calls, one for POSIX paths and one for Windows-normalized paths) was replaced with a shared helper that tries a list of candidate roots. The stripped cwd is now recorded per tool-use id in the new wireIngestContext map, which is persisted and migrated alongside wireToolInputs on saved transcripts.

Why

This lets a replayed conversation history verify each recorded tool input against the normalized input consistently, and lets the Bash prefix-stripping logic be reconstructed the same way across session resumes.

Read from
Names in the bundlewire_ingest_context
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 wire_ingest_context is used for, or where it's consumed, is not stated.

See this entry in the whole of v2.1.265 →

Feedback