Claude Code on the web and iPhone

Start a small coding task in your browser and check the same session on your iPhone. Claude runs the work in a cloud environment, and you review the resulting branch before it becomes part of your project.

Before you start

• A Claude Pro, Max, or Team account, or an eligible Enterprise seat: premium or Chat + Claude Code. Organization policy can restrict access; cloud sessions are unavailable with Zero Data Retention or the HIPAA configuration.
• An existing GitHub repository you may let Claude access. Use a practice repository for your first task and choose the intended starting branch.
• The current Claude iOS app, signed in to the same Claude account and organization as your browser.
• A task whose required files are already on GitHub, with a clear expected result. Cloud sessions do not use your laptop’s unsaved files or local configuration.

Want to do it yourself?

Difficulty

6 out of 10

Estimated completion time

45–90 minutes

Skills you’ll need: Connect a repository, confirm the cloud branch, continue a session across devices, and review the diff before a pull request.

I’ll do it myselfI’d rather get help

How this helps your brand

Following the same cloud session across devices can help you keep a small project update moving. Reviewing the branch and actual check results protects the distinction between finished agent work and an accepted release.

1. 1

   Step 1: Connect the repository from your browser

   Open claude.ai/code, sign in, and follow the GitHub connection flow. Review the permissions on GitHub’s authorization page before continuing.

   For a private repository, the Claude GitHub App must be installed with access to that repository. If the repository is missing, check the installation’s repository access in GitHub’s Installed GitHub Apps settings, or ask its organization owner. On Claude Team and Enterprise accounts, an Owner must also enable the GitHub connector.

2. 2

   Step 2: Confirm the cloud environment and branch

   Complete the Default environment setup if onboarding asks for it. The environment controls network access and startup commands. The initial Trusted network setting reaches common package registries and other allowlisted domains.

   Choose the repository below the input box. In the browser, confirm the starting branch in the control after the repository selector. Use Plan mode for this first exercise so you can review the approach before editing.

   Pick a change that does not need a local-only service. Updating an existing setup explanation in a README is a useful first task because you can compare the result directly with the repository.

3. 3

   Step 3: Submit one task and approve its plan

   Paste the prompt below and send it. Read the proposed files and checks. Correct any wrong assumption before approving implementation.

   The session runs in the cloud and can keep working after you close your laptop. In the normal cloud workflow, Claude pushes a working branch when it reaches a stopping point. Treat that branch as work to review.

4. 4

   Step 4: Continue the same session on iPhone

   Open the Claude app’s Code tab and select the session you started in the browser. Read the progress and send a relevant follow-up, such as asking Claude to explain a changed setup instruction.

   Confirm the session and repository before replying so you do not start a duplicate task. This is the same cloud work viewed from another device; your laptop does not need to stay open for it to continue.

   Illustrated exampleTwo devices, one continuing session

   One cloud session · exampleClarify README setupRepository: practice-site · starting branch: main

   BrowserStart here

   Clarify README setup

   Use package.json to correct the setup instructions in README.md.

   Plan approvedUpdating the same cloud task

   iPhone · Code tab

   Clarify README setuppractice-site

   Explain why you changed that setup instruction.

   Follow-up in the existing session

   Match the account, organization, repository, and session before replying. The cloud work continues when your laptop closes.

5. 5

   Step 5: Resolve failures using their actual output

   If setup or a check fails, read the failing command and its output. A registry blocked by the environment’s network settings is different from a test failure in your code. Review the environment configuration before retrying a setup failure.

   If Claude cannot run a check because it needs your local tools or service, have it state that limitation. Run that check in your normal development environment before accepting the change. Do not turn an unrun test into a passing result.

   Illustrated exampleA setup problem needs a different response from a failing test

   Three different reportsRead what actually happened

   Setup blocked

   npm installRegistry request blocked by network policy

   Review the cloud environment’s network access, then retry setup.

   Check failed

   npm testExpected 200, received 500

   Read the failing test and investigate the code or fixture.

   Not run

   npm run test:localRequires a service on your laptop

   Run it in your normal environment before accepting the change.

   Sample output, assuming these scripts exist in the repository. “Not run” is an open check, never a passing result.

6. 6

   Step 6: Review the diff and create a draft pull request

   Back in the browser, select the added-and-removed-lines indicator to open the diff. Read each changed file. Select a line to add feedback, then send a message so Claude receives the queued comments.

   When the change and evidence are ready, use Create PR and choose a draft. Open the pull request on GitHub and inspect Files changed against your requested scope. Keep it for review until the checks you need have passed and you are ready to merge.

   Illustrated exampleFollow the change from diff to draft

   Example working branchclaude/readme-setup → main

   1 file

   README.mdIllustrative diff

   ## Start development

   −

   RemovedRun npm start.

   +

   AddedRun npm run dev.

   Evidence: package.json defines the development script as dev.

   1. 1
      Inspect the changed linesOnly the requested README instruction changed.
   2. 2
      Send your feedbackAfter adding line comments, send a message so Claude receives them.
   3. 3
      Create a draft PRInspect Files changed on GitHub and resolve any outstanding checks.

   Draft · awaiting reviewMerge only when you are ready.

Work on one small change in this repository.

Starting branch: [branch]
File and problem: [path and what needs correcting]
Required result: [exact wording or behavior]
Evidence to use: [existing files that support the change]
Checks: [commands or inspection steps and expected results]

First propose the files you will change and the checks you will run. Wait for my approval of the plan. After approval, make only that change and preserve unrelated work. Do not invent setup commands or configuration values. Report changed files, actual check results, and anything the cloud environment could not verify. Prepare the branch for my review, but leave pull request creation and merging to me.