If paths are ephemeral and you can't pre-configure them to apply path mappings, maybe you could use an API which would collect the paths and runtime and set the mapping for the debugger?

See: #743 (comment) for how to do that.

I was also thinking that maybe having the path mapping allow for environment variables set in the server could potentially be a solution here too (so, you could have an environment variable resolved in the server as a part of the path mapping resolution) -- note that this isn't implemented at this point.

so, you could have an environment variable resolved in the server as a part of the path mapping resolution

So that'd be relevant here?

so, you could have an environment variable resolved in the server as a part of the path mapping resolution

So that'd be relevant here?

debugpy/src/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_process_net_command_json.py

Line 322 in 4067700

if remote_root == '.':

Yes.

See: #743 (comment) for how to do that.

Ah hey that works, thanks! I'd still advocate for a env var, as thats much easier.

OK I actually did something slightly different:

import debugpy._vendored.force_pydevd
from _pydevd_bundle.pydevd_process_net_command_json import PyDevJsonCommandProcessor
orig_resolve_remote_root = PyDevJsonCommandProcessor._resolve_remote_root

def patched_resolve_remote_root(self, local_root, remote_root):
    if remote_root == ".":
        remote_root = CHROOT
    return orig_resolve_remote_root(self, local_root, remote_root)

PyDevJsonCommandProcessor._resolve_remote_root = patched_resolve_remote_root

I didn't want to tell our users to omit pathMappings as that is the VS Code default. This way we assume "." means our sandbox root.