I m Sean, the builder behind NextEleven and DeadBolt. I d like to hear from developers about the hardest part of adding execution controls to an agent they already use.
DeadBolt puts a permission check at the tool boundary. A trusted executor checks the gate and starts the protected action only after a fresh explicit allow. You can build it in with Rust, or bolt it on through a local HTTP sidecar or trusted stdio MCP proxy. It is free and open source under Apache-2.0.
The boundary matters: it protects the routes you connect to it. It is not a whole-agent sandbox and cannot cancel an action already running.
The first evaluation uses harmless temporary files and needs no AI account. The captioned walkthrough shows it inside Harness.
I built DeadBolt because I wanted a concrete place to enforce permission immediately before an agent's tool call changes something.
The trusted executor checks the gate and starts the protected action only after a fresh explicit allow. Build it in with Rust or bolt on a local HTTP sidecar or trusted stdio MCP proxy. It is free under Apache-2.0.
Stable update, October 12: DeadBolt 2.0.0 is now published. It provides fixed run deadlines, optional supervisor-only liveness, separated credentials, exact-action approval in trusted integrations and readable MCP denial reasons. Conflicting recognized destinations are refused, and startup against a damaged existing store fails closed. Native downloads, the matching Python client, Homebrew and the MCP bundle are available. The Rust package is also published on crates.io as n11-deadbolt 2.0.0; install the CLI with cargo install n11-deadbolt --version 2.0.0 --locked.
Release, checksums and qualification: https://github.com/seanebones-lang/deadbolt/releases/tag/v2.0.0
Stable editor setup: https://seanebones-lang.github.io/deadbolt/editors-v2.html
Installed protocol/effect checks cover four published targets. Prior RC3 receipts include coworker-operated Linux tests and actual Cursor model calls on one macOS ARM64 host; those candidate receipts are separate from stable-byte tests and are not certification. The first local evaluation needs no AI account. If you try it, share your OS, client, version, expected result and actual result.
2.0.0 is our baseline through October 19. We'll review feedback weekly and validate fixes before publishing. You may use, fork and modify it under Apache-2.0, including commercially, subject to its terms. Useful tested contributions are welcome for review and possible inclusion.
DeadBolt protects connected routes, not the whole agent; it cannot cancel an action already running or enforce OS network isolation. The captioned videos show actual Harness dispatch with a deterministic local demo provider. They were recorded October 10; use current guides for installation. Narration is AI-generated.
Built by NextEleven.