Cursor fails to detect worktrees.json in remote setup

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I follow the instructions to configure worktrees (Parallel Agents | Cursor Docs), but Cursor fails to find the config file.
This makes the feature unusable for me.

Steps to Reproduce

This is all done in a remote configutaion - I use Cursor with a remote host over SSH.

  1. Create a worktrees.json file according to the instructions in Parallel Agents | Cursor Docs or via the UI in Cursor (it suggests creating one after creating a Worktree agent)
  2. Commit the file, to be on the safe side with the worktree creation
  3. Create a new agent, set it to use worktrees, and give it a prompt.
  4. Check the “Worktree Setup” in the “Output” panel (following Parallel Agents | Cursor Docs)
  5. The output says:

[2026-01-18T14:21:11.474Z] [worktree-setup] no config file found in worktree or root, skipping

Expected Behavior

A new worktree is created, and the configuration is detected and executed.

Operating System

Windows 10/11
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.41 (user setup)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

I get this issue when running with a remote host.
I did not try it locally as my setup is fully remote.

I am working on a Windows machine, SSH-ing into a Linux machine.

In the logs, I get a JSON print showing the expected paths for the config files:

[2026-01-18T14:21:11.462Z] [worktree-setup] checking config
{“composerId”:“5a0d39cd-55ff-4bfd-9a43-9695cb5925a5”,“worktreePath”:“/home/tamirb/.cursor/worktrees/myrepo__SSH__devpod_/sdn”,“rootWorkspacePath”:“/workspace/tamirb/managed-environments/prime-duke/myrepo”,“worktreeConfigFile”:“file:///home/tamirb/.cursor/worktrees/myrepo__SSH__devpod_/sdn/.cursor/worktrees.json”,“rootConfigFile”:“file:///workspace/tamirb/managed-environments/prime-duke/myrepo/.cursor/worktrees.json”,“isTargetWindows”:false,“remoteOS”:3}

Both of the config paths (the rootWorkspacePath and the worktreeConfigFile) exist and are accessible.
My guess is that Cursor is having issues because they are remote paths, but presented as local paths (file://), but this is a guess.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

Hey, thanks for the report. This is a known issue with worktrees in remote environments. The agent uses a file:// URI to check the config, and it doesn’t resolve correctly over SSH.

The same bug is already tracked here: Agent “Worktree Setup” fails to find config file in Remote SSH sessions

I’ll reply in that thread when there’s any news.