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 XML commands: structured command envelopes for workflow, integration, 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 XML Command Types​

Common command 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

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. Use SageChat XML commands for structured mutations.
  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.