Sunflower Browser Bridge

Let your Sunflower agents use approved Chrome tabs through your Sunflower account.

Give your agents access to your Chrome browser, with your approval. Sunflower Browser Bridge connects Chrome to the Sunflower CLI through your Sunflower account. Agents can work with the sites you are already signed in to, inspect pages, and capture results using a shared browser interface. YOU APPROVE EACH SESSION Review the session title and request in the extension. Accept once to allow browser control, screenshots, recording, and supported debugging features for that session. Disconnect access from the extension whenever you choose. A matching Sunflower web tab can also show the approval request. A SEPARATE WINDOW FOR AGENT WORK New agent pages open in a separate, unfocused window. Existing tabs are shared only when you select them. The agent window uses your normal Chrome profile and website sessions; it is not an isolated browser profile. Websites may still show their own prompts, downloads, or popups. TOOLS FOR REAL BROWSER WORK • Navigate pages, inspect content, click controls, and fill forms. • Capture screenshots and record browser video. • Record tab audio/video after the required local toolbar interaction. • Collect Chrome performance traces to investigate JavaScript, layout, and rendering work. • Use supported Chrome DevTools Protocol commands and Playwright scripts through the Sunflower CLI. CONNECT THROUGH SUNFLOWER Sign in to the extension, then use “sunflower browser” from your terminal or agent workflow. The extension uses the Sunflower service to connect the CLI to Chrome. No exposed Chrome debugging port is required. Advanced users can select a compatible development server in the extension settings. REQUIREMENTS AND DATA A Sunflower account and a compatible Sunflower CLI installation are required. Chrome 125 or newer is required. Browser access operates within Chrome's extension/debugger capabilities; it does not provide every feature of a separately launched browser. Chrome may display its debugger-access warning while a session is attached. Approved page content and automation results can be sent through Sunflower to your connected CLI or agent. Captured files are private in Sunflower by default; you can choose to share them. Performance traces may include activity from shared browser/GPU processes. See the privacy policy for details about data handling and your controls.