Do the PCs need WinRM, a domain or a VPN?

No. Each PC runs a small client that opens an outbound connection to Octling. Nothing listens for inbound traffic, so workgroup PCs and machines behind home routers work the same as domain-joined ones.

Which account do the commands run as?

The Windows user who installed the client. In resident mode it starts when that user signs in and runs with that user's normal rights, not as SYSTEM and not elevated. A temporary connection runs in the window where it was started and ends when that window closes.

Can I run my existing .ps1 scripts?

Yes. Paste the script and ask for it to be run as is, or ask the AI to write it to a file on each PC and run the file. The commands and their output are kept in the task log.

What happens to PCs that are switched off?

A batch task can skip offline devices; they catch up if they come online before the run ends. Anything that did not finish is listed separately and can be retried on its own. A scheduled batch task picks up whichever devices match the selection each time it runs.

Is there a record of what ran on each PC?

Yes. Every command and its output is shown in the task and written to the audit log, per device.

Use cases · Windows fleets

Run PowerShell on many Windows PCs without WinRM

You look after forty office PCs across three customers. Half are not domain-joined, WinRM is off, and nobody will open a firewall port for you. The job itself is small: find out which machines still have the old VPN client, or clear a stuck print queue everywhere. With Octling each PC keeps an outbound connection, and you run the job from a browser tab.

“Which of these PCs still have Windows 10? Give me a table with the build number and last boot time”

“Uninstall the old FortiClient 6.x where it exists. Leave 7.x alone and tell me which PCs had neither”

What a run looks like

Create a deployment pack and send the install command (or its guide page) to whoever sits at the PCs. The same command works on every machine until the limit or expiry you set, and each PC joins the group you picked.
Start with a read-only question. The AI runs the PowerShell it needs on each PC, for example Get-CimInstance Win32_OperatingSystem, and gives you one answer for the fleet.
For anything that changes the machines, run it as a batch task with “Confirm on the first device, replay on the rest”. One PC goes first and you read the exact commands and their output.
Confirm, and the other PCs replay the same command sequence. Offline PCs can be skipped and catch up if they come online before the run ends. Failures are listed on their own so you can retry only those.

Your own script, or no script

If you already have a one-liner, paste it and say “run exactly this”. If you only know the outcome you want, describe it and let the AI write the PowerShell. Either way the commands that ran are in the task log, so you can copy them out and keep them.

What to know before you rely on it

It runs as the signed-in user, not as SYSTEM. On Windows the resident client is a scheduled task that starts when that user signs in, with the user’s normal rights. Reading settings, per-user installs and most cleanup work fine. A command that needs elevation fails unless that user can elevate without a prompt, so plan machine-wide installs accordingly.

Commands go through cmd first. The agent starts each command with cmd /C, and the AI calls powershell from there. Long scripts with heavy quoting are more reliable when you ask the AI to save them as a .ps1 file on the PC and run the file.

Antivirus may complain about the installer. The install script detects Windows Defender and, when run as administrator, adds an exclusion. With third-party antivirus you may have to allow it by hand.

It is not an RMM. There is no patch-compliance dashboard, no remote screen and no software inventory database. It is a fast way to ask a question of many PCs or push a fix to them, with approval rules and an audit log around it.

Keep risky commands behind a click

Command rules decide which commands wait for your approval, and high-risk commands are blocked. In an unattended batch, anything that needs approval is skipped and noted in the result instead of being run. Add things like Remove-Item -Recurse, shutdown or Restart-Computer to your rules if you want a human to confirm them every time.

Questions

Do the PCs need WinRM, a domain or a VPN?: No. Each PC runs a small client that opens an outbound connection to Octling. Nothing listens for inbound traffic, so workgroup PCs and machines behind home routers work the same as domain-joined ones.
Which account do the commands run as?: The Windows user who installed the client. In resident mode it starts when that user signs in and runs with that user's normal rights, not as SYSTEM and not elevated. A temporary connection runs in the window where it was started and ends when that window closes.
Can I run my existing .ps1 scripts?: Yes. Paste the script and ask for it to be run as is, or ask the AI to write it to a file on each PC and run the file. The commands and their output are kept in the task log.
What happens to PCs that are switched off?: A batch task can skip offline devices; they catch up if they come online before the run ends. Anything that did not finish is listed separately and can be retried on its own. A scheduled batch task picks up whichever devices match the selection each time it runs.
Is there a record of what ran on each PC?: Yes. Every command and its output is shown in the task and written to the audit log, per device.