From 6ec579a0c2f10672888376bc0105db25db833009 Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Wed, 3 Jun 2026 04:18:51 -0700 Subject: [PATCH] docs(web): document chat ack timing metadata (#89802) --- docs/web/control-ui.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/web/control-ui.md b/docs/web/control-ui.md index 7c128ba58349..ff11a9871b33 100644 --- a/docs/web/control-ui.md +++ b/docs/web/control-ui.md @@ -180,7 +180,7 @@ Activity entries keep only sanitized summaries and redacted, truncated output pr - - `chat.send` is **non-blocking**: it acks immediately with `{ runId, status: "started" }` and the response streams via `chat` events. + - `chat.send` is **non-blocking**: it acks immediately with `{ runId, status: "started" }` and the response streams via `chat` events. Trusted Control UI clients may also receive optional ACK timing metadata for local diagnostics. - Chat uploads accept images plus non-video files. Images keep the native image path; other files are stored as managed media and shown in history as attachment links. - Re-sending with the same `idempotencyKey` returns `{ status: "in_flight" }` while running, and `{ status: "ok" }` after completion. - `chat.history` responses are size-bounded for UI safety. When transcript entries are too large, Gateway may truncate long text fields, omit heavy metadata blocks, and replace oversized messages with a placeholder (`[chat.history omitted: message too large]`).