Tags give the ability to mark specific points in history as being important
-
-
v2.3.8
f3defd75 · ·claudebox v2.3.8 — MCP mode is documented MCP was reachable but had no docs/modes/ page; the README described it only as an endpoint inside API mode, never as the standalone mode that coexists with the others. Documents its port, its separate token (no fallback to the API token, and empty means no auth), and the five tools. No image behaviour changed.
-
-
-
-
-
-
-
-
v2.3.0
055e6a48 · ·v2.3.0 — install Claude Code at first run instead of baking it into the image; add THIRD_PARTY.md
-
-
-
-
-
v2.1.2
e105b62c · ·claudebox v2.1.2 — bump baked-in toolchains and harden the image supply chain Toolchains: claude-code 2.1.197 -> 2.1.220, Go 1.26.1 -> 1.26.5, kubectl apt channel v1.31 -> v1.36, pyenv Python 3.12.11 -> 3.12.13. Supply chain: pin the aicodebox base image by @sha256 digest, and SHA256-verify the Go tarball (per-arch) before extraction instead of piping curl into tar.
-
v2.1.1
52d1cdb8 · ·claudebox v2.1.1 — fix `claudebox --update` permission-denied on the global claude install Run the marker-triggered `claude update` as `sudo claude update` so it can write the root-owned npm global install (/usr/lib/node_modules) from the non-root aicode runtime user.
-
v2.1.0
8a6eefa7 · ·claudebox v2.1.0 — make container memory limit configurable wrapper.sh adds CLAUDEBOX_MAX_MEM environment variable (with legacy CLAUDE_MAX_MEM fallback) to override the per-container memory limit at launch time. Defaults to 10g.
-
v2.0.13
5e797d4e · ·claudebox v2.0.13 — bump the aicodebox base image to v0.14.0 Dockerfile's BASE_IMAGE default moves from psyb0t/aicodebox:v0.13.0 to psyb0t/aicodebox:v0.14.0.
-
v2.0.12
2a33c4a0 · ·claudebox v2.0.12 — pin the aicodebox base image to a version tag Dockerfile's BASE_IMAGE default moved from psyb0t/aicodebox:latest (a floating tag) to psyb0t/aicodebox:v0.13.0 (a pinned version), so builds are reproducible until the pin is deliberately bumped.
-
v2.0.11
957812fc · ·claudebox v2.0.11 — stop leaking a root-owned GOPATH into the full image's runtime Dockerfile.full set GOPATH=/root/go via ENV during the Go dev-tools install step (run as root), which leaked into the runtime container for every user. The non-root aicode user inherited a GOPATH it doesn't own, pointing at a dir already rm -rf'd by the same build step, so go install/get/mod failed with permission denied. Now scoped inline to just the one RUN step; runtime falls back to Go's own per-user default ($HOME/go).