Setup, Clipplane

Current availability

macOS-first distribution.The stable extension 0.9.0 reuses the signed, notarized, and stapled Host 0.8.0 package for macOS arm64 published through the immutable v0.8.0 GitHub Release. Windows has no official binary installer; its best-effort path uses a full commit SHA and PowerShell setup scripts. Never use third-party Host mirrors or unsigned installers presented as Clipplane releases.

The extension zip is an asset on the immutable v0.9.0 GitHub Release; the macOS Host package stays on the pinned v0.8.0 release. The active Inbox is Markdown and Host protocol 3 is unchanged, so the 0.9.0 extension works with the existing Host. Windows source setup requires Git and Node 24.13 or later in the Node 24 line. Linux, macOS x64, and Windows arm64 are not public targets.

Install on a supported system

macOS arm64

Download clipplane-host-v0.8.0-macos-arm64.pkg from the immutable release.
Before opening it, run shasum -a 256 clipplane-host-v0.8.0-macos-arm64.pkg and require 1f714ca3a455458f3669e60cec02b1038be105270f4add05083637338479521c. Run pkgutil --check-signature clipplane-host-v0.8.0-macos-arm64.pkg and require Apple Team ID S7V7CK2G9T.
Open the package and complete installation.
Close every browser window, reopen Chrome or Edge, then choose Check again in Clipplane.

Windows x64 from source

Install Git plus Node 24.13 or later in the Node 24 line. Do not execute a tag's Source code archive.
In PowerShell 7, run $clipplaneCommit = "1c19c56f2745e32a156f4659d93cca865f553695", git clone https://github.com/KKenny0/Clipplane.git, cd Clipplane, and git checkout --detach $clipplaneCommit.
Require (git rev-parse HEAD).Trim() to equal the full commit above, then run npm ci --omit=dev --ignore-scripts followed by npm run setup:windows:chrome or npm run setup:windows:edge.
Close every browser window, reopen Chrome or Edge, then choose Check again.

Windows source setup registers the Host under the current user's HKCU registry and remains best-effort support. Clipplane publishes a self-contained Host bundle for verified Windows workflows, but no signed Windows installer or SmartScreen reputation is promised.

Detection and updates

The onboarding page checks the Host version and protocol. A successful check means the browser can reach the expected local Host. It does not enable external sync.

On macOS, install a newer signed package only after its digest and Apple Team ID match the documented values. On Windows, check out the documented full commit, run npm ci --omit=dev --ignore-scripts, and rerun the setup command. Restart every browser window and check again. Clipplane keeps missing and outdated states separate.

What a failure state means

State	Meaning	Next action
Host missing	Chrome cannot find or connect to the local Host.	Install or repair the Host, restart all browser windows, then check again.
Update required	The Host answered, but its protocol is older than the extension requires.	Install the current matching Host and restart Chrome.
Forbidden	The Host registration does not allow this extension identity.	Reinstall from the matching official candidate. Do not edit the manifest by hand.
Unsupported page	The browser prevents capture on this surface.	Use a normal web page. Internal pages and the Chrome Web Store cannot be clipped.
Consent required	An external destination is configured without current per-sink consent.	Open Sync settings and review the fields before enabling it.
Note saved, sync failed	The note exists, but the optional external request failed.	Keep the note and retry sync. Do not capture again.

Uninstall

The macOS package includes the matching Host uninstall helper. Windows source users run pwsh -NoLogo -NoProfile -File .\scripts\uninstall-native-host.ps1 from the matching source directory. Uninstall removes owned Chrome and Edge Host registrations and deletes Clipplane's Notion and flomo credentials by default; local notes and capture files remain untouched.

Do not include secrets in support reports.If setup still fails, use Copy diagnostics in Storage or follow the safe report checklist on the Support page. The built-in report omits personal paths, captured content, and credentials.