Huginn v1.5.0

First time installing?

Huginn is an open-source personal project and isn't code-signed. Windows SmartScreen and macOS Gatekeeper will both show a warning on first install — that's expected. Code-signing certificates cost real money and aren't worth it for a free personal tool. The source is public on this repo; you can read it.

Windows

1. Download Huginn-win-Setup.exe below.
2. Run it. SmartScreen will warn that the app is from an unknown publisher.
3. Click More info, then Run anyway.

macOS

1. Download the .pkg for your Mac: Huginn-osx-arm64-Setup.pkg (Apple Silicon — M1/M2/M3/M4) or Huginn-osx-x64-Setup.pkg (Intel). Not sure? Apple menu → About This Mac → the Chip/Processor line.
2. Open it. macOS will block it because it isn't signed — that's expected. In the warning, click Done (or Cancel) — not "Move to Trash", which deletes the installer you just downloaded.
3. Open System Settings → Privacy & Security, scroll to the Security section, and click Open Anyway next to the note about Huginn being blocked. Authenticate, confirm Open, then follow the installer.

Once installed, future updates download and apply themselves the next time you launch the app — you don't need to repeat any of this.

---

What's new

• New: an agent can ask why a single service finding is happening. Huginn runs the drill-downs behind the finding using its own sign-in and answers over the MCP connection, so an agent can reach the telemetry behind a finding, over the same window Huginn measured, without Azure access of its own.
• A service finding's open button now opens the portal on the query behind the finding. It used to open the failures or performance blade, which lists every operation the resource has and answers over a different window, so the finding being looked at had to be found again by hand. What opens depends on the kind: a failing route opens the exceptions with their stack traces, a failing dependency opens the exception from the call that used it, and a slow route opens its percentiles over the window.
• New: opening a finding in the portal explains what the portal does to the link, once. The portal covers the query with its own queries hub, and may show it in Simple mode with the KQL hidden. Neither can be set from a link, so the query looks absent when it is not there to see. The explanation can be turned off from the dialog itself or under Settings, General.
• Agents are told at connect time where to start, and how Huginn's access relates to their own. An Azure MCP server holds a single identity for its lifetime, which stays invisible until a query fails with what looks like a permission error and is not one.