🚨 We fixed the worst part of browsing — switching tabs.

SiteQuest — Mon, 29 Jun 2026 18:37:05 +0000

SiteQuest is now LIVE (Beta)

Most people don't struggle with using the internet—they struggle with context switching.

Think about your current workflow: You’re reading documentation, you need to prompt ChatGPT or check a reference, so you open a new tab. By the time you switch back, you’ve lost your place and your momentum.

Browsers were built for viewing static pages. But modern work is an unpredictable loop of reading, thinking, referencing, and building. Current browsers make that loop painful.

So, we built an overlay browser that sits on top of your existing workspace.

🎥 See it in action

⚡ Core Features

SiteQuest is a lightweight desktop overlay (macOS & Windows) that toggles instantly with a keyboard shortcut. It doesn't replace your current browser—it just brings the web to wherever you are working.

Overlay Engine: Runs any website or web app seamlessly over any active window.
Custom Shortcuts: Summon or hide your pages instantly with customizable global keybinds.
Pinned Quests: Lock critical sites or tools in place for always-on access while you code or write.
Local AI Privacy: Chat with pages, rewrite text, or translate directly using local AI models.
Built-in Adblocker: Automatically strips out ads, pop-ups, and tracking scripts to keep you focused.
Cross-Device Sync: Your custom layouts and saved sites automatically sync across multiple devices.

🧪 Join the Beta

"Your second browser should not be another browser window."

This is an early beta. It’s a completely different way to interact with the web, and we're actively refining it based on how people use it and it offers a feature-rich free version too. If you hate switching tabs as much as we do, we'd love your feedback.

Try it here: https://sitequest.qzz.io/?src=launch

Why AI Didn't Make Me Faster (And It Wasn't AI's Fault)

SiteQuest — Thu, 25 Jun 2026 17:34:42 +0000

You have three different tabs open containing three different variations of the exact same documentation. You are looking for a single configuration key. You switch back to your editor, ready to type it out, but your finger twitches. Instinctively, your left thumb hits Cmd and your index finger taps Tab.

Suddenly, you're looking at a browser window. You click a link. Then another.

Ten minutes pass. You are now reading an essay about 14th-century agriculture or browsing the latest tech hardware release. You stare at the screen, a vague sense of dread washing over your chest, and think: Wait, what was I doing again? We've all been there. It's not laziness. It's a systemic design flaw in how we work.

The Phenomenon: The Tab Reflex

I call this behavior The Tab Reflex.

It is the completely automatic, near-subconscious urge to leave your current application the moment a micro-question or minor point of friction arises. It's a muscle memory habit built over years of using software designed around separate windows and disjointed ecosystems.

Your hand reaches for the shortcut to change windows before your conscious mind has even formulated the exact question you need answered.

The True Cost of Switching Contexts

Most of us are acutely aware that we switch tabs too much. What we fail to realize is the astronomical mental invoice we pay for it—a cognitive toll I call the Alt-Tab Tax.

The true cost of an interruption isn't the three seconds it takes to open a window, or the ten seconds it takes to read a snippet. The true deficit is the Context Recovery Cost—the agonizing period of time it takes your brain to re-assemble the complex mental scaffolding of what you were doing before you left.

"How did I end up here?"

When you finally return to your project, your working memory has completely evaporated. You have to re-read your own text, re-trace your logic, and reload your thoughts. The heavy cognitive tax comes from recovering your environment, not from the question you went to look up.

How many hours of your week are silently vanishing into this endless loop of rebuilding your focus?

Before you answer, you can calculate your focus points here to see exactly how much context switching is costing you.

While experimenting with ways to reduce this friction, I ended up building a desktop tool called SideQuest. But honestly, the bigger realization wasn't the tool—it was understanding how much time I was losing to context switching in the first place.

DEV Community: SiteQuest