Repository navigation
Not able to commit changes when using GPG-autosigned commits #274
Description
To be fair, it's entirely possible I'm just a noob or an idiot here. I have my Git config set up to automatically sign my commits using a GPG signature, which is configured with a passphrase. However, that means when I try to commit changes using the T3 Code interface, it simply returns an error, as there is no mechanism to accept my GPG passphrase.
This leaves me with one of two options:
- Update my Git config so automatic signing is turned off
- Manually commit changes using the terminal
As of right now, I've chosen the latter.
Edit: Just realized I can configure the Git config locally. Still not ideal, but a better temporary solution.
Reacted by Can Rau, Niklas Wojtkowiak, Sargun Vohra and Alex Martossy
Reacted by Can Rau
Activity
0xnim commentedon Mar 12, 2026
I know jetbrains uses pinentry for the gpg input
sargunv commentedon Apr 12, 2026
I have a similar issue, but my signing is configured not with a passphrase, but with an SSH key in my mac's TPM. So I just need to touch id to sign my commit. I'd expect that to work since it needs to TTY input (works properly with conductor, other IDEs, etc) but T3 Code still fails with:
No touch id prompt was presented.
sargunv commentedon Apr 12, 2026
asking the agent to "commit and push" within t3 code works fine though. (with touch id), even though the tty situation is the same. I'd be happy if the "commit and push" button just injected an instruction to the agent (so it can write the commit message, deal with pre-commit failures, etc autonomously).
maria-rcks commentedon Oct 9, 2026
Note
This is an automated response from a bot acting on maria's behalf.
This issue has had no activity since 2026-04-12.
Is it still relevant on the current version? If so, your version and OS would help.
alexaka1 commentedon Oct 9, 2026
What would be appropriate for activity on the issue? I can easily setup a bot to keep commenting. The issue is easily reproducible, just set up commit signing in your git config with a key that requires a passhprase or pin entry.
sargunv commentedon Oct 9, 2026
I ended up using a plaintext key for commit signing because of this issue