Command A vs Helix 02

At a Glance

Compare
Command ACohere
Helix 02Figure
Pricing and Limits
Context windowMaximum documented tokens256KNot reported
Model facts checkedAug 29, 2026View model evidence →Aug 29, 2026View model evidence →
Different Model RolesThese models do not share a sourced market category. Their primary-source facts remain comparable below, while performance claims require matched evidence.

Available Benchmarks

All benchmark results →
No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.

Side-by-Side Facts

FieldCommand AHelix 02
DeveloperCohereFigure
FamilyCommand AHelix
ModelCommand AHelix 02
VersionCommand A02
Lifecycleactiveactive
ReleasedUnknown2026-01-05
Knowledge cutoff2024-06-01Unknown
Input modalitiesTextText, Image, Robot state
Output modalitiesTextRobot action
Context window256KUnknown
Total parameters111BUnknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableYesNo
Self-hostableNoNo
Provider accessCohere (Standard)Unknown
Capabilitiesagents, chat, citations, multilingual, rag, structured_outputs, toolsdexterous-manipulation, long-horizon-control, tactile-control, whole-body-control
Robotics model typeUnknownVision-language-action model
Action representationUnknownFull-body joint targets
Control architectureUnknownSemantic reasoning, visuomotor policy, and kHz whole-body controller
Inference locationUnknownOn device
Native control rate (Hz)UnknownUnknown
Supported embodimentsUnknownFigure 03
Training dataUnknownFigure reports more than 1,000 hours of human motion data plus sim-to-real reinforcement learning for its whole-body controller.

Command A Capabilities

agentschatcitationsmultilingualragstructured outputstools
Model typeUnknown
InferenceUnknown
Action representationUnknown
Supported embodimentsUnknown
Canonical IDcoherelabs/command-a-03-2025

Helix 02 Capabilities

dexterous-manipulationlong-horizon-controltactile-controlwhole-body-control
Model typeVision-language-action model
InferenceOn device
Action representationFull-body joint targets
Supported embodiments1
Canonical IDfigure/helix-02

Primary Evidence

Sources and Freshness

Questions

Command A vs Helix 02 FAQs

Is Command A or Helix 02 better for coding?+

This comparison does not currently contain a protocol-matched coding benchmark for both Command A and Helix 02, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Which is cheaper, Command A or Helix 02?+

Only Command A has a directly sourced input price: $2.50 per million tokens. Only Command A has a directly sourced output price: $10.00 per million tokens.

Which has a larger context window, Command A or Helix 02?+

Neither model has a larger sourced context window in this comparison. Command A is 256K and Helix 02 is —.

Which performs better in benchmarks, Command A or Helix 02?+

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Can Command A or Helix 02 be self-hosted?+

Both models have the same recorded self-hosting status: unsupported. Command A is not marked open weight; Helix 02 is not marked open weight.

Can Command A and Helix 02 understand images?+

Command A is not documented with image input; Helix 02 is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Command A or Helix 02?+

Neither has a larger sourced maximum output. Command A is 8K and Helix 02 is —.

Do Command A and Helix 02 support reasoning and tool use?+

Command A: tool calling. Helix 02: image input. Feature support does not establish relative quality.

Which is available from more inference providers, Command A or Helix 02?+

Command A has 1 sourced provider route; Helix 02 has 0, so Command A has broader tracked availability.

Which offers better value, Command A or Helix 02?+

There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.

Send Feedback