Built with WordPress, hosted on Fastly. Domain registered in 2026.
agentbondage.org is built with WordPress, hosted on Fastly.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 9 Nov 2026 | |
| WordPress Plugins1 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| – | 9 Nov 2026 | |
| CDN & Hosting3 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
From what the site says about itself, and account IDs it shares with other sites.
ns1djs.name.comns3dgr.name.comns2fln.name.comns4fmx.name.comUser-agent: GPTBot Allow: / User-agent: OAI-SearchBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: CCBot Allow: / User-agent: * Allow: / Sitemap: https://agentbondage.org/sitemap.xml
# Bondage
> A local C launcher for coding agents that verifies exact artifacts, optionally releases secrets with envchain-xtra, optionally sandboxes with nono, and keeps shell logic out of the trust boundary.
## What it is
Bondage exists because coding agents should not run loose with live keys, weak dependency provenance, and broad ambient environment access. It verifies exact absolute paths and exact hashes, optionally releases secrets through envchain-xtra, optionally applies nono sandbox profiles, and then execs the exact target.
## Trust anchors
- The operating system remains the strongest available layer for secret storage and signing identity.
- Keychain is the preferred secret store when envchain-xtra is used.
- Signing identity, where available, is useful as an approval and drift signal.
- Bondage should trust exact artifacts, not a shell alias or mutable PATH result.
## What it does not solve
- It does not make a bad npm tree trustworthy.
- It does not fix host compromise before launch.
- It does not override human mistakes about what should get secrets.
## Install
```sh
brew tap nvk/tap
brew install nvk/tap/agent-bondage
brew install nvk/tap/envchain-xtra
```
## Core docs
- Homepage: https://agentbondage.org/
- Full LLM reference: https://agentbondage.org/llms-full.txt
- Source: https://github.com/nvk/bondage
- Getting Started: https://github.com/nvk/bondage/blob/main/GETTING_STARTED.md
- Trust Model: https://github.com/nvk/bondage/blob/main/TRUST_MODEL.md
- envchain-xtra: https://github.com/nvk/envchain-xtra
- Homebrew tap: https://github.com/nvk/homebrew-tap
## Key facts
- Maintainer: https://github.com/nvk
- Language: C
- Current launcher baseline: agent-bondage / bondage 0.3.1
- Current secret-release baseline: envchain-xtra 1.4.1
- Current sandbox baseline: nono 0.80.0
- Registry-managed Nono packs are independent dependencies; update only packs the selected profile extends and validate them with the installed Nono version
- Companion secret layer: envchain-xtra
- Optional sandbox layer: nono
- Batch repair: `bondage repair` shows pending repins as one plan, requires a typed yes on a TTY, refuses non-interactive use and same-version fingerprint changes
- GPU gate: `nono_allow_gpu = true` emits Nono's explicit `--allow-gpu` request while the selected Nono profile remains the authorization gate
- Sandbox-aware doctor: inaccessible paths are reported as incomplete and never receive false repin suggestions
- Intended trust chain: `shell name -> bondage -> [envchain-xtra] -> [nono] -> exact target`
- Hook rule: sandbox denials should be fixed in managed profiles and launcher config. Agent-visible hook output is prompt surface, so keep hook diagnostics factual and short; do not inject repair workflows into the transcript.
## Upgrade checks
After package-manager upgrades, use portable variables and avoid publishing local usernames or project paths:
```sh
export BONDAGE_CONF="${BONDAGE_CONF:-$HOME/.config/bondage/bondage.conf}"
export NONO_PROFILE="${NONO_PROFILE:-codex}"
brew upgrade nono
brew cleanup nono
bondage --config "$BONDAGE_CONF" repair
nono outdated
nono update --dry-run
nono profile show "$NONO_PROFILE" >/dev/null
bondage --config "$BONDAGE_CONF" verify codex
nono why --profile "$NONO_PROFILE" --path "$HOME/.ssh" --op read
nono why --profile "$NONO_PROFILE" --path "$HOME/.config/nono/profiles" --op write
nono why --profile "$NONO_PROFILE" --path "$HOME/.config/nono/profile-drafts" --op write
```
| – |
| 9 Nov 2026 |
| – | 9 Nov 2026 |