coilyco-flight-deck/ward

Watch

Keep brokered engineers visually grouped with their Ward Compose app #1590

New issue

Closed

opened 2026-07-28 07:46:31 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-28 07:46:31 +00:00

Member

Engineer containers should visually group with their director/broker Compose app.

Problem

warded director now keeps the director and dispatch broker visually grouped in Docker Desktop, but brokered engineer containers still appear as separate top-level containers instead of underneath the same Compose application as the director and broker that launched them.

That makes demos and live operation harder to read: the workflow looks like disconnected containers even though the engineer belongs to the same Ward control-plane session.

This is a visual ownership/discoverability issue, not necessarily a broker-connectivity issue.

Expected behavior

When a director dispatches an engineer through the broker, Docker Desktop should show the engineer under the same relevant Compose application/group as the director and broker, or Ward should provide an equivalent grouping label/project convention that Docker Desktop recognizes.

Scope

Inspect the current labels and launch path for brokered engineer containers.
Compare them with the fixed director/broker grouping behavior from ward#1564.
Preserve detached engineer lifecycle, cleanup, logs, and broker visibility.
Do not dispatch an engineer from this issue filing session.

Acceptance

A brokered engineer launched from a director is visually grouped with the related Ward Compose app in Docker Desktop when the UI supports that grouping.
The engineer still carries clear ward.* labels for repo, issue, role, harness, and dispatch request.
Existing ward agent list, ward agent logs <target>, reaper, and dispatch-health behavior continue to work.
Automated coverage protects the chosen label/project/launch contract, with bounded manual Docker Desktop verification for UI rendering.

ward#1564 fixed the analogous director/broker visual grouping problem.
ward#1567 wants no-target logs to discover the current Compose group.

Engineer containers should visually group with their director/broker Compose app. ## Problem `warded director` now keeps the director and dispatch broker visually grouped in Docker Desktop, but brokered engineer containers still appear as separate top-level containers instead of underneath the same Compose application as the director and broker that launched them. That makes demos and live operation harder to read: the workflow looks like disconnected containers even though the engineer belongs to the same Ward control-plane session. This is a visual ownership/discoverability issue, not necessarily a broker-connectivity issue. ## Expected behavior When a director dispatches an engineer through the broker, Docker Desktop should show the engineer under the same relevant Compose application/group as the director and broker, or Ward should provide an equivalent grouping label/project convention that Docker Desktop recognizes. ## Scope - Inspect the current labels and launch path for brokered engineer containers. - Compare them with the fixed director/broker grouping behavior from ward#1564. - Preserve detached engineer lifecycle, cleanup, logs, and broker visibility. - Do not dispatch an engineer from this issue filing session. ## Acceptance - A brokered engineer launched from a director is visually grouped with the related Ward Compose app in Docker Desktop when the UI supports that grouping. - The engineer still carries clear `ward.*` labels for repo, issue, role, harness, and dispatch request. - Existing `ward agent list`, `ward agent logs <target>`, reaper, and dispatch-health behavior continue to work. - Automated coverage protects the chosen label/project/launch contract, with bounded manual Docker Desktop verification for UI rendering. ## Related - ward#1564 fixed the analogous director/broker visual grouping problem. - ward#1567 wants no-target logs to discover the current Compose group.

coilyco-ops commented

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

Author

Member

WARD-WORKFLOW: reservation-released

release details

Run never started. ward container reap released container engineer-codex-ward-1590 (--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-1590` (`--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`

coilyco-ops added the

autonomy

headless

priority

labels

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

coilyco-ops referenced this issue

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

Provide a concise issue-scoped asynchronous status summary #1601

coilyco-ops added

priority

and removed

priority

labels

2026-07-29 06:19:14 +00:00

coilyco-ops referenced this issue

2026-07-31 08:09:53 +00:00

Give each Ward collaboration cluster a harness-scoped stable identity #1592

coilyco-ops commented

2026-07-31 08:12:13 +00:00

Author

Member

Closing as merged into rewritten #1592. The canonical session-identity issue now covers both concurrent Compose naming and director, broker, and engineer grouping.

coilyco-ops closed this issue

2026-07-31 08:12:14 +00:00

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#1590

No description provided.

Rows
Columns