@sgrzybolowski, you should be able to get that from your PayPal account transaction history.

@Shawndell-Harris, please send me your home IP address via chat. I'll unblock it.

@Emanuel-MAIA, awesome!

@Luz, the agent should prompt for a token the first time you run it. You could try closing and re-running the TRIGGERcmd agent. [image: 1688955851454-5d9e7eab-855c-40e1-aefe-58aaa65b66af-image.png] If that doesn't work, you could try: close the agent, delete your C:\Users\(your user)\.TRIGGERcmdData folder, and open it again.

@José-Pábulo, please try switching the command from background to foreground, or vice versa. The GUI Editor will run both types of commands, but the foreground agent won't run background commands, and vice versa. Did you install the background agent?

@HeeHang, good. Can I ask what computer name you gave it when it failed? I wonder if there was a special character in it or something that I didn't test for.

@Zubairsk, where did you get that text? Do you live in the UK and got that somehow when you tried to find the TRIGGERcmd skill?

@Cristian-Garcia, I'm glad you asked. Google deprecated conversational actions like the original TRIGGERcmd (and Execute Comando) Google Assistant actions. So on Google Home devices, please enable the TRIGGERcmd Smart Home action. It works better anyway. It creates a smart home device for each command, and because Google has a list of those devices ahead of time, it does a better job of matching your words to your commands. Instead of, "Hey Google, ask TRIGGERcmd to run Calculator" you'll say, "Hey Google, turn on Calculator".

@Oscar-Alvarado, I'm glad you asked. Google deprecated conversational actions like the original TRIGGERcmd (and Execute Comando) Google Assistant actions. So on Google Home devices, please enable the TRIGGERcmd Smart Home action. It works better anyway. It creates a smart home device for each command, and because Google has a list of those devices ahead of time, it does a better job of matching your words to your commands. Instead of, "Hey Google, ask TRIGGERcmd to run Calculator" you'll say, "Hey Google, turn on Calculator".

@Kristopher-Adams, you could try renaming your curl.bat file. I suspect it might be running itself because the command in the script is curl.

@fmaick93, please try this command (no space in sendkeypress): nircmd sendkeypress f1

Solved, I used WinGet (Auto Hot Key). Code Working: Browser_Home:: WinGet, pid, PID, ahk_exe SolarlandClient-Win64-Shipping.exe run, C:\tools\nircmd.exe muteappvolume /%pid% 2 return

@Zubairsk What do you do with this machine? What gen is your Ryzen?

@Red-Sufi awesome. Good job.

@Fernando-Mateos, Google is removing all conversational actions, so you should use the TRIGGERcmd Smart Home action instead. It works much better anyways. It simulates an on/off switch, so you just say "Hey Google, turn on calculator".

@kanashi横維, are you hoping there's a way to hide this TRIGGERcmd tray icon? [image: 1683326914357-cceeb91a-5425-4f60-907a-4a844fa81bfc-image.png] Sorry, there's no way to hide it. EDIT: Actually, you could install the background service, then prevent the TRIGGERcmd Agent shortcut from executing when you login. If you do that, you'll need to manually run it to get to the GUI Editor for commands.json. To prevent the TRIGGERcmd Agent shortcut from running (the "foreground" agent), you would remove it from your Startup folder. Press Windows-R and paste in shell:startup and click OK. [image: 1683396832623-01b43a7b-16a5-43dd-bdcd-d640262719a2-image.png] Then delete the shortcut or move it out of the Startup folder. [image: 1683396903138-dc9c70a4-5361-4525-b567-55b972d0f33a-image.png]

@Eduardo-Henrique, I tried all of those characters and I could not get it to break. So maybe that was not the problem. Can you send me the computer name you were using when it wasn't working?

@Lucas-Eduardo-0, a re-installing won't help because the problem is in your data files which persist when you uninstall. Will you please paste the contents of this file here? c:\Users\(your user)\.TRIGGERcmdData\commands.json The corruption might be in that file. Or, if you want, you could try a complete reset with this steps: Close the TRIGGERcmd agent Rename the c:\Users\(your user)\.TRIGGERcmdData folder. Delete the computer in your TRIGGERcmd account. Open the TRIGGERcmd agent. Copy/paste your token from the Instructions page into the prompt.