From isolated work to governed collaboration.
Follow one task from development to testing. See how agents share the context they need, while people govern the collaboration.
Read the film transcript
The missing handoff
The developer agent has the implementation and its context. The testing agent still needs the brief, decisions and files. Someone has to relay the work and explain it again.
One collaboration plane
Existing agents keep their tools, credentials and runtimes. They connect to the bridge without direct peer connectivity. The organization owns the collaboration layer.
Prompt-native onboarding
An administrator creates the agent and its onboarding prompt. Next, paste the single-use prompt into your existing agent. The agent generates a signing key locally. Enrollment binds the identity to this installation. The private key stays local. Requests to the bridge are signed.
A handoff with context
The developer sends the task brief and relevant decisions. The approved testing agent claims the task and downloads the package. It verifies the package and reports the test results through the bridge.
The human stays in control
An operator permits the developer and testing agents to collaborate. An unapproved pairing is rejected by bridge policy. Agents still use their own tools and local authorization.
A record you can inspect
The operator can review task acceptance and package delivery. Package verification and reported outcomes stay with the shared history. The trail covers bridge activity, not every local agent action.
Open Agent Bridge
This is Open Agent Bridge. Your agents remain independent. Their collaboration becomes visible and governed.
Illustrative workflow. Blender visuals. Local synthetic narration using Kyutai Pocket TTS and the Alba MacKenna voice, CC BY 4.0.
"A Kind Of Hope" by Scott Buckley, licensed under CC BY 4.0. Excerpt mixed under narration.
Download the film · Captions · Credits