Experimental web browser optimized for rabbit-holing

An experimental web browser prototype reimagines tab management as a horizontal, branching history of pages, making it easier to follow and revisit “rabbit holes” during research or casual exploration. Commenters compare it to tools like Tree Style Tabs, Nyxt, Skipper, and various note-taking and sensemaking systems, highlighting use cases from academic literature dives to ADHD-friendly workflows. While many want this as a mainstream browser feature or extension—including on mobile—others warn that without guardrails it could amplify tab overload, underscoring a broader desire for better history, session, and context management in browsers and desktops.

Overall reception

  • Many commenters find the rabbit-hole–optimized browser concept compelling, especially for research and exploratory reading.
  • Several say they independently envisioned similar systems, or built prototypes, and feel this validates the idea.
  • Some see it as one of the more Memex-like realizations of web browsing, especially with preserved trails and potential for annotations.

Comparisons to existing tools

  • Frequent comparisons to:
    • Firefox extensions: Tree Style Tabs, Tree Tabs, Sideberry, FoxyTab.
    • Alternative browsers: Arc, Orion, Nyxt, horse browser, OPML-era browsers.
    • Session/tab tools: Skipper, OneTab, Chrome tab groups and Journeys, BrowserBox/CloudTabs.
  • Opinions differ on novelty:
    • Some say it resembles tree-style tabs or PaperWM-like tiling.
    • Others argue it’s more about history trails and parallel panes than simple tab trees.
  • Nyxt’s global history tree and various research projects (SenseMap/HistoryMap, WikiDive) are noted as close relatives.

Use cases and workflows

  • Strong interest for:
    • Deep research (ArXiv, scientific literature, Wikipedia dives).
    • Knowledge management and sensemaking, akin to mind maps, Zettelkasten, or org-mode / Logseq workflows.
    • Code browsing and IDE search, where sideways/parallel navigation could reduce window/tab clutter.
    • Task-specific workspaces and multi-window “contexts” across OS desktops.
  • Some want similar mechanics for Slack threads, mobile browsers, and LLM/chat “notebook-like” sessions.

Concerns, skepticism, and ADHD perspectives

  • Multiple self-identified ADHD users worry it could exacerbate tab hoarding (hundreds to thousands of tabs).
  • Some prefer linear history; branching histories and complex UI are described as cognitively harder.
  • Others argue that persistent, searchable trails plus tagging could reduce fear of closing tabs and turn “rabbit-holing” into a research advantage.
  • A separate camp prioritizes “plate clearing” and aggressive tab pruning or “tab bankruptcy” over richer history structures.

Implementation and limitations

  • Several users report difficulty building/running the project (tooling errors, Electron-related confusion).
  • Some question why this isn’t a browser extension instead of a standalone browser.
  • The project is noted as older (2021) and apparently not actively maintained; interest remains high, but production readiness is unclear.