Branchy

Branchy shows your tabs as a tree in the browser's side panel, the way an IDE shows files. • A tab hangs under the tab that opened it. Close a tab and the tabs under it move up a level. • Tickets gather their pages. Tabs that carry a tracker key such as PROJ-123 (the issue, its merge requests, pipelines and builds) hang under the ticket, wherever they were opened from. Tickets opened from tickets nest: initiative → epic → task → merge request reads as one branch. • Folders nest, with names and colors. Top-level folders are mirrored as the browser's tab groups (islands in Opera), so the tab strip shows the same grouping. A ticket on the top level gets a folder of its own once it has a second tab. • Statuses at a glance, if you want them: connect a Jira, GitLab or Jenkins site in Settings, and each row shows where its work stands: a ticket's status, what keeps a merge request from merging, a pipeline's progress, a failed job, a build's time left. They are read with your own sign-in in the browser; no tokens. • Drag and drop, multi-select, menus on right click: move, close, reload or unload a whole branch, or copy its links as Markdown. • Search by title, ticket, page kind or status; each result shows where its tab sits in the tree. • A link opened from another app goes to the tab that already shows that page, instead of opening a copy. • The tree survives browser restarts. • Light and dark themes, text size, and a picture of yours behind the tree, with the accent taken from it. • Backup: export the tree to a file, and import it in another browser or profile. Privacy: everything stays in your browser. Branchy has no server, collects no analytics and sends nothing to anyone. Statuses are read only from the sites you connect. Privacy policy: https://github.com/ReQur/TabTree/blob/main/PRIVACY.md Works in Chrome, Edge and Opera. Open source (MIT): https://github.com/ReQur/TabTree