The Codex VS Code panel was stuck loading while the remote extension host was repeatedly reconnected instead of replaced. Two separate issues were found:
- The installed Codex extension bundle hit a Node compatibility path involving the global
navigatorobject. - Codex's internal
GitRepoWatcherrequested a recursive watch on the repository root, separate from VS Code'sfiles.watcherExclude.
The VS Code workspace watcher exclusion for obj is in place, but it does not configure Codex's internal Git watcher.