Finding / omnigent

2026-10-13-omnigent-brokered-databricks-authentication-adds-a-contained-codex-executor-and-a-migration-contrac

Brokered Databricks authentication adds a contained Codex executor and a migration contract. v0.16.0 introduces trusted-signer authentication and a model_egress grant for the affected Databricks Codex executor. The worker receives a placeholder while the trusted signer owns credential minting and request authorization. Signer-backed execution refuses an inactive or unsupported sandbox and constrains the registered endpoint. This is a specific executor path, not every codex-native launch. The newest tag accepts stable Codex 0.146.0 or newer, so the introducing PR’s exact-version claim is stale.

Channel: tagged-release. Half: both. Date: 2026-09-26 merged; 2026-09-29 stable package.

Operator consequence: Configure the active supported sandbox, explicit provider/profile, route grant and credential helper before migrating this path. Keep the signer outside the worker’s authority. Validate the actual Codex version rather than copying an old exact-version pin; no end-to-end credential-containment test was run here.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-omnigent-brokered-databricks-authentication-adds-a-contained-codex-executor-and-a-migration-contrac

Profile citations

  • omnigent / claim / brokered-codex-launch-contract

Source links

Primary links, including exact changelog lines when available.