{"version":"2.1.323","anchor":"rename-session-now-returns-a-proper-error-when-no-callback-i","canonical_anchor":"rename-session-now-returns-a-proper-error-when-no-callback-i","heading":"rename_session error is now built the standard way when renaming is unsupported","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/rename-session-now-returns-a-proper-error-when-no-callback-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### `rename_session` error is now built the standard way when renaming is unsupported\n\nWhen a host program cannot rename sessions, the `rename_session` error is now built by Claude Code's shared error code with the same text\n\n**What**\n\n`rename_session` is a request a program driving Claude Code can send to rename a session. When that program has not set up a way to handle renames, Claude Code replies with an error. That error is now built by Claude Code's shared error code instead of by hand. The message still reads \"rename_session is not supported in this context (onRenameSession callback not registered)\".\n\n**Why**\n\nPrograms that handle this error get it in the same form as other errors, though the exact shape may differ slightly from before.\n\n- Area: SDK\n- Names: `rename_session`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}