Does Termdeck work with a SuperGrok subscription?

Yes. Bring your own xAI SuperGrok subscription. Termdeck drives the Grok CLI with the credentials and model access already on your machine — it does not sell model tokens or replace your xAI account.

Is there a web UI for Grok CLI?

Termdeck is one. It runs Grok over the Agent Client Protocol, renders native Grok session files in the browser, and lets you follow or drive runs from any device while sessions stay on disk for the terminal.

Can I use Grok with Claude Code and Codex in one dashboard?

Yes. Pick the engine per chat. Grok, Claude Code, and Codex share one sidebar, fleet board, approvals UI, and usage view.

Official · Grok CLI + SuperGrok

Termdeck officially supports Grok CLI and SuperGrok.

Q: Does Termdeck support Grok CLI officially?

Yes. Termdeck officially supports xAI's Grok CLI as a first-class engine. Start Grok Build sessions from the browser, stream transcripts, approve tool calls, switch model and reasoning effort, and review diffs beside Claude Code and Codex.

xAI’s Grok CLI is a first-class engine in Termdeck — not a plugin, not a half-wired experiment. Bring your SuperGrok (or other xAI) subscription, run Grok Build on machines you own, and drive every session from the browser or your phone next to Claude Code and Codex.

Open dashboard Try the demo

Official Grok CLI engine

Grok Build sessions over the Agent Client Protocol — same control surface as Claude Code and Codex.

Your SuperGrok sub

Use the xAI credentials and model access already on the machine. Termdeck is the control plane, not a token reseller.

Native session files

Browser and terminal share one session on disk. Start in either place; continue in the other.

Compare

Grok CLI alone vs. Grok + Termdeck

	Grok CLI (terminal)	Grok + Termdeck
Where it runs	Your machine	Your machine — unchanged
Auth & billing	Your SuperGrok / xAI account	Same subscription — bring your own
Read a session	Terminal scrollback	Streamed to any browser / phone
Tool approvals	In-terminal prompts	Allow / deny in the UI, with PWA push
Model & effort	CLI flags / in-session switches	Picker in the composer, mid-run
Diff review	Plain text in the terminal	Every edit as a readable diff
Beside Claude & Codex	Separate tools, separate panes	One sidebar, fleet board, and usage view
CLI round-trip	—	Native Grok session files; terminal-friendly

Termdeck never hosts the model or proxies your code. Grok runs locally with your auth; the browser is the seat of control.

What’s included

What official Grok support includes

Start and resume Grok Build from the browser

Open a new Grok chat, set the working directory, pick a model and reasoning effort, and send the first prompt without leaving the dashboard. Existing sessions load from Grok’s native files so terminal appends are picked up before the next web turn.

Stream transcripts and tool calls live

Agent messages, thoughts, and tool use land in the same transcript UI as Claude Code and Codex. When a tool needs permission, approve or deny from the desktop UI or from your phone via the installable PWA.

SuperGrok (and xAI) subscriptions stay yours

Termdeck does not sell Grok tokens. Install the Grok CLI, sign in the way xAI documents, and Termdeck uses that machine-local auth. Plan limits on termdeck.io are about connected machines and concurrent live sessions — not model usage.

One fleet with three engines

Grok sessions group by project next to Claude Code and Codex. Search, usage rollups, multi-machine agents, and the fleet board treat Grok as a peer engine, not a side channel.

FAQ

Grok CLI web UI, answered

Does Termdeck support Grok CLI officially now?

Yes. Grok is a shipped, first-class engine: runner, disk parser, watcher, model picker, approvals, and cloud remote path where applicable. It is listed and driven the same way as Claude Code and Codex.

Do I need a SuperGrok subscription?

You need whatever access xAI requires for the Grok CLI on that machine (often a SuperGrok or other xAI plan). Termdeck does not provide the model; it provides the web UI and control plane on top of the official CLI.

How does Termdeck talk to Grok?

Over the Agent Client Protocol (grok agent stdio): session create/load, prompts, cancel, model/effort switches, and permission requests. Session state stays in Grok’s own on-disk format.

Can I approve Grok tool calls from my phone?

Yes. Install Termdeck as a PWA. When a Grok run needs permission, the same approval inbox and push path used for Claude and Codex can unblock you away from the keyboard.

Will browser turns break the terminal workflow?

No by design. Termdeck loads native Grok sessions before each web turn so terminal-started work is visible, and it keeps using Grok’s session files rather than inventing a parallel store.

Can I run Grok next to Claude Code and Codex?

Yes — that is the point of the multi-engine dashboard. Choose the engine per chat and manage Claude Code, Codex, and Grok from one sidebar and fleet board.

Get started

Drive Grok CLI from your browser.

Bring SuperGrok. Keep the Grok CLI on your machines. Open Termdeck for the UI.

Open dashboard Try demo