Blocks outside project writes on Linux

Block agent writes outside your project

For developers running local coding agents who need lasting project changes listed for review.

Opens a completed sample run with a blocked write and receipt.

01 / SAMPLE RUN

See the blocked write and receipt

The bundled demo uses a temporary sample project. It leaves your current project unchanged.

awb demoENFORCED

$ awb demo
BLOCKED  ../blocked-agent.conf
CREATED  target/config.pyc
MODIFIED src/config.rs
DELETED  obsolete.txt
RECEIPT  write-receipt.json

02 / RECEIPT COVERAGE

AWB compares watched paths before and after a run. The receipt includes ignored files and Git metadata.

watched_paths

git diffAWB receipt

src/auth.tsmodifiedmodified

target/cache.pycignoredcreated

.git/hooks/pre-commitnot listedmodified

03 / HOW IT WORKS

Landlock applies the write boundary. Snapshots compare lasting changes only in watched paths.

01
Choose paths
Set allowed paths for writes and watched paths for the receipt.
"allow_write": ["."]
02
Run the agent
Put the local agent command after --. Child processes inherit the boundary.
awb run -- claude
03
Review the receipt
Inspect created, modified, and deleted paths with content and metadata hashes.
awb inspect .awb/…

04 / INSTALL

Build the MIT-licensed CLI from its source repository.

Enforced: Landlock ABI 3 or newer

cargo install --git https://github.com/B-Divyesh/sf-agent-write-barrier

cd your-project
awb init
awb check
awb run -- claude

05 / LIMITS AND PRIVACY

Supported Linux
The 15-case test blocks writes outside allowed paths under Landlock.
Not a full sandbox
AWB does not isolate networks, processes, devices, open file descriptors, or kernel flaws.
Visible fallback
AWB fails closed without enforcement. Explicit audit mode labels receipts and cannot block writes.

The CLI has no telemetry. The site uses no analytics or third-party runtime files. Read the privacy details.