Hermes Agent SuperGrok support means you can run Hermes Agent on Grok using your SuperGrok or X Premium+ subscription, signed in through your browser, with no xAI API key. Run hermes model, pick xAI Grok OAuth (SuperGrok / X Premium+), approve the login at accounts.x.ai, and you're chatting with Grok inside Hermes. If you get an HTTP 403 after logging in, the documented fix is to set XAI_API_KEY and switch to the API-key provider.
📺 Watch: Hermes Agent + SuperGrok: Build ANYTHING!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
This guide walks through the setup, what one login covers, and what to do when xAI blocks your tier.
What is Hermes Agent SuperGrok sign-in?
Hermes Agent is the open-source AI agent from Nous Research. It supports dozens of model providers. One of them is xai-oauth, which the Hermes docs call "xAI Grok OAuth (SuperGrok / X Premium+)".
Per the Hermes guide, it uses a browser-based OAuth device-code login against accounts.x.ai. It works with either:
- A SuperGrok subscription on your xAI account, or
- An X Premium+ subscription on the X account you sign in with. The docs say xAI links the subscription status to your xAI session automatically.
No XAI_API_KEY is required. You log in once, and Hermes refreshes the session in the background.
When it landed
Nous Research shipped the provider in Hermes Agent v0.14.0, published 16 May 2026. The release notes put it at the top of the highlights: "If you pay for SuperGrok, you can now use Grok inside Hermes by signing in with your xAI account — no API key, no separate billing." The provider is listed as PR #26534.
The X Premium+ note came 12 days later. The v2026.5.28 release includes "xAI OAuth: note X Premium+ also unlocks Grok OAuth" (PR #29055).
Want Hermes running inside a full agent system, with every model and tool already wired? The AI Profit Boardroom ($69/mo) gives you the Agent OS, a 30-day AI agent roadmap, daily tutorials as new tools ship, weekly coaching calls and the prompt library.
How to connect Hermes Agent to SuperGrok
The Hermes quick start takes about a minute.
- Run hermes model to open the provider and model picker.
- Select xAI Grok OAuth (SuperGrok / X Premium+) from the list.
- Hermes opens or prints an accounts.x.ai verification URL. Enter the code shown if it asks, then approve access in the browser.
- Pick a model. grok-4.6 is pinned to the top.
- Run hermes and start chatting.
After the first login, credentials are saved to auth.json in your Hermes folder and refreshed before they expire. You stay signed in until you run hermes auth logout xai-oauth or revoke access in your xAI account settings.
Other ways to log in
- Skip the picker. Run hermes auth add xai-oauth to start the login directly.
- Remote servers. On SSH, containers or cloud shells, run hermes auth add xai-oauth --no-browser. Hermes prints the URL and code. Open it on your laptop. The docs say no SSH tunnel is needed for xAI.
- Desktop app and dashboard. Same device-code flow. Hermes shows the URL and code and polls until you approve.
- Set it in config. hermes config set model.provider xai-oauth and hermes config set model.default grok-4.6.
To check it worked, run hermes doctor. The Auth Providers section shows the state of xai-oauth.
If you keep separate setups for work and personal use, each Hermes profile can hold its own login. See my guide on Hermes multiple profiles.
📺 Watch: Hermes3D Is INSANE: AI Agents Now Have a 3D Office
What one SuperGrok login covers
Per the Hermes docs, the same OAuth bearer token is reused by every direct-to-xAI surface. One login covers chat plus these tools:
| Hermes feature | Works with SuperGrok OAuth? | Notes from the Hermes docs |
|---|---|---|
| Chat (grok-4.6 and others) | Yes | Default model grok-4.6. Also grok-build-0.1, grok-4.3 and the grok-4.20 variants. |
| Image generation | Yes | grok-imagine-image, grok-imagine-image-2.0, grok-imagine-image-quality. |
| Video generation | Yes | Grok Imagine. The video_gen toolset is off by default; enable it in hermes tools. |
| X Search (x_search) | Yes | Auto-enables when xAI credentials exist. Read-only search of public X posts. |
| Text-to-speech | Partly | The TTS table says XAI_API_KEY is preferred, because the subscription bearer 403s on metered TTS. |
| Live speech-to-text | No | Live STT needs XAI_API_KEY; the Grok OAuth login is not used for it. |
To pick a backend for each tool, run hermes tools. If OAuth tokens are already stored, the picker confirms it and skips the credential prompt.
What your subscription pays for
The Hermes provider docs have a "Subscription plans" table. For xAI it says OAuth draws on your subscription quota, which is documented explicitly for X Search. Inference quota beyond that is listed as "not currently documented". So if you hit a wall, it's xAI's limit, not a Hermes setting. My guide on Hermes Agent usage limits covers how limits work across providers.
Not sure if Grok is the right model for your business tasks? Book a free AI strategy session and we'll map out which jobs to hand to which model.
📺 Watch: Hermes AI Agents Just Went Portable
Fixing the HTTP 403 error
This is the most common problem. The browser login succeeds, tokens are saved, but chat or token refresh returns HTTP 403. The message reads like "The caller does not have permission to execute the specified operation".
The Hermes guide is clear on the cause: it's not a stale token. xAI's backend enforces its own allowlist on the OAuth API, and it "has been seen to reject standard SuperGrok subscribers with HTTP 403" even when the in-app subscription is active. That's tracked in hermes-agent issue #26847. Re-running hermes model won't change it.
The documented fix:
- Get an API key from console.x.ai.
- Set it as XAI_API_KEY in the .env file in your Hermes folder.
- Run hermes config set model.provider xai to switch to the API-key provider.
The docs say the API-key surface "is not subject to the same gating today". The other option they give is upgrading your subscription at x.ai/grok if you need the OAuth route.
Keep in mind the API key is billed by xAI per token, separately from your subscription. For X Search specifically, the docs note that when both are configured the explicit XAI_API_KEY wins, so searches run on metered API billing until you remove the key.
Other errors
- Token expired. If refresh fails for good, Hermes shows one "re-authentication required" message. Run hermes auth add xai-oauth again.
- Authorization timed out. The device code expires if you don't approve in time. Start the login again.
- No xAI credentials found. You haven't logged in yet, or the credential file was deleted. Run hermes model and pick the Grok OAuth provider.
SuperGrok in Hermes vs the Grok app
The Grok app gives you chat. Hermes Agent gives Grok tools: a terminal, a browser, memory, skills, scheduled jobs and messaging apps like Telegram and Slack. Signing in with SuperGrok puts the model you already pay for behind all of that.
xAI also has its own agent. For a side-by-side, read Grok Bot vs Hermes. To see where Hermes fits in a bigger setup with other agents, the Agent OS guide walks through it. For how agents and models score on real tasks, see Goldie Bench.
Want the setup prompts and the full system ready to go? Join the AI Profit Boardroom and plug Grok into the Agent OS on day one.
Hermes Agent SuperGrok FAQ
Do I need an xAI API key to use Grok in Hermes Agent?
No. With a SuperGrok or X Premium+ subscription you sign in through your browser with the xai-oauth provider. The Hermes docs say XAI_API_KEY is not used for that provider. You only need a key if xAI returns a 403 or for features like live speech-to-text.
Does X Premium+ work, or only SuperGrok?
Both. Per the Hermes guide, signing in with an X account that has Premium+ links the subscription to your xAI session, so the OAuth flow works the same way. The note was added in the v2026.5.28 release.
Why do I get a 403 after logging in?
xAI restricts OAuth API access to certain SuperGrok tiers, even with an active subscription. It's not a Hermes bug or a stale token. Set XAI_API_KEY and run hermes config set model.provider xai, per the Hermes troubleshooting guide.
Which Grok model does Hermes use by default?
grok-4.6, pinned to the top of the OAuth model picker. The list comes from a live model cache, so new xAI releases show up once it refreshes.
Ready to put Hermes and Grok to work on your business? Book a free AI strategy session and get a clear plan for what to automate first. Or grab a free strategy session here and talk it through live.
