pierrelf.com / mct
Mission Control Turbo: macOS multitasking turbocharged
fork atom
Swift 84.8%
Shell 2.2%
Other 13.0%
7 1 0

Clone this repository

https://tangled.org/pierrelf.com/mct https://tangled.org/did:plc:meotu43t6usg4qdwzenk4s2t/mct
git@tangled.org:pierrelf.com/mct git@tangled.org:did:plc:meotu43t6usg4qdwzenk4s2t/mct

For self-hosted knots, clone URLs may differ based on your setup.

Download tar.gz
README.md

Mission Control Turbo#

Turbocharge your macOS experience!

Mission Control Turbo is a lightweight macOS application that replaces the built-in Mission Control experience.

Features#

  • Global hotkey — trigger the overlay from anywhere (default: ⌃↑)
  • Live window thumbnails — captured via ScreenCaptureKit
  • Keyboard navigation — arrow keys to move between windows, Return to select, Escape to dismiss
  • Multi-display support — overlay appears on every connected screen
  • Grouped by app — windows are organized under their app name and icon
  • Menu bar extra — access the overlay, settings, and quit from the menu bar
  • Configurable — change the hotkey in Settings

Requirements#

  • macOS 26 Tahoe
  • Apple Silicon (arm64)

Permissions#

Mission Control Turbo requires two system permissions:

Permission Reason
Accessibility Register the global hotkey and activate windows
Screen Recording Capture window thumbnails for the overlay

You'll be prompted to grant these on first launch. They can also be managed in System Settings → Privacy & Security.

Tip: To use the default ⌃↑ hotkey, disable the native Mission Control shortcut in System Settings → Keyboard → Keyboard Shortcuts → Mission Control.

Building#

./build.sh

The built app bundle will be at build/MCT.app.

Code signing#

The build script ad-hoc signs the app by default (using codesign -s -). This is sufficient to run locally, but macOS will reset permissions (Accessibility, Screen Recording) every time you rebuild.

To preserve permissions across builds, sign with a self-signed certificate:

  1. Open Keychain Access
  2. Go to Keychain Access > Certificate Assistant > Create a Certificate...
  3. Enter a name (e.g. Your Name), set Certificate Type to Code Signing, click Create
  4. Create a .env file in the project root (git-ignored):
echo 'CERT_NAME="Your Name"' > .env

The build script reads CERT_NAME from .env automatically. When set, the app is signed with your certificate and macOS will remember granted permissions between rebuilds.

AI disclaimer#

This project was largely developed using Claude Code Opus 4.6 as an experiment in AI-assisted software development.