Repository navigation
Install the complete Codex package so its daemon starts - #268
Merged
Merged
Conversation
Recent Codex releases launch a background app-server daemon by default
and refuse to start it from a bare binary ("this CLI has no complete
local package"), forcing users to pass --no-daemon. Install the
codex-package release asset (codex-package.json, code-mode host,
bundled rg and bwrap) under ~/.local/share/codex and symlink its
entrypoint onto PATH, matching the standalone installer's layout.
The daemon copies that package (~430 MB) into $CODEX_HOME/packages on
first start and recreates it when missing, so exclude it from backups:
add a per-agent backup_exclude_dir_names field, fold it into the
backup exclude list alongside credential files, and set it to
.codex/packages for Codex.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The proxy's main thread blocked in an untimed threading.Event.wait(). When the kernel delivered SIGTERM to an accept or connection thread, CPython only flagged the signal for the main thread, which never woke to run the handler, so the proxy kept running. This was the cause of the intermittent test_proxy_shuts_down_on_sigterm failure (TEST-001); with a few connections open it reproduced in about 1 in 4 runs. Wait with a timeout so pending signal handlers always get to run, and add a regression test that sends SIGTERM with connections open. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recent Codex releases launch a background app-server daemon by default and refuse to start it from a bare binary ("this CLI has no complete local package"), forcing users to pass --no-daemon. Install the codex-package release asset (codex-package.json, code-mode host, bundled rg and bwrap) under ~/.local/share/codex and symlink its entrypoint onto PATH, matching the standalone installer's layout.
The daemon copies that package (~430 MB) into $CODEX_HOME/packages on first start and recreates it when missing, so exclude it from backups: add a per-agent backup_exclude_dir_names field, fold it into the backup exclude list alongside credential files, and set it to .codex/packages for Codex.