LeonardoMacedoCano

Claude Code Dock — DevOps skill for Claude Code

DevOps community

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

How to install Claude Code Dock

This entry records only its repository, not the path inside it, so there is no exact command to give. Open LeonardoMacedoCano/claude-code-dock and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Dock does

Run Claude Code on a server that's always on — and never forgets, even after a crash. Docker, Remote Control from any device.

Alternatives in DevOps

MCP Boilerplate — A remote Cloudflare MCP server boilerplate with user authentication and Stripe for paid tools 1k ★
Codeg — Aggregate and browse AI coding agent sessions (Claude Code, Codex, Gemini CLI, etc.) in one place 850 ★
MCP SSH Manager — MCP SSH Server: 37 tools for remote SSH management Claude Code & OpenAI Codex DevOps automation, backups, data 460 ★

README

Claude Code Dock

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

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) [![Docker](https://img.shields.io/badge/Docker-Ready-2496ED?logo=docker)](https://www.docker.com/) [![Unraid](https://img.shields.io/badge/Unraid-Compatible-F15A2C)](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:**

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.
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).