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

Entries carried over from a previous session are now tagged sessionTail and can be filtered out

Session-carried-over entries are now flagged sessionTail so lists like the model picker can exclude them

Group of 3 Under the hood Internal Changes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ModelsArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release

Unclear It is unclear what a "session tail" model entry is or what visible effect excluding it from basePickerIds has for users of the model picker.

What

Entries that come from a prior session (rather than the current one) are now tagged with a sessionTail marker in several places:

  • Recent session/path history entries get sessionTail: true when they are added to the result list.
  • Entries appended to available-model lists (both plain string values and custom-model entries) are tagged sessionTail: true as well, with matching logic switched to a new helper.
  • The model-picker state now also returns basePickerIds, a version of the picker id list with sessionTail-flagged entries filtered out, alongside the existing full pickerIds.

Why

This lets parts of the UI, like the base model picker, show only entries that belong to the current session instead of ones carried over from an earlier one, while still keeping the full list available where needed.

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 doubtIt is unclear what a "session tail" model entry is or what visible effect excluding it from `basePickerIds` has for users of the model…

See this entry in the whole of v2.1.280 →

Feedback