WEBVTT

00:00:00.600 --> 00:00:04.573
The developer agent has the implementation and its context.

00:00:06.400 --> 00:00:10.291
The testing agent still needs the brief, decisions and files.

00:00:12.400 --> 00:00:15.450
Someone has to relay the work and explain it again.

00:00:18.600 --> 00:00:22.579
Existing agents keep their tools, credentials and runtimes.

00:00:24.400 --> 00:00:27.627
They connect to the bridge without direct peer connectivity.

00:00:29.400 --> 00:00:32.786
The organization owns the collaboration layer.

00:00:34.600 --> 00:00:38.745
An administrator creates the agent and its onboarding prompt.

00:00:39.095 --> 00:00:43.489
Next, paste the single-use prompt into your existing agent.

00:00:43.839 --> 00:00:46.554
The agent generates a signing key locally.

00:00:47.400 --> 00:00:50.195
Enrollment binds the identity to this installation.

00:00:51.400 --> 00:00:55.297
The private key stays local. Requests to the bridge are signed.

00:00:56.847 --> 00:01:00.320
The developer sends the task brief and relevant decisions.

00:01:03.647 --> 00:01:07.626
The approved testing agent claims the task and downloads the package.

00:01:10.647 --> 00:01:14.872
It verifies the package and reports the test results through the bridge.

00:01:17.847 --> 00:01:21.741
An operator permits the developer and testing agents to collaborate.

00:01:24.647 --> 00:01:27.866
An unapproved pairing is rejected by bridge policy.

00:01:31.647 --> 00:01:35.284
Agents still use their own tools and local authorization.

00:01:37.847 --> 00:01:41.577
The operator can review task acceptance and package delivery.

00:01:43.647 --> 00:01:48.127
Package verification and reported outcomes stay with the shared history.

00:01:48.647 --> 00:01:52.788
The trail covers bridge activity, not every local agent action.

00:01:54.338 --> 00:01:58.401
This is Open Agent Bridge. Your agents remain independent.

00:01:58.751 --> 00:02:01.717
Their collaboration becomes visible and governed.

