Repository navigation
Description
The Chat window does not say which Completer is answering. With a Harness attached and with the HTTP endpoint, the conversation looks identical, so a user cannot tell which mind they are talking to, or that a Harness they configured never came up.
The owner proposed the upper right corner, in small text, and invited a challenge. Here is one.
Where it should go
Not a floating corner label. ADR-0010 already sanctions exactly one place for this kind of fact: "the bar may say what our own layers are doing right now, in one line, with nothing to operate", and it warns about "the next pull request that wants a sixth thing in this window". A badge in the corner is that sixth thing, and the upper right of a window is where controls live, so a label there invites a click on something that does nothing.
Two candidates that respect the ADR:
- The opening header, beside who you are talking to. The mode is a constant for the process. One session serves the app's lifetime per ADR-0008, and feat(settings): Choose the Completer source in Settings, not only the env (#436) #452 settled that changing the source takes a relaunch, so the mode cannot change while the window is open. Constants belong where the window says what this conversation is, and
chat_openingalready carries the Harness inspect for the empty state, including the not-authenticated case and its login command. Cheapest, and it reads as identity rather than telemetry. - A cell at the left end of the status bar. Defensible, but the bar is for what changes every tick, and it has a width budget its own comments guard carefully: cells are kept to three characters so the line fits. A mode string is the widest thing that would ever sit there.
Recommend the first, with the live facts left where they are. The bar already says whether a turn is on the wire and when the next wake is due; the mode is not that kind of fact.
What it should say
- Harness attached: its name, and enough to prove it is live rather than merely configured.
hermes · session 655092d4reads well and matches what Settings shows. - Harness set but not running: say so, since this is the state a user most needs to see and the one feat(settings): Choose the Completer source in Settings, not only the env (#436) #452 made visible in Settings.
- Harness attached but not authenticated: name the login command, as Settings does. Never run it.
- No Harness: the model and the host,
gpt-4o-mini · localhost:8000. - Director off: static weights, since there is no mind at all then.
Never print a key, a token, or a URL carrying credentials. ADR-0010's seventh rule covers logging a credential and the same applies to drawing one.
Acceptance
- The Chat window says which mind is answering, in all five states above, without a control the user can press.
- It agrees with what the Director inspect reports, so Settings and Chat cannot disagree.
- No credential is drawn.
- If it lands in the status bar instead, the line still fits at the window's minimum width.
Related: ADR-0010 for the surface, ADR-0008 for why the mode is constant, #452 for the Settings copy this should match, #466 for whether "Director" is the right word to show a user at all.
— Claude Code, on @omesser's behalf.
Metadata
Metadata
Assignees
Labels
Projects
- StatusShow more project fieldsDone
Activity
omesser commentedon Sep 7, 2026
The dependency for this has landed. #480 merged, so an already-open Chat surface is now told when Director or the Harness source changes, and it re-reads the opening rather than keeping the mode it opened with.
That was the missing half: a mode label is only honest if it refreshes when the mode does. The recommendation in the issue stands, and the push it needs now exists.
— Claude Code, on @omesser's behalf.
feat(chat): Name login command in header for not-signed-in state
docs(pr): Refresh #474 mind-header screenshots for FA brain glyph
omesser commentedon Sep 9, 2026
Landed in #550 (
113624d). Chat header now shows which mind answers (Harness or HTTP), with the not-signed-in case naming the login command.— Cursor agent (Coder), on @omesser's behalf.