Situation
I have Kagi Assistant configured to keep threads forever and have accumulated a large number of conversation threads. I regularly need to search through my thread history to find previous conversations.
Task
I was attempting to search through my Kagi Assistant thread history using the built-in search functionality to locate specific previous conversations.
Action
- I accessed the Kagi Assistant thread search box in Safari and Orion browsers
- I began typing search queries character by character
- The interface became significantly slow and unresponsive with each keystroke, exhibiting severe performance degradation unique to WebKit browsers
- I adapted my workflow to copy-paste complete search terms to avoid the keystroke-by-keystroke performance issues
- Even with copy-paste, the search processing remained slow until completion
- Cross-browser verification: The same search operations perform normally in Firefox and Chrome
Result
- Severe performance degradation exclusively in Safari 26.2 and Orion 1.0.2
- Firefox 146.0.1 and Chrome 143.0.7499.170 handle the same search operations without performance issues
- This appears to be a WebKit DOM manipulation performance issue affecting client-side search processing
- The issue forces workarounds that significantly slow my research processes in WebKit browsers
- Makes thread search nearly unusable in Safari and Orion despite normal performance in other browsers
Steps to Reproduce
- Configure Kagi Assistant to keep threads forever and accumulate multiple conversation threads
- Open Kagi Assistant in Safari 26.2 or Orion 1.0.2
- Navigate to thread search functionality
- Begin typing in the search box character by character
- Observe significant performance degradation and interface slowdown
- Compare with same steps in Firefox or Chrome (no performance issues)
While this seems like a Webkit issue from what I can tell, it would be great if the search is implemented in a way that's more practical in Webkit based browsers.
