That was a mistake and the extension was updated to remove that permission. Source: their blog posts, and the extension update that doesn't require this permis

That was a mistake and the extension was updated to remove that permission. Source: their blog posts, and the extension update that doesn't require this permission. https://kagi.com/changelog https://kagi.com/changelog > Note: Our initial release of extension (0.3) had wrong scope of permissions. Thanks to the quick and efficient intervention from our community, this was mitigated. Make sure you are using 0.3.3 version.