Skip to content

WindowRanger 1.0.1

Choose a tag to compare

View all tags
@VeniVidiVici VeniVidiVici released this 30 Aug 20:11
Immutable release. Only release title and notes can be modified.
v1.0.1
22049ae
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

WindowRanger 1.0.1

WindowRanger 1.0.1 is a focused Stable correction for the bundled command-line interface. The app,
workspace engine, settings, layouts, profiles, previews, and update channels are otherwise
unchanged from 1.0.0.

Fixed

  • Fixed every IPC-backed windowranger command being rejected by a signed installed app with
    The WindowRanger command peer is not the bundled executable. The CLI now verifies the exact
    signed WindowRanger bundle location returned by macOS while retaining the same-user, Team ID,
    code-identifier, dynamic-signature, and exact helper-path checks.

Requirements

  • macOS 14 or later.
  • Accessibility permission for window discovery and management.
  • Screen Recording permission only when optional captured workspace previews are enabled.

Installation

Download WindowRanger-1.0.1.dmg from this release's Assets section, open it, and drag
WindowRanger onto the Applications shortcut. The notarized ZIP and both checksum files are included
as fallbacks and for verification.

Homebrew users can install or upgrade the public Stable Cask with:

brew install --cask appranger/tap/windowranger
brew upgrade --cask appranger/tap/windowranger

Stable 1.0.0 users can also install this correction through WindowRanger's signed in-app updater.

Known limitations

  • WindowRanger manages virtual workspaces inside the current macOS desktop; it does not replace
    native macOS Spaces.
  • Captured workspace previews remain optional and off by default.
  • Some applications expose ambiguous or read-only Accessibility windows that WindowRanger
    conservatively ignores.

Feedback and security

Use the repository issue forms for privacy-safe bugs, feature requests, and questions. Do not post
suspected vulnerabilities, private diagnostics, window titles, document names, URLs, or user file
paths in a public issue; follow SECURITY.md instead.

Assets 8
Loading