Skip to content

Browser extension for one-click bookmarking from Chrome and Firefox #417

@oxr463

Description

@oxr463

Is your feature request related to a problem? Please describe.

Saving a page to FindFirst requires navigating away from the current tab, opening the web app, and manually entering the URL and tags. This breaks the browsing flow; by the time a user switches apps to save something, they've already lost context. There's no way to capture a page in the moment without interrupting what they're doing.

Describe the solution you'd like

A browser extension (Chrome and Firefox, Manifest V3) that lets users save the current page to FindFirst in one click, without leaving the tab.

The extension should include:

  • Popup UI - save the current tab's URL and title with optional tags; tag autocomplete from the user's existing tags; create new tags inline
  • Context menu - right-click any page or link to save it directly
  • Options page - configure the FindFirst server URL and view connection status (supports self-hosted instances)
  • Auth flow - sign in to FindFirst from within the extension; session persists across browser restarts via extension storage

All API calls (bookmark save, tag fetch, auth) route through a background service worker so that auth state and cookie handling work correctly across Chrome and Firefox.

Describe alternatives you've considered

  • Browser bookmarks + manual import - no real-time sync, requires extra tooling, loses tag metadata
  • Bookmarklet - no persistent UI, awkward on mobile, requires JS execution on the page, can't handle CORS cleanly
  • Mobile share sheet - addresses phone use cases but not desktop, and doesn't replace the extension for desktop users

Additional context

  • Single shared src/ TypeScript codebase; esbuild produces separate dist/chrome/ and dist/firefox/ artifacts
  • No runtime framework (plain HTML/CSS/TS) to keep bundle size minimal
  • Works against any self-hosted FindFirst instance via configurable base URL
  • Note: The FindFirst API server will need CORS headers allowing requests from chrome-extension:// and moz-extension:// origins (Access-Control-Allow-Origin + Access-Control-Allow-Credentials: true) before end-to-end testing is possible

Metadata

Metadata

Assignees

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions