The Kariant Krome extension
Kariant Krome is a free browser extension that puts Kariant in your browser: Klick chat in the side panel with web↔extension continuity, "k" search from the omnibox, page insight, and SynthID verification. Krome does not run on the sites you visit until you grant it site access in Krome ▸ Settings, and journey and kontext capture stay opt-in and off by default.
What Krome does todaylink
- check_circleSide-panel Klick chat — the Klick AI assistant in your browser’s side panel, with web↔extension continuity: a conversation started on kariant.app continues in the extension and vice versa.
- check_circleOmnibox search — type "k" followed by a space in the address bar to search Kariant from anywhere.
- check_circlePage insight — ask Klick about the page you are on and get grounded context.
- check_circleSynthID verify — check content for Google SynthID watermarking to help spot AI-generated media. Right-click any image and Kariant fetches and checks it server-side.
- check_circleOpt-in journey and kontext capture — OFF by default; if you turn it on, your browsing journey can enrich your Kontext profile for better personalization. You can switch it off again at any time.
Site access: you grant it, per grouplink
On a fresh install, Krome runs on kariant.app only. Nothing is injected into the other sites you visit until you turn on a site-access grant in Krome ▸ Settings, and each grant is a standard browser permission you can revoke at any time from chrome://extensions.
Turning a grant off removes Krome’s scripts from those pages immediately — you do not have to restart the browser, and you do not have to uninstall the extension to stop it running somewhere.
- check_circleOn-page intelligence (any site) — the Krome button, intelligence sidebar, buyer intel, price tracker, competitor radar, journey scanner and Kontext capture.
- check_circleLead discovery (LinkedIn / X) — partner lead capture on those two sites only.
- check_circleDemand signals (Reddit / Hacker News / Product Hunt / Indie Hackers / Quora) — partner signal spotting on those community sites only.
Privacy: capture is off by default, and every capture is listedlink
Krome captures nothing about your browsing unless you explicitly opt in. Journey and kontext capture ship disabled; enabling them is your choice, and disabling them again takes effect immediately.
When a scan does send page text to Kariant AI, Krome logs it: Krome ▸ Settings lists the site, how much text was sent, when, and whether identifiers were redacted before it left. The first time it happens you also get a one-off notification, so the behaviour is never silent. You can clear that log at any time.
Identifiers found in page text — email addresses, phone numbers, card numbers, IBANs, and Indian identifiers such as Aadhaar, PAN, GSTIN and IFSC — are redacted server-side before any AI model sees the text.
Sensitive sites are never scanned. Banking, payments, crypto, brokerage, health, government, webmail, password-manager and sign-in pages are excluded, as are intranet and private-network addresses (for example a company wiki on an internal hostname or a private IP).
Separately, Kariant partners have a capture suite (lead capture, demand signals, price captures, competitor visits) whose results are reviewed by the partner at /partner/krome — that suite operates within the same consent rules and never overrides your capture settings.
Install Krome (self-hosted zip)link
Krome is distributed as a self-hosted zip from kariant.app/krome — it is not on a web store. It runs on Chromium-based browsers, version 116 or newer (Chrome, Edge, Brave, and similar).
- 1Download the extension zip from kariant.app/krome and unzip it to a folder you will keep.
- 2Open your browser’s extensions page (for example chrome://extensions) and turn on Developer mode.
- 3Click "Load unpacked" and select the unzipped folder.
- 4Pin Krome to your toolbar, sign in, and the side panel is ready.
- 5Open Krome ▸ Settings and turn on the site-access grants you want. Until you do, Krome runs on kariant.app only.
Connecting your Kariant account to the extensionlink
Signing the extension in from the web uses a direct, private browser channel between kariant.app and Krome — your session token is never placed anywhere another extension or a script on the page could read it.
That channel needs a current build on both sides. If /krome reports "Your installed extension predates the secure handoff", download the latest zip from kariant.app/krome, reload the extension, and reload the page. Signing in inside the extension with your email and password always works as an alternative.
While Krome is distributed as a self-hosted zip rather than a published store listing, one-click connect from the web is switched off: kariant.app will only hand your session to an extension whose identity it can verify in advance, and a self-hosted build does not have a fixed published identity yet. If /krome says secure connect is not available in this build, sign in inside the extension with your email and password — everything else works the same. Reloading or reinstalling will not change it; it turns on when Krome is published.
The extension connection screen behaves the same way for now: it shows a "Krome connection coming soon" notice with the Allow action disabled — you can only deny or close it, and no access is granted until the connection flow ships.
Frequently asked questions
Does Krome track my browsing?expand_more
Not unless you opt in — and not at all on sites you have not granted access to. Journey and kontext capture are off by default; with capture off, Krome only acts when you invoke it (side panel, omnibox, page insight).
Which sites does Krome run on?expand_more
kariant.app out of the box, plus whichever site-access grants you turn on in Krome ▸ Settings. Each grant is a normal browser permission — revoke it there or from chrome://extensions and Krome stops running on those pages straight away.
Can I see what Krome has sent to Kariant AI?expand_more
Yes. Krome ▸ Settings lists every page capture: the site, the amount of text, the time, and whether identifiers were redacted first. You can clear the log whenever you like.
Why is the install a zip instead of a web store listing?expand_more
Krome is currently distributed self-hosted from kariant.app/krome. Installing via "Load unpacked" on a Chromium browser (116+) takes under a minute and keeps you on the latest build Kariant publishes.
/krome says secure connect is not available in this build — is something broken?expand_more
No. One-click connect from the web is deliberately switched off until Krome is published, because kariant.app hands your session only to an extension whose identity it can verify beforehand. Sign in inside the extension with your email and password in the meantime; the side panel, omnibox and page insight all work normally once you do.
Do my Klick conversations sync with the website?expand_more
Yes — that is the web↔extension continuity. A chat started on kariant.app is available in the side panel and the other way around, under the same account.
"Continue with Google" fails in the extension — what now?expand_more
Each Kariant extension needs its own Google OAuth client bound to its extension ID, and that registration is still being completed. Krome now tells you exactly which client and extension ID were rejected instead of a generic error. Sign in with your email and password, or connect from kariant.app/krome, until it is finished.