Wouldn't you then need to sync the randomly generated salt across browsers? That doesn't seem so stateless anymore.

I have made a CLI stateless password manager for myself once (still use it, actually) and I generally "solved" the salt issue by providing the salt manually.

Examples:

    syntax: gassy salt base [password length || 16]

    gassy spoiler news.ycombinator
    gassy email@personal.me home_email
    gassy name@ work.com 32
    

in the next step you're prompted for a password (with echo off). Also, it calculates a token based on the salt which determines in which way the password will be generated.

I know it's not ideal, but it served me well so far! :-)

yes, that's exactly what stepstep said