{"version":"2.1.290","anchor":"code-session-list-http-status-in-fetch-errors-and-sanitized","canonical_anchor":"code-session-list-http-status-in-fetch-errors-and-sanitized","heading":"Session list errors show the HTTP status, and titles are cleaned up","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/code-session-list-http-status-in-fetch-errors-and-sanitized","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Session list errors show the HTTP status, and titles are cleaned up\n\nFailing to fetch code sessions now reports the HTTP status code, and session titles are cleaned and squeezed onto one line\n\n**Unclear.** Exactly which characters the title cleanup removes is not stated.\n\n**What**\n\nWhen Claude Code cannot fetch your list of code sessions, the error now reads \"Failed to fetch code sessions: HTTP\" followed by the status number. Previously it gave the server's status text. The status number is a code such as 404 or 500.\n\nSession titles in the list are now cleaned before they are shown, and runs of whitespace in them are collapsed into single spaces. A title that is not text shows as \"Untitled\".\n\n**Why**\n\nTitles sent by the server can no longer bring stray control characters or line breaks into the session list. The status code in errors is also easier to look up than free text.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}