TabNest / Support
If the TabNest workspace is not rendering correctly, start by checking new-tab override permission, bookmark access, and whether local extension storage is being blocked.
Make sure TabNest is installed correctly and allowed to replace the browser's default new-tab page.
Some browser setups or extension conflicts can compete for the same new-tab surface, so disable conflicting extensions first if needed.
If tabs, bookmarks, or bundles appear empty, first check whether the browser granted the required permissions.
If you just changed workspace structure and do not see it reflected, refresh the new-tab page or reopen the browser window so local state can reload cleanly.
Session restore depends on locally stored data, so clearing extension storage, private mode, or enterprise restrictions may affect recovery.
If you need help, the best feedback report includes the current extension version, browser version, and repeatable steps on the Chrome Web Store page.
