Thank you — this is incredibly helpful feedback, and I really appreciate you taking the time to actually install and test it. You’re absolutely right about the

Thank you — this is incredibly helpful feedback, and I really appreciate you taking the time to actually install and test it. You’re absolutely right about the README. Right now it’s too abstract and assumes context that a first-time user doesn’t have. I’ll add concrete examples with command output and input flow so it’s clear what to expect before installing anything. Good catch on the password confirmation during init — that’s a real footgun. I agree it should prompt twice and fail early if there’s a mismatch. I’ll fix that. The storage/location behavior is also on me. At the moment it defaults to the current working directory, which clearly isn’t intuitive or well-documented. I need to make this explicit and likely move toward a config file + deterministic path (or a required --path), so behavior is predictable regardless of where the command is run. On the password prompt: lockify currently relies on the OS keyring to cache the passphrase after first entry for local dev convenience, which is why you weren’t prompted again. I agree this needs to be much clearer, configurable, and better documented — including when the tool will and won’t prompt, and what security tradeoffs that implies. This is exactly the kind of “stranger workflow” feedback I was hoping for. I’m still early in the project, and comments like this are what will make it usable. Thanks again, and I’m glad to hear you might revisit it once it matures.