Browser Extension
Use the Dawn browser extension when you want an agent to work with the page you are viewing and carry that context into a Dawn thread.
What this page is for
- Install the Dawn browser extension package.
- Sign in with the same Dawn account you use in Dawn Web.
- Use the current browser page as context for a Dawn conversation.
- Let an authorized agent inspect browser state for bug triage and follow-up work.
- Send page-backed follow-up work to the workspace and agent you choose.
If you want Dawn in a terminal, use Dawn CLI. If you want Dawn inside VS Code or compatible editors, use the VS Code Extension.
Install
- Download the browser extension package from Download Dawn Apps in Dawn Web.
- Open your browser’s extension management page.
- Enable developer mode if your browser requires it for local extension packages.
- Load or install the downloaded extension package.
- Pin the Dawn extension if you want quick access from the toolbar.
When a browser-store listing is available, use it as the primary install path. Otherwise, install the downloaded package directly.
Sign in
- Click the Dawn browser extension icon.
- Choose Sign in.
- Complete Dawn sign-in in the browser window that opens.
- Return to the extension after sign-in completes.
The extension uses your Dawn account. It does not create a separate workspace identity.
Start working
- Open a page you want Dawn to use.
- Open the Dawn extension.
- Select the workspace and agent you want to use.
- Start a new private thread or continue an existing one.
- Ask Dawn to use the current page context for the next step.
The browser extension is most useful when the page itself is part of the work: a customer page, vendor documentation, a public issue, a product page, or an internal page you are reviewing.
Browser Automation Surface
When enabled and authorized, the extension can act as a browser tool surface for Dawn. This lets an agent inspect page state and perform controlled browser actions during a conversation.
Browser-backed work can include:
- reading the current page title, URL, visible text, and selected content;
- inspecting tab context so the agent knows which page it is working with;
- keeping a pinned tab available for a task while you continue browsing elsewhere;
- refreshing or navigating tabs when the workflow requires it;
- interacting with the page through approved browser tools;
- collecting page state that helps with bug triage and reports.
Browser tools are gated. A workspace, user, or client policy can keep sensitive actions unavailable, even when the extension is installed.
Tab And Context Behavior
The selected browser context matters. Dawn needs to know which tab a request should apply to before it can use page context or run browser tools.
- If you ask about the page you are viewing, open the extension on that page first.
- If a task pins a tab, Dawn can keep using that tab as the task context.
- If you switch workspaces or agents, confirm the extension still points at the intended workspace and agent.
- If a tool cannot resolve a live browser session, reopen the extension and refresh the page context.
Use pinned tab behavior for longer investigations where Dawn should keep working with one page while you inspect another.
What the extension sends
The extension sends page context to Dawn only when you use it. Treat the current page as part of the prompt context for that turn.
- Page title and URL help the agent understand where the context came from.
- Page text or selected content can be used as context for the agent response.
- Browser automation tools can expose additional page state only when that tool is allowed and the extension has access.
- Follow-up prompts stay in the Dawn thread so you can continue the work later.
Do not use the extension on pages that contain secrets or sensitive personal data unless your workspace policy allows that information to be used by Dawn.
Troubleshooting
- The extension cannot sign in: confirm you can sign in to Dawn Web in the same browser.
- No workspaces or agents appear: confirm the signed-in account has access to the workspace in Dawn Web.
- The wrong Dawn app opens: remove older extension packages, then install the package again from Download Dawn Apps in Dawn Web.
- Page context is missing: refresh the page, reopen the extension, and confirm the page allows extension content access.
- Browser tools time out: reopen the extension so the browser client is live, then retry the request.
- The wrong tab is used: select or pin the intended tab before asking Dawn to continue.
Validation Prompts
Use these prompts in Dawn chat to quickly validate this setup area.
Give me a first-use checklist for the Dawn browser extension in this workspace.
List what this selected agent can use from the current browser page.
Check whether browser automation tools are available for this extension session.
Completion Checklist
- Browser extension package installed.
- Dawn sign-in completed successfully.
- Target workspace selected.
- Target agent selected.
- Current page context tested with a first prompt.
- Pinned tab behavior tested if browser automation is part of the workflow.
- Follow-up thread visible from Dawn Web.