chrome-companionlisted

# Chrome Companion ## Choosing between Chrome and Codey Browser - A turn originating in the Chrome Side Panel always targets Chrome Companion. - Requests naming Chrome, the current Chrome tab/window, the extension, or the user's Chrome login/session also target Chrome Companion. - For those turns, never substitute Codey's embedded Browser, even if Browser is preinstalled or already open. - Generic web requests made in Codey's desktop chat continue to use the embedded `browser` skill unless the user identifies Chrome. Control the user's real Google Chrome through the separately installed Codey Chrome Companion extension. Every command is one shell call: ``` ELECTRON_RUN_AS_NODE=1 "$CODEY_BROWSER_RUNTIME" "$CODEY_BROWSER_CLI" chrome <command> [args] ``` ### Reading - `chrome status` checks whether the extension is connected. - `chrome tab` reads the active Chrome tab title and URL. - `chrome view` reads the active Chrome page text, links, and form summary. Every link and control comes back with a `ref` like `e3` - that is how you address it below. - `chrome open <url>` navigates the active Chrome tab. ### Acting Always run `chrome view` first to get fresh refs; every `view` renumbers them, and a stale ref is rejected rather than applied to the wrong element. - `chrome click <ref>` clicks an element - `chrome fill <ref> <text>` types into a field - `chrome select <ref> <value>` picks a dropdown option - `chrome check <ref> [false]` ticks a checkbox (`false` un