Real Browser Integration

SuperBuilder gives AI agents access to a real browser — not a headless sandbox, not a simulated environment. Your actual Chrome browser, with your logged-in accounts, your cookies, your extensions, and your saved sessions.

Why "Real Browser" Is Different

Most AI tools that offer browser access use headless Chrome in a clean sandbox. That means:

• No logins — the agent can't access anything behind authentication
• No cookies — session state is blank every time
• No extensions — none of your custom blockers, save tools, or work extensions
• Sandboxed environment — the agent can't interact with your local network, your VPN, or your internal tools

SuperBuilder is different. When you open the Browser Panel, you're giving the agent access to your actual Chrome profile. The agent can navigate to Figma, GitHub, Linear, your internal dashboard — anywhere you're already logged in — and interact with it as you would.

What the Agent Can Do with the Browser

• Navigate any URL — including authenticated internal tools and staging environments
• Read page content — extract data, read documentation, scrape structured information
• Click, type, and interact — fill forms, click buttons, trigger UI actions
• Take screenshots — capture the current state of a page for reference or visual testing
• Execute JavaScript — run code in the browser context for testing or data extraction
• Work with tabs — open, switch between, and manage multiple tabs

Practical Use Cases

Testing your own app in staging — the agent opens your staging environment (where it's already logged in as you), clicks through a new feature, and reports what it finds. No credentials needed, no test account setup.

Pulling data from internal dashboards — your analytics dashboard, your team's project tracker, your billing system. The agent reads the live data and uses it in its work.

Verifying UI changes — after making a code change, the agent opens the browser, loads the relevant page, screenshots it, and checks that the change renders correctly.

Researching and referencing documentation — the agent can open documentation sites, API references, or GitHub issues and read them as part of solving your task. It uses real browser rendering, not raw HTML.

Interacting with third-party tools — Figma, Notion, Airtable, Linear — anything with a web UI that the agent needs to interact with to complete a task.

Privacy and Control

Because the browser uses your real profile, you control what the agent can access simply by what you're logged into. If you're not logged into something, the agent can't access it.

You can also:

• Open the Browser Panel to watch what the agent is doing in real time
• Pause browser automation at any point
• Restrict the agent to specific URLs or domains if needed

The browser runs locally on your machine. Pages opened by the agent are visible to you in the Browser Panel — you're always able to see what's happening.

How to Use the Browser Panel

The Browser Panel is available in the SuperBuilder Mac app:

1. In any thread, open the Browser Panel from the toolbar
2. The browser loads with your Chrome profile
3. Navigate to a starting URL, or let the agent navigate based on your task prompt
4. The agent interacts with the browser and reports what it finds or does

You can watch the agent work in real time, or step away and come back to the completed output.

Integration with Agent Tasks

The browser isn't just a standalone tool — it integrates naturally into agent tasks:

• An agent writing an integration can open the third-party API's documentation in the browser to get the latest specs
• An agent debugging a UI issue can open the browser, inspect the problem visually, and cross-reference with the code
• An agent building a scraper can prototype the scraping logic in the browser, test it, then write the production code

Frequently Asked Questions

Does this work with two-factor authentication?

Yes, because the agent uses your existing logged-in session. 2FA was completed when you originally logged in. The agent uses your existing cookies and session tokens.

Can the agent access my local network and internal tools?

Yes. Because the browser uses your actual profile and runs on your machine, it can reach anything your browser can reach — including internal tools on your VPN, local development servers, and staging environments.

What browser is used?

SuperBuilder uses Chrome with your profile. Support for other browsers is on the roadmap.

Is there any risk to my saved passwords or sensitive browser data?

The agent interacts with pages through browser automation — the same way any browser extension would. It doesn't have direct access to your saved passwords or keychain. It can only interact with what's visible on the page.

Can the agent see all my open tabs?

The agent can see and switch between tabs in the Browser Panel. It doesn't have access to tabs outside of the SuperBuilder browser session.