gawkbot

Runs on your machine, with your keys. No account, no cloud, no per-seat pricing.

Every bot runs on your machine as its own worker, with a shell, a browser, and a working directory of its own. It uses the tools you allow it, nothing more, and then it does the thing you have been putting off since March.

You talk to one bot at a time. Mention another and yours goes off to consult it rather than dragging it into your conversation. Ask for something menial and it tends to be finished before you have described it properly. Then it builds you a microapp, so there is somewhere to click.

The card charges, yes. They are in the app, waiting for you.

This is the part that is not a joke. An agent with your credentials and a browser is a real risk, and the honest posture is to grant it as little as possible for as long as possible. The defaults below are the actual defaults.

Runs on your machine, with your keys. There is no gawkbot cloud in the path, and no account to create. Point it at a local model and nothing leaves at all.

Every send, commit, purchase, and delete is gated behind an approval you have to click. Approval is per action, not a blanket grant, and it does not persist.

Each bot works in its own directory with its own tool allowlist, so what a bot can touch is per bot rather than per workspace. Your credentials never leave your machine.