BREAKER DELTA
Breaker Delta
OverviewGetting StartedReading the SiteCLI ReferenceConfigurationSkill & MCPExtensionDeploy Your Own
Chrome Extension: Echo Catcher

The extension is the radar in your pocket: spot something that might take off while browsing and capture it in one click; open a page the radar already tracks and it tells you the wave height on the spot. Its full standalone guide lives in the engine repo at apps/extension/README.md; this page is the in-site quick reference.

What it does

  • πŸŒ€ One-click echo capture: on any page, click the toolbar icon to save the title, URL, your selected text and a one-line note into a local echo inbox.
  • βœ“ Tracked status: the top of the popup shows whether the current page is already tracked; if it is, you see the topic, its heat, its first-seen date and a link to its topic page.
  • 🌊 Heat badge: on GitHub / Hacker News / Reddit / X / Product Hunt, a page matching a tracked topic gets a badge card in the bottom-right corner (topic, heat, first-seen date, topic link); breaking topics carry a ⚑.
  • ⚑ Alert count: the orange number on the toolbar icon is how many topics are currently breaking out. No number means no breaking topics β€” that is normal.
  • πŸš€ One-click submit: the ζŠ•ζ³’ button on an echo opens a new-issue page in the target data repo with title, body and label already filled in β€” you only click Submit on GitHub. No token needed, and the extension never submits for you.
  • πŸ“€ Export: copy the whole inbox as GitHub Issue text, or download it as JSON.

Install (unpacked, developer mode)

  1. Get the extension folder: fastest is a ready-made sideload copy; or build it yourself from the engine repo root with bun run --filter @breaker-delta/extension build β€” output lands in apps/extension/dist/.
  2. Open chrome://extensions/ and turn on Developer mode (top right).
  3. Click "Load unpacked" and select the extension folder.
  4. Pin the extension to the toolbar so capturing takes one click less.

After changing code or data, click the reload (↻) button on the extension's card at chrome://extensions/ β€” closing the popup does not update anything.

Settings

Open via βš™ in the popup footer or the extension's Options page: data repo (owner/repo receiving submissions, default daiyanze/breaker-delta-data; a full github.com URL also works), instance site URL (where topic links point and where topics/alerts data is fetched from β€” point it at your own instance if you run one), open the submit page right after capturing, and keep the local copy after submitting. Settings live in chrome.storage.local only.

Where the data comes from

Topic and alert data (topics.json / alerts.json) is generated by the site build and published with the site. The extension fetches it live from the configured instance site (on install, on browser startup, and when the popup opens; the Settings page can force a refresh) and caches it locally; the bundled snapshot is only a fallback when the site cannot be reached. Downloads only β€” no backend, no accounts.

Permissions and privacy (why only three)

  • activeTab: temporary access to the current tab only when you click the icon β€” title, URL and selected text. It cannot touch your pages at any other time.
  • scripting: together with activeTab, reads the selected text when you capture.
  • storage: the echo inbox lives in your browser only.
  • No tabs / history / cookies / all-URLs permission; browsing history is never recorded; badge matching happens locally and never leaves the browser; no telemetry, no third-party code.
  • After submitting, an echo is marked "submit page opened" β€” the extension cannot see whether you actually clicked Submit on GitHub. Very long excerpts are truncated so prefilled URLs stay within GitHub's length limit.

Troubleshooting

  • No heat badge: check in order β€” is the page on one of the five supported sites? Is the topic actually tracked? Is the data stale (force a refresh in Settings)? Then reload the page.
  • No badge number on the icon: normal when nothing is breaking out.
  • "Current page cannot be read": protected pages (chrome:// internals, the Web Store) cannot be read β€” a Chrome restriction. Try a normal web page.
  • Selected text not saved: select the text first, then open the popup; the popup shows "N characters selected" when an excerpt will be saved.
  • Settings does not open: reload the extension at chrome://extensions/ and confirm version β‰₯ 0.6.1 β€” that version added a fallback that opens the settings page in a new tab when the official API silently fails.