fence

Lightweight, container-free sandbox for running commands with network and filesystem restrictions

Could not verifysource: GitHubhomepageGoApache-2.0commit 737751a82b49

Go, Apache-2.0 licensed. The project labels itself: bubblewrap, code security, coding agent, landlock, sandbox, seatbelt, seccomp and socat.

Argusic could not get fence running. An Argusic agent installed it in 10 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Fence builds, runs, and all unit tests pass; sandbox/integration tests fail because the container kernel does not support user namespaces required by bubblewrap

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 50 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
50 / 100
cost of the verifying run
$0.11 (measured)
recorded runs
2
last tested
stars
1,025
forks
44
open issues
42
watchers
4
size
2 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing fence, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • bwrap: kernel does not allow non-privileged user namespaces — all sandbox integration tests fail5 minutes
  • Go not pre-installed; had to download Go 1.26.0 and set PATH3 minutes
  • bubblewrap (bwrap) not found; required for Linux sandboxing2 minutes
  • socat not found; required for network bridging2 minutes
Install time
10 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
go build -o fence ./cmd/fence exited 0 producing 13MB binary; ./fence --help prints full usage text; go test -run 'TestCheck|TestWrap|TestPath|TestDangerous|TestMerge|TestLoad|TestURL|TestSSH|TestHooks' ./... all 11 packages PASS; go test ./internal/sandbox, FAIL (integration tests require bwrap+user-namespace)
Model tokens used
358,528
Exact commit tested
737751a82b49
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

ok    github.com/fencesandbox/fence/internal/toolcall  0.003s [no tests to run]
ok    github.com/fencesandbox/fence/pkg/fence  0.004s
?     github.com/fencesandbox/fence/tools/generate-config-schema  [no test files]
Now I have a complete picture. Here's the final assessment:
**Install**: Go was not pre-installed — downloaded and extracted Go 1.26.0 to `/home/runner/go/bin`…
**Tests**: 11 packages pass (all unit tests across `config`, `proxy`, `bridge`, `templates`, `toolc…
2026-10-11T13:34:43.187472Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
tokens used
358,528
Now I have a complete picture. Here's the final assessment:
**Install**: Go was not pre-installed — downloaded and extracted Go 1.26.0 to `/home/runner/go/bin`…
**Tests**: 11 packages pass (all unit tests across `config`, `proxy`, `bridge`, `templates`, `toolc…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 10 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.08
Argusic Runner1/3Unverified80.000.11

Topics (from GitHub)

bubblewrapcode-securitycoding-agentlandlocksandboxseatbeltseccompsocat

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/fence.svg)](https://argusic.com/subject/fence)

Questions

Does fence run?
Argusic could not verify that fence runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test fence?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 737751a82b49. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test fence?
The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does fence take to install?
10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does fence need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing fence?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for fence?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion