Grok BotWorkBack officeAI score · 69/100AI-assisted edit · no obvious prompt-injection riskX

Using Grok Bot as a Manager: Dispatch 10 Tasks to Multiple Bots in One Message

Position Grok as a Harness orchestration layer: let a manager Bot break down, queue, and hand off tasks to specialist Bots, outsourcing heavy work to Codex and Gemini

Some experienceStepsTip
Who
Operators or small teams managing content production, asset organization, and multi-platform distribution
You get
Send a batch task list to a single manager Bot, which auto-splits and dispatches subtasks to specialist Bots, then aggregates deliverables and a pending-approval checklist
You need
Grok Bot

Constraints

Requires Grok Ultra subscription (tight quota; author’s rough measure is ~2 billion+ Tokens/week). You need to configure multiple Bot roles (e.g., Editor-in-Chief, Operator A/B) in Harness and connect external models (Codex, Gemini via Antigravity). Tools like Notion must be authorized for the corresponding Bots. The source does not show specific configuration screens or permission-granting paths.

What they did

The author has deeply used Codex and Claude since early 2026, consuming nearly 100 billion Tokens. This week they switched to daily use of Grok Ultra, positioning Grok as a team manager rather than a single model. One morning, they sent the Manager Bot a message with 10 tasks: topic into Notion, master outline, Twitter and WeChat versions, de-AI-flavor, cover image, asset filing, two scheduled radar briefings, and an approval checklist. The Manager Bot wrote nothing itself; it only broke down, queued, and dispatched: outline to Editor-in-Chief, two platform versions to two Operators in parallel, de-AI-flavor queued until draft completion, cover image dispatched to Codex, copy polish dispatched to Gemini via Antigravity.

How it went

Tasks were generally completed, but the author reports rework happens almost daily: copy tone rejected and rewritten, handoff fields mismatched and flagged by another Bot, network timeouts leaving tasks stuck. Grok’s visible handoff makes progress tracking easier—open the corresponding window to see status. Ultra quota is roughly 2 billion+ Tokens/week (personal rough measure), with chores and scheduled tasks consuming it quickly; the author believes usage without external AI would likely be insufficient. (author_report)

Worth knowing

1. Quota limits: Ultra ~2 billion+ Tokens/week (author’s rough measure); official caps not published. Codex 20x package feels like ~4 billion Tokens/week (author estimate). 2. Model capability boundary: Grok is not top-tier for large codebase work, image generation, or long-horizon complex reasoning; heavy work should be outsourced. 3. Human review is mandatory: multi-Bot collaboration does not mean hands-off output; final acceptance remains the user’s responsibility. 4. The source does not describe the exact Harness UI paths for Bot creation, role definition, or external model connection; actual setup depends on Grok’s current product. 5. Not tested by this site; the workflow above is the author’s reported experience, not a platform-verified result.

Steps

  1. Configure the multi-Bot team and external model permissions

    In Grok Harness, create or select a Manager Bot and assign subordinate roles: Editor-in-Chief (for outlines), Operator A (Twitter version), Operator B (WeChat version), etc. Connect Codex and Gemini as callable external models: cover-image tasks route to Codex; de-AI-flavor copy routes to Gemini (via Antigravity). Bind tool credentials such as Notion to each Bot. The source does not show specific UI fields; follow Grok’s actual product paths.

  2. Send a batch task to the Manager Bot and watch auto-dispatch

    Send the Manager Bot a single message with multiple tasks, for example: add topic to Notion; write a master outline; produce Twitter and WeChat versions simultaneously; remove AI flavor; make a cover image; file assets into the Notion library; run two radar scheduled briefings; finally list items needing my approval. The Manager Bot auto-splits: outline to Editor-in-Chief; two platform versions to two Operators in parallel; de-AI-flavor set to “queued” and auto-triggered after draft completion; cover image calls Codex; copy polish calls Gemini via Antigravity. Watch task status in each specialist Bot’s conversation window.

  3. Review deliverables and handle rework

    Check each specialist Bot’s conversation for deliverables: draft tone, cover image, asset filing results, briefing summaries. Reject and request rewrites directly in the corresponding window when quality is off (e.g., wrong tone, mismatched handoff fields). Use Harness visible handoff tracking to see stuck steps without asking each Bot for status. The Manager Bot finally aggregates a “items needing my approval” list. Note: network timeouts may leave tasks stuck mid-process and require manual restart.

Prompt you can copy

Reference prompt · Editorial suggestion。Confirm the destination, input variables and output format before use.

This block is the prompt. Ads are never placed here.

No prompt needed — just follow the steps.

No prompt needed — just follow the steps.

Source

把 Grok Bot 当主管用：Harness 多 Bot 分派、交接与上下文传递（Article） · zhu1894341 · X · 2026-10-31T07:14:42.000Z

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related