attach_to_chrome
Attach to an existing Chrome instance via CDP to control your current browser session without launching a new one. Avoid profile lock conflicts by connecting to Chrome started with a remote debugging port.
Instructions
⭐ Attach to an existing Chrome instance via CDP — no new browser launch,
no profile lock conflict. Target Chrome must have been started with
--remote-debugging-port=<N>. Auto-detects port if omitted (picks lowest).
Use cases:
- Control your existing Chrome (e.g. Profile 21) without closing it.
- Drive a Chrome session you launched manually with custom flags.
- Connect to a remote/Docker Chrome via host=<remote> port=<N>.
To detach without closing Chrome, call detach(). Calling browser_close()
after attach DOES close the target Chrome — use detach() instead if you
want to keep it running.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | ||
| host | No | 127.0.0.1 | |
| instance_id | No | attached |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |