PhoneHarness: Harnessing Phone-Use Agents through Mixed GUI, CLI, and Tool Actions
Authors: name: Chenxin Li, name: Zhengyao Fang, name: Zhengyang Tang, name: Pengyuan Lyu, name: Xingran Zhou, name: Xin Lai, name: Fei Tang, name: Liang Wu, name: Yiduo Guo, name: Weinong Wang, name: Junyi Li, name: Yi Zhang, name: Yang Ding, name: Huawen Shen, name: Sunqi Fan, name: Shangpin Peng, name: Zheng Ruan, name: Anran Zhang, name: Benyou Wang, name: Chengquan Zhang, name: Han Hu

Phone agents are increasingly expected to complete real mobile workflows rather than merely predict the next screen action. However, much of the current mobile-agent literature still evaluates agents primarily as GUI controllers that observe a screen, emit taps and swipes, and are scored by target app state. Real phone-use tasks are broader: they require deciding when to use app GUIs, device-side commands, or structured tools, while leaving evidence that the intended side effect actually occurred. We introduce PhoneHarness, a mixed-action benchmark and execution harness for studying phone-use agents on verifiable mobile workflows. PhoneHarness runs a device-side agent loop over GUI, CLI, and host-side tool actions, combining deterministic action routing with bounded GUI delegation and auditable execution traces. Its benchmark, PhoneHarness Bench, evaluates whether agents complete tasks with observable side effects, not only whether they produce plausible final answers. On the annotated evaluation split, PhoneHarness reaches a 75.0% pass rate, outperforming the strongest non-PhoneHarness settings by 12.9 percentage points. PhoneHarness and PhoneHarness Bench therefore play distinct but mutually dependent roles: the harness makes mixed phone workflows executable, while the benchmark measures whether agents can use that harness reliably and safely. Our findings suggest that reliable phone automation depends on action-surface routing and verifiable execution, not only visual GUI control.