poltertab 1.9.0-beta.1 → 1.9.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 +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -57,10 +57,10 @@ Prefer not to install globally? `npx poltertab setup` does the same thing.
|
|
|
57
57
|
|
|
58
58
|
The installer prints this link when it finishes:
|
|
59
59
|
|
|
60
|
-
1. Download the latest [release zip](https://github.com/abhinav162/poltertab/releases/latest) and unzip it
|
|
60
|
+
1. Download the latest [release zip](https://github.com/abhinav162/poltertab/releases/latest) and unzip it into its own folder (e.g. `unzip poltertab-extension-vX.zip -d poltertab-extension`, or double-click on macOS — which creates a folder automatically)
|
|
61
61
|
2. Open Chrome → `chrome://extensions/`
|
|
62
62
|
3. Enable **Developer mode** (top right toggle)
|
|
63
|
-
4. Click **Load unpacked** and select the
|
|
63
|
+
4. Click **Load unpacked** and select that folder (the one containing `manifest.json`)
|
|
64
64
|
|
|
65
65
|
Then restart your AI tool so it picks up the new tools.
|
|
66
66
|
|
|
@@ -356,7 +356,7 @@ PolterTab servers share that port by design (see above). Both sides must move:
|
|
|
356
356
|
Chrome allows only one debugger at a time per tab. When DevTools is open on the target tab, `browser_upload_file` (method `"picker"`) fails with "Another debugger is already attached". Close DevTools on that tab before running a picker upload.
|
|
357
357
|
|
|
358
358
|
**Adding `debugger` permission requires re-approving the extension:**
|
|
359
|
-
Loading or reloading the
|
|
359
|
+
Loading or reloading the extension folder after the `debugger` permission was added prompts Chrome to ask for re-approval — the extension is disabled until you click **Keep** or **Allow** on the warning dialog in `chrome://extensions/`. Unpack-loaded extensions do not auto-update, so this only happens when you explicitly reload or update the extension folder.
|
|
360
360
|
|
|
361
361
|
**Extension not connecting:**
|
|
362
362
|
|
package/package.json
CHANGED