Skip to main content

SageChat + Command System

SageChat is not only chat UI. It is a command surface with structured execution paths.

Two Control Layers​

  • Command Palette (Cmd/Ctrl + K): high-speed route/action launcher for operators
  • SageChat command protocol: server-guided structured envelopes for workflow, integration, UI intent, WebSocket, and context operations

Command Palette: Operational Shortcuts​

Representative actions include:

  • GrayMatter start path
  • Workflow Studio launch
  • Agents Hub
  • Integration Accounts
  • OpenAPI Studio
  • Swarm Ops
  • CMS / CRM / data workbook routes

Actions can be auth-gated and are ranked with recent-command bias for speed.

SageChat Command Protocol​

Operators should use plain English. The XML/JSON envelopes are executor protocol emitted by Valor and parsed by the app; they must not be shown as explanatory chat text or presented as the primary user command language.

When protocol blocks appear in an assistant response, SageChat renders them as informative command/status cards with icons, summaries, options, and execution state. Workflow commands execute through the deterministic command system and target REST/control-plane handlers; UI-intent commands synchronize panels without free-text parsing in downstream components.

Common protocol categories in production:

  • <readpage /> for context capture
  • <workflow>...</workflow> for create/update/task/module operations
  • <integration>...</integration> for integration account operations
  • <apiaction>...</apiaction> for deterministic UI intents
  • <screencapture>...</screencapture> for screenshot or DOM scrape capture
  • <websocket>...</websocket> for broadcast/coordination messages
  • <ask_followup_question>...</ask_followup_question> for option cards that collect the next operator choice
  • <attempt_completion>...</attempt_completion> for terminal result cards

Deterministic UI Intents​

SageChat emits normalized UI-intent events (for example, open-target-view, show-report, launch-server-config-wizard, bind-account) so downstream panels can react reliably instead of parsing free text.

Workflow Context Injection​

When workflow intent is detected, SageChat uses API-doc fragments (/docs/fragments/*) to inject valid module/schema context before generation requests. This reduces invalid module payloads and improves first-pass workflow quality.

Operator Guidance​

  1. Use Command Palette for navigation and known actions.
  2. Ask SageChat in plain English for structured mutations; Valor decides when to emit executor protocol.
  3. Confirm side effects in target panels (workflow canvas, integration console, telemetry views).

Pair with Workflow Studio and Integration Accounts + MCP Marketplace for end-to-end operation.