RoxyRoxyRoxy
Reproduced on a clean fresh profile with just kagi extension present. 
and even without kagi extension.
It does not happen all the time, but looks like more than 70%. It happens both with new tab -- search request -- <ENTER>, and with pre-opened kagi.com.
Additionally to csp-blocked CSS, here is what I see in console log (v= token erased manually):
The script from <URL> was blocked. Since the synthetic response is enabled on this page, scripts are blocked until the new Content Security Policy is added via the <meta> tag.
search?q=chromium+web+store:1 The script from https://kagi.com/asset/a6d6e60/js/k_sea.min.js?v= was blocked. Since the synthetic response is enabled on this page, scripts are blocked until the new Content Security Policy is added via the <meta> tag.
search?q=chromium+web+store:1 The script from https://kagi.com/asset/a6d6e60/js/k_sea.min.js?v= was blocked. Since the synthetic response is enabled on this page, scripts are blocked until the new Content Security Policy is added via the <meta> tag.
search?q=chromium+web+store:1 The script from https://kagi.com/asset/a6d6e60/js/k_serp.min.js?v= was blocked. Since the synthetic response is enabled on this page, scripts are blocked until the new Content Security Policy is added via the <meta> tag.
