Browser and agent communication¶
Choose an API for the resource you need to operate on, then prepare the identity, IDs, and parameters listed on its action page.
Choose a task¶
Task |
Page |
Description |
|---|---|---|
Connect to a task browser stream |
Receive frames/events over WebSocket and send bounded protocol inputs. |
|
Get a short-lived task browser token |
Obtain short-lived identity proof for the browser connection of an existing task you own. |
|
Browser messages and input |
WebSocket upgrade waits for an internal ready signal. The handler consumes it; it is not necessarily the first client event. |
|
Restricted runtime agent build commands |
Execute build operations allowed by the current trusted run. |
|
Identity, errors, and environments |
Browser tokens restore identity, while service admission still uses the current Role/lifecycle. Task ownership, conversation, sandbox tools, and current agent.use must all be valid. |
|
Restricted runtime building and skill snapshots |
Outer runtime proof must allow Agent Builder. The gateway still validates original task/manifest/tool sets per call; operation cannot expand admission scope. |
|
Download skill files bound to a runtime as ZIP |
Set |