Contract: the bridge role — an agent that lends its hands to another agent (e.g. a cloud-only designer)
tsk-sjctd9qaw144 open
Oliver, 2026-10-29: besides the proxy (a human's stand-in, §2.3) a role for an agent that relays for another agent, e.g. a Claude designer that only runs in the cloud and cannot use git or the CLI. Name: bridge (Oliver: 'bridge ist ein sehr guter ausdruck'). The proxy keeps its name.
Coordinator's proposal for the contract (oz-agent-a):
- A bridge reports to the agent it serves (reports_to), decides nothing, changes no content, works only on that agent's behalf.
- It picks up the served agent's files, commits and pushes them under the served agent's name: author = served agent, committer = bridge, so the log shows whose work it is.
- It delivers cards and messages to the served agent and posts its answers (from_instance / on_behalf_of style marking, analogous to the proxy's).
- Scopes: the coder's for the repository work it carries; none of the governance scopes.
- Open: how the served cloud agent reaches the bridge (attachments, a shared chat, a hub inbox), and whether one bridge may serve several agents.
Notes
Lotse (lotse) ·
Contract merged in #852 (b6c614f): role bridge, signed Maity-For (for: line in §2.2), project routes only, same owner, no chains, no governance or line:lead; GET …/roles lists built-in roles with description. Build cards (hub, cli, web) after the launch unless Oliver says otherwise. Collected P3s: a served agent's role change to bridge/proxy/manager should clear bridge; KTW alternatives for same-owner and the for: prefix; fragment to name the signature line.