Code Cushman 001 vs Composer 2
Code Cushman 001 (2021) and Composer 2 (2026) are agentic coding models from OpenAI and Cursor (Anysphere). Code Cushman 001 ships a not-yet-sourced context window, while Composer 2 ships a 200K-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.
Composer 2 is safer overall; choose Code Cushman 001 when coding workflow support matters.
Decision scorecard
Local evidence first| Signal | Code Cushman 001 | Composer 2 |
|---|---|---|
| Decision fit | Coding | Coding, RAG, and Agents |
| Context window | — | 200K |
| Cheapest output | - | $2.5/1M tokens |
| Provider routes | 0 tracked | 1 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Local decision data tags Code Cushman 001 for Coding.
- Composer 2 has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Composer 2 has broader tracked provider coverage for fallback and procurement flexibility.
- Composer 2 uniquely exposes Function calling, Tool use, and Code execution in local model data.
- Local decision data tags Composer 2 for Coding, RAG, and Agents.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output prices on this page.
Code Cushman 001
Unavailable
No complete token price in local provider data
Composer 2
$1,025
Cheapest tracked route: Cursor
Cost delta unavailable until both models have sourced input and output token prices.
Switch friction
- No overlapping tracked provider route is sourced for Code Cushman 001 and Composer 2; plan for SDK, billing, or endpoint changes.
- Composer 2 adds Function calling, Tool use, and Code execution in local capability data.
- No overlapping tracked provider route is sourced for Composer 2 and Code Cushman 001; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Function calling, Tool use, and Code execution before moving production traffic.
Specs
| Specification | ||
|---|---|---|
| Released | 2021-11-03 | 2026-03-19 |
| Context window | — | 200K |
| Parameters | — | — |
| Architecture | decoder only | - |
| License | Proprietary | Proprietary |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Code Cushman 001 | Composer 2 |
|---|---|---|
| Input price | - | $0.5/1M tokens |
| Output price | - | $2.5/1M tokens |
| Providers | - |
Capabilities
| Capability | Code Cushman 001 | Composer 2 |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| Function calling | No | Yes |
| Tool use | No | Yes |
| Structured outputs | No | No |
| Code execution | No | Yes |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint differs most on function calling: Composer 2, tool use: Composer 2, and code execution: Composer 2. 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 Composer 2 has $0.5/1M input tokens. Provider availability is 0 tracked routes versus 1. 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 Composer 2 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. For teams standardizing a stack, that distinction is often the difference between a benchmark win and a reliable deployment.
FAQ
Is Code Cushman 001 or Composer 2 open source?
Code Cushman 001 is listed under Proprietary. Composer 2 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 function calling, Code Cushman 001 or Composer 2?
Composer 2 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 Composer 2?
Composer 2 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 code execution, Code Cushman 001 or Composer 2?
Composer 2 has the clearer documented code execution signal in this comparison. If code execution 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 Composer 2?
Code Cushman 001 is available on the tracked providers still being sourced. Composer 2 is available on Cursor. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
When should I pick Code Cushman 001 over Composer 2?
Composer 2 is safer overall; choose Code Cushman 001 when coding workflow support matters. If your workload also depends on coding workflow support, start with Code Cushman 001; if it depends on coding workflow support, run the same evaluation with Composer 2.
Continue comparing
Last reviewed: 2026-05-19. Data sourced from public model cards and provider documentation.