New strings in Claude Code's native binary suggest internal worker results, system notific

EXHIBIT 2098 · URGENT

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

New strings in Claude Code's native binary suggest internal worker results, system notifications, new API endpoints, and hints at internal tool usage and rule-based decision reasons.

READY TO POST:

claude code's latest binary update hints at more nuanced internal signals and notifications. seems like they're refining how the system communicates within itself.

seeing some new api endpoints and internal decision logic in the claude code binary. could be laying groundwork for deeper integration or advanced internal tooling.

⚠️ 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.300 -> 2.1.301: +13752 strings, -12844 strings, 19 interesting [model_id] (1) + /$bunfs/root/claude-code.d.ts-a75b5762.txt.zst [feature_flag] (11) + ${v} Worker results and system notifications are internal signals, not conversation partners \u2014 never thank or acknowledge them. Summarize new information for the user as it arrives. + <${l$}>No completion record was found for them in the previous session. ${w} Task ids in this notification beginning with "${st}" are internal scan markers, not tasks.</${l$}> + @internal Only on the assistant message that reports a refusal: the API msg_* id of the refused response (message.id on this message is a local UUID). Absent when the CLI has no well-formed id for it.Q + @internal Path of the background task's output file on the machine that keeps the command, when that is not this process> + @internal With decision_reason_type 'hook': the event of the hook that asked. 'PreToolUse': the terminal's dialog names the hook 'PreToolUse:' followed by tool_name. 'tool.check': it names it 'tool.check'. A host can write the same, as plain text. Absent for any other hook. For display only: never a + @internal With decision_reason_type 'rule': the source of the rule in the decision reason (a PermissionRuleSource word). It names the first rule that matched, not the strongest, and says nothing of what that rule hides. For the host's logs: a host should not decide by it.Q + SDK betas dropped: experimental betas are disabled by your organization's policyA + experimental? + internalHardDenyB + internal_querier + tengu_ccr_plugin_refresh_in_idle_enabled* [endpoint] (7) + /api/frame/deploy/direct + /api/frame/perm/q + /v1/messages3 + /v1/sessionsH + http://localhost + http://localhost:<port>/callback~ + will NOT apply (see h