Constant "path should be a `path.relative()`d string" error

Support Bug Reports
1

Describe the Bug

I have a shared workspace with several repos. Every time when the agent tries to find a component, it gets the same "path should be a path.relative()d string, but got.. " errors.

Steps to Reproduce

  1. Create a workspace with two repos
  2. Prompt it to do anything
    Voila.

Expected Behavior

It should find the expected files.

Screenshots / Screen Recordings

Screenshot 2025-12-10 at 16.55.36.png
Screenshot 2025-12-10 at 16.55.36.png1392×214 16.3 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (Universal)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

Doesn’t matter which one

For AI issues: add Request ID with privacy disabled

099d1156-699f-450d-a008-254f439df5e9

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. Looks like a bug in path handling for workspaces with multiple repos.

Need details to reproduce and escalate:

  • Attach your .code-workspace file (or screenshot of folders/paths)
  • Any symlinks between repos?
  • Example real paths of both repos and file where it fails (screenshot shows ../app-ui/src/pages/...)
  • Console: Cmd+Shift+P → Developer: Toggle Developer Tools → Console tab, copy errors
  • Logs: Cmd+Shift+P → Developer: Open Logs Folder, attach latest files
  • New Request IDs on re-reproduction

Quick test workaround: open each repo in separate Cursor windows and repeat. Does error disappear? Once we have data, I’ll pass bug to engineers as blocker.