Juiced — Claude Code, with more juice.

Juiced

3 min read Original article ↗

Cloud workspaces for Claude Code

Juiced runs Claude Code in a private cloud workspace that you drive from your terminal. Close your laptop. Claude keeps working.

curl -fsSL https://juiced.codes/install.sh | sh

juiced claude # then run in your project

macOS & LinuxYour own Claude Code login

your-project — juiced

~/your-project $ juiced claude

add a settings page with a theme toggle

Read 3 files

Write app/settings/page.tsx

/detach

Detached. Claude is still working.

~/your-project $

cloud workspacesession detached · claude running

//How it works

Four steps, no server to babysit.

Your code, Claude login and conversations live in a private cloud workspace. Your terminal is the remote control.

  1. 01

    Start Claude in the cloud

    Juiced copies your repo to a private workspace and runs Claude Code there in its own sandbox.

    $ juiced claude

  2. 02

    Close your laptop

    Detach or close the terminal. Claude keeps working without you.

    ❯ /detach

  3. 03

    Pick up where you left off

    Run it again to reconnect to the same conversation. Idle compute shuts down, but your files stay.

    $ juiced claude

  4. 04

    Bring the changes home

    When Claude is done, review its work and apply it to your branch. Nothing on your laptop changes until you do.

    $ juiced claude peek --changes-only

    # compare local and remote files

    $ juiced claude sync --from-workspace

    # import Claude's commits

    $ juiced claude fast-forward

    # apply them to your branch

//Features

The Claude Code you know, kept running.

Juiced doesn't replace Claude Code. It gives it a home that outlives your terminal.

  • A session in every tab

    Each terminal tab gets its own Claude session. Open another tab to work on something else in parallel.

  • One workspace per project

    Your current directory picks the workspace, so each project keeps its own files, Claude login, and conversations.

  • Explicit code transfer

    Git repositories start from your local HEAD. After that, nothing moves between your laptop and the cloud unless you ask.

  • Local files on request

    Ask Claude to use your local .env or test fixtures. Juiced shows exactly what it will send and waits for your approval.

  • Native Claude Code

    The stock Claude Code CLI with your own Claude account, including its permission checks, models, skills, and MCP servers.

  • GitHub access

    Give the workspace a scoped token so Claude can push branches and open pull requests.

//Documentation

Run Claude Code in the cloud

Learn how to start a workspace, leave Claude running, and bring your changes home.

docs/getting-started

Get started with Juiced

Requirements, Juiced account sign-in, Claude Code login, and your first persistent cloud workspace.

docs/workspaces-and-sessions

Workspaces, sessions, and persistence

What Juiced saves, how project isolation works, and how to detach from and reconnect to Claude Code.

docs/syncing-code

Move code between your laptop and the cloud

Send commits and local edits to Juiced, inspect remote changes, and import or fast-forward results explicitly.

docs/remote-claude-code

Keep Claude Code running with your laptop closed

Run Claude Code in a persistent cloud workspace, detach from your terminal, and reconnect to review its work.

docs/juiced-vs-vps

Juiced vs a VPS for Claude Code

Compare Juiced’s cloud workspaces and terminal sessions with managing Claude Code on your own virtual server.

docs/

All documentation

Every guide in one place, from setup to Git transfers.