- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper addresses cross-category industrial anomaly detection, where small defects on unfamiliar product types are hard to distinguish from benign appearance variations under a global view. The authors propose IndusAgent, a tool-augmented reinforcement-learning framework built on a Qwen3-VL-8B policy that learns to inspect before deciding. There are six tools: crop, enhancement, geometric measurement, within-image comparison, texture analysis, and an external visual prior queried from Qwen3-VL-Max.
Critical strengths
The framework is supported by a structured dataset that integrates global visual observations, high-resolution local patches, and expert normalcy priors to supervise industrial inspection trajectories.
IndusAgent actively utilizes and coordinates external tools during inspection, including dynamic region cropping, high-frequency feature enhancement and prior retrieval.
The agent's decision-making and tool usage are optimized via a gated reinforcement learning objective that jointly improves anomaly classification, localization accuracy, and reasoning capabilities.
Critical weaknesses
The core performance gains seem to heavily rely on standard visual prompt techniques and basic external tools (e.g., dynamic cropping, high-frequency filtering). The conceptual leap of wrapping these tools in an LLM agent framework for IAD is incremental, and it is unclear whether the complexity of the agentic workflow is strictly necessary compared to simpler, optimized visual prompting baselines.
There lacks a mathematically rigorous formulation of the reward function of Gated Reinforcement Learning. It is unclear how the reward balances pixel-level anomaly localization with categorical reasoning.
The authors evaluate IndusAgent against its base model (QN3VL8B) and general 72B parameter models. They fail to compare the framework against state-of-the-art specialist open-vocabulary and zero-shot IAD models (e.g., WinClip [1], AnomalyCLIP [2], or recent agentic frameworks like AgentIAD [3], AnomalyAgent [4]).
The paper does not provide a detailed comparison with existing agentic anomaly detection methods. How does the proposed approach differ from these methods [3,4], and what advantages does it offer over them?
[1] Jeong, Jongheon, et al. "Winclip: Zero-/few-shot anomaly classification and segmentation." IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR). IEEE, 2023.
[2] Zhou, Qihang, et al. "Anomalyclip: Object-agnostic prompt learning for zero-shot anomaly detection." International Conference on Learning Representations. Vol. 2024. 2024.
[3] Miao, Junwen, et al. "AgentIAD: Agentic Industrial Anomaly Detection via Adaptive Memory Augmentation." arXiv preprint arXiv:2512.13671 (2025).
[4] Zhang, Yi, et al. "AnomalyAgent: Training-Free Agentic Models for Zero-/Few-Shot Anomaly Detection." arXiv preprint arXiv:2605.30140 (2026).
Since the authors employ an LLM for anomaly detection, they should provide experiments to evaluate the generalization ability of the proposed method. However, the paper does not provide any such evaluation.
Questions for authors
Industrial anomaly detection is a well-studied problem. What specific limitations of industrial anomaly detection can be addressed by introducing LLMs or agents? Beyond presenting the work in a relatively well-structured manner, what meaningful contribution does the proposed method make to the field of industrial anomaly detection?
3 comments
Y2: How is the reward formulated, how are its gates evaluated, and how is localization rewarded?
A2: Thank you for asking how the reward treats localization. The full reward is
Here is final diagnostic correctness, localization reward, canonical-type agreement, the successful-call and positive-margin-change indicator, admitted calls, and format reward. Correctness gates auxiliary credit and call cost; format reward remains independent. Localization uses continuous box IoU. The box-IoU threshold of 0.5 used to screen teacher trajectories serves a separate data-selection role. The tool-progress term uses confidence change following a successful observation as a proxy for progress.
We separate positive-credit gating from cost gating using
Y3: How does the method compare with specialist anomaly detectors such as WinCLIP and AnomalyCLIP?
A3: Thanks for suggesting comparisons with specialist detectors. Full improves both detection metrics over the two CLIP-based specialists on the same target sets: 90.1 AUROC / 83.4 BA, compared with 82.6 / 77.9 for WinCLIP and 86.1 / 81.2 for AnomalyCLIP (Table 4). The specialists are substantially faster, taking 0.08 and 0.09 seconds per query versus 1.47 for Full. This comparison shows an accuracy gain at higher inference latency.
Table 4. Specialists and native-style agents
All systems are evaluated on the same target sets. BA thresholds are individually selected on source data, and auxiliary supervision excludes the target product categories. AUROC uses continuous anomaly scores. Each system retains its native backbone and budget; external calls use that system's own service units, not Qwen3-VL-Max-equivalent units. Scores are percentages and means equally weight MVTec-AD, MPDD, VisA, DTD, and SDD. Resources are per query; API charges exclude local computation.
| System | AUROC | BA | Seconds/query | External calls | API CNY/query |
|---|---|---|---|---|---|
| WinCLIP | 82.6 | 77.9 | 0.08 | 0 | 0 |
| AnomalyCLIP | 86.1 | 81.2 | 0.09 | 0 | 0 |
| AnomalyAgent native-style | 90.8 | 84.1 | 4.80 | 2.40 | 0.0240 |
| Full | 90.1 | 83.4 | 1.47 | 0.17 Prior | 0.0006 |
Y4: How does the method compare with existing agents, and what external visual information does it use?
A4: Thank you for bringing up existing agent baselines. AnomalyAgent native-style reaches 90.8 AUROC and 84.1 BA, 0.7 points above Full on both metrics (Table 4). Full takes 1.47 versus 4.80 seconds per query and incurs 0.0006 versus 0.0240 CNY in API charges. It retains closely comparable accuracy with substantially lower latency and API expenditure.
The common-backbone comparison in Table 5 also includes an adapted AgentIAD-style controller: Full reaches 83.4 BA versus 82.2, with 0.17 versus 0.30 Prior calls. Full combines an 8B policy with Qwen3-VL-Max as the query-conditioned Prior. Reference-free inference means that no paired normal exemplars are supplied; the Prior provides external visual information.
Table 5. Controller performance and resources
Trained controllers share Qwen3-VL-8B, accepted source images, supervision/update budgets, preprocessing, and evaluation. Prior-enabled rows use the same interface. Fixed retains SFT/R11/GRPO, learns crop coordinates and Prior focus, and executes one Crop and one Prior. Each controller receives feedback from its own actions. Full has six available tools; Fixed has two. Adapted methods can differ in objectives or tools. Base plus fixed Prior has no industrial training. BA is a percentage averaged equally over the five benchmarks named above. Calls and resources are per query, Prior is Qwen3-VL-Max, and API charges exclude local computation.
| Policy | Mean BA | Local / Prior calls | Seconds/query | API CNY/query |
|---|---|---|---|---|
| IAD-R1-style without Prior | 79.2 | 0 / 0 | 1.07 | 0 |
| IAD-R1-style with Prior | 82.0 | 0 / 1 | 2.58 | 0.0039 |
| AgentIAD-style | 82.2 | 0.65 / 0.30 | 1.68 | 0.00115 |
| Fixed Crop + Prior | 82.6 | 1 / 1 | 2.76 | 0.0038 |
| Base + fixed Prior | 78.8 | 0 / 1 | 2.47 | 0.0037 |
| Full | 83.4 | 0.78 / 0.17 | 1.47 | 0.0006 |
Y5: What kind of generalization does the evaluation establish?
A5: We appreciate the request to clarify the generalization setting. The experiment tests transfer to product categories held out from industrial post-training. Target categories are excluded before trajectory construction, and the canonical defect vocabulary remains fixed. The result therefore concerns product-category transfer within that vocabulary. Novel defect taxonomies, foundation-model pretraining exposure, and changes in acquisition conditions are separate generalization questions beyond this protocol.
Thank you for the detailed feedback on the agent's contribution, comparisons, and generalization.
A1: We appreciate the question about the learned policy's contribution. Our contribution is a learned inspection policy that chooses actions for each image and integrates feedback from their execution. Full reaches 83.4 balanced accuracy (BA), compared with 82.6 for the trained fixed Crop-plus-Prior policy, while using 0.17 versus 1.00 Prior calls per query (Table 1). Latency falls from 2.76 to 1.47 seconds, approximately 46.7%, and API charges fall by 84.2%. Table 2 reports all five benchmarks; the fixed policy is slightly better on MPDD, at 72.8 versus 72.6.
All trained controllers share Qwen3-VL-8B, accepted source images, supervision and update budgets, preprocessing, and evaluation. Prior-enabled configurations use the same Qwen3-VL-Max interface. The fixed controller retains SFT, the full R11 reward, and GRPO. It learns image-dependent crop coordinates and Prior focus, and executes one Crop and one Prior. Each controller receives feedback from its own executed actions.
Full can choose among six tools, whereas the fixed controller uses Crop and Prior. The comparison therefore includes both scheduling and the available tool set. The IAD-R1-style and AgentIAD-style adaptations can also differ in objectives or tool configurations. Base plus fixed Prior has no industrial training. This trained fixed-policy control evaluates an alternative with fixed tool use; tool-removal experiments measure sensitivity to tool availability.
Table 1. Controller performance and resources
BA is a percentage. Means equally weight MVTec-AD, MPDD, VisA, DTD, and SDD. Calls and resource figures are per query. Prior is the external Qwen3-VL-Max component; API charges exclude local computation. The supplementary Full result, 83.4, is reported separately from the manuscript result of 83.5.
Table 2. Per-benchmark balanced accuracy (%)