Repository navigation
Settings UI 'Codex binary path' has no effect #486
Description
Activity
Investigation notes
Traced the full data flow from UI to server. The server-side code to consume a custom binary path already works —
readCodexProviderOptions()incodexAppServerManager.tsextracts it, andstartSession()spawns with the custom path. The contract schema (ProviderSessionStartInput.providerOptions) also exists.The break is in the orchestration layer:
ThreadCreateCommandandThreadTurnStartCommandinpackages/contracts/src/orchestration.tshave noproviderOptionsfield. The web app stores the setting in localStorage but has no channel to send it to the server.To fix this, the orchestration commands need a
providerOptionsfield,ProviderCommandReactorneeds to read it, andProviderHealth.tsneeds to stop hardcoding"codex".- added a commit that references this issue
on Mar 8, 2026 - added a commit that references this issue
on Mar 8, 2026 - added a commit that references this issue
on Mar 14, 2026 - added a commit that references this issue
on Jun 17, 2026 - added a commit that references this issue
on Jul 7, 2026 - added a commit that references this issue
on Aug 18, 2026
Problem
The Settings UI exposes "Codex binary path" and "Codex home path" fields, but neither value reaches the server. The user can type a custom path, but the server ignores it and always spawns the default
codexbinary.Steps to reproduce
/usr/local/bin/codex-nightly)codexbinaryExpected behavior
When
codexBinaryPathis set in Settings, the server should use that value when spawning Codex CLI commands (both for sessions and health checks).Relevant files
The server-side plumbing exists but never receives data. The gap is in the orchestration layer:
apps/web/src/appSettings.ts— storescodexBinaryPathin localStoragepackages/contracts/src/provider.ts— definesproviderOptions.codex.binaryPathschemapackages/contracts/src/orchestration.ts—ThreadCreateCommandandThreadTurnStartCommandlack aproviderOptionsfield, so the web app has no way to send the settingapps/server/src/orchestration/Layers/ProviderCommandReactor.ts— never reads or forwardsproviderOptionsapps/server/src/codexAppServerManager.ts—readCodexProviderOptions()(line ~1510) andstartSession()(line ~551) already handle custom paths, but always receiveundefinedapps/server/src/provider/Layers/ProviderHealth.ts—runCodexCommand()hardcodes"codex", ignoring any custom path