More recent versions of Bitwarden have added support for SSH keys and added an SSH agent to the desktop app. Currently, Goldwarden still uses secure notes to store SSH keys. Instead, it should just directly use the new SSH key item type. It'd be useful for compatibility with the actual Bitwarden application, so both Goldwarden and Bitwarden can use the same keys in their respective SSH agents.
A temporary workaround for this issue is adding your ssh keys twice - generating them in Bitwarden or Goldwarden, then making a custom note or SSH key with the same key details.
Additionally, I think the UX of using SSH keys in Goldwarden could be improved. Maybe this should be its own issue, but idk. My main two problems are that you have to use your master password (as opposed to the PIN that you can use to unlock your vault) to "unlock" the SSH key whenever using it (although it seems to remain "unlocked" for a little while after "unlocking" it), and that you get a desktop notification every time the SSH key is used. I understand why this is the case; to notify you if there's an application using your SSH key without your consent. It does get a bit annoying when using applications like lazygit that create SSH connections without user input - I don't need Goldwarden sending me a notification every time lazygit polls an SSH remote. The image below is exaggerated, I was manually pulling, but it is a genuine problem imo.
More recent versions of Bitwarden have added support for SSH keys and added an SSH agent to the desktop app. Currently, Goldwarden still uses secure notes to store SSH keys. Instead, it should just directly use the new SSH key item type. It'd be useful for compatibility with the actual Bitwarden application, so both Goldwarden and Bitwarden can use the same keys in their respective SSH agents.
A temporary workaround for this issue is adding your ssh keys twice - generating them in Bitwarden or Goldwarden, then making a custom note or SSH key with the same key details.
Additionally, I think the UX of using SSH keys in Goldwarden could be improved. Maybe this should be its own issue, but idk. My main two problems are that you have to use your master password (as opposed to the PIN that you can use to unlock your vault) to "unlock" the SSH key whenever using it (although it seems to remain "unlocked" for a little while after "unlocking" it), and that you get a desktop notification every time the SSH key is used. I understand why this is the case; to notify you if there's an application using your SSH key without your consent. It does get a bit annoying when using applications like lazygit that create SSH connections without user input - I don't need Goldwarden sending me a notification every time lazygit polls an SSH remote. The image below is exaggerated, I was manually pulling, but it is a genuine problem imo.