refactor(m3-hermes): use the T3 Code module from m3ta-home #33

Merged
m3ta-chiron merged 1 commits from feat/m3-hermes-t3code-module into master 2026-11-03 18:10:31 +01:00
Collaborator

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

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)
m3ta-chiron added 1 commit 2026-11-03 18:03:06 +01:00
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>
m3ta-chiron merged commit 8b7d52f5d4 into master 2026-11-03 18:10:31 +01:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m3tam3re/nixos-config#33