Tags give the ability to mark specific points in history as being important
-
-
-
v0.5.6
34d23fa2 · ·v0.5.6: full images inherit the current minimal image Dockerfile.full now defaults to psyb0t/codexbox:latest. The staged image workflow publishes the minimal image before building the full variant, so latest-full inherits the current minimal release rather than the obsolete v0.2.0 base.
-
v0.5.5
6d91b9fe · ·v0.5.5: codex's in-container updater works instead of failing on permissions codex was installed into npm's default global prefix (/usr), leaving the package root-owned in /usr/lib/node_modules while the container runs as the unprivileged aicode user — so `codex update` failed with EACCES. It now installs under /home/aicode/.local, with /home/aicode/.npmrc pinning the same prefix across the entrypoint's privilege drop and a /usr/local/bin/codex symlink keeping the sudo-run init scripts resolving. Also brings codexbox/pyproject.toml back in step with the tag: it was left at 0.3.5, and the Makefile derives VERSION from it.
-
v0.5.4
94014226 · ·codexbox v0.5.4 — a page per mode, and a corrected cron claim Mode docs moved to docs/modes/ so each mode's env vars live in one place instead of two. MCP mode was missing from the Table of Contents. CRON_MODE_HISTORY_DIR was documented as relocating run history; it does not — the scheduler's history root is fixed, and that variable only points the telegram bot at the cron inbox. No image behaviour changed.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
v0.3.5
bb15caac · ·v0.3.5 — fail over slow full-image apt mirrors Bound apt transfer times and fail over amd64 package installation through verified Ubuntu mirrors.