The suite froze at the moment of submission and still said "in review" a week
after the listing went public. Since docs win over code here, a stale spec is a
false spec — and one of its "still open" items (the store URL for the README)
had already been closed by ea246aa.
- docs/00: status is published with the listing URL; the store item id and
listing URL join the §9 canonical identifiers table, because the id is also
the CHROME_EXTENSION_ID secret v1.1 automation needs; §8's approval criterion
marked achieved; §10 item 5 resolved and item 6 rewritten — DISCORD_CI_WEBHOOK
is not optional in practice, since notify-ci-failure.yml fails on every CI
completion without it. Two new post-launch items: the JA native review pass
(now shipping to users) and the never-performed post-approval smoke test.
- docs/15: the progress table gains a published row and a Phase 6 row; v1.0.x
stops being speculative and becomes the live workstream, with the intake path
spelled out end to end and a release trigger. Decision log: the Changelog-link
row is marked resolved, the two-tab known limitation superseded, and twelve
rows added for the Phase 6 design — recorded before the code, as the project's
own docs-first rule requires.
- docs/06 §3.5: the Changelog link points at CHANGELOG.md (it has since Phase 5)
and About gains a store listing entry. Also states why no support email
appears in the UI: an in-product address invites unsanitized bookmark files.
- CLAUDE.md: leads with the fact that this is shipped software, and what that
changes. Records EditTab.svelte back at 481 lines rather than the 459 it
claimed, adds a Phase 6 section, and adds the worktree bootstrap gotcha.
Also adds `verify:full`, because hard rule 8 now points at it. `verify` omits
coverage, build and check:manifest, all of which a tag run enforces — so a core
change can pass every documented local step and fail only after the tag is
pushed, when gh release create has already run and cannot be re-run.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
BookmarkMagic
Move your bookmarks between browsers the simple way: with a file. No account, no cloud sync, 100% offline.
A Chrome (MV3) extension for importing, exporting and editing bookmarks and folder trees. English · Tiếng Việt · 日本語.
Screenshots
| Edit | Export |
|---|---|
![]() |
![]() |
| Settings | About |
|---|---|
![]() |
![]() |
What it does
- Import HTML, JSON or CSV bookmark files, with a full preview first — counts, folders, depth, duplicates and warnings before anything is written.
- Choose how: into a new dated folder (the safe default), merged into your existing folders, or replacing everything. Replace saves a JSON safety backup first and deletes nothing until that backup is proven.
- Export everything, or just the folders you pick, to HTML (Chrome, Edge, Brave, Firefox, Safari, Vivaldi, Opera), JSON, CSV or Markdown.
- Edit the tree: search, rename, drag & drop, create folders, delete, and find duplicate links — every action reachable from the keyboard.
Privacy
This is the whole point of the project, so it is worth being precise.
- No network access at all. Not analytics, not telemetry, not update pings.
There is no server. A grep gate (
npm run guard) fails the build if anyone addsfetch,XMLHttpRequest,WebSocket,EventSourceorsendBeacon. - Exactly two permissions:
bookmarksandstorage. No host permissions, no content scripts, no background worker. Two gates enforce it: a unit test overwxt.config.ts, andnpm run check:manifest, which CI runs against the builtmanifest.json— because a build can add what the config never asked for. - Zero runtime dependencies. Nothing third-party ships in the extension.
- Settings use
chrome.storage.local, neverstorage.sync, so even your preferences stay off any vendor cloud.
Full policy: legal/PRIVACY.md.
Honest limitations
- Favicons cannot be imported — the bookmarks API has no favicon field.
- Imported bookmarks get today's date. Chrome does not let an extension set a bookmark's original creation date. Your exported files keep the real ones.
- CSV is a flattened view: empty folders and "which folder is the toolbar" are not preserved. Use HTML or JSON for a faithful backup.
- Markdown is share-only — BookmarkMagic cannot read it back.
Install
From the Chrome Web Store: here
From source:
npm ci && npm run build
Then load .output/chrome-mv3/ at chrome://extensions with Developer mode on.
Development
npm run dev
npm run verify is the gate everything else answers to — lint, type-check,
knip, the grep gate and the test suite, in that order. It must be green before
every commit.
The docs/ directory is the binding specification, not notes: where
code and docs disagree, the docs win. Start with CLAUDE.md, then
docs/00–docs/02.
Contributing
Bug reports and translation fixes are welcome via issues. A bug report about parsing is far more useful with a sanitized sample of the file that broke.
Security issues: please follow SECURITY.md rather than opening
a public issue.
Support development
Entirely optional — BookmarkMagic is free software either way.
GitHub Sponsors · Ko-fi · Buy Me a Coffee · Patreon · PayPal
Licence
GPL-3.0-or-later. Also see legal/EULA.md,
legal/DISCLAIMER.md and
legal/THIRD_PARTY_NOTICES.md.
Not affiliated with or endorsed by Google, Chrome, or any browser vendor. Browser names are trademarks of their respective owners.



