Error reference changederrors
Nearest release: v2.1.248, published 5 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+22added
Lines−0removed
From line
85
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits189to this page, all time
The whole hunk
from line 85, old and new numbered
/
This page is larger than the 256 KiB this site keeps, so one side of the diff below stops where the stored text does.
from line 85
8585| `403` with `x-deny-reason: host_not_allowed` in a cloud or routine session | [Network](#host-not-allowed-in-a-cloud-session) |
8686| `proxy refused the connection` | [Network](#the-proxy-refused-the-connection) |
8787| `403` with `This GraphQL query is not enabled for this session` in a cloud session | [GitHub proxy](/docs/en/cloud-environments#github-proxy) |
88| `The cloud environments service returned an empty response` / `The cloud environments service returned a response in an unexpected format` | [Network](#the-cloud-environments-service-returned-an-empty-or-unexpected-response) |
8889| `Couldn't reconnect to your Remote Control session` | [Network](#couldnt-reconnect-to-your-remote-control-session) |
8990| `N sessions ended while this machine was offline — the environment was cleaned up on the server and can't be resumed.` | [Network](#sessions-ended-while-this-machine-was-offline) |
9091| `Couldn't share the transcript.` | [Network](#couldnt-share-the-transcript) |
from line 1240
12391240
12401241Before v2.1.238, Claude Code reported a refused tunnel as a generic network error.
12411242
1243<h3 id="the-cloud-environments-service-returned-an-empty-or-unexpected-response">
1244 The cloud environments service returned an empty or unexpected response
1245</h3>
1246
1247Claude Code requests your [cloud environments](/docs/en/cloud-environments) list at several points, such as when you create a cloud session from the CLI or run [`/remote-env`](/docs/en/cloud-environments#select-an-environment-from-the-cli). When it can't read the server's answer, it shows one of these messages:
1248
1249```text theme={null}
1250The cloud environments service returned an empty response (HTTP 200 with no body). This is usually temporary — try again in a moment.
1251The cloud environments service returned a response in an unexpected format (HTTP 200 with a non-JSON body). This is usually temporary — try again in a moment.
1252The cloud environments service returned a response in an unexpected format (HTTP 200 without a usable environments list). This is usually temporary — try again in a moment.
1253```
1254
1255The server accepted the request but answered with a body that isn't the environments list: empty, not JSON, or JSON without the list. This usually accompanies a service-side disruption and clears on its own. Depending on the surface that requested the list, Claude Code may add a prefix, such as `couldn't list environments:` in the `/remote-env` dialog.
1256
1257**What to do:**
1258
1259* Retry the action. Claude Code requests the list again each time
1260* If the message keeps appearing, check [status.claude.com](https://status.claude.com) for active incidents
1261
1262Before v2.1.236, Claude Code showed a raw JavaScript TypeError instead of these messages.
1263
12421264<h3 id="couldnt-reconnect-to-your-remote-control-session">
12431265 Couldn't reconnect to your Remote Control session
12441266</h3>
from line 2510
24882510
24892511### EUNKNOWN when starting a background session
24902512
2491Windows refused to start a program with an error code that has no standard name, so the failure surfaces as `EUNKNOWN`. The usual trigger is a software restriction policy, such as Group Policy or AppLocker, blocking the program being started. The error appears when you start a [background session](/docs/en/agent-view) with `/background` or `claude --bg`:
2492
2493```text theme={null}
2494Couldn't reach the background service (spawn background service: EUNKNOWN: unknown error, uv_spawn) — run 'claude daemon status'
2495```
2496
2497On some accounts the message says `daemon` in place of `background service`.
2498
2499Claude Code starts the background service through PowerShell so the service survives closing the terminal, using PowerShell 7 when it's installed and Windows PowerShell 5.1 otherwise. When neither PowerShell can run, Claude Code starts the service directly instead, so a policy that blocks only PowerShell doesn't cause this error. If you see it, the policy is blocking the Claude Code executable itself.
2500
2501Before v2.1.212, Claude Code used only Windows PowerShell 5.1 to start the service, so any machine where Group Policy blocked PowerShell 5.1 failed with `Couldn't start the session — EUNKNOWN: unknown error, uv_spawn`, even with PowerShell 7 installed.
2502
2503**What to do:**
2504
2505* If the message reads `Couldn't start the session`, upgrade to v2.1.212 or later. On earlier versions you can also run `claude daemon run` in a separate terminal first, then start the background session again. That command runs the background service in the terminal's foreground, so the service lasts only as long as that terminal stays open.
2506* If the error appears on v2.1.212 or later, ask your Windows administrator to allow the Claude Code executable in the restriction policy
2507* If the background service stops when you close the terminal, Claude Code started it without PowerShell. Install PowerShell 7, or ask your administrator to unblock PowerShell, so the service can outlive the terminal.
2508
2509## Wrapper and IDE errors
2510
2511These errors come from the program that launched Claude Code for you, such as an IDE extension or an [Agent SDK](/docs/en/agent-sdk/overview) application, rather than from Claude Code itself.
2512
2513### Claude Code pro
2513Windows refused to start a program with an error code that has no standard name, so the failure surfaces as `EUNKNOWN`. The usual trigger is a software restriction policy, such as Group Policy or AppLocker, blocking the program being started. The error appears when you start a
No line in this hunk matches that.