Code Cushman 001 vs K-EXAONE 236B-A23B
Code Cushman 001 (2021) and K-EXAONE 236B-A23B (2025) are agentic coding models from OpenAI and LG Research. Code Cushman 001 ships a not-yet-sourced context window, while K-EXAONE 236B-A23B 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.
K-EXAONE 236B-A23B is safer overall; choose Code Cushman 001 when coding workflow support matters.
Decision scorecard
Local evidence first| Signal | Code Cushman 001 | K-EXAONE 236B-A23B |
|---|---|---|
| Decision fit | Coding | Long context |
| Context window | — | 256k |
| Cheapest output | - | - |
| Provider routes | 0 tracked | 0 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Local decision data tags Code Cushman 001 for Coding.
- K-EXAONE 236B-A23B has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Local decision data tags K-EXAONE 236B-A23B for Long context.
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
K-EXAONE 236B-A23B
Unavailable
No complete token price in local provider data
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 K-EXAONE 236B-A23B; plan for SDK, billing, or endpoint changes.
- No overlapping tracked provider route is sourced for K-EXAONE 236B-A23B and Code Cushman 001; plan for SDK, billing, or endpoint changes.
Specs
| Specification | ||
|---|---|---|
| Released | 2021-11-03 | 2025-12-31 |
| Context window | — | 256k |
| Parameters | — | 236B |
| Architecture | decoder only | MoE |
| License | Proprietary | Open Source |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Code Cushman 001 | K-EXAONE 236B-A23B |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers | - | - |
Pricing not yet sourced for either model.
Capabilities
| Capability | Code Cushman 001 | K-EXAONE 236B-A23B |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| Function calling | No | No |
| Tool use | No | No |
| Structured outputs | No | No |
| Code execution | No | No |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint is close: both models cover the core production surface. That makes context budget, benchmark fit, and provider maturity more important than a simple checklist. If your application depends on one integration detail, verify it against the provider route you plan to use, not just the base model listing.
Pricing coverage is uneven: Code Cushman 001 has no token price sourced yet and K-EXAONE 236B-A23B 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 K-EXAONE 236B-A23B 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 K-EXAONE 236B-A23B open source?
Code Cushman 001 is listed under Proprietary. K-EXAONE 236B-A23B 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.
When should I pick Code Cushman 001 over K-EXAONE 236B-A23B?
K-EXAONE 236B-A23B 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 K-EXAONE 236B-A23B.
What is the main difference between Code Cushman 001 and K-EXAONE 236B-A23B?
Code Cushman 001 and K-EXAONE 236B-A23B differ most on context, provider coverage, capabilities, or pricing depending on the data currently sourced. Use the specs table first, then validate the model behavior with your own prompts.
Continue comparing
Last reviewed: 2026-05-10. Data sourced from public model cards and provider documentation.