Atomic capability · tools

Terminal commandsProduct capability

Propose or execute shell commands in a project environment.

Terminal commands: 7 supported, 0 partial, 0 unsupported, 24 unreviewed across 31 cataloged products.

Markdown · JSON

Current evidence by product

Can my agent use Terminal commands?

Read across for the answer. 7 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

  • Supported7
  • Partial0
  • Unsupported0
  • Unknown24
  • Not applicable0

Web

9 products

Desktop

13 products

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

This capability covers a built-in, permissioned route for an agent to propose or execute shell commands in its working environment. It does not claim unattended execution, access beyond the selected workspace, a particular shell, or identical approval behavior.

Only current product documentation is used here. Preview tracks and unreviewed surfaces remain unknown.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Claude CLIcli · current
Supported
Target
current Claude Code CLI documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Cursordesktop · current
Supported
Target
current Cursor documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Codex CLIcli · current
Supported
Target
current Codex CLI documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Gemini CLIcli · current
Supported
Target
current Gemini CLI documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Copilot Chatdesktop · current
Supported
Target
current VS Code documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
OpenWork Desktopdesktop · current
Supported
Target
current OpenWork architecture documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • policyshell execution remains subject to OpenWork and OpenCode permission rules
Evidence
Grok Botdesktop · current
Supported
Target
2026-08-28 Grok Bot desktop documentation observation · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • runtimecommands run on the account-scoped hosted computer by default; credentials and files there are shared across the account's Bots
  • policycommands on the operator's local Mac or Windows computer are separately controlled and default to asking every time
Evidence
  1. 1. Evidence checked 2026-08-28: Claude Code documents Bash as a permission-controlled tool and provides CLI modes for agentic command execution.
  2. 2. Evidence checked 2026-08-28: Cursor Agent documents running terminal commands while completing coding tasks.
  3. 3. Evidence checked 2026-08-28: OpenAI documents Codex CLI as able to run code and commands locally in the selected directory.
  4. 4. Evidence checked 2026-08-28: Gemini CLI's official tool reference includes the `run_shell_command` tool with workspace and approval controls.
  5. 5. Evidence checked 2026-08-28: VS Code documents terminal tools for agent mode, with user-configurable approval and auto-approval behavior.
  6. 6. Evidence checked 2026-08-28: OpenWork's OpenCode-backed runtime includes shell execution, with permission requests surfaced in the desktop app and policy controlled by the host.
  7. 7. Evidence checked 2026-08-28: Grok Bot's persistent cloud computer includes a command line and filesystem; local-computer commands are a separate capability controlled by a desktop approval policy.