Scopo, Cmd+Tab scoped to the current macOS Space

Name: Scopo, Cmd+Tab scoped to the current macOS Space
Availability: InStock
Author: IgorCRD

by IgorCRD·Mar 4, 2026·2 points·0 comments

Visit Project View on HN

AI Analysis

●●●BangerSolve My ProblemSlickShip It

Cmd+Tab respects Spaces, zero setup, native Swift performance.

Strengths

•Addresses genuine multi-project friction with minimal cognitive load—no configuration, reads existing Spaces
•Native Swift implementation with low-level CGEventTap interception ensures sub-millisecond responsiveness
•Private-by-design: no analytics, no cloud, no accounts—accessibility permissions only

Weaknesses

•macOS-only; no Windows or Linux support limits addressable market
•Pricing ($20–30/yr) may feel high for a single-feature utility despite honest model

Post Description

I built Scopo after reading Theo's [https://x.com/theo] post about the "Agentic Code Problem". The reality that developers now work on 3-4 projects simultaneously and spend more time switching between windows than actually building.

The core idea: macOS Spaces are already project boundaries. Why doesn't Cmd+Tab respect them?

Scopo replaces the system Cmd+Tab with one scoped to your current Space. Each Space is a project context. You see 3-4 relevant windows instead of a bunch of unrelated windows and apps.

I built it for myself, used it for weeks on my work machine, and realized I couldn't work without it when I switched to a machine that didn't have it.

Some implementation details:

- CGEventTap to intercept Cmd+Tab before the Dock handles it - Moving windows between spaces on macOS 15 is hard — all SLS/CGS private APIs are broken without SIP disabled. Scopo simulates a Mission Control drag (same technique as Hammerspoon's Drag.spoon) - TF-IDF + cosine similarity for smart window-to-project matching

Built with Swift/AppKit

https://scopo.app

First time launching something, would genuinely appreciate any feedback on the product or the implementation.