Claude Pro User Reports 5-Hour Usage Window Burned on Single Prompt with No Output

A Reddit user /u/TaleOfACat reports a frustrating experience with Claude Pro: a single prompt consumed their entire 5-hour usage window (100%), yet the model returned no usable output. Instead of delivering code, Claude entered what the user calls “project architect mode” — outputting paragraphs like “surveyed project scope” and “architected comprehensive redesign” with no final file. The model then hit its own internal limit and prompted the user to send a “continue” message to proceed.

The user acknowledges that tokens are consumed as generation starts, but argues that as a paying user, this is a broken experience. Key complaints:

• Burning an entire usage window on internal “planning” that produces no deliverable.
• Encouraging another “continue” message after the usage is already drained.
• Lack of a goodwill adjustment or safety mechanism when the model clearly fails to deliver the requested output.

The post reflects a common pain point for Claude Pro users: the unpredictability of token consumption when the model engages in extensive internal reasoning without producing a final result. The user suggests that the product should at minimum avoid consuming the window on non-deliverable text and not prompt additional messages after draining the usage.