Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsIf Claude Code cannot start a cloud session or cannot see a GitHub repository, first separate an account or organization-policy problem from a GitHub authorization problem. Cloud sessions require an eligible Claude account and a supported sign-in; repository visibility then depends on whether you connected GitHub through the Claude GitHub App or shared access through the local gh CLI.
First confirm that cloud sessions are available to your account
A cloud session runs on cloud infrastructure rather than on your computer. It is different from Remote Control, which lets you connect to a local CLI session from another device. Anthropic’s Claude Code cloud documentation lists Pro, Max, and Team plans as eligible, along with Enterprise users who have premium seats or Chat + Claude Code seats. An organization can also disable cloud sessions by policy.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
- If the error says your organization disabled cloud sessions, ask an organization administrator to check the policy. Reconnecting GitHub will not override it.
- If the message refers to a third-party model provider, cloud sessions are not available through that provider.
- If you see “Unable to get organization UUID,” an API-key-insufficient message, or a session-picker loading error, check whether the CLI is using API-key authentication or stale account information. Cloud CLI workflows require sign-in to the relevant claude.ai account, not API-key-only authentication.
To refresh the account state, run /login in Claude Code, sign in to the Claude account that should own the session, and retry. Commands such as claude --cloud and claude --teleport require the CLI to be signed in to that account.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose the right GitHub connection and check its access
Claude Code documents two ways to make repositories available. They grant access differently, so identify which route you used before changing permissions.
| Connection route | Repository reach | Setup and feature notes |
|---|---|---|
| Claude GitHub App | Public repositories and private repositories where the app is installed. | Authorize it during web onboarding. The app must be installed for Projects and Auto-fix requirements described in Anthropic’s cloud-session documentation. |
/web-setup with the local gh CLI |
Repositories the signed-in gh identity can access; Claude receives the local CLI token. |
Run /web-setup in the terminal and complete the connection for the intended Claude account. In Team or Enterprise, Quick web setup can hide this command if the organization toggle is off; an Owner controls that toggle. |
If a private repository is missing
- With the GitHub App route, verify that the app is installed on the specific private repository—not merely authorized for another repository or organization.
- With
/web-setup, check which GitHub identity is active inghand confirm it can see the repository. Then confirm the setup completed for the Claude account you are using. - Check that you opened the session under the same Claude account or organization that owns the GitHub connection.
For the token route, the token’s existing repository access determines what the cloud session can reach. For the app route, app installation determines private-repository access. Neither route makes a repository visible if its required authorization is absent.
Tell provisioning failures apart from repository failures
“Session creation failed” or a session that stays at provisioning does not necessarily mean GitHub authorization is broken. Anthropic notes that a VM may not have been allocated. Check Claude’s service status for a cloud-session incident, wait about a minute and retry, then verify that the selected GitHub connection can reach the target repository.
Rank #2
Know which version of your repository the cloud session receives
When you start a CLI cloud session with --cloud, Claude ordinarily clones the current branch from the current directory’s GitHub remote. Unpushed local commits are not part of that remote snapshot; push them before starting if the task depends on them.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If there is no GitHub remote, or the Claude GitHub App is not installed on the repository, Claude can use a local repository bundle instead. You can request bundling with CCR_FORCE_BUNDLE=1 when a normal remote clone would otherwise be used. Bundle requirements and behavior are documented in Anthropic’s cloud-session guide:
- The repository must be a Git repository with at least one commit.
- Bundles under 100 MB are supported. Larger repositories may fall back to narrower representations and can still fail.
- Untracked files are excluded. Stage any untracked files the cloud task needs.
- On macOS, Linux, and WSL, uncommitted changes to files that look sensitive—such as
.env,*.tfvars,id_rsa, and*.pem—are left on the local machine. On native Windows, uncommitted changes to tracked files are uploaded as-is. - A bundle session can push results to GitHub only if the connected GitHub identity has push access.
Before starting, inspect the staged, committed, and uncommitted content that may be uploaded. Do not assume all uncommitted secrets are excluded on every platform.
Use the diagnostics that match the failure
claude doctorfrom the shell runs read-only installation and settings diagnostics, including validation errors and warnings. Use it when Claude Code cannot start./doctorinside a running session checks installation, settings, extensions, and context./mcpchecks MCP server status. Use it when MCP servers are not loading or responding as expected.
For login loops or 403 errors, follow the installation and login troubleshooting guidance; for settings that do not apply or MCP configuration problems, investigate configuration; for API errors, consult the error reference. Anthropic links these references from its Claude Code troubleshooting documentation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Account for organization network and security constraints
In Anthropic-hosted cloud sessions, API calls come from Anthropic-managed infrastructure. Sessions routed to a self-hosted environment use the organization’s network. Anthropic says organizations that use Anthropic API IP allowlisting will see authentication failures for Anthropic-hosted cloud sessions unless those hosted services are exempted. If authentication fails in an organization-managed environment, ask the administrator whether the session is hosted or self-hosted and whether the organization’s network policy applies; changing a local firewall is not an established fix.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →For Anthropic-hosted environments, Anthropic says Git credentials and signing keys stay outside the sandbox, and Git operations pass through a proxy that authenticates for the session with scoped credentials. Self-hosted environments use their own Git credentials and carry their own isolation responsibilities. Do not extend the hosted-environment assurances to self-hosted deployments.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
