Extension
Chrome Extension Disclosure
What the Huske Chrome capture extension can access, what it sends, and how every capture enters review.
Beta notice / Effective July 18, 2026
Purpose
The extension helps you stage the current page as project memory: URL, page title, selected service category, project assignment, role, note, and related capture context. It is not a general browsing-history collector or content crawler.
activeTab permission
activeTab gives the extension temporary access to the tab where you explicitly invoke the Huske action. It does not grant standing access to every page or broad browsing history.
storage permission
storage keeps the configured Huske app URL in browser.storage.local. It does not persist selected project/context and is not used as a copy of the Huske workspace database.
Exact host permission
The production manifest allows requests only to https://huske.io/*. Development builds use http://localhost:3000/*. The extension does not request wildcard access to arbitrary third-party hosts.
Staged review
Submitting from the extension stages a capture in Huske. The capture is not silently attached as durable project memory: Decisions lets you approve the suggested assignment, adjust details, or dismiss it.
Authentication and workspace boundary
Extension requests use Huske's authenticated capture routes and server-side workspace resolution. The extension does not receive provider OAuth tokens, Project Agent tokens, database credentials, or workspace-export access.
Data not requested
The capture flow is not designed to collect passwords, API keys, private keys, source repositories, complete page bodies, or payment data. Do not place secrets or regulated data in capture notes.
Questions
Email hello@huske.io with extension privacy, permission, or staged-capture questions before using the beta on sensitive pages.
Contact Huske