https://projectious-work.github.io/aibox/v1.x/docs/Recent content in Documentation on aiboxHugoenhttps://projectious-work.github.io/aibox/v1.x/docs/overview/Mon, 01 Jan 0001 00:00:00 +0000https://projectious-work.github.io/aibox/v1.x/docs/overview/<h1 id="overview">Overview</h1> <p>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.</p> <h2 id="the-short-version">The Short Version</h2> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">aibox init my-app --harness claude --addon python </span></span><span class="line"><span class="cl">aibox apply </span></span><span class="line"><span class="cl">aibox up </span></span></code></pre></div><p><code>aibox init</code> writes the initial project contract. <code>aibox apply</code> reconciles that contract into generated files and content. <code>aibox up</code> starts or attaches to the workspace.</p>https://projectious-work.github.io/aibox/v1.x/docs/roadmap/Mon, 01 Jan 0001 00:00:00 +0000https://projectious-work.github.io/aibox/v1.x/docs/roadmap/<h1 id="roadmap">Roadmap</h1> <p>This page outlines planned features and improvements for aibox. The internal source of truth is the processkit work item index under <code>context/</code>; this page is the public-facing summary.</p> <h2 id="current-focus">Current Focus</h2> <p>Current work is focused on making long-running AI workspaces cheaper and more predictable:</p> <ul> <li>explicit Compose project and image names for each aibox project</li> <li>optional tool bundles so idle containers do not carry unnecessary CLIs</li> <li>suspended non-focused tmux panes</li> <li>runtime resource snapshots and doctor thresholds</li> <li>init-reaper support for orphaned helper processes</li> <li>processkit MCP gateway adoption and daemon validation in real projects</li> </ul> <h2 id="planned--near-term">Planned — Near Term</h2> <h3 id="processkit-gateway-follow-through">processkit Gateway Follow-Through</h3> <p>Keep validating the gateway-mode MCP defaults in downstream projects and tune daemon guidance as more host/container runtime combinations are exercised.</p>