Overview

Mon, 01 Jan 0001 00:00:00 +0000

Overview

aibox creates reproducible, AI-ready development workspaces from one project configuration file. It is not a new container runtime and it is not a process framework. It is the glue that turns a declared project shape into a standard devcontainer, selected tool bundles, AI harness configuration, and either a processkit-backed context layer or a harness-only project skeleton.

The Short Version

aibox init my-app --harness claude --addon python
aibox apply
aibox up

aibox init writes the initial project contract. aibox apply reconciles that contract into generated files and content. aibox up starts or attaches to the workspace.

Roadmap

Mon, 01 Jan 0001 00:00:00 +0000

Roadmap

This page outlines planned features and improvements for aibox. The internal source of truth is the processkit work item index under context/; this page is the public-facing summary.

Current Focus

Current work is focused on making long-running AI workspaces cheaper and more predictable:

explicit Compose project and image names for each aibox project
optional tool bundles so idle containers do not carry unnecessary CLIs
suspended non-focused tmux panes
runtime resource snapshots and doctor thresholds
init-reaper support for orphaned helper processes
processkit MCP gateway adoption and daemon validation in real projects

Planned — Near Term

processkit Gateway Follow-Through

Keep validating the gateway-mode MCP defaults in downstream projects and tune daemon guidance as more host/container runtime combinations are exercised.

Documentation on aibox

Overview

Overview

The Short Version

Roadmap

Roadmap

Current Focus

Planned — Near Term

processkit Gateway Follow-Through