Feature description

The Finder integration has been modernized by introducing a native FinderSync extension directly within the VisualDiffer app.

This replaces the previous approach based on a separately installed Automator script, which is no longer required. The FinderSync integration provides the same Finder context menu functionality using native macOS APIs and is now the recommended and supported way to interact with VisualDiffer from Finder.

This issue documents what changed and clarifies the rationale behind deprecating the Automator-based integration.

Why is this useful?

The previous Finder integration relied on an external Automator workflow that users had to install and maintain manually, which added friction and complexity to setup and onboarding.

Using FinderSync:

• Removes the need for external scripts
• Simplifies installation and user experience
• Improves maintainability and long-term macOS compatibility
• Aligns the project with modern macOS extension APIs

Overall, this results in a cleaner, more robust, and more predictable Finder integration.

Alternatives considered

Continue supporting the existing Automator script as the primary Finder integration.

This option was rejected because Automator-based workflows are harder to maintain, require manual installation, and provide a less native experience compared to FinderSync.

Environment (if relevant)

macOS 13 (Ventura) or later — required for native FinderSync integration

Priority

None

Screenshots or mockups (optional)

Additional notes (optional)

No response