How TeamDay runs it
TeamDay calls grok with a prompt, working directory, streaming JSON output, model selection when requested, and a resume ID when the mission is continuing an existing session. Runner credentials come from the connected xAI account or API-key setup.
Best fit
- Grok-backed coding work: use xAI models directly in the same mission system as Claude Code, Codex, Gemini CLI, Hermes, and Pi.
- Independent review: assign a Grok-backed agent to verify or challenge work from another harness.
- Server-side automation: TeamDay keeps the CLI in the runner, captures events, and stores the resulting job history.
Status in TeamDay
Supported. Grok Build can be selected as a TeamDay harness after the runner has xAI credentials. The integration uses deterministic CLI event parsing and durable resume IDs; TeamDay-managed MCP injection is not enabled for Grok Build yet.
Learn more
- Getting started: docs.x.ai/build/overview
- Headless scripting: docs.x.ai/build/cli/headless-scripting
- npm: @xai-official/grok