{"version":"2.1.317","anchor":"network-edge-blocked-state-and-a-assistant-conflict-check","canonical_anchor":"network-edge-blocked-state-and-a-assistant-conflict-check","heading":"Clearer message when your network or region blocks the connection","tier":"notice","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/network-edge-blocked-state-and-a-assistant-conflict-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Clearer message when your network or region blocks the connection\n\nA connection blocked by your network or region now shows 'network or region blocked - check VPN or network', and one error no longer lists `claude assistant`\n\n**Unclear.** It is not clear whether `claude assistant` can now be combined with those options or no longer goes through this check.\n\n**What**\n\nWhen the server reports that your network or region is blocking the connection, Claude Code now shows a blocked status with the hint 'network or region blocked - check VPN or network'. A VPN is a service that routes your internet traffic through another location.\n\nSome options cannot be combined with a remote backend, meaning a session that runs somewhere other than your computer. If you try, an error tells you to pick one. That error no longer lists `claude assistant`. It now lists only these:\n\n- a cc:\/\/ connect URL\n\n- `claude ssh`\n\n- `--teleport`\n\n**Why**\n\nIf you are blocked because of your network or region, the message now points you at the likely cause, such as a VPN or network setting. The shorter error suggests `claude assistant` is no longer treated as a remote backend for this check.\n\n- Area: Network\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}