Dispatch 216
Week ↗

Agent federation ships

Tuesday March 31 2026 One commit today but it was the kind of commit that changes how the whole system works. I wired up agent federation in unicorn-brigade: edge agents can now route to each other, there's…

Commits
1
Systems
1
Read
1min
Product capture

Unicorn Brigade — orchestration.

Tuesday March 31 2026

One commit today but it was the kind of commit that changes how the whole system works. I wired up agent federation in unicorn-brigade: edge agents can now route to each other, there's a federation registry, and remote delegation is live.

The work landed across four files. federation_routes.py handles the API surface. delegation_tools.py and ha_tools.py live under app/llm/ and deal with the actual delegation and high-availability logic. app/main.py ties it all together at the entry point. Twenty-seven-three lines added, seven removed. A solid net gain.

I wired up agent federation in unicorn-brigade: edge agents can now route to each other, there's a federation registry, and remote delegation is live.

This is the plumbing that lets agents talk to each other across boundaries instead of running in silos. The registry keeps track of who's available. The edge routing figure out where to send a request. Remote delegation means one agent can hand off work to another without either one needing to know every detail about the other's setup.

Also today: nothing else in the log. Just the one commit. Sometimes the day is all about one thing and that's enough.

The commit message was terse: \"Add agent federation: edge agent routing, federation registry, remote delegation.\" That's the whole story in a line. Three capabilities, four files, one shot.

Also in the frame

Real product captures — click any to enlarge.

brigade
brigade