Tags give the ability to mark specific points in history as being important
-
v0.18.4
2345996c · ·Rebuilds on Aicodebox v0.16.0. - Rebuilds both variants on digest-pinned Aicodebox `v0.16.0`. - The new base adds the opt-in `stream_options.include_aicodebox_events` option for streaming chat completions. It sends native Pi records as named `aicodebox.native` SSE events. Standard OpenAI chunks are unchanged.
-
v0.18.3
36bb1881 · ·Documents wrapper and agent use. - Documents the wrapper-first path for interactive, one-shot, full-image, and local API or MCP runs. - Documents nested sibling-box launches and the wrapper-managed host context. - Makes the bundled agent skill and MCP plugin setup match the actual wrapper behavior.
-
v0.18.2
3355e465 · ·v0.18.2 - Makes the installed `pibox` wrapper the primary documented entry point for interactive, one-shot, provider-configured, and detached service runs. - Keeps raw Docker invocation documented as a deliberate alternative. - Updates pi-coding-agent to `0.85.1`. - Rebuilds both variants on digest-pinned Aicodebox `v0.15.1`. - Disables npm dependency lifecycle scripts in both image builds.
-
v0.18.1
dcb6137a · ·v0.18.1 - Corrects host-wrapper setup and shared-settings documentation. - Pins the remote installer to the matching `v0.18.1` wrapper.
-
v0.18.0
4024bebc · ·v0.18.0 - Add the `pibox` host wrapper and installer with persistent Pi, pibox state, and SSH directories. - Add managed installation into a caller-selected wrapper directory without replacing existing SSH keys. - Add nested box launches with host-path propagation, sibling wrapper mounts, and shared `AICODEBOX_ENV_*` and `AICODEBOX_MOUNT_*` settings. - Download the installed wrapper from the matching immutable release tag.
-
v0.17.0
a11036ca · ·- Adds `psyb0t/pibox:latest-full`, built from digest-pinned `aicodebox:v0.15.0-full` with Pi and pibox on top. - Rebuilds the minimal image on digest-pinned `psyb0t/aicodebox:v0.15.0`. - Excludes local virtual environments and agent scratch from Docker build contexts.
-
v0.16.2
3ea68c2a · ·- Fixes every model in `PIBOX_AVAILABLE_MODELS` other than `PIBOX_PROVIDER_MODEL` failing on each request. Only the configured provider model was written to Pi's provider model list, so any other advertised model fell back to Pi's default API shape, disagreed with the provider base URL, and failed with `Stream ended without finish_reason`. - Registers every model in `PIBOX_AVAILABLE_MODELS` under the configured `PIBOX_PROVIDER_API`, for both the generic provider and the `ANTHROPIC_BASE_URL` compatibility path. - Warns during startup when `PIBOX_PROVIDER_BASE_URL` and `PIBOX_PROVIDER_API` describe different protocols, instead of surfacing the mismatch as a truncated stream at request time. - Adds live E2E coverage for a second advertised model over both Anthropic Messages and OpenAI Chat Completions, and for a LiteLLM gateway serving models from several upstreams. - Asserts the full OpenAI Chat Completions response contract in the generic-provider tests: response object, echoed model, message role, finish reason, content, and token usage.
-
v0.16.1
9f2d064c · ·v0.16.1 - Adds live E2E coverage for Z.AI Coding Plan through both Anthropic Messages and OpenAI Chat Completions generic-provider configuration. - Documents the Z.AI Coding Plan OpenAI endpoint and model-list endpoints.
-
-
v0.15.13
157320ec · ·- Updates pi-coding-agent to 0.84.4. - Rebuilds on aicodebox v0.14.8, which provides Node.js 24.20.0 and Python 3.14.7.
-
v0.15.12
a83c901d · ·- Bumped the digest-pinned base image to `psyb0t/aicodebox:v0.14.6`, which adds independent event retention through `eventMode` and the stable full-event envelope to `POST /run`. - Documented how `eventMode: "full"` preserves native Pi thinking, tool lifecycle, retry, compaction, and provider records. - Added adapter regression tests proving full-event mode keeps Pi's JSON stream and preserves native thinking and tool records unchanged. - Added `make pkg-lock` and refreshed the lockfile against aicodebox v0.14.6.
-
-
-
v0.15.9
0ab19bc7 · ·pibox v0.15.9 — 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, and the Table of Contents links every page including MCP mode. 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. The intro promised five ways in and listed six. No code changed.
-
-
-
-
-
-