[BUG] EOPNOTSUPP errors when using --settings flag

Resolved 💬 2 comments Opened Dec 25, 2025 by arn314 Closed Dec 26, 2025

[BUG] EOPNOTSUPP errors when using --settings flag

Description

Using --settings flag emits EOPNOTSUPP errors to stderr.

Minimal Reproduction

claude -p "hi" --model haiku --settings '{}'

Observed Behavior

Multiple EOPNOTSUPP errors emitted:

Error: EOPNOTSUPP: unknown error, watch '/var/folders/.../T/ssh-askpass-*.sock'
    at new FSWatcher (node:fs:29:31)
    at _watchWithNodeFs (/$bunfs/root/claude:392:6746)

Errors reference socket files in TMPDIR (ssh-askpass-*.sock, vscode-git-*.sock).

Key Observation

  • Without --settings: no errors
  • With --settings '{}': errors appear

The flag itself triggers the behavior, not the content.

Speculation (unverified)

The --settings flag may trigger file watching (possibly for hot-reload), and the watcher may be iterating TMPDIR or using a broad pattern that includes socket files. Socket files don't support watch() syscall.

Environment

  • Version: 2.0.76
  • OS: macOS (Darwin 24.6.0, arm64)

View original on GitHub ↗

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