Your data and safety

Everything jigbee writes stays on your Mac. The only thing that leaves it is the prompt to the model you chose.

On your Mac

• Sessions, memory, reports, screenshots and logs: ~/Library/Application Support/jigbee.
• Your ChatGPT sign-in: auth/ in that folder, refreshed by the app, never copied elsewhere.
• No account with jigbee, no telemetry, no server of ours in the loop. The Chrome extension talks only to the app on 127.0.0.1 and requires the pairing code on every request.

To the model

Each browser step sends the page as text (what a screen reader would see, not pixels), your job, the step log and your memory notes to OpenAI through your ChatGPT plan, or to the provider whose key you gave. Desktop steps, which you allow per session, send a screenshot of the screen as well. The stats card shows exactly where the tokens went.

What it will not do

• Irreversible actions (pay, book, send, post, delete, cancel, submit a final form, change settings) stop and ask you first. You approve from the window or the menu bar.
• Sign-ins, codes, captchas, card numbers: it never types them. It pauses, you do it in the same browser, it continues.
• Your Mac (pointer and keyboard) only after you allow it, per session.
• Spend: each job pauses at the cap you set ($1 by default) and asks before going on.
• Code: a coding job runs only in a repo you added under Settings → Coding, on its own branch, and nothing is pushed or published without asking. It never types commands into a terminal through the desktop.

Open source

MIT licensed, built in public: github.com/ramankrishna/jigbee. The evals run the same jobs every night and publish what passed.