Skip to main content

Computer notes / Browser access

A computer for your AI. Beyond the chat.

Give an AI agent a place to open web pages, save the results and run commands. Clawd's computer workflow brings a browser, files and a shell together behind a connector for Claude or Grok.

Join the computer waitlist

Computer access is on a waitlist. The published Hermes and OpenClaw agent plans are separate and do not promise access to this connector workflow.

Published agent plans are separate. See agent plans.

How the work connects
  1. You directClaude or Grok

    Give a bounded task through a connected chat.

  2. The computerBrowser + files + shell

    Open pages and save work outside the conversation.

  3. You reviewA saved result

    Check the sources and output before using them.

Proposed task flow. The recorded demo shows browser and file calls; shell support is documented separately.

The practical part

Choose the tools your task needs.

  1. A browser for actual pages

    Use the computer when your task needs page navigation, a screenshot or page content. A persistent browser profile can keep session state, but sites can expire logins, block automation or ask you to complete a challenge.

  2. Files for usable output

    Ask for a named output file, such as a CSV of source links, rather than only a chat reply. Check the file against the pages. AI extraction can miss details or mistake a navigation label for an answer.

  3. A shell for bounded commands

    The computer image supports shell commands inside its home directory, with a default timeout of 30 seconds and a maximum of 120 seconds. This is not a promise of unrestricted server access or an always-running worker.

Read the Claude computer setup guide

Worked example

Turn two help pages into a support contact sheet.

In this example, the fictional Oak help page links to /contact and the Elm help page lists installation steps with no contact link. The .example URLs below are illustrative. Replace them with pages you can read once computer access is enabled. This is not a recorded run.

Ask for this

Open the two help-page URLs I provide. Find each site's support contact route. Save source_url, support_route and review to research/support.csv. Leave missing details blank. Do not sign in or submit any forms.

Illustrative output

source_url,support_route,review
https://oak.example/help,https://oak.example/contact,needs review
https://elm.example/help,,not found

Check the result. Open each real source yourself and check the contact link. A blank cell means the agent did not find an answer. It does not prove the site has no support option. These fictional rows show one found route and one missing answer.

Make the call.

A good fit when

You want a hosted browser, saved files and short shell tasks for an AI you direct from chat, and can wait for computer access.

Consider another setup when

You need a computer available immediately, unrestricted infrastructure control or a worker guaranteed to run unattended around the clock.

Before you choose

Good questions.

Can I give Claude or Grok this computer today?

Computer access is currently on a waitlist. Join through the homepage. The setup guides describe the connector flow for enabled accounts; they are not a promise of immediate access.

Is this the same as buying an agent hosting plan?

No. The published plans cover hosted Hermes and OpenClaw agents. The computer connector is a separate waitlist workflow. Do not buy an agent plan on the assumption that it includes computer access.

Does the browser always stay signed in?

A persistent profile can retain session state. The destination site controls session expiry and may require another sign-in or a challenge. Only grant access to accounts and pages you are authorized to use.

What has the recorded demo actually shown?

The demo shows Claude using browser and file tools in two chats on one computer. It is evidence of that recorded workflow, not a live verification of every connector, website or shell task.