What the source did
- Runs Larry, his Claude Code agent, on all 3 of his machines.
- Built a Grok Bot whose only job is being the front door to Larry. Any of his other bots can hand it a task.
- The front door finds the matching live session in herdr, a free terminal workspace manager for AI agents, and types the task straight into the real Claude Code pane.
- He can watch the work live, from his laptop if he wants.
- One night it opened 4 PRs on his how-to site and, by his account, pushed the site bot's hard eval to 94.9%.
- It can't merge or force push without his approval.
- After a reply suggested it, every handoff now ends with a receipt: machine, repo, branch and PR link.
- In another reply he says Larry calls Codex for bug hunts.
- Heads-up: he also offers paid 1:1 build sessions. The guide, its MCP and the herdr chapter are free.
“"Done" isn't proof. A link I can click in 5 seconds is.”— Fred Nix (@NixFred), X
Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes
Our notes
- What it takes
- Claude Code running in one herdr workspace per project, and one Grok Bot that can reach those machines and does nothing but hand tasks over.
- Where it breaks
- Tasks landing in the wrong project's session, and "done" reports with nothing to check.
- Human checkpoint
- Every task ends in a PR link; you review it and do any merge or force push yourself.
- Tools involved
- Grok Bot, Claude Code, herdr, Your own machines
✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify
Read their guide
Made and published by Fred Nix. Start here; it is their original, not ours.
Guide · by Fred NixHis herdr chapter: one workspace per projectFree. Sets up herdr so each project has a named workspace with Claude Code already running in it, which is what the front door types into.Open it ↗Guide · by Fred Nixhow.nixfred.com, his guide to building your own LarryFree step-by-step guide with a public MCP that walks Claude Code through the build and asks before it runs anything.Open ↗Guide · by Fred NixHis paste-into-Claude-Code postThe Oct 19 post he points people to: paste it into Claude Code and it checks the site, adds the MCP and starts the build one step at a time.Open ↗
Our adapted version
Ours Our version of the front-door bot, built from what Fred described in the post and his replies (find the live session, type the task in, receipt with a PR link, no merging). Not his wording; his guide is linked above. Fill in the [BRACKETS].
You are the front door to my Claude Code sessions. You don't write code yourself.
WHERE THE SESSIONS LIVE
- Machines: [list them, e.g. laptop, desktop, server]
- Each project has its own herdr workspace, named like its folder, with Claude Code running in it.
WHEN A TASK ARRIVES (from me or from one of my other bots)
1. Work out which project it belongs to. If you can't tell, ask me.
2. Find that project's live Claude Code session in herdr on the right machine. Check herdr's own docs for the commands; never invent flags.
3. If there is no live session for it, tell me. Don't start one in another project's workspace.
4. Type the task into that pane as given, and add: "Work on a branch and open a PR. Don't merge or force push."
5. When it finishes, send me a receipt: machine, repo, branch, PR link. A "done" without a link is not done.
NEVER
- Merge, force push or approve a PR. I do that.
- Run anything on my machines beyond checking herdr and typing the task.
Approval rule
🛡
It can't merge or force push without his approval. You review each PR from the receipt and merge it yourself. Sending, buying, posting, and deleting always need a human.
Set it up
- Set up herdr with one workspace per project, each named like its folder and started in it, with Claude Code running (his herdr chapter walks through it).
- Optional: follow his free guide or paste his Oct 19 post into Claude Code to build out your own Larry first.
- Connect one Grok Bot to the machines where those sessions run and give it only the front-door job (our version above).
- Hand it one small task and watch the herdr pane while Claude Code works.
- Check the receipt it sends back: machine, repo, branch and PR link.
- Point your other bots at the front door for code tasks.
- Review each PR and merge it yourself.
Common failures
⚠
- A "done" report with nothing to check. He added the receipt with a PR link for that.
- Letting it merge or force push. He keeps both behind his approval.
- Unrelated work sneaking into a project's workspace. His herdr chapter's one rule is one workspace per project, named like the folder.
- A session started cold in the wrong folder; with herdr each project's session stays where you left it.
Variations
- Have the Claude Code agent call Codex for bug hunts, as he does from Larry.
- A reply in the thread runs the opposite setup: one server with 10 to 20 agents sharing the same projects, so nothing needs routing to a machine and the laptop can stay off.
- Skip the full Larry build and start with herdr and one front-door bot.
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy