xAI Grok — sign in with your subscription
What you get
- Grok models (e.g.
grok-4.3) driven by your subscription — no API key, no per-token billing. - A background-refreshed session: sign in once, stay signed in until you sign out.
- A live
x_searchtool that searches current X (Twitter) posts through Grok.
Requirements
- An active SuperGrok subscription, or an X Premium+ subscription on the X account you sign in with.
- A browser on the machine (or use the manual-paste flow on a headless box).
There's no client key or app registration to set up — Flowly handles the OAuth client for you. Pick the provider and go.
Sign in
From the terminal UI
Open the provider picker
Type /provider in chat and select xAI Grok.
Approve in the browser
Press Enter on the xAI Grok row — your browser opens to xAI's sign-in page. Approve access and return to Flowly.
Start chatting
Flowly picks a Grok model and connects. The token refreshes in the background, so you stay signed in.
From the CLI
flowly xai login # opens the browser (or --manual-paste on a headless box)
flowly xai status # check connection + token expiry
flowly xai test # validate the token against xAILive X (Twitter) search
Signing in unlocks x_search — the agent can pull current X posts straight through Grok: recent posts from a specific handle, time-bounded searches, or X-grounded answers, with citations back to the source posts. Just ask:
- "What's @elonmusk posted about Grok this week?"
- "What are people on X saying about the new release?"
It appears the moment you sign in and disappears when you sign out — no restart needed.
Sign out
In the provider picker, highlight xAI Grok and press X. Or from the CLI:
flowly xai logoutTroubleshooting
“Authenticated, but not entitled” (HTTP 403)
Sign-in worked, but xAI hasn't granted your account access to this surface. Make sure your SuperGrok / X Premium+ subscription is active. xAI controls this allowlist; if it rejects you, use an xAI API key (the xai provider) instead.
Browser shows “couldn’t reach your app”
On older builds the consent page couldn't confirm the local sign-in and showed a "paste the code" fallback. Update to the latest Flowly — the sign-in listener now confirms automatically.
Works in the terminal but not the desktop app
Sign-in is done from the terminal UI / CLI. If the desktop app still shows the old provider after you sign in, restart it so its bundled agent picks up the change.