Skip to content
agent-connector

Agent Architecture

Grok CLI

Grok CLI is a community open-source terminal coding agent for the xAI Grok API. It exposes interactive and headless modes, JSON event streaming, subagents by default, Telegram remote control, scheduling, MCP, skills, custom subagents, hooks, media generation, and a macOS computer subagent.

Source reviewed #38Checked 2026-07-06
Setup guideSource
Run type
CLI
Adapter
json-stdio
Source
OSS · superagent-ai/grok-cli
Stars
★ 3k

Archive Context

This page is one host entry inside the full architecture archive and keeps multi-surface products visible instead of collapsing them into a single run type.

42 host archive
Host page
grok-cli
Run cohort
CLI: 30
Archive route
/agents

Host Surface Perspectives

The host is the primary architecture boundary. Each runnable surface below separates what the host owns from what agent-connector can safely install for Grok CLI.

1 surface entry

CLI

cli
Host entry
A terminal command owns the process, current working directory, stdin/stdout, shell environment, and project file discovery.
Host owns
The CLI host owns agent loop timing, approval prompts, tool execution, session files, and how hook or MCP subprocesses are launched.
Connector role
agent-connector can only write the host's documented CLI config, prompt, memory, hook, MCP, or package files and point them at the home binary. Current wired connector surfaces: MCP server, Hooks, Memory.
Implementation consequence
A CLI surface is byte-addressable and smoke-testable from a temporary HOME, but terminal UI behavior still belongs to the host process. No visible host-native gap is currently tracked for this surface.

Verified Architecture

Source-checked on 2026-07-06. These notes are intentionally separate from the generated surface matrix below.

Sequence #38

Source pass

Current source review findings are kept as the first architecture section so readers can separate external evidence from the generated local coverage model.

  • Grok CLI is a community-built terminal coding agent for the Grok API with OpenTUI, headless mode, subagents, schedules, and Telegram remote control.
  • It documents shell-command hooks with JSON stdin/stdout and lifecycle events such as PreToolUse, UserPromptSubmit, SessionStart, and SubagentStart.
  • Project settings, AGENTS-style instructions, skills, MCP servers, sandbox mode, and desktop computer subagents are distinct host-only affordances.

Runtime boundary

The adapter target is the community Grok CLI process, not xAI's official product. Grok CLI owns the OpenTUI terminal UI, Bun runtime, headless mode, session state, schedules, and Telegram bridge.

  • The README states the project is community-built and not affiliated with xAI.
  • Headless mode can emit newline-delimited JSON step events.

MCP registration

Grok CLI supports MCP servers configured through `/mcps` in the TUI or `.grok/settings.json` under `mcpServers`. This is a concrete terminal-native MCP surface.

  • MCP is listed alongside skills, sessions, headless mode, and custom subagents.
  • API key state lives in env, `.env`, CLI flags, or `~/.grok/user-settings.json`.

Hook bridge

Grok CLI documents hooks that execute shell commands at key lifecycle events and configures them in `~/.grok/user-settings.json`. This makes it a strong json-stdio hook host.

  • The README shows `PreToolUse` hooks with matchers and command entries.
  • Hooks can enforce policy, run linters, trigger tests, or log activity.

Content surfaces

Grok CLI content includes `.agents/skills`, `~/.agents/skills`, custom foreground subagents in `~/.grok/user-settings.json`, schedules, generated media, computer screenshots, and persistent sessions.

  • Built-in subagents include task delegation and a computer subagent.
  • Telegram remote control pairs a phone with a running CLI process.

Marketplace and host-only affordances

The host-only affordance is Grok API alignment: live X search, web search, media generation, speech-to-text remote control, batch API runs, and community TypeScript hackability.

  • The macOS computer subagent depends on accessibility permissions.
  • Community status should stay visible so users do not assume official xAI support.

Host-specific shape

Grok CLI stores MCP and hooks in user settings and reads AGENTS.md-style memory; commands, skills, subagents, statusline, and actions are not confirmed file surfaces.

  • Form factor: CLI.
  • Native surfaces: MCP server, Hooks, Memory.
  • Wired surfaces: MCP server, Hooks, Memory.
  • Visible gaps: none.

Hooks

Hooks enter through a host-launched command that exchanges event JSON over stdio.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

  • Runtime handlers: none.
  • User-visible affordances: Users see managed memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Known Limits

  • Community project status must be explicit.
  • Computer subagent support is macOS-targeted in current docs.
  • xAI API model names and pricing can change quickly.

Evidence checked

Grok CLI repositoryxAI API

Architecture Diagram

Host-specific flow for the CLI surface.

json-stdio
Host-owned architecture flowHost surfaceCLIRuntimejson-stdioNative artifactsMCP + hooks + memoryConnector boundarystdio eventsUser surfacememoryagent-connector writes only documented host artifacts; the host owns the agent loop.
  1. 1
    Entry point: CLI

    Terminal agent process reads user/project config and invokes the connector home binary for runtime callbacks.

  2. 2
    Connector package

    defineConnector package declares server, hooks, content, memory, and actions.

  3. 3
    Adapter module: grok-cli

    json-stdio renderer at src/adapters/grok-cli/index.ts.

  4. 4
    Native host artifacts

    Adapter writes MCP config + hook config + memory/rules through this host's native file, package, or marketplace surface.

  5. 5
    Runtime boundary

    host launches JSON-stdio hook command

  6. 6
    User-visible surface

    Users see managed memory surfaces after install; runtime-only surfaces stay behind the host boundary.

  7. 7
    Coverage ceiling

    3/3 native surfaces wired. No visible host-native gap in the current coverage matrix.

Component Diagram

Static parts of the Grok CLI integration and which side owns each one.

Components and ownershipGrok CLI hosthostagent-connector packageconnectorgrok-cli adapterjson-stdioNative artifactsartifactsRuntime bridgeruntimeUser-visible surfaceuser
  • Grok CLI host

    CLI surface owns the model loop, UI shell, config discovery, and native lifecycle for this integration.

  • agent-connector package

    Normalizes connector declarations into MCP, hook, memory, content, and action payloads before delegating to a host adapter.

  • grok-cli adapter

    Implements the json-stdio translation layer in src/adapters/grok-cli/index.ts.

  • Native artifacts

    Adapter writes MCP config + hook config + memory/rules through this host's native file, package, or marketplace surface.

  • Runtime bridge

    host launches JSON-stdio hook command

  • User-visible surface

    Users see managed memory surfaces after install; runtime-only surfaces stay behind the host boundary.

Runtime Sequence Flow

Message order from install to runtime for the CLI surface.

User / projectagent-connectorgrok-cli adapterGrok CLIAgent runtimeCoverage matrix1. Choose host adapter2. Resolve connector declaration3. Render host-native shape4. Host loads artifacts5. Run through host boundary6. Expose remaining ceiling
  1. 1 · User / project
    Choose host adapter

    Install or update starts against Grok CLI; the selected surface is CLI.

  2. 2 · agent-connector
    Resolve connector declaration

    The package reads connector metadata and routes it to the grok-cli adapter instead of exposing a generic host contract.

  3. 3 · grok-cli adapter
    Render host-native shape

    Adapter writes MCP config + hook config + memory/rules through this host's native file, package, or marketplace surface.

  4. 4 · Grok CLI
    Host loads artifacts

    host launches JSON-stdio hook command

  5. 5 · Agent runtime
    Run through host boundary

    Users see managed memory surfaces after install; runtime-only surfaces stay behind the host boundary.

  6. 6 · Coverage matrix
    Expose remaining ceiling

    3/3 native surfaces wired. No visible host-native gap in the current coverage matrix.

Architecture Archive

The same five study axes are rendered for every host: runtime shape, hooks, MCP, memory, and host-only affordances.

Host-specific shape

Grok CLI stores MCP and hooks in user settings and reads AGENTS.md-style memory; commands, skills, subagents, statusline, and actions are not confirmed file surfaces.

  • Form factor: CLI.
  • Native surfaces: MCP server, Hooks, Memory.
  • Wired surfaces: MCP server, Hooks, Memory.
  • Visible gaps: none.

Hooks

Hooks enter through a host-launched command that exchanges event JSON over stdio.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

  • Runtime handlers: none.
  • User-visible affordances: Users see managed memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Special Feature Inventory

Host-specific capabilities separated from the generic surface matrix: lifecycle hooks, MCP registration, memory/rules, marketplace delivery, and UI or content affordances owned by the host.

Lifecycle hooks

Wired

Hooks enter through a host-launched command that exchanges event JSON over stdio.

MCP registration

Wired

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory and rules

Wired

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace delivery

Direct files

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Host-only affordances

Not confirmed

Wired host affordances: none. Host-native gaps: none. Not confirmed: Commands, Skills, Subagents, Statusline handler, Action affordances.

Source Review Notes

Latest source pass for host-specific architecture details. This is separate from generated adapter coverage and local drift guards.

Checked 2026-07-06Open review source
superagent-ai/grok-cli repository
  • Grok CLI is a community-built terminal coding agent for the Grok API with OpenTUI, headless mode, subagents, schedules, and Telegram remote control.
  • It documents shell-command hooks with JSON stdin/stdout and lifecycle events such as PreToolUse, UserPromptSubmit, SessionStart, and SubagentStart.
  • Project settings, AGENTS-style instructions, skills, MCP servers, sandbox mode, and desktop computer subagents are distinct host-only affordances.

Evidence Map

Each host page ties public source evidence to the local adapter and drift guards that keep the rendered archive aligned with code.

Public source: superagent-ai/grok-cli

Primary public repository or product source used for current host status and source links.

external
Open source

Local adapter implementation

Defines the install/uninstall behavior, native config rendering, capability flags, and any runtime parse/format bridge for this host.

local
src/adapters/grok-cli/index.ts

Platform metadata and host-native matrix

Records the form factor, public source target, ranking source, native host surfaces, and current agent-connector coverage cells.

local
site/src/platform-data.ts

Architecture drift guard

Asserts that every registered host has a page, diagram, host-specific brief, source link, form-factor band, and adapter-aligned surface data.

local
tests/docs/platform-drift.test.ts

Runtime Shape

Hooks are dispatched through a host-launched command. The adapter parses host JSON, calls the connector handler, and formats the reply back to the host contract.

MCP registration
Wired through this adapter
Hook bridge
Wired

Connector Surfaces

Static content

MCP server, Hooks, Memory

Runtime handlers

No runtime handler surfaces wired

Surface Matrix

Wired means agent-connector installs it now. Host native marks support we know about but have not wired yet.

SurfaceStatus
MCP server
Static content
agent-connector installs this surface today.
Wired
Hooks
Static content
agent-connector installs this surface today.
Wired
Commands
Static content
No confirmed host-native surface.
N/A
Skills
Static content
No confirmed host-native surface.
N/A
Subagents
Static content
No confirmed host-native surface.
N/A
Memory
Static content
agent-connector installs this surface today.
Wired
Statusline handler
Runtime handler
No confirmed host-native surface.
N/A
Action affordances
Runtime handler
No confirmed host-native surface.
N/A