I created a separate app for triggering commands called TRIGGERcmd Misson Control.

@Guilherme-Matos, I tried it. When I ran the TRIGGERcmd Agent in the other user account on my computer, the token prompt did show up, but I had to click the agent's icon at the bottom of the screen because it was behind my browser. I had to bring it to the front.

If you don't get an icon at the bottom, let me know, and please tell me whether you're using the latest version. I'm running version 1.0.56 which I'm about to release. I added an emoji icon picker for commands.

Download and add this to your Claude skills to list and run commands from Claude:

TRIGGERcmdSKILL.md

@Rodney-Mathee, I'm glad you told me it's wifi, not wired ethernet. That changes things. For one, that WakeMeOnLan.exe tool from Nirsoft won't work because it doesn't support wireless networks.

I've never tried "wake-on-wlan" but in theory it's possible with the right hardware.
https://documentation.ubuntu.com/core/explanation/system-snaps/network-manager/how-to-guides/configure-the-snap/wake-on-wlan/

@Rodney-Mathee, you'll need to use a separate computer on your network to turn it on via "Wake On Lan" and you'll probably need to enable it in the BIOS of the computer you want to turn on.

This tool could send the "magic packet" to turn on the other computer on your network:
https://www.nirsoft.net/utils/wake_on_lan.html

The following is from the documentation page I linked to above:

Turn On a Computer From Command-Line
WakeMeOnLan allows you to wake up a computer on your network without displaying any user interface, by using the /wakeup command-line option. You can specify the computer name, IP address, or the free user text that you typed in the properties window, as long as the computer information is stored inside the .cfg file. You can also specify the MAC address of the remote network card, even if the computer is not stored in the .cfg file.
Optionally, you can specify the port number in the second parameter, and broadcast address in the third parameter.

Examples:
WakeMeOnLan.exe /wakeup 192.168.1.25
WakeMeOnLan.exe /wakeup Comp01
WakeMeOnLan.exe /wakeup Comp02
WakeMeOnLan.exe /wakeup 40-65-81-A7-16-23
WakeMeOnLan.exe /wakeup 406581A71623
WakeMeOnLan.exe /wakeup Comp02 30000 192.168.0.255
WakeMeOnLan.exe /wakeup 192.168.1.25 20000 192.168.1.255

You can also wake up all computers in the list by using /wakeupall command-line option. Like in the /wakeup command-line option, you can optionally specify broadcast address and port number.

Examples:
WakeMeOnLan.exe /wakeupall
WakeMeOnLan.exe /wakeupall 20000 192.168.2.255 If you want to wake up all computers in specific IP addresses range, you can use /wakeupiprange command-line option

Examples:
WakeMeOnLan.exe /wakeupiprange 192.168.0.25 192.168.0.100
WakeMeOnLan.exe /wakeupiprange 192.168.0.11 192.168.0.20 20000 192.168.0.255

If you want to wakeup multiple computers, you can use /wakeupmulti command-line option.
Examples:
WakeMeOnLan.exe /wakeupmulti 192.168.1.19 192.168.1.55 192.168.1.82
WakeMeOnLan.exe /wakeupmulti Comp01 Comp02

@Andru, thanks for the idea. I'll look into it.

@Lokilator nice, I've used the shutdown command in the past. I haven't seen that one.

@Lokilator, you could run a command to put the PC to sleep, but once it's sleeping, the computer can't run commands, so you can't wake it up from the computer itself. You'd need to run a command on a second PC that would send the magic packet to wakeup the first PC that's sleeping. Is that clear?

If you have 2 PC's, they could wake each other up as long as one of them is not sleeping at the time.

@Pepe-Tops , good to know. I'll test and fix that if I can reproduce it.

@Matt-Packwood, I thought I did produce an Apple Silicon version. Are you saying this version isn't an Apple Silicon version?

https://agents.triggercmd.com/TRIGGERcmdAgent-arm64.dmg