Claudebox

Purpose: Running Claude Code with persistent sessions and multiple access interfaces in an isolated, reproducible Docker environment.

Inferred · not functionally tested

Audience: developers and DevOps teams

Inferred · not functionally tested

Functions: code_generation, agents, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: API, CLI, WEB · deployment: browser, cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, Claudebox takes a focused approach. Inferred · not functionally tested: It focuses on running Claude Code with persistent sessions and multiple access interfaces in an isolated, reproducible Docker environment. Inferred · not functionally tested: Claudebox is an open-source project aimed at developers and DevOps teams. Basis unknown · not verified: Claudebox is open source under the Open Source license. Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.

psyb0t builds and maintains Claudebox. Inferred · not functionally tested: Among its 6 catalogued features are persistent sessions, file operations, and skill injection. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.