[BUG] Task Tool Usage Counter Shows "0 tool uses" Despite Successful Tool Execution
Resolved 💬 3 comments Opened Aug 3, 2025 by leaflessbranch Closed Aug 15, 2025
Summary
The Task tool consistently reports "0 tool uses" in output despite subagents successfully executing multiple tools and returning real-time data.
Expected Behavior
Task tool usage counter should accurately reflect the number of tools executed by subagents.
Actual Behavior
- UI/logs show "0 tool uses" for all subagent invocations
- Users receive false impression that subagents are non-functional
- Counter remains at zero regardless of actual tool execution
Steps to Reproduce
- Create any subagent with
tools: bash, ssh, read, write - Launch subagent via Task tool with request requiring tool execution
- Request specific commands (e.g., "Run:
echo $(date)") - Observe subagent executes commands successfully and returns real data
- Check usage counter shows "0 tool uses"
Environment
- Platform: Linux
- Claude Code Version: 1.0.67
- Reproduction Rate: 100% consistent across multiple subagent types
Evidence of Actual Tool Execution
- ✅ Subagents execute bash commands successfully
- ✅ Real-time data returned with current timestamps
- ✅ SSH connections established and commands run
- ✅ API calls made and fresh data retrieved
- ❌ Usage counter remains at zero
Impact
- User Experience: Confusion about subagent functionality
- Debugging: Difficult to assess actual tool usage
- Trust: False impression of broken functionality
Workaround
Ignore usage counter and evaluate subagent effectiveness based on data quality and freshness.
Additional Context
This appears to be a reporting/logging bug rather than functional issue. Subagents work correctly but metrics are inaccurate.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗