METAGROK
BUILD / import-claude-code-into-grok-build

Build

Import Claude Code into Grok Build

import-claude-code-into-grok-build

Import Claude Code into Grok Build

Grok Build can take over a Claude Code setup in two layers: automatic discovery of Claude files on disk, and an explicit session / settings import. Official references: CLI Reference, Modes and Commands, Skills, Plugins & Marketplaces.

What loads with zero setup

With no extra config, Grok reads Claude Code marketplaces, plugins, skills, MCPs, agents, hooks, and instruction files (CLAUDE.md, Claude.md, CLAUDE.local.md, .claude/rules/) alongside .grok/. Claude Code CLI flag names that overlap are accepted as aliases (--allowedTools, --disallowedTools, --append-system-prompt, --system-prompt, --dangerously-skip-permissions).

For enterprise MDM, Grok can also read a subset of Claude’s managed-settings.json (permission rules, MCP allowlists, some telemetry/feedback and marketplace restrictions). Grok’s own /etc/grok/requirements.toml still wins — see Enterprise Deployments.

Import sessions from the shell

grok import [targets...]

grok import brings sessions over from Claude Code. Pass target paths when you need a specific tree; run without targets when the default Claude locations are enough. Confirm what Grok discovered afterward:

grok inspect

Import settings from the TUI

Inside an interactive session, run:

/import-claude

That opens the Claude settings import modal (listed under Modes and Commands).

After import

  1. Run grok inspect (or grok inspect --json) and check rules, skills, plugins, hooks, and MCP origins.
  2. Open /plugins / /mcps / /hooks / /skills if you need to toggle or re-auth a server.
  3. Prefer Grok-native project rules in AGENTS.md / .grok/rules/ when you are standardizing a repo for both tools — see Make Grok Build follow AGENTS.md.

Pitfalls

  • Importing sessions does not replace team policy pins in requirements.toml.
  • Claude disableBypassPermissionsMode does not lock Grok’s always-approve; pin disable_bypass_permissions_mode in Grok’s own requirements file if you need that lock.
  • Compatibility scanners can be turned off with GROK_CLAUDE_* env vars listed in the settings reference.