Claude Cloud Shift Get started

Built for Claude Code + AWS

Close the laptop.
Keep the session moving.

Move a live Claude Code session to a persistent EC2 host—transcript, memory, settings, working tree, and all.

See how it works
Claude Cloud Shift session active
~/Git-Repositories/projectzsh

❯ ccs shift

Claude Cloud Shift · session 7f3e2a

✓ prerequisites 24 checks passed

✓ worktree committed + pushed

✓ host i-05802c2335bab6dfe · running

◒ replicating untracked files

/Users/anorman/Git-Repositories/project

SESSION transcript anchor verified · 12.4 MB

REMOTE same absolute path · same conversation

↗Live shiftMove mid-thought
↯Resume intactMemory travels too
⌂Same pathNo brittle rewrites
◷Auto-stopIdle-aware guardrail
⇣Safe returnSnapshot before pull

One conversation. Two machines...or more

Everything a long-running session needs.

◎[01]

The same conversation

Transcript, memory, settings, and trust state arrive together so Claude can resume—not restart.

⌘[02]

The whole working tree

Tracked changes travel through Git. Untracked work moves separately without trampling your repository.

↗[03]

Reach it from anywhere

The host updates its own Route 53 record, then SSH and tmux keep your session one command away.

◷[04]

Stops when work stops

Activity-aware idle detection watches the transcript and attached users—not a misleading process list.

◇[05]

Persistent by design

Tools, repositories, credentials, and build trees stay on encrypted storage between starts.

↩[06]

Return without regret

A dated local snapshot lands before cloud work comes home, and transcript anchors guard both sides.

More than remote access

What Shift gives you over simple SSH.

CapabilityPlain SSH to EC2Cloud Shift
Continue the same Claude conversation×✓
Move uncommitted and untracked work safely×✓
Preserve absolute Claude state paths×✓
Reconnect through stable DNSmanual✓
Stop itself after real inactivity×✓
Bring the work home with a safety snapshot×✓

Your repository stays a Git repository. Your conversation stays one conversation.

A reversible workflow

Shift Out. Turn On. Shift Back.

Each stage is visible, repeatable, and resumable. If a step needs attention, fix it and continue from there.

01
local

Start where you are

Run ccs shift inside the conversation you want to move.

02
sync

Shift the living state

Code, untracked files, Claude state, and the exact transcript anchor move together.

03
AWS

Resume in the cloud

Attach through tmux and keep working on a persistent Amazon Linux host.

04
home

Bring it home

ccs return snapshots first, pulls the work, joins the transcript, and stops the host.

Designed for unattended work

Let Claude run.
Keep control.

Cloud Shift gives an autonomous session room to work, and gives you room room to roam.

22

One open port. SSH only, key authentication only.

1

One DNS record. The instance role can UPSERT exactly one A record.

0

Secrets in logs. Sensitive values travel over stdin and are redacted.

ccs statusus-west-2

❯ ccs status

instance running dnsagrees · 34.220.239.125 sessionattached · tmux “claude” last activity38s ago idle decisionkeep running estimated cost$0.1714 / hour
GUARDRAIL

Host stops only when the transcript is quiet and nobody is attached.

478offline tests passing
22composable commands
~1 mintypical repeat shift
$8/mostopped storage baseline
↗ Open source · MIT

Ready to leave the
laptop behind?

Bootstrap the CLI, verify your AWS access, and make the first shift.