Skip to main content
Code Runner executes a snippet and returns its output. Each call starts fresh — nothing persists between runs.

​
The tools

Two tools, same argument shape:
  • run_python — Python, core standard library.
  • run_javascript — JavaScript (ES6+), core standard library. No DOM or browser APIs.
The result carries stdout, stderr, an exit code, and execution metadata.

​
Filesystem

When the Files capability is also bound to the same agent or gateway, Code Runner can read and write the workspace with ordinary file I/O: Python uses open / pathlib. JavaScript uses an fs global exposing readFileSync, writeFileSync, existsSync, readdirSync, statSync, and mkdirSync. Files written here are shared with the Files capability and with other tools.
/workspace/home is agent-scoped and persistent, and concurrent Code Runner calls can race on it. Use unique filenames rather than assuming a lock.
Binding Files changes what the tool descriptions tell the model about the shared workspace; the mounts themselves are governed by the sandbox policy.

​
Limits

Execution is bounded twice — by a fuel budget and by a wall clock — so a tight loop is stopped either way. Fuel exhaustion surfaces as a timeout.

​
Cost

Metered per second of execution. See noorle.com/pricing.

​
Autonomy

Act tier. At Supervised it pauses unless auto-approved; at Read-only it is denied.

​
Code Runner or Sandbox?

Reach for Code Runner for arithmetic, parsing, and reshaping data. Reach for Sandbox when you need a dependency or a shell.

​
Next