Task tool lacks transparency - missing visibility into sub-tool calls and external requests

Description:

When using the Task tool to spawn an agent for complex investigations, there is
insufficient visibility into the detailed actions taken by the spawned agent. This creates
transparency and reproducibility issues.

Related Issues:

• Issue #3958: Task tool has permission handling problems (CLI crashes)
• Multiple issues mention "Task tool" API errors with missing tool_result blocks
• General Task tool stability concerns noted in search results

Current Behavior:

• Task tool returns only a final summary report
• Sub-tool calls made by the spawned agent (WebFetch, Read, etc.) are not visible to the

primary Claude instance

• External requests (article fetching, web searches) happen without explicit visibility
• User reported that the spawned agent requested permission to fetch articles, but this

interaction is not visible in the conversation history

Expected Behavior:

• Complete visibility into all sub-tool calls made by the Task agent
• Explicit logging of any external requests (WebFetch calls, article downloads, etc.)
• Preservation of the full interaction chain between primary Claude and spawned agent
• User should see all requests for external resource access

Impact:

1. Transparency: Users cannot see what external resources were accessed
2. Reproducibility: Cannot reconstruct the exact steps taken during investigation
3. Trust: "Black box" behavior undermines confidence in the tool
4. Compliance: May violate requirements for audit trails in research contexts
5. Debugging: Impossible to troubleshoot Task tool issues without execution visibility

Reproduction Steps:

1. Use Task tool for investigation requiring external resources
2. Spawned agent makes WebFetch calls or requests article access
3. Only final summary is returned, detailed steps are hidden

Proposed Solution:

• Include detailed execution log showing all sub-tool calls
• Make external resource requests explicit and visible
• Preserve full conversation chain between primary and spawned agents
• Add option to show/hide detailed execution steps for user preference
• Consider this enhancement alongside fixing existing Task tool stability issues

Environment:

• Claude Code interactive mode
• Task tool with WebFetch, Read, and other sub-tools

Additional Context:
This transparency issue was discovered during dose-response analysis work where the user
observed that articles were requested and potentially fetched, but no record of these
requests exists in the visible conversation history. Given the existing Task tool issues
noted in #3958 and related API problems, improving transparency would also aid in debugging
these stability concerns.