# Secret Agent not called up properly

**URL:** <https://discuss.zetetic.net/t/secret-agent-not-called-up-properly/688>\
**Category:** Codebook\
**Created:** [July 27, 2015, 10:54pm UTC](https://discuss.zetetic.net/t/secret-agent-not-called-up-properly/688 "2015-07-27T22:54:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Husni\_H](https://avatars.discourse-cdn.com/v4/letter/h/779978/32.png) [@Husni\_H](https://discuss.zetetic.net/u/Husni_H)\
**Post date:** [July 27, 2015, 10:54pm UTC](https://discuss.zetetic.net/t/secret-agent-not-called-up-properly/688/1 "2015-07-27T22:54:35Z")

</div>

I used the default keybinding ‘Ctrl+Shift+’ to bring up Secret Agent. It works the 1st time, but on the subsequent time the Secret Agent seems to think that I pressed the last ‘’ again and clears the previous search and shows ‘’ instead. I tried with different keybinds e.g 'Ctrl+Shift+.'but it still behaves the same way. I have changed the keyboard settings repeat rate but did not resolve the issue. I’m seeing this issue on MS Surface Pro 3 with Surface Pro keyboard (Windows 8.1) and also HP 8460p laptop (Windows 7).

E.g.  
Press ‘Ctrl+Shift+’ for 1st time.  
Secret Agent pops up.  
Key in ‘Gmail’ in Secret Agent.  
Gmail entry appears. Double click on Website.  
Secret Agent disappears. Website opens in web browser.  
Press ‘Ctrl+Shift+’ for 2nd time for login name.  
Secret Agent pops up and briefly shows the ‘Gmail’ entry and then immediately show ‘’ in the search window.

Please help.

---

<div class="post-metadata">

**Author:** ![developernotes](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/developernotes/32/1309_2.png) [@developernotes](https://discuss.zetetic.net/u/developernotes)\
**Post date:** [July 28, 2015, 1:05pm UTC](https://discuss.zetetic.net/t/secret-agent-not-called-up-properly/688/2 "2015-07-28T13:05:47Z")

</div>

Hello @Husni_H

I’m sorry to hear about the behavior you are experiencing. We have received one other report of this behavior, however we have not been able to reproduce this locally. We will continue to investigate this further. Thank you.
