Session retry loops forever — no max attempt cap or configurable limit

[Fatty911]

Description

SessionRetry.policy() in retry.ts retries retryable errors indefinitely with no maximum attempt count. The policy() function stops only when retryable() returns undefined (non-retryable error). Once an error is classified as retryable, the schedule retries forever.

This is the same underlying problem described in #21960, #17648, and #12234.

Steps to reproduce

1. Use a provider that returns persistent 429/overloaded errors (e.g., GitHub Copilot weekly limit exhausted)
2. Send any message
3. Observe the session retrying forever with exponential backoff

Expected behavior

• Configurable max retry attempts (e.g., experimental.max_retries)
• After max attempts exhausted, session should stop and surface the error
• Backward compatible: existing behavior preserved when not configured

Suggested fix location

• packages/opencode/src/config/config.ts - add experimental.max_retries to schema
• packages/opencode/src/session/retry.ts - add max attempt check in policy()

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• fix(session): SessionRetry.policy() retries forever with no max attempt count #21960: SessionRetry.policy() retries forever with no max attempt count — same root cause and fix location
• Session retries forever on weekly rate limit errors #24011: Session retries forever on weekly rate limit errors — same infinite retry symptom
• [Bug]: Session processor retries indefinitely with unbounded exponential backoff — no max retries or circuit breaker #17648: Session processor retries indefinitely with unbounded exponential backoff — no max retries or circuit breaker — same problem, also requests configurable limits

If your issue is distinct, please clarify how it differs from the above. Otherwise, consider adding your input to one of the existing threads.

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.