Web chat answers with generated UI #3

Closed
opened 2026-10-27 13:34:12 +00:00 by sam · 2 comments
Owner

StreamRequest gains can_render_ui (only the web UI sets it) and Message gains a format so stored replies re-render. The gateway adds the library prompt when the flag is set. Query() maps to the WebMCP tool registry so views stay live without another turn; Mutation only for actions that already go through approval. Telegram and email keep Markdown.

Acceptance criteria

A web chat answer can render as a live view (e.g. a task table backed by a Query); other channels receive Markdown unchanged.


Imported from beads archie-core-11uab.2 · GitHub #1848 · type feature · priority P3 · created 2026-10-25

StreamRequest gains can_render_ui (only the web UI sets it) and Message gains a format so stored replies re-render. The gateway adds the library prompt when the flag is set. Query() maps to the WebMCP tool registry so views stay live without another turn; Mutation only for actions that already go through approval. Telegram and email keep Markdown. ### Acceptance criteria A web chat answer can render as a live view (e.g. a task table backed by a Query); other channels receive Markdown unchanged. --- _Imported from beads `archie-core-11uab.2` · GitHub #1848 · type feature · priority P3 · created 2026-10-25_
sam self-assigned this 2026-10-27 13:34:12 +00:00
Author
Owner

Decided against this, It's tacky.

Decided against this, It's tacky.
sam closed this issue 2026-11-10 11:54:42 +00:00
Author
Owner

Concrete cases from a design review of the chat as the primary interface: (1) action cards inside a reply, e.g. a PR mention carries Review PR and a diagnosed blocker carries its fix button, reusing the blocker routes the dashboard already has; (2) mini-forms in the reply when the fix needs input, e.g. a credential reference field and Save; (3) a workflow built from chat renders its node map in the reply and updates as the operator iterates; (4) long diagnoses lead with a short summary and put the trace in a collapsible block.

Concrete cases from a design review of the chat as the primary interface: (1) action cards inside a reply, e.g. a PR mention carries Review PR and a diagnosed blocker carries its fix button, reusing the blocker routes the dashboard already has; (2) mini-forms in the reply when the fix needs input, e.g. a credential reference field and Save; (3) a workflow built from chat renders its node map in the reply and updates as the operator iterates; (4) long diagnoses lead with a short summary and put the trace in a collapsible block.
sam added the lowfeature labels 2026-11-12 15:51:27 +00:00
sam added a new dependency 2026-11-14 14:45:14 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#3