Skip to main content
Continuum integrates Grok through a headless harness. Grok sessions participate in Chat, Code, Usage, and provider pickers on the same footing as other providers.

​
Requirements

The grok CLI must be installed and authenticated. Continuum starts Grok sessions through its headless harness; credentials are managed by the grok binary itself.

​
How it integrates

Continuum spawns the headless Grok harness and manages the session lifecycle through the daemon. Send, interrupt, and provider selection work through the same daemon endpoints as Claude and Codex. Grok sessions appear in:
  • Chat tab — solo and broadcast modes
  • Code tab — session list and workbench
  • Usage tab — token history and usage limits

​
Usage and limits

Grok’s usage limits and token history are surfaced in the Usage tab. The source is Grok session data read locally; Continuum does not make direct calls to xAI APIs.

​
Broadcast

Grok participates in the Chat tab’s multi-provider broadcast mode. Send one prompt to Grok alongside Claude, Codex, Antigravity, Cursor, and OpenRouter, and compare answers side-by-side.

​
No effort dial

Grok does not have a reasoning effort control exposed in Continuum. The effort chip is not shown for Grok sessions.