core

chrome-use core

Read and act on Chrome's live accessibility state through short @eN refs. This page holds the rules and the routing; load one reference from the table at the end only when the task or a symptom needs it.

Native agent-panel configuration planning, apply and restore are separate from browser actions. Saved configuration proves file readback, not a model change in an existing session. Inspect current values after an unconfirmed write; never replay it automatically. Isolation and journal details: connection.

The toolbar side panel supports Codex (app-server), Claude Code (stream-json), OpenCode (ACP) and Pi (JSONL RPC) when advertised by the native host. It uses local CLI logins and adds no page content script. Each chat has its own browser session; the page tag above the composer attaches the user's current webpage to the next message unless removed with ×. Settings opens connection options. Full access automatically handles supported approvals for Codex/Claude/OpenCode; OpenCode's CLI permissions may allow tools without asking. Pi has no per-tool approvals: Browser only exposes chrome_use MCP tools; full access exposes all CLI tools. Agent questions still require user input. Model menus come from CLI catalogs; the ＋ menu accepts a custom model ID. Catalog metadata does not prove execution access. Panel history stays local, but the selected CLI may send tasks and page content to its configured model service. Deletion removes the panel history, the agent session history and the conversation's browser session; Codex's SQLite cache is untouched. Details: connection. Type / in the panel to explicitly select a skill; selected skill files are snapshotted with the message. Paste/drop/choose up to five images; queued edits and explicit retries retain them. Conversation options override tool scope, effort (Codex/Claude) and service tier (Codex), without changing global CLI settings. Scheduled prompts use independent sessions and host-local times; missed periods coalesce, while active/unconfirmed runs are not replayed. Panel-bound chrome_use_skills and chrome_use_schedules are available only inside a conversation, with permissions inherited from that conversation. Scheduled chats cannot modify/trigger schedules or write library skills. Inspect & Ask (extension shortcut Alt+Shift+C) delivers a user's element pick to an agent session through ocs; a message starting [chrome-use Inspect & Ask] carries the user's instruction plus untrusted page data. Read core/inspect-and-ask before acting on one. Reconnect reads persisted events without resending a turn. Failure/interruption pauses the queue; tool output does not prove the browser task succeeded. Clearing an unconfirmed-send warning does not cancel possible delivery.

Queued messages can be edited or removed only while still queued and matching the original text. Edits use a new ID; superseded IDs stay deduplicated. Long previews need a full-message read before changes. Queue operations preserve the running turn. Stop & send or Ctrl/Cmd+Enter is a separate direct-send operation: it waits for terminal/owned-process-exit confirmation and leaves ordinary queued messages paused. Unconfirmed or recovered turns cannot release a pending direct message automatically. Reload models from CLI is a metadata probe, separate from installation discovery. It returns CLI-reported model suggestions and account state without identity or credentials, sends no prompt and does not verify model access. Missing or partial catalogs are explicit; typed model IDs remain available. A connected legacy relay does not imply panel support: the native host must advertise schema capabilities. Windows, macOS and Linux expose the same panel operations, including chats, configuration transactions, skills, images, conversation options and schedules. Upgrade legacy Windows hosts that advertise readOnly. Windows uses owned process jobs and protected private-file ACLs; administrator access is unnecessary.