Supported versions

Alfred-Workflow supports all versions of Alfred 2 & 3 and all versions of macOS supported by Alfred 2. It works with Python 2.6 and 2.7, but not Python 3.

Some features are not available on older versions of macOS.

Alfred versions

Alfred-Workflow works with all versions of Alfred 2 and 3, but you must own the Powerpack to use Alfred’s workflow feature.

All Script Filter features provided by Alfred 2 as of v2.8.3 and by Alfred 3 as of v3.6.2 are supported in the latest version of Alfred-Workflow.

The Workflow class is compatible with both Alfred 2 and Alfred 3. The Workflow3 class is only compatible with Alfred 3.


Versions 3.4.1 altered the way workflow variables are set via Script Filter feedback, and Workflow3 as of version 1.27 of Alfred-Workflow uses the new mechanism.

As a result, versions 1.27+ of Alfred-Workflow are not compatible with versions of Alfred older than 3.4.1.

Workflow3 uses Alfred 3’s JSON feedback format. It supports workflow variables and more advanced modifiers than Workflow/Alfred 2.

macOS versions


Versions of macOS before High Sierra have an extremely old version of OpenSSL, which is not compatible with many servers’ SSL configurations, including GitHub’s. workflow.web cannot connect to these servers, which also means that the update mechanism does not work on macOS 10.12/Sierra and older.

Alfred-Workflow supports the same macOS versions as Alfred 2 and 3, namely 10.6 (Snow Leopard) and later (Alfred 3 is 10.9+ only).


Notifications, added in version 1.15 of Alfred-Workflow, are only available on Mountain Lion (10.8) and above.

Python versions

Alfred-Workflow only officially supports the system Pythons that come with macOS (i.e. /usr/bin/python), which is 2.6 on 10.6/Snow Leopard and 2.7 on later versions.


Other Pythons (e.g. Homebrew, conda, pyenv etc.) are not supported.

This is a deliberate design choice, so please do not submit feature requests for support of, or bug reports concerning issues with any non-system Pythons.

This includes Python 3.

(But if you manage to add full Python 3 support without breaking 2.6, a pull request would be gratefully accepted.)

Here is the full list of new features in Python 2.7, but the most important things if you want your workflow to run on Snow Leopard/Python 2.6 are:

Python 2.6 is still included in later versions of macOS (up to and including El Capitan), so run your Python scripts with /usr/bin/python2.6 in addition to /usr/bin/python (2.7) to make sure they will run on Snow Leopard.

Why no Python 3 support?

Alfred-Workflow is targeted at the system Python on macOS. Its goal is to enable developers to build workflows that will “just work” for users on any vanilla installation of macOS since Snow Leopard.

As such, it strongly discourages developers from requiring users of their workflows to bugger about with their OS in order to get a workflow to work. This naturally includes requiring the installation of some non-default Python.

Alfred-Workflow is also precisely the kind of project that’s hard to make 2- and 3-compatible for a few reasons.

  • Python 2.6 support is a hard requirement.
  • Alfred-Workflow’s APIs are thin wrappers around I/O, and it is very much a POSIX/command-line oriented library.
  • workflow.web, as an HTTP library, is all about working with strings of non-specific encoding, which Python 3 turned into a shit show (though it’s slowly getting better).

Personally, I don’t use Python 3 very much (Python 2 is a much better fit for command-line tools, which is what I usually write), and it’s not part of macOS, so I consider the huge effort required to write 2.6- and 3.x-compatible code a waste of my time. If someone else wants to contribute Python 3 support, it will be gratefully accepted.

I realise that Python 3 solves many of the string-handling issues that catch out novice Pythonistas, but as stated, support for non-system Pythons is simply not a goal of this project.

Python 3 will be supported when it ships with macOS by default, and never in version 1 of Alfred-Workflow, which must continue to support Python 2.6 and Alfred 2 (which doesn’t get along with Python 3 [1]).

[1]Alfred uses UTF-8, but Alfred 2 doesn’t specify an encoding in the workflow environment. POSIX-compliant software, like Python, therefore assumes ASCII. Python 2 can handle this misconfiguration, but Python 3 dies in flames.