Repository navigation
feat(clipper): Lens web clipper browser extension, Chrome first - #277
Merged
Merged
Conversation
A MV3 extension in extensions/browser: clip the page (Readability), the selection or a picked element to Markdown with MarkDownload-style templates, and send it to Lens through a namespace's import webhook. Shared core for the Firefox, Edge and Safari targets; CI builds a zip per target and attaches them to releases. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018uA6PhZXrmpgsbfDh2W23u
This was referenced Oct 10, 2026
18 of 22 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: the only way to get a web page into Lens was to paste text or push its URL to an import webhook by hand.
After: a browser extension (Chrome first, in
extensions/browser/) clips the page, the selection, or a part you pick into Markdown and sends it to Lens. It works like MarkDownload:{title|kebab},{date:YYYY-MM-DD}, filters, YAML front matter (empty lines dropped), and a separate template for selections.How: everything goes through the existing
POST /api/v1/hooks/import. Markdown is sent as JSON{text, title}, or as multipart when it includes images or the URL. You can add one import-hook token per namespace. Tokens stay in local storage and everything else syncs. Host permission is only asked for the Lens address you add. The shared core insrc/core/is plain WebExtension code (browser ?? chrome), and each browser is atargets/<name>.jsonmanifest overlay, so the Firefox, Edge and Safari threads only add a target. A new Browser extension workflow tests, builds and zips each target as a run artifact, and the Release workflow now also starts it so the zips get attached to releases.Motivation and Context
Adeel asked for a web clipper on every major browser; this thread owns the shared core and Chrome.
Steps to reproduce (if appropriate):
cd extensions/browser && npm ci && npm test && npm run build, then use Load unpacked ondist/chrome. In the options, add your Lens address and an import webhook token.Checked end to end in headless Chromium with the built extension against a mock hook: the page clip, the popup send with its "Open in Lens" link, the picker, and the options Check.
Types of changes
Checklist:
docs/accordingly. (docs/web-clipper.md)🤖 Generated with Claude Code
https://claude.ai/code/session_018uA6PhZXrmpgsbfDh2W23u
Generated by Claude Code