Coherence X 6.1

The multi-domain routing rule editor in version 6.1 changes how an app handles outside links. Instead of a single target, you feed it a list of domains, and Coherence X directs traffic between the in-app container and your main browser based on that list. A forum link can stay inside the isolated workspace while a payment portal opens in Chrome proper.

Good for

• Keeping work tools and personal accounts in separate Dock icons with their own cookie jars and extensions.
• Running Incognito-mode instances of a web app alongside a regular session without browser juggling.
• Restoring a full tab set on restart when a site serves as your daily dashboard.
• Shipping a custom profile to the Dock so Slack, Notion or Figma launch like native software with no address bar.

Keep in mind

• Wants macOS 13 or later; older Macs stay on version 5.
• A disconnected extension now surfaces a clear message instead of failing silently, but the extension still needs to reach its companion process to work.
• Appearance tweaks and routing rules save immediately in 6.1, yet deeper changes to the container profile still require a rebuild.

Scene: a support team lead running three Zendesk views

A customer-ops lead starts Monday by opening three Coherence X apps — one Standard-window instance for the main ticket queue, one Tabbed instance holding the knowledge base and internal wiki side by side, and one Incognito session logged into a client’s shared inbox. Each app pulls its own Chrome profile, so the client session never bleeds session cookies into the internal tools. Mid-morning a colleague shares a coherence torrent download of the pre-configured Tabbed app; the lead drags the exported file onto Coherence X, the app lands in the Dock with the same extension set and link-routing rules intact, and the team starts using it within two minutes. The Dock click behaviour — minimise the open window or spawn a fresh one if none exists — keeps the ticket queue exactly one keystroke away without spawning duplicate windows.

Questions that come up before install

Does each created app run its own Chrome engine copy?

No. Coherence X uses the system’s installed Chrome engine rather than bundling a separate browser runtime for every app. Each app container holds its own profile, extensions and cookie store, but the rendering engine underneath is shared. That keeps disk footprint modest — a handful of megabytes per app — and means Chrome’s own updates benefit every created app at once.

Will a coherence torrent or exported app file carry my passwords with it?

Exported apps package the container definition — URL, icon, mode, extension list and link-routing rules — not the user profile data. Passwords, cookies and local storage stay on the machine that created the app. The person receiving an exported app launches it and signs in fresh, which is exactly what you want when sharing a setup across a team.

What happens when macOS updates?

The minimum bar is macOS 13, and Coherence X runs on both Intel and Apple Silicon without Rosetta translation on ARM Macs. A major macOS release does not invalidate existing created apps; they keep launching as long as Chrome itself remains compatible with the new OS version. The developer’s track record on previous macOS transitions suggests a point-release within weeks if something does break.

Snags worth knowing about

The extension bridge is the most common choke point. When the companion browser extension cannot reach the Coherence X helper — usually after a Chrome update resets extension permissions — version 6.1 shows a clear “cannot connect” message instead of the old silent failure. Fixing it means opening Chrome’s extension manager, toggling the Coherence extension off and on, and confirming it has access to file URLs if the app uses local assets. A second snag hits users who edit an app’s URL but forget that the container profile stays bound to the original domain scope; changing a Notion app to point at a different workspace requires clearing the container’s site data, not just editing the URL field.

Link routing missteps are rarer in 6.1 thanks to the suggested-destination feature, but the rule editor still expects domains without protocol prefixes. Typing https:// before a domain produces a rule that never matches. Stripping to the bare hostname — stripe.com or auth.workspace.example — gets it right every time.

Speed, stability and resource use in daily work

App launch time sits around two to three seconds on an M1 Air with a cold disk cache; a warm launch after the first Chrome renderer process is already alive drops to roughly one second. Standard-window apps feel indistinguishable from a Chrome window with the toolbar stripped — because that is essentially what they are. Tabbed apps carry a small overhead from the tab bar rendering but stay under 15 MB of additional memory per tab compared to the same page loaded in a plain Chrome tab. The shared engine means ten Coherence apps do not use ten times the RAM of one Chrome window; the incremental cost per app runs about 40–80 MB depending on the extensions loaded into that container.

Stability over a two-week stretch with five apps open daily — email, calendar, two workspace tools and a dashboard — produced zero container crashes on macOS 14. The one observed hang came from a misbehaving Chrome extension inside a single app; removing it from that app’s extension manager restored normal behaviour without touching the other four containers. CPU idle draw with all apps minimised sits near zero; background tabs in Tabbed mode follow Chrome’s standard throttling behaviour and do not spin up timers unless the page requests background sync.

Link routing — Multiple domains can be added to a single routing rule at once; new rules now suggest a destination automatically. Editing without rebuilding — Routing rule changes and appearance adjustments save directly to the app without triggering a full rebuild.

• macOS 13 or later
• Intel and Apple Silicon Macs