Chrome

# Chrome

Use this skill when the user mentions `@chrome`.

Chrome is the routing touchpoint for the Codex Chrome Extension:

- Use Chrome directly for browser automation requests and for Chrome setup, detection, repair, or profile checks.
- For bare or general `@chrome` requests, do not ask a clarification question just because the request is ambiguous. Proceed with browser automation in this skill using the `chrome` backend.
- If communication with the Codex Chrome Extension ultimately fails, even after checks, do not attempt to complete the user's request using applescript, bash commands or any other scripting methods.
- Do not install or repair the native host yourself. If native host setup appears broken, tell the user to reinstall the Chrome plugin from the Codex plugin UI.

Before using this skill for the first time in the current conversation context, read the entire `SKILL.md` file in one read. Do not use a partial range such as `sed -n '1,220p'`; read through the end of the file. Do not mention this internal skill-loading step to the user.

## Chrome Extension Checks

On the first Chrome-backed browser task in a session, try a lightweight browser-client call such as listing open tabs after bootstrap. If the call fails, wait 2 seconds and retry the same lightweight browser-client call once. Any non-error response means the extension is installed and working.

If browser-client still reports that it cannot communicate with Chrome after that retry, confirm that Chrome is installed, running and that the extension is present in the selected Chrome profile:

From the plugin root, use `node_repl` to run:

```
scripts/chrome-is-running.js --check
scripts/installed-browsers.js --check
scripts/check-extension-installed.js --json
scripts/check-native-host-manifest.js --json
```

Depending on the outcome follow the following checks. Be sure to ask the user permission when required, if it is stated in the check.


### 1. Chrome is not installed

Keep the first response short and non-technical unless the user asks for more information.

If Chrome is not installed, then inform the user that this plugin only works with the Chrome browser.


### 2. Chrome is not running

Keep the first response short and non-technical unless the user asks for more information.

If Chrome is not running then ALWAYS ask the User if they would like to launch Chrome. ALWAYS wait for a user response before taking action.


### 3. The native host manifest is not installed, or is invalid

Keep the first response short and non-technical unless the user asks for more information.

Do not install or repair the native host yourself. If native host setup appears broken, tell the user to reinstall the Chrome plugin from the Codex plugin UI.


### 4. The Codex Chrome Extension is not installed

Keep the first response short and non-technical unless the user asks for more information.

If the Codex Chrome Extension is missing, tell the user:

`Cannot communicate with the Codex Chrome Extension. Confirm that the extension is installed and enabled in Chrome.` 

Ask the User if you can open the Codex Chrome Extension webstore page so they can verify that the extension is installed. ALWAYS wait for a user response before taking action. ALWAYS refer to the extension as the [Codex Chrome Extension](https://chromewebstore.google.com/detail/codex/<<EXTENSION_ID>>), and not by it's extension ID.

You can construct the URL of the Codex Chrome extension webstore page by appending the `extensionId` from `scripts/extension-id.json` to `https://chromewebstore.google.com/detail/codex/`.


### 4. The Codex Chrome Extension is not enabled

Keep the first response short and non-technical unless the user asks for more information.

If the Codex Chrome Extension is not enabled ask the User if you can open the Google Chrome Extension Manager so they can verify that the extension is enabled. ALWAYS wait for a user response before taking action. Always refer to the Google Chrome Extension Manager as [Google Chrome Extension Manager](chrome://extensions/).


### 5. Codex Extension is installed and enabled, the manifest file is installed, but communication still fails

Keep the first response short and non-technical unless the user asks for more information.

If Chrome is running and the extension/native-host checks pass, ask the User if you can open a Chrome window for the selected Chrome profile and retry the connection. ALWAYS wait for a user response before taking action.

If the User agrees, run:

```
scripts/open-chrome-window.js
```

Then wait 2 seconds and retry the browser-client setup once.

After one successful setup check in a session, do not repeat extension detection unless browser-client reports an extension connection failure.

If the issue is specifically the native host or extension-backed install path, or if communication still fails after opening a Chrome window and retrying setup once, tell the user to reinstall the Chrome plugin from the Codex plugin UI. Never import or run `scripts/installManifest.mjs` yourself.


## Chrome Error handling

### File upload errors

Keep the first response short and non-technical unless the user asks for more information.

If file upload fails when using `playwright_file_chooser_set_files`, `set_files` or similar tell the user exactly this:

`To enable file upload, go to chrome://extensions in Chrome, click Details under the Codex extension, and enable "Allow access to file URLs." See [here](https://developers.openai.com/codex/app/chrome-extension#upload-files) for details.`


## Commands

### installed-browsers.js

This script reports which browsers are installed.

From the plugin root, use `node_repl` to run:

```
scripts/installed-browsers.js
```

Use JSON output when another tool or script needs structured data:

```
scripts/installed-browsers.js --json
```

### chrome-is-running.js

This script checks whether Google Chrome is actively running. It exits `0` when Chrome is running, `1` when Ch