Handle 429 Rate Limit Responses from Copilot API in Agent

[CarGDev]

Problem

The Agent encounters "429 Too Many Requests" errors from the Copilot API, causing the agent to fail and throw an error.

Error message:

Agent error: Copilot API error: 429 Too Many Requests

Expected Behavior

The Agent should gracefully handle 429 rate limit responses by:

1. Implementing exponential backoff/retry logic
2. Displaying a user-friendly message about rate limiting
3. Continuing operation once rate limit resets

Current Behavior

• Agent fails immediately when hitting a 429 response
• No retry logic is implemented
• User sees a cryptic error message

Proposed Solution

Implement rate limit handling:

1. Detect 429 status code from API responses
2. Parse Retry-After header if present
3. Implement exponential backoff with jitter
4. Show progress/waiting indicator to user
5. Retry request after appropriate delay
6. Add max retry limit to prevent infinite loops

Files to Investigate

• Agent API call implementations
• HTTP client configuration
• Error handling middleware

Acceptance Criteria

• 429 responses are detected and handled gracefully
• Retry logic with exponential backoff implemented
• User sees informative message about rate limiting
• Agent continues after rate limit resets
• Max retry limit prevents infinite loops
• Add tests for rate limit handling