claude-code - 💡(How to fix) Fix [FEATURE] Allow Chat Projects to save created files to a user-defined folder instead of AppData scratch directory

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

When working inside a Chat Project in the Claude Desktop app (Windows), files generated by Claude (Word, Excel, PowerPoint, PDF) are saved to a deeply nested internal directory under AppData\Roaming\Claude...\AI-Output. To actually use a file, the user has to: 1. Click Download on each generated file 2. Locate it in the system Downloads folder 3. Manually move it into the project folder where their work lives For users running document-heavy workflows — knowledge workers, executives, consultants producing multiple deliverables per session — this adds friction on every single file. The AppData path is also hidden, hard to access via Explorer, and unreliable across sessions. Chat Projects are positioned as persistent workspaces. The file output behavior should match.

Proposed Solution

Add a per-Project “Save outputs to:” setting that lets the user designate a folder where files created in that Project automatically save (e.g., C:\Users<user>\Documents\My Project). Implementation options: • A setting in the Project’s sidebar/settings panel • A prompt on first file creation per Project, with a “remember this for this Project” option • Default fallback to current behavior when no folder is set • Bonus: optional sub-folder organization by date or session name The pattern is already proven in Cowork (designated working folder). Extending it to Chat Projects would align the two experiences. Use Case I’m a former Fortune 100 CIO using Chat Projects for document-heavy work — strategy memos, briefing docs, analysis decks. A typical session produces 5–10 files. Today that means 5–10 Download → Locate → Move sequences, all to land files in the same folder I’ve already set up for that Project. The friction breaks flow and makes Projects feel less like “persistent workspaces” and more like “chat with attachments.”

Alternative Solutions

Changing the browser/desktop default download location — partial fix, but still requires manual move per Project • Using Cowork instead — works, but requires the desktop to stay awake and doesn’t fit every Chat use case • Save to Google Drive — helpful for some files, but folder targeting is limited

OS: MacOS/iOS/iPADOS • Claude Desktop app: latest (May 2026) • Plan: paid (Pro/Max) • Usage pattern: daily Chat Project sessions producing multiple Office/PDF deliverables

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

I am using Chat Projects for document-heavy work — strategy memos, briefing docs, analysis decks. A typical session produces 5–10 files. Today that means 5–10 Download → Locate → Move sequences, all to land files in the same folder I’ve already set up for that Project. The friction breaks flow and makes Projects feel less like “persistent workspaces” and more like “chat with attachments.”

Additional Context

No response