Governance / Pro
pi-sandlock
Tiered process isolation. The agent runs inside a capability tier - what it can touch is bounded by the kernel, not by prompts.
What it does.
- Kernel-level enforcement - seccomp + Landlock via the Sandlock engine.
- Five capability tiers (offline to full-write) with a per-project ceiling; elevation requires confirmation.
- Multi-profile configs per project, persisted across reloads, switchable from the command line.
- Deny-by-default gate for unconfined tools, with a JSONL audit trail of every decision.
Before you install.
- Linux: the sandlock engine binary (>= 0.8.x) on PATH.
- macOS: the sandlock engine binary (>= 0.8.x) on PATH.
Put it to work.
Use the Pro archive from your purchase. The Pro or Team bundle includes its Pi extensions. An individual module archive uses the same installer.
Choose a file to build your exact command.
Run this command from the folder containing the archive. Selecting a file here does not install or execute anything.
Activate your license with /bastille-license refresh inside Pi. Activation and periodic entitlement validation contact Polar. Your workload is not uploaded to Bastille-C3.
Full installation & activation guide →In use.
Inside Pi
/sandlockInside Pi
/sandlock-profileInside Pi
/sandlock-tierInside Pi
/sandlock-learnInside Pi
/sandlock-auditProfiles live in ~/.pi/agent/extensions/pi-sandlock/profiles/. Active profile and tier persist in extensions/pi-sandlock/state.json; projects can ship their own .pi/sandlock.json config.
Worth knowing.
- Requires a valid Polar license.
Remove this module
Uninstall this extension
pi uninstall npm:@bastilleworks/pi-sandlockRemoving an extension does not cancel your subscription. Manage renewal separately.
On the same ground