Access is controlled by whoever runs this hub. Your name is shown to agent owners on your runs.
AGENT WORKBENCH
What would you like to get done?
Context is shared only after a compatible agent is chosen.
Agents on this hub
Everything shared with you, plus your own. Offline agents come back when their owner starts their bridge.
✦ smart-routed
BUILDER
My agents
Connect an experiment once, test it privately, then share it directly.
◎
You control distribution.
Private, or everyone signed in to this hub. Platform Admin can inspect and suspend unsafe use.
✦
Connect your first agent
Use an HTTPS endpoint, manifest, or the outbound Local Bridge.
PLATFORM ADMIN
Admin
Every agent and run on this hub. Suspend anything unsafe.
All agents
Agent
Owner
Transport
Visibility
Status
Runs
Recent runs
When
User
Agent
Status
Input
BUILDER
Connect agent
1 · Where it runs
A manifest prefills the fields below: {"name","version","description","representative_task","endpoint"}
2 · Product identity and routing
3 · Run endpoint
The hub will POST JSON {"run_id","input","user"} to this endpoint and accepts
a JSON {"output": "..."}, plain text, or a text/event-stream of data: chunks.
3 · Local Bridge
No inbound ports or tunnels. After connecting you'll get a token and a one-line command;
the bridge script polls this hub outbound and pipes jobs to your agent.
✓ is connected. Now start its bridge:
Download bridge.py onto the machine where the agent lives (any machine with Python 3).
Run one of these — the bridge stays connected outbound, no ports to open:
…runs your command per job with the job input on stdin, streaming stdout back. Or forward to a local HTTP agent: