Which Claude Code remote setup survives a handoff?
Pilot Claude Code on the web and the CLI on a remote host with the same repository task. Choose the surface that lets a second operator reach a verifiable checkpoint within your time budget.
Measure time to a usable checkout
Pick one real task with a read-only verification command and a known starting commit. For each surface, ask a second operator to open the same revision under their own authorized access, find a named file, and run the same check. Record the checkout time, check time, and observed result separately. The terminal CLI supports direct file and command work, so use the remote-terminal pilot for jobs that depend on an existing host environment. Include a dependency or tool the job actually uses in your check. For the web pilot, confirm repository access and environment setup through the exercise. A page that loads quickly can still miss the handoff target if the operator cannot reproduce the check. Keep the starting revision and expected result identical across both trials.
Overview - Claude Code DocsTest transcript portability as a separate dependency
If you build on the Claude Agent SDK, test the session store on two disposable hosts before making transcript recovery a team requirement. On the first host, start a session in a checked-out fixture, give it a distinctive harmless marker, and capture the session ID. On the second host, use the same store and a matching working directory, then resume and ask for both the marker and a fact from the fixture. Record those answers separately. A recalled marker with the wrong file content points to checkout or working-directory drift. A readable checkout with a missing transcript points to session lookup or persistence. For ordinary web or CLI handoffs, give the next operator the commit, last check result, and next task in writing. The documented SessionStore applies to the SDK.
Persist sessions to external storage - Claude Code DocsChoose web or a remote terminal
Anthropic lists the web and the terminal CLI as Claude Code surfaces. Start with the web when a task can be specified from repository contents and reviewed from its resulting changes. Pilot the CLI on a Linux VPS when you need a custom compiler, private network access, or a particular runtime environment. With the VPS, your team owns shell access, host maintenance, and recovery.
Use the same repository revision and task in both pilots. Ask each to build the project and produce a reviewable change, then check whether the next operator can open the change and reproduce the validation. If a build dependency or internal service cannot be reached from the web environment, document that exact dependency and test it from the remote CLI before selecting the VPS.
Overview - Claude Code DocsHand over files and context together
Anthropic documents resuming previous conversations in Claude Code. In an illustrative handoff, one engineer starts a refactor on branch parser-cleanup, records the starting commit, and leaves one named test failing. Before signing off, they save the changes in an approved shared branch or workspace and leave the session identifier, the test name, and the remaining decision in a handoff note.
The incoming operator connects with their own authorized access, checks the branch and diff against the note, and tries to resume the conversation if that setup permits it. The handoff passes when they can reproduce the failing test and identify the next edit from the recovered context. If the transcript is inaccessible, open a fresh session with the note and diff. Keep the handoff usable even when conversation access differs between operators.
Common workflows - Claude Code DocsDiagnose a failed cross-host resume
For an application built on the Claude Agent SDK, Anthropic documents a SessionStore adapter that mirrors transcripts to your own backend. A session can resume on another host with a matching working directory. If your workers are replaceable, rehearse with a fresh worker and restore the repository and any uncommitted changes separately. The transcript carries conversation context, while the working tree supplies the files the next run will edit.
If the new worker opens a blank session, check that the original session identifier was saved, that the backend contains its transcript, and that the new worker uses the expected working directory. If the transcript loads but the diff is missing, inspect the workspace restore. For a straightforward terminal deployment, compare the effort of this architecture with keeping one durable remote workspace and using a written handoff.
Persist sessions to external storage - Claude Code Docs