claudelxc

Turn a Proxmox host into a fully provisioned, self-updating Claude Code box — with one command.

claudelxc builds an Ubuntu 26.04 LXC running Claude Code in permission auto mode, fronted by the CloudCLI UI web app, on top of a full dev toolchain — and then keeps the whole thing up to date on its own.

Quick start

Run on your Proxmox host, as root:

bash <(curl -fsSL https://raw.githubusercontent.com/serversathome/claudelxc/stable/install.sh)

Answer a few prompts (container ID, CPU/RAM/disk, storage, bridge, network). A few minutes later you get a link to the web UI on port 3001. Open it, create a login, and start talking to Claude.

What you get

• Claude Code (native install) in auto mode — actions are auto-approved through a safety classifier, with a deny floor that always blocks reading secrets (.env, *.pem, keys) and catastrophic commands.
• CloudCLI UI on :3001 — chat, file explorer/editor, git panel, and a built-in terminal, driving the same Claude Code under the hood.
• Dev toolchain — Node.js (LTS), Python 3, Go, Rust, Docker + Compose, plus git, ripgrep, fzf, fd, database clients, and build essentials.
• Curated plugins & skills — code-review, security-guidance, claude-security, commit-commands, frontend-design, modern-web-guidance, context7, elements-of-style, superpowers, language-server (LSP) plugins for TypeScript/Python/Go/Rust/C++ (with their servers installed), and a Playwright-based webapp-testing skill.
• Agent teams enabled out of the box; thinking and effort are left at the model's adaptive defaults (/effort to change per session). Remote Control (/rc) works once you log in.

It keeps itself updated

Every box updates itself nightly — no action needed. It pulls the latest claudelxc, re-applies the setup, then refreshes the OS, Claude Code, the web UI, and any container images, and finishes with a health check. Your logins and everything under /project are preserved across updates.

Force it any time from inside the box:

claudelxc-update      # full update pass right now
claudelxc-doctor      # just the health check

Update log: /var/log/claudelxc-update.log. To turn nightly updates off, delete /etc/cron.d/claudelxc.

Already have an older box?

If you deployed a Claude Code box with an earlier version of this script (or the old agentic.sh), it has Claude Code but won't self-update — improvements never reach it. Adopt it into the self-updating fleet without rebuilding. Run this inside that container, as root:

bash <(curl -fsSL https://raw.githubusercontent.com/serversathome/claudelxc/stable/adopt.sh)

It brings the box fully up to spec (installs the web UI, the nightly updater, and anything missing), then it self-updates every night like a fresh deploy. What's preserved vs. changed:

• Kept: your Claude login, everything under /project, your CloudCLI login, Docker/Rust, and the box's current OS (no release-upgrade — it just tracks the latest config).
• Merged: managed keys in /root/.claude/settings.json (auto mode, the deny floor, required env, the curated plugins) are enforced, while anything you added — your own enabled plugins, custom permissions, statusLine, hooks — is preserved. Managed entries that a newer release retires (see templates/settings.retired.json) are removed. A pre-adopt copy is still saved as settings.json.pre-claudelxc.

Re-running is safe. Afterward, claudelxc-doctor should come back all-green.

Managing the box

• Web UI service: systemctl status cloudcli (journalctl -u cloudcli for logs)
• Start Claude in a shell: claude (drops you in /project)
• Config: /root/.claude/settings.json (permissions + env)
• Console / SSH: pct enter <id> from the host, or ssh root@<box-ip>

Deploy details (IP, update commands) are also written into the container's Notes panel in the Proxmox UI.

Good to know

• The box clones this public repo anonymously — no credentials are stored on it.
• It self-updates from the stable branch, which tracks the latest known-good release.
• Runs as root inside a privileged LXC (--unprivileged 0) with nesting, keyctl, and an unconfined AppArmor profile — what Docker-in-LXC needs. Treat the box as trusted-network equipment, not as an isolation boundary.