Use Grok Build Coming from Claude Code
Updated July 28, 2026
grok), not the Grok chatbot.Mental model
Claude Code stores a lot under ~/.claude/. Grok Build uses ~/.grok/. Skills for Grok live in ~/.grok/skills/. Project guidance often still works via AGENTS.md and related conventions Grok reads. Do not assume every Claude hook fires safely under Grok without review.
Grok can import some Claude-compatible surfaces. CodeAgentSwarm may pin certain Claude hook imports off for Grok terminals so you do not run two title-gates or double Stop notifiers. That is intentional.
Skills and MCP
Copy or reinstall skills into ~/.grok/skills/ rather than only linking Claude's tree blindly. MCP servers for Grok go in ~/.grok/config.toml under [mcp_servers.*] tables. CodeAgentSwarm can install its task MCP for Grok the same way it does for other agents.
See also sharing skills between agents for the multi-CLI pattern.
Run both, do not force a cutover
Most teams should not day-one migrate every workflow. Put Grok Build on exploratory or SuperGrok-favored tasks while Claude Code keeps the critical path, then widen. CodeAgentSwarm is designed for that mix.
FAQ
Grok understands common project instruction patterns including AGENTS.md-style files. Verify on your version; do not assume every Claude-only path is honored.
Typically ~/.grok/skills/ (agentskills layout).
Usually no. Run both until you know which tasks prefer which agent.
Keep Claude Code and add Grok Build in CodeAgentSwarm instead of replacing your whole stack overnight.