Code Cushman 001 vs Qwen2.5-72B
Code Cushman 001 (2021) and Qwen2.5-72B (2025) are agentic coding models from OpenAI and Alibaba. Code Cushman 001 ships a not-yet-sourced context window, while Qwen2.5-72B ships a 128k-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.
Qwen2.5-72B is safer overall; choose Code Cushman 001 when coding workflow support matters.
Specs
| Released | 2021-11-03 | 2025-10-10 |
| Context window | — | 128k |
| Parameters | — | 72B |
| Architecture | decoder only | - |
| License | Proprietary | Open Source |
| Knowledge cutoff | - | 2024-09 |
Pricing and availability
| Code Cushman 001 | Qwen2.5-72B | |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers | - | - |
Pricing not yet sourced for either model.
Capabilities
| Code Cushman 001 | Qwen2.5-72B | |
|---|---|---|
| Vision | ||
| Multimodal | ||
| Reasoning | ||
| Function calling | ||
| Tool use | ||
| Structured outputs | ||
| Code execution |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint differs most on function calling: Qwen2.5-72B and tool use: Qwen2.5-72B. 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 Qwen2.5-72B has no token price sourced yet. Provider availability is 0 tracked routes versus 0. 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 Qwen2.5-72B when provider fit 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 Qwen2.5-72B open source?
Code Cushman 001 is listed under Proprietary. Qwen2.5-72B is listed under Open Source. 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 Qwen2.5-72B?
Qwen2.5-72B 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 Qwen2.5-72B?
Qwen2.5-72B 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.
When should I pick Code Cushman 001 over Qwen2.5-72B?
Qwen2.5-72B 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 provider fit, run the same evaluation with Qwen2.5-72B.
Continue comparing
Last reviewed: 2026-04-18. Data sourced from public model cards and provider documentation.