Surfaces

Decide when to use the Web app, CLI, MCP, or Slack.


Surface Best for Main boundary
Web Browsing, settings, billing, administration Not intended for scripting
CLI Authoring, publication, scripts, administration Works explicitly with UUIDs and JSON
MCP Agent-operated case coordination and playbooks Workspace administration remains outside MCP
Slack Creating cases, tasks, and notes; linking threads; personal notifications Requires workspace installation and a personal connection

All surfaces operate on the same cases, playbooks, tasks, records, and suggestions. CLI and MCP expose matching domain operations with names adapted to each protocol. Review content before publishing from either surface, and use a workspace-scoped token when automation must have an unambiguous context.