{"version":"2.1.269","anchor":"new-agent-sdk-control-request-rename-session","canonical_anchor":"new-agent-sdk-control-request-rename-session","heading":"New agent-SDK control-request: rename_session","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-agent-sdk-control-request-rename-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New agent-SDK control-request: rename_session\n\nSDK control-request rename_session refined with remote\/host distinction and a get_memory_dialog request added\n\n**What**\n\nThe `rename_session` control-request, which lets a hosting application (or claude.ai) rename a session's title, now distinguishes two kinds of rename:\n\n- a `remote` rename, relayed from claude.ai, treated as the default\n\n- a `host` rename, made from within the hosting IDE, which Claude Code treats as if the user renamed it directly\n\nIt 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.\n\nA 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.\n\n**Why**\n\nThese 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.\n\n- Area: SDK\n- Names: `rename_session`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}