v0.3.0.4: Agent-hop swarm routing
·
1 commit
to fix/swarm-agent-hop-routing
since this release
0.3.0.4: Agent-hop swarm routing
Fixes multi-machine mesh routing so a gateway (Honcho, editors, or any OpenAI client) reaches peers via peer agent URLs (http://<LAN-IP>:11400/v1) instead of unreachable loopback oMLX rows from another host.
Fixes
- Agent-hop backends:
peer_agent_backends()emits one routable backend per LAN peer; gateways no longer merge peer127.0.0.1:8080URLs into the pool - Round-robin distribution:
round_robinalternates local inference and peer agent hops when the same model exists on multiple machines - Self-peer guard: config save,
peers --save, and dashboard peers-scan skip this host's ownlisten_urlinswarm.peers - mDNS LAN URL: wildcard bind (
0.0.0.0:11400) advertises LAN IP in status/heartbeat (existing behavior; regression test added)
Verify (two-machine LAN)
# Gateway — Honcho points here; routing.default_strategy = "round_robin"
./netllm serve --host 0.0.0.0
./netllm status # peer backend: http://<peer-LAN>:11400/v1
./netllm test --model <shared-model>
curl -s http://127.0.0.1:11400/metrics | rg netllm_requests_total
curl -s http://<peer-LAN-IP>:11400/metrics | rg netllm_requests_totalBoth metrics should increase when traffic round-robins across machines.
Docs
- honcho-integration.md: agent-hop diagram and metrics check
netllm-swarmskill: gateway +round_robinguidance
Previous release
- v0.3.0.3 notes: macOS swarm Settings QoL + web dashboard admin