"Capture Screenshot (Configurable) -> Run Terminal Command" defined command is shared between all actions.

For my use case, this is not a blocking issue but as I noticed it, I believe it should be reported.

I wanted to have two different shortcuts using Configurable Screenshots :

  • Shift+Option+S to make an interactive screenshot and open it.
    It runs open {filepath}

  • Shift+Option+S to make an interactive screenshot and translate its contents.
    This one runs shorcuts run ... as described in Translate anything displayed on the screen.

Whenever I select "Run Terminal Command" in "After Capture" field, a pop-up shows up and I can define the command.
However it sets the command for all the Configurable Screenshots using "Run Terminal Command".
Which means both my shortcuts run the same command!

In my case I switched the first "After Capture" to "Open in other application ..." and selected my default application to open pictures, so this is not a blocking bug.

Thanks,
Aurel

I'm experiencing the exact same issue. After examining the trigger definitions, I can see why this happens: both shortcuts use the "Capture Screenshot (Configurable)" action with BTTRunTerminalCommand, but there's no way to distinguish between them to execute different terminal commands.

The terminal command parameter appears to be global to the screenshot action rather than trigger-specific…

exported_triggers.json (2.5 KB)