[DOCS] Claude Code on the web docs do not document the in-progress provisioning checklist shown while a cloud session container starts (v2.1.195)

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/claude-code-on-the-web

Section/Topic

The "Session creation failed" troubleshooting entry under "Troubleshooting". The docs describe the failure case ("Session creation failed" or "stalls at provisioning") but do not document the v2.1.195 improvement that shows a provisioning checklist in the web UI while the container starts, so users see what is happening instead of staring at an apparently stuck session.

Current Documentation

The current troubleshooting text says:

If a new session fails to start with Session creation failed or stalls at provisioning, Claude Code could not allocate a cloud environment. Check status.claude.com for cloud session incidents Retry after a minute, as capacity is provisioned on demand * Confirm your repository is reachable. The connecting GitHub account must have access to the repository on GitHub, either through the Claude GitHub App authorization or a gh token synced via /web-setup — installing the App on the repository is not required. See [GitHub authentication options](#github-authentication-options).

There is no description of the web UI surface users see during normal startup (as opposed to failure), and no documentation of what steps the provisioning checklist reports.

What's Wrong or Missing?

Claude Code v2.1.195 improves Remote session startup by surfacing a provisioning checklist in the web UI while the container starts. The checklist walks users through the steps the session is performing (cloning the repository, restoring environment cache, applying setup script, opening the conversation surface) so they can tell normal startup from a stuck session.

The docs still treat "stalls at provisioning" as a single failure mode and do not describe what users see on the screen during a healthy startup. Users who open a cloud session for the first time after the v2.1.195 update have no doc-level explanation of the new provisioning checklist, and the troubleshooting guidance cannot help them tell a healthy but slow startup from a stuck session.

Suggested Improvement

Add a short section before "Troubleshooting" that documents the provisioning checklist, and add a note to the existing "stalls at provisioning" bullet so users can distinguish a healthy slow startup from a stuck one:

### Session startup While the cloud session container is being provisioned, the web UI shows a provisioning checklist that walks through the current step: cloning the repository, restoring the [environment cache](#environment-caching), applying the [setup script](#setup-scripts), and opening the conversation. Claude Code v2.1.195 adds the checklist so a healthy slow startup is distinguishable from a stuck one. If the checklist stops progressing for more than a few minutes, see the [troubleshooting steps below](#session-creation-failed).

And add a clarifying bullet under "Session creation failed":

* If the provisioning checklist shows progress and then stops, the session is genuinely stalled; if it never appears, the request never reached the cloud.

Impact

Medium - Makes feature difficult to understand

Additional Context

The setup-script section already describes the cache and the fact that "the setup script step is skipped" on cache hits, which is exactly the kind of step the new provisioning checklist reports. Cross-link from the new section so users who want to understand the cache hit path can find it.

Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/claude-code-on-the-web | New "Session startup" section before "Troubleshooting", plus a clarifying bullet under "Session creation failed" |

Total scope: 1 page affected