RealCLI: Toward a Unified Evaluation of Human-Agent Collaboration for CLI Agents
Organizations: IQuest Research · Beihang University · Renmin University
Abstract
Command-line interface (CLI) agents increasingly execute longer-horizon tasks, yet existing benchmarks either assume that user instructions remain fixed throughout execution or evaluate task outcomes without capturing runtime collaboration quality. In this paper, we present REALCLI, a paired benchmark that unifies the evaluation of task execution and human-agent collaboration quality on realistic CLI tasks. To comprehensively measure collaboration, REALCLI builds a five-dimensional framework, operationalized into 22 sub-dimensions and 51 interaction scenario templates. REALCLI provides two modes for paired comparison: REALCLI-EXEC supplies complete specifications upfront, whereas REALCLI-COLLAB introduces a scripted user that delivers progressive information, corrections, constraint revisions, and authorization decisions. Evaluations reveal profound capability gaps in frontier agents: the best configuration attains an average score of only 49.2%, and when evaluated by the joint collaboration score (), the peak performance reaches merely 37.6%. These results show that task effectiveness diverges sharply from collaboration quality, with models consistently struggling in steerability, trust calibration, and safety boundary management. REALCLI provides a rigorous, reproducible foundation for measuring and advancing collaborative CLI agents.
Figures & tables
| Benchmark | Ver. | User | Pair | Und | Ste | Obs | Tru | Saf |
|---|---|---|---|---|---|---|---|---|
| SWE-bench ( Jimenez et al., 2023 ) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Ambig-SWE ( Vijayvargiya et al., 2025 ) | ✓ | ✓ | ✓ | ✗ | ✓ | ✗ | ✗ | ✗ |
| Terminal-Bench ( Merrill et al., 2026 ) | ✓ | ✗ | ✗ | ✗ | ✗ | (✓) | (✓) | ✗ |
| LongCLI-Bench ( Feng et al., 2026 ) | ✓ | (✓) | (✓) | ✗ | (✓) | (✓) | ✗ | ✗ |
| Dialogue SWE-Bench ( King and Flanigan, 2026 ) | ✓ | ✓ | ✗ | (✓) | ✓ | ✗ | ✗ | ✗ |
| SWE-Together ( Wu et al., 2026 ) | ✓ | ✓ | ✗ | ✗ | (✓) | ✗ | ✗ | ✗ |
| Dimension | Evaluation focus | Sub. / Tpl. |
|---|---|---|
| U nderstandability (U) | Legibility of plans, execution state, and outcomes | 4 / 12 |
| S teerability (S) | User intervention, redirection, and constraint persistence | 5 / 11 |
| O bservation & R ecovery (OR) | State verification and recovery from failures | 3 / 9 |
| T rust C alibration (TC) | Accurate disclosure of risks, limits, and task status | 5 / 12 |
| S afety & R isk Awareness (SR) | User control over high-impact or unauthorized actions | 5 / 13 |
| Model | Claude Code | Terminus-2 | Codex | Avg. | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Closed-source models | ||||||||||
| Claude Opus 5 | 58.2 | 58.4 +0.2 | 27.4 -30.8 | 65.4 | 62.4 -3.0 | 37.6 -27.9 | 46.5 | 55.5 +9.0 | 31.5 -15.0 | 49.2 |
| Claude Opus 4.8 | 54.5 | 53.5 -1.0 | 18.3 -36.3 | 52.5 | 53.5 +1.0 | 21.1 -31.4 | 40.6 | 50.0 +9.4 | 23.0 -17.6 | 40.8 |
| GPT-5.6 Sol | 44.6 | 45.5 +0.9 | 6.7 -37.9 | 51.5 | 47.5 -4.0 | 9.1 -42.4 | 58.5 | 49.5 -9.0 | 8.5 -50.0 | 35.7 |
| Open-source models | ||||||||||
| Model | Claude Code | Terminus-2 | Codex | Avg. | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| U S OR TC SR | U S OR TC SR | U S OR TC SR | ||||||||
| Closed-source models | ||||||||||
| Claude Opus 5 | 46.9 | 27.4 | 50 20 78 43 43 | 60.2 | 37.6 | 85 40 89 43 43 | 56.8 | 31.5 | 60 30 100 33 60 | 32.1 |
| Claude Opus 4.8 | 34.1 | 18.3 | 56 10 44 23 37 | 39.4 | 21.1 | 42 30 56 23 47 | 43.4 | 23.0 | 63 30 44 43 37 | 20.8 |
| GPT-5.6 Sol | 14.7 | 6.7 | 29 10 11 13 10 | 19.1 | 9.1 | 48 30 11 7 0 | 17.1 | 8.5 | 48 20 11 7 0 | 8.1 |
| Open-source models | ||||||||||
Appendix figures & tables3 assets
Supplementary material from the paper’s appendix.
Appendix
| Dimension | Subdimension | Scenarios | Tasks |
|---|---|---|---|
| Understandability | Plan transparency | 2 | 25 |
| Feedback granularity and timing | 3 | 34 | |
| Error presentation | 2 | 35 | |
| Operation economy | 1 | 17 | |
| Steerability | Interruptibility | 2 | 19 |
| Clarification behavior | 2 | 22 |
| Type | Scenario Condition & Expected Behavior |
|---|---|
| Dimension 1: Understandability | |
| 1.1 Plan transparency | |
| Probe | Hidden complexity: User understates task complexity. Expected: Agent discovers hidden couplings and explicitly updates its plan before acting. |
| Probe | Execution deviation: Plan fails due to errors/limits. Expected: Agent updates the plan and informs the user. |
| Passive | Trivial task: The task is simple and unambiguous. Expected: Agent avoids generating a lengthy, disproportionate plan. |
| 1.2 Feedback granularity and timing | |
| Category | Sub. | Representative Task Scope | Subdomain | Tasks |
|---|---|---|---|---|
| System Operations | 9 | Files, processes and services, environments and dependencies, containers, networks, cloud resources, permissions, cleanup, and scheduling | Cloud Resource Management | 1 |
| Container Orchestration | 2 | |||
| Environment & Dependencies | 2 | |||
| File Management | 2 | |||
| Network Service Development | 1 | |||
| Permission Management | 1 |