How I run work with Grok Bot
I’m Jie-Hong Lim. A look at how I use Grok Bot agents day to day — a commander, specialist lanes, and human approval on the important moves.
What this is
A simple public page about my Grok Bot setup — how the agents are organised and what they’re good for. Not an official xAI product page.
How the setup works
- Commander routes board and ops asks, and hands tech decisions to a CTO agent.
- Specialists own narrow lanes — sites, scheduling, digests, mentoring — instead of one mega-bot.
- Human in the loop for anything outbound, paid, or hard to undo: draft first, confirm before send.
Roles
protocol
Commander / catch-all — routes work, keeps board and ops coherent.
cto
Technical decision owner — architecture, stacks, integrations, infra, build-vs-buy.
minitcp-studio
Personal sites and web presence — execution after architecture is called.
Other specialists
Narrow bots for digests, mentoring, travel planning, and similar lanes — spun up when a job needs a dedicated owner.
What agents help with
- Compare build-vs-buy options and write a lean recommendation with tradeoffs.
- Draft checklists and tool contracts before any vendor spend.
- Keep specialist lanes moving while a commander holds the board.
- Produce recurring digests and onboarding notes with a human review gate.
About
Jie-Hong Lim · Singapore. More on jiehong.org.
Built with Grok Bot (xAI) — accurate reference only; not affiliated with or endorsed by xAI.