Tasks from the CLI, MCP and API meet your plan like every other task
Starting a task from the CLI, MCP or API is now held to the workspace plan's queue and billing, and refused up front as the dashboard refuses it, instead of by a separate cap of 5.
On plans with room for more than 5, you're no longer stopped at 5 tasks from these surfaces. When the queue is full the start is refused right away with the dashboard's message, which links to the upgrade page on Free, and a start that billing would stop, for want of model access or a paid-up subscription, is refused up front too, with a link to fix it, instead of opening a task that stops at once. For scripts these are 409 capacity_full and 409 payment_required, with the message in reason; 429 too_many_running is gone. Until the next CLI release, the CLI shows only the code; MCP clients get the full message now.
#2036