圣Claude AI工作站

Stop configuring. Start building.

One command. Full AI development workstation. Claude Code, web UI, headless browser, 7 AI CLIs, 50+ dev tools — containerized and ready.

You were going to spend 2 hours setting this up manually. Or you could just docker compose up.

Works with your existing Claude Code subscription. Max/Pro plan, API key — whatever you have, it just works.

---

:whale: Docker Compose — Quick

The "I just want it running" template. Copy this entire block into a docker-compose.yaml file:

```yaml

Just run: docker compose up -d

:whale2: Docker Compose — Full

Same image, every knob exposed. Copy this entire block into a docker-compose.yaml file:

```yaml

:building_construction: Architecture

What survives `docker compose down && docker compose up`:

• Your Anthropic authentication and API keys
• Claude Code settings, memory (CLAUDE.md), and OAuth session (no re-login)
• All your code in ./workspace
• Git configuration
• Codex, Gemini, and Cursor CLI auth (since v1.1.7)

Re-triggering first-boot setup:

```bash

:hammer_and_wrench: Building Locally

Want to build the image yourself instead of pulling from Docker Hub? Go for it:

```bash git clone https://github.com/CoderLuii/HolyClaude.git cd holyclaude

Build full image

docker build -t holyclaude .

Build slim image

docker build --build-arg VARIANT=slim -t holyclaude:slim .

Build for ARM (Apple Silicon, Raspberry Pi, AWS Graviton)

docker buildx build --platform linux/arm64 -t holyclaude . ```

This source release vendors the patched CloudCLI package under vendor/artifacts/, so docker build installs that bundled tarball instead of downloading @siteboon/claude-code-ui from npm.

Then use image: holyclaude instead of image: coderluii/holyclaude:latest in your compose file.

<p align="right"> <a href="#top">↑ back to top</a> </p>

---

:zap: Quick Start

1. Create a folder for HolyClaude:

mkdir holyclaude && cd holyclaude

2. Create a docker-compose.yaml file. Copy one of the templates below: - Quick template — minimal, zero config, just works - Full template — all options, fully documented

3. Pull and start:

docker compose up -d

4. Open the web UI:

http://localhost:3001

5. Create a CloudCLI account (takes 10 seconds), sign in with your Anthropic account, and you're live.

No .env files. No pre-configuration. No reading 40 pages of docs before you can start. It just runs.

Want to reach it from outside your network? Don't port-forward it. See Remote Access & Exposure — use Tailscale or Cloudflare Tunnel instead.

<p align="right"> <a href="#top">↑ back to top</a> </p>

---

HolyClaude — Quick Start

HolyClaude — Full Configuration

All options documented inline.

Detailed docs: https://github.com/CoderLuii/HolyClaude/blob/master/docs/configuration.md

:wrench: Environment Variables

The complete reference. Every variable, what it defaults to, what it does.

<p align="right"> <a href="#top">↑ back to top</a> </p>

---

Persisting the CloudCLI account (optional, local storage only)

By default, the CloudCLI account database (~/.cloudcli) is container-local and gets wiped on rebuild. Re-creating the account takes 10 seconds, so most people leave it as-is.

If you want it to survive rebuilds, add a named Docker volume to your compose file:

services:
  holyclaude:
    volumes:
      - ./data/claude:/home/claude/.claude
      - ./workspace:/workspace
      - cloudcli-data:/home/claude/.cloudcli   # add this line

volumes:
  cloudcli-data:                                # and this block

Do NOT bind-mount ./data/cloudcli on a network share (NAS, SMB/CIFS, NFS). CloudCLI stores its account in SQLite, and SQLite's file locking breaks on network mounts. You'll hit database is locked errors constantly. Named volumes live on the Docker engine's local filesystem, which is why this works — bind mounts pointing at a NAS will not.

A bind mount to a local SSD path is fine too, just keep it off any network share.

<p align="right"> <a href="#top">↑ back to top</a> </p>

---

:robot: AI CLI Providers

Seven AI CLIs. One container. No other Docker image gives you this.

Claude Code is the primary CLI. The others are there because sometimes you want a second opinion, or a specific model's strengths, or you're comparing outputs. Having all of them one Tab away is the whole point.

<p align="right"> <a href="#top">↑ back to top</a> </p>

---

:package: Image Variants

Two flavors. Same quality. Pick your weight class.

```bash

Full image only (additional packages)

The full image includes everything above, plus:

<details> <summary><strong>Additional npm packages — deployment, ORMs, performance</strong></summary>

</details>

<details> <summary><strong>Additional Python packages — PDFs, data viz, web frameworks</strong></summary>

</details>

<details> <summary><strong>Additional system packages — media, documents</strong></summary>

</details>

Slim users: Missing a package? Ask Claude. It installs npm/pip packages in seconds. System packages (pandoc, ffmpeg) take 1-2 minutes. You get the same capabilities — the full image just has zero wait time.

<p align="right"> <a href="#top">↑ back to top</a> </p>

---

:bar_chart: Alternatives

How does HolyClaude compare to other approaches?

HolyClaude isn't competing with coding agents — it's the infrastructure layer that makes them all work better. It's the container you run them inside.

<p align="right"> <a href="#top">↑ back to top</a> </p>

---

:construction: Troubleshooting

<details> <summary><strong>CloudCLI shows wrong default directory</strong></summary>

CloudCLI opens to /home/claude instead of /workspace.

Cause: WORKSPACES_ROOT not reaching the CloudCLI process. Docker-compose env vars don't pass through s6-overlay's s6-setuidgid — it runs with a clean environment by design (security feature, not a bug).

Fix: Already handled in HolyClaude. The s6 run script sets WORKSPACES_ROOT=/workspace directly in the process environment. </details>

<details> <summary><strong>SQLite "database is locked"</strong></summary>

Cause: SQLite databases on SMB/CIFS network mounts. CIFS doesn't support the file-level locking SQLite requires.

Fix: Don't store SQLite databases on network shares. HolyClaude keeps .cloudcli in container-local storage for exactly this reason. If you have your own SQLite databases in /workspace on a NAS, move them to a local path. </details>

<details> <summary><strong>Chromium crashes / blank pages / tab failures</strong></summary>

Cause: Insufficient shared memory. Docker defaults to 64MB.

Fix: Ensure shm_size: 2g in your compose file. For heavy browser use (many tabs, complex pages), increase to 4g. </details>

<details> <summary><strong>File watchers not detecting changes (hot reload broken)</strong></summary>

Cause: SMB/CIFS network mounts don't support inotify.

Fix: Enable polling in your compose environment:

- CHOKIDAR_USEPOLLING=1
- WATCHFILES_FORCE_POLLING=true

<details> <summary><strong>Permission denied errors</strong></summary>

Cause: Container UID/GID doesn't match host file ownership.

Fix: ```bash