Problem
Jupyter Server clients, including nb-cli, cannot reliably determine which Python environment a server was started in.
That forces clients to rely on user-provided env-manager hints instead of aligning directly with the connected server, and makes features like #52, where clients want to return the right Python command for the connected server environment, harder to build correctly.
Proposed solution
Expose server environment identity from Jupyter Server.
One possible direction is to derive it from environment variables, such as VIRTUAL_ENV, when available during server startup, and expose it to clients through a server extension API endpoint or existing session/server metadata.
Problem
Jupyter Server clients, including
nb-cli, cannot reliably determine which Python environment a server was started in.That forces clients to rely on user-provided env-manager hints instead of aligning directly with the connected server, and makes features like #52, where clients want to return the right Python command for the connected server environment, harder to build correctly.
Proposed solution
Expose server environment identity from Jupyter Server.
One possible direction is to derive it from environment variables, such as
VIRTUAL_ENV, when available during server startup, and expose it to clients through a server extension API endpoint or existing session/server metadata.