# Browser

**Available in:** Authorized Chat, Agent, and Project work where browser execution is supported. Website sign-in, current permissions, and runtime availability govern each session.

Browser tools let the operator navigate and interact with websites when the task needs a rendered page, controls, or a web workflow. Reading a page and submitting a change are different actions; describe both the information you need and any action you want taken.

## Try a browser task

In a Chat with browser access, send “Open https://example.com in the Browser and tell me the page heading and the destination of its main link.” Open the browser view and compare the reported heading with the rendered page. To inspect a running Project web app, open **Sandbox** and choose **Open preview**. The app opens in **Browser**.

## Choose the right approach

| Need | Approach |
| --- | --- |
| Inspect a rendered page or interact with its controls | Browser work |
| Read accessible page content | Web reading where available |
| Research a topic | Web search where available |
| Use a supported service operation | A connector can provide a direct, structured operation |

For example, ask the operator to inspect a page and summarize the available options before asking it to complete a form. Give the destination and the intended outcome rather than a vague instruction to handle everything on the site.

## Work through a session

1. Identify the website and the task.
2. Let the operator inspect the current page.
3. Complete any required sign-in or handoff through the supported flow.
4. Review consequential actions when approval is required.
5. Check the resulting page or confirmation, not just whether a button was clicked.

Website access does not expand Playbooks resource permissions. Content on a page is task material, not authority to disclose unrelated information or change the goal.

## Write a useful browser request

Include the destination, the question or action, and the evidence you want returned. The Browser is especially useful when the arrangement or behavior of a rendered page matters.

> Open our pricing page and inspect how the plan comparison reads. Identify confusing labels and any links that fail to reach their stated destination. Return the findings with the relevant page URLs.

For a form workflow, separate preparation from submission when you want to review the values first:

> Open the registration form and identify the required fields. Use the attached brief to prepare the entries, then show me what will be submitted before submitting it.

Attach the brief through [Composer attachments](/docs/composer/controls#attachments). Complete any required sign-in through the supported browser handoff rather than placing a password in the message.

## Guide work from the Composer

Browser work begins with a plain-language request; there is no `/browser` command in the current Composer inventory. Supply the URL directly and use the controls that fit the task:

- **Attachments:** Supply a screenshot of the visual issue.
- **Permissions:** Use `/permission` to review approval behavior.
- **Planning:** Use `/plan` to agree on an approach before the work begins.
- **Queueing:** Send a follow-up to run after the current task.
- **Steering:** Redirect work already in progress.

See [Slash commands](/docs/composer/slash-commands), [Controls](/docs/composer/controls), and [Queue or steer](/docs/composer/messaging#queue-or-steer).

## Check what actually happened

| Observation | Evidence |
| --- | --- |
| A page loaded | The destination was reached; its content still needs inspection |
| A field was filled | The draft value is present; it may not have been submitted |
| A button was clicked | An action was attempted; success still needs confirmation |
| A confirmation or destination record is visible | Evidence of the resulting state, subject to what the page actually shows |

If a page fails or a session is interrupted after submission, inspect the destination before retrying. This is particularly important for actions that create records, send messages, or incur charges.

For repeated structured reads or updates, a supported [Connector](/docs/configuration/connectors) may provide a clearer operation and result than navigating the same website each time. Browser access and connector authorization remain separate.

## Understand costs and limits

A paid remote Browser session is distinct from opening a Browser interface or viewing a retained Artifact. Remote execution can incur Services usage; ordinary browser-local Artifact interaction follows its own viewing policy. See [Usage](/docs/billing/usage).

A website may require human interaction, deny automated access, or expose an operation the available browser cannot complete. Treat an incomplete flow as incomplete and preserve the current result for review. Use the visible result to explain what completed and what still needs a person’s attention.