Installation
Productivity runs on macOS (Apple silicon or Intel, Metal required) and Linux (Wayland or X11, normally with a Vulkan driver). The Ubuntu APT repository is signed; macOS builds have no Developer ID signature or notarization.
macOS with Homebrew
You need Apple’s Command Line Tools (xcode-select --install), Rust,
and uv for the packaging helper.
git clone https://gitlab.com/framezero/productivity.git
cd productivity
brew tap-new local/productivity # once
uv run --locked python tools/brew_local.py
brew trust --cask local/productivity/productivity
brew install --cask local/productivity/productivity
tools/brew_local.py builds an optimized release, ad-hoc signs and verifies the finished
app bundle, and writes a local archive and cask. The archive excludes Finder/resource-fork
metadata that would invalidate strict signature verification. The helper never installs
or launches the app. To update, quit Productivity, pull, rerun the
Python command, and run brew reinstall --cask local/productivity/productivity.
Uninstall with brew uninstall --cask productivity; your data stays in place.
This is not a published tap, so brew update does not fetch new builds. Ad-hoc signing
checks bundle integrity but does not establish a developer identity or notarize the app;
macOS may still ask for approval in System Settings → Privacy & Security.
brew trust approves the local cask, not the app’s macOS signature.
If an older local build says it is damaged and should be moved to the Bin, regenerate the bundle with the current helper and reinstall it:
# Save your work and quit Productivity first.
uv run --locked python tools/brew_local.py
brew reinstall --cask local/productivity/productivity
brew install skips an already-installed version even after rebuilding; reinstall
replaces it. Do not repeat brew tap-new if the tap already exists.
To check the replacement’s signature, run
codesign --verify --deep --strict --verbose=2 /Applications/Productivity.app.
Ubuntu 26.04 (APT repository)
CI publishes a signed amd64 repository on every successful main pipeline. Installation
from the earlier unsigned repository worked on Ubuntu 26.04; the signed setup below and
graphical launch of the packaged app have not been verified on Ubuntu yet.
Latest .deb download and build details ·
Release SBOM · Test coverage
APT checks every update against the repository’s signing key. Its fingerprint is:
BD52 1CD6 100F C5CF D197 ECE9 9F9C F1D4 7765 E81C
The key file is also committed in the source repository as
packaging/apt/productivity-archive-keyring.asc. These commands work in bash, zsh, and fish.
First download the key and compare its fingerprint with the one above:
sudo install -d -m 0755 /etc/apt/keyrings
sudo wget -qO /etc/apt/keyrings/productivity.asc https://productivity-b29eff.gitlab.io/productivity-archive-keyring.asc
gpg --show-keys /etc/apt/keyrings/productivity.asc
If the fingerprint differs, stop and delete the file. Otherwise add the source and install:
printf '%s\n' 'Types: deb' 'URIs: https://productivity-b29eff.gitlab.io' 'Suites: resolute' \
'Components: main' 'Architectures: amd64' 'Signed-By: /etc/apt/keyrings/productivity.asc' |
sudo tee /etc/apt/sources.list.d/productivity.sources >/dev/null
sudo apt update
sudo apt install productivity
/etc/apt/sources.list.d/productivity.sources then contains:
Types: deb
URIs: https://productivity-b29eff.gitlab.io
Suites: resolute
Components: main
Architectures: amd64
Signed-By: /etc/apt/keyrings/productivity.asc
Upgrading from the earlier unsigned repository: if your source file still says
Trusted: yes, run both blocks above. tee replaces the file, which removes Trusted: yes;
APT then refuses any repository data that this key did not sign.
The signing key is valid until 2028-11-14. Before then, a renewed key will be announced
here; you will need to download it again with the same wget command.
If Productivity cannot start, it shows the error and this session’s log instead, with buttons to copy both, open the log folder, or report it: Report on GitLab copies the error and log and opens the project’s issues, so you can paste them into a new issue. “This database was created by a newer version” means a newer build, such as one run from source, has already upgraded your database; this package is older and will not open it. Install a package at least as new as that build. Your data is not changed.
Quit Productivity before upgrading with sudo apt update && sudo apt install --only-upgrade productivity.
Uninstall with sudo apt remove productivity, and delete the source file if you no longer
want it. Neither deletes your tasks or Markdown files. The repository keeps only the current
package. The build identity of the published package is available too.
From source
Install Rust (stable) and, on Linux, the native libraries below. Then:
git clone https://gitlab.com/framezero/productivity.git
cd productivity
cargo run --locked --release
The first build takes a while because GPUI compiles its rendering stack.
macOS requirements
Install Apple’s Command Line Tools. The app uses GPUI’s runtime Metal shaders, so the standalone Metal compiler is not needed. If your developer tools point to a fresh Xcode, finish its first-run setup and review its license before building.
Linux requirements
On Ubuntu or Debian:
sudo apt-get install -y build-essential clang cmake pkg-config \
libasound2-dev libfontconfig1-dev libfreetype6-dev \
libwayland-dev libx11-dev libx11-xcb-dev libxcb1-dev \
libxkbcommon-dev libxkbcommon-x11-dev libxi-dev libxrandr-dev \
libxcursor-dev libxinerama-dev libgl1-mesa-dev libegl1-mesa-dev libvulkan-dev
Package names vary by distribution. Also install a Vulkan driver for your GPU, for example
mesa-vulkan-drivers.