Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Agent modifies explicitly specified file paths without authorization

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The agent altered a file path that was explicitly provided by the user, placing the file in the wrong location without asking.

Root Cause

The agent invented a path prefix (GodotForge/) based on internal assumptions about where the file "should" live, without verifying the existing directory structure and without authorization to alter the path at all. The correct behavior — per the active instructions — was to either write to the exact path given or ask one clarifying question first.

RAW_BUFFERClick to expand / collapse

Summary

The agent altered a file path that was explicitly provided by the user, placing the file in the wrong location without asking.

What happened

User instructed: "write this to claude_mcp.md in Docs/Research/McpIntegration"

Agent wrote to GodotForge/Docs/Research/McpIntegration/claude_mcp.md — prepending GodotForge/ to the path the user specified. The path was unambiguous. The agent had no authorization to modify it.

Verbatim instructions violated

From the user's global CLAUDE.md, which was active during the session:

Do exactly what was asked. Nothing more.

Ambiguity: If the request is ambiguous, ask one clarifying question before acting. Do not make an assumption and proceed with extra work "just in case."

Scope Creep Is Prohibited. The following are never acceptable without explicit user request:

  • Creating new files beyond what is strictly necessary

Root cause

The agent invented a path prefix (GodotForge/) based on internal assumptions about where the file "should" live, without verifying the existing directory structure and without authorization to alter the path at all. The correct behavior — per the active instructions — was to either write to the exact path given or ask one clarifying question first.

Impact

  • File created at wrong location
  • Empty directories created unnecessarily
  • User time spent correcting the deviation
  • Degraded trust in path-related instructions

Expected behavior

Write to the exact path specified. If uncertain, ask one clarifying question. Never silently alter a user-provided path.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Write to the exact path specified. If uncertain, ask one clarifying question. Never silently alter a user-provided path.

#configuration error#environment variable#network issue#logging issue#authentication issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Agent modifies explicitly specified file paths without authorization