Luumen connects to Windows servers over WinRM. You add a Windows host the same way you add a Linux one, with two differences: WinRM has to be turned on from the Windows side first, and you open Windows sessions from the Hosts page.
Prepare the Windows Host
A default Windows installation does not accept remote WinRM connections.
In an elevated PowerShell session on the host, confirm the service is running with Get-Service WinRM, then configure it to listen for remote requests with winrm quickconfig. That opens the HTTP listener on 5985 and the matching firewall rule.
The account you connect with needs permission to use WinRM. Local administrators already have it. Other accounts usually need to be members of the Remote Management Users group.
Luumen reaches Windows hosts directly, so the host needs to be routable from your machine.
Add the Host
Add the host as usual and set the Connection type to WinRM.
Those are the only two ports Luumen accepts for WinRM; anything else is rejected as a port error:
The port defaults to 5985, which is WinRM over HTTP.
Set it to 5986 and Luumen uses HTTPS. On 5986 the traffic is encrypted. Luumen accepts the listener's certificate without validating it, so a self-signed certificate works without extra setup.
To verify a Windows host, connect to it. Test Connection checks SSH hosts.
Add a Credential
WinRM authenticates with a username and password, so create a Password credential.
Create it from the Add credential button inside the host you are adding. A credential created there is saved as a WinRM credential and matched to the host. A credential created from the Credentials page is saved for SSH.
Start a Session
Open Windows sessions from the Hosts page. Select the host and click Connect. Once the session is open, LuumenAI reads it and asks for your approval before it runs anything, the same as on Linux.
Capability | SSH | WinRM |
Connect from the Hosts page | Yes | Yes |
Connect from a LuumenAI conversation or Connect Group | Yes | No. The action reads WinRM hosts can't connect from chat yet. Connect from the Hosts page; LuumenAI then works in that session normally. |
Test connection and credential Test | Yes | No. Testing exercises SSH only. You must verify by connecting. |
Jump host | Yes | No. A Windows host cannot use a jump host or serve as one. |
Session persistence | With | No. A dropped Windows session does not resume. |
LuumenAI Host context and approvals | Yes | Yes, once a session is open. |
If a WinRM Host Won't Connect
Most WinRM failures are the same authentication and network problems as SSH. Confirm the listener with winrm enumerate winrm/config/listener on the host, confirm the account is allowed, and see Fix connection errors.