roost bridge

Lets a Claude running in roost look at and use this browser — with your consent, once per Claude session.

roost bridge connects your browser to roost, so the Claude coding agent running in a roost terminal on your server can work in the Chrome you are actually logged into, not in a headless browser that sees none of your accounts. What it is for roost runs your long-lived coding sessions on a server and shows them in a browser tab. A Claude working there can change code and run tests, but it cannot see the staging site behind your SSO, the admin page you are logged into, or the bug you are looking at right now. roost bridge closes that gap. Claude can ask your browser to: • list your open tabs • open a page (in a "Claude" tab group in your window) and close the ones it opened • read a page: its text, and numbered references to its links, buttons and inputs • click, type and fill file inputs • take a screenshot of what is visible • read the page's console messages and errors Typical uses: "open staging and check that the checkout still works", "look at the error in the console after I click Save", "screenshot the dashboard and compare it with the design". You stay in control • Nothing happens until you allow it. The first request from each Claude session opens a window that shows which roost, project and terminal is asking and what it wants to do. You choose Allow for this session, Allow once, or Deny. No answer means Deny. • Allowed sessions are listed in the toolbar button and can be revoked at any time. Every grant ends when Chrome restarts. • Sites on your deny-list are never driven. Neither are Chrome's own pages, the Chrome Web Store, or roost itself. • Calls are accepted only from roost addresses you add, and only when they are signed with a key that your own roost server generates. • Unsafe mode, which allows everything without asking, is off by default. The toolbar badge shows !! whenever it is on. The other direction • Right-click any page to send it, the selected text or a screenshot to your roost Claude's prompt. • Each roost project has a simple handoff page where another browser agent, such as Claude in Chrome, can exchange messages with the Claude in your roost. Privacy roost bridge talks only to the roost server you configure, which is your own. It sends nothing to the developers or to anyone else, and contains no analytics, tracking or remote code. Setup roost bridge needs roost 0.8.0 or later on your server (https://github.com/PeterKnego/roost). On the roost host, register the tools once: claude mcp add -s user roost -- roost mcp Run roost browser-key there and paste the key into this extension's options. Add your roost address in the options, then open roost in a tab. Full guide: https://github.com/PeterKnego/roost/blob/master/extension/README.md