Skip to main content

Codex Partner

Codex Partner is a self-hosted control panel for long-running Codex work. It keeps one native Codex thread alive and lets terminals, browsers, and multiple devices interact with the same task.

Codex Partner task workspace

Why

  • Long tasks stop too early. Persistent Goals can resume after a failed turn, disconnect, or service restart until the objective is complete.
  • Multiple clients split the session. Every connected browser is a view of the same server-owned Codex thread, not a competing resume process.
  • Messages collide with active work. New messages wait in a durable queue and enter the conversation only when their turn actually starts.

Highlights

  • Live task state, tool activity, context usage, and paginated history
  • Goal Resume with pause, retry, and restart recovery
  • Ordered message queue with manual dispatch
  • Workspace browser, editor, uploads, downloads, and image previews
  • Browser terminal that preserves its session when hidden
  • Model and API provider management with health checks and failover
  • Codex memories, Skills, archive, recycle bin, and SSH workspace support
  • Default YOLO mode for newly created sessions
  • Explicit delivery controls: Enter queues behind a running turn, Alt+Enter inserts into the current dashboard turn, and terminal takeover always asks before stopping terminal work
  • External thread-owner indicator: when a Codex process this dashboard did not start still holds a thread's writer lock, the session is marked, retries stop instead of looping, and one click can send it SIGTERM so the dashboard takes the thread over

Platform support

Codex Partner runs natively on Linux, macOS, and Windows with Python 3.10 or newer.

Platform Codex sessions Workspace tools Browser terminal Background service
Linux Yes Yes POSIX PTY systemd user service
macOS Yes Yes zsh/bash PTY Run directly or use launchd
Windows 10/11 Yes Yes PowerShell through ConPTY Run directly or use Task Scheduler

Windows terminal support uses pywinpty, which is installed automatically. Key-based remote SSH works when the OpenSSH client is installed. Browser password prompts for remote SSH are not available on native Windows; configure an SSH key first.

Install

Requires Python 3.10+ and an authenticated Codex CLI.

PyPI

pip install codex-partner
codex-partner

From source

git clone https://github.com/froststeam/Codex-Partner.git
cd Codex-Partner
pip install .
cp .env.example .env
codex-partner

Open http://127.0.0.1:8787.

Linux keeps SSH browser authentication enabled by default. macOS and Windows default to unauthenticated loopback access because desktop installations normally do not run an SSH server. For access from other devices, set CODEX_DASHBOARD_HOST=0.0.0.0, configure CODEX_DASHBOARD_AUTH=ssh, and put HTTPS in front of the service. When authentication is handled by a reverse proxy, explicitly set CODEX_DASHBOARD_AUTH=none; Codex Partner rejects a non-loopback bind with an implicit unauthenticated default.

The sign-in dialog has an optional SSH port field for daemons that do not listen on port 22. It defaults to 22, remembers the last port you used, and overrides CODEX_DASHBOARD_AUTH_SSH_PORT (default 22) for that one sign-in.

macOS

Install Python and Node.js with Homebrew if they are not already available, then install and authenticate Codex:

brew install python node
npm install --global @openai/codex
codex login
python3 -m pip install --user --upgrade codex-partner
python3 -m codex_partner

Open http://127.0.0.1:8787. Application data defaults to ~/Library/Application Support/CodexPartner; native Codex state remains in ~/.codex.

Windows

Run these commands in PowerShell. Install Python and Node.js first if they are not already available:

winget install --id Python.Python.3.12 -e
winget install --id OpenJS.NodeJS.LTS -e
npm install --global @openai/codex
codex login
py -m pip install --user --upgrade codex-partner
py -m codex_partner

Open http://127.0.0.1:8787. Application data defaults to %LOCALAPPDATA%\CodexPartner; native Codex state remains in %USERPROFILE%\.codex. If codex is not found after installing Node.js, close and reopen PowerShell so its PATH is refreshed.

For local desktop use, keep the default 127.0.0.1 bind address. To set options for one PowerShell session:

$env:CODEX_DASHBOARD_PORT = "8787"
$env:CODEX_DASHBOARD_AUTH = "none"
py -m codex_partner

Docker

docker build -t codex-partner:0.0.17 .
docker run -d --name codex-partner \
  -p 8787:8787 \
  --cap-add=SYS_ADMIN \
  --security-opt seccomp=unconfined \
  --add-host=host.docker.internal:host-gateway \
  -e CODEX_DASHBOARD_AUTH=ssh \
  -e CODEX_DASHBOARD_AUTH_SSH_HOST=host.docker.internal \
  -v codex-partner-data:/var/lib/codex-partner \
  -v codex-home:/home/codex/.codex \
  -v codex-workspace:/workspace \
  codex-partner:0.0.17
docker exec -it codex-partner codex login

Linux systemd

After completing the source installation above, stop the foreground process and install the user service:

mkdir -p ~/.config/systemd/user
cp codex-partner.user.service.example ~/.config/systemd/user/codex-partner.service
systemctl --user daemon-reload
systemctl --user enable --now codex-partner.service
systemctl --user status codex-partner.service

This service uses the current user's existing Codex login, configuration, memories, and Skills. The example assumes the repository is at ~/Codex-Partner; edit the two paths in the unit if it is elsewhere.

On Linux with a systemd user session, local Codex turns run in separate transient user services. Restarting codex-partner.service disconnects and reconnects the control panel without stopping an active Codex turn. The detached Codex service is removed after its turn completes. This restart isolation currently applies to local Linux sessions; macOS, Windows, Docker, and remote SSH sessions retain their platform transport behavior.

View logs with journalctl --user -u codex-partner.service -f. To keep it running after logout, run sudo loginctl enable-linger "$USER" once.

Use

Create a session, choose a workspace and model, then send a message. Messages sent during an active turn queue automatically. Set a Goal to let Codex Partner keep resuming unfinished work. Reopen the same session from any connected device to continue the same thread.

Type /help in the message input for commands. Press ` to toggle the terminal, Shift+N / Shift+P to switch sessions, and Ctrl/Cmd+K to focus or unfocus the composer.

Metadata

Release files for codex-partner 0.0.17

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for codex-partner 0.0.17
File Size Uploaded Provenance
codex_partner-0.0.17.tar.gz 3.3 MB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for codex-partner 0.0.17
File Interpreter ABI Platform
codex_partner-0.0.17-py3-none-any.whl Python 3 none any Details

Total release size: 6.7 MB

Release files / codex_partner-0.0.17.tar.gz

Download URL codex_partner-0.0.17.tar.gz
Size 3.3 MB
Tags Source
SHA-256 checksum
How to use checksums
994cfe80649bd34c2dfac70349969fbc064f75dda2acf845e68369c397a9e003
BLAKE2b-256 checksum
How to use checksums
33e083565e37ff511d2330171fb6f299e9492508dcf270a145fb3dfaa70ae780
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Release files / codex_partner-0.0.17-py3-none-any.whl

Download URL codex_partner-0.0.17-py3-none-any.whl
Size 3.5 MB
Tags Python 3
SHA-256 checksum
How to use checksums
a4084636e30ef8cbf352120a3bb81a1d919cf112a58e64033e2a9b9cd8f857a8
BLAKE2b-256 checksum
How to use checksums
b33c23e20e56b704e0a69c07fc0a43df9fd3be253335cea6e94a34a510bdb996
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

Security for codex-partner 0.0.17

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for codex_partner-0.0.17.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page