When Claude Code resumes a session or teleports one (brings a session from elsewhere into your terminal), it downloads that session's history page by page. It now stops with an error when:
- the server answers with an error status
- the reply is not in the expected shape
- a later page is not found
- it has run out of retries
Before, it returned nothing or only the pages it had downloaded so far. If the server refuses because the session needs a trusted device, Claude Code now says: "This session requires a trusted device, and this computer isn't recognized as one." It also explains how to register this computer through /login.
A failed resume or teleport is now clearly reported. Before, you could end up with an empty or cut-short session and no sign that anything went wrong.
* Added support for `forceLoginMethod: "gateway"` and `forceLoginGatewayUrl` in your own user settings on machines with no managed settings, so `/login` opens on that Claude apps gatewaysee the edit
1. Remote settings, delivered from claude.ai as [server-managed settings](/docs/en/server-managed-settings) or by a [Claude apps gateway](/docs/en/claude-apps-gateway). Claude Code fetches this source only when the session authenticates to…see the edit
In sessions signed in through `/login`, the CLI stamps each export with the authenticated user's identity, read from the gateway-issued JWT: the `user.id`, `user.email`, and `user.groups` attributes. Per-developer cost and usage attributio…see the edit
The gateway gives you per-developer usage metrics without any per-machine OTEL configuration. Claude Code emits OpenTelemetry (OTLP) metrics, logs, and opt-in traces; [Monitoring usage](/docs/en/monitoring-usage) covers everything the CLI …see the edit
/login on Claude Code changelog