From 5f777006693110fe4bd9306ddd3572fcf34a712b Mon Sep 17 00:00:00 2001 From: "zoo-github-actions-auth[bot]" Date: Mon, 10 Aug 2026 14:58:53 +0000 Subject: [PATCH] YOYO NEW API SPEC! --- spec.json | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/spec.json b/spec.json index aeaaab1a..b053de4f 100644 --- a/spec.json +++ b/spec.json @@ -43144,6 +43144,15 @@ "description": "The content of the user's message.", "type": "string" }, + "correlation_id": { + "nullable": true, + "description": "Stable identifier used to correlate this user request across services.", + "allOf": [ + { + "$ref": "#/components/schemas/Uuid" + } + ] + }, "current_files": { "description": "The current files in the project, if any. This can be used to provide context for the AI. This should be sent in binary format, if the files are not text files, like an imported binary file.", "type": "object", @@ -43156,6 +43165,15 @@ } } }, + "engine_api_call_id": { + "nullable": true, + "description": "API call ID for the active Engine modeling session, when available.", + "allOf": [ + { + "$ref": "#/components/schemas/Uuid" + } + ] + }, "forced_tools": { "description": "The user can force specific tools to be used for this message.", "type": "array", @@ -43781,7 +43799,7 @@ "additionalProperties": false }, { - "description": "Replay containing raw bytes for previously-saved messages for a conversation. Includes server messages and client `User` messages.\n\nInvariants: - Client replay includes server messages: `Info`, `Error`, `Reasoning(..)`, `ToolOutput { .. }`, `Files { .. }`, `ProjectUpdated { .. }`, and `EndOfStream { .. }`. - Client replay also includes client `User` messages. - Backend replay includes client `User` messages plus selected reasoning, edit metadata, recovery output, and final responses. - The following are NEVER included: `SessionData`, `ConversationId`, `Delta`, `BackendShutdown`, or `ZookeeperAutoRouterMetadata`. - `ZookeeperRecoveryToolOutput` is included only in replay sent to the text-to-CAD backend and is filtered from client replay. - Ordering is stable: messages are ordered by prompt creation time within the conversation, then by the per-prompt `seq` value (monotonically increasing as seen in the original stream).\n\nWire format: - Each element is canonical serialized bytes (typically JSON) for either a `MlCopilotServerMessage` or a `MlCopilotClientMessage::User`. - When delivered as an initial replay over the websocket (upon `?replay=true&conversation_id=`), the server sends a single WebSocket Binary frame containing a MsgPack-encoded document of this enum: `Replay { messages }`.", + "description": "Replay containing raw bytes for previously-saved messages for a conversation. Includes server messages and client `User` messages.\n\nInvariants: - Client replay includes server messages: `Info`, `Error`, `Reasoning(..)`, `ToolOutput { .. }`, `Files { .. }`, `ProjectUpdated { .. }`, and `EndOfStream { .. }`. - Client replay also includes client `User` messages. - Backend replay includes client `User` messages plus selected reasoning, edit metadata, recovery output, and final responses. - The following are NEVER included: `SessionData`, `ConversationId`, `Delta`, `BackendShutdown`, `ZookeeperAutoRouterMetadata`, or `ZookeeperTurnUsage`. - `ZookeeperRecoveryToolOutput` is included only in replay sent to the text-to-CAD backend and is filtered from client replay. - Ordering is stable: messages are ordered by prompt creation time within the conversation, then by the per-prompt `seq` value (monotonically increasing as seen in the original stream).\n\nWire format: - Each element is canonical serialized bytes (typically JSON) for either a `MlCopilotServerMessage` or a `MlCopilotClientMessage::User`. - When delivered as an initial replay over the websocket (upon `?replay=true&conversation_id=`), the server sends a single WebSocket Binary frame containing a MsgPack-encoded document of this enum: `Replay { messages }`.", "type": "object", "properties": { "replay": {