I made the network feel like one working surface
My agent environment is spread across a Windows workstation, a mainframe, a Mac, and services that live behind WireGuard. Before Bridge, each surface had its own address, process list, and tool inventory. The hard part was not starting another agent. It was knowing where the useful agent lived, what it could do, and which machine should receive the work.
Bridge is the control plane for that environment. From any WireGuard-connected device, I can open one browser surface that understands the registry, the reachable hosts, and the state of the work moving through them. It is designed so a phone or tablet can be the place I inspect a run, choose an agent, and send the next piece of work without sitting at the machine that hosts the process.
That is network control in the operational sense: one authenticated mesh, one view of the machines and services I operate, and one place to dispatch work. It is not an unrestricted network administration panel. Access remains scoped by the WireGuard mesh and the capabilities of each upstream service.
I separated the control plane from the agents themselves
The browser shell does not try to become another agent runtime. A Node sidecar scans the local Claude registries and exposes a small JSON contract. The React grid renders that contract, while a Rust terminal client reads the same shape. That boundary means a discovery feature does not need to be rebuilt three times, and the terminal surface can remain useful when a browser is not.
The registry currently covers agents, skills, commands, and MCP tools. The shell also has a place for network services and embedded operational widgets. That lets Bridge grow from an index into a dispatch surface without coupling the dashboard to every service it can reach.
I made discovery the first reliable action
The MVP answers the first question I ask when I sit down: what can I use here? It indexes more than 169 skills and dozens of agents, shows their purpose and source, and keeps the browser and TUI on a shared contract. Session management is already represented in the workspace. Launchers, project switching, KOPENG search, attention queues, and the server grid are the next layers of the control plane.
Bridge is still in progress. The shipped value is the network-aware workspace boundary and the registry contract. The broader promise, dispatching and supervising work from any connected device, is the direction the remaining widgets are built to complete.