-
Notifications
You must be signed in to change notification settings - Fork 5.2k
xAI Request Failure #13400
Copy link
Copy link
Closed
Labels
area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.Agent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:authAuthentication, login, SSO, session management, and account security.Authentication, login, SSO, session management, and account security.bugSomething isn't working.Something isn't working.os:macmacOS-specific behavior, regressions, or requests.macOS-specific behavior, regressions, or requests.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.warp:auto-triage-review
Description
Metadata
Metadata
Assignees
Labels
area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.Agent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:authAuthentication, login, SSO, session management, and account security.Authentication, login, SSO, session management, and account security.bugSomething isn't working.Something isn't working.os:macmacOS-specific behavior, regressions, or requests.macOS-specific behavior, regressions, or requests.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.warp:auto-triage-review
Type
Fields
No fields configured for issues without a type.
Pre-submit Checks
Describe the bug
I am receiving a failed request upon querying grok build 0.1 via the Supergrok integration via a X Premium+ account. It looks like the OAuth2 token was invalidated and is no longer working, this points towards a refresh failure and needs deeper investigation. It would also be great if this could be detected and the user logged out or reprompted to log back in.
To reproduce
Expected behavior
The model should answer by refreshing the OAuth token or the user should be reprompted to log back in
Screenshots, videos, and logs
I'm sorry, I couldn't complete that request.
Response stream finished unexpectedly with internal error: XAI API error: POST "https://api.x.ai/v1/responses": 403 Forbidden "The OAuth2 access token could not be validated."
Operating system (OS)
macOS
Operating system and version
macOS 27 Developer Beta 1
Shell Version
No response
Current Warp version
v0.2026.07.01.09.21.preview_01
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
No response
Additional context
Conversation ID {"conversation_id":"f0bcf6e6-4534-4216-b2ed-41b47e1cb239"}
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
No response