Skip to main content
January 15, 2025
Solved

Clear Search Field without Mouse?

  • January 15, 2025
  • 4 replies
  • 300 views

front from the background if the app hasn't locked the most recent search is still typed in with those results on the screen.

I don't remember this happening in older versions and there does not seem to be a way with a keyboard shortcut to clear the search field even if you typy CMD+F it takes you the search bar but if there is already a search result typed in you cannot clear it without using your mouse to click the "X" that says cancel search.

I FEEL like ESC button use to clear the search field if you were in the search bar but that won't work.

I'd be happy even if I had to make a keyboard maestro macro or applescript to clear it on reactivation but moving the mouse really bugs me!


1Password Version: 8.10.56
Extension Version: Not Provided
OS Version: macOS 16.2
Browser: Not Provided

Best answer by 1P_Dave

@BrianAMartin221 

Thank you for the reply. I don't believe that there's currently a dedicated shortcut to cancel search so that you no longer see the previous search results. One option would be to press CMD 1-9 to choose your current account/collection which will bring you back to All Items.

I'll share your feedback with the team, thank you for posting! 

-Dave

4 replies

GreyM1P
1Password Employee
January 23, 2025

Hi there @BrianAMartin221

⌘A (Command–A) then ⌫ (Backspace or Delete) will select all the text in the search box and then delete it. Will that work for you?

So, the sequence of events would be:

  1. ⌘F (Command–F) to go to the Search box.
  2. ⌘A (Command–A) to select any text in the Search box.
  3. ⌫ (Backspace or Delete) to clear it.

Let me know if you have any questions. :)

— Grey

April 3, 2025

Grey

Steps #1 & #2 work fine but when I hit backspace, it does clear the search field but the previous filtered results are still showing I have to run a new search to change what is showing.

1P_Dave
1P_DaveAnswer
1Password Employee
April 15, 2025

@BrianAMartin221 

Thank you for the reply. I don't believe that there's currently a dedicated shortcut to cancel search so that you no longer see the previous search results. One option would be to press CMD 1-9 to choose your current account/collection which will bring you back to All Items.

I'll share your feedback with the team, thank you for posting! 

-Dave

April 28, 2025

What a ridiculous solution from the 1password team. Just make the whole field selected (like typing cmd+a) instead of these insane workarounds. 

1P_Dave
1Password Employee
April 28, 2025

@savah 

I'm sorry for the frustration. Just to clarify, if you press CMD-F you should see the previous search term automatically focused and selected aside from certain specific situations that our developers are looking into. 

Can you tell me a little more about the scenario where you don't see the field selected? I'd like to make sure that the issue is filed with our team as something to resolve in the future. 

-Dave

April 29, 2025

See the screenshot. I have searched initially for 365, and copied a password from the results. Switched to a different app and then i came back to 1password to get another password. Hit again CMD+F and instead of highlighting the previous password and make typing work straight away, 1password only adds up the new search term to the previous one, so you will end up searching, for example, "365 gmail". Workaround? Remember to hit CMD+A before searching to do this.

Absolutely insane, i wonder how the team has not thought of this productivity and efficiency killer. I have beared with it for 2+ years but enough is enough.

 

April 29, 2025

 

You can see the screenshot. I have searched for "365" and it showed results. I switched windows and came back to 1password to search for something else. I hit cmd+f and instead of highlighting the previous search to facilitate immediate typing it just adds to the previous search obviously producing 0 results. Each time i have to remember to hit cmd+a and then start typing which is mindblowing. I have been doing this for 2 years but enough is enough.

1P_Dave
1Password Employee
April 29, 2025

@savah 

Thank you for the screenshot. I can confirm that I've been able to reproduce the issue here on my end and that our development team already has an internal work item open to get this fixed with a future update in their backlog. I've added your report there. 

I'm sorry for the disruption to your workflow. 

-Dave