Anthropic's `claude-code` binary adds strings referencing "claude-haiku-3-5" and a "featur

EXHIBIT 1771 · URGENT

Oct 1, 2026 01:22 UTC binary @anthropic-ai/claude-code-darwin-arm64

Anthropic's `claude-code` binary adds strings referencing "claude-haiku-3-5" and a "feature_multi_turn_ask" flag, suggesting new model and multi-turn interaction features.

READY TO POST:

anthropic's claude-code binary just got an update referencing "claude-haiku-3-5" — could we see a new haiku variant soon?

looks like anthropic is working on a "feature_multi_turn_ask" flag within claude-code. multi-turn interactions might be getting an upgrade.

⚠️ FROM COMPILED BINARY — lower confidence, verify before posting. (May include bundled-dependency strings, not just first-party changes.) @anthropic-ai/claude-code-darwin-arm64 2.1.285 -> 2.1.286: +13806 strings, -11738 strings, 28 interesting [model_id] (2) + /$bunfs/root/claude-code.d.ts-015d8aac.txt.zst + claude-haiku-3-5 [feature_flag] (16) + **`feature_multi_turn_ask` is at 0%** + <${mj}>No completion record was found for them in the previous session. ${h} Task ids in this notification beginning with "${Ge}" are internal scan markers, not tasks.</${mj}> + @internal Epoch ms on the session server's clock when it received the HTTP request that delivered this message. Written by the session server; the CLI copies it to the turn's result as user_message_server_received_wall_ms. + @internal Input tokens of the model call whose send time is request_sent_wall_ms: input_tokens + cache_read_input_tokens + cache_creation_input_tokens from that call's message_start. Lets a consumer group turn latency by prompt size. Present only with request_sent_wall_ms, and only when the sum is a + @internal The server_received_wall_ms of the user message that user_message_uuid names, copied unchanged, so the session server can measure from its own receipt to request_sent_wall_ms (two machines' clocks) without keeping the receipt time. Present only with request_sent_wall_ms, and only when that + Claude Code does not send first-party-only beta features to this session's API provider + In auto mode the client adds an \`anthropic-beta\` value and a top-level + Internal subagent for workflow script orchestration.( + Turn the flag on or rollout incrementally when you're ready for users to get it, at https://featureflags.com/flags/feature_multi_turn_ask. + anthropic[-_]beta + internal_querierJ + learn: I gated `feature_multi_turn_ask` in the flag dashboard at 0% rollout + parameters). On \`/v1/messages\` pass body fields and \`anthropic-beta\` values + retr