CLI: make daemon_auto_start opt-in — a persistent, self-updating background daemon shouldn't be the default
Codex CLI's daemon_auto_start is set to false by default, causing issues and requiring users to use --no-daemon or manually stop the daemon.
Intelligence analysis by Qwen 2.5 (3B)
The Codex CLI's daemon_auto_start feature, which starts a persistent background daemon, is set to false by default. This has caused issues and users need to use --no-daemon or manually stop the daemon to resolve the problem.
The Codex CLI is a tool for using the Codex app. By default, it doesn't start a background daemon that keeps the app running. Users need to tell the CLI to not start the daemon, or they need to manually stop it. This can cause problems and make the app less reliable.
Analysis
Background
The Codex CLI is a command-line interface for the Codex application. It includes a feature called daemon_auto_start, which starts a persistent background daemon. This daemon is responsible for managing the Codex application's backend and ensuring it stays running even after the user closes the Codex window.
The Issue
The issue at hand is that the daemon_auto_start feature is set to false by default in the Codex CLI. This means that the daemon is not automatically started when the Codex CLI is launched. As a result, users need to use the --no-daemon flag or manually stop the daemon to ensure that the Codex application runs correctly.
Proposed Solutions
There are two proposed solutions to address this issue. The first solution is to automatically fall back to local mode when the daemon startup is blocked by elevation. This would allow the daemon to start even if the user is not elevated, which could improve security and user experience.
The second solution is to make the daemon_auto_start feature opt-in rather than the default. This would preserve the security restrictions without disrupting the normal CLI workflow.
Key points
- The Codex CLI's daemon_auto_start feature is set to false by default
- Users need to use --no-daemon or manually stop the daemon to ensure the Codex application runs correctly
- There are two proposed solutions to address this issue: automatically fall back to local mode or make the feature opt-in
By making the daemon_auto_start feature opt-in, users will have more control over whether the daemon is started, which can improve security and user experience.
If the daemon_auto_start feature is not made opt-in, users will still need to take additional steps to manage the daemon, which could lead to security concerns and user frustration.
