Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.268 ·

New coordinator_context and context_sections system-prompt injectors

Claude Code can now inject named context sections and a coordinator's worker-tool list into the system prompt

Group of 3 Nothing to try yet In Development
JSON All of v2.1.268
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
System PromptArea: what it touches
In DevelopmentKind: in v2.1.268,
In DevelopmentSection of the release

Unclear Whether this is switched on for any account is unknown; the tengu_indexed_corbato gate controlling it has not been read.

What

  • Two new context-injection types, coordinator_context and context_sections, are added to the existing set of system-prompt injectors (environment, model, session_context, etc). coordinator_context injects the list of worker tools available to a coordinator in multi-agent ("coordinator/worker") setups, and context_sections injects arbitrary named text sections (each with a name and text).
  • These same two injectors are also available as message attachments when building a conversation, with coordinator_context only injected when a new gate check passes.
  • The session-refresh logic used when resuming a session now builds a flat list of {name, text} sections (merged from user and system context) instead of separate fields, and always marks refreshed context as bare: true on the error path instead of silently returning stale context.
  • A gate that used to suppress the environment/model/output_style/session_context/instructions/date/language injectors entirely has been removed, so these now always run.

Why This lets Claude Code pass structured, named context (like a coordinator's list of worker tools) into the system prompt in a more organized way, and makes session resumption more reliable by always refreshing context sections instead of occasionally reusing stale data.

Read from
Feature flag
tengu_indexed_corbato Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.268: off

Read once, for one account on one subscription tier, against v2.1.268. It isn't a statement about your account. What a flag value here can and cannot tell you

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 doubtWhether this is switched on for any account is unknown; the `tengu_indexed_corbato` gate controlling it has not been read.
The name it cites is new in this buildNew in this build: tengu_indexed_corbato

See this entry in the whole of v2.1.268 →

Feedback