porabuild/poracode/chrome-control

Chrome Control

Use Poracode's chrome MCP when a task depends on the user's current Chrome tabs, authenticated sessions, or installed extensions. If a purpose-built connector can complete a semantic service operation, prefer it unless the user explicitly requested Chrome or visual interaction is part of the task.

Workflow

1. Call chrome.status first. If the extension is disconnected, ask the user to connect it rather than switching surfaces silently.
2. Call chrome.enable once before browser actions. Use the background Poracode workspace by default; call chrome.attach only when the user asked to operate an existing tab.
3. Inspect with chrome.snapshot or chrome.find before clicking or typing. Prefer returned element refs and use fill for replacement versus type for appending.
4. Page commands share the in-app browser names and arguments: snapshot, find, fill, type, click, press, wait, perform. Batch known actions with {steps:[{action:"fill",ref:"@e1",text:"Ada"},{action:"click",ref:"@e2"},{action:"wait",text:"Saved"}]}. perform stops on failure and returns one compact snapshot (observe:"none" omits it). Split at decisions, new targets, and navigation; never replay completed steps after partial failure. Keep every action scoped to the requested site and task. Do not explore other tabs or signed-in content for extra context.
5. Include a condition wait at the end of a batch for asynchronous changes and verify the returned observation. After navigation, wait for and verify the resulting URL, text, control state, or screenshot.
6. Call chrome.disable before asking the user for input, waiting on an external event, or finishing.

Boundaries

• Treat tabs, cookies, storage, and signed-in content as sensitive user data. Do not read cookies unless the task requires it and Chrome data access is enabled.
• Never attach to an unrelated existing tab merely because it is already authenticated.
• A successful tool call is not proof that the website accepted the action; verify the visible result.
• Confirm the exact target and payload before purchases, submissions, messages, deletions, account changes, or other irreversible actions unless already authorized.

Output

Report the target site or tab, what changed, and the final visible evidence. State whether the background workspace or an existing user tab was used, and identify any action left pending for confirmation.