[PM-38764] Forwarded email aliases are generated immediately upon viewing the page, rather than after confirming

[PseudoResonance]

Steps To Reproduce

1. Go to "Generator"
2. Click "Username"

Expected Result

Alias should only be generated after clicking a button to confirm.

Actual Result

Alias will be immediately generated upon viewing the page, which can accidentally generate/save a bunch of unused aliases at the service every time you click generator. It makes it really hard to tell what aliases are real and which are garbage that Bitwarden generated when I didn't need it.

Screenshots or Videos

No response

Additional Context

The browser extension functions properly, and requires clicking the "generate" button to generate the initial alias, in order to prevent cluttering up the alias service. By default, the alias field simply says -.

I am specifically using Addy.io, but I suspect the behavior is the same on any service.

Build Version

2026.4.2

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden 1.36.0

Environment Details

No response

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: PM-38764

[PseudoResonance]

The issue is also present on iOS, bitwarden/ios#1571

[pamperer562580892423]

Another user here.

And I would guess, this response by @Krychaz would still be valid: #6357 (comment)

[PseudoResonance]

That's about passwords though, which while annoying is less of a problem in my opinion. Aliases on an external service are going to be calling the API every single time and making a new alias that clutters everything up.