Platforms

Supported Runtimes

Provider-by-provider breakdown of hook contexts, approval modes, and Stoplight-assisted support for ask, allow, and deny workflows.

Hook functionality varies significantly among agent runtimes, but Stoplight aims to provide a clear, standardized experience across all of them. Understanding how we do this involves understanding the current level of provider-level hook support for tool calls, as well as whether your agents are predominantly running from highly interactive sessions, or from headless, remote environments.

In all cases, wherever hook-based `ask` menus are not supported, or invoked from headless, remote environments, Stoplight uses a custom, remote approval interface that blocks tool calls until expiry and polls the Stoplight backend until a decision is made.

Available agent runtimes

Claude Code hook contexts

Hook context	Covers	Allow	Ask	Deny	Fail mode
`PreToolUse`	command file mcp	Yes	Native ask	Yes	open

Approval coverage by operation kind

Kind	Mapped hook contexts	Runtime native approvals	Stoplight native ask	Recommended path
Command	PreToolUse	Available	Available	Native or Stoplight
File	PreToolUse	Available	Available	Native or Stoplight
MCP	PreToolUse	Available	Available	Native or Stoplight

Recommendation

Native approvals work well

Claude Code exposes native ask support cleanly enough that local approval workflows remain viable across the main operation kinds.

Tool-name mapping

Shell

Bash

Read

Write

Edit

MultiEdit

Glob

Grep

Web

WebFetch

WebSearch

Task