Michael (@mbfrosty) header
Michael (@mbfrosty) profile picture

Diary of an AI Platform Engineer

Phoenix
Joined September 2026
Photo by Michael (@mbfrosty)Photo by Michael (@mbfrosty)Photo by Michael (@mbfrosty)Photo by Michael (@mbfrosty)
I kept adding scheduled jobs on my Mac to wire up my agents. Watchers, cleanup jobs, app watchdogs, Hookwise triggers. I wanted one place my bot could see all of them. macjobs is that command center. One CLI that covers launchd, cron, Homebrew services, Tailscale routes, and which job owns which port. It has JSON output and a skill you can hand straight to your bot. brew install --cask MBFrosty/tap/macjobs
1
30
See macjobs in action
12
Event driven bots are way more efficient than polling ones. Most of my routines were waking up on a schedule just to find nothing changed. So I built Hookwise. It finds those routines and helps you set up the replacement: a small local watcher that keeps state and fires the routine's webhook only when something actually happens. My fleet audit estimated 239 wakes a month down to 39. x.ai/bot/uNrolSDYQDll8cVYFqj…
15
poteto poteto @poteto Would love custom cards for plugins, like the Cursor agent cards. Is that on the roadmap?
23
One of my favorite new automations. I circle something in TestFlight, type a note, and a fix shows up in the next build. App Store Connect fires a webhook when feedback comes in. Tailscale exposes a small listener on my Mac. The listener files a Linear issue with my note and the screenshots. Forge (my Grok Bot dev desk) picks it up, posts a plan, hands it to a coding agent, and merges once checks pass. When the queue is clear, it ships one TestFlight build and pings me with what's in it. My only job now is testing on my phone and leaving feedback. Worth wiring up if you ship through TestFlight.
4
3
127
With Grok Bot and Cursor Projects, I’m finally feeling like a director with a real team. Groky (COS) is the executive assistant, the jack of all trades we know and love. Cursor Projects now fill the project manager role. Workers spawned by the Project are team leads. Architect, analyst, developer, QA, and the rest come from skills and frameworks (pstack, GSD, Superpowers, or your own). I don’t feel like I’m missing anything at this point. It just works.
1
29
Want Cursor Projects available from Grok Bot? Install the Cursor desktop app on the Grok Bot computer. Sign in, then tell your CoS to create a Project for a repo (or a group of repos). Copy the agent id and keep it as the standing handle for that work. From then on, Grok Bot can reply straight into that Project session.
3
50
Grok Bot → Cursor Projects is simpler than it looks. Projects are just durable bc-… agent chats. From Grok Bot you can list them, follow up with a reply, and watch until they finish.
1
1
2
94
So the split is: • Grok Bot CoS = life ops + front door (“drop this in the Project for that repo”) • Cursor Project = plans, fan-out, on-prem vs cloud Same usage either way — don’t run a second orchestrator bot that duplicates the Project.
1
41
Setup: open a Project in Cursor, grab its agent id/link, tell your CoS that’s the standing handle for that body of work. Next coding ask → reply into that chat. Let the Project decide on-prem vs cloud. Skip freestyle one-off cloud agents.
17