Publish the chat and setup fields the dashboard cannot see #1645

Closed
opened 2026-10-27 13:41:13 +00:00 by sam · 0 comments
Owner

Two dashboard behaviours degrade in the extracted UI process because webui.Server.Cfg is nil there and the published ConfigView does not carry the values:

  1. chat.show_tool_calls (api_chat.go chatShowToolCalls) is always false, so the chat page never expands tool calls however the daemon is configured.
  2. /api/setup (api_setup.go handleSetup) returns an empty step list, so the getting-started checklist panel is omitted. Identity/repos are already in the snapshot; the chat-channel step and the operator name are not.

Fix is additive on the ratified mechanism, not a new decision: the daemon publishes the fields in webui.ConfigView (as MultiIdentity was added on 2026-09-11 for task forge links), and the handlers read the projection when they hold no configuration. Check whether the setup checklist is even wanted in a process that cannot fix anything it reports before adding fields for it.

Found by the real-process smoke suite on archie-core-8cda.5.6; recorded in docs/prds/ui-service-boundary.md under 'Real-process evidence'. Related: archie-core-ml30.

Close reason

Landed in 55a4ac2 + 03775e6; GitHub #821 already closed.


Imported from beads archie-core-wg23 · GitHub #821 · type task · priority P3 · created 2026-09-11 · closed 2026-09-17

Two dashboard behaviours degrade in the extracted UI process because webui.Server.Cfg is nil there and the published ConfigView does not carry the values: 1. chat.show_tool_calls (api_chat.go chatShowToolCalls) is always false, so the chat page never expands tool calls however the daemon is configured. 2. /api/setup (api_setup.go handleSetup) returns an empty step list, so the getting-started checklist panel is omitted. Identity/repos are already in the snapshot; the chat-channel step and the operator name are not. Fix is additive on the ratified mechanism, not a new decision: the daemon publishes the fields in webui.ConfigView (as MultiIdentity was added on 2026-09-11 for task forge links), and the handlers read the projection when they hold no configuration. Check whether the setup checklist is even wanted in a process that cannot fix anything it reports before adding fields for it. Found by the real-process smoke suite on archie-core-8cda.5.6; recorded in docs/prds/ui-service-boundary.md under 'Real-process evidence'. Related: archie-core-ml30. ### Close reason Landed in 55a4ac2 + 03775e6; GitHub #821 already closed. --- _Imported from beads `archie-core-wg23` · GitHub #821 · type task · priority P3 · created 2026-09-11 · closed 2026-09-17_
sam added the lowtask labels 2026-10-27 13:41:13 +00:00
sam self-assigned this 2026-10-27 13:41:13 +00:00
sam closed this issue 2026-10-27 13:41:13 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1645