Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
konstk1
7 months agoNew Contributor
Keep 1password in the background (without dock or menu bar icon)
Hi, It appears that if I uncheck "keep 1password in menu bar" and then close main window, 1password shuts down and chrome extension loses connection. This means next time I try to use it, it has to ...
- 7 months ago
Hello konstk1! 👋
Thanks for reaching out! In order for 1Password to run in the background the menu bar icon has to be turned on. This is to ensure that you know when 1Password is running in the background and whether it is locked or unlocked so that you don't have a situation where 1Password is running unlocked in the background without you knowing about it.
I know that there are some third-party apps that allow you to hide menu bar icons, using one of those might give you the functionality that you're looking for.
Let me know if you have any questions.
-Dave
brookjordan
6 months agoNew Contributor
I’ve been going crazy, not able to work out why sometimes 1Password doesn’t work. It’s this! Why isn’t this noted. Why does it say that 1Password will continue working in the background… when, in fact, it will not. It doesn’t even tell you that 1Password must remain open to keep working if you uncheck this item.
But, yes, please, a way to hide everything about 1Password while keeping the cmd-/ shortcut working would be amazing.
1P_Dave: I'll pass along your feedback to the team
Thank you so much. How did the conversation go?
- 1P_Dave6 months ago
Moderator
Welcome to the community! I'm sorry for the confusion, the menu bar icon does need to be enabled in order for 1Password to keep running in the background. Was there a specific reason why you wanted to hide the menu bar icon? Currently, it allows you to know whether 1Password is running and unlocked even after you close the main window.
Why does it say that 1Password will continue working in the background…
Can you post a screenshot of where you see this? And are you running macOS 15.5 or a different version? I'd like to better understand the situation.
-Dave