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: resolve instance IDs to driver kinds in ProviderCommandReactor
- Use the actual unknown provider slug in ProviderAdapterRequestError
instead of hardcoding 'codex', so error messages and tracking
correctly identify which driver caused the failure.
- Resolve instance IDs to their underlying driver kind via
ServerSettings.providerInstances, so custom instances (e.g.
'codex_personal') properly map to their driver and are not
rejected at the ProviderKind narrowing check.
- Compare driver kinds (not instance IDs) when checking for
provider switches, so two instances of the same driver are
correctly treated as compatible.
detail: `Thread '${threadId}' references unknown provider driver '${threadProviderCandidate}'. The driver is not installed in this build (rolled-back / fork mismatch).`,
303
+
detail: `Thread '${threadId}' references unknown provider driver '${threadInstanceId}'. The driver is not installed in this build (rolled-back / fork mismatch).`,
0 commit comments