docs: add macOS per-profile launcher example#256
Open
mvanhorn wants to merge 1 commit into
Open
Conversation
Closes CloakHQ#246. Codifies the maintainer reply from CloakHQ#246: a runnable launch_persistent_context script parameterized by PROFILE_NAME and PROFILE_SEED constants, with a header comment block describing the two-step Automator "Run Shell Script" wrap. Lets users build native macOS desktop .app launchers (one per profile) that open CloakBrowser directly with a fixed fingerprint seed — no Manager web UI. Adds a single bullet in the Examples section of README.md pointing at the new file. No changes under cloakbrowser/.
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
1 participant
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.
Summary
Adds a runnable per-profile macOS launcher example so users can ship one
.appshortcut per CloakBrowser profile (fixed fingerprint seed, persistent profile dir) without reading through #246 to reconstruct the pattern.Why this matters
In #246, @webparadoxer asked how to create native macOS desktop launchers per profile (e.g.
Cloak Profile A.app,Cloak Profile B.app) that open the browser directly with a stable fingerprint, not the Manager web UI. The maintainer's reply walks through a completelaunch_persistent_context+ Automator pattern. Right now that pattern is only discoverable by finding and reading the issue thread.This codifies the maintainer's reply as a small example file.
Testing
python3 -m py_compile examples/macos_profile_launcher.pypasses.grep "examples/macos_profile_launcher.py" README.mdreturns 1 (link present, no broken markdown).launch_persistent_contextimport path asexamples/persistent_context.py, so future API renames pick it up consistently.PROFILE_NAMEandPROFILE_SEEDconstants at the top of the file make per-profile copies a one-edit affair. The header comment block describes the two-step Automator wrap.cloakbrowser/changes. No new dependencies.Fixes #246