Workbranch › Guides

How to use Claude Code on the web

Claude Code doesn't have to run on your laptop. At claude.ai/code it runs in the cloud, keeps going when you close the lid, and pushes a branch for you to review. This guide covers the plans, connecting GitHub, starting a task, and taking the work back to your own machine.

Updated 30 October 2026

Steps and names below follow Anthropic's Claude Code documentation as of October 2026. The web interface may change.

Who can use it

Cloud sessions are included on Pro, Max and Team plans, and for Enterprise users with premium seats or Chat + Claude Code seats. You need a GitHub repository; to start something new, create a repository with a README on GitHub first. Organizations with Zero Data Retention, the HIPAA configuration or customer-managed encryption keys can't use cloud sessions.

Connect GitHub (one time)

1. Open claude.ai/code and sign in with your Claude account.
2. Follow the prompt to connect GitHub and approve the request on GitHub's authorization page.
3. For private repositories, install the Claude GitHub App on the GitHub account or organization that owns them. A GitHub organization owner may need to approve it. You can click Skip and do this later.
4. Set up the environment. On Pro and Max, an environment called Default is created for you. On Team and Enterprise, a Create your first cloud environment form appears: leave the values and click Create & finish.

The Default environment uses Trusted network access: common package registries and other allowlisted domains, nothing else. You can edit it later to change network access, add environment variables or a setup script.

Start a cloud session

1. Click the repository selector below the input box and choose a repository. You can add more than one. To start from a feature branch, change the branch next to it.
2. Choose a permission mode: Plan (Claude proposes an approach and waits for your approval before editing), Accept edits (Claude makes changes and pushes without stopping), or Auto where your organization allows it.
3. Describe the task specifically: name the file or function, paste any error output, and say what should happen.
4. Press Enter. Claude clones the repository into an isolated virtual machine, runs your setup script if you have one, and starts working. You can watch and steer, or leave.

Each task gets its own session and branch, so you can start several in parallel. Sessions are also reachable from the Code tab in the Claude mobile app.

Review and open a pull request

1. When Claude pushes its branch, the Changes card beside the chat shows lines added and removed. Click the counts to open the diff.
2. Hover over a line and click + to leave an inline comment. Comments are sent with your next message.
3. Click Create PR. To open a draft instead, right-click it and choose Create draft PR.
4. Keep going in the same session: paste CI failures or review comments and ask Claude to fix them.

Move a session to your computer

With the Claude Code CLI signed in to the same claude.ai account, run claude --teleport in a checkout of the same repository to pick a cloud session, or claude --teleport followed by the session ID. Inside a running CLI session, /teleport does the same, and on claude.ai/code Open in > Terminal copies the command. Teleport needs a clean working directory (it offers to stash changes) and a branch that was pushed. After that, the terminal has its own copy: new local work doesn't appear in the web session.

The other direction works for new tasks only: claude --cloud "your task" starts a fresh cloud session for the current repository, cloning your branch from GitHub, so push local commits first. An existing terminal session can't be pushed to the cloud from the CLI.

Good to know

• Cloud sessions share rate limits with all your other Claude use.
• Sessions don't use your local configuration; they only see what's in the repository, such as .claude/settings.json and subagents in .claude/agents/.
• Terminal-only commands such as /plugin or /resume aren't available in the cloud; /compact, /context and /clear work.
• Your GitHub credentials stay on Anthropic's servers and don't enter the session's machine.
• Sessions stop after a period of inactivity. Reopening one restores the conversation but not commands that were still running.

If it doesn't work

• No repositories appear: private repositories show up only where the Claude GitHub App is installed and has access to them.
• "Claude Code isn't available on your account": switch to the right organization, or ask an Owner for a seat that includes Claude Code.
• Session creation failed: check status.claude.com and retry after a minute.
• Teleport says it can't get the organization: run claude auth login and sign in with your claude.ai account rather than an API key.

Carry decisions between sessions

Parallel cloud sessions each end with their own decisions and loose ends. The Workbranch connector for Claude lets you say "save this to Workbranch" so those tasks, decisions and open questions land in one project, sorted by topic. See Workbranch for Claude. For the local CLI, see getting started with Claude Code.

Sources

• Use Claude Code with your Pro or Max plan (Claude Help Center, checked 30 October 2026)
• Get started with Claude Code in the cloud (Claude Code docs, checked 30 October 2026)
• Use Claude Code in the cloud (Claude Code docs, checked 30 October 2026)

Frequently asked questions