Posts made by Russ

@Yoni, thank you for reporting this.

Please try again. It should work now.

@Alisson-Teixeira, I translated that as:

"I would like to know if it's possible to turn off the monitor and the computer at the same time with just one command? In the free version? With the example command, the monitor enters power saving mode, but doesn't turn off completely...

Question for Windows please"

You can run multiple commands in one command by putting && between commands, like this:

nircmd.exe monitor off && shutdown /s /t 10

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

@Pepe-Tops, no, you don't need a subscription to add more commands. You can have as many commands as you want. You might need to restart your agent if it stopped sync'ing.

One thing to keep in mind - your agent is either running in foreground or background mode, and when it's in foreground mode it will only add/remove/run foreground commands, and vice-versa.

If you installed the background agent, make sure your commands are background commands if you want it to use them.

I just followed this guy's tutorial:
https://towardsdatascience.com/run-claude-code-for-free-with-local-and-cloud-models-from-ollama/

I'm using claude code with ollama running gpt-oss:20b on my PC with my Nvidia GPU to speed it up.

I found this CLAUDE.md file works well. It tells the gpt-oss model how to use the Write tool to write to files:

My CLAUDE.md file:

## Important rules
- If the user wants you to write a file, do it. Use your Write tool to create the file. The Write tool has a required parameter called "file_path".

My interactive claude session:

 ▐▛███▜▌   Claude Code v2.1.29
▝▜█████▛▘  gpt-oss:20b · API Usage Billing
  ▘▘ ▝▝    ~/appdev/raspi

  /model to try Opus 4.5

❯ create a python script called hello.py in the current directory that prints "Hello World".

● Write(hello.py)
  ⎿  Wrote 2 lines to hello.py
      1 print("Hello World")

This is a command that runs a non-interactive claude session. You could run it via the TRIGGERcmd agent

claude -p -d --model gpt-oss:20b --permission-mode acceptEdits "create a python script called hello.py in the current directory that prints Hello World"

I created a this myclaude.bat file:

set ANTHROPIC_BASE_URL=http://127.0.0.1:11434
set ANTHROPIC_AUTH_TOKEN=ollama
cd c:\myfolder
claude -p -d --model gpt-oss:20b --permission-mode acceptEdits %1

My Command field in the GUI editor looks like this:

start /w c:\myfolder\myclaude.bat

My commands.json entry looks like this:

 {
  "trigger": "claude code",
  "command": "start /w c:\\myfolder\\myclaude.bat",
  "offCommand": "",
  "ground": "foreground",
  "voice": "",
  "voiceReply": "",
  "allowParams": "true",
  "quoteParams": "true",
  "mcpToolDescription": ""
 }

@Brad-Magri-Olson, thank you for reporting the issue.

I'm on version 1.0.54 and so far I'm not able to reproduce the issue.

Can you try upgrading to 1.0.54? I tried downgrading my agent and I still couldn't reproduce it.

Also, can you tell me what background command you're running?
Also, what antivirus software do you use? I wonder if that's killing the service.

@David-Coulson, I fixed it. Now you won't get these "TRIGGERcmd - Your command didn't run" emails if the trigger was from Home Assistant.

Thanks again for reporting the problem.

@Nuno-Gomes, thanks for telling me. Please try again. It should work now.

@Asit-Mishra, thanks for telling me. Please try again. It should work now.

@Yoni, thanks for letting me know. I'll make it case-insensitive in the next version.

@Matt-Lodder, what OS are you running? I just tried echo on my Windows laptop and it did not pop up a window.