Skip to content

bug: parallel ag run sessions share CC rate limit — no backoff or queueing #3931

@OneStepAt4time

Description

@OneStepAt4time

Dogfooding Finding — Adversarial Stress Test

Discovered by: Hephaestus (parallel `ag run` stress test, #3846)
Severity: P3 (enhancement)

Description

When launching 3 parallel `ag run` sessions, each creates an independent CC session that competes for the same CC rate limit. There is no coordination, backoff, or queueing between Aegis-managed sessions.

Expected

  • Aegis should be aware of active sessions and their CC usage
  • When approaching rate limits, new sessions should queue or warn
  • Optional: a `--concurrency` flag to limit parallel CC sessions

Actual

All 3 sessions fire independently. When the rate limit is hit, each session discovers it independently and fails with no coordination.

Environment

  • Aegis v0.6.7
  • 3 concurrent `ag run` sessions

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2backenddogfoodingDogfooding issues found during 5-minute setup testingenhancementNew feature or requestreleasedIncluded in a published releasetests

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions