{"version":"2.1.290","anchor":"code-session-creation-requires-a-usable-session-id","canonical_anchor":"code-session-creation-requires-a-usable-session-id","heading":"Starting a code session now rejects an unusable session id","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/code-session-creation-requires-a-usable-session-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Starting a code session now rejects an unusable session id\n\nWhen creating a code session, Claude Code now checks that the session id it gets back is usable, not just present\n\n**What**\n\nWhen Claude Code creates a code session, the server sends back a session id. Claude Code used to check only that the id was there. It now also checks that the id is valid. If it is not, Claude Code logs \"No usable session.id (cse_*) in response\" instead of \"No session.id (cse_*) in response\".\n\n**Why**\n\nA session id with the wrong format is now caught at the start instead of being used.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}