
Company News
Free Business Plan Upgrades for Open Source Maintainers
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.
Browse and interact with Codex more easily, and orchestrate multiple tasks from a dedicated workflow board.
Codex capabilities:
/, @, and $ support - Use slash commands, file mentions, and skill mentions in the composer (similar to Codex CLI).Remote mode:
~/.codex history or connect to a remote codex-deck server.UI design:
Code context and inspection:
unstaged, staged, or last-turn file diffs with patch rendering.AI-monitored task workflow:
Overview, Tasks, History, Logs, Control, and Raw JSON.Terminal:
Block mode vs Text mode
Right panes
Mobile phone page
Images support
/, @, and $ support in the message input box
Supported message block views
Expanded blocks
Collapsed blocks
Interactive mode uses codex under the hood. If codex is not on your PATH, set:
export CODEX_CLI_PATH="/absolute/path/to/codex"
npm install -g codex-deck
Run from any directory:
codex-deck
By default, Codex Deck opens http://localhost:12001 in your browser.
Uninstall:
npm uninstall -g codex-deck
git clone https://github.com/asfsdsf/codex-deck.git
cd codex-deck
npm install -g pnpm
pnpm install
pnpm build
pnpm start
Uninstall:
cd ..
rm -rf codex-deck
Download codex-deck-vX.X.X-[arch] from the GitHub Releases page, extract it, and run the codex-deck executable from that directory.
Uninstall:
rm -rf codex-deck-vX.X.X-[arch]
No matter which local installation method you use, codex-deck supports these options:
codex-deck [options]
Options:
-V, --version Show version number
-p, --port <number> Port to listen on (default: 12001)
-d, --dir <path> Codex directory path (default: ~/.codex)
--dev Enable CORS for development (frontend at localhost:12000)
--no-open Do not open browser automatically
-h, --help Show help
Quick map:
Server machine (Docker host): runs remote server and hosts the web app.Local machine (where Codex runs): starts codex-deck CLI and connects to server.Web page (browser): signs in and controls connected local machines.Security note:
local machine and web page; the server stores encrypted blobs plus routing metadata.https:// in real deployments. Use http:// only for trusted local/lab testing.Clone the repository and enter the project root on the server machine:
git clone https://github.com/asfsdsf/codex-deck.git
cd codex-deck
Build the remote server image:
docker build -t codexdeck-server -f Dockerfile.server .
Server environment variables (used in this step):
CODEXDECK_REMOTE_ADMIN_PASSWORD (required): password for https://your-server-host/admin.CODEXDECK_REMOTE_SETUP_TOKENS (optional): comma- or newline-separated setup tokens to seed on first boot. You can also create tokens later in the admin page.PUBLIC_URL (recommended): the public URL users and CLIs use to reach this server (use https://... in production).CODEXDECK_REMOTE_BROWSER_AUTH_PERSISTENCE (optional): browser login persistence. session ends on browser close, remember persists.Run the server:
docker run -p 3005:3005 \
-e CODEXDECK_REMOTE_ADMIN_PASSWORD=<admin-password> \
-e CODEXDECK_REMOTE_BROWSER_AUTH_PERSISTENCE=remember \
-e PUBLIC_URL=https://your-server-host \
-v codexdeck-data:/data \
codexdeck-server
This container serves both the remote web app and remote server. Data is stored in codexdeck-data.
In a browser, open https://your-server-host/admin, log in with CODEXDECK_REMOTE_ADMIN_PASSWORD, and create one setup token for each local CLI you want to connect. If you prefer, you can still pre-seed tokens with CODEXDECK_REMOTE_SETUP_TOKENS before first boot.
On each local machine (the machine that has Codex CLI history), start codex-deck like this:
codex-deck \
--remote-server-url https://your-server-host \
--remote-setup-token <token-a> \
--remote-username <cli-login-name> \
--remote-password <cli-login-password>
Open https://your-server-host/ in a browser and sign in with the same remote username and password used for that local machine.
You can chat with Codex at any time while working in the terminal.
To use AI Terminal:
Terminal in the left pane.New Terminal.You can also:
Chat in session to see the detailed steps in the Codex session.Continue to let the Codex session continue.Using workflows is as easy as chatting.
To create a new workflow:
Workflow in the left pane.New Workflow.Example chat requests (user side only):
Notes:
sandbox_mode = "danger-full-access"is enabled for workflow agents.
Requirements:
git clone https://github.com/asfsdsf/codex-deck.git
cd codex-deck
pnpm install
pnpm build
pnpm dev
pnpm dev starts:
http://localhost:12000http://localhost:12001pnpm build:packages
This builds portable archives in ./build/ for:
macos-arm64macos-x64linux-x64On non-Linux hosts, linux-x64 packaging requires Docker because node-pty must be installed on Linux.
Limit targets with:
./scripts/build-packages.sh --targets macos-arm64,macos-x64
MIT © zzami
FAQs
Browse and interact with Codex more easily, and orchestrate multiple tasks from a dedicated workflow board.
We found that codex-deck demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Company News
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.

Security News
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.

Security News
During a UK cyber test, a Mythos 5 agent used sockpuppets, social engineering, and prompt injection to try to get a maintainer to merge malware.