Skip to content
CleroHelp center

Search documentation

Try a topic or a task

↑ ↓ Move through results · Enter Open · Esc Close

Русский
English · Review draft
Documentation previewReview draft · English

Use the project browser

Find the browser preview, inspect progress, and hand control back deliberately.

Based on current source Evidence & limitations

Browser entry, shared scope, view/control/resume behavior source-backed; no live browser operation tested. This guide is a review draft; check access and saved results in your current workspace.

On this page

Browser work is useful when a task depends on a website’s current interface or content. Give the agent a bounded question and identify any action that needs your review.

The browser procedure below follows current source. The live documentation test did not start a browser or exercise its controls; no Browser tab was visible in the project navigation.

Ask for a browser task

An agent needs the relevant Browser / Use browser tool capability. If it is not available, an authorized person must inspect the agent’s tool configuration. Do not assume every agent has browser access.

Start with a public, read-only task:

Inspect these public product pages and summarize the audience, offer, and calls to action. Include the URLs checked and distinguish visible evidence from interpretation. Do not submit forms or contact anyone.

Open the live preview

The current implementation starts the shared project browser when needed. While the agent uses it, a preview appears near the conversation’s resources or artifacts.

  1. Find the browser preview in chat.
  2. Choose Open browser.
  3. Inspect the viewer. Opening it is view-only.

Do not look for a separate project Browser tab based on older tutorials.

Take control and continue

Choose Take control when you need to interact yourself. The source indicates this pauses the owning agent. Select Continue to hand control back and resume.

The current source also resumes when the viewer is closed while you hold control. Use Continue deliberately when you are ready, rather than assuming closing the viewer leaves the agent paused.

Check the site and account

The browser/profile is shared at project scope in the inspected implementation. Do not describe it as a private browser for each chat. Before a sign-in or external action, verify the site, account, and task.

Follow the sign-in request shown by the product. Keep credentials out of ordinary chat and screenshots. The exact authentication flow was not validated in the live demo.

When access is unavailable

Ask for the specific missing tool, permission, or site error. A page blocked by authentication is different from an agent without browser capability. Do not grant broader access merely to avoid diagnosing the actual issue.

Check the result

Open important source links, confirm the relevant locale and date, and inspect any changed destination. For read-only findings, request URLs and evidence. For an external change, request a verifiable outcome before retrying an ambiguous action.