Keeps the same tabs on all your machines. Tab changes are applied in real time on all of your devices.
The extension watches for tab changes and synchronizes them in real time across all of your computers that have it enabled (Chrome on Android does not support extensions yet). Btw you need to enable synchronization in the Chrome settings.
*You can toggle synchronization on/off from the extensions icon.
*The extension works in unison with Chrome "On startup" settings :
**If you choose "Open a new tab" - it will start with a new tab , and sync the tabs from other computers/previous session in the background .
**If you choose "Continue where I left off" or a set of pages it will merge them with the sync tabs
*Windows' and tabs' positions and size can be individual on each device , as the synchronization only takes in account the tabs' URLs.
*It's implied that you want to keep your tabs across sessions . Otherwise (if tabs were removed at sessions' end) when you close the browser on one device - the tabs (therefore windows) on all other devices would close.
*New tabs (chrome://newtab) and developer tools (chrome://developer-tools/*) are unaffected by the extension for fluency .
*On sync (if a change is detected on another machine) the extension just compares two lists - URLs of all local tabs , and URLs that are synced on the last remote tab change. Differences are applied to the local tabs and that's it . That has its limitations , but the biggest advantages are simplicity and speed (along with the aforementioned "feature" (for me at least) that the tabs can be in different windows with different sizes on separate devices) .
*Note that synchronization occurs only when all tabs have completed loading (otherwise it's a real mess for sites with login forms and not only)
*For developers that want to check out the code - yes , it's open source, and you can check it out at GitHub : https://github.com/petko10/real-time-tab-sync . I've tried to document it well, so it can be used by anyone to learn about writing extensions.
Thanks to Chris de Claverie for his contributions!