> the task just happens to run down the 5 hour window usage.

In a single prompt? From zero usage? That doesn't "just happen".

When you're using the SDK, yes it can. Example: I used the Python SDK to translate a bunch of source code recently. I spawned a subagent for each module that needed translating and left it to run for a few hours with a parallelism limit of 5. It blasted through the 5 hour usage and dug into extra usage credits.

I have zero assurances that the above can't result in a ban. The usage pattern is not distinct from OpenClaw.

▲

deaux 4 hours ago | parent [-]

As I said, it doesn't just happen, you explicitly had to set it up so it could happen.

	▲	kuboble 2 hours ago \| parent [-]
		I'm confused about this comment. The GP has described a task which feels like a task very well within intended usage of CC, but can easily eat up the usage limit. What should we read between the lines about this scenario? Is it a bannable offense?