Claude Code with Chrome

Reproducible practice

Reproduce one public-page defect with the smallest Chrome permission scope

Capture URL, visible state, console evidence, and a repeatable path without exposing an authenticated session or submitting data.

Prerequisites

• A supported Chrome environment and the official extension.
• A public or disposable test page containing no personal account data.
• Site permissions limited to the exact test origin.

Steps

1. Record the test boundary

   Write the exact URL, viewport, expected result, and actions that are allowed before enabling Chrome.

2. Connect explicitly

   Start Claude Code with Chrome only for this session; connection was not tested in this audit.

   claude --chrome

3. Reproduce without transmission

   Navigate and inspect visible state and console output; stop before login, form submission, upload, purchase, or permission prompt.

4. Capture minimal evidence

   Record the final URL, screenshot or console error, and deterministic reproduction steps, then disconnect.

Expected result

The defect is reproduced or ruled out on one permitted origin with no sensitive input, submission, or unrelated browsing access.

Validation

• Review extension site permissions before and after the test.
• Repeat the path from a clean page state.
• Confirm evidence contains no cookie, token, account identifier, or private URL.

Failure handling

Cleanup or rollback

• Disconnect Chrome and remove the temporary site permission if it is no longer needed.
• Delete sensitive screenshots or logs through the approved retention process, not ad hoc sharing.

Boundaries and when not to use it

• Browser access can expose authenticated content and transmit data through clicks or forms; confirmation is required at the action boundary.
• A public-page reproduction does not prove behavior for another account, region, extension set, or backend state.