Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
4 years agoCLI cache is either not working or not significantly reducing time to return a secret
Hi,
I have been testing the 1password CLI (along with secrets automation, ssh and other things) for personal things but also with the idea of increasing use at $dayjob and everything is working ...
andi_t_1P
1Password Team
4 years agoHi @gunzy83 , thanks for bringing this up! I elevated this internally to make sure we are not missing any significant points of improvement. For now, to try to answer your questions, you might see all those requests if you have biometric plugin enabled and the unlock happens with every command, so a bunch of auth requests are done in the background. Besides that, the CLI does invariably retrieve metadata about your account. Additionally, if the field you are trying to retrieve is a file, an extra request will be made to download that file.
You are right when saying that the CLI does not work offline like the desktop app, and yes this is intended, at least for now.
Something to note: caching is enabled by default so when not specifying the cache flag, it will still work in the background. To de-activate it you need to specify --cache=false.
All the best,
Andi