Under the hood
rename_session now checks the session id and logs host-initiated renames separately
What
The control-channel rename_session request now rejects a rename if the session_id it specifies doesn't match the current session. Separately, when a rename originates from a 'host' source, it's now also recorded and propagated through a new dedicated call, in addition to the existing rename mechanism.
Why
This prevents a session from being renamed by a mismatched request and adds proper tracking for renames initiated by the host application.
Names in the bundlerename_session
Documented inclaude-code/agent-sdk/python