Reproduction steps

Zed's remote server log files grow without limit or rotation. On a large monorepo with many directories, the same 3 error messages are spammed continuously, producing tens of GB of log files. In my case, a single log file reached 29 GB. Top 3 messages:

• OS file watch limit reached
• filesystem watcher lost sync
• error reading target of Bazel symlinks (bazel-out, bazel-bin, bazel-testlogs)

Current vs. Expected behavior

• Dangling symlinks after Bazel server shuts down (execroot/ cleaned up) — Zed logs error every scan cycle
• Logs one line per directory that can't be watched, repeated every scan cycle → millions of identical "OS file watch limit reached" lines
• Logs one line per directory per rescan, rescanning never res

Zed version and system specs

• Zed 1.2.7
  Commit: deb48ce
  Version: 1.2.7+stable.284.deb48ceb47125223df73902d1c3b72f2f442222b
• OS (remote): Linux (Ubuntu)
• Project: Large monorepo (~8 GB, thousands of subdirectories including Kotlin, Python, TypeScript, Helm charts, Bazel build files)
• fs.inotify.max_user_watches: default (8192)

Attach Zed log file

Relevant Zed settings

Relevant Keymap

(for AI issues) Model provider details

No response

If you are using WSL on Windows, what flavor of Linux are you using?

None