Forum Discussion
1P_Dave It’s my understanding that end users are in this predicament because of decisions that the devs made about no longer unlocking all vaults with the master password of one of them. So they eliminated the default vault feature because they could no longer guarantee that the vault would be available. Instead they implemented some complicated algorithm of which vault to use as a “default” based upon which one is selected, the current phase of the moon, etc. based upon the comments all over this forum it doesn’t seem to be working as designed. But even if it is the problem is that it’s not easily predictable. And that is not a good look when dealing with where a sensitive password is stored. AgileBits should absolutely stop being so stubborn and restore the default vault feature. But in the meantime the current behavior should be removed. It’s better to have no default at all and just make the user explicitly select the vault to save in than to have an unpredictable default.