ward canonical 1st time user flow #1138

New issue

Open

opened 2026-07-13 01:53:48 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-07-13 01:53:48 +00:00

Owner

The problem

people having a smooth setup

Proposed change

warded director < issue ref >

mandatory configs like the image url, issue tracker, auth...

smoke test all the necessary things. docker, git, issue tracker, agent auth...

launch the engineer

show current configuration, press enter to continue (really only necessary for agents that launch TUIs like claude, other agents should just continue)

director launches, it knows about the engineer that just launched, mentions that you -can- watch it but the idea of ward is that we are providing enough warding that they should be able to work on their own

and then... user does whatever they want past that point. not our scope anymore

Alternatives considered

No response

Before filing

I searched existing issues and this is not a duplicate.
This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

Decision for release inclusion

Removed from warded control plane coherence for now. Kai confirmed this is not headless yet because prior attempts did not capture enough scope. Bring this back only after the first-time-user flow is decomposed into concrete ward-owned steps or after a human scopes the full path in detail.

### The problem people having a smooth setup ### Proposed change `warded director < issue ref >` mandatory configs like the image url, issue tracker, auth... smoke test all the necessary things. docker, git, issue tracker, agent auth... launch the engineer show current configuration, press enter to continue (really only necessary for agents that launch TUIs like claude, other agents should just continue) director launches, it knows about the engineer that just launched, mentions that you -can- watch it but the idea of ward is that we are providing enough warding that they should be able to work on their own and then... user does whatever they want past that point. not our scope anymore ### Alternatives considered _No response_ ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb. --- ## Decision for release inclusion Removed from `warded control plane coherence` for now. Kai confirmed this is not headless yet because prior attempts did not capture enough scope. Bring this back only after the first-time-user flow is decomposed into concrete ward-owned steps or after a human scopes the full path in detail.

coilysiren added the

interactive

labels

2026-07-13 01:53:48 +00:00

coilysiren referenced this issue

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283