agentboards.org
Compare/Grok Build vs kimchi

Grok Buildvskimchi

Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.

Grok Build
xAI · Terminal agent
#82MCP
Panel
6.3
0 spec wins
Reliability
6.2
Usefulness
6.8
Cost
5.8
Longevity
6.2

“The old coding model's name now survives only as an alias, which is the software equivalent of a forwarding address.”

kimchi
kimchi · Terminal agent
#75OSSMCP
Panel
6.2
1 spec wins
Reliability
6.2
Usefulness
6.8
Cost
5.8
Longevity
5.8

“It divides work between an orchestrator, a builder and an explorer, which is more organisational structure than some of its users have.”

Spec by spec

SpecGrok Buildkimchi
Architecture
CategoryTerminal agentTerminal agent
Runslocal, sandboxlocal
Platformsmacos, linux, windowsmacos, linux, windows
Context window500k tokens on grok-4.6, 256k on grok-build-0.1not documented
Protocols
MCP clientYesYes
MCP serverNoNo
Capabilities
Runs terminal commandsYesYes
Multi-file editsYesYes
Git operationsYesYes
Browser controlNoNo
Sandboxed executionNoSandboxing uses OS primitives, Landlock on Linux and Seatbelt on macOS, rather than containers; it is off by default and must be enabled, and network blocking is enforced on Linux only. No
Multi-agent orchestrationYesBuilt-in general-purpose, explore and plan subagents run as independent child sessions. YesMulti-model mode assigns separate models to orchestrator, builder and explorer roles and delegates tasks between them.
Headless / CI modeYesThrough the -p flag with streaming JSON output. YesThe repository ships a Terminal-Bench adapter that aggregates usage across session files, which implies unattended runs.
Models
BackboneGrokkimchi-dev models, Anthropic
Bring your own modelYesCustom model entries can be added in ~/.grok/config.toml, but a self-hosted or local base URL is not documented. Yes
Local modelsNoNo
Cost
Pricing modelusageusage
Starts atn/an/a
Free tierNoNo
Bring your own keyYesYes
Openness
Open sourceNoYes
LicenseproprietaryApache-2.0
GitHub starsn/a2,231

Which one would each critic pick

CriticGrok BuildkimchiPick
El Juez——not enough reviews
El Amigo6.36.5kimchi — Pick it if you want role-splitting without wiring it yourself; pick a single-model agent if you would rather not debug three models at once.
El Crítico6.36.0Grok Build — Sandboxing is off until you turn it on, and the network half of it is enforced on Linux only, so a macOS session has weaker containment than the docs suggest at a glance.
El Profesor7.06.5Grok Build — Two structural choices carry the design: subagents run as independent child sessions with their own context, and the agent embeds in other editors over the Agent Client Protocol.
La Inversora6.86.0Grok Build — This is a model company's distribution channel wearing an agent's clothes; the product's job is to make its own tokens the default purchase.
La Jefa5.85.0Grok Build — There is no seat price at all: at two dollars per million in and six out, sixty engineers is a meter with no ceiling and no per-person cap.
El Hacker5.57.0kimchi — Apache-2.0, MCP tools attach, and an external provider can replace the built-in models, so the vendor's endpoint is a default rather than a cage.

Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.

Want a third column? The compare tool handles any two agents. Three-way comparisons are on the roadmap once the spec rows are all verified.