Mario Zechner 030a61d88c feat: add maxDelayMs setting to cap server-requested retry delays ... When a provider (e.g., Google Gemini CLI) requests a retry delay longer than maxDelayMs (default: 60s), the request fails immediately with an informative error instead of waiting silently for hours. The error is then handled by agent-level auto-retry, which shows the delay to the user and allows aborting with Escape. - Add maxRetryDelayMs to StreamOptions (packages/ai) - Add maxRetryDelayMs to AgentOptions (packages/agent) - Add retry.maxDelayMs to settings (packages/coding-agent) - Update _isRetryableError to match 'retry delay' errors fixes #1123		2026-02-01 00:50:41 +01:00
..
agent	feat: add maxDelayMs setting to cap server-requested retry delays	2026-02-01 00:50:41 +01:00
ai	feat: add maxDelayMs setting to cap server-requested retry delays	2026-02-01 00:50:41 +01:00
coding-agent	feat: add maxDelayMs setting to cap server-requested retry delays	2026-02-01 00:50:41 +01:00
mom	Add [Unreleased] section for next cycle	2026-01-31 01:09:12 +01:00
pods	Release v0.50.7	2026-01-31 01:08:29 +01:00
tui	fix: make pre-commit hook fail on lint warnings, fix template literal warnings	2026-02-01 00:25:57 +01:00
web-ui	fix: make pre-commit hook fail on lint warnings, fix template literal warnings	2026-02-01 00:25:57 +01:00