You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(agents): use configured primary as fallback origin to prevent indefinite session pinning
When a model fallback occurs without an existing autoFallbackPrimaryProbe
(first fallback), resolveFallbackSelectionOrigin falls back to selectionRun
(which is the fallback candidate) instead of the configured primary. This
records the wrong origin, causing the snap-back probe guard
(originProvider !== primaryProvider) to always return early — the session
stays pinned to the fallback model indefinitely.
Fix: pass params.followupRun.run (the configured primary) as the primary
reference through applyFallbackCandidateSelectionToEntry →
resolveFallbackSelectionOrigin, so the origin is always the primary model
even on the first fallback.
Fixes#92776
0 commit comments