pibox
docker-pibox puts pi-coding-agent inside an aicodebox container. One image, several ways in: an interactive shell, a one-shot prompt, an HTTP API with an OpenAI-compatible endpoint, an MCP server, a Telegram bot, and a cron scheduler that fires Pi on whatever schedule you want.
You talk to pibox. pibox talks to Pi. Pi talks to whatever LLM you point it at.
Quick start
Install the host wrapper, then run it from the directory you want Pi to work in:
curl -fsSL https://raw.githubusercontent.com/psyb0t/docker-pibox/main/install.sh | bash
PIBOX_PROVIDER_BASE_URL=https://api.z.ai/api/anthropic \
PIBOX_PROVIDER_API=anthropic-messages \
PIBOX_PROVIDER_API_KEY=your-z-ai-api-key \
PIBOX_PROVIDER_MODEL=your-model-id \
pibox -p "list the files in this workspace"
The wrapper forwards every PIBOX_* variable into the container, so the provider settings above reach Pi without extra flags. Install and the wrapper covers the installer, the image variants and long-running containers.
What is on this site
| Page | What it covers |
|---|---|
| Install and the wrapper | Installer options, wrapper usage, image variants, nested launches, upgrades and removal |
| Configuration | Every pibox environment variable, the PIBOX_* to AICODEBOX_* aliasing, Git identity and startup hooks |
| LLM providers | Pointing Pi at OpenAI-compatible, Anthropic Messages or Google endpoints |
| Modes | How the API, Telegram, cron and MCP modes combine, with a page for each |
| GitHub Action | Running Pi in a workflow on read-only context |
| Agent integrations | The skill and plugins for Claude Code, Codex and OpenClaw |
| Security | What the container can reach, which surfaces need tokens, and where secrets end up |
| Troubleshooting | Startup refusals, provider errors and their fixes |
| Architecture | How a request travels from the wrapper to the Pi CLI |
| Development | Building the images, running the tests, CI and releases |
The base image
pibox is a thin layer. The modes, the HTTP server, the Telegram bot, the cron scheduler and the container entrypoint come from the shared aicodebox base, which also has its own documentation site. pibox adds Pi, the adapter that turns aicodebox run requests into Pi command lines, the PIBOX_* names, the provider bootstrap and the host wrapper. This site documents the pibox names and behavior in full, so you do not need the base documentation to run pibox.