Batch WO Dispatch

Benchmarked against: Anthropic — Batch processing Tools: dispatch_work_order, create_work_order, list_work_orders Architecture: Local UBI dispatch worker (fire-and-forget)

Batch dispatch enables running multiple Work Orders through low-cost engines efficiently. Instead of one-at-a-time execution, batch patterns allow parallel or sequential WO processing.

---

Single dispatch

The basic dispatch pattern — one WO, one engine:

dispatch_work_order(
    work_order_id="WO-2026-0305-001",
    engine="groq"
)

The worker runs as a background process. Use check_dispatch() to see results later.

---

Batch patterns

Pattern 1: Create and dispatch multiple WOs

# Create a batch of research WOs
for topic in ["Claude Agent SDK updates", "LangGraph 2.0 status", "MCP protocol changes"]:
    wo = create_work_order(
        title=f"[SS1-Research] Intel — {topic}",
        assignee="Mac CLI 小克",
        project="SS1",
        description=f"Research latest information on: {topic}. Summarize findings.",
        priority="low"
    )
    # Dispatch with free engine
    dispatch_work_order(work_order_id=wo["order_id"], engine="groq-search")

Pattern 2: Intel patrol (automated batch)

The patrol system dispatches multiple search queries across configured domains:

# Patrol all enabled domains
run_patrol(force=True)

# Or patrol a specific domain
run_patrol(domain="llm_tech")

Each patrol query becomes a separate search → auto-ingest to UB flow.

Pattern 3: Batch file ingestion

The ingest engine processes multiple files:

# Create a WO with file paths in description
create_work_order(
    title="[SS1-Operations] Batch ingest — specs directory",
    assignee="Mac CLI 小克",
    project="SS1",
    description="/path/to/file1.md\n/path/to/file2.md\n/path/to/file3.md"
)
dispatch_work_order(work_order_id="WO-...", engine="ingest")

---

Engine selection for batches

Batch type	Recommended engine	Cost
Research queries	groq-search	Free
Authoritative research	gemini-search	~$0.014 each
Text analysis	groq or deepseek	Free / Cents
File ingestion	ingest	Free
Code operations	claude	~$1-2 each (expensive for batch!)

Cost warning: Batching engine=claude dispatches can get expensive quickly. Use Claude engine only for WOs that truly need file operations.

---

Monitoring batch progress

# Check all pending/in-progress WOs
list_work_orders(status="in_progress")

# Check dispatch center for results
check_dispatch()

# Get specific WO result
get_work_order_detail(order_id="WO-2026-0305-001")

---

Batch limitations

Limitation	Impact	Workaround
Fire-and-forget execution	No real-time progress	Poll with check_dispatch()
No inter-WO dependencies	Can't chain WO results	Use orchestrator agent for sequencing
Single engine per dispatch	Can't mix engines in one WO	Create separate WOs per engine
Worker process limits	System resources	Don't dispatch too many Claude WOs simultaneously

---

Related pages

Page	Relationship
Dispatch Modes	Engine mode details
WO Admin	WO system reference
Local UBI MCP	Dispatch worker
Choosing an Engine	Engine selection