[1]: https://github.com/kagisearch/bangs?tab=readme-ov-file#bang-...
I don’t use any LLM features of Kagi, and it’s not hindered in any way.
IMO, as they improve their (own/in-house) indexes, I think they’ll be able to build more features on top of standard Kagi search.
The problem is that Google ruined its reputation by showing completely inaccurate results when it started displaying AI-generated results.
We have a an AI integration philosophy that we have been following since day one.
https://help.kagi.com/kagi/why-kagi/ai-philosophy.html
The primary guideline of that philosophy is that any AI feature is opt-in and on-demand rather than being pushed down the user. So to characterize our efforts as you did, can at best be described as doing disservice to reality. Why the need for that?
Happy to see that custom bangs work (eg a discourse forum I visit), but eventually I'd like to specify how far along the path to "snap".
I'd like my @javadoc to hit `site:docs.oracle.com/en/java/javase/23/docs/api/` instead of the current `site:docs.oracle.com`.