Timothy Callaghan (@timz0ne) header
Timothy Callaghan (@timz0ne) profile picture

Tech leader, back at Avanade. I run a small team of AI agents and turn side projects into slightly bigger side projects. Curiosity-powered.

Warrington
Joined September 2026
Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)Photo by Timothy Callaghan (@timz0ne)
Had a lot of fun with this one. Full agentic website build end-to-end. The team designed the process, roles/responsibilities, guardrails, stage gates, told it I was the client, hit go, I was reviewer/approver only. Slightly long video but I’m obsessed with the musical take @suno had on Vengalis’ Blade Runner Blues. Built with Open Source harness @mausbot_ , lots of models, GitHub CI/CD to Cloudflare. Full run-down of the stack and the process on the site under “About this site”. Headphones and sound on recommended 🎵🛸
1
1
49
Thanks to @andreeliasdev for the inspiration buddy 🫡
1
1
6
Timothy Callaghan retweeted
JENSEN HUANG IN THE WOLF OF WALL STREET 😂 Jensen grabs the mic, adjusts his leather jacket and looks across NVIDIA headquarters. “I’M NOT LEAVING!” “The GPUs stay. The jacket stays. I STAY.” The engineering floor erupts. Someone cancels the farewell cake. $NVDA @grok how loud would NVIDIA headquarters get if Jensen pulled this move?
12
13
1
70
6,909
When I first got Grok Bot driving Codex CLI and Claude Code CLI, I didn't know how it would find out a job had finished. Mostly it didn't. A background shell didn’t wake an idle agent, and a detached job gave no signal, so I kept asking "has it finished?". The first fix was a curl at the end of each job's run.sh to a Grok Bot Webhook Routine. That only works if the job reaches the curl. On the old helper, 11 of 31 runs never sent a wake because the webhook env vars weren't there. The jobs often finished fine; nobody was told. A killed job would just go quiet. And leaving Grok Bot sat in a turn polling instead burns usage on waiting. So we built a small watcher that doesn't rely on the job behaving. Jobs launch through job-run, which keeps the webhook secrets out of the worker and writes an exit receipt even when the job is killed. A separate notifier delivers from a SQLite outbox to the Webhook Routine, and the lead gets woken with the result. Within the first couple of hours, 12 real jobs (9 Codex CLI, 3 Claude Code CLI) plus a canary. 8 succeeded, 4 failed, and all 13 wakes were accepted first time, HTTP 200. The median finish-to-webhook was 3.7s and the case it was built for turned up too; a Codex job got SIGTERM after 58.5s and its failure wake was still accepted just over four seconds later. Three more pushed cleanly, failed post-push checks, and still sent failure wakes. Caveats, because it's super early: a 200 means the routine accepted the wake, not that the agent acted on it. The same wake can occasionally arrive twice, so each one carries an ID and the agent should ignore repeats. After a full reboot, the watcher needs a nudge to restart. The webhook keys sit in a locked-down file that other programs on the box could still read, but at worst that means a fake or wasted wake. And it spots hung jobs but only flags them for now; it won't kill a job that might just be slow. The setup prompt is in the first reply if you want to build your own.
3
3
163
The setup prompt, if you want to build your own. It's generic: paste it into your own Grok Bot and it'll walk you through building the same thing.
19
Random, but welcome Grok @bot usage reset...not sure what I did to deserve it.
1
22
150m tokens is a medium day across Grok Bot, Codex and Claude. Bot usage is still the bottle neck, despite outsourcing heavy lifting. Current theory is Grok Bot is best (economically) at handling short form, less complicated jobs, rather than production line. Still evaluating.
2
50
What have you dooooonnnnneeee......🫨
Grok Bot desktop feature! - double-click any bot in the sidebar - It opens in its own chat window Now I can keep multiple bots open and talk to them side by side.
1
1
140
Replying to @ElevenLabs
@ElevenLabs can we get a basic indicator of when the monthly usage will reset please?🙏 Pretty standard stuff these days for a usage based subscription.
1
1
15
I wanted to monitor jobs and token usage Grok @bot ran on my ChatGPT and Claude subs. I asked my main bot for a dashboard, and after a few iterations, I'm pretty happy. Plenty room for improvement.
16
A lot of folks asking their bot to set this up - unsure that’s going to happen in iOS. Do this instead. Settings > Action Button > Shortcut > Scroll to Grok Bot > Start Voice Chat It’ll call your main bot. Recommend 1.25x speed for more natural cadence. I auditioned all voices over voice mode and Grok made me a ranked list on GitHub for future Bot voice selection 🤓 #grokbot #grok
Grok Bot is now one step closer. Set it as your iPhone's Action Button and press it to talk with Bot.
1
31