openwhispr 1.7.5 (new cask)#275246
Open
bitconym wants to merge 1 commit into
Open
Conversation
bitconym
force-pushed
the
openwhispr-cask
branch
from
July 16, 2026 10:01
d4c3f20 to
65f254e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a cask for the OpenWhispr Mac application. I personally installed the application with
brewper the guide, and ran the application, changing its settings and doing a speech-to-text conversion to check the proper functionality. I uninstalled the application, and manually investigated and verified thezappaths myself against a live install on Apple Silicon; worth mentioning, the app is also notarized.The app spreads its data across several locations. Its models (Whisper/embedding) and a local Qdrant vector database live under
~/.cache/openwhispr; its Electron user-data directory (SQLite databases, keys, logs) is at~/Library/Application Support/open-whispr; and it also creates a marker directory at~/.openwhisprplus a recent-documents shared-file-list entry. Because the app auto-updates, I additionally installed an older release and let it update in place to capture the updater's footprint: electron-updater downloads into~/Library/Caches/open-whispr-updaterand hands off to Squirrel.Mac for the install, which creates~/Library/Caches/com.gizmolabs.openwhispr,~/Library/Caches/com.gizmolabs.openwhispr.ShipIt,~/Library/HTTPStorages/com.gizmolabs.openwhispr, and a per-machineShipItplist under~/Library/Preferences/ByHost. Thezapstanza covers every path I observed the app create.After making any changes to a cask, existing or new, verify:
brew audit --cask --online <cask>is error-free.brew style --fix <cask>reports no offenses.Additionally, if adding a new cask:
brew audit --cask --new <cask>worked successfully.HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask>worked successfully.brew uninstall --cask <cask>worked successfully.zapstanza paths.I used Claude Code to help author the cask and to script the investigation of the app's on-disk footprint. However, I ran every command myself on my own Apple Silicon Mac and personally verified the results. In particular, I determined the
zappaths empirically: I installed the app, launched it and used it, then installed an older release and drove the in-app auto-update to 1.7.5 to observe exactly which paths the updater creates (the Squirrel/ShipIt,HTTPStorages, andopen-whispr-updatercache paths only appear during a real update, not a fresh install). I cross-checked the result againstbrew generate-zapand confirmed the stanza covers every path I observed the app create.