Detent Point
Remote tabs show you whose machine you're on
The most expensive command in remote administration is the one that runs on the wrong box. Everyone who manages servers has done it or watched it: identical-looking consoles, muscle memory, and a production machine receiving something meant for a lab.
DetentShell’s remote sessions are designed around not losing track. File, New Remote PowerShell Tab, or Ctrl+Shift+R, opens a WinRM session in the Enter-PSSession style: you name the computer, provide credentials, and the tab becomes a live remote PowerShell with its own console and script tabs, sitting next to your local sessions.
The detail doing the safety work is the tab title. It reads user@computer, permanently. Not a tooltip you’d have to hover over, not a status line you’d have to check. It’s in the tab, where your eyes land on every switch. Local tabs say PowerShell 1. The remote one says whose machine it is. Six tabs into a long day, that label is the guardrail.
The credential dialog is built the careful way. The password field feeds a SecureString from the first keystroke, and the credential object is assembled from the secure buffer at submission. The password never takes a lap through a plain string property. It’s the same prompt bridge that handles Get-Credential inside running scripts, correlation-ID’d per request so simultaneous prompts from different tabs can’t cross wires, and canceling a connection attempt cancels cleanly instead of leaving a hung tab.
A remote session is still a session in the DetentShell model, so the usual properties hold: isolated from your other sessions, its own script tabs sharing its runspace, output streaming into its own console. The remoting layer itself is PowerShell’s own WinRM, the transport your organization already governs and logs. The workbench wraps around it rather than tunneling past it.
The edges are labeled honestly. Some interactive and debugging surfaces behave differently across a remoting boundary, and where the boundary can’t support something, the failure is one clear sentence. A remote session that mostly works like local, except when it silently doesn’t, is exactly how wrong-machine stories begin.