Repository navigation
Crowsnest 0.12.0
Syspeek is now Crowsnest. Same product, same 33-view console, same local-only
collection — a name that says what it is: the lookout above the fleet.
What changed
- The binary, packages, config path, systemd/LaunchAgent/MSI entries, focus
bridges, docs, site and the relay dashboard all say Crowsnest. - Repositories:
codeafridi/Crowsnestandcodeafridi/crowsnest-relay
(old URLs redirect).
Upgrading is not a reinstall
- On first start the new config file is seeded from
~/.config/syspeek
(orSyspeek), andSYSPEEK_CONFIGis still read. - The stable machine id and the offline spool are copied from the old cache
directory first, so the relay does not see a brand-new machine. - Installers remove the old systemd unit, XDG autostart, LaunchAgent, HKCU Run
value, shims and GNOME/KWin focus bridges before installing the new ones. - Packages declare Conflicts/Replaces/Obsoletes on
syspeek; the MSI keeps
the existing UpgradeCode; the Homebrew cask conflicts with the old cask.
Deliberately breaking
- Prometheus metrics are
crowsnest_*(weresyspeek_*). - The
--recordJSON envelope key is"crowsnest". - Webhook payload
source/receiverlabels name crowsnest. - Relay sessions use
__Host-crowsnest; existing logins sign in again.
The ingest token hash, session hash and channel-secret HKDF domains keep their
historical values on purpose — those strings are stored data, not branding, and
renaming them would invalidate every token, session and sealed secret.
Assets
| Platform | Asset |
|---|---|
| Linux (any glibc ≥ 2.34, bundled Qt) | crowsnest-portable.tar.gz, Crowsnest-0.12.0-x86_64.AppImage (+ .zsync) |
| Debian/Ubuntu | crowsnest_0.12.0_amd64.deb |
| macOS 12+ (universal) | Crowsnest-0.12.0-macos.dmg |
| Windows 10+ | Crowsnest-0.12.0-windows.msi, Crowsnest-0.12.0-windows-portable.zip |
SHA256SUMS covers all six downloadables.
Proof
CI green on Ubuntu 24.04, macOS 15 and Windows, plus both clean-room Debian
container jobs (22.04/24.04 install + --dump + --probe). The portable bundle
and AppImage in this release were built locally and each ran --dump and
--probe before upload.
Not run on real hardware: a real Mac battery, NVIDIA silicon, a real X11
desktop with click-through, a real cloud account.