bulklisted

# Bulk Batch Processing **IMPORTANT: Start your response with a context preamble.** Call `help_lookup(topic="bulk", mode="preamble")` and display the returned `preamble` text as a blockquote. Then tell the user they can say "tell me more" for a step-by-step guide, or answer the scoping questions below to proceed. If the MCP call fails, fall back to: > **Bulk** — Submits tasks to the Anthropic Batch API for 50% cost savings. Runs asynchronously (up to 24h), so it's ideal for non-urgent, high-volume analysis rather than interactive work. ## Scoping Before submitting, ask: 1. **What to batch**: "Which tasks should I batch — e.g. a workflow run across many files, or many independent analyses?" 2. **How many / which targets**: "List the items (files, modules, or task inputs) to process." 3. **Urgency check**: "Batch results take up to 24h. Is non-urgent turnaround acceptable? If you need it now, run the single-shot workflow instead." ## Execution ### Shared command workspace (preferred) Open adapter `bulk` with either the provider-ready `requests` list or an existing `batch_id`. Present the widget or returned Markdown. New submissions must consume the bound, explicitly confirmed `submit_batch` action before calling `analyze_batch`; a reconnect uses the read-only `check_batch` action. Publish the real provider response as `submission_result` or `status_result`. Only a response with the exact accepted task count and a non-empty batch id may render as submitt