Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
Unclear What wire_ingest_context is used for, or where it's consumed, is not stated.
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.
