fix: distinguish ChatGPT authorization recovery from storage failures
This commit is contained in:
@@ -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;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user