Claude Cowork can use connected services and, where enabled, a browser to work across sites. For a single task, decide which tool should read each source, which account should be active and whether any step may change data. Ask for a draft with links first. A request to “check the latest records and update the report” leaves the target, scope and meaning of “latest” open to interpretation.
Take a weekly operations note. It needs one record from a connected tracker, a status from an internal dashboard and a notice from a public vendor page. Let the connector read the tracker. Open the dashboard in an authorized browser, then use the public page for the vendor's own wording. Keep the report in the task output until a person can verify the sources and choose where it should go. A missing dashboard result is a blocked row, even if the other two sources are ready.
In a Reddit discussion about Cowork’s built-in browser, one reader asked whether it used their signed-in browser or a separate session. Check the account before handing over a task. If the entire job already lives in browser tabs, Tabbit Browser offers a separate route covered below. Reddit discussion
Key takeaways
Use a connector when it exposes the exact record and fields you need.
Open the relevant page for browser-only fields, and verify the account and workspace in that browser.
Return a linked evidence table before writing the summary. Keep missing and conflicting values visible.
Approve one exact change at a time. Read the saved value back by record ID.
Choose a connector or browser for each source
| Route | Start here when | Verify before using it |
|---|---|---|
| Service connector | An authorized integration exposes the needed records or fields | Workspace, account, read or write scope, and returned IDs |
| Cowork built-in browser | A permitted web page is the relevant source and you can sign in to the browser if needed | Browser availability, reachable domain, active session and site policy |
| Claude in Chrome | The task belongs in an authorized Chrome profile or tab | Profile, signed-in workspace, extension connection and site permissions |
| Desktop computer use | An approved task needs a desktop interface beyond a connector or ordinary web access | Operating system, granted permissions and the exact app or window |
A connector that can search a workspace may still lack access to an individual project. Start with a known record and check the returned identifier. When the connector supplies the status but omits a browser-only note, use the browser for that specific field. Keep the different source links in your output. If the connector reports a status update at 09:00 and the dashboard reflects a later change, include both times and ask the reviewer to decide which source governs the report.
For an internal URL, network reachability comes first. A site may require a company network, VPN, single sign-on or a specific Chrome profile. Cowork can only use the account and browser session it can actually reach. Ask for a harmless workspace label or known record ID before opening sensitive records. If the browser redirects to the login page or lands in a different workspace, stop that part of the task. Anthropic's connector overview and Team and Enterprise browser setup cover the relevant controls. How computer use works in Cowork explains where on-screen interaction fits.
For context, see what an AI agent does and web search versus browser control.
Verify the Cowork surface before starting
Check which surface you are in and which browser is selected in Cowork. With both browser routes enabled, Anthropic documents a preferred-browser setting. On desktop, the built-in browser is the default for people who have not already selected Claude in Chrome. Its session is separate from your Chrome session. Open the intended browser and confirm a workspace label before asking Claude to read a record.
Anthropic documents an optional site-by-site login import for the built-in browser. Confirm which account it uses, including after an import. Built-in browser guide
A cloud task can still depend on the desktop app for local access. Anthropic says new Cowork tasks on Pro, Max and Ultra started running in the cloud on October 6, 2026. The same guide describes the desktop connection needed for local files, local connectors, browser use or computer use when you start elsewhere. Check the connected computer and the settings in front of you. Team and Enterprise policies can affect which routes are available. A web session opening successfully is a separate check from a company dashboard loading. Cowork surfaces and desktop access
If the account matters, name the browser explicitly in the request. Anthropic says Cowork asks before switching when a named browser is unavailable. A generic request can fall back to the other browser. Browser permission checks apply per site, while connector access follows the connected service account and the connector’s tool settings. Anthropic
The articles on checking a signed-in browser session and choosing a browser connection by task show how another agent separates session and tool selection.
Read first, then assemble the report
Write down the precise fields before the first run. For a weekly operations note, these can be the record identifier, status, owner role, source update time and link. The report might cover a vendor incident, a response ticket and the approval state of the associated internal change. Tie the sources together with an explicit ID. A similar title can belong to a different incident.
| Item | Read with | Report | If unavailable |
|---|---|---|---|
| Response ticket | Tracker connector | Ticket ID, state, last update and record link | Request the exact ID or mark it blocked |
| Internal change | Approved browser profile | Workspace, change ID, displayed state and deep link | Record the login, permission or network issue |
| Vendor incident | Public browser page | Vendor title, reported time and source URL | Mark as missing and retain the attempted URL |
| Weekly note | Task output | Table, conflicts and draft summary | Keep unresolved rows separate from confirmed ones |
This is an illustrative workflow using fictitious records. Suppose the tracker says a response is closed and the vendor page says a service incident is resolved. The internal page still shows a change awaiting review. Those can all be true because they describe different records. The note should distinguish them rather than declaring the entire issue closed. If you need a short summary for stakeholders, produce it after the evidence table so each sentence can be checked against a row.
One Cowork user described a scheduled job that went through applications in five accounts using the Chrome extension. Their setup still paused at the login page for the operator. That is one person's workflow, and the important detail for a first run is the defined handoff at the sign-in screen. Original r/ClaudeAI report
For example, use vendor incident V-74 as the shared reference and keep the two internal IDs in separate columns. OPS-218 can be closed while CHG-56 still waits for approval. If the link between CHG-56 and V-74 is missing, mark it as unconfirmed and leave it out of the summary.
Prompt for a read-only first run
Read only the approved tracker project and the two URLs I give you. Use the tracker connector for the ticket. Use the selected browser for the internal dashboard and the public notice. Verify the workspace before reading the dashboard. Return an evidence table with source, record ID, field, value, timestamp, link and status. Mark inaccessible sources and conflicting values. Draft a short note here. Pause if an account is wrong, and before sending, publishing, creating, submitting or changing anything.Put a checkpoint before a write
Site access lets the tool reach a page. A write approval specifies what may change. Ask Cowork to show the destination workspace, record ID, current value, exact new value and who will see it. An approval for a weekly note in a draft folder should not carry over to a customer-facing post or an update to the source ticket.
After a person approves one change, request a receipt from the destination. Reopen the exact record or retrieve its latest version through the connector. Match its ID and read back the changed field. If saving timed out, look for the record before retrying. An ambiguous result belongs in the receipt with the attempted action and the last verified state. It should stay out of the completed count until you have read it back.
Treat web page text as source material. Instructions inside an issue, a shared document or a vendor page may come from someone outside your workflow. Keep allowed sites and actions in the task brief. If a page asks the agent to export information or sign in somewhere new, bring that decision back to the person who set the scope. Anthropic's Cowork safety guidance
When all the sources are already in Tabbit
If the report comes from two tabs you can open in Tabbit Browser, open the approved pages and give Agent Mode the two URLs and the fields to collect. Ask for a draft in the task. The same row format applies even when everything is browser-based.
Use Cowork for the mixed job if you need its connector and browser in the same task. For a browser-only job, the open pages and the execution log give you a place to verify what the agent actually visited.
See what an agentic browser is for the differences among browser, tool and agent.
Keep the task small enough to check
A useful first task has one known connector record, one allowed page and a draft that fits on one screen. Review the source links and the browser used. Once that works, add another source or one approved write, and keep the same receipt format. Read how to choose a first browser-agent task and how an agent connects to an existing browser when a signed-in session matters.
If the workflow already runs inside Cowork with the required account and sources, use that setup. If your team needs an agent to work in an authorized Tabbit Browser session, compare that route with Cowork by checking the session, tool and output each step needs. Tabbit and Claude Cowork
FAQ
Can Claude Cowork use an internal website?
It may be able to use an approved internal website when the selected browser can reach it, the intended account is signed in, and the organization allows access.
What if the connector does not cover a page?
Check whether a permitted browser can read that page. If the account, network or site policy prevents access, ask the user for an approved export or mark the row as blocked.
Does Cowork inherit my Chrome login?
Claude in Chrome can act in the authorized Chrome profile. Cowork's built-in browser has its own session, so verify the active account separately.
Can Cowork combine results from several websites?
It can draft a document from reachable, permitted sources. Request a link, record ID, observed value and status for each item so a reviewer can reproduce the read.
Can browser permission replace approval to submit a form?
Keep access and approval separate. Check the exact target record and proposed change before authorizing a write.