Roadmap

This page tracks status honestly rather than optimistically. Anything listed as planned has no date attached, because Konode is a small independent project and a date would be a guess.

Working today

Four data types, across Chromium and Firefox, onto storage you already own, with optional end-to-end encryption on every backend. Entry by entry:

• Shipped

  Live on both stores

  • Firefox Add-ons1.5.1
  • Chrome Web Store1.5.1
• Shipped1.5.1

  Keep bookmarks out of sync

  Under Bookmarks, in setup and in Settings → Data Types, Exclude bookmarks from sync opens your bookmark tree with a box in front of every folder and bookmark. Whatever you tick stays on this device untouched: it is never uploaded, nothing your other devices do changes it, and changes inside it no longer start a sync. It was asked for by someone whose other extension keeps a big bookmark folder of its own, which froze the browser while Konode synced every entry in it.

  A ticked folder stays excluded when you rename it. Excluding deletes nothing, so copies your other devices already have stay where they are.

• Shipped1.5.1

  Tab groups come back with your tabs

  A synced session now carries which of its tabs share a group, and Restore puts them back together. Allow group names and colors when Konode asks for open tabs, or later in Settings, and those come back too. Chrome, Edge, Brave and the other Chromium browsers have groups, and so does Firefox from version 138. Where a browser has none, a session restores as it did before.

  Restoring a session you have restored before opens only the tabs you do not already have, instead of opening the whole session again.

• Shipped1.5.1

  A deletion that arrives in pieces is held back

  The limit on how much of your bookmarks another device may delete used to judge each sync on its own, so a large deletion that arrived a piece at a time could go through piece by piece. Konode now adds up what other devices removed over the last 24 hours and holds back the piece that takes the total over the limit, with a restore point saved first.

  The limit also counts bookmarks rather than copies of them, so a pile of duplicates no longer makes your tree look bigger than it is.

• Shipped1.5.1

  Manual conflict resolution asks only when bookmarks really differ

  With conflict resolution on Manual, Konode used to ask on the first sync between any two devices, because it compared files rather than the bookmarks in them, and each browser gives a bookmark its own ID and date. It now compares the bookmarks themselves: the folder each one is in, its address and its title. Two devices that hold the same bookmarks are not asked about.

• Shipped1.5.1

  Firefox for Android, listed on Firefox Add-ons

  Konode installs from Firefox Add-ons on Android and syncs open tabs and the extension list there, on GitHub or WebDAV storage. Firefox for Android gives extensions no bookmarks, no history and no Google sign-in, so those are marked unavailable instead of failing the sync, and Google Drive is not offered.

• Shipped1.4.0

  Nutstore (坚果云)

  A storage card for Nutstore: pick it, sign in with your Nutstore email and a third-party app password, and there is nothing else to set up. If you are in mainland China this is the one that matters, because Google Drive cannot be reached from there. In Simplified Chinese, Nutstore is the first card in the list.

  A free Nutstore account allows 600 WebDAV requests every 30 minutes, and the card says so: with three or more devices, a sync interval of 120 seconds or more keeps well clear of it.

• Shipped1.4.0

  Italian, Russian and Traditional Chinese

  Konode now speaks English, Hungarian, German, Spanish, Italian, Russian and Chinese, both Simplified and Traditional. Traditional Chinese is its own translation with the words used in Taiwan, not the Simplified files converted character by character, and a native speaker reviewed it.

• Shipped1.3.2

  A blocked deletion that would not stop

  Konode refuses any one sync that would remove more than 60 percent of your bookmarks, and saves a restore point when it does. What it used to do next was keep that request and publish it again under its own name, so within a few cycles every device was asking every other one to delete bookmarks all of them still had. The warning returned every minute, named a different device each time, and nothing you did on any single device ended it.

  Nothing was ever lost. The guard refused the deletion every time; what it could not do was stop being asked. A device now only ever asks for the deletions it made itself, and ignores that request when a peer makes it, so the warning stops on the first sync after one device updates, even while your others are still on the older build.

• Shipped1.3.1

  See what a held back deletion holds, and allow it

  Settings → Activity shows a card for a deletion Konode stopped: how many bookmarks of how many, which device asked for it, and how much of your tree that is, with a button that applies it. Before this the only route was a slider that stops at 95 percent, so a device asking to clear nearly all of its bookmarks stayed blocked wherever you put it.

  Saying yes covers the sync that follows and nothing after it, so a deletion that turns up later is stopped and shown to you like any other. The restore point is already saved before you are asked.

• Shipped1.3.0

  Interface translation

  English, Hungarian, German, Spanish and Chinese (Simplified), all five complete, on every screen Konode has. It reads through the browser's own chrome.i18n, so there is no library and no bundle cost, and it follows the language your browser is already set to rather than asking you to pick one.

  Spanish and Chinese came from volunteers on Hosted Weblate, where translating needs no git, no pull request and nothing installed. A language reaches a release once it is complete, because a screen that is half translated reads worse than an English one.

• Shipped1.2.0

  Chromium browsers and Firefox

  Chrome, Brave, Helium and ungoogled-chromium, plus Firefox and Waterfox. Verified across Firefox, Brave and Helium sharing one sync folder. History arrives on its original visit dates on Firefox, the only engine that permits it.

• Shipped1.1.0

  Three backends, seven ways in

  Google Drive with the narrow drive.file scope, GitHub with a fine-grained token on a single private repository, and WebDAV against any compliant server. Nextcloud, ownCloud, pCloud, Koofr and Fastmail each get a card of their own. Synology, kDrive and everything else go through the generic WebDAV card.

• Shipped1.1.0

  Bookmark restore points

  Timestamped copies of the bookmark tree on your own storage, the newest ten kept. Saved by hand, or automatically when Konode refuses an unusual mass deletion. A restore only ever adds bookmarks back, never removes any.

• Shipped1.1.0

  Activity, statistics and devices

  One tab in Settings covering what synced and when, alongside the device list and the option to forget a device you no longer use. Since 1.3.0 forgetting reaches your other machines too: each one drops the forgotten device on its next sync, so its tabs stop being offered and its extensions stop counting as missing here.

• Shipped

  Four data types, merged across every device

  Bookmarks with two-way sync, tombstoned deletions, and renames, moves and folder reorders propagating. Open tabs and sessions, de-duplicated history, and the installed-extension list. Every type folds in each peer's file on every sync, so three or more devices converge rather than overwriting one another.

• Shipped

  Optional end-to-end encryption

  Turn it on and your storage provider holds ciphertext it cannot read. The key is derived on your device from a passphrase that never leaves it: AES-256-GCM, with PBKDF2-SHA256 over 600,000 iterations. Every download is checked against a SHA-256 sum before it is applied, on every backend.

• Shipped

  Conflict resolution you choose

  Newest change wins, always prefer this device, always prefer the other, or resolve each conflict yourself. The first three decide without asking and are what most people want. Resolving by hand is the weakest of the four today, and the Planned section says what it is missing.

• Works

  Orion, on the WebKit engine

  Not a supported target, and the reason is no longer that it fails. A field session in August 2026 had Orion and Brave sharing one WebDAV folder with encryption on, and all four data types synced.

  What it also showed is that WebKit breaks assumptions the Chromium code rests on, invisibly to the test suite. Three of those are fixed in 1.3.0:

  • arriving bookmarks split across Orion's two bookmark roots, so a tree landed partly in each
  • a saved session restored as one tab, because WebKit grants a click a single programmatic open and Konode spent it checking whether it was allowed more
  • a first install showed no setup wizard, because the engine never fires the event that opens it. The popup now offers a way in until a provider is chosen

  All three are written and released, and none has been run on an Orion device yet, which is why this card still says Works rather than Shipped. Reports are welcome.

  Google Drive sign-in is the one thing that stays broken: the browser's own OAuth bridge throws instead of opening Google's consent screen, so Drive is switched off there with a plain message. WebDAV is the verified way in, GitHub is reported working there by someone running Orion RC, and Safari itself would need a native app wrapper that Konode does not ship.

Planned

Nothing here has a date. Konode is a small independent project and a date would be a guess.

• In review

  Microsoft Edge Add-ons

  Konode is submitted to Microsoft Edge Add-ons, with the same package as the Chrome Web Store, so the version is the same whichever store you install from. On desktop, Edge already installs Konode from the Chrome Web Store, after asking once to allow extensions from other stores.

  Once it is listed, the next step is checking what works on Edge for Android. Microsoft decides which extensions are offered there, and its own list of extension APIs does not show bookmarks on Android, so we will report what actually works rather than promise it now.

• Next

  A held-back deletion that names what it holds

  When Konode stops a large deletion from another device, the card in Settings → Activity says how many bookmarks it would remove, and never which ones. A number cannot answer the question the card asks, which is whether you meant it. The plan is to list the bookmarks it holds, title and address, with "and so many more" past the first few.

  The four conflict-resolution options get new descriptions at the same time, because none of them says what it does with another device's deletions, and that is where they differ most.

• Next

  A device list that says when each device was last active

  Reinstall Konode, or set it up in a second browser, and it joins as a new device, while the old one stays in the list and in the merge until you forget it. Telling the two apart today means reading timestamps. The plan is "last active 39 days ago" on every row, a clear mark on the devices that are plainly gone, and the browser each one runs in.

  Konode will not merge two devices into one by itself. It cannot tell a reinstall from two browsers running side by side, and treating those two as one would lose data, so the choice stays with you.

• Next

  Conflict resolution that shows you the difference

  Set conflict resolution to Manual and Konode asks which version of your bookmarks to keep, without showing you either one. Both answers act on the whole tree, so the choice is a guess. The plan is a resolve screen in Settings with room to list what actually differs, title and address for bookmarks and history, reached by a button on the popup rather than squeezed into a popup 360 pixels wide.

  The problem underneath it is already fixed: since 1.5.1, Manual asks only when the bookmarks on two devices really differ, so the screen has a smaller and clearer job.

• Planned

  The reading list, on Chromium browsers

  Chrome has a reading list that extensions can read and write, so it can sync the same way bookmarks do. Firefox has no equivalent, so there it will show as unavailable and be skipped, the way bookmarks already are on Firefox for Android.

• Planned

  More backends, cheapest sign-in first

  Token and basic-auth backends come first, because they are the same class of work as WebDAV and GitHub: S3-compatible storage, Backblaze B2 and a Dropbox token. S3 will take your own endpoint from the start, so a self-hosted server works, not only Amazon. OAuth backends follow, Dropbox and OneDrive among them, each needing its own app registration, redirect and refresh handling per browser.

  Gitea and Forgejo have been asked for too. Their API is shaped like GitHub's, so the likely route is letting you set your own server address on the GitHub card rather than writing a new backend.

• Planned

  More languages

  Japanese, Estonian and Arabic are being translated by volunteers on Hosted Weblate, and none of them has a date. Each ships in the first release after it is finished. Arabic is the first right-to-left language, so it brings the page layout work with it. Anyone who reads a language Konode does not speak yet can start it there.

• Planned

  Diffs between restore points

  See what actually changed between two restore points, rather than only that a sync ran. A restore point already holds a full bookmark tree, and the extension already reads one back and decrypts it in order to restore it, so this is a comparison view over data that exists. Bookmarks only, and only across the ten most recent restore points.

• Planned

  Faster history sync

  The full-history dedup scan that runs on every import. Since 1.3.1 it is built once per sync rather than once per device, which was the larger half of the cost as soon as you had more than one other device. What is left is that a sync importing any history at all still reads your whole local history once, to answer whether it already holds a newer visit for a page. An incremental diff for very large bookmark trees, past ten thousand or so, sits in the same bucket.

Not planned

Some things get asked for regularly and are not coming, for reasons worth stating plainly:

• No

  iCloud Drive

  Apple publishes no third-party API for iCloud Drive and no WebDAV, so there is no supported way for an extension to put a file there. What circulates as iCloud over WebDAV is a relay service that copies your files through its own servers, which is the arrangement Konode exists to avoid.

  The sanctioned route, CloudKit, writes into a container the developer registers rather than into your iCloud Drive. You could not open those files in Finder, copy them out, or hand them to another tool. Being able to do exactly that is what "storage you own" means here, so an iCloud card would be the one backend that makes the promise untrue. On Apple hardware, any WebDAV provider works today, and so does a private GitHub repository.

• No

  Safari

  Safari runs only extensions that are packaged inside a Mac app and distributed through the App Store with a paid Apple developer account. That makes it a separate app with its own review and upkeep, not one more build the way Firefox was, so it is not on the roadmap. On the Mac, Orion runs on the same engine as Safari and takes Chrome and Firefox extensions, see its card above.

• No

  MEGA and Filen

  Both were asked for, and neither is planned. MEGA has no plain storage address a browser can write to, so it needs MEGA's own client library and its encryption bundled into the extension. It is parked, and the design notes stay in the repository for anyone who wants to pick it up.

  Filen is blocked on a license before any engineering. Its official SDK is AGPL-3.0 and Konode is MPL-2.0, and shipping the two together is a legal question that has to be answered first. If you already run Filen's command line tool, it can serve your drive over WebDAV from your own machine, and the generic WebDAV card takes a local address. Nobody has reported trying that.

• No

  Cookie sync

  Cookies are your logged-in sessions. Copying them to storage would put every account at risk the moment any device or the storage itself was compromised, and reading them would need access to every site you visit. Konode will not do it.

• No

  Password sync

  Browser extensions cannot read the browser's native password store. That is a security boundary the browser enforces, so this is not something Konode can choose to add. Use a dedicated password manager.

• No

  A hosted Konode backend

  Running a server would undo the entire point. Your data goes to storage you already control, which is only true as long as there is nothing in the middle.

• No

  Analytics or telemetry

  Not now and not later, including the anonymous, aggregated kind. Bug reports through GitHub issues are how Konode finds out what is broken.