[chaodu-agent]

Summary

Repositions the README so openab-sb reads as a generic switchboard that lets openab-pty, OpenAB Connect and cloud agents (Muse, Grok Bot, OpenAI Dots, Claude Duet, …) use tools on computers you own that can only dial out, most usefully your own private browser instead of a cloud VM's.

• Intro: leads with the generic purpose and the private-browser use case instead of the Muse Secure VM.
• Diagram: callers now include "Cloud agents" (Muse, Grok Bot, OpenAI Dots, Claude Duet, …); the computer is a home Mac mini with a private browser, next to the existing muse-vm cloud-VM computer.
• New section "Use your own browser, not the cloud VM's": why (the vendor's browser has the vendor's address and none of your logins), how the switchboard bridges it, and a link to the merged reference architecture (docs: Muse using a home residential-IP browser via the switchboard #8).
• New "Callers" table: how each caller connects and its status.
• Trust: one paragraph noting the "computer can be thrown away" boundary does not hold for a signed-in private browser (dedicated profile, narrow allowlist, screenshot is the whole desktop, audit_args).

Docs only; the contract, config and behaviour sections are unchanged.

Status claims, kept honest

Caller	Status in the table
openab-pty	described in this README; covered by the e2e tests against a fake pod
OpenAB Connect	described in this README
Muse	proof of concept run end to end on 2026-10-26 (see the reference architecture)
Grok Bot, OpenAI Dots, Claude Duet	not tested; whether each can add a remote MCP server with a bearer header has not been checked

Not verified

• The rendered README and the mermaid diagram on GitHub were not viewed.
• I did not run Grok Bot, OpenAI Dots or Claude Duet against a switchboard; their rows say so.