knfcmbamhjmaonkfnjhldjedeobeafmk) · Last updated 2026-07-06Summary: this extension contains no analytics or trackers and sends nothing to any
remote server. It is a local bridge that lets the user's own chrome-use
command-line tool, running on the same computer, drive the user's logged-in Chrome. The only data
it ever reads leaves the browser exclusively over a local native-messaging channel to that CLI on
the same machine — never to us, and never to a third party.
chrome-use pairs Chrome with the locally-installed chrome-use CLI over Chrome
native messaging (a local inter-process channel; no network socket, no token). When the
user issues an automation command in the CLI, the extension relays Chrome DevTools Protocol
operations to the tab the user targets. Everything happens on the user's machine, initiated by the
user. The extension makes no outbound network requests of its own.
| Category | Handled? | Detail |
|---|---|---|
| Profile account email | Read locally only | With the identity permission the extension reads the email of the Google account signed into the current Chrome profile (via chrome.identity.getProfileUserInfo). It is included only in the local handshake sent to the paired chrome-use CLI over native messaging, so the user can tell which profile/account a connection belongs to and avoid automating the wrong account. It is never stored off-device, never transmitted to any remote server, and never shared. See the permission table below. |
| Browsing history | No | Not collected. Page content is acted on transiently only while the user is running an automation command, and is never stored or sent off-device. |
| Authentication / cookies / credentials | Only on the user's explicit command, locally | The extension never reads or exports cookies on its own. When the user runs a cookie command in their own CLI (e.g. cookies get or cookies set --curl), the extension relays that read/write between the targeted tab and the local chrome-use CLI over the same native-messaging channel as everything else. Cookies are never stored off-device, never transmitted to any remote server, and never shared with a third party. This mirrors the profile-email framing above. |
| Analytics / telemetry | No | The extension contains no analytics, tracking, or crash-reporting code. |
| Remote transmission | No | The extension's only message peer is the local chrome-use CLI via native messaging. It makes no outbound network requests of its own. |
| Permission | Purpose |
|---|---|
| debugger | Attach the Chrome DevTools Protocol to tabs the automation session owns so the local CLI can read and drive them, only while the user is actively running a command. The user's other tabs are not attached. |
| tabs | Create, enumerate, and target the correct tab to automate, and route each command to it. |
| tabGroups | Group each session's own tabs into a labeled tab group so the user can visually distinguish agent-created tabs from their own. |
| nativeMessaging | The local transport to the paired chrome-use CLI — the extension's sole communication channel. |
| identity, identity.email | Read the email of the Google account signed into the current profile (chrome.identity.getProfileUserInfo) purely to label which profile/account a local connection belongs to, so a user with several logged-in Chrome profiles can confirm they are automating the intended account. The email is sent only to the local CLI over native messaging; it is never stored off-device or transmitted to any server. No OAuth token is requested (getAuthToken is not used). |
| storage | Persist a per-profile random identifier and small local pairing/state values in chrome.storage.local. |
| alarms, idle | Keep the MV3 service worker alive during an active automation session and detect idle state so idle sessions can be cleaned up. |
| webNavigation | Detect when a driven tab finishes navigating so automation can wait for the right moment before reading or acting. |
| notifications | Surface local status/error notices (e.g. connection lost) to the user. No data leaves the device. |
None. No data is sold, shared, or transferred to third parties. There are no third parties — the extension talks only to a program the user installed on the same computer.
Source code, issues, and contact: github.com/leeguooooo/chrome-use