Resolve role-specific agent display identities at launch #1465

New issue

Closed

opened 2026-07-16 00:53:34 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-16 00:53:34 +00:00

Member

Consume cli-guard RoleAgentOverride.DisplayName and Pronouns for the selected role and harness. Resolve the role identity over the harness default, append it after composed session doctrine, use the same identity for Ward body and commit-trailer signatures while preserving fleet Git attribution, expose it through role inspection, and then activate the commented AOS role values. Schema support landed in cli-guard commit 6f0ee07. The staged AOS values landed in agentic-os commit 0bc2a54.

coilyco-ops added the

autonomy

headless

priority

labels

2026-07-28 08:54:03 +00:00

coilyco-ops referenced this issue from a commit

2026-07-28 09:37:52 +00:00

fix(agent): resolve role display identities

coilyco-ops closed this issue

2026-07-28 09:37:52 +00:00

coilyco-ops commented

2026-07-28 09:38:08 +00:00

Author

Member

WARD-WORKFLOW: done ✅

details

workflow: merge-remote-main; review summary: skipped - in-container review gate intentionally skipped because the temporary ward default is pending brokered QA.

Implemented role/harness display identity resolution, projected it into container doctrine and Ward signatures, preserved fleet Git attribution, exposed identity in role roster, and activated the staged AOS role values. Felt straightforward after finding the schema was already in cli-guard. Confidence: high. Surprises: remote main advanced twice during landing and one package test run hit a pre-existing async cleanup flake before clean reruns. Follow-ups: none.

WARD-WORKFLOW: done ✅ <details><summary>details</summary> workflow: merge-remote-main; review summary: skipped - in-container review gate intentionally skipped because the temporary ward default is pending brokered QA. Implemented role/harness display identity resolution, projected it into container doctrine and Ward signatures, preserved fleet Git attribution, exposed identity in role roster, and activated the staged AOS role values. Felt straightforward after finding the schema was already in cli-guard. Confidence: high. Surprises: remote main advanced twice during landing and one package test run hit a pre-existing async cleanup flake before clean reruns. Follow-ups: none. </details>

coilyco-ops commented

2026-07-28 09:38:19 +00:00

Author

Member

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: done ✅.

ward container reap released container engineer-codex-ward-1465 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-ward-1465` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-28 09:46:58 +00:00

Inspect failed release run 2501 after role identity launch landed #1605

coilyco-ops referenced this issue

2026-07-28 10:09:55 +00:00

Inspect failed release run 2501 after role identity launch landed #1605