HuskDesk：告別分頁混亂，保留工作脈絡｜Hacktoberfest 2026 第 3 週開發挑戰

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

HuskDesk — Close the Tabs. Keep the Context.

Your browser remembers the pages. But does it remember what you were doing?

We've all been there.

Twenty tabs open. Three unfinished projects. A documentation page you swear you'll read later. An important task buried somewhere between GitHub, Stack Overflow, and a dozen other tabs.

You close your browser to get a fresh start—and suddenly, getting back into your workflow feels like starting from scratch.

I wanted to solve that problem.

Meet HuskDesk: a local-first Chrome extension designed to help you organize your browser workspace, preserve your progress, and return to unfinished work without losing context.

The idea is simple: let your browser handle the clutter, so you can focus on the work that actually matters.

What I Built

HuskDesk is a productivity-focused Chrome extension built around one principle:

Your workflow shouldn't disappear just because you close your tabs.

Here's what it can do:

• 📂 Workspaces: Save collections of open tabs as named workspaces and restore them when you're ready to continue.
• 🌙 Tab Hibernation: Save and verify tab information before closing tabs to free up your workspace.
• 🧠 Resume Memory: Keep notes about what you were working on, what matters, and what you need to do next.
• 🗂️ Tab Organizer: Group tabs using domain-based organization, with experimental local AI-assisted grouping.
• 🔄 Pick Up Where You Left Off: Reopen saved workspaces and individual tabs without having to reconstruct your workflow manually.
• 🎨 A Focused Interface: Manage your browser work through a clean dashboard with light and dark themes.

HuskDesk isn't trying to make you work faster every second. It's trying to remove the little interruptions and repetitive tasks that make focused work harder.

Demo

GitHub Repository: github.com/hey-anshuman/HuskDesk

Huskdesk is currently distributed as an open-source project. You can explore the code, follow the setup instructions in the README, and build the extension locally.

Code

The repository includes the extension source code and project documentation covering the architecture, design decisions, implementation status, security considerations, and test plan.

Built with a modern web stack, HuskDesk uses React, TypeScript, and Vite for its extension interface and Chrome's extension APIs for browser workspace management.

Contributions, feedback, and ideas for making everyday browser workflows less frustrating are welcome.

How I Built It

HuskDesk is built with React, TypeScript, Vite, and Chrome Extension Manifest V3.

The interesting part of this project is its approach to AI.

Instead of making a paid cloud AI API a requirement, I integrated Gemma 3 1B through Ollama, allowing the experimental AI grouping feature to run using a model on the user's own machine.

The architecture combines two approaches:

1. Reliable productivity features

Workspace capture and restoration, tab hibernation, and Resume Memory provide the core experience. These features don't require an AI account.

2. Optional local AI assistance

The experimental AI grouping workflow sends requests to a locally running Ollama service. The model can suggest how tabs should be grouped, while domain-based organization provides a fallback when AI grouping isn't available or produces unsuitable results.

This separation matters. The extension's fundamental purpose remains useful without requiring users to configure an AI model.

Local AI grouping is still experimental, and it requires users to install and run Ollama separately. It isn't a fully autonomous agent, and the quality of its suggestions can vary.

Why Does Open Innovation Matter?

For a productivity tool that works with someone's browser activity, the choice of AI architecture matters.

I wanted local AI to be an option, not another subscription.

Using an open-weight model with local inference offers several advantages:

• More control: Users can run inference on their own machine instead of depending on a hosted AI API.
• Privacy by design: The AI grouping request can stay on the local machine rather than sending tab information to a remote AI provider.
• No mandatory paid AI API: Users don't need to purchase cloud model credits just to try the AI feature.
• Room to experiment: Developers can inspect the integration, test different models, and improve the workflow without tying the project to one proprietary AI service.

Open innovation also makes the project easier for other developers to learn from, inspect, and extend.

Of course, local inference isn't automatically a guarantee that every part of an application is offline or that all stored data is encrypted. HuskDesk still needs to be transparent about its permissions, local storage, and optional AI setup.

For me, open-source software and open-weight AI aren't just technology choices. They're ways to give users more control over the tools they rely on every day.

The Lazy Payoff 🦥

The best productivity tool isn't necessarily the one that does the most things.

Sometimes, it's the one that saves you from doing the same small things over and over again.

With HuskDesk, the intended payoff is straightforward:

• Spend less time reopening tabs and reconstructing a workspace.
• Keep important context in Resume Memory instead of relying on memory alone.
• Reduce tab clutter without losing the information needed to continue.
• Experiment with local AI-assisted organization without making a paid AI service mandatory.

I haven't measured a reliable time-saving figure yet, so I won't claim that HuskDesk saves a specific number of minutes or hours. That's something I'd like to measure through real-world use and feedback.

The goal is to make returning to work feel less like rebuilding a desk after someone has cleared it—and more like sitting down exactly where you left off.

Close the tabs. Keep the context. Get back to what matters.

Prize Categories

Primary submission: Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady.

HuskDesk uses Gemma 3 1B through Ollama, so the Best Use of Gemma category may also be relevant, provided the implementation meets that category's official rules.

I'll only claim partner categories that HuskDesk genuinely qualifies for under the challenge guidelines.

Built with curiosity, local-first thinking, and a little less tab chaos.

🔗 Project: HuskDesk on GitHub

Feedback and contributions are welcome!