Nothing to try yet
No documentation found
Two transcript debugging aids, raw tool inputs and exact wire block order, are computed but each sits behind its own gate.
Message normalization now computes two extra debugging aids on every pass: a wire_tool_inputs field (populated only when the resolved value is a non-empty object, otherwise left void 0) attached to tool-call output, and a reordering of assistant content blocks to match exact API wire order before they're written into transcripts/JSONL. Both are computed unconditionally and fed into the message pipeline, but each is controlled by its own gate function, so neither is active yet.
Flag reading moved
The flag server now returns on for tengu_humble_hammock, read as this account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved
The flag server now returns off for tengu_humble_hammock, read as this account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this build
New in this build: tengu_humble_hammock