This happens more than people think, especially when file names are similar (like draft-final.md vs draft-final-v2.md) or when work happens across multiple sessions.

Good news: this is usually fixable in minutes if you switch to a path-proof workflow.

2-Minute Recovery Checklist

Known-Good Prompt (Copy/Paste)

Before editing anything, verify file identity.

Target file (only this one): [full path]
Do not edit any other file.

Step 1) Read and show:
- exact full path
- first 3 lines
- last modified timestamp (if available)

Step 2) Show a dry-run patch (no writes yet).
Wait for my approval.

Step 3) After approval, edit only target file.

Step 4) Return proof:
- edited file full path
- exact changed lines/snippets
- explicit list of files NOT touched.

Why This Happens

• Similar filenames in different folders.
• Stale context from a long thread where earlier file paths are still in memory.
• Vague instructions like “update the report” without path.
• Cross-surface mismatch (dashboard vs Discord) where a different workspace/session was active.

High-Friction Mistakes to Avoid

1) “Use the latest file” with no path

“Latest” is ambiguous. Always specify a full path or unique filename.

2) Batch edits across many files without checkpoints

If precision matters, run one file at a time and verify after each write.

3) No unchanged-file confirmation

If you don’t request a not-touched list, silent collateral edits can be missed.

Advanced Edge Cases (Worth Checking)

1) Same filename in multiple roots

Many users keep copies like /workspace/report.md and /workspace/archive/report.md. Require the agent to print the absolute path, not a relative path like ./report.md.

2) Path looks right but points through a symlink

A symlink can resolve to a different real location. Ask the agent to show both: requested path and resolved real path before writing.

3) Session/surface mismatch after a reset

If you switched from dashboard to Discord (or restarted into a fresh session), confirm the active workspace root first. Wrong-file edits often come from working in the wrong session, not bad intent.

4) “Looks unchanged” because edits landed in another branch/folder snapshot

For repo workflows, ask for git status --short and edited file paths right after the change. This catches edits made in an unexpected branch or nested copy.

Escalation Packet (if it keeps happening)

• Where you ran it (Dashboard / Discord DM / server channel)
• Exact prompt used
• Expected target file path
• Actual edited file path(s)
• Before/after snippets (small redacted samples)
• Timestamp + timezone