pi-mono/packages
Vegard Stikbakke 8133c94db9 fix(ai): honor server-provided slow_down interval in device-code polling
GitHub's device flow documents slow_down as a rate limit: a poll that
arrives inside the throttle window is answered with slow_down instead of
the token, and the response's interval field reports the new required
minimum ("adds 5 seconds to the last interval"). A client that only
tracks its own +5s increment can stay behind the server's ratcheting
requirement when its timers fire early - common with WSL/VM clock drift
(microsoft/WSL#10006) - so every subsequent poll keeps hitting the rate
limit and login appears to hang forever even after the browser reports
the device as authorized.

Adopt the server-provided interval when a slow_down poll result carries
one, falling back to the RFC 8628 section 3.5 +5s increment otherwise.
GitHub Copilot passes the interval field through.

This restores part of the #1994 mitigations that were lost in the #4788
device-code refactor.

refs #6187
2026-07-03 22:26:12 +02:00
..
agent fix(coding-agent): serialize split-turn compaction summaries 2026-07-01 15:37:00 +02:00
ai fix(ai): honor server-provided slow_down interval in device-code polling 2026-07-03 22:26:12 +02:00
coding-agent fix(coding-agent): remove Vercel AI Gateway attribution 2026-07-03 15:14:01 +02:00
orchestrator Add [Unreleased] section for next cycle 2026-06-30 22:29:44 +02:00
tui Add [Unreleased] section for next cycle 2026-06-30 22:29:44 +02:00