{"version":"2.1.319","anchor":"remote-and-ccr-small-changes-session-surface-voice-call-n","canonical_anchor":"remote-and-ccr-small-changes-session-surface-voice-call-n","heading":"More remote-session errors are now sorted into clear categories","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/remote-and-ccr-small-changes-session-surface-voice-call-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### More remote-session errors are now sorted into clear categories\n\nRemote sessions now record the surface they run on, treat voice calls as unclassified, and group several account errors as not allowed\n\n**What**\n\nClaude Code made several small changes to remote sessions, which run somewhere other than your own machine:\n\n- session details now include which surface the session runs on\n\n- a voice-call session type is now treated as unclassified\n\n- the errors `oauth_scope_insufficient`, `organization_banned` and `hybrid_org_surface_unavailable` are now all grouped as the account not being allowed\n\n- an added check recognises the error for a session whose security level is below organization policy\n\n**Why**\n\nRemote-session errors are being sorted into categories more finely.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}