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.
11 lines
152 B
Nix
11 lines
152 B
Nix
{
|
|
imports = [
|
|
./hermes-agent.nix
|
|
./herdr-sandbox.nix
|
|
./hermes-dashboard.nix
|
|
./ai-memory.nix
|
|
./netbird.nix
|
|
./t3code.nix
|
|
];
|
|
}
|