This setting does exist for "Universal Autofill" [1] which is what I use instead of any browser extensions because I don't want to get phished when I'm not at my best. [2] [3]
On the Mac app, the setting is at the bottom of the General settings screen.
The downside to forgoing the browser extensions is that creating new logins is painfully manual. The risks of using the extensions just freak me out too much.
Painfully manual. Every time I have to delete the word "Login" when creating new login, I wonder how hard could it be to vibecode myself what I want. I fantasize about getting a job there to fix the UX issues and then quit.
The toy example with an API definition that includes zero semantic documentation doesn’t give me a lot of confidence that TypeSpec helps author API definitions that are actually good. It’s easy to create a concise language if all you want to generate is boilerplate.
What I desperately want is the generation of a lock file so that environment installs are cryptographically guaranteed to be repeatable byte-for-byte. I recognize that this means either checksums every platform supported, but I’ve been startled that none of the options I’ve found seem to have the capacity for this.
Unfortunately, neither nix flakes nor tools based on nix that don’t “easily surface” this feature provide the security guarantees I’m seeking, since security guarantees are a function of cryptographic proofs and abstractions that are comprehensible to an end user.
On the Mac app, the setting is at the bottom of the General settings screen.
The downside to forgoing the browser extensions is that creating new logins is painfully manual. The risks of using the extensions just freak me out too much.
[1]: https://support.1password.com/mac-universal-autofill/
[2]: https://hudlow.org/2026/practical-antiforgery#two-steps-forw...
[3]: https://hudlow.org/2026/practical-antiforgery/demo/1password
reply