Poll PositionLook before you build

Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.

Drop

Rootless Linux sandbox modelled on virtualenv: disposable environments that reuse your existing distro, hide your real home and secrets, and block localhost services, with optional gVisor.

droprun.sh/Active

v0.3.1 released 2026-10-09; repo pushed 2026-10-23. Show HN 2026 (193 points). (checked 2026-10-25)

In Agent guardrails

Where it stands apart

What it shares with most of the community

Nearest neighbors

Every answer

QuestionAnswerSource
Is it actively maintained?activesource
2026-10-25
How is the main thing licensed?permissive open source (MIT/Apache/BSD)
Apache-2.0
source
2026-10-25
How is it mainly sustained?stands apart individual side project, no revenue
Copyright Jan Wrobel; free Apache-2.0 tool; no pricing, sponsors or company found.
source
2026-10-26
Can it run entirely on your own device or infrastructure, without the maker's servers?yessource
2026-10-25
Do you need an account to use it?no account
Local rootless Linux tool installed and run on your machine; no account mentioned.
source
2026-10-26
Who is it for?developerssource
2026-10-25
Which shared standard or format does it mainly build on?stands apart OS sandbox primitives (Seatbelt, bubblewrap, Linux namespaces, seccomp)
Rootless Linux namespaces (optional gVisor); own TOML config.
source
2026-10-26
Where does it mainly step in?at the OS or VM boundary (sandbox, container, syscall supervisor)source
2026-10-25
What mainly decides whether an action is allowed?rules, policy, or boundaries written in advance
TOML config of exposed files, dirs and local services.
source
2026-10-25
If the guard itself breaks, is missing, or cannot decide, what happens by default?fails closed: the action does not run
The agent is started inside the sandbox; nothing outside it to bypass.
source
2026-10-25
Which agents does it work with?any agent or process (not limited to a named list)source
2026-10-25
In the default setup, where does the agent's work actually execute?in a local VM, container, or OS sandboxsource
2026-10-25
What is the main thing it protects?the developer's machine and files
'A hallucinated rm -rf ~ doesn't touch your actual home dir.'
source
2026-10-25
Does it keep a record of agent actions?no, or not a focussource
2026-10-25
Does it control the agent's outbound network access?stands apart yes, but open by default or optional
Blocks localhost services by default; public internet stays reachable.
source
2026-10-25
What is it mainly for?letting agents run with fewer approvals, safely
'Run agents with --dangerously-skip-permissions and let Drop enforce permissions at the OS level.'
source
2026-10-25
Is enforcement kept out of the agent's reach?yes, enforced in code or infrastructure the agent cannot changesource
2026-10-25

Sources

This page was derived from:

RSS for this project

Are you a maintainer? Claiming and correcting projects is coming soon.