VS Code extension repeatedly starts git-init-watcher on non-Git NAS workspaces

Summary

The Codex VS Code extension starts a git-init-watcher for a workspace that has no .git directory and does not use Git.

On a mapped NAS drive, the filesystem watch fails and the extension retries, flooding the Output panel with warnings.

Environment

• Windows
• VS Code extension: openai.chatgpt@26.908.40401
• Workspace: V:\NGINX\www\evmgt
• Mapped network drive: V: → \\nas3\APPS
• No .git directory exists in the workspace
• VS Code built-in Git integration is disabled ("git.enabled": false)

Actual behavior

Repeated warning:

[warning] [git-init-watcher] Git init watcher failed cwd=V:\NGINX\www\evmgt errorCode=UNKNOWN errorMessage="UNKNOWN: unknown error, watch"
Error: UNKNOWN: unknown error, watch
    at FSWatcher._handle.onchange (node:internal/fs/watchers:267:21)

The extension keeps retrying the watcher although the workspace is not a Git repository.

Expected behavior

Do not create a Git-init watcher unless Git metadata exists, or stop retrying quietly after an unsupported filesystem-watch error. This would prevent warnings in ordinary non-Git folders on network drives.

No source file or test is named in the report; start by locating the git-init-watcher entry point and reproducing the warning on a non-Git network workspace. Done means the watcher is not repeatedly started or retried in that case, and the warning flood is absent.