- Please ensure Git, Docker, and Docker Compose are installed
all profile, which enables Box Runtime-dependent features by default, including the sandbox, stdio MCP hosting, and Skill add/edit:
langbot, langbot_plugin_runtime, and langbot_box. If you only need the basic services and do not want to enable Box Runtime, run:
langbot_box creates sandbox containers through the host Docker socket, so the Box root path must be identical on the host and inside the container:
The Box control plane’s transport depends on the deployment method. In Docker deployments it runs as the standalone
langbot_box container, and langbot connects to it over WebSocket (ws://langbot_box:5410). In manual / uvx deployments, langbot instead spawns a stdio subprocess as the Box control plane. langbot_box creates sandbox sibling containers on the host Docker through the mounted docker.sock; the LangBot image already bundles the docker client, so no extra installation is required.No sandbox backend (Docker/nsjail/E2B) is ready, first make sure the current user can access Docker:
docker info works, restart LangBot.
The container maps port 5300 for WebUI access. You can visit http://127.0.0.1:5300 to view the WebUI.It also maps ports
2280-2285 reserved for message platform adapters.
After completing the LangBot deployment, please continue reading:
