LLM Reference

Code Cushman 001 vs Grok Build 0.1

Code Cushman 001 (2021) and Grok Build 0.1 (2026) are agentic coding models from OpenAI and xAI. Code Cushman 001 ships a not-yet-sourced context window, while Grok Build 0.1 ships a 256k-token context window. This comparison covers specs, pricing, capabilities, benchmarks, provider availability, and production fit. It focuses on practical selection signals rather than broad model-family marketing. The goal is to make the tradeoff clear before deeper testing.

Grok Build 0.1 is safer overall; choose Code Cushman 001 when coding workflow support matters.

Decision scorecard

Local evidence first
SignalCode Cushman 001Grok Build 0.1
Best forcustom coding agents and code generationcustom coding agents, code generation, and tool loops
Decision fitCodingCoding, RAG, and Agents
Context window256k
Cheapest output-$2/1M tokens
Provider routes0 tracked3 tracked
Shared benchmarks0 rows0 rows

Decision tradeoffs

Choose Code Cushman 001 when...
  • Local decision data tags Code Cushman 001 for Coding.
Choose Grok Build 0.1 when...
  • Grok Build 0.1 has the larger context window for long prompts, retrieval packs, or transcript analysis.
  • Grok Build 0.1 has broader tracked provider coverage for fallback and procurement flexibility.
  • Grok Build 0.1 uniquely exposes Reasoning, Function calling, and Tool use in local model data.
  • Local decision data tags Grok Build 0.1 for Coding, RAG, and Agents.

Monthly cost at traffic

Estimate token spend from the cheapest tracked input and output route or tier on this page.

Code Cushman 001

Unavailable

No complete token price in local provider data

Grok Build 0.1

$1,300

Cheapest tracked route/tier: xAI Console

Cost delta unavailable until both models have sourced input and output token prices.

Switch friction

Code Cushman 001 -> Grok Build 0.1
  • No overlapping tracked provider route is sourced for Code Cushman 001 and Grok Build 0.1; plan for SDK, billing, or endpoint changes.
  • Grok Build 0.1 adds Reasoning, Function calling, and Tool use in local capability data.
Grok Build 0.1 -> Code Cushman 001
  • No overlapping tracked provider route is sourced for Grok Build 0.1 and Code Cushman 001; plan for SDK, billing, or endpoint changes.
  • Check replacement coverage for Reasoning, Function calling, and Tool use before moving production traffic.

Specs

Specification
Released2021-11-032026-05-14
Context window256k
Parameters
Architecturedecoder only-
LicenseProprietaryProprietary
Knowledge cutoff--

Pricing and availability

Pricing attributeCode Cushman 001Grok Build 0.1
Input price-
0-200,001t
$1/1M tokens
200,001t+
$2/1M tokens
Output price-
0-200,001t
$2/1M tokens
200,001t+
$4/1M tokens
Providers-

Capabilities

CapabilityCode Cushman 001Grok Build 0.1
VisionNoNo
MultimodalNoNo
ReasoningNoYes
Function callingNoYes
Tool useNoYes
Structured outputsNoYes
Code executionNoNo
IDE integrationNoNo
Computer useNoNo
Parallel agentsNoNo

Benchmarks

No shared benchmark rows are currently sourced for this pair.

Deep dive

The capability footprint differs most on reasoning mode: Grok Build 0.1, function calling: Grok Build 0.1, tool use: Grok Build 0.1, and structured outputs: Grok Build 0.1. Both models share the core language-model surface, so the practical split is not just feature count. Use those differences to decide whether the page is about raw model quality, agentic coding support, multimodal ingestion, or predictable structured API behavior.

Pricing coverage is uneven: Code Cushman 001 has no token price sourced yet and Grok Build 0.1 has $1/1M input tokens. Provider availability is 0 tracked routes versus 3. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.

Choose Code Cushman 001 when coding workflow support are central to the workload. Choose Grok Build 0.1 when coding workflow support and broader provider choice are more important. For production, rerun your own prompts through the exact provider, region, and tool stack you plan to ship. This keeps the decision grounded in measurable tradeoffs instead of brand-level assumptions. It also helps separate model capability from provider packaging, which can change cost and latency.

FAQ

Is Code Cushman 001 or Grok Build 0.1 open source?

Code Cushman 001 is listed under Proprietary. Grok Build 0.1 is listed under Proprietary. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.

Which is better for reasoning mode, Code Cushman 001 or Grok Build 0.1?

Grok Build 0.1 has the clearer documented reasoning mode signal in this comparison. If reasoning mode is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Which is better for function calling, Code Cushman 001 or Grok Build 0.1?

Grok Build 0.1 has the clearer documented function calling signal in this comparison. If function calling is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Which is better for tool use, Code Cushman 001 or Grok Build 0.1?

Grok Build 0.1 has the clearer documented tool use signal in this comparison. If tool use is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Which is better for structured outputs, Code Cushman 001 or Grok Build 0.1?

Grok Build 0.1 has the clearer documented structured outputs signal in this comparison. If structured outputs is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Where can I run Code Cushman 001 and Grok Build 0.1?

Code Cushman 001 is available on the tracked providers still being sourced. Grok Build 0.1 is available on xAI Console, Vercel AI Gateway, and OpenRouter. Provider coverage can affect latency, region availability, compliance posture, and fallback options.

Continue comparing

Last reviewed: 2026-05-25. Data sourced from public model cards and provider documentation.