Code Cushman 001 vs OpenAI GPT OSS Safeguard 120B
Code Cushman 001 (2021) and OpenAI GPT OSS Safeguard 120B (2025) are agentic coding models from OpenAI. Code Cushman 001 ships a not-yet-sourced context window, while OpenAI GPT OSS Safeguard 120B ships a not-yet-sourced 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.
OpenAI GPT OSS Safeguard 120B is safer overall; choose Code Cushman 001 when coding workflow support matters.
Decision scorecard
Local evidence first| Signal | Code Cushman 001 | OpenAI GPT OSS Safeguard 120B |
|---|---|---|
| Decision fit | Coding | Classification and JSON / Tool use |
| Context window | — | — |
| Cheapest output | - | $0.6/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.
- OpenAI GPT OSS Safeguard 120B has broader tracked provider coverage for fallback and procurement flexibility.
- OpenAI GPT OSS Safeguard 120B uniquely exposes Structured outputs in local model data.
- Local decision data tags OpenAI GPT OSS Safeguard 120B for Classification and JSON / Tool use.
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
OpenAI GPT OSS Safeguard 120B
$270
Cheapest tracked route: AWS Bedrock
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 OpenAI GPT OSS Safeguard 120B; plan for SDK, billing, or endpoint changes.
- OpenAI GPT OSS Safeguard 120B adds Structured outputs in local capability data.
- No overlapping tracked provider route is sourced for OpenAI GPT OSS Safeguard 120B and Code Cushman 001; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Structured outputs before moving production traffic.
Specs
| Specification | ||
|---|---|---|
| Released | 2021-11-03 | 2025-09-01 |
| Context window | — | — |
| Parameters | — | — |
| Architecture | decoder only | - |
| License | Proprietary | Proprietary |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Code Cushman 001 | OpenAI GPT OSS Safeguard 120B |
|---|---|---|
| Input price | - | $0.15/1M tokens |
| Output price | - | $0.6/1M tokens |
| Providers | - |
Capabilities
| Capability | Code Cushman 001 | OpenAI GPT OSS Safeguard 120B |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| Function calling | No | No |
| Tool use | No | No |
| Structured outputs | No | Yes |
| Code execution | No | No |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint differs most on structured outputs: OpenAI GPT OSS Safeguard 120B. 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 OpenAI GPT OSS Safeguard 120B has $0.15/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 OpenAI GPT OSS Safeguard 120B when provider fit 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 OpenAI GPT OSS Safeguard 120B open source?
Code Cushman 001 is listed under Proprietary. OpenAI GPT OSS Safeguard 120B 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 structured outputs, Code Cushman 001 or OpenAI GPT OSS Safeguard 120B?
OpenAI GPT OSS Safeguard 120B 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 OpenAI GPT OSS Safeguard 120B?
Code Cushman 001 is available on the tracked providers still being sourced. OpenAI GPT OSS Safeguard 120B is available on AWS Bedrock. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
When should I pick Code Cushman 001 over OpenAI GPT OSS Safeguard 120B?
OpenAI GPT OSS Safeguard 120B 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 OpenAI GPT OSS Safeguard 120B.
Continue comparing
Last reviewed: 2026-05-11. Data sourced from public model cards and provider documentation.