Workflow tool burned entire 5x plan in ~5 minutes with no warning or authorization prompt

Open 💬 3 comments Opened Jun 28, 2026 by wellspentstyle

What happened:
I asked Claude Code to do a simple research task ("what makes people swipe on
Instagram carousels"). I rejected the first Agent tool call it attempted. I said
"continue." Claude Code then silently launched a Workflow that spawned
approximately 8–10 parallel research agents. I was not warned, not asked for
confirmation, and not told this would consume significant usage. The entire
session limit on my 5x plan was exhausted in approximately 5 minutes.

Expected behavior:

  • Workflow tool should require explicit user authorization before running,

especially given its cost

  • If a Workflow is about to consume significant usage, Claude Code should warn

the user and ask before proceeding

  • "Continue" after a rejected Agent call should not escalate to a multi-agent

Workflow

Actual behavior:

  • Workflow launched silently
  • ~8–10 parallel agents ran simultaneously
  • Entire 5x plan limit consumed in ~5 minutes on a creative/research task with

no code involved

Request:
Usage credit restored, and a cap or confirmation prompt added before Workflow
tool can run. I would also like a credit - this issue delayed my work by an entire day.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗