Hi there,

Thank you for reporting this issue!

After reading your review, I tested several cross-machine import scenarios. I found that under certain specific conditions, the extension's strict domain-matching logic was incorrectly flagging and skipping valid cookies on the new device.

I've just released a new update that fixes this behavior, ensuring your JSON payloads are processed and applied correctly.

Could you please update to the latest version and give it another try? *(Quick tip: Make sure you are on the correct target website or have the "All Domains" toggle enabled when pasting your JSON).* Let me know if this resolves the issue for you! Your feedback is highly appreciated.

Best regards,

Neeno

Hi,

Thank you for the detailed review! I had to use Google Translate to read it, but I really appreciate the thoughtful feedback.

I am very glad to hear the extension helped you smoothly transfer your session data from Firefox to Waterfox. I also appreciate you taking the time to check the source code to verify that it is fully local, unobfuscated, and safe to use.

Your advice about adding a GitHub repository link is spot on. I am actually in the process of setting up a public GitHub repository for this extension right now, and I will be adding the link to the Add-on page very soon.

Thanks again for using the extension and for the great suggestion!

Best regards,

Neeno

Hi there,

Thank you for reporting the issue, and I’m glad to hear that you found the extension useful overall! I’ve just released a fix for the bug you mentioned.

The problem was caused by the way the extension handled cookies for domains with compound top-level domains (TLDs) like .co.uk, .co.jp, .gov.br, etc. Previously, when creating snapshots or exporting cookies, it was mistakenly including all cookies for domains sharing that TLD (e.g., exporting cookies for `telegraph.co.uk` would also capture cookies for `google.co.uk`).

This issue has now been resolved. The extension has been updated with an improved public suffix heuristic that correctly identifies the root domain, ensuring that only the cookies for the current site (e.g., `telegraph.co.uk`) are captured.

Could you please update to the latest version of the extension and try again? Let me know if the fix works for you, or if you encounter any further issues. Your feedback is highly appreciated!

-----------
Edit - 2026/01/30:

"Hey! Thanks so much for the feedback and for catching that specific edge case with 'westerntelegraph'. You were exactly right—the previous version was using a 'contains' check which was a bit too aggressive.

I've pushed a fix in version 2.0.3 that switches to Strict Domain Matching. It now checks the domain hierarchy specifically, so it will correctly include subdomains like .clerk.telegraph.co.uk but will properly exclude unrelated sites that just happen to share a suffix like .westerntelegraph.co.uk. Thanks again for helping refine this!"

Best regards,
Neeno

Thank you for the great suggestion! We are happy to announce that "Dark Mode" is now fully implemented in version 1.7.0, allowing the extension to seamlessly match your browser theme.

New Features & Improvements:
- This update brings more than just a new look. We have completely overhauled the core experience with major improvements to reliability and control, including:

• Smart Staging:
   A new "Review Import" screen lets you preview data and filter duplicates before applying changes.

• Conflict Control:
   You can now decide exactly how to handle existing cookies by choosing to Overwrite, Skip, or Rename them.

• Workflow Enhancements:
   We added an "Auto-Reload" option and a real-time "Activity Log" to help you track imports and debug issues instantly.

Thanks for your review and suggestion

Support for "All Domains" was added in v1.6, kindly update your extension

    • Support for "All Domains" alongside "Current Domain"
    • Accepts mixed cookies from different domains (when "All Domains" is checked)