Observed behavior
During local acceptance testing on branch issue3745, a named Codex profile with ephemeralSettings.base-url pointing at a loopback Praxis endpoint continued connecting to that loopback address when invoked with only --set base-url=http://192.168.1.38:18443/backend-api/codex. The model request succeeded, so response text alone concealed that the intended override had not taken effect.
Socket evidence showed the original loopback destination. Adding the dedicated --baseurl option alongside the same --set option produced connections to the intended LAN address through Caddy and Praxis.
Reproduction shape
- Save an authenticated Codex profile with a loopback base URL.
- Run
bun scripts/start.ts --profile-load PROFILE --set base-url=http://LAN_IP:18443/backend-api/codex --model gpt-5.6-luna --prompt 'Reply with exactly PRAXIS_LAN_OK and no other text. Do not call tools.'.
- Observe actual network destination, not just successful output.
- Repeat with
--baseurl http://LAN_IP:18443/backend-api/codex added. The LAN path was then observed.
Expected / investigation needed
Determine the intended precedence between named-profile endpoint settings and CLI --set base-url. If this is a supported runtime override, it should select the explicit destination; otherwise reject or clearly document the unsupported setting rather than silently leaving the profile endpoint active.
This report records observed behavior, not an established root cause. No isolated precedence regression test has been added, and --baseurl alone was not separately characterized in this run. The test used the issue3745 workspace fix, not an assertion about every published version.
Local evidence retained under tmp/issue3745/lan-proxy/, including smoke-baseurl.log and smoke-baseurl-sockets.log; these are not committed artifacts. No credentials are included. Related to #3745 but distinct from hostname-based Codex mode selection.
Recreated by request after the original llxprt-authored issue became unavailable due to account flagging. Content preserved from the original report.
Observed behavior
During local acceptance testing on branch issue3745, a named Codex profile with ephemeralSettings.base-url pointing at a loopback Praxis endpoint continued connecting to that loopback address when invoked with only
--set base-url=http://192.168.1.38:18443/backend-api/codex. The model request succeeded, so response text alone concealed that the intended override had not taken effect.Socket evidence showed the original loopback destination. Adding the dedicated
--baseurloption alongside the same--setoption produced connections to the intended LAN address through Caddy and Praxis.Reproduction shape
bun scripts/start.ts --profile-load PROFILE --set base-url=http://LAN_IP:18443/backend-api/codex --model gpt-5.6-luna --prompt 'Reply with exactly PRAXIS_LAN_OK and no other text. Do not call tools.'.--baseurl http://LAN_IP:18443/backend-api/codexadded. The LAN path was then observed.Expected / investigation needed
Determine the intended precedence between named-profile endpoint settings and CLI
--set base-url. If this is a supported runtime override, it should select the explicit destination; otherwise reject or clearly document the unsupported setting rather than silently leaving the profile endpoint active.This report records observed behavior, not an established root cause. No isolated precedence regression test has been added, and
--baseurlalone was not separately characterized in this run. The test used the issue3745 workspace fix, not an assertion about every published version.Local evidence retained under
tmp/issue3745/lan-proxy/, includingsmoke-baseurl.logandsmoke-baseurl-sockets.log; these are not committed artifacts. No credentials are included. Related to #3745 but distinct from hostname-based Codex mode selection.Recreated by request after the original
llxprt-authored issue became unavailable due to account flagging. Content preserved from the original report.