gawkbot, the open source Grok Bot. Bots you almost control
open source bots that (almost) serve you
gawkbots automate your menial work via AI models and build you microapps to manage the outcome, so that you have a false sense of control.
Runs on your machine, with your keys. No account, no cloud, no per-seat pricing.
They do the boring part.
You find out afterwards, on a dashboard.
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.
- filer Filed forty-one expense reports overnight. Left you a chart to look at.
- reconciler Matched the invoices against the bank. Two did not agree. Both now do.
- triager Triaged your inbox before you woke up. Ninety-three down to four.
- scheduler Booked the six meetings you kept not booking. Invitations are out.
- chaser Chased everyone who owed you a reply. Got four. Still working on Dave.
- tidier Renamed nine hundred files to the convention you described once, badly.
It is already done.
Here is an app about it.
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.
Trust your bots with less over time.
This is the part that is not a joke. A bot 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.
- Every tool call is written to a local log you can read. If a bot did something, there is a line for it.
- Permissions shrink by default. A grant you stop using expires rather than accumulating quietly.
The open source Grok Bot.
gawkbot is an open source Grok Bot: a team of always-on AI bots that runs on your own machine instead of a vendor's cloud. It is free, it uses the coding bot you already pay for (Claude Code, Codex, or a local model), every external action waits for your approval, and it builds you a microapp so you have something to look at.
| GROK BOT (xAI) | GAWKBOT | |
|---|---|---|
| Price | Bundled with SuperGrok and Cursor paid plans | Free. No account, no seats, no usage fees |
| Source | Closed | Public, Sustainable Use License |
| Runs on | xAI's cloud | Your machine, with your keys |
| Models | Grok, chosen for you | Claude Code, Codex, Opencode, local models, Hermes, OpenClaw |
| Approvals | Bots act on your accounts around the clock | Every send, commit, purchase, and delete waits for your click |
Last updated 1 September 2026. If a row is wrong, file an issue and it gets fixed.
Free.
The work has already started.
Source-available under the Sustainable Use License. Free to run and free to self-host, for your own internal business purposes and for non-commercial use. You can read it, modify it, and distribute your changes. The licence does not let you sell gawkbot itself as a hosted product. There are no seats, no usage fees, and no plan to add them.