Exfing 2.4: group-level proxy binding, permission templates, Local API v2

2.4 is a release about doing things in bulk. Putting a batch of profiles behind the same proxy route used to mean opening each profile's settings one at a time, and setting up a new teammate meant ticking permissions item by item. This version lifts both of those to the group level.

Added

• Group-level proxy binding — assign a proxy route to a profile group, and new profiles created in that group inherit it. A per-profile override still takes precedence over the group setting.
• Permission templates — save a role plus a profile scope as a template and apply it when inviting someone. Templates can be shared across the workspace.
• Local API v2 — adds an endpoint for launching sessions across a whole profile group and unifies the error response shape. v1 endpoints keep working; migration notes are in the Local API documentation.
• Import and export — the profile list exports to CSV with profile name, group, proxy route identifier, and last launch time. Cookies and local storage are not exported.

Improved

• The profile list switches to virtual scrolling past 500 profiles, so scrolling and filtering stay responsive.
• Proxy health checks moved from "on profile launch" to an on-demand batch check, with results shown inline in the list.
• The fingerprint settings panel was regrouped, moving less frequently used parameters into a collapsed "Advanced" section.
• The Windows installer is smaller, and updates now download incrementally.

Fixed

• Fixed a case on some macOS versions where the profile list could render blank after minimizing and restoring the window.
• Fixed first-launch authentication occasionally needing a retry for SOCKS5 proxies that use a username and password.
• Fixed open sessions not terminating promptly after a member's profile access was revoked.
• Fixed the Local API returning duplicate session IDs when creating sessions concurrently.

How to update

The desktop client offers the update on next launch. You can also grab the installer from the download page. Workspace-side changes are already live and need no action.