Description
Claude Desktop writes output files to inconsistent and incorrect locations:
- Wrong root entirely: Wrote to
/home/claude/CC_INSTRUCTION_VALIDATE_CONFLUENCE_CORE16.md instead of the project working directory (C:\Users\Cassie\Desktop\trading_system)
- Inconsistent subdirectories: Previously wrote reports to
docs/, then started writing to reports/, with no user-requested change
Environment
- Platform: Claude Desktop (latest version, Windows)
- OS: Windows 10/11
- Project root:
C:\Users\Cassie\Desktop\trading_system
- Date observed: January 29, 2026
Expected Behavior
Files should be written relative to the project working directory consistently, respecting the directory structure the user has established.
Actual Behavior
- Desktop uses
/home/claude/ as the write path (appears to be a Linux sandbox/container path leaking through)
- Output directory drifts between sessions (
docs/ → reports/ → /home/claude/)
Possibly Related
However this is distinct: the model is not misspelling a path, it's using an entirely different filesystem root that doesn't exist on the user's Windows machine.
Description
Claude Desktop writes output files to inconsistent and incorrect locations:
/home/claude/CC_INSTRUCTION_VALIDATE_CONFLUENCE_CORE16.mdinstead of the project working directory (C:\Users\Cassie\Desktop\trading_system)docs/, then started writing toreports/, with no user-requested changeEnvironment
C:\Users\Cassie\Desktop\trading_systemExpected Behavior
Files should be written relative to the project working directory consistently, respecting the directory structure the user has established.
Actual Behavior
/home/claude/as the write path (appears to be a Linux sandbox/container path leaking through)docs/→reports/→/home/claude/)Possibly Related
However this is distinct: the model is not misspelling a path, it's using an entirely different filesystem root that doesn't exist on the user's Windows machine.