Code Cushman 002 vs Gemini 3.5 Pro
Code Cushman 002 (2021) and Gemini 3.5 Pro (2026) compare a coding-specialized model against a standalone API model. Code Cushman 002 ships a not-yet-sourced context window, while Gemini 3.5 Pro ships a 2m-token context window. This page treats the result as workflow and deployment fit, not a universal model winner.
Treat this as a product-type comparison: Code Cushman 002 is coding-specialized model, while Gemini 3.5 Pro is standalone API model. Choose based on workflow fit before reading any benchmark or price row as decisive.
Decision scorecard
Local evidence first| Signal | Code Cushman 002 | Gemini 3.5 Pro |
|---|---|---|
| Product type | Coding-specialized model | Standalone API model |
| Best for | custom coding agents and code generation | reasoning-heavy apps, multimodal apps, and long-context analysis |
| Decision fit | Coding | Long context and Vision |
| Context window | — | 2m |
| Cheapest output | - | - |
| Provider routes | 0 tracked | 0 tracked |
| Shared benchmarks | 0 shared | 0 shared |
Decision tradeoffs
- Local decision data tags Code Cushman 002 for Coding.
- Gemini 3.5 Pro has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Gemini 3.5 Pro uniquely exposes Vision, Multimodal, and Reasoning in local model data.
- Local decision data tags Gemini 3.5 Pro for Long context and Vision.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
Code Cushman 002
Unavailable
No complete token price in local provider data
Gemini 3.5 Pro
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 002 and Gemini 3.5 Pro; plan for SDK, billing, or endpoint changes.
- Gemini 3.5 Pro adds Vision, Multimodal, and Reasoning in local capability data.
- No overlapping tracked provider route is sourced for Gemini 3.5 Pro and Code Cushman 002; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Vision, Multimodal, and Reasoning before moving production traffic.
Specs
| Specification | ||
|---|---|---|
| Released | 2021-11-15 | 2026-05-19 |
| Context window | — | 2m |
| Parameters | — | — |
| Architecture | Decoder Only | - |
| License | Proprietary | Proprietary |
| Openness | Proprietary | Proprietary |
| Commercial use | Commercial use: conditional | Commercial use: conditional |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Code Cushman 002 | Gemini 3.5 Pro |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers | - | - |
Pricing not yet sourced for either model.
Capabilities
| Capability | Code Cushman 002 | Gemini 3.5 Pro |
|---|---|---|
| Vision | No | Yes |
| Multimodal | No | Yes |
| Reasoning | No | Yes |
| Function calling | No | No |
| Tool use | No | No |
| Structured outputs | No | No |
| Code execution | No | No |
| IDE integration | No | No |
| Computer use | No | No |
| Parallel agents | No | No |
Benchmarks
No shared benchmark scores are currently available for this pair.
Deep dive
The capability footprint differs most on vision: Gemini 3.5 Pro, multimodal input: Gemini 3.5 Pro, and reasoning mode: Gemini 3.5 Pro. 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 002 has no token price sourced yet and Gemini 3.5 Pro 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 002 when coding workflow support are central to the workload. Choose Gemini 3.5 Pro when reasoning depth 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 002 or Gemini 3.5 Pro open source?
Code Cushman 002 is listed under Proprietary. Gemini 3.5 Pro 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 vision, Code Cushman 002 or Gemini 3.5 Pro?
Gemini 3.5 Pro has the clearer documented vision signal in this comparison. If vision is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for multimodal input, Code Cushman 002 or Gemini 3.5 Pro?
Gemini 3.5 Pro has the clearer documented multimodal input signal in this comparison. If multimodal input is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for reasoning mode, Code Cushman 002 or Gemini 3.5 Pro?
Gemini 3.5 Pro has the clearer documented reasoning mode signal in this comparison. If reasoning mode 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 002 over Gemini 3.5 Pro?
Treat this as a product-type comparison: Code Cushman 002 is coding-specialized model, while Gemini 3.5 Pro is standalone API model. Choose based on workflow fit before reading any benchmark or price row as decisive. If your workload also depends on coding workflow support, start with Code Cushman 002; if it depends on reasoning depth, run the same evaluation with Gemini 3.5 Pro.
Continue comparing
Last reviewed: 2026-06-20. Data sourced from public model cards and provider documentation.