Client or integration
OpenCodex dashboard
Area
Dashboard
Summary
Disabling Codex from the Integrations overview opens the Grok Build consequence dialog, and after confirmation the Codex card can retain its pre-toggle state until a full page reload. The status API also supplies the OpenCodex config path instead of Codex's effective $CODEX_HOME/config.toml, so the dialog cannot accurately identify the file it will change. Expected: Codex-specific consequences name the actual file, and the card refreshes its desired and observed state immediately after the toggle.
Reproduction
- Run
ocx start with Codex routing injected and open the local dashboard.
- Open Integrations and click the enabled Codex switch.
- Observe that the confirmation dialog says “Disable the Grok Build integration?” and does not identify the effective Codex config file.
- Confirm Disable.
- Observe that the Codex card can still show the pre-toggle state until the page is reloaded.
- Expected: Codex-specific consequences identify
$CODEX_HOME/config.toml; the switch reflects the desired state and the badge refreshes from observed routing.
Version
2.42.0 (ea3231a8293b)
Operating system
Linux (reproduced in the component test; the behavior is dashboard-side and expected across platforms)
Provider and model
Not provider-specific; any Codex routing configuration
Logs or error output
No runtime exception is raised; the defect is stale or misleading dashboard state.
Screenshots and supporting files
No screenshot attached; the behavior is deterministic and covered by a mounted regression test.
Redacted configuration
{}
Checks
Client or integration
OpenCodex dashboard
Area
Dashboard
Summary
Disabling Codex from the Integrations overview opens the Grok Build consequence dialog, and after confirmation the Codex card can retain its pre-toggle state until a full page reload. The status API also supplies the OpenCodex config path instead of Codex's effective
$CODEX_HOME/config.toml, so the dialog cannot accurately identify the file it will change. Expected: Codex-specific consequences name the actual file, and the card refreshes its desired and observed state immediately after the toggle.Reproduction
ocx startwith Codex routing injected and open the local dashboard.$CODEX_HOME/config.toml; the switch reflects the desired state and the badge refreshes from observed routing.Version
2.42.0 (
ea3231a8293b)Operating system
Linux (reproduced in the component test; the behavior is dashboard-side and expected across platforms)
Provider and model
Not provider-specific; any Codex routing configuration
Logs or error output
No runtime exception is raised; the defect is stale or misleading dashboard state.
Screenshots and supporting files
No screenshot attached; the behavior is deterministic and covered by a mounted regression test.
Redacted configuration
{}
Checks