@gajahduduk, changing the command's voice word might be what fixed it. That deletes and recreates the Alexa device.

@Russ the shutdown comand doesnt work

@gajahduduk, I built this amd64 (Apple Silicon) version. Would you mind testing it?

https://agents.triggercmd.com/TRIGGERcmdAgent-darwin-arm64-1.0.38.zip

It's a .zip instead of a .dmg, so just move the app into your Applcations folder after you unzip it.

@Russ Many thanks. Unfortunately I don't own an Alexa so I'm going to need to find an alternative. I can get GH to speak custom phrases on command using "assistant.command.Broadcast" with Google's Web based Automations script editor but that is just a fixed phrase. Guess I'm going back to Gemini for more ideas! Good to see TC still going strong - I first used it 5 years ago!

@Adroit-Tester2, the background agent on Windows is meant to run commands that don't do anything with the GUI, like this reboot command:

shutdown /r /t 1

One benefit is the TRIGGERcmdAgent Windows service runs before you login, so you could reboot the PC even if it's not logged in.

Background commands run in the context of the TRIGGERcmdAgent Windows service that runs as Local System, which can be of benefit too because it has full access to your PC and it bypasses UAC.

Here's a test command you use try in background mode to verify it's working:

echo testing > c:\folder\log.txt

I just tried that and it produced the log.txt file when I ran it in background mode.

If you want to see the processes run, I suggest you leave them in foreground mode. You could still lock the PC after logging it on if you don't want the developers to mess with them.