Codexbox

Name: Codexbox
Author: psyb0t

by psyb0tversion 0.7.6i★ –iRuns on your computer

Registry nameio.github.psyb0t/codexbox

Install

Overview

Description from the maker (original English)

Self-hosted MCP server: run OpenAI Codex CLI prompts and manage workspace files.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "codexbox": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/psyb0t/codexbox:v0.7.6"
      ]
    }
  }
}

Run this in your terminal

claude mcp add codexbox -- docker run -i --rm docker.io/psyb0t/codexbox:v0.7.6

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "codexbox": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/psyb0t/codexbox:v0.7.6"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "codexbox": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/psyb0t/codexbox:v0.7.6"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account psyb0t, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7223 servers in this category
Published to the registry more recently than 72% of the other 7223 servers in this category
Basic checks equal to or better than 100% of the other 7223 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Codexbox safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.6) reached the registry 15 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

docker-codexbox

OpenAI Codex CLI inside an aicodebox container. Minimal and toolchain-loaded images, five ways in: interactive shell, one-shot exec, OpenAI-compatible endpoint, MCP server, Telegram bot, and a cron scheduler that fires codex on whatever schedule you want.

You talk to codexbox. codexbox talks to codex. codex talks to OpenAI — or your ChatGPT subscription. Nobody cares about the middle.

Quick start
Using the codexbox wrapper
Image variants
Modes
API mode
Telegram mode
Cron mode
MCP mode
Configuration
Auth
Agent integrations
Development
Tests
License

Quick start

Docker installed and running is the only prerequisite.

One-liner install

The installer pulls the selected image, creates the persistent Codex and SSH directories, downloads the wrapper, and installs codexbox on your PATH.

# minimal image — default

curl -fsSL https://raw.githubusercontent.com/psyb0t/docker-codexbox/master/install.sh | bash

full image — every development tool pre-installed

export CODEXBOX_FULL=1 && curl -fsSL https://raw.githubusercontent.com/psyb0t/docker-codexbox/master/install.sh | bash

custom command name

curl -fsSL https://raw.githubusercontent.com/psyb0t/docker-codexbox/master/install.sh | bash -s -- codex

Installing with CODEXBOX_FULL=1 bakes latest-full into the wrapper, so the choice persists; you do not need to export it again. CODEXBOX_FULL must be set for bash, not merely for curl, hence the export … && form above.

Local checkout

From a checkout of this repository, build the matching image and install the local wrapper without pulling a published codexbox image:

make install       # minimal image

make install-full # full image

install only the local wrapper; do not build or pull

make install-wrapper CODEXBOX_FULL=1 make install-wrapper # full image

These targets set CODEXBOX_SRC_LOCAL=true. make install and make install-full build their image first; make install-wrapper only installs the local wrapper.sh against the selected existing image. It fails if that image is absent instead of falling back to docker pull.

The remote installer downloads wrapper.sh from its matching release tag. Automation can set CODEXBOX_INSTALL_DIR, CODEXBOX_BIN_NAME, and AICODEBOX_MANAGED_INSTALL=1 when it installs into a different command directory without prompting to replace an existing SSH key.

Using the `codexbox` wrapper

The wrapper mounts the current directory as the workspace, persists ~/.codex (so login survives container recreation), forwards auth and configured environment variables, and manages a per-directory container.

export OPENAI_API_KEY=sk-...         # or use a subscription: `codexbox login --device-auth`

codexbox # interactive TUI — continues the last session for THIS dir codexbox --no-continue # same, but starts a brand-new session instead codexbox exec "fix the failing test in ./app" # one-shot codex exec, output to your terminal echo "summarize README.md" | codexbox exec - # prompt via stdin codexbox login --device-auth # ChatGPT-subscription OAuth login (persists in ~/.codex) codexbox login status # which auth mode is active codexbox --version # passthrough to codex --version codexbox stop # stop this dir's running container(s) codexbox clear-session # drop codex's saved sessions (keeps auth + config)

The wrapper forwards "$@" straight to the image, so any codex subcommand works (codexbox mcp ..., codexbox doctor, etc.). The sandbox-bypass flag is injected inside the container — you never pass it yourself.

The bare interactive TUI defaults to continuing the most recent session for the directory you're in (same idea as claudebox's default) — codex's own resume --last cwd-scopes the lookup and starts a fresh session automatically when there's nothing to resume, so this is safe on a brand-new workspace too. Pass --no-continue to force a fresh session instead.

Install codexbox, claudebox, and pibox in the same command directory, normally /usr/local/bin, when one box needs to launch another. The wrapper finds sibling wrapper files there and mounts them read-only into the container. A sibling wrapper then runs through the host Docker daemon and mounts its own host data directory. Codexbox does not directly mount another agent's home.

Agent use and nested launches

The installed wrapper is the normal interface for people and agents. An agent should run codexbox from the requested workspace instead of assembling a new docker run command. The wrapper preserves the workspace path, Codex state, SSH state, image choice, and per-workspace container lifecycle.

codexbox exec "inspect this workspace and report the failing tests"

CODEXBOX_FULL=1 codexbox exec "run the full test suite" printf '%s\n' "summarize README.md" | codexbox exec -

When one box needs another, install codexbox, claudebox, and pibox in the same command directory. A running box can call the sibling command directly. The parent wrapper passes the host launch context and mounts only the sibling wrapper file. Do not set AICODEBOX_HOST_*, copy a wrapper, or manually mount another box's state directory.

The wrapper does not forward an SSH agent on its own. To give the box your agent, mount its socket and point SSH_AUTH_SOCK at it:

CODEXBOX_MOUNT_SSH="$SSH_AUTH_SOCK:/ssh-agent:ro" CODEXBOX_ENV_SSH_AUTH_SOCK=/ssh-agent codexbox

Every key loaded in that agent becomes usable inside the box.

Manual Docker use

Use raw Docker only for an explicitly requested container deployment. The wrapper is the normal route for interactive, one-shot, and local service use. The Modes section has the relevant deployment commands and configuration.

Image variants

psyb0t/codexbox:latest is the default minimal image: Codex, Node.js, Python, uv, Docker, Git, jq, and curl.
psyb0t/codexbox:latest-full starts from the shared aicodebox:latest-full base, then adds Codexbox's adapter, entrypoint, auth, and config.

CODEXBOX_FULL is binary: the installer defaults to minimal, 0 selects minimal, and 1 selects full. At runtime, an unset value preserves the installed image choice. Any other value fails. The installer writes the resolved image into the installed wrapper, so the choice persists without exporting the variable on every run. A runtime CODEXBOX_FULL=0 or CODEXBOX_FULL=1 temporarily forces a variant; CODEXBOX_IMAGE remains the highest-priority explicit override.

The full image adds:

Go 1.27.2 with gopls, Delve, golangci-lint, staticcheck, gofumpt, and test/code-generation helpers
Python 3.14.8 with pytest, Black, Flake8, mypy, Pyright, Poetry, Pipenv, and common HTTP/parsing libraries
JavaScript and TypeScript linting, formatting, process, framework, API-test, static-server, Lighthouse, and Storybook CLIs
GitHub CLI, Terraform, kubectl, and Helm
Build tools, CMake, ClangFormat, Valgrind, GDB, strace, and ltrace
PostgreSQL, MySQL, SQLite, and Redis clients
Vim, Nano, tmux, htop, archive tools, network diagnostics, ripgrep, fd, bat, eza, shellcheck, and shfmt

The full variant inherits the shared Aicodebox full image. Aicodebox owns the shared toolchain pins, locks, and supply-chain checks. Codexbox adds only its agent package and startup layer.

Licensing note: the minimal image is clean — just Apache-2.0 Codex on top of the aicodebox base. The full image additionally bundles HashiCorp Terraform, which is BUSL-1.1 (source-available, non-compete), not OSI-approved open source. If that matters to your use case, stick to the minimal image or review the BUSL-1.1 terms yourself before using latest-full. Full breakdown in THIRD_PARTY.md.

Wrapper environment variables

Set CODEXBOX_GIT_NAME and CODEXBOX_GIT_EMAIL on the host to configure the runtime user's global Git identity before startup hooks. Direct container deployments accept the same names. Nonempty AICODEBOX_GIT_NAME and AICODEBOX_GIT_EMAIL inside the container take precedence; through the wrapper, supply those shared values as AICODEBOX_ENV_AICODEBOX_GIT_NAME and AICODEBOX_ENV_AICODEBOX_GIT_EMAIL. Empty settings preserve existing Git config. Multiline values are rejected.

make version V=X.Y.Z synchronizes package metadata, lockfile, the Codex plugin manifest, and the installer's wrapper release ref without committing or tagging. Remote installs download the matching release wrapper unless CODEXBOX_INSTALL_REF overrides it. Updating an image does not update an installed wrapper.

Set these on the host before running codexbox:

Var	Default	What it does
`OPENAI_API_KEY`	—	API-key auth (seeded into `~/.codex/auth.json` on boot). Not needed for subscription login.
`OPENAI_BASE_URL`	—	Point codex at an OpenAI-compatible endpoint
`CODEXBOX_IMAGE`	installed image	Override the image the wrapper runs
`CODEXBOX_FULL`	installed choice (`0` initially)	`0` forces minimal; `1` forces full
`CODEXBOX_DATA_DIR`	`~/.codex`	Host dir mounted as `CODEX_HOME` (auth + config + sessions)
`CODEXBOX_SSH_DIR`	`~/.ssh/codexbox`	SSH key directory mounted into the container (for git over SSH)
`CODEXBOX_MAX_MEM`	`10g`	Per-container memory limit
`CODEXBOX_CONTAINER_NAME`	derived from `$PWD`	Override the per-workspace container name
`CODEXBOX_ENV_*`	—	Forward arbitrary env into the container (prefix stripped: `CODEXBOX_ENV_FOO=bar` → `FOO=bar`)
`CODEXBOX_MOUNT_*`	—	Mount extra host dirs (`/host:/container` syntax, or a bare path for same-path-both-sides)
`AICODEBOX_ENV_*`	—	Forward a shared environment variable into the launched container, with the prefix stripped
`AICODEBOX_MOUNT_*`	—	Mount a shared host directory into the launched container

AICODEBOX_HOST_* is the versioned nested-launch context used by sibling wrappers. It records host bind-source paths and is set automatically by a wrapper. Do not set it for an ordinary host launch.

CODEXBOX_MODE_CRON=1 + CODEXBOX_MODE_CRON_FILE=/path/cron.yaml codexbox starts the cron scheduler as a long-running background container instead.

Prefer no host install? Everything the wrapper does is plain docker run; see Manual Docker use and Modes.

Modes

Foreground modes (API / Telegram / Cron) are mutually exclusive — except CODEXBOX_TELEGRAM_MODE=1 + CODEXBOX_CRON_MODE=1, which run together (cron in-thread inside telegram). API wins if set alongside anything else.

MCP mode (CODEXBOX_MCP_MODE=1) is independent — it coexists with whatever foreground mode is running. In API mode it's mounted at /mcp/ on the API port; in other modes it runs as a sidecar uvicorn on its own port.

Each

Only the beginning is shown; read the rest in the repo

Codexbox

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

docker-codexbox

Table of Contents

Quick start

One-liner install

full image — every development tool pre-installed

custom command name

Local checkout

install only the local wrapper; do not build or pull

Using the codexbox wrapper

Agent use and nested launches

Manual Docker use

Image variants

Wrapper environment variables

Modes

Using the `codexbox` wrapper