Grok bots route Claude Code session questions to their owners
@therookiehacker describes Grok bots launching tagged Claude Code sessions. Questions and stops trigger a webhook; a main bot routes each event to the session-owning bot to inspect, steer, escalate or prepare a brief.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Help me design a Claude Code session launcher that tags the owning bot and routes question or stop webhooks to it. Surface decisions that need my input and explain approval boundaries before enabling session control.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @therookiehacker
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- @therookiehacker reports a workflow that routes Claude Code session questions and stops to the responsible Grok bot. Bots then steer sessions, bring questions to the poster or write briefs; no measured time saving is given.
- Human involvement
- The poster is having the bots build the scripts and hooks and receives questions or briefs from them. The capture does not describe access controls, deployment approval or a review policy for code changes.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Each Grok bot launches its Claude Code sessions through a company-wide script that tags the initiating bot.
- When Claude Code has a question or stops, it pings a Grok bot webhook.
- The main bot routes the event to the session-owning bot, which inspects it and steers the session, brings a question to the person or writes a brief.
@therookiehacker describes using Grok bots to supervise Claude Code sessions without repeatedly asking for updates. The poster says the bots are building scripts and hooks for the workflow, and describes a company-wide launch script that tags each session with the bot that started it.
When Claude Code has a question or stops, it pings a Grok bot webhook. A main bot routes that event to whichever bot owns the session. The owning bot can then inspect the session, steer the work, bring a question to the poster or write a brief. Session ownership is the connecting detail: an interruption goes to the responsible bot rather than becoming an unassigned notification.
The reported workflow links session launch, event delivery, routing and follow-up action. It is not a claim that Claude Code operates without supervision. Some questions still reach the person, and the bots' role includes deciding what to surface rather than merely collecting status messages.
The post gives no measured time saving or completed software-delivery outcome. It also leaves the hook implementation, routing rules and approval boundaries unspecified. This is a firsthand description of an orchestration setup, not an independently tested implementation or a guarantee that every stopped session is recovered.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @therookiehacker
Frequently asked questions
How does the workflow identify a session owner?
The company-wide launching script tags each Claude Code session with the bot that started it.
What triggers the webhook routing?
The poster says Claude Code pings a webhook whenever it has a question or stops. A main bot routes the event to the owning bot.
What can the responsible Grok bot do next?
It can inspect and steer the session, bring questions to the person or write a brief, according to the account.
More details
About this account
Grok bots reportedly launch sessions, route webhook events by ownership and inspect or steer Claude Code work. The post does not specify routing code, escalation criteria or what session actions require approval.
Scout supplied verified public X API captures read live on 2026-11-02 at approximately 08:00–08:08 UK time and explicitly authorised their use instead of reopening X. This entry uses the supplied written capture, not independent retrieval or reproduction. The supplied bio was reviewed for maker affiliation and self-promotion. Media content and self-thread continuations were not reviewed. The suggested prompt is an editorial addition; the post does not share a verbatim task prompt.
Credit: @therookiehacker
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot · Claude Code · webhooks
agent orchestration · session routing · webhooks
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.