Skip to main content
This matrix was reviewed against official upstream contracts on October 27, 2026. A registered callback does not prove that every provider version emits it. Configuration-layout tests, a native client run, and delivery from your deployed provider are separate validation steps. Use Cloud agent hooks for Cursor Cloud Agents and Grok Bot. Use device managed hook actions for local clients. Native hook coverage is separate from network routing coverage. Platform-specific layouts describe setup support. Historical binary evidence does not qualify every current client release or operating system. Verify the exact runtime and provider version in your environment before a broader rollout. Cloud monitoring does not execute policy enforcement. The generic profile installer excludes entries whose canonical kind is empty. Session-boundary names in the shared profile describe parser acceptance, not installed callback coverage. Product-specific installers can register additional lifecycle observations. Verify emitted boundaries on the actual installed configuration before claiming a complete session history. Native command hooks use their own setup. Framework SDK instrumentation, OTLP exporters, provider inference hooks and gateway routing require separate configuration and credentials. Their visibility and controls differ. When several routes report the same activity, verify correlation before treating the records as additional conversation coverage.

Current limits

  • Cursor Cloud can emit generic HTTP MCP tool callbacks with redacted output. Dedicated cloud MCP callbacks and early read-only turns remain unavailable. Redacted content is not inspected content.
  • Grok Bot team setup may expose secrets only to setup processes. Persist the collector secret privately for later hooks. Validate a fresh Bot for each pilot member. A missing native conversation ID permits tool-use pairing, not conversation reconstruction.
  • VS Code Local is a legacy harness. The current shared Copilot harness has a separate contract and setup path.
  • Qwen UserPromptSubmit can represent a model continuation. Its callback name alone does not establish a new human prompt.
  • Cowork can execute remotely. Desktop plugin qualification does not establish coverage of hosted sessions across web or mobile.
A watcher or manual intervention request records intent. Check the linked evaluation and outcome to determine what happened. Only an applicable executed enforcement path can establish that a tool was blocked or rewritten. Monitor-only cloud events remain observational.