[BUG] Triggers file watchers since 2.1.7

Open 💬 3 comments Opened Jan 21, 2026 by PaulCrz

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?

When starting a Claude Code session (especially with --continue or --resume), the FileHistory backup system touches/accesses source files in a way that updates their modification timestamps, even though file contents are not changed. This triggers hot reloads on development servers (Vite, uvicorn/FastAPI, etc.), causing constant unnecessary restarts.
Version affected: >= 2.1.7
Version working: 2.1.6 (stable) — rolling back with claude install stable fixes the issue
OS: macOS
Steps to reproduce:

Have a project with dev servers using file watchers (Vite, uvicorn with --reload, etc.)
Run claude --debug in the project directory
Start or resume a session
Observe dev servers hot reloading repeatedly without any actual code changes

What Should Happen?

No code file updates when their is no active prompt in Claude Code

Error Messages/Logs

Steps to Reproduce

Have a project with dev servers using file watchers (Vite, uvicorn with --reload, etc.)
Run claude --debug in the project directory
Start or resume a session
Observe dev servers hot reloading repeatedly without any actual code changes

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.6

Claude Code Version

Greater or equal to 2.1.7

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗