Users with a Claude Pro (or Max) subscription, whose Claude usage is already covered through Claude Code's OAuth, currently have no supported way to dispatch Mission Control tasks through that subscription. The existing dispatcher only supports OpenClaw gateway or API keys, preventing Pro subscribers from utilizing their existing Claude access for task dispatch.
## Problem Statement Users with a Claude Pro (or Max) subscription — whose Claude usage is already covered through Claude Code's OAuth — have no supported way to dispatch MC tasks through that subscription. The current dispatcher in `src/lib/task-dispatch.ts` has only two paths: 1. **OpenClaw gateway** (`runOpenClaw(['gateway', 'call', 'agent', ...])`) — requires the `openclaw` binary. The `target_session` task-metadata branch (`task-dispatch.ts:693, 703-724`) also routes through OpenClaw, via `callOpenClawGateway('chat.send', ...)`. 2. **Direct Anthropic API** (`POST https://api.anthropic.com/v1/messages` with `x-api-key` — `task-dispatch.ts:221, 247`) — billed as pay-as-you-go API usage, **separate** from Pro. So a Pro-only user is effectively pushed toward installing OpenClaw purely to reach their own subscription, or paying twice for API access they already have via Pro. Meanwhile, most of the plumbing to route dispatch through the locally-installed `claude` CLI (which uses the