Atomic capability · tools

Code executionProduct capability

Run generated code in a sandbox.

Code execution: 0 supported, 1 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.

Markdown · JSON

Current evidence by product

Can my agent use Code execution?

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

  • Supported0
  • Partial1
  • Unsupported0
  • Unknown30
  • 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

Run generated code in a sandbox or constrained project environment. OpenWork’s cell stays partial because the reviewed source establishes local execution and approval boundaries, not a default isolation guarantee.

The matrix below lists published web, desktop, and CLI surfaces. Unreviewed cells remain unknown until a dated note and public source support a more specific status.

Use the Markdown and JSON twins if you are an agent reading this site.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

OpenWork Desktopdesktop · current
Partial
Target
current OpenWork architecture documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • runtimelocal workspace execution is documented; default sandbox isolation is not
  • policyexecution is constrained by workspace and approval configuration
Evidence
  1. 1. Evidence checked 2026-08-28: OpenWork Desktop runs OpenCode and the OpenWork server against a selected workspace and documents shell execution as a permission-sensitive primitive; default sandbox isolation is not established.