Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

New agent-SDK control-request: rename_session

SDK control-request rename_session refined with remote/host distinction and a get_memory_dialog request added

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaSDKwhat it touches
KindInternal Changesin v2.1.269,
Under the hood

SDK control-request rename_session refined with remote/host distinction and a get_memory_dialog request added

What

The rename_session control-request, which lets a hosting application (or claude.ai) rename a session's title, now distinguishes two kinds of rename:

  • a remote rename, relayed from claude.ai, treated as the default
  • a host rename, made from within the hosting IDE, which Claude Code treats as if the user renamed it directly

It also carries an optional session_id, so if a rename request arrives for a session the process has already left (for example after /clear or after resuming a different session), it's refused instead of being applied to the wrong session.

A related new internal request, get_memory_dialog, lets a host application fetch the same rows and toggle states shown in the /memory dialog (instruction files, memory folders, auto-memory and auto-dream toggles) so it can render its own version of that dialog instead of the terminal one. Requesting it clears the session's memory-file cache first, the same as running /memory does.

Why

These give host applications finer control and visibility over session naming and memory settings without needing the terminal UI, and prevent a stale rename from silently landing on the wrong session after a /clear or resume.

Read from
Names in the bundlerename_session
What the documentation says

See this entry in the whole of v2.1.269 →