@insaneoctane, I'm sure it was #3.
It has to show up on the webpage before you can trigger the command with the API, and background commands don't show up until you install the background service. That background service feature is often misunderstood. I almost wish I didn't include it. It's meant to allow you to trigger commands in the context of a Windows service or a Linux daemon so you don't have to be logged in for the commands to run.
