Three-lane agent setup (interactive cockpit / autonomous workers / Hermes control lane): T3 Code server on m3-hermes as a systemd service under the m3tam3re user — reachable only from the NetBird mesh via direct pairing (no T3 Connect cloud relay).
Changes
hosts/m3-hermes/services/t3code.nix (new): t3 serve --host 0.0.0.0 on port 3773, User=m3tam3re, claude-code/opencode2 in system packages + service PATH
hosts/common/ports.nix: t3code = 3773
fixai-memory.nix + hermes-dashboard.nix: netbirdRange 100.64.0.0/16 → 100.81.0.0/16 — the fleet mesh actually runs in 100.81.0.0/16 (verified via wt0 kernel route + peer list); the old rules never matched any real peer
Auth model (updated)
Subscription logins live in each harness's own credential store on m3-hermes — no gateway/shared-key routing (providers don't allow subscription auth through other tools; the keyless m3ta-gateway stays herdr-worker-only):
sudo -u m3tam3re claude auth login
sudo -u m3tam3re opencode auth login
Validation
✅ alejandra clean
✅ Full m3-hermes eval passes — unit-t3code.service.drv generated in store with correct inputs (t3code-0.1.5, claude-code-2.1.314, git-2.56.0)
⚠️ Full toplevel build NOT completed on-VM (VM was overloaded by an earlier full build — deliberately not retried locally). Recommend colmena build in CI/before deploy.
One-time steps after deploy (documented in module header)
sudo -u m3tam3re claude auth login (persists in ~/.claude)
sudo -u m3tam3re opencode auth login
t3 pair or grab pairing URL from journalctl -u t3code → add environment in T3 desktop/mobile app
Security
Port 3773 mesh-only (same posture as ai-memory/hermes-dashboard). No cloud relay, no new secrets needed.
## What
Three-lane agent setup (interactive cockpit / autonomous workers / Hermes control lane): **T3 Code server** on m3-hermes as a systemd service under the m3tam3re user — reachable only from the NetBird mesh via direct pairing (no T3 Connect cloud relay).
## Changes
- `hosts/m3-hermes/services/t3code.nix` (new): `t3 serve --host 0.0.0.0` on port 3773, User=m3tam3re, claude-code/opencode2 in system packages + service PATH
- `hosts/common/ports.nix`: t3code = 3773
- **fix** `ai-memory.nix` + `hermes-dashboard.nix`: netbirdRange 100.64.0.0/16 → **100.81.0.0/16** — the fleet mesh actually runs in 100.81.0.0/16 (verified via wt0 kernel route + peer list); the old rules never matched any real peer
## Auth model (updated)
Subscription logins live in each harness's own credential store on m3-hermes — **no gateway/shared-key routing** (providers don't allow subscription auth through other tools; the keyless m3ta-gateway stays herdr-worker-only):
- `sudo -u m3tam3re claude auth login`
- `sudo -u m3tam3re opencode auth login`
## Validation
- ✅ alejandra clean
- ✅ Full m3-hermes eval passes — unit-t3code.service.drv generated in store with correct inputs (t3code-0.1.5, claude-code-2.1.314, git-2.56.0)
- ⚠️ Full toplevel build NOT completed on-VM (VM was overloaded by an earlier full build — deliberately not retried locally). Recommend colmena build in CI/before deploy.
## One-time steps after deploy (documented in module header)
1. `sudo -u m3tam3re claude auth login` (persists in ~/.claude)
2. `sudo -u m3tam3re opencode auth login`
3. `t3 pair` or grab pairing URL from `journalctl -u t3code` → add environment in T3 desktop/mobile app
## Security
Port 3773 mesh-only (same posture as ai-memory/hermes-dashboard). No cloud relay, no new secrets needed.
Three-lane agent setup (interactive cockpit / autonomous workers / Hermes
control lane): T3 Code server runs on m3-hermes as a systemd service under
the m3tam3re user, reachable only from the NetBird mesh (direct pairing,
no T3 Connect cloud relay).
- hosts/m3-hermes/services/t3code.nix: t3 serve on port 3773 (port
registry), User=m3tam3re, keyless m3ta-gateway opencode config for
harnesses, claude-code/opencode2 in service PATH
- ports.nix: t3code = 3773
- fix netbirdRange in ai-memory.nix + hermes-dashboard.nix: the fleet
mesh actually runs in 100.81.0.0/16 (wt0 kernel route), the previous
100.64.0.0/16 rules never matched any real peer
One-time steps after deploy (documented in the module header):
sudo -u m3tam3re claude auth login; t3 pair for client devices.
Subscription auth (Claude Code, OpenCode) must live in each harness's own
credential store; providers do not allow routing subscriptions through
other tools. The keyless m3ta-gateway stays herdr-worker-only. Both
harnesses now login interactively once after deploy (see module header).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Three-lane agent setup (interactive cockpit / autonomous workers / Hermes control lane): T3 Code server on m3-hermes as a systemd service under the m3tam3re user — reachable only from the NetBird mesh via direct pairing (no T3 Connect cloud relay).
Changes
hosts/m3-hermes/services/t3code.nix(new):t3 serve --host 0.0.0.0on port 3773, User=m3tam3re, claude-code/opencode2 in system packages + service PATHhosts/common/ports.nix: t3code = 3773ai-memory.nix+hermes-dashboard.nix: netbirdRange 100.64.0.0/16 → 100.81.0.0/16 — the fleet mesh actually runs in 100.81.0.0/16 (verified via wt0 kernel route + peer list); the old rules never matched any real peerAuth model (updated)
Subscription logins live in each harness's own credential store on m3-hermes — no gateway/shared-key routing (providers don't allow subscription auth through other tools; the keyless m3ta-gateway stays herdr-worker-only):
sudo -u m3tam3re claude auth loginsudo -u m3tam3re opencode auth loginValidation
One-time steps after deploy (documented in module header)
sudo -u m3tam3re claude auth login(persists in ~/.claude)sudo -u m3tam3re opencode auth logint3 pairor grab pairing URL fromjournalctl -u t3code→ add environment in T3 desktop/mobile appSecurity
Port 3773 mesh-only (same posture as ai-memory/hermes-dashboard). No cloud relay, no new secrets needed.