Boundary Release Checklist

**Remaining tasks**:

- [ ] Few times I noticed some MCP related errors in Coder Tasks environment, is it related to boundary? Is it reproducible?
- [ ] Should proxy follow redirects?
- [ ] Real-Time configuration updates? Without necessity to rebuild workspace.
- [ ] Why boundary fails on `sudo apt-get update`? Some certs are missing?

---

- [X] ~~Fix overrides in claude-code module~~ - Moved to [https://github.com/coder/boundary/issues/140]()
- [ ] Investigate weird errors in coder-task logs
- [ ] Investigate injection of certs in HTTP Proxy (customers had issues with that)
- [X] ~~base image should include ip tool~~

---

- [ ] Fix GetUserInfo + CertPath method
- [ ] Prototype boundary with no permission/Slirp4netns

**PRs to merge**:

- [X] [https://github.com/coder/boundary/pull/70]()
- [X] [https://github.com/coder/registry/pull/455]()

**Release checklist**:

- [X] Make `--dangerously-skip-permissions` work with `cap_net_admin` @evgeniy-scherbina
- [https://github.com/coder/boundary/issues/73]()
- [X] Move changes to `Write Coder On Coder` template. Should it be done directly in UI or via github PR? @evgeniy-scherbina
- [X] Make `proxy_port` configurable in claude-code module @evgeniy-scherbina
- [X] Make `log-level` configurable via claude-code module? Default is WARN. @evgeniy-scherbina
- [X] Make `boundary_version` configurable in claude-code module @evgeniy-scherbina
- [X] Optionally run profiler on boundary, and double check that new proxy doesn't have any memory/goroutine leaks. @evgeniy-scherbina
- [https://github.com/coder/boundary/issues/74]()
- [X] Make a decision how boundary should be installed in claude-code module. Use `coder exp boundary` vs directly install and use `boundary`. Coder exp boundary works out of the box, but it's very inconvenient and slow to develop, because after every change to boundary source code - we need to update version in coder/coder repo and wait for CI to finish.
- [X] Update documentation:
- [X] github repo readme
- [X] coder docs
- [X] Take a look at `--allowed-hosts`, is it safe to run `agentapi server --allowed-hosts="*"`?
- [X] Is it safe to run chain of 4 processes: `agentapi -> boundary (parent) -> boundary (child) -> claude`. Doesn't it interfere with `agentapi -> claude` communication?

Command: `agentapi server --allowed-hosts="*" --type claude --term-width 67 --term-height 1190 -- sudo -E env PATH=$PATH setpriv --inh-caps=+net_admin --ambient-caps=+net_admin --bounding-set=+net_admin /home/coder/go/bin/boundary "${BOUNDARY_ARGS[@]}" -- claude "${ARGS[@]}"`
- [X] Make a decision about `allow-rules` formatting, related tasks: @bcpeinhardt
- [X] [https://github.com/coder/boundary/issues/44]()
- [X] [https://github.com/coder/boundary/issues/50]()
- [X] Check this command: `sudo -E env PATH=$PATH setpriv --inh-caps=+net_admin --ambient-caps=+net_admin --bounding-set=+net_admin`. Is it safe: `sudo -E env PATH=$PATH`? Do we need all perms: `inh-caps, ambient-caps, bounding-set`?
- [X] Try to use `setcap` instead of `setpriv`?

**Future tasks**:

- [X] remove unprivileged jail (confirm with product)?
- [X] remove macos support (confirm with product)?
- [X] ~~Sometimes, if boundary completes with error, it doesn't make cleanup, and then I had to manually run:~~~~
~~`~~ip link show~~`~~
~~`~~ip -o link show | awk -F': ' '{print $2}' | grep '^veth_h' | cut -d'@' -f1 | xargs -r -n1 sudo ip link delete~~`~~
~~ ~~we should make sure clean up is always executed (network interfaces are removed, iptables rules are removed).~~
- [X] \~\~refactor e2e tests: [https://github.com/coder/boundary/blob/main/e2e_tests/boundary_integration_test.go\~\~]()
- [X] ~~add e2e tests to test behaviour with claude?~~
- [X] ~~add e2e tests to test behaviour with claude and agentapi?~~
- [X] ~~add tests for proxy to test behaviour when golang client uses ALPN to upgrade to HTTP 2?~~
- [X] Install boundary with install script in claude-code test module? `curl -fsSL https://raw.githubusercontent.com/coder/boundary/main/install.sh | bash`
- [X] Rethink arch. about 1 port?