How do the top AI agent harnesses handle tool calls?

The seven harnesses ship the same core tools (read, write, edit, run a command) and differ on who approves a call. OpenCode and pi run tools without asking by default; Antigravity's default asks only outside a sandbox; Codex sets a sandbox and a separate approval policy; Claude Code layers allow, ask and deny rules that hooks can tighten. Read 2026-11-06.

By Mackenzie Bowes · mackenzie@mackenziebowes.com · @_mackenziebowes on X

Contents

Short answer, from the docs read: the tool list is nearly the same everywhere, and the real difference is the default for who approves a call. pi and OpenCode run tools without asking unless the user turns on checks.[1][2] Antigravity's default lets commands run inside a sandbox and asks before leaving it.[3] Codex splits the question in two: a sandbox sets what a command can touch, and an approval policy sets when the agent must stop and ask.[4] Claude Code lets a user write allow, ask and deny rules per tool, and its docs say a deny rule keeps a call refused and a hook that blocks a call stays blocked.[5] Cursor's agent docs list its tools but the approval settings were not read.[6] This is the third page in a series that began with a survey of the harnesses and continued with memory.

A tool call is the moment the model asks the harness to do something, such as read a file or run a command, and the harness decides whether to do it and returns the result.

The tools they ship

Who approves a call

Where the line between sandbox and permission falls

Two harnesses treat a sandbox as the thing that makes asking unnecessary. Antigravity's Default and Auto presets run commands without prompts only inside a sandbox.[3] Codex says the sandbox reduces approval fatigue, because the agent can run routine commands inside a boundary the user already approved.[4] Hermes Agent offers the sandboxed backends but the page read does not say whether it prompts.[7]

What the comparison rules out

These are consequences of the docs read, not findings from a test.

Terms

Not yet proven

If you run one of these harnesses and its defaults surprised you, I would like to hear it: mackenzie@mackenziebowes.com.

Sources

  1. Mario Zechner, "What I learned building an opinionated and minimal coding agent", 2025-11-30. Read in Rotunda 2026-11-06. mariozechner.at/posts/2025-11-30-pi-coding-agent/
  2. OpenCode docs, Tools. Read in Rotunda 2026-11-06. opencode.ai/docs/tools/
  3. Google Antigravity Docs, Agent settings. Read in Rotunda 2026-11-06. antigravity.google/docs/agent-settings
  4. OpenAI, Codex docs, Sandbox. Read in Rotunda 2026-11-06. learn.chatgpt.com/docs/sandboxing
  5. Claude Code Docs, Permissions. Read in Rotunda 2026-11-06. code.claude.com/docs/en/permissions
  6. Cursor Docs, Agent overview. Read in Rotunda 2026-11-06. cursor.com/docs/agent/overview
  7. Hermes Agent docs, Tools and Toolsets. Read in Rotunda 2026-11-06. hermes-agent.nousresearch.com/docs/user-guide/features/tools
  8. Claude Code Docs, Tools reference. Read in Rotunda 2026-11-06. code.claude.com/docs/en/tools-reference
  9. OpenCode docs, Permissions. Read in Rotunda 2026-11-06. opencode.ai/docs/permissions/
  10. Claude Code Docs, Memory. Saved 2026-10-22. code.claude.com/docs/en/memory

Terms on this page

  • Hook: A command that an AI coding agent runs automatically at a set point in its work.
  • Model Context Protocol: An open standard for connecting AI applications to outside tools and data.
  • Tool call: A request from an AI model to run one action, such as a search or a file write, which the surrounding program carries out.