Skip to content

Handle rate limits better #33

@elie222

Description

@elie222

What problem are you trying to solve

I ran deepsec on my project using Claude Code on a 20x Max plan. It hit rate limits and I got this output:

    Turn 1 (5s, 0 tool calls)
    Investigation complete (7.4s, 1 turns, 0 tool calls $0.000 0 tokens)
  Batch 233/239 complete: 5 analyses, 0 findings (5 in flight, 234/239 done)

    Agent SDK error: Claude Code returned an error result: You've hit your limit · resets 3:30am
    Agent SDK error: Claude Code returned an error result: You've hit your limit · resets 3:30am
    Investigation complete (7.0s, 1 turns, 0 tool calls $0.000 0 tokens)
  Batch 235/239 complete: 5 analyses, 0 findings (4 in flight, 235/239 done)

    Investigation complete (6.6s, 1 turns, 0 tool calls $0.000 0 tokens)
  Batch 236/239 complete: 2 analyses, 0 findings (3 in flight, 236/239 done)

What would you want deepsec to do

Ideally, the items it skipped over I'd be able to re-run later when my rate limit is reset. If there's already a way to do this, I'd love to hear.

Workaround you're using today

Not actually sure how to handle as if I rerun it I'll hit the same problem again I imagine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions