project `settings.json` can't use relative binary paths

[ask4fusora]

Summary

project settings.json can't use relative path.

Description

Say, I have a binary in my project I want to use. But while absolute path works, relative path doesn't, which is weird.

Example folder image

{
  "lsp": {
    "biome": {
      "binary": {
        // "path": "D:\\01-projects\\ask4fusora\\valor-smith\\node_modules\\.bin\\biome.exe", // <- This works
        "path": "node_modules\\.bin\\biome.exe", // <- This does not work
        "arguments": ["lsp-proxy"]
      }
    }
  }
}

{
	"context_servers": {
		"mcp-server-todo": {
			"source": "custom",
			"enabled": true,
			"command": "npm\\dist\\win32-x64\\mcp-server-todo", // <- This doesn't work
      // "command": "D:\\01-projects\\ask4fusora\\mcp-server-todo\\npm\\dist\\win32-x64\\mcp-server-todo", // <- This works
			"args": []
		}
	}
}

Steps to reproduce:

1. With any binary relative to the project.
2. Use that binary in settings.json

Expected Behavior: Relative path binaries should work
Actual Behavior: Doesn't work

For version matching problems, having relative path binary as an option would be really helpful, especially when you don't have to pollute your PATH env variable; don't have to worry where you move your project to on your machine; don't have any random caller wrapper such as bunx, npx, ...

Zed Version and System Specs

Zed: v0.209.6 (Zed)
OS: Windows 10.0.26200
Memory: 15.4 GiB
Architecture: x86_64
GPU: NVIDIA GeForce GTX 1660 Ti || NVIDIA Corporation || 581.29 r581_07

[ask4fusora]

#38227

[ask4fusora]

#30938

[ask4fusora]

It seems the problem is that Zed has yet to have a way to load relative paths whatsoever.

[HactarCE]

Thanks for the issue! This seems like something we should have

[ask4fusora]

@HactarCE Thank you for the great work for LSP and DAP.

I will look at the relative path for MCP binaries.