Support

Ninety percent of the time: the tab was already open before you installed (or updated) Pluck. Those tabs need one refresh to pick up the in-page listener — newly opened tabs work immediately. Alternatively, click the toolbar button → it works on open tabs without a refresh. Also note that browsers block all extensions on chrome:// pages and the Chrome Web Store itself (Pluck flashes a red × on its icon there), and check the popup in case you previously recorded a different combo.

Some pages restrict programmatic clipboard access; Pluck automatically falls back to a second copy method, so this is rare. If it happens: click the capture's entry in the popup's Recent list to re-copy it from there. If a particular site blocks copies consistently, please file a bug with the URL.

Because nothing shorter was unique. Pluck verifies every selector against the live DOM — it must match exactly one node — and only adds :nth-of-type() or ancestor segments when the element has no unique identity of its own. Tip: press ↑ before clicking to grab a parent container that has an id or distinctive class — those anchor much shorter selectors.

On rare, highly repetitive pages there's no uniquely addressable path within a sane depth. Pluck tells you instead of pretending: the toast and the history entry carry an amber warning. The copied text still includes the element's text and opening tag, which is usually enough for an AI agent to locate it in source. If you hit this on a normal-looking page, send the URL — the engine's heuristics evolve from exactly these reports.

Open the popup → click the shortcut chip → press your combination (it needs Ctrl, Alt or ⌘ — plain letters won't record, so typing can never trigger it). It updates live in every open tab. Reset shortcut in the popup footer restores the default (⌘⇧E on macOS, Ctrl+Shift+E elsewhere).

Yes — any Chromium browser with Manifest V3. Arc is specifically why Pluck handles its shortcut in-page instead of through the browser's command API: extension commands are unreliable there, an in-page listener isn't. Install the same way: chrome://extensions (or the browser's equivalent) → Developer mode → Load unpacked.