{"version":"2.1.312","anchor":"session-logs-fetch-can-refuse-redirects","canonical_anchor":"session-logs-fetch-can-refuse-redirects","heading":"Fetching session logs now reports failures as errors","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/session-logs-fetch-can-refuse-redirects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Fetching session logs now reports failures as errors\n\nFetching session logs can now refuse redirects, and a failed fetch raises an error based on the response instead of returning nothing\n\n**What**\n\nClaude Code can fetch the logs of a session, the record of one conversation. That fetch now has an option to refuse redirects, where a server sends the request on to another address. When a fetch fails, Claude Code now raises an error that depends on the server's response, such as one telling you your session has expired and to run `\/login`. Before, a failed fetch returned nothing.\n\n**Why**\n\nA failed fetch now tells you what went wrong, for example that you need to sign in again, instead of failing quietly.\n\n- Area: Elsewhere\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}