The tab setup that works best for most developers is one group per task (a ticket, a feature, a bug), plus a few permanent groups for environments and reference docs. Close a task’s tabs when you switch and reopen them when you come back. In LB TAB Layers, ■ closes a group, ▶ reopens it, and every group is saved as a Chrome bookmark folder, so a context switch no longer costs you your context.
A typical afternoon: the issue you are working on, the pull request that will fix it, three pages of API docs, a Stack Overflow answer, the CI run, the staging site, localhost:3000, the logs dashboard — and then someone asks you to review another PR. Developer tabs multiply because every task touches several tools, and every interruption adds another set.
Why developer tabs get out of hand
- Tasks overlap. You are rarely on one thing. A review, a hotfix and the main feature all have their own tabs.
- Context is expensive to rebuild. Finding that one docs page and that one comment again takes longer than reading them did.
- So nothing gets closed. The tab bar becomes the to-do list, and Chrome becomes the heaviest thing on the machine next to your IDE and containers.
A structure that works: tasks and permanent groups
| Group | What goes in it | Lifetime |
|---|---|---|
| One per task (e.g. “#482 login timeout”) | The issue, the PR, the docs and answers you needed for it | Until it ships, then archive or delete |
| Environments | Local, staging and production URLs, admin panels | Permanent |
| Monitoring | CI, logs, error tracking, dashboards | Permanent |
| Reference | Language and framework docs, style guides, internal wiki pages | Permanent |
| Reviews | PRs waiting for your review | Emptied often |
Name task groups after the ticket number so search finds them. Inside a large group, add section dividers (Add section divider in the group’s … menu) to separate “Spec”, “Code” and “Testing”.
Chrome habits worth having
- Ctrl-click or middle-click links from an issue or search results to open them in the background, then read them in order.
- Ctrl+1 to Ctrl+8 jump to a tab by position; Ctrl+9 goes to the last tab. Pin your local app so it is always tab 1.
- Chrome profiles keep work and personal accounts apart — useful when you have several GitHub or cloud accounts.
- Shift+Esc opens Chrome’s Task Manager, handy when a dev build or a dashboard is eating memory.
Switching tasks without losing your place
LB TAB Layers sits in Chrome’s side panel (Alt+T, Option+T on Mac). The workflow for an interruption looks like this:
- Save what you have open. Every tab not yet in a group is listed under Solo Tabs. Click Group all into a new group and name it after the ticket. Or drag individual tabs into an existing task group.
- Close the task with ■. The tabs close and free memory for your build; the group stays saved as a Chrome bookmark folder.
- Do the other thing. Press ▶ on “Reviews” or on the hotfix group.
- Come back with ▶. The original task’s tabs reopen — the issue, the PR, the exact docs pages.
Because ▶ only opens tabs that aren’t already open, you won’t end up with three copies of the staging site. To give a task its own window, use Open in new window from the group’s … menu.
Features that suit developer work
| Feature | How developers use it |
|---|---|
| Ctrl+Shift+S (⌘+Shift+S) | Drop the current page into 📥 Sort later without touching the mouse — an answer you will need, a doc you want to read properly |
| Right-click → Save to TAB Layers | Save a page or a link from an issue straight into the task’s group, without opening it |
| Notes on saved tabs | “Repro steps are in comment 14”, “Use the v2 endpoint” — see notes |
| Copy as Markdown | Copy a group as a Markdown list of links (with notes) for a PR description, a ticket or a stand-up |
| Create split (pair) | Save two pages as a pair that opens side by side in two windows — docs and the app, or staging and production |
| Typo-tolerant search | Find a saved page by title, URL or note, even with a typo — see search |
| Focus timer | Blocks distracting sites such as social media for 25 minutes while you concentrate |
| Auto Group by Domain | Sort a messy window of Solo Tabs into one group per site in one click |
Copy as Markdown produces a heading with the group name and one line per tab, which pastes cleanly into most issue trackers and chat tools.
Things developers ask about
- localhost and internal URLs. Any tab can be saved into a group from the side panel. The page right-click menu and Ctrl+Shift+S work on normal
httpandhttpspages, which includeshttp://localhost; they don’t work onchrome://pages. - Shortcut clashes. If a browser-based IDE or tool already uses Ctrl+Shift+S or Alt+T, change LB TAB Layers’ keys at
chrome://extensions/shortcuts. - Where the data goes. Groups are plain Chrome bookmarks in a folder named “LB TAB Layers”, so they sync with Chrome, can be exported from the bookmark manager, and stay if you remove the extension. No account is needed.
- Finished tasks. When a ticket ships, right-click its group and choose Archive to keep it out of the way without deleting it, or delete it if you won’t need it again (deleting a group also deletes its bookmark folder).
A daily rhythm
- Morning: ▶ on “Monitoring” to check CI and errors, then ■.
- Work: ▶ on today’s task group. New tabs you open for it go into the group as you find them useful.
- Interruptions: ■ on the task, ▶ on the other group, then back.
- End of day: anything left in Solo Tabs either goes into a group or gets closed with Close all tabs except active.
ℹ️ The free version allows up to 5 groups (subgroups count toward that). Developers with many tasks usually want more — every feature, with no group limit, is unlocked during the 3-month free trial, and PRO is a one-time purchase.
Frequently asked questions
Q. How should developers organize browser tabs?
Use one group per task, named after the ticket, plus a few permanent groups for environments, monitoring and reference docs. Close a task’s group when you switch and reopen it when you return.
Q. Can I save localhost pages in LB TAB Layers?
Yes. Any open tab can be saved to a group from the side panel. The page right-click menu and the Ctrl+Shift+S shortcut work on http and https pages, including http://localhost, but not on chrome:// pages.
Q. How do I share a set of links in a pull request?
Use Copy as Markdown on the group. It copies a heading with the group name and a Markdown link for each tab, including any notes, ready to paste.
Q. Will closing a group lose my tabs?
No. ■ closes the tabs but every saved tab stays as a Chrome bookmark. Press ▶ on the group to open them again.
▶ See it in action
Managing bookmarks and tabs together in the sidebar. (The video shows the Japanese UI.)
Switch tasks. Keep your context.
A group per ticket, saved as Chrome bookmarks. Try every feature free for 3 months.
Add to Chrome — it's free →