I’m having the same issue following the release of 2.0. The extension and Safari are set to use the same engine (ddg), and searches almost never use Kagi in Safari. If I tap the extension under the aA button, it will switch from a ddg results page to Kagi. If I run a new search, it goes to ddg. OS version is 17.2.1.
I’ve deleted, reinstalled, and reconfigured the Kagi extension. It’s enabled for both private browsing and non-private browsing. The extension has access to all pages. I’ve never had trouble with it prior to the 2.0 update.
I’m hoping for a quick fix because I need Kagi to work! I love it so much!