I would like Command Tasks and Key Sequence Tasks to support resolving credential replacement tokens such as $EffectiveUsername$ and $EffectivePassword$ directly from 1Password items.
Current behavior: when a task references a 1Password item by credential name, $EffectivePassword$ resolves to an empty value.
Expected behavior: if the credential name matches a 1Password item visible in Royal TSX, task tokens should resolve from that item’s username/password fields, the same way they do for native Royal TSX credentials.
This would make it possible to securely use 1Password-stored secrets in automation tasks without duplicating them into Royal TSX credentials.
I would like Command Tasks and Key Sequence Tasks to support resolving credential replacement tokens such as
$EffectiveUsername$and$EffectivePassword$directly from 1Password items.Current behavior: when a task references a 1Password item by credential name,
$EffectivePassword$resolves to an empty value.Expected behavior: if the credential name matches a 1Password item visible in Royal TSX, task tokens should resolve from that item’s username/password fields, the same way they do for native Royal TSX credentials.
This would make it possible to securely use 1Password-stored secrets in automation tasks without duplicating them into Royal TSX credentials.