BashExecutorDescription
Defined in: bash/executor.ts:39
BashExecutor.describe’s return shape — the sandbox config actually in effect.
Extended by
Section titled “Extended by”Properties
Section titled “Properties”allowRead
Section titled “allowRead”allowRead:
string[] |null
Defined in: bash/executor.ts:54
Absolute paths reads are confined to, or null when this executor is not bounding reads
at all (the whole host filesystem is visible read-only). null is the honest answer for
a backend that cannot bound reads — createAsrtBashExecutor — rather than reporting an
empty list that would read as “nothing is readable.”
Even when non-null, the sandbox still contains the system paths any program needs to
execute (/usr, /etc, the lib directories), so /etc/passwd stays readable. The
guarantee is “no user data outside these roots,” not “only these roots.”
allowWrite
Section titled “allowWrite”allowWrite:
string[]
Defined in: bash/executor.ts:43
Absolute paths writable inside the sandbox.
backend
Section titled “backend”backend:
string
Defined in: bash/executor.ts:41
Which executor implementation this is, e.g. "asrt" or "native".
denyRead
Section titled “denyRead”denyRead:
string[]
Defined in: bash/executor.ts:56
Absolute paths hidden from reads, on top of the executor’s own defaults.
denyWrite
Section titled “denyWrite”denyWrite:
string[]
Defined in: bash/executor.ts:58
Absolute paths denied write access, on top of allowWrite not already covering them.
network
Section titled “network”network:
object
Defined in: bash/executor.ts:59
allowedDomains?
Section titled “allowedDomains?”
optionalallowedDomains?:string[]
Domains allowed when allowNetwork is true and the executor supports per-domain rules.
allowNetwork
Section titled “allowNetwork”allowNetwork:
boolean
deniedDomains?
Section titled “deniedDomains?”
optionaldeniedDomains?:string[]