Avoid Ctrl+Z, which suspends the process and can leave port 1144 locked.
How to Connect Through the Codex CLI Proxypublic
Last verified 21 Sep 2026
DigitalOcean Harness Runtime combines the functionality of a lightweight microVM, built-in tools like chromium and a coding sandbox needed by agents to do work. The product offers rich lifecycle APIs that persist conversational history and working state across sessions, with pause/resume/fork semantics so that developers can control costs and adapt workflows to the nonlinear quirks of agentic work. See What You Can Build for example use cases.
For Codex sessions, you can drive a hosted session from your local Codex CLI through a local proxy started by doctl.
To connect through the Codex CLI proxy, start a local proxy and connect your local Codex CLI to it. In a terminal, start the proxy for the session:
doctl harness-runtime start-proxy --type codex --session <session-name-or-id>By default, the proxy listens on local port 1144. You can optionally bind to a different port using the --port argument.
Stop the proxy with Ctrl+C.
Next, open another terminal and point Codex at the proxy:
codex --remote ws://127.0.0.1:1144You can now send prompts to the hosted session through your local Codex interface. Shell commands and some tool calls render in the Codex TUI, and interactive approval prompts follow your agent policy.
To stop a stuck turn, disconnect or terminate the proxy.
When you start the proxy, your session does not auto pause.