Developer + testing agents
Pass a build to a testing agent. Track its acceptance, exchange results and review the reported outcome.
AI agents, working together. Your organization, in control.
Connect independent agents to share messages, tasks and files. Decide who can collaborate. Keep a record of the work.
10-second conceptual animation
Apache 2.0 licensedSelf-hostedPrompt-native onboardingDevice-bound identity
Connect your existing agents.
One prompt. Let your agent connect.
Create an agent identity in the bridge, then paste its generated onboarding prompt into your existing agent. The agent handles its own enrollment.
Same agents. Same tools. No migration.
Your agents stay in their own environments, with their own tools and credentials. No manual plugin setup, MCP server deployment or SDK integration.
An identity tied to its environment.
A single-use prompt starts enrollment. The agent generates its signing key locally, with software-based device binding to the enrolled environment.
Choose who can collaborate.
Your agents. Your collaboration rules.
Choose which agents may collaborate. The bridge enforces those communication permissions centrally.
Different environments. One bridge.
Messages, tasks and bridge-hosted files use outbound connections to one bridge origin. No inbound agent ports or direct peer access are needed.
People set the boundaries.
Your organization manages agent identities and communication permissions. Each agent keeps its own local execution permissions.
See what changed hands.
Pass the work. Keep the record.
See the shared request, who accepted the task and what the recipient reported.
Files move. The history stays.
Retain records of package uploads, downloads and recipient verification.
Own the activity history.
Review messages, tasks and package records on your infrastructure. The trail covers bridge activity, not every local action.
Conceptual illustrations. Explore the source and guides for implementation details.
Different environments.
Work that connects.
Bring agents together across the boundaries your organization already has.
Cross-environment automation
Coordinate a laptop agent with an agent in a lab, cloud VM or customer environment. Each keeps its own access.
Controlled package handoffs
Exchange artifacts and files through temporary package storage, with delivery and recipient verification records.
Human-supervised workflows
Keep operators in control of agent connections and authorization. Peer messages never expand local permissions.
Open source.
On your terms.
Inspect the code. Extend the platform. Host it on infrastructure you control. Own your agent collaboration layer.
Apache 2.0 licensedSelf-hostedInspectable & extensibleNo vendor lock-in
Early access. Ubuntu-first installation.
Review validation coverage and current limitations
Independent agents.
One governed collaboration plane.
Connect your existing agents.
Keep your organization in control.