@Xander, got it. Sorry I thought you were suggesting he use Chrome to launch a shortcut. I get your original meaning now.

Just so it's clear to OP, he could put start c:\path\to\shortcut.lnk in the Command field or include it in his script that TRIGGERcmd could run for him. Example:

start C:\Users\russe\Desktop\Claude.lnk

Then if he pre-configured the Run field of that .lnk shortcut, he could make it open Maximized.

870d6398-667f-48d1-a855-aebe81f945c5-image.png

As for OP's 3rd request - to click a button within that window, I'd ask ChatGPT. Just asked it "how to click a button on a web page with a script." here:
https://chatgpt.com/share/68fe7888-36f8-8004-9c72-e7c6385f927b

@Simon thanks again for reporting the error. I'll see if I can reproduce it. It looks like it's in the Home Assistant integration. Sorry about the trouble.

EDIT: I see from your screenshot that this.computer_name was null for some reason, so I added code to prevent a crash when that happens. I'll produce a new version soon.
https://github.com/rvmey/TRIGGERcmd-Agent/commit/b54e988e7d251105bc6faa8c3fa6a5240644cbef

EDIT2: Done - please upgrade to the current version (v1.0.52) to avoid that error in the future.

Thanks @Xander .

@Zaydel-Jiménez, please confirm, you're seeing the "A break point has been reached" error during Windows shutdown? If so, can you get a picture of that error like Furkan did, it might help me. Also, if it happens every time or only once in a while it would also help me to know that.

I couldn't find the old 1.0.48 version but I don't think it will be any better in terms of that error than the latest version 1.0.50 because it contains the same code I thought would fix it. It's a tricky problem to fix because I can't reproduce it myself.

FYI, these are the version notes:
https://www.triggercmd.com/forum/topic/14/triggercmd-agent-versions