← visual.onfleek.live
The goal: let the OnFleek server reach across the home network and install or fix apps on the
761st_Armor PC by itself — no walking over to it each time. To do that, we open a small
"side door" (Windows remote-management, called WinRM) once. After that, everything runs from the server.
Target PC
761st_Armor192.168.89.191
Driven From
OnFleek192.168.89.100
Login Made
claude-remotepw in api-keys.md
Delivery
nginx hub:4048 irm | iex
The Steps // 3 to go live
1
Open the door (on the 761st PC)
Waiting on you
The door can only be unlocked from the inside, one time. On the 761st PC: click Start, type
PowerShell, right-click it → Run as administrator, then paste the line below and press Enter.
It prints a few green "[ok]" lines and the PC's address, then says you can close it.
Run on 761st_Armor (as administrator)
irm http://192.168.89.100:4048/enable-remote.ps1 | iex
2
Test the door (from the server)
Claude does this
Once you say it's done, the server adds the 761st PC to its "trusted" list and knocks on the door using the new
claude-remote login. A quick handshake test confirms it can run commands over there.
3
Install your apps
Claude does this
With the door open, the server installs whatever you want using Windows' built-in app store tool
(winget) — Chrome, VLC, 7-Zip, Steam, and so on. From here on, future installs and fixes need
zero trips to the other PC.
What Opening The Door Changes // on the 761st PC
- Turns on remote controlStarts the built-in Windows service (WinRM) that lets the server send commands.
- Adds one firewall "okay"A rule that allows that traffic — on your home network only, never the internet.
- Makes one admin loginA new account named
claude-remote so the server has its own key. Your own logins are untouched.
Safe by design: this does not touch your internet, IP address, gateway, DNS, or Wi-Fi —
it only opens a local door on your own home network. The claude-remote password is stored in your private
keys file (api-keys.md), not on this page.