Replaces the hand-written t3code service on m3-hermes with m3ta.t3code from m3ta-home, as already done on m3-kratos.
Binds the current NetBird address of wt0 instead of 0.0.0.0, so t3 pair prints a URL mesh peers can reach.
Opens 3773 via networking.firewall.interfaces.wt0 instead of the ip46tables rules in extraCommands.
Restarts with NetBird (the service is bound to the wt0 device), so running sessions drop when NetBird restarts.
The agent runtime stays in the host file: agent-lib sync, Claude skills mirror, Gitea SSH config, known hosts. The harnesses, git, openssh and beads come from systemPackages, which the module puts on the service PATH via /run/current-system/sw.
Verified: m3-hermes evaluates; ExecStart, bindsTo/wantedBy on wt0 and the wt0 firewall port evaluate as expected; no 3773 rule left in extraCommands. Not yet deployed.
After deploy: if wt0 is already up, run systemctl start t3code once (the module's unit is wanted by the device).
Replaces the hand-written `t3code` service on m3-hermes with `m3ta.t3code` from m3ta-home, as already done on m3-kratos.
- Binds the current NetBird address of `wt0` instead of `0.0.0.0`, so `t3 pair` prints a URL mesh peers can reach.
- Opens 3773 via `networking.firewall.interfaces.wt0` instead of the `ip46tables` rules in `extraCommands`.
- Restarts with NetBird (the service is bound to the `wt0` device), so running sessions drop when NetBird restarts.
The agent runtime stays in the host file: agent-lib sync, Claude skills mirror, Gitea SSH config, known hosts. The harnesses, git, openssh and beads come from `systemPackages`, which the module puts on the service `PATH` via `/run/current-system/sw`.
Verified: m3-hermes evaluates; `ExecStart`, `bindsTo`/`wantedBy` on `wt0` and the `wt0` firewall port evaluate as expected; no 3773 rule left in `extraCommands`. Not yet deployed.
After deploy: if `wt0` is already up, run `systemctl start t3code` once (the module's unit is wanted by the device).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The server now binds the NetBird address of wt0 instead of 0.0.0.0, so
the pairing URL is reachable from mesh peers, and the port opens on wt0
via the module instead of hand-written ip46tables rules. The agent
runtime (agent-lib sync, Claude skills, Gitea SSH) stays host-specific.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Replaces the hand-written
t3codeservice on m3-hermes withm3ta.t3codefrom m3ta-home, as already done on m3-kratos.wt0instead of0.0.0.0, sot3 pairprints a URL mesh peers can reach.networking.firewall.interfaces.wt0instead of theip46tablesrules inextraCommands.wt0device), so running sessions drop when NetBird restarts.The agent runtime stays in the host file: agent-lib sync, Claude skills mirror, Gitea SSH config, known hosts. The harnesses, git, openssh and beads come from
systemPackages, which the module puts on the servicePATHvia/run/current-system/sw.Verified: m3-hermes evaluates;
ExecStart,bindsTo/wantedByonwt0and thewt0firewall port evaluate as expected; no 3773 rule left inextraCommands. Not yet deployed.After deploy: if
wt0is already up, runsystemctl start t3codeonce (the module's unit is wanted by the device).🤖 Generated with Claude Code