[Bug] Tab completion fails with relative paths starting with `./`
Resolved 💬 2 comments Opened Jan 22, 2026 by garykognic Closed Jan 24, 2026
Bug Description
Tab completion (and suggestions) seems to fail on some paths. e.g. @./src/myfolderstart_<tab> changes to @src/myfolderstart_end but then can't dig deeper. If I run @../workspace/src/myfolderstart_<tab> then it works as expected.
Environment Info
- Platform: linux
- Terminal: cursor
- Version: 2.1.15
- Feedback ID: f538d7b5-ba74-4fb6-bcfe-5c69c66a1b33
Errors
[{"error":"Error: ENOENT: no such file or directory, scandir '/etc/claude-code/.claude/skills'\n at readdirSync (unknown)\n at <anonymous> (/$bunfs/root/claude:12:1903)\n at LJ (/$bunfs/root/claude:11:34882)\n at readdirSync (/$bunfs/root/claude:12:1864)\n at J5$ (/$bunfs/root/claude:1480:380)\n at J5$ (/$bunfs/root/claude:1480:1350)\n at <anonymous> (/$bunfs/root/claude:1480:4440)\n at <anonymous> (/$bunfs/root/claude:1480:5171)\n at A (/$bunfs/root/claude:11:7245)\n at gU1 (/$bunfs/root/claude:4123:4342)\n at async <anonymous> (/$bunfs/root/claude:5410:2332)","timestamp":"2026-01-22T05:14:43.805Z"},{"error":"Error: ENOENT: no such file or directory, scandir '/home/ultra/.claude/skills'\n at readdirSync (unknown)\n at <anonymous> (/$bunfs/root/claude:12:1903)\n at LJ (/$bunfs/root/claude:11:34882)\n at readdirSync (/$bunfs/root/claude:12:1864)\n at J5$ (/$bunfs/root/claude:1480:380)\n at J5$ (/$bunfs/root/claude:1480:1350)\n at <anonymous> (/$bunfs/root/claude:1480:4483)\n at <anonymous> (/$bunfs/root/claude:1480:5171)\n at A (/$bunfs/root/claude:11:7245)\n at gU1 (/$bunfs/root/claude:4123:4342)\n at async <anonymous> (/$bunfs/root/claude:5410:2332)","timestamp":"2026-01-22T05:14:43.805Z"},{"error":"Error: NON-FATAL: Lock acquisition failed for /home/ultra/.local/share/claude/versions/2.1.15 (expected in multi-process scenarios)\n at o7$ (/$bunfs/root/claude:3241:2091)\n at h_A (/$bunfs/root/claude:3241:1202)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-01-22T05:14:43.866Z"}]This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗