Separate model capability from harness and system-design effects
Determine whether the observed capability gap between the Kimi K2.5 legacy human-in-the-loop PentestGPT system and the Claude Opus 4.8 autonomous PentestGPT system is caused by model capability, harness design, execution paradigm, autonomy, memory architecture, or their interaction.
References
We cannot say whether the model or the harness accounts for the gap.
We compare with two baselines, Step-wise VLM and SeeAct-V, but have not tested the Jev-Mobile workflow with Jev replaced by a small VLM; that comparison would clarify whether the observed behavior depends on typed decision-model execution or on the delegated workflow more generally.
The deepest caveat is inherited from \S\ref{sec:incident2}: whether the harness causes the scores, versus the models alone, is unmeasured until a boundary-correct ablation is run.
A factorial comparison is therefore left to future work.
WebDevJudge~\citep{webdevjudge2025}, which benchmarks LLM and multimodal judges for web development, illustrates the importance of understanding these capabilities as it finds that its standalone GUI-agent workflow actually underperforms its strongest static judges due to errors arising during planning and execution.
It remains unclear whether further gains should be sought primarily through better use of available information and tools, through additional inference (for example, in a multi-agent system), or through a combination of the two. Further analysis is needed to determine their relative contributions and whether they can be meaningfully separated.