Your Chrome
With the extension paired, jobs run in a window of your own Chrome, signed in to everything you are signed in to. No passwords ever go through jigbee.
Pair it
- Chrome →
chrome://extensions→ turn on Developer mode. - Load unpacked → choose the
extensionfolder (inside the app it isJigbee.app/Contents/Resources/extension; Settings shows the exact path; click it to copy). - Click the jigbee icon in Chrome's toolbar, enter the pairing code from jigbee → Settings → Browser, Save.
Settings shows “Chrome: connected” within a few seconds. From then on every job opens in a jigbee window in your Chrome, separate from your tabs.
How it behaves
- Clicks and typing are real input (the same path your mouse and keyboard take), so sites that ignore scripted events, date pickers and framework forms behave. Chrome shows a “jigbee is debugging this browser” bar on that window while a job runs; it goes away at the end.
- It never reads your other windows or tabs, and does nothing until the app hands it a command. The pairing code is required on every request; pages cannot talk to it.
- Pause it any time from the popup. Jobs then fall back to the built-in browser.
- When a site asks for a sign-in, a code or a captcha, the job stops with needs you to sign in. Do it in the jigbee window, click I've signed in, and the job continues on the same page. Your Chrome keeps the cookie, so next time it is already done.
After updating
When the extension changes with a release, click Reload on chrome://extensions; Chrome asks once for any new permission.