Triggercmd
for LuumenAI
Run approved commands on your registered machines from the terminal
TRIGGERcmd runs commands on computers you have registered with its agent. Connect it with an API key and Luumen can read your computer list, the commands each one exposes, and your panel buttons. When you ask for a restart or a script run, the agent names the exact command and target machine first, then holds the trigger for your approval.
The Triggercmd toolbox
5 tools: 3 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadList TriggerCMD Commands V2List all available commands for the authenticated user.
- ReadList TriggerCMD ComputersList all computers associated with your TriggerCMD account.
- ReadList TriggerCMD Panel ButtonsRetrieve all panel buttons configured in your TriggerCMD account.
- WriteTrigger CommandTrigger a specified command on a target computer. Approval by default
- WriteTrigger Panel ButtonTrigger a specific panel button. Approval by default
One prompt, start to finish
What a governed Triggercmd run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — trigger command, trigger panel button — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Triggercmd — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Triggercmd to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.