Claude Code / Platform integration

Claude Code web version

The web version is suitable for initiating remote tasks, viewing progress and managing multiple sessions.

GitHub authentication method

Claude Code on the web works primarily around GitHub repositories. You can use GitHub App to authorize when getting started on the web page, or you can use the terminal /web-setup to synchronize the local gh CLI token.

way	suitable for
GitHub App	Getting started with browsers, the team wants to use automatic repair PR.
/web-setup	Individual developers already using the gh CLI.

What’s in the cloud environment?

Web sessions run in a cloud environment managed by Anthropic. CLAUDE.md, .claude/settings.json, .mcp.json, rules, skills, agents, and commands in the repository can be cloned into the cloud session with the repository; the user's local ~/.claude content will not be automatically brought over.

Static API tokens and interactive SSO do not automatically exist in cloud environments.
In-repository configuration is better suited for web sessions than user-local configuration.
Network access, environment variables, and setup scripts need to be configured separately in the cloud environment.

Configure cloud environment

The cloud environment can set the name, network access level, environment variables, and setup script. setup script is used to install dependencies, start services or prepare tools.

The cloud is suitable for running tests, starting services, and processing Issues/PRs, but it is not suitable for tasks that rely on the login status of your local browser.

# setup script example
#!/bin/bash
pnpm install
pnpm build

Complete usage points

Supplement the core concepts, operation sequences, permission boundaries and verification requirements that are easily compressed and missed in official documents, making it easier for English readers to learn completely by page.

Web cloud environment supplement

Claude Code on the web runs in a cloud environment and works primarily around GitHub repositories. It's suitable for remote tasks, handling issues/PRs, managing multiple sessions and viewing progress across devices. It does not automatically own your local login state, shell configuration, or user-level ~/.claude contents.

The cloud environment can inherit team configuration through CLAUDE.md, .claude/settings.json, .mcp.json, rules, skills, agents, and commands in the repository. When network, environment variables, dependency installation, and service startup are required, cloud environment settings and setup scripts should be used.

If the task relies on a local browser, localhost, private services, or interactive SSO, the web may not be appropriate and a local CLI, Desktop, or Chrome should be used.

Study Checklist

Put the content on this page into real tasks and use the five dimensions of entry, context, permissions, verification and team rules to check whether you have truly mastered it.

Study Checklist

After reading this page, do not just remember the concept name. You should be able to place "Claude Code web version" back into a real Claude Code engineering workflow: where the task starts, what context the system loads, which actions need approval, how the result is verified, and how to roll back when it fails.

If this is a portal or platform page, specifically confirm what contexts this portal can access: local files, cloud repositories, browser logins, team messages, external tools, and whether these contexts are sufficient to complete the verification.

Be able to describe in your own words the specific problem this page solves, rather than just reciting the title.
Able to write a minimal example task with goals, scope, prohibitions, and acceptance criteria.
Be able to determine which information should be put into the current prompt and which should be captured as project rules or configurations.
Be able to explain which long-term rules should go into CLAUDE.md, and which runtime behavior should be handled by settings, permissions, Hooks, Skills and MCP.
Ability to check diffs, command output, test results, screenshots or PR notes after a task is completed instead of just trusting the natural language summary.

If this page is used for team training, ask learners to complete a small task with Claude Code: read and explain first, submit a plan, make the smallest useful change, and close with real verification commands plus human diff review.