[BUG] Claude wrote files to system temp folder (AppData\Local\Temp) without disclosure

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

During a session where I had explicitly restricted Claude's working directory to a specific project folder (claudeProj), Claude wrote multiple working files to C:\Users\[username]\AppData\Local\Temp\ without:

• Informing me it was writing outside the agreed project folder
• Asking for permission to do so
• Explaining what it was doing or why in plain English before running the command

I only discovered this when I noticed the temp folder wasn't appearing in my project directory like a previous working folder had. When I asked about it, Claude acknowledged it had broken the agreed boundary.

The core problem: The permission prompt Claude triggers before running a command is not sufficient disclosure. It shows the raw command but does not highlight when something significant is happening — like writing files to a location outside the user's project. Users cannot reasonably be expected to parse every command line before approving.

What Should Happen?

• Claude should never write files outside an agreed working directory without explicit plain-English disclosure and user approval
• Before any command, Claude should clearly state what it's doing, where, and why — not just surface a raw command for approval
• Ideally there should be a way for users to hard-restrict Claude to a specific directory that cannot be bypassed

Error Messages/Logs

Steps to Reproduce

Ask claude to do something in a copy of a file or something like that and it might decide to step outside of the specified folder and make/edit filed.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

4,6

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_