Workspaces, sessions, and persistence

A workspace belongs to a project

Juiced selects a persistent cloud workspace from your local project path. Two directories with the same name stay separate because the selection includes a hash of the resolved path. Linked Git worktrees are supported.

A workspace keeps your remote code, Claude login, and saved conversations between runs. Workspaces do not share files or Claude credentials.

To choose a workspace explicitly, put the option before the command:

juiced --workspace my-project claude

Detach while Claude keeps working

Enter /detach or close your terminal to disconnect while the remote turn continues. Your laptop does not need to stay connected for the cloud process to work. Completion, errors, permission requests, and compute limits can still stop or pause progress.

/exit and /quit stop the remote process. During a turn, Esc or Ctrl+C interrupts Claude.

Reconnect to the same conversation

Run juiced claude in the same terminal tab, project, and workspace to reconnect to its saved session. From another tab, list the sessions and select the ID you want:

juiced claude sessions
juiced claude --session ses_…

Start a fresh conversation with juiced claude --new. A new conversation uses the same project workspace and files.

Persistent files, temporary compute

Claude runs in a sandbox attached to the workspace. Idle compute shuts down while the workspace data remains available for later runs. Disconnecting does not mean a process will run forever.

Local and cloud files are separate. Normal launches do not reconcile them. See how code transfers work, or read the guide to running Claude Code with your laptop closed.