fix: distinguish ChatGPT authorization recovery from storage failures

This commit is contained in:
amosblomqvist
2026-10-25 01:52:52 +03:00
parent 55a6501a09
commit 3cc598ded5
4 changed files with 71 additions and 4 deletions
+6 -1
View File
@@ -5,7 +5,12 @@ export interface ChatGPTStatus {
/** App-wide ChatGPT background permission, independent of account selection. */
allowBackgroundUse: boolean;
activeId: string | null;
accounts: { id: string; email: string; registration: string; connected: boolean; planEnabled?: boolean }[];
accounts: {
id: string; email: string; registration: string; connected: boolean; planEnabled?: boolean;
/** Main-owned authorization recovery eligibility. Missing means unknown, not eligible.
* False for storage failures, paused/closed connections, and healthy authorization. */
canSignInAgain?: boolean;
}[];
error: string | null;
catalogError?: string | null;
}