Closed Codex, but it’s still running? The background helper in plain English

👋 Easy read · Oct 20, 2026 · ~6 min read

The short version

Closed your terminal and found Codex still humming in the background? The Codex CLI now starts a shared background helper on its own, so your chats and remote control can share one server.

If you would rather Codex open and close with its window, one flag skips the helper for a single run and one command switches it off for good.

Jargon jar: a CLI (command-line interface) is a program you run by typing commands in a terminal window. A background process is a program that keeps running with no window of its own.

A daemon is the old Unix nickname for that kind of always-on helper; the Codex docs call this one the “shared background server.” A server here just means a program on your own computer that other programs talk to, not a machine in a data center.

A feature flag is an on/off switch for one feature. config.toml is the settings file Codex keeps in its home folder (usually ~/.codex). An auto-updater is a helper that downloads new versions without asking each time.

Why people are talking about it

Picture closing the kitchen for the night, flicking off the lights, and finding the oven still warm in the morning. That is roughly how some Codex users felt when they spotted Codex running after every window was closed.

The change itself shipped quietly. The release notes for Sep 24, 2026 give it one line: Codex “enabled automatic background-server startup for eligible interactive sessions” (Codex CLI 0.157.0 release notes).

A day later, a user opened a request in the official Codex GitHub tracker asking for that auto-start to be opt-in instead of on by default (openai/codex issue #48195).

On Oct 12, 2026 the request hit the front page of Hacker News, where the thread reached 609 points and 294 comments (Hacker News discussion, numbers as of our research). The issue was still open when we wrote this.

You do not need to pick a side in the comment war. You just need to know what is running on your computer and where the off switch is.

What the background helper is

Before this change, a Codex chat in your terminal worked like a food truck: it opened when you started it and packed up when you closed the window.

Now an interactive Codex session can start a separate helper program that stays put, more like a kitchen that keeps the stove lit so the next order cooks faster. Your terminal window becomes a window into that kitchen rather than the whole kitchen.

The official CLI reference describes the opposite mode, the --no-daemon flag, as running “the interactive CLI without the shared background server” (Codex CLI reference).

Because the helper is shared, one running copy can serve more than one Codex window. That is the whole point of having it.

Why Codex added it

A shared helper lets several features lean on the same running kitchen. The Codex CLI reference lists a few:

codex agents opens a command center to “browse chats and switch between agents on a shared server.” It does not work with --no-daemon.
codex remote-control starts remote control “through the managed background server when eligible,” with a fallback that runs in the foreground instead.
--remote connects to a remote server, and it also cannot be combined with --no-daemon.

So the helper is less a mystery guest and more a sous-chef hired so you can hop between chats and devices. The complaint in the issue is not that the sous-chef exists. It is that nobody asked before hiring one.

What users report it doing

Everything in this section comes from users writing in the Codex GitHub tracker, not from OpenAI’s docs. Treat it as field notes, not a spec sheet.

The person who opened issue #48195 reports that on their machine the helper:

keeps running after every Codex window is closed, until it is stopped or the computer restarts;
copies the Codex package, which they measured at about 374 MB, into a folder under ~/.codex/packages/ and runs from that copy;
starts a separate updater that checks for new versions five minutes after launch and then every hour, and restarts the helper when it updates.

Other open reports in the same tracker describe old releases piling up in that folder until it reached 2.8 GB (openai/codex issue #52067), and an auto-update cutting off work that was still in progress (openai/codex issue #40969).

These are individual reports, but they show how a beginner can end up with an extra program, extra disk use and surprise restarts they never chose.

How to switch it off

You have two choices: skip the helper for one session, or turn auto-start off for good. These commands come from the Codex CLI reference and the workaround posted in issue #48195.

# See every feature flag and whether it is on
codex features list

# Start one session without the background helper
codex --no-daemon

# Turn auto-start off for good (saved in config.toml)
codex features disable daemon_auto_start

# Stop a helper that is already running
codex app-server daemon stop

A few notes so the off switch actually sticks:

Check the name first. The CLI reference says codex features list shows known flags and their state, and codex features disable saves your choice in config.toml. The flag name daemon_auto_start comes from the issue thread, so confirm it appears in your list.
Stop the one already running. A closed Windows report says that turning auto-start off did not stop Codex from attaching to a helper that was already running (openai/codex issue #48778). Stop it once after changing the setting.
Watch for a leftover updater. The original reporter says daemon stop left the updater running and they had to end it by hand (issue #48195). A restart clears it too, per the same report.

If you use codex agents or remote control, leave the helper on. Those features are built around it.

What has changed since

OpenAI has kept adjusting the helper in later releases:

On Oct 8, 2026, Codex stopped auto-starting the helper for WSL setups whose home folder lives on a Windows drive (Codex CLI 0.162.0 release notes).
On Oct 15, 2026, a new /daemon command let you restart the helper from inside a chat. Codex “warns about work the restart could interrupt, then reconnects automatically” (Codex CLI 0.163.0 release notes).

Neither release note says the default changed, so plan on auto-start being on until you switch it off.

Common mix-ups

“Is this the Codex app?” No. This is about the Codex command-line tool you run in a terminal. The issue suggests a shared helper makes more sense for the desktop app and remote control (issue #48195).
“Will turning it off break Codex?” Plain chats in the terminal still work with --no-daemon. Only the shared-server features listed above need the helper (Codex CLI reference).
“Does closing the window stop it?” Per the user reports, no. Stop it with the command above or restart your computer.

Chef’s pick: run codex features list once so you know what is switched on. If you only chat with Codex in one terminal, turn auto-start off and stop the running helper, and the kitchen closes when you do.

Sources

Show all 9 sourcesShow fewer