For developers
A tab manager built for
how developers work.
Local servers, pull requests, docs, the issue you’re fixing and the answer that explained it. TabHabit sorts them into groups as you open them, so switching between tasks is one click.
Free · Chrome and Firefox · No account · No AI
Every local server in one place
Turn on the Dev habit and every tab on localhost, 127.0.0.1 or a .test site lands in a Dev group, whatever the port. Restart your dev server on a new port and the tabs still go to the same place.
A workspace per repo
Write one rule like github.com/your-org/{repo} and each repository gets a workspace of its own, named after it. Or right-click any tab and choose “Always put this site in…”.
A tree of how you got there
TabHabit remembers which tab opened which, so a trail through docs, issues and threads stays together as a branch you can fold, move or close in one go.
It never moves your tabs behind your back
A tab you’re working in doesn’t jump to another group when you browse somewhere else, and tabs you place by hand stay put.
Hand your context to your tools
Select tabs and copy them as Markdown that keeps the tree, or as context for an AI assistant: titles, addresses, the tree and your note. Nothing is sent anywhere by TabHabit itself.
Find anything
⌘K searches every window, folded branch, parked workspace and closed tab. Close freely: the tab you need tomorrow is one search away.
Questions
Does it handle localhost on any port?
Yes. The Dev habit matches localhost, 127.0.0.1, 0.0.0.0 and .localhost or .test sites with or without a port.
Can I group tabs by repository?
Yes. A rule with a {key} in it, like github.com/your-org/{repo}, makes one group per repository, named after it.
Does TabHabit send my URLs anywhere?
No. Your tabs, tree, rules and backups stay in your browser. There’s no account and no analytics. The only thing that ever leaves is optional Pro sync, encrypted on your device.