Claude Code Dock

Claude Code Dock

**Run Claude Code on a server that's always on — and never forgets, even after a crash.**

[](LICENSE) [](https://www.docker.com/) [](https://unraid.net/)

**Jump to:** [What It Solves](#what-it-solves) · [Is This For You?](#is-this-for-you) · [Example](#example) · [Quick Start](#quick-start) · [Documentation](#documentation)

---

What It Solves

[Claude Code](https://www.npmjs.com/package/@anthropic-ai/claude-code) normally runs in a terminal on your own machine, or via Remote Control from a terminal session that has to stay open. Close the laptop, lose the network, or have the process crash — and the session, along with its context, is gone.

**claude-code-dock fixes both halves of that problem:**

1. Always on. Claude runs inside a Docker container on a server that never sleeps or shuts down — homelab box, NAS, VPS. Not tied to your laptop being open or your terminal staying connected.
2. Survives failure, not just disconnects. Login, conversation history, and settings live on the host (bind-mounted, not inside the container's own writable layer), and the container restarts automatically if it crashes, the host reboots, or you update it. Reconnect and Claude picks up exactly where it left off — no re-authenticating, no starting the conversation over.

If a session freezes (Claude stuck waiting for a permission prompt), VPN into your server, attach to the tmux session, unblock it, detach. No physical access needed.

**Why trust it on your server:** no ports exposed, no authentication layer of its own (Claude Code's own login handles that), the long-running process never runs as root. Details in [Security](docs/security.md).

---

Is This For Yo