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.277 ·

Session-start announcements can now be moved to just before the closing line

A new env var lets session-start context blocks (sandbox info, model, skills, etc.) be repositioned right before the final prompt line

Group of 2 Use it now Internal Changes
JSON All of v2.1.277
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
System PromptArea: what it touches
Internal ChangesKind: in v2.1.277,
What probably matters to youSection of the release

Unclear The finding does not say what effect this repositioning has on model behavior or when it is triggered versus the default placement.

What

At the start of a session, Claude Code attaches several 'announcement' blocks to the first message, things like sandbox instructions, environment details, the active model, proactivity notes, budget info, available tools, skill listings, output style instructions, language, and auto-mode status. A new mechanism can now move these announcements so they sit right before the closing line of the message instead of their normal position.

This behavior is controlled by a new environment variable, CLAUDE_CODE_SESSION_START_ANNOUNCEMENTS_BEFORE_PROMPT. When it's set, Claude Code checks whether the repositioning is possible (it isn't for models without system messages, when there's no user message, or when there's nothing to announce) and moves the announcements if so.

Why

Repositioning these blocks can change how the model weighs session-start context relative to the user's actual request. The feature records telemetry on whether and why the reposition happened or was skipped, which helps diagnose behavior differences tied to this setting.

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 doubtThe finding does not say what effect this repositioning has on model behavior or when it is triggered versus the default placement.

See this entry in the whole of v2.1.277 →

Feedback