Deployment
matrixorigin/memoria
Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
$ npx skills add langbot-app/LangBot --skill langbot-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install langbot-app/LangBot langbot-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/langbot-app/LangBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skills/langbot-deploy .claude/skills/langbot-deploy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "langbot-deploy" agent skill from https://github.com/langbot-app/LangBot/tree/master/skills/skills/langbot-deploy into .claude/skills/langbot-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langbot-deploy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/langbot-app/LangBot/tree/master/skills/skills/langbot-deployType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add langbot-app/LangBot --skill langbot-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install langbot-app/LangBot langbot-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langbot-app/LangBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skills/langbot-deploy .agents/skills/langbot-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "langbot-deploy" agent skill from https://github.com/langbot-app/LangBot/tree/master/skills/skills/langbot-deploy into .agents/skills/langbot-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langbot-deploy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langbot-app/LangBot --skill langbot-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install langbot-app/LangBot langbot-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langbot-app/LangBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skills/langbot-deploy .cursor/skills/langbot-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "langbot-deploy" agent skill from https://github.com/langbot-app/LangBot/tree/master/skills/skills/langbot-deploy into .cursor/skills/langbot-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langbot-deploy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/langbot-app/LangBot.git --path skills/skills/langbot-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add langbot-app/LangBot --skill langbot-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install langbot-app/LangBot langbot-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langbot-app/LangBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skills/langbot-deploy .gemini/skills/langbot-deploy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "langbot-deploy" agent skill from https://github.com/langbot-app/LangBot/tree/master/skills/skills/langbot-deploy into .gemini/skills/langbot-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langbot-deploy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install langbot-app/LangBot langbot-deployInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add langbot-app/LangBot --skill langbot-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/langbot-app/LangBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skills/langbot-deploy .github/skills/langbot-deploy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "langbot-deploy" agent skill from https://github.com/langbot-app/LangBot/tree/master/skills/skills/langbot-deploy into .github/skills/langbot-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langbot-deploy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langbot-app/LangBot --skill langbot-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install langbot-app/LangBot langbot-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langbot-app/LangBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skills/langbot-deploy .opencode/skills/langbot-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "langbot-deploy" agent skill from https://github.com/langbot-app/LangBot/tree/master/skills/skills/langbot-deploy into .opencode/skills/langbot-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "langbot-deploy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
langbot-deployDeploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
This covers production use; development is left to `langbot-dev`. Docker Compose is the recommended route: clone the repository and work in its `docker` folder. The `all` or `box` profile starts three services: `langbot`, serving the API and UI on port 5300, `langbot_plugin_runtime`, with control on 5400 and debug on 5401, and `langbot_box`, the sandbox runtime on 5410. Box spawns sandbox containers through the host Docker socket, so its root path must be identical on the host and inside the container.
Control tokens are optional in the open-source setup, but an exposed Box endpoint should get the same token of at least 32 characters on both sides, generated with `openssl rand -hex 32` and never committed. The plugin runtime token must likewise be set on both sides or the connection fails. `data/config.yaml` is generated on first run; `api.global_api_key`, when non-empty, accepts requests to the HTTP API and MCP server without login, so use it only internally over HTTPS. Kubernetes uses `docker/kubernetes.yaml`.
Read from SKILL.md and the folder at commit de886ed. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
dockeropensslgitFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
langbot.appFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
LANGBOT_BOX_CONTROL_TOKENLANGBOT_PLUGIN_RUNTIME_CONTROL_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
LangBot Deployment Guide loads about 1.2k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 495 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
`sudo usermod -aG docker <user>` and restart in a new shell.Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from langbot-app/LangBot at commit de886ed, republished under its Apache-2.0 licence (© langbot-app). 495 words, ~1,217 tokens.
.claude/skills/langbot-deploy/SKILL.md (or your agent's skills folder).Covers running LangBot in production. For development see langbot-dev.
git clone https://github.com/langbot-app/LangBot
cd LangBot/docker
# Full stack (sandbox/Box + stdio MCP hosting + skill add/edit enabled)
docker compose --profile all up
# Basic (no Box runtime)
docker compose upThe all / box profile starts three services:
langbot — main app, serves API + UI on :5300.langbot_plugin_runtime — plugin runtime (control :5400, debug :5401).langbot_box — Box sandbox runtime (:5410). Uses the host Docker socket to
spawn sandbox containers, so the Box root host path and in-container path
must be identical (BOX__LOCAL__HOST_ROOT=${LANGBOT_BOX_ROOT:-${PWD}/data/box}).
OSS allows its RPC and managed-process relay to run without a token when both
sides leave LANGBOT_BOX_CONTROL_TOKEN unset. For an exposed endpoint, set
the same value of at least 32 non-whitespace characters in both the LangBot
and Box containers. Generate it once with openssl rand -hex 32; never put
it in box.runtime.endpoint or commit it to config.A Compose deployment may optionally set
LANGBOT_PLUGIN_RUNTIME_CONTROL_TOKEN on both langbot and
langbot_plugin_runtime when port 5400 needs shared-secret protection. OSS
defaults to leaving it unset on both sides. If enabled, generate one value with
openssl rand -hex 32; configuring only one side causes the control connection
to fail. Kubernetes may use the langbot-plugin-runtime-control Secret shown in
docker/kubernetes.yaml.
With Box off, the dashboard/skills list stays visible (read-only) but sandbox
tools, skill add/edit, and stdio MCP are disabled. Set box.enabled: false
(or BOX__ENABLED=false) to match.
See docker/kubernetes.yaml and the deployment guide at
https://langbot.app/docs. docker/deploy-k8s-test.sh is a test helper.
data/config.yaml on first run)Top-level sections: api, system, command, concurrency, proxy,
database, vdb, storage, plugin, monitoring, box, space.
Key settings:
| Key | Meaning |
|---|---|
api.port | HTTP API + UI port (default 5300) |
api.global_api_key | Global API key for the HTTP API + MCP server. Non-empty = accepted with no login/DB record; no lbk_ prefix required. Empty = disabled. Plaintext — trusted/internal only, serve over HTTPS. |
plugin.runtime_ws_url | Standalone plugin runtime WS URL (e.g. ws://langbot_plugin_runtime:5400/control/ws) |
box.enabled | Master switch for the Box sandbox runtime |
box.backend | local (Docker/nsjail autopick) / docker / nsjail / e2b / explicit unsafe host; env override BOX__BACKEND |
box.runtime.endpoint | External Box runtime URL (e.g. ws://127.0.0.1:5410); empty = local auto-managed |
Many keys have ENV__SUBKEY overrides (e.g. BOX__BACKEND, BOX__ENABLED).
--standalone-runtime.--standalone-box flag; the Docker box host is
langbot_box:5410.box.backend: host runs commands directly as the Box Runtime system user.
It is never auto-selected, provides no sandbox isolation, and is only for
trusted local development. A WebSocket-controlled host backend requires
LANGBOT_BOX_CONTROL_TOKEN; local stdio control is allowed.# data/config.yaml
api:
port: 5300
global_api_key: 'a-strong-secret' # empty disables itThis key authenticates both the HTTP API and the MCP server (/mcp) without a
login session. See langbot-mcp-ops for using it, and docs/API_KEY_AUTH.md.
docker group →
sudo usermod -aG docker <user> and restart in a new shell.box.backend: host as a production fallback. It cannot enforce
image, filesystem, network, PID, CPU, memory, or storage isolation.api.global_api_key to version control.© langbot-app, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/skills/langbot-deploy of langbot-app/LangBot.
Open the folder on GitHubat commit de886ed
LangBot Deployment Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| LangBot Deployment Guide this skilllangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Deploymentmatrixorigin/memoria | 607 | — | ~1.6k | Automated safety check: Notes | Apache-2.0 | |
| Debug Openshell ClusterNVIDIA/OpenShell | 15k | — | ~19k | Automated safety check: Notes | Apache-2.0 | |
| Onboarding Validationopen-edge-platform/edge-ai-suites | 140 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Agenticx DeployerDemonDamon/AgenticX | 279 | — | ~866 | Automated safety check: Pass | Apache-2.0 | |
| Vss Deploy Warehouse HelmNVIDIA-AI-Blueprints/video-search-and-summarization | 1.9k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 |
matrixorigin/memoria
Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.
NVIDIA/OpenShell
Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.
open-edge-platform/edge-ai-suites
Validate the get-started experience of Open Edge Platform (OEP) software components from the perspective of a first-time user.
DemonDamon/AgenticX
Guide for deploying AgenticX agents to production including Docker containerization, Kubernetes orchestration, Volcengine AgentKit cloud deployment, and API server setup.
NVIDIA-AI-Blueprints/video-search-and-summarization
A skill your agent uses when the user asks to deploy, upgrade, or size the VSS warehouse blueprint (2D / 3D / MV3DT) on Kubernetes via Helm — as opposed to Docker Compose, which is covered by…
CommunityToolkit/Aspire
WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.
langbot-app/LangBot
Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.
langbot-app/LangBot
Covers developing the LangBot core backend and web UI: dev setup, repo layout, API auth types, adding endpoints, migrations and keeping the MCP server in step.
langbot-app/LangBot
Guides building, migrating and testing LangBot messaging-platform adapters for the Event-Based Agents layout, with unified event and message conversion.
langbot-app/LangBot
Manages a LangBot instance over its built-in MCP server: endpoint, API-key authentication, client config and the tool set for bots, processors and more.
langbot-app/LangBot
Browses and searches the LangBot Space marketplaces for plugins, MCP servers and skills through its read-only MCP server, authenticated with a personal access token.
langbot-app/LangBot
Prepares a LangBot development and testing environment for an agent, covering service startup, proxy settings and browser access through Computer Use or Playwright MCP.
Works with
Categories
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key. This covers production use; development is left to `langbot-dev`. Docker Compose is the recommended route: clone the repository and work in its `docker` folder.
LangBot Deployment Guide fits situations like: installing LangBot with Docker Compose for self-hosting; deploying LangBot to Kubernetes; securing the Box and plugin runtime control connections; setting the global API key or editing config.yaml.
Run `npx skills add langbot-app/LangBot --skill langbot-deploy -a claude-code`. Or copy the skill folder (skills/skills/langbot-deploy in langbot-app/LangBot) into .claude/skills/langbot-deploy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add langbot-app/LangBot --skill langbot-deploy -a codex`. Or copy the skill folder (skills/skills/langbot-deploy in langbot-app/LangBot) into .agents/skills/langbot-deploy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add langbot-app/LangBot --skill langbot-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/langbot-deploy, .gemini/skills/langbot-deploy, .github/skills/langbot-deploy and .opencode/skills/langbot-deploy in your project.
Going by SKILL.md and its folder, LangBot Deployment Guide needs the command-line tools its instructions call (docker, openssl and git) and credentials named LANGBOT_BOX_CONTROL_TOKEN and LANGBOT_PLUGIN_RUNTIME_CONTROL_TOKEN. Our summary lists: Docker and Docker Compose, or a Kubernetes cluster; `openssl` for generating control tokens.
SKILL.md names 1 domain. As links in the text: langbot.app. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
LangBot Deployment Guide is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with LangBot Deployment Guide: Deployment (matrixorigin/memoria, 607 stars), Debug Openshell Cluster (NVIDIA/OpenShell, 15k stars), Onboarding Validation (open-edge-platform/edge-ai-suites, 140 stars) and Agenticx Deployer (DemonDamon/AgenticX, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
langbot-app (a GitHub organization) maintains it in langbot-app/LangBot, which has 18,033 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: langbot-app/LangBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.