[FEATURE] Auto-allow access to Claude Code's internal task output files
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Problem
When using the Task tool to run background agents, reading the output file (e.g., via Read tool or TaskOutput tool) requires explicit user permission, even when:
The file is located in Claude Code's own temporary directory (AppData/Local/Temp/claude/...)
The file was generated by Claude Code itself during the same session
The user has already set "defaultMode": "bypassPermissions" in their settings
This creates unnecessary friction when working with background tasks, as users must manually approve reading files that Claude Code itself created.
Expected Behavior
Files within Claude Code's internal task management directory should be automatically accessible without requiring additional permission prompts, since:
These files are generated by Claude Code, not external sources
They exist within a Claude-controlled temporary directory
Access is typically requested as part of the same workflow that created them
Environment
OS: Windows
Claude Code version: (current)
This is related to the permission inheritance issues discussed in #11934 and #5465,
but focuses specifically on Claude Code's own internal temp files rather than
general subagent permission propagation.
Proposed Solution
Auto-allow read access to paths matching Claude Code's internal temp directory pattern (e.g., /AppData/Local/Temp/claude/ on Windows, or equivalent on other platforms) when the access is initiated from within the same Claude Code session.
Alternative Solutions
Users must manually click "Allow" each time they want to read task output, which interrupts the workflow.
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗