Mandip Adhikari
← Index
ProjectJun 2026 — Present

Parallex

A Mac app that runs a second Slack, WhatsApp, Claude or Chrome — each with its own sign-in, data, keychain and Dock icon — without ever modifying the original app. Shipped through 64 versions with a self-updater, a Homebrew cask, and a lab that tests 35 apps on a clean Mac every night.

brew install --cask mandipadk/parallex/parallex

Swift · SwiftUI · C · Objective-C · APFS · Code signing · GitHub Actions · Homebrew

3.7.2 · 64 releases · macOS 14+

64
releases, 0.8.0 to 3.7.2
35
apps tested nightly on a clean Mac
38 / 40
instances ran clean in the Oct 30 lab run

Two kinds of instance

A launcher instance is a small app, under 2 MB, that starts the original with flags pointing its data somewhere else — --user-data-dir for Chromium apps, for example. Nothing is injected.

An own copy is an APFS clone with its own bundle ID, re-signed on the Mac with a local certificate kept in Parallex's own keychain. Every copy is signed with the same certificate, so camera and file permissions survive when Parallex refreshes it; the copy's built-in updater is turned off and Parallex updates it instead.

Slack.app (original, never changed)
    │  APFS clone
    ▼
Slack Work.app ── own bundle ID, re-signed locally
    │  launcher: home-redirect library loaded? no ──▶ refuse
    ▼
running copy ── ~/Library, $HOME ──▶ instance folder
    │           Documents, Downloads ──▶ shared via links
    └── guard: no access to the original's prefs, caches, data

Redirecting the home folder

Mac apps find ~/Library by asking who the user is, not by reading $HOME. So for apps that aren't sandboxed, the launcher loads a small library that answers with the instance folder; child processes such as a shell or git get the real home back.

App Store apps already get a sandbox container. For apps that keep sign-ins in containers shared across a developer's apps (WhatsApp, for one), a second library points those lookups at the copy's own containers. Chromium and Electron copies each get their own Safe Storage key.

The trade-offs, written down

Re-signing drops the hardened runtime and breaks anything tied to the developer's signature: iCloud, Apple push notifications, Sign in with Apple, universal links and system extensions. Apple's own apps can't be copied. The public How it works page lists all of this instead of burying it.

A compatibility lab, every night

A GitHub Actions macOS runner downloads the latest release and checks its checksum, installs each app fresh with Homebrew, creates an instance exactly the way New Instance does, opens it, and records whether it kept running, crashed, or reached the original app's data. Browsers are also tested as profile-folder instances, so 35 apps give 40 instances. Results land on the site's compatibility page.

nightly runner (clean macOS)
  fetch release ──▶ verify checksum ──▶ Parallex.app
  brew install --cask <app>   × 35
  per app: instance ──▶ open ──▶ wait 30s ──▶ check
     ran │ quit │ crashed │ leaked │ not copied
  results.json ──▶ lab-results branch ──▶ /compatibility