Release candidate, 0.6.0

A clearer boundary from page to local note.

This page describes the private 0.6.0 candidate. It is not a claim that the Chrome Web Store item or signed Host installers are publicly available.

What changed

Popup, onboarding, settings, and history

The four surfaces now share one state vocabulary. A local save, duplicate, optional sync failure, missing Host, outdated Host, unsupported page, and consent requirement each have distinct language and recovery actions. Green means a confirmed result, not a request that merely started.

Capture boundaries

Selection keeps exact highlighted text. Page prefers readable extraction and uses a conservative DOM fallback. Element makes the chosen region visible before confirmation. Internal pages and the Chrome Web Store are rejected before capture. Oversized or over-budget captures fail without writing an empty or partial clip.

Store and Host distribution

The candidate has a canonical Chrome Web Store identity while retaining the documented legacy dev-preview identity in Native Host origins during migration. Store packaging removes the public identity key from the upload copy and rejects native binaries, remote code, secrets, and broad permissions. Host bundles include install and uninstall helpers, but remain unsigned build inputs until platform signing and clean-machine verification are complete.

Migrating from the dev preview

The published v0.5.0 GitHub dev-preview extension uses legacy ID mhgcfphfcgbgabhbegdonadkedfaddhc. The 0.6.0 candidate uses canonical Store ID emacefnmbogjdcblglmipolnickjnmbl.

Chrome treats them as separate extensions. Extension storage does not automatically migrate between IDs. During the migration window, the local Host can allow both documented identities, but users may need to recheck settings and consent in the canonical extension.

What has been verified

  • Automated extension, Host-core, capture, consent, credential, history, package-policy, and UI-contract tests.
  • Chrome Web Store archive policy, including omitted manifest key and no Native Host executable.
  • macOS arm64 unsigned Host bundle construction and protocol smoke on Node 20.
  • Store screenshots captured from the 0.6.0 Store-ID candidate with review-safe content.

These checks do not replace signed clean-machine installation tests.

Known limitations

  • Public signed Windows and signed/notarized macOS Host installers are not available.
  • The Chrome Web Store item has not entered public review.
  • Browser internal pages, the Chrome Web Store, and isolated cross-origin frames cannot be captured.
  • Linux and public Edge Add-ons distribution are outside the 0.6.0 candidate.
  • External sync requires user-supplied Notion or flomo credentials and explicit per-destination consent.

Release status

Private candidate only.The next gate is signed Host assets plus clean Windows and macOS installation, capture, update, and uninstall verification. After that, the Store item can go to private trusted testers. Public review comes only after those testers complete a first local clip.

Follow repository progress and source changes on GitHub.