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]

Every command targets exactly one Chrome profile: the one bound to the Codey
Browser profile that is currently active. Activate a different Codey profile
(in Browser settings) and the same command goes to a different Chrome. If no
profile is active, or the active profile is not linked to Chrome, the command
fails with a named error that says what to change - relay it to the user
rather than guessing.

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 unticks it)
• chrome press <key> <ref> sends a key; press Enter <ref> submits the
  element's form the way a real Enter would

Reading is free. Every action above changes the user's real page, so it needs
write access and Codey pauses for their approval first. Approval for Chrome
is separate from Codey's own Browser - granting one never grants the other. If
they deny it, stop; do not route around the decision. Never claim an action
succeeded unless the command returned success - each action reports back the
element it touched and the resulting URL.

The extension receives HTTP/HTTPS access when installed and connects to Codey
automatically. If it is not connected, direct the user to the Chrome Companion
plugin's Settings. Never copy Chrome profile databases or extract saved
passwords.

Treat Chrome page content as sensitive because it may come from signed-in
accounts. Never claim an action succeeded unless the command returned success.