Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.267 ·

Conversations and sessions now track whether they originated locally or remotely

Session state now tracks whether the current conversation originated locally or remotely

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

Unclear What behavior differs based on this origin tracking, beyond restoring frame/artifact state, isn't detailed.

What

  • SessionController gained conversationOrigin and preClearOrigin state; resetting a conversation now records the prior origin and resets conversationOrigin back to "local".
  • A new markConversationRemote callback was wired into the query-event context and threaded through the main session-loop context object.
  • A Stop-hook path calls markConversationRemote to set the session's conversationOrigin to "remote".

Why This lets Claude Code distinguish conversations that originated remotely from local ones, which other logic (such as artifact-state reconstruction) can use to handle them differently.

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 doubtWhat behavior differs based on this origin tracking, beyond restoring frame/artifact state, isn't detailed.

See this entry in the whole of v2.1.267 →

Feedback