Browse 41 harnesses

30-day usage· Aug 12–Sep 10, 2026

Data as of September 11, 2026 · About the data
Rank #19#15 of21CLI agents · 7-day #20
Tokens 100.1B
Requests 895K

Capabilities and verification

Reviewed against the HarnessRouter capability catalog onAugust 24, 2026. Every verified row cites its public source; rule-derived rows apply HarnessRouter's published classification rules to documented behavior. A “No public evidence” badge marks a gap in the public record, not a statement thatCrush lacks them.

Configuration & support

• Other models Directly verified
• Custom instructions Directly verified
• Skills Directly verified
• Custom tools No public evidence
• MCP Directly verified
• Sandbox & approvals Directly verified
• Sessions Directly verified
• Subagents Directly verified

Execution & agency

• Workspace files Directly verified
• Structured actions Directly verified

Environment control

• Browser control No public evidence
• Computer control No public evidence

Observation & capture

• Screen observation No public evidence
• Screenshot export No public evidence
• Recording export No public evidence

Artifact outputs

• Documents Rule-derived
• Spreadsheets Rule-derived
• Presentations Rule-derived
• Images Rule-derived
• Video Rule-derived
• App deployment No public evidence

Sources:github.com

Machine interfaces

• API ·Stable

Related harnesses

Nearest CLI agents by usage rank in the same 30-day window.

• Compare with Qwen Code, #13CLI agent
• Compare with MiMo Code, #14CLI agent
• Compare with PostQode, #16CLI agent
• See the full usage rankings

Want Crush supported throughUHPUnified Harness Protocol defines a shared contract for running agent harnesses through one interface. A compatible implementation lets HarnessRouter support this harness without changing your product integration.?

Join the HarnessRouter Discord and post an implementation request in #unified-harness-protocol. Tell us the real task you want to run. Do not include private task data.
Join Discord to request support