Obv kagi products get added sometimes or UI changes, so custom CSS also needs to change.
Currently there is a problem (in my opinion) and there's a quality of life. Both could be solved the same solution:
Allow people to give a url for the custom css.
For example, I could use jcrabapple's raw css url from their site: https://repo.jcrabapple.com/jcrabapple/82208449e52b434a8e695c8124fa3f79/raw/HEAD/kagi-catppuccin-mocha.css
and I would be able to plonk that into the custom css page.
It would then pull down the css from that page and apply that.
One of the other things this would solve is the problem of "i installed this custom css and it'd like to see if there is an update for it.... oh wait... where did I download it from again?"
For safety reasons (I assume you can do js injections through css somehow) I guess you'd need to have a window that shows the new css and asks the user to confirm to apply or show an actual git-style diff.
How I imagine this working:
You go to the custom css page https://kagi.com/settings/?p=custom_css
it has a field for url. you put in a url, it downloads it and previews the code to you. the user then has to confirm. and it's applied
next time the user visits the page, it will redownload and check if it's changed. if so, it'll show an 'update available' button. clicking that will show the new css or a diff. and once again the user can confirm before it applies
