"Allow for remainder of session" permission does not persist - prompts repeatedly for same tool

"Allow for remainder of session" permission does not persist - prompts repeatedly for same tool

Description

When granting permission for a tool with "Allow for remainder of session", the permission does not persist. Subsequent uses of the same tool in the same session continue to prompt for permission.

Reproduction Steps

1. Start a new Claude Code session
2. Use the Read tool to read a file (e.g., Read on a temp file path)
3. When prompted, select "Allow for remainder of session"
4. Use the Read tool again on a different file
5. Expected: Tool executes without prompting
6. Actual: Permission prompt appears again

Environment

• OS: Windows 11
• Claude Code version: Latest (as of 2026-01-29)
• Shell: PowerShell / Git Bash

Evidence

Observed independently in two separate Claude Code sessions running concurrently:

1. Session "idx-vault" - Repeatedly prompted for /tasks permission despite granting session-wide access
2. Session "CxMS coordinator" - Repeatedly prompted for Read permission on temp files despite granting session-wide access

Both sessions were part of a multi-agent workflow where the repeated prompts significantly disrupted productivity.

Affected Tools

• Read tool (reading files)
• /tasks command (task management)

This suggests the bug is not tool-specific but affects the session permission persistence mechanism broadly.

Workaround

Use Bash cat command instead of the Read tool:

# Instead of using Read tool:
cat "/path/to/file.txt"

This bypasses the Read tool permission system entirely but loses the benefits of the dedicated tool (line numbers, offset/limit, etc.).

Impact

• Workflow disruption: Users must repeatedly approve the same action
• Trust erosion: Users expect "for remainder of session" to mean what it says
• Workaround overhead: Switching to Bash for reads loses tool features

Possibly Related

This may be related to other permission persistence issues. The settings.local.json allowlist with wildcards (e.g., Read(*)) also seems to not fully prevent prompts in some cases.

Additional Context

Both affected sessions were running in the same workspace with a shared coordination file. However, they were independent Claude Code processes, so session state should not have been shared or conflicting.

---

Suggested Labels

• bug
• permissions
• ux