Skip to main content
Starting with agent 1.5.0, every heartbeat carries a build block that describes where the running code came from. The dashboard renders it as a badge next to the agent’s version.

The three channels

Agents older than 1.5.0 report nothing and show no badge.

How the hash works

The hash is a SHA-256 digest over the agent’s src/ tree: every .ts, .js, and .json file, visited in sorted path order, path and contents both included. The release pipeline computes it with the same function the agent uses at boot, so the two values can only agree when the code is identical.
  • Official images carry a build-info.json stamped at build time with the channel, git commit, and the hash of the exact tree the image was built from.
  • Source runs compute the hash live at startup.
  • Each release publishes its hash as a build-info.json asset on the GitHub release, which is what the dashboard compares against.

What this is, and what it is not

The build block is self-reported telemetry. The agent is open source; a fork can send any value it likes, including a copied official hash. The badge answers the practical question (“is this deployment running the code we published, or something else?”) for operators acting in good faith. It is not an integrity control and does not change what the agent is allowed to do. If you maintain a private fork on purpose, the Modified or Source badge is expected and harmless. It exists so that an unexpected modification, or a stale patched image someone forgot about, is visible instead of silent.
Update availableThe dashboard compares each agent’s reported version against the latest published release and shows an update chip when the agent is behind. This works independently of the provenance badge.