Codex director launch config ignores selected roles.kdl model overlay #1497

New issue

Closed

opened 2026-07-22 08:38:38 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-22 08:38:38 +00:00

Member

A director Codex surface is launching with model/effort values that do not match the selected agentic-os role bundle.

Evidence from the surfaced container:

WARD_ROLE=director
WARD_CONFIG_REF=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os@524e5765162c56718e7938efb237e6a798700164//.ward
/home/ubuntu/.ward/.codex/config.toml contains model = "gpt-5.5" and model_reasoning_effort = "high"
Codex session payload also reports model: "gpt-5.5"

The selected bundle at /opt/ward-context/coilyco-flight-deck/agentic-os/.ward/roles.kdl has role director > agent codex set to model gpt-5.6-sol and reasoning-effort xhigh. Current Forgejo main for agentic-os .ward/roles.kdl shows the same director Codex values.

Ward's embedded fleet overlay in .ward/ward-kdl/ward-kdl.fleet.kdl and cmd/ward/fleetassets/fleet.generated.kdl still sets director Codex to gpt-5.5 / high, and that appears to be what the entrypoint uses to write Codex config.

Please reconcile the config source precedence so director Codex launch config matches the selected role bundle, or make the runtime intentionally ignore roles.kdl for model overlays and update the visible config/docs so operators do not read roles.kdl as authoritative. Add a regression test around a director Codex surface with WARD_CONFIG_REF selecting a bundle whose role overlay differs from the embedded fleet default.

A director Codex surface is launching with model/effort values that do not match the selected agentic-os role bundle. Evidence from the surfaced container: - `WARD_ROLE=director` - `WARD_CONFIG_REF=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os@524e5765162c56718e7938efb237e6a798700164//.ward` - `/home/ubuntu/.ward/.codex/config.toml` contains `model = "gpt-5.5"` and `model_reasoning_effort = "high"` - Codex session payload also reports `model: "gpt-5.5"` The selected bundle at `/opt/ward-context/coilyco-flight-deck/agentic-os/.ward/roles.kdl` has `role director > agent codex` set to `model gpt-5.6-sol` and `reasoning-effort xhigh`. Current Forgejo main for agentic-os `.ward/roles.kdl` shows the same director Codex values. Ward's embedded fleet overlay in `.ward/ward-kdl/ward-kdl.fleet.kdl` and `cmd/ward/fleetassets/fleet.generated.kdl` still sets director Codex to `gpt-5.5` / `high`, and that appears to be what the entrypoint uses to write Codex config. Please reconcile the config source precedence so director Codex launch config matches the selected role bundle, or make the runtime intentionally ignore `roles.kdl` for model overlays and update the visible config/docs so operators do not read `roles.kdl` as authoritative. Add a regression test around a director Codex surface with `WARD_CONFIG_REF` selecting a bundle whose role overlay differs from the embedded fleet default.

coilyco-ops referenced this issue

2026-07-22 08:41:47 +00:00

Audit and remove remaining baked coilyco fleet configuration from ward #1498

coilyco-ops referenced this issue

2026-07-22 08:44:36 +00:00

Codex engineer launch fails when prompt begins with dash-prefixed pre-flight text #1499

coilyco-ops referenced this issue from a commit

2026-07-22 10:28:56 +00:00

fix(agent): project selected role config (closes #1497)

coilyco-ops closed this issue

2026-07-22 10:28:56 +00:00

coilyco-ops commented

2026-07-28 08:58:57 +00:00

Author

Member

WARD-WORKFLOW: reservation-released

release details

Run never started. ward container reap released container engineer-codex-ward-1497 (--harness codex): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A ward agent director re-queues it automatically. A manual ward agent retry no longer needs --override-reservation.

— Codex, via ward agent

WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run never started. `ward container reap` released container `engineer-codex-ward-1497` (`--harness codex`): it exited without launching the agent (smoke-test death, ward#222/#264/#595), so it did no work and the launch intent it took is retracted. Nothing is running on this issue. It needs re-dispatch. A `ward agent director` re-queues it automatically. A manual `ward agent` retry no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/ward#1497

No description provided.

Rows
Columns