TabSloth 🦥 - Let Your Tabs Take a Nap

Sanjeevi Kumar V — Wed, 21 Oct 2026 17:19:02 +0000

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady

TabSloth 🦥 — Let Your Tabs Take a Nap

What I Built

I built TabSloth, a local-first AI browser companion that helps people escape the endless cycle of opening tabs, forgetting why they opened them, and promising themselves they'll organize everything later.

We've all been there.

You're researching a project. One article leads to another, a tutorial opens three documentation pages, and suddenly your browser looks like a digital junk drawer. Closing everything feels risky because somewhere in that mess is the thing you actually needed.

So you leave everything open.

For days.

TabSloth gives those tabs a better future.

With one click, it can:

Understand the chaos: Analyze open tab titles and page content to identify what each tab is about.
Group by intention: Organize related tabs into projects such as "Learn LangGraph," "Plan a Trip," or "Fix That Bug."
Create memory capsules: Generate a concise summary, preserve the relevant links, and identify the next logical action.
Hibernate the clutter: Let you close tabs once their useful context has been saved.
Resume without the archaeology: Reopen a project later and pick up where you left off.

Instead of asking users to become better at organizing, TabSloth makes organization something they barely have to think about.

The goal isn't to browse more efficiently. It's to spend less energy managing the act of browsing.

Demo

Live demo: [Will be added soon]

The ideal demo starts with a browser full of unrelated tabs, turns them into three or four project cards, hibernates the clutter, and restores one project with its summary and links intact.

Code

The project is designed around a browser extension, a local AI inference layer, and a lightweight interface for managing saved browsing sessions.

How I Built It

TabSloth is built around a simple principle: the AI should do the thinking, but the user's browser should retain control.

1. Browser extension

A browser extension collects tab metadata, including titles and URLs. With explicit user permission, it can also extract relevant page text.

The extension provides controls for analyzing tabs, reviewing suggested groups, saving sessions, and restoring them later.

2. Local open-weight AI

The core intelligence uses an open-weight instruction model, such as Qwen2.5-0.5B-Instruct, through a compatible local inference runtime.

The model receives normalized tab information and produces structured JSON describing:

Suggested project groups
A short description for each group
Important links
A concise session summary
A suggested next action

A lightweight validation layer checks the output before it is displayed or saved.

The model is replaceable, so developers can experiment with other compatible open-weight models without redesigning the application.

3. Local-first storage

Saved sessions and their metadata are stored locally in the browser. The AI workflow is designed to avoid sending browsing history or page content to a remote inference API.

After the model and required assets have been downloaded, the application can be designed to operate offline, subject to browser and runtime support.

4. Human-controlled automation

TabSloth proposes groups and actions, but the user remains in control of closing tabs and restoring sessions. Nothing should silently discard a user's work.

The result is a small, practical AI workflow rather than another assistant that requires constant attention.

Why Does Open Innovation Matter?

Browsing history can reveal far more about someone than they realize: work projects, personal interests, financial research, private correspondence, and unfinished ideas.

Sending all that context to a hosted AI service just to organize browser tabs is an unnecessary trade-off for this use case.

Open-source AI makes a different approach possible.

Privacy by design: Page content can remain on the user's device instead of being sent to a third-party inference API.

Offline capability: Once the required model assets are available locally, the core workflow can continue without a live AI service.

Freedom to experiment: Developers can compare models, adjust prompts, change grouping strategies, and optimize inference for different hardware.

Lower recurring costs: Local inference avoids per-request API charges, although it still consumes device resources and requires an initial model download.

Community-driven improvements: Contributors can improve tab extraction, grouping quality, model compatibility, accessibility, and browser support without depending on a single AI vendor.

A closed API might make the first prototype easier to deploy, but it would introduce a remote dependency for a task that benefits from local processing.

For TabSloth, open innovation isn't just about choosing a different model. It's about deciding that the user's browsing context should remain theirs.

The Lazy Payoff

Imagine finishing a research session with 30 open tabs.

Without TabSloth, you might spend ten minutes revisiting pages, renaming bookmarks, writing notes, and deciding what can safely be closed.

With TabSloth, the intended workflow is:

Click Organize My Chaos.
Review the AI-generated project groups.
Save the sessions and close the tabs you no longer need.
Return later and click Resume.

The target is to turn several minutes of repetitive tab management into a quick review.

I'll measure the actual time saved during testing rather than claim an unverified number. Useful metrics include grouping accuracy, summary usefulness, time required to organize a session, and the percentage of sessions users can successfully resume.

Because sometimes productivity doesn't mean doing more.

Sometimes it means finally closing those 37 tabs and going outside.

TabSloth: Your tabs work overtime. Let them rest. 🦥

DEV Community: Sanjeevi Kumar V