Direct response
Claude Code and supported Grok or Hermes interactions can resolve through Masko.
PERMISSIONS AND APPROVALS
When an agent stops for permission or a question, Masko makes the request visible and gives you the action the integration can truly support.
macOS 14+ · Start free with Ko
NO FAKE BUTTONS
Some agents expose a response transport. Others keep the decision inside their native terminal or IDE. Masko preserves that boundary.
Claude Code and supported Grok or Hermes interactions can resolve through Masko.
Codex, Cursor, and Kimi keep certain questions and approvals in their own surface.
The visible request explains what is asking and what action is proposed.
The goal is not to remove the agent security model. It is to make the moment easier to notice and understand.
A supported hook or bridge exposes the interaction.
Masko shows the source, request, and available response path.
Resolve directly or return to the native prompt without hunting for it.
Every agent page publishes its current response behavior and limitation.
Direct actions are sent only through a response transport owned by the integration.
Dangerous commands can remain on the agent native security surface.
Version-sensitive integrations expose the release used for current compatibility testing.
TRY IT
› Refactor the sign-in flow
✓ Read src/auth/session.ts
✓ Read src/lib/validate.ts
✓ Updated the redirect handler
Claude wants to run a command
Bash · npm run build
one very attentive colleague.
Claude Code: answer supported hook permission prompts through the mascot.
Interactive preview. No commands run.THE LITTLE DETAILS
we were hoping you’d ask.
No. It can answer only when the integration exposes a supported response path.
Masko shows the request and returns you to the agent native terminal or IDE.
No. Masko routes supported responses and respects native approval boundaries.
Each agent exposes different hooks, payloads, and response channels.
Masko supports macOS 14 or newer.
MASKO FOR MAC