Skip to main content
October 9, 2021
Question

Support for Orion Browser

  • October 9, 2021
  • 462 replies
  • 43793 views

Please add support for the https://browser.kagi.com. It needs explicit signature verification from 1Password to work. Otherwise, it should work out of the box.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

462 replies

April 12, 2023

@CostcoFanboy Thanks for the heads up about BitWarden, I will likely follow you and move away from 1Password if this isn't resolved by the time my subscription is up.

April 14, 2023

Quite ridiculous that we still have yet to actually see ANYTHING come from this. It has been two years at this point and all we have continually gotten are the generic copy & paste like 'We promise we are looking into this and will do something about it soon!'. At this point, I am very seriously considering moving away from 1Password once my subscription ends and move to another provider that actually listens to their paying customers.

April 14, 2023

I plus-one'd on this thread back on page one or two, and then in early February of this year I wrote the following. If AgileBits doesn't make good on this by the end of the month, I'm afraid I'm out of here...

This is, I’m afraid, the last straw. I’ve stuck with 1Password even as it gets harder and harder to use (and to support — I’m the “IT guy” for a good dozen clients who are more and more confounded by 1Password with each passing release). I even stuck with you when you went Electron, though the gods know how much worse the interface is now.

But as this thread shows, AgileBits no longer cares about their security-conscious Mac users.

Regretfully, unless there’s a sudden and dramatic shift on AgileBits’s part by the time my renewal is due in May, I’ll be leaving. And I’ll be recommending a different solution to my clients and family.

It’s a shame, too. This used to be such a good company and such a good product.

April 16, 2023

I registered to chime in with a vote for Orion support — it's disappointing to see a heavily upvoted issue get dismissed so casually by staff, especially when Arc was thrown such early support. I hope we se this change soon, but adding a vote for something internally doesn't mean much when nothing happens.

April 18, 2023

Hey folks. Just wanted [...] I'll also have a clearer timeline on the Secure Settings work in the next couple of days that I can share with you. Thanks!

Been more than 2 weeks so far, will be 3 Thursday. Maybe I should apply to https://jobs.lever.co/1password, seems like a fairly cozy gig. 🤔

janpeeters
April 18, 2023

Hi @"matt.g1P," you wrote:

I'll also have a clearer timeline on the Secure Settings work in the next couple of days that I can share with you.
I know that promisses can be challenged by reality but can you tell us more? Thanks.

1P_MattG
1Password Employee
April 18, 2023

Just checked in with the team working on secure settings. It's a small group and they've still got a few issues to close before we can enable 3rd Party Browser support for everyone. It's definitely still happening though!

April 20, 2023

Why can't 1Password just whitelist Orion like they did to SigmaOS or Ark and THEN release the General 3rd Party Browser feature?

1P_Dave
1Password Employee
April 20, 2023

We don't have plans to add other browsers on an individual basis and we're focused on developing our secure settings feature so that folks are able to use any browser they wish to use with 1Password in the future. There are many different browsers (such as Orion, Waterfox, and others) that users have requested support for and secure settings will allow everyone the use of their favourite browser with 1Password. 🙂

-Dave

April 20, 2023

@1P_Dave others have requested but only one browser's cross-community with 1P has a thread with 12 pages over the course of 18 months :/

nobody's disputing that secure settings will be a more permanent resolution, it's just frustrating when other tiny (but VC-backed) browsers received whitelisting during the period that this thread has been active with zero real reasoning from the 1P team as to why that decisioning was made.