Scripts and automation commands¶

Scripts and automation commands can use pVisor's execution boundaries, staging, review and records too.

pvisor spawn --safe --overlaynet-deny-all -- ./agent.sh
pvisor status --review last
pvisor apply last --path src

Behavior¶

• The command runs in the staged view, which contains the project's current files; writes go to the stage.
• pvisor spawn returns the command's exit code unchanged, so scripts and CI can judge success or failure.
• If the command exits nonzero, its file changes stay staged for you to review and apply or drop.
• Everything after -- is passed through unchanged as the command and arguments.

Networking¶

When a script matches no agent preset, --safe denies all outbound access. Choose as needed:

When used as command names, bash, sh, zsh, and fish reuse the Codex preset destinations; see --safe presets.

Environment variables¶

--safe projects only the necessary variables. Pass the variables a script needs explicitly with --pass-env NAME; see credentials and environment.

Complete example¶

Your first run uses a "fake agent" script to demonstrate modifications, deletion, a denied sensitive read, and blocked networking. The runnable examples under examples/pvisor/ cover file isolation, changeset management, and network isolation.