ghost-bridge 0.7.1 → 0.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +17 -0
- package/dist/cli.js +266 -140
- package/dist/server.js +132 -33
- package/extension/background.js +236 -81
- package/extension/manifest.json +1 -1
- package/extension/offscreen.js +64 -21
- package/extension/popup.html +72 -54
- package/extension/popup.js +72 -42
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -94,6 +94,11 @@ Typical prompts:
|
|
|
94
94
|
| `get_page_content` | Text, HTML, and structured DOM extraction |
|
|
95
95
|
| `get_interactive_snapshot` | Find clickable and editable elements |
|
|
96
96
|
| `dispatch_action` | Click, fill, press, scroll, hover, select |
|
|
97
|
+
| `pin_current_tab` | Keep Ghost Bridge attached to the current tab while you browse elsewhere |
|
|
98
|
+
| `pin_tab` | Pin a target tab by tab ID, URL fragment, or title fragment |
|
|
99
|
+
| `unpin_tab` | Return to following the focused tab |
|
|
100
|
+
| `get_target_tab` | Show the current target mode and tab |
|
|
101
|
+
| `list_tabs` | List available Chrome tabs |
|
|
97
102
|
| `list_network_requests` | Inspect captured network traffic |
|
|
98
103
|
| `get_network_detail` | Read one request in detail |
|
|
99
104
|
| `get_last_error` | Inspect recent console, exception, and network error events |
|
|
@@ -112,6 +117,7 @@ Recommended flow:
|
|
|
112
117
|
|
|
113
118
|
Notes:
|
|
114
119
|
|
|
120
|
+
- Use `pin_current_tab` when you are debugging a page and need to switch to other tabs without changing the AI target. Use `unpin_tab` to restore the original follow-focused-tab behavior.
|
|
115
121
|
- `list_network_requests` and `get_network_detail` automatically summarize `data:` URLs and very long URLs so inline images or oversized query strings do not overwhelm model context
|
|
116
122
|
|
|
117
123
|
## Configuration
|
|
@@ -136,6 +142,17 @@ flowchart LR
|
|
|
136
142
|
C <-->|"CDP"| D
|
|
137
143
|
```
|
|
138
144
|
|
|
145
|
+
## Troubleshooting
|
|
146
|
+
|
|
147
|
+
If the popup shows `No Bridge` / `Not Found`, it means the Chrome extension could not find a Ghost Bridge WebSocket service on the configured port. It does not necessarily mean your AI client is closed.
|
|
148
|
+
|
|
149
|
+
Run `ghost-bridge status` and check:
|
|
150
|
+
|
|
151
|
+
- `Active WebSocket Service`: the running server path should match the CLI/package you expect
|
|
152
|
+
- `Chrome Extension > Sync`: the installed extension should match the current package
|
|
153
|
+
|
|
154
|
+
If either is out of sync, run `ghost-bridge init`, reload the Chrome extension, and restart the MCP client so the browser, extension copy, and server process all point at the same build.
|
|
155
|
+
|
|
139
156
|
## Limitations
|
|
140
157
|
|
|
141
158
|
- Chrome DevTools on the target tab can conflict with `chrome.debugger.attach`
|