@Russ It still didn't work properly, only the "Gnome editor" shows up in my account.
Here are the installdaemon.sh installation prints, with the defined commands and the status up of my agent with the account.
If you don't have more options to solve the problem, I appreciate the help, I insisted on Trigger in debian because it was very useful when I was using it in Ubuntu 22.




Hello everyone, I hope you are doing well.

I did the test here as instructed, but I really think there is something that needs to be corrected in Triggercmd for Debian 12, because as you can see in the prints, by default it is already defining these commands, but in my account when I go to the option " View triggers", it only brings me to "Gnome Editor", if I change the name of it in the commands.json file it disappears from my account. So I assume this is really an incompatibility with Debian 12. Since it only brings a single command among the 4 defined in the file and if I change the name of the single command or even the command itself it disappears from my account.

In my case, the interface no longer appears after I login with the token. After this process, the triggercmdagent interface does not open at all.

About the file you asked me to change, what should I change exactly?

bolded text

Hello everyone, I hope you are doing well.

I'm facing a problem here with the triggercmdagent, I updated my pc from ubuntu 22 to debian 12, until then in ubuntu the agent was working normally. Now in debian 12 when I run the agent on it, I can register the new pc, but after that the agent does not show the interface so that I can create my scripts. I already uninstalled it and installed it again, removed the pc and re-registered on the platform, turned off the computer and restarted. I would like to know if triggercmdagent is not compatible with debian 12 or am I doing something wrong?