Diagnostics export

Create one

1. Open it. In the dashboard choose Library tools → Diagnostic export (or find Diagnostic export in the command palette).
2. Read it. The dialog shows the exact text that would be saved. Nothing has been downloaded yet.
3. Download. Choose Download. Your browser saves bookmark-scope-diagnostics.json. Nothing is uploaded anywhere; sending it to anyone is up to you.

What is in it

{
  "format": "bookmark-scope-diagnostics",
  "version": 1,
  "extensionVersion": "5.2.1",
  "createdAt": "2026-10-07T09:30:00.000Z",
  "redaction": "allowlisted-fields-only",
  "events": [
    { "ts": "2026-10-07T09:29:51.120Z", "scope": "dashboard",
      "event": "init_started", "level": "info", "metrics": {} }
  ]
}

• The extension version and the time of export.
• Up to 200 recent events, each with a time, a scope ( background , dashboard , popup , options or app ), an event name from a fixed list, a level, and a few numeric or true/false counters such as count , failed , skipped or total .

What is left out

The filter works on an allowlist: anything it does not recognise is dropped or replaced with other. In particular the file never includes bookmark addresses or titles, bookmark IDs, tag names, free-form error messages, or any nested data.

The dialog repeats this: Includes event types, timestamps and numeric counts. Excludes bookmark URLs, titles, IDs, tags and error text.

Where to send it

Open an issue on the GitHub repository (opens in a new tab) and describe what you did, what you expected and what happened. Mention your browser and version. Read the file once yourself first.