Code Cushman 001 vs ShieldGemma 9B
Code Cushman 001 (2021) and ShieldGemma 9B (2024) are agentic coding models from OpenAI and Google DeepMind. Code Cushman 001 ships a not-yet-sourced context window, while ShieldGemma 9B ships a 8K-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.
ShieldGemma 9B is safer overall; choose Code Cushman 001 when coding workflow support matters.
Specs
| Released | 2021-11-03 | 2024-07-01 |
| Context window | — | 8K |
| Parameters | — | 9B |
| Architecture | decoder only | decoder only |
| License | Proprietary | 1 |
| Knowledge cutoff | - | - |
Pricing and availability
| Code Cushman 001 | ShieldGemma 9B | |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers | - |
Pricing not yet sourced for either model.
Capabilities
| Code Cushman 001 | ShieldGemma 9B | |
|---|---|---|
| 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 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 ShieldGemma 9B has no token price sourced yet. 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 ShieldGemma 9B 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 ShieldGemma 9B open source?
Code Cushman 001 is listed under Proprietary. ShieldGemma 9B is listed under 1. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.
Where can I run Code Cushman 001 and ShieldGemma 9B?
Code Cushman 001 is available on the tracked providers still being sourced. ShieldGemma 9B is available on NVIDIA NIM. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
When should I pick Code Cushman 001 over ShieldGemma 9B?
ShieldGemma 9B 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 ShieldGemma 9B.
What is the main difference between Code Cushman 001 and ShieldGemma 9B?
Code Cushman 001 and ShieldGemma 9B 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-04-18. Data sourced from public model cards and provider documentation.