You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ba936f3
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): resolve the configured shell in the session location
Review on the first revision showed ShellSelect.Service is not
provided to the persistentPty handlers: the experimental endpoints
carry no location middleware, so the yield failed every terminal
create and leaked into the routes layer.
Resolve in the session's location instead, the same way
middleware/session-location.ts does: sessionInfo, then
instances.provide, then ShellSelect.Service, awaiting plugin
activation so the config-to-shell state is populated. Resolution is
lazy (explicit commands never enter it) and best effort: terminals
whose session cannot be resolved keep the environment shell, which
the existing tests depend on.
Fixesanomalyco#51051
0 commit comments