Repository navigation
Codex Bridge 1.13.25
- Pairs with Integration and panel 1.13.25, which require Home Assistant 2026.9.0 or later. Update Home Assistant Core before installing the Integration.
- Retries Integration setup automatically when the App answers but a later setup step fails, for example while the App is still finishing startup. Previously the entry stopped in a setup error until it was reloaded. As before, setup also retries while the App is unreachable.
- Starts Home Assistant's reauthentication flow when the App or an external Bridge rejects the Integration's token. Open the repair named after the entry, such as "Authentication expired for Codex Bridge", or select Reconfigure on the highlighted card in Settings > Devices & services: an App connection reconnects after the App restarts, and an external Bridge accepts a new token. An App connection notices a rejected token while it runs; an external Bridge's token is checked only when Home Assistant starts or reloads Codex Bridge.
- Keeps live updates retrying after App errors that used to stop them until the Integration was reloaded: protocol errors, App errors marked as not retryable and unexpected failures. These retries start after 1 minute and back off to at most 10 minutes, and the log records one info-level message when updates stop and one when they recover. An unreachable App is still retried at most 30 seconds apart, as before.
- Adds redacted diagnostics to the Codex Bridge integration entry.
- Raises a Repairs issue for each saved account that needs a fresh sign-in. It closes on the next reading that reports the account as signed in, or when the account is removed.
- Adds Reconfigure for an external Bridge to change its address or token. On an App connection it explains that restarting the App reconnects it.
- Shows each saved account as its own device under the Codex Bridge connection device, which is shown under the App's device.
- Registers task actions when the Integration loads and checks their data before contacting the App. Problems the caller can correct, such as an unknown or busy project or chat, a reused task ID, an unavailable model or data the App rejects, remain validation errors. App outages, a rejected connection token, a required Codex sign-in, a full Codex queue or task history and unexpected Bridge failures are now action errors. All have translated messages, and while the connection is not loaded the actions fail with a validation error that says so.
- Compatibility changes to check in automations, scripts and dashboards:
- Entity IDs and unique IDs are unchanged, but saved-account sensors take their friendly names from the account device. For example, "Codex Bridge Work weekly usage" becomes "Work Weekly usage".
- Saved-account sensors move to their account's device, which starts without an area. A sensor without an area of its own no longer takes the connection device's area, so check area-based cards and templates such as
area_entities(),device_entities()anddevice_id(), or assign an area to the account device. When the App's complete account list no longer includes an account, its device is removed with its sensors. - The Assist agent's name now follows the connection device. With the default entry title it remains "Codex Bridge Assist".
- Sensors the App answers without a value report
unknowninstead ofunavailable: the last task outcome, usage and reset sensors, and saved-account values that are stale, signed out or unreported.unavailablenow means the App cannot answer. - The last task outcome sensor is now an enum sensor, so dashboards show translated state names such as "Completed". Its state values are unchanged.
- The saved-account allowance status sensor is an enum sensor with the states
available,stale,usage_unavailable(previouslyunavailable) andreauthentication_required, and thetelemetry_statusattribute of every saved-account sensor uses the same values. During an App outage the status sensor is unavailable, so Home Assistant hides its attributes, includingtelemetry_status,last_updatedanddata_age_seconds, until the App answers. Thesource_availableattribute has been removed from every saved-account sensor. - Task actions reject project or chat IDs containing characters other than letters, digits, underscores and hyphens, blank titles, prompts and overrides, and prompts over 65,536 bytes.
- Downgrading to Integration 1.13.12 leaves the saved-account devices in place without entities. Reinstalling 1.13.25 reuses them.
- Bundles the Sigstore-verified Codex runtime
0.166.0. - Keeps model and reasoning-level choices dynamically discovered from that runtime.
- Bundles Bridge
0.20.1without changing its Integration API compatibility.
Published from the signed App workflow: https://github.com/Herbertmt978/HA_Codex_Bridge/actions/runs/41244261499