Support zed . CLI inside Dev Containers to open specific subdirectories (Monolithic Dev-Machine use case)

[GinoNovello]

What are you proposing?

Inject the zed CLI into Dev Containers to allow opening specific subdirectories as new, scoped Zed windows from the integrated terminal, bypassing the strict requirement of having a .devcontainer.json in the opened folder.

Why does this matter?

Zed currently requires a .devcontainer.json in the root of the opened folder to mount the container. For a monolithic "Dev-Machine" setup (multiple projects in a /repos folder), users are forced to open the root. This clutters the file tree and ruins Ctrl+P search. Injecting the CLI allows running a single container to save resources, while maintaining clean, project-scoped editor windows.

Are there any examples or context?

In VS Code, you can open the root container, cd into /repos/my-project, and run code .. This opens a new window scoped only to that project within the same running container. In Zed, zed . returns command not found.

Possible approach

Automatically inject the zed CLI binary upon connection. When executed, it should communicate with the host's Zed instance to launch a new window scoped to the requested path, attaching to the existing container lifecycle instead of looking for a local .devcontainer.json.