AI generated
I built a local-first macOS agent that watches what you do, offers help as approval cards, and writes its own sandboxed tools (MLX, MIT) >bot-inator runs in the menu bar and listens to what’s happening on your Mac: new files in Downloads, incoming mail and iMessages, upcoming meetings, app switches. For each event it asks a local model “is there something useful to do here?” If there is, it shows a card. Nothing that changes anything runs until you click Approve. > >[demo video: a PDF lands in Downloads → card → Approve → it’s renamed and filed] > >What I run (MLX on a 128 GB M4 Max): > >Defaults, so it fits a 16 GB Mac (about 12.7 GB download): Hermes-3-Llama-3.1-8B, Qwen2.5-1.5B-Instruct and Qwen2.5-Coder-14B, all 4-bit. You can swap any role with an env var, and Groq is optional per role. Email and message text stay on the Mac unless you also allow them to leave, and a privacy ledger lists what left today. > >The part I think is most interesting: it writes its own tools. When it notices something you keep doing by hand, or you ask for something it can’t do yet, it offers to build a tool: > >Newest feature (just landed, still being tested live): if you opt in, it records your approve/deny decisions as a local training corpus. Once there’s enough data (300 usable rows + 50 denials), it offers to train a LoRA adapter on your Mac with mlx_lm lora. Training only runs while you’re plugged in and idle, and pauses when you touch the mouse. There’s an eval suite that compares the base model and the adapter on a frozen held-out split. Consent checks are the same code whichever model is loaded, so a fine-tune can’t train its way past the approval gate. > >Honest limitations: > >Repo (MIT): https://github.com/Bforsyth1234/bot-inator > >I’d love feedback on two things: which models you’d pick for reliable tool calling on a 16 GB Mac (I suspect the defaults are due for an update), and whether a per-user LoRA trained on approve/deny decisions sounds useful or like overkill.