[DOCS] Discrepancy in documentation: Reference to non-existent built-in subagent "Verify" in IAM guide
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/iam
Section/Topic
The Task (Subagents) section within the Identity and Access Management documentation.
Current Documentation
Under the Task (Subagents) heading, the documentation states:
UseTask(AgentName)rules to control which subagents Claude can use: -Task(Explore)Matches the Explore subagent -Task(Plan)Matches the Plan subagent -Task(Verify)Matches the Verify subagent
What's Wrong or Missing?
The IAM guide lists Task(Verify) as an example of a built-in subagent that can be controlled via permission rules. However, the dedicated subagents guide (https://code.claude.com/docs/en/sub-agents), which explicitly defines all built-in agents, does not list a "Verify" agent.
The subagent guide only defines:
- Explore
- Plan
- General-purpose
- Helpers like Bash, statusline-setup, and Claude Code Guide.
There is no mention of a "Verify" subagent in the feature overview, leading to confusion about whether this is a hidden built-in feature or a hallucination/legacy leftover in the documentation.
Suggested Improvement
If the "Verify" subagent does not exist as a built-in tool, it should be removed from the IAM examples to prevent user confusion.
Suggested replacement text for the IAM guide:
UseTask(AgentName)rules to control which subagents Claude can use: -Task(Explore)Matches the Explore subagent -Task(Plan)Matches the Plan subagent -Task(general-purpose)Matches the general-purpose subagent
Impact
High - Prevents users from using a feature
Additional Context
- Reference link for IAM: https://code.claude.com/docs/en/iam#tool-specific-permission-rules
- Reference link for Built-in Subagents: https://code.claude.com/docs/en/sub-agents#built-in-subagents
- This discrepancy makes it difficult for users to know which built-in agents they should proactively manage via
settings.json.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗