Introducing Desktop App Integration for Mac! 🎉


Team Member
edited August 2020 in Browser Beta

We have something pretty cool that I’m excited to share with you: the 1Password X beta now has experimental integration with 1Password for Mac.

If you have both 1Password X and the desktop app installed on your Mac, you can:

  • Unlock 1Password X with Touch ID (about time!!!)
  • Keep 1Password X unlocked between browser restarts
  • Edit items in 1Password for Mac straight from 1Password X
  • Fill logins from 1Password mini
  • And more…

Desktop App Integration is a major new feature which we’ll eventually be rolling out to all customers, but we wanted our beta friends to be the first to try it out. That’s you! :)


To try out Desktop App Integration, you need:

  1. 1Password X 1.15.BETA-0 or newer (Chrome only for now, stay tuned Firefox friends)
  2. 1Password for Mac Beta that is 7.3 BETA-4 or newer
  3. The same accounts in both 1Password X and 1Password for Mac. If any of the accounts do not match, or if there are a different number, Desktop App Integration will not work.

Set up Desktop App Integration

  1. You will need to unlock 1Password X at least once to configure things.

After you unlock, 1Password X will be connected to 1Password for Mac and you won’t have to go through the setup process again.


How did you do this black magic?
It’s neat, eh? We’ll talk about the tech closer to release, but the short answer is that the clients establish an authenticated connection through your account(s), and then use native messaging to send encrypted payloads back and forth. It’s a much more sophisticated link than the one used in our traditional desktop extension, and it allows for some really intriguing possibilities.

I’m still being asked for my Master Password in 1Password X
Make sure you’ve followed the setup instructions exactly as written. If 1Password X is still not connecting (or if it’s trying to connect and failing) please let us know in the forum. Including your console logs will help us troubleshoot and get you on your way faster.

I didn’t see any confirmation after following all the steps. Is it working?
You won’t see any immediate confirmation. You can test the connection by locking the extension and seeing if the Mac app locks, or vice versa. Then you can try out other features, like clicking Edit on an item. The interface is still a work in progress and will become easier to use as time goes on.

Can I turn off Desktop App Integration after setting it up?
Sure. Just disable the feature and restart your browser. 1Password X will always be able to work independently, with or without the desktop app.

There’s a 1Password desktop app on Windows, too…

Yes, there is! 🤠



  • noelbernienoelbernie Senior Member

    nicely done!

  • dtearedteare Agile Founder

    Team Member


  • DenalBDenalB
    edited February 2019

    I don't use a Mac. But...

    There’s a 1Password desktop app on Windows, too…
    Yes, there is!

    I'm looking forward to a beta which is working with the Windows app. ;)

    Thanks to all of you at 1Password Team! :+1:

  • Thanks guys! I use multiple profiles on chrome and the unlock seems to be working on one profile and not on the other. I installed the beta extension on both profiles and restarted my browser, as asked.

    Also, Editing from 1password x doesnt work as advertised, it still takes my to Wondering if I'm doing something wrong here?

  • dtearedteare Agile Founder

    Team Member

    I'm looking forward to Windows Hello support too, @DenalB! @SergeyTheAgile came to my house earlier this week to hack on this and we're getting closer every day. Hopefully we'll have a beta for you to enjoy soon. 🙂

    @udh: It's great to hear things are working great on your one profile. I'm not sure why your second profile isn't working but I'm sure we can figure it out. My first guess is that the accounts on your second profile don't match your 1Password for Mac exactly.

    Can you double check the accounts you have in 1Password X and in the Desktop App? I know we have one bug at the moment where the sign-in address must be identical. It means if one account uses and another uses, our new Desktop App Integration feature will treat them as different. This is a bug that we need to fix but for now you can workaround this by removing your account from 1Password X and then re-adding it.

    Please give that a go and let us know how it turns out.



  • Hopefully we'll have a beta for you to enjoy soon. 🙂

    Yes, I'm waiting... @dteare . Hurry up please! :chuffed:

    How does it work with a beta version? When I install a beta am I in a kind like a beta-channel? Will I only get beta versions then? Or will I also get the newest final version after all the betas? Or do I have to manually switch back to the final version?

  • MikeTMikeT Agile Samurai

    Team Member

    Hi @DenalB,

    How does it work with a beta version?

    Once 1Password is configured to use the beta update channel, you'll be prompted to get all of our beta updates including ones that are released as stable updates. The way it works is that when we're confident the latest beta update is stable, we release that same beta build to the stable channel. You can choose to switch the update channel back to stable at this point or you can keep it on and get the beta update for the next stable update.

    When I install a beta am I in a kind like a beta-channel?

    You have to manually switch to the beta update channel in 1Password's Update settings. You can do that via 1Password menu > Settings > Updates.

    Will I only get beta versions then? Or will I also get the newest final version after all the betas? Or do I have to manually switch back to the final version?

    You'll get all stable and beta updates.

    You can always switch back to the stable update channel via the Updates setting, you'll be prompted to get the next stable update when it is out and no more beta updates.

  • Thanks @MikeT . And how does it look like with 1Password X? Is there also a beta-channel? Or is it an own extension?

  • AGAlumBAGAlumB 1Password Alumni

    @DenalB: Good question! Chrome doesn't have a concept of "channels" for separate release types, like "beta", "stable", etc., so we have separate "beta" and "stable" extensions in the Chrome Web Store. Cheers! :)

  • so we have separate "beta" and "stable" extensions in the Chrome Web Store

    Good to know. Thanks @brenty . :)

  • Is this integration meant to work with Chrome Canary yet?

    (I followed the steps - and it doesn't seem to be connected - e.g. if I lock 1Password via the Chrome extension, it doesn't lock the Mac app).

    Or are there specials steps we need to do to make the native messaging work?

  • Also, I should mention I did try copying over the .json file:

    cd ~/Library/Application\ Support/
    cd Google/Chrome/NativeMessagingHosts/
    cp ../../Chrome\ Canary/NativeMessagingHosts/

    However, when I restart Chrome Canary - it seems to be stuck at this screen:

  • rudyrudy

    Team Member
    edited February 2019


    does the file have a chrome origin of khgocmkkpikpnmmkgmdnfckapcdkgfaf listed in it?

  • edited February 2019

    No, the file has:

    {"path":"\/Applications\/1Password\/Contents\/Library\/LoginItems\/1Password Extension\/Contents\/MacOS\/1PasswordNativeMessageHost","description":"1Password Extension","type":"stdio","allowed_origins":["chrome-extension:\/\/aomjjhallfgjeglblehebfpbcfeobpgk\/","chrome-extension:\/\/phicbbndgmmpogmijjkbmdhpioaieaha\/","chrome-extension:\/\/fpnbobholfpcolmkinlokiaaanjilcop\/","chrome-extension:\/\/ffgeebhnlfcekjbfekfppddlklaopmok\/","chrome-extension:\/\/aeblfdkhhhdcdjpifhhbdiojplfjncoa\/","chrome-extension:\/\/khgocmkkpikpnmmkgmdnfckapcdkgfaf\/","chrome-extension:\/\/embifcomanedggmloeniaakjemfalpda\/","chrome-extension:\/\/hjlinigoblmkhjejkmbegnoaljkphmgo\/","chrome-extension:\/\/ljbhaimghdpplcjhneliplimpfopbici\/"],"name":""}

    The origin is:


    (I realised that the entire above is rendered as one scrollable line on this forum.

  • rudyrudy

    Team Member


    It looks like it does have the right origin present in it, so its not that the file is missing the appropriate reference for this to work. is 1Password 7 for Mac running when you interact with the extension?

  • Yup, I can confirm that 1Password 7 for Mac is running when I interact with the extension.

    Are there any other debugging/diagnostic logs I can pull from the running extension?

  • I LOVE this!! Well done 1P :)

  • beyerbeyer

    Team Member

    @gerrymcil: Thanks! I'm delighted to hear you're already in love because I'm currently working on making this feature faster and more stable.

    @victorhooi: I've stopped running Canary due to me wasting time tracking down issues that always ended up being a Chrome bug. However, I did just install Canary from scratch, copied over my NativeMessagingHosts file like you, and everything seems to be working fine here. Can you double-check that your version of Canary is up to date and doesn't require a restart to finish a pending update (Chrome > About Google Chrome)?

    Assuming everything is good to go there, can you email me your console logs from the background page of 1Password X?

    Attach the diagnostics to an email message addressed to [email protected].



  • Can we customize suggested passwords?

  • AGAlumBAGAlumB 1Password Alumni
    edited February 2019

    @HHACU: While it isn’t possible to customize the Suggested Passwords 1Password X makes for you conveniently, with a composition that works well in most cases, the Password Generator is there if you want to use different options:

    Cheers! :)

  • 1P updated today to;

    1Password 7
    Version 7.2.6.BETA-1 (70206001)
    AgileBits Beta

    It appears since the update the 1P X chrome extension appears to have stopped working with the desktop integration. I've tried reinstalling the extension but to no avail.

    It continues to ask for the master password every time the browser restarts. Any ideas?

  • dtearedteare Agile Founder

    Team Member

    Thanks for reporting this issue to us, @gerrymcil. 🤗

    I'm unsure why things would stop working with that update. We made many changes but I thought we managed to find a way to keep the old version of the extension working with the new version of 1Password for Mac.

    I suspect this will fix itself today when we release the new version of the 1Password X beta, but just to be sure, could you take a peek at your console logs and share with us any errors you see there? It's probably easiest to just take a screenshot and attach it here.



  • Hi @dteare ,

    Thanks for getting back.

    I have attached a console log as requested.


  • It looks like the update to the extension today has sorted the issue @dteare :)

    So happy!!!

  • dtearedteare Agile Founder

    Team Member

    Awesome! Happy to hear things are back to normal for you with the new beta.

    Thanks for the error log by the way, it was quite helpful.


  • I just came across this post and am excited about the Desktop App Integration and ability to use Touch ID!

    However, I am using Vivaldi and when I right click on the icon of the 1 Password X Beta extension, I don't get an option for Experimental Features...Am I just out of luck with Vivaldi or is there another way to set this up?

  • beyerbeyer

    Team Member
    edited March 2019

    Hey @geeduhb,

    Unfortunately, Vivaldi doesn't fully support the chrome.contextMenus API which means any browser action context menus we create are not available. 😢

    However, if you're willing to get your hands a little dirty, you can enable Desktop App Integration by following the steps below:

    1. Right-click the 1Password icon in the toolbar and choose “Manage Extensions”.
    2. Click the toggle next to “Developer mode” to enable it (if it isn't already).
    3. Click the “background page” link under “Inspect views.”
    4. Click the Console tab in the DevTools window.
    5. Paste the following function into the Console and hit enter:
      localStorage.setItem('features', '[["nativeUnlock",true]]')
    6. Restart your browser, and Desktop App Integration will be enabled.

    To disable it, follow the same steps above, expect paste the following instead for Step 5:
    localStorage.setItem('features', '[["nativeUnlock",false]]')

    Please let me know if that works for you! 😃


  • Awesome @beyer, this is exactly what I was looking for and did the trick!

    It did take a little fooling around with because in the console, the "message" to the local app seemed to fail the first time, and then after I quit the browser again and reopened it for a second time it said it successfully sent. However, then it wasn't contacting the app to unlock with Touch ID, only presenting me with the password box every time it locks. I was able to fix it by locking the app, quitting out and reopening, at which time it made the connection/call to the app itself to unlock.

    Anyway, I continue to be impressed by the customer service in this forum. You guys are extremely active and always willing to help figure out issues. I am very happy to be a customer. Thanks!

  • BenBen AWS Team

    Team Member

    Thanks for the kind words, @geeduhb. I'm glad to hear beyer's steps worked out for you.


  • I was excited to come across this discussion, but it's not working for me... I followed the instructions, but 1 Password X still isn't connecting with the desktop app, even after completely exiting the browser, restarting, etc. 1 Password X and 1 Password 7 desktop are both up to date. Anything else to try?

This discussion has been closed.