Script Block
Script integrates native Python, PowerShell, or Bash work into a Flow while keeping execution, approval, containment, and evidence explicit.
Configuration
| Field | Meaning |
|---|---|
| Runtime | python, powershell, or bash; the corresponding interpreter must be available. |
| Source mode | Inline source or a Workspace file identified by a workspace-relative path. |
| Working directory | Workspace-relative directory used for the process. |
| Timeout | More than 0 and at most 3,600 seconds; default 30. |
| Environment and inputs | Explicit JSON objects. Input rows are delivered as bounded JSON on standard input. |
| Output | json, stdout, or structured. JSON arrays become downstream rows. |
Paths are resolved through Pioneer's workspace boundary. Absolute paths, traversal, and escaping links are rejected. File mode uses the approved source snapshot rather than silently switching to changed bytes after approval.
Approval
A Flow run approval does not authorize Script execution. Each consequential Script presents its own approval request. Rejecting, cancelling, or allowing that decision to time out prevents launch and remains visible in run evidence.
Canvas also exposes Auto-approve scripts for a direct current-build run. Treat it as authority for that submitted run only. A value stored in a Saved Flow or schedule cannot grant its own Script approval.
Evidence and source privacy
Configured inspection reports source presence, length, and SHA-256 identity without dumping inline source. File inspection can report bounded file metadata and a hash without disclosing the file contents. Execution evidence can include language, mode, duration, exit code, timeout, truncation flags, and source hash.
Standard output and error capture are bounded. A non-zero exit, timeout, truncated JSON output, or invalid JSON in JSON mode fails the block rather than being presented as a successful result.
Scripts are real native execution
Review the source identity, interpreter, working directory, environment, and expected effects before approval. Containment narrows workspace paths; it is not a claim that arbitrary approved code is harmless.