The Problem
macOS Hot Corners are limited to a single action per screen corner and lack visual feedback or extensibility. Users who want richer automation—launching apps, running shortcuts, or invoking custom scripts from any screen edge—must resort to ad‑hoc scripts or third‑party tools that often require manual configuration and provide no UI integration.
What This Does
SuperCorners replaces the built‑in Hot Corners with a Swift/SwiftUI macOS app that adds zones (mid‑edge triggers) and a menu‑bar action picker. Core logic lives in SuperCorners/Actions/ (e.g., CornerActions.swift, CornerHotkey.swift) which map mouse position events to user‑defined actions. UI components in SuperCorners/Views/ render the settings pane (SettingsView.swift), toast notifications (ToastNotification.swift), and floating utility windows (FloatingCalculator.swift, FloatingNote.swift). The app’s entry point is SuperCorners/SuperCornersApp.swift, which bootstraps the SwiftUI lifecycle and injects the ActionBrowser view.
How To Use It
Clone & Open git clone https://github.com/daniyalmaster693/SuperCorners.git cd SuperCorners open SuperCorners.xcodeproj
The Xcode project (SuperCorners.xcodeproj/project.pbxproj) contains all targets and resources. Build & Run In Xcode select the SuperCorners scheme (SuperCorners.xcodeproj/xcshareddata/xcschemes/SuperCorners.xcscheme) and press ⌘R. The binary is SuperCorners.app produced in DerivedData. Grant Permissions On first launch macOS prompts for Accessibility permission. The app cannot capture mouse events without it (see Info.plist for required usage description). Configure Actions Open the settings window (triggered by the menu‑bar icon defined in SuperCorners/Views/Main/ActionBrowser.swift). Add or edit actions in the Action List UI, which persists to the app’s internal store (no external config file is shipped). Available actions are implemented in SuperCorners/Actions/ (e.g., CornerMousePosition.swift for zone detection, KeyPress.swift for shortcut simulation). Run the App After configuration, move the cursor to a corner or edge zone while holding the hotkey defined in SettingsView.swift. A toast appears (ToastHelper.swift) confirming execution.
No external build scripts, package managers, or environment variables are required; the project is self‑contained.
Real‑World Use
A developer can replace manual “open terminal in current folder” shortcuts with a corner trigger: configure a corner action to run the AppleScript located in SuperCorners/Actions/CornerActions.swift that calls open -a Terminal "$PWD". Once set, moving the cursor to the top‑right corner while holding the modifier instantly opens a terminal at the active Finder location, eliminating repetitive keyboard shortcuts.
Code Health & Issues
Medium – Missing CI/CD – No .github/workflows or other pipeline; changes are not automatically validated. Low – Limited Test Coverage – Only three test files (SuperCornersTests.swift, UI tests) cover a fraction of the UI and action logic; core action execution paths remain untested. Low – Hard‑coded Asset Paths – Image assets referenced directly (e.g., Assets/SuperCorners-1.png) may break if the bundle structure changes; consider using Bundle.main.url(forResource:). Low – No Documentation of Public API – The repo contains README.md and GettingStarted.md but lacks inline documentation for public structs/functions (e.g., CornerHotkey). Adding Swift‑Doc comments would improve maintainability. Low – Entitlements File Unverified – SuperCorners.entitlements is present but not referenced in the project settings; ensure required capabilities (e.g., com.apple.security.accessibility) are correctly configured.
Overall the code compiles cleanly in Xcode 15+, follows SwiftUI conventions, and the UI is modularized into distinct view folders.
The Bottom Line
SuperCorners delivers a functional, SwiftUI‑based extension to macOS Hot Corners with actionable zones, toast feedback, and a menubar picker. It is ready for personal or small‑team use where macOS automation is needed, but the lack of CI and sparse test coverage mean a cautious review before adopting it in production environments.