halo-record

Tamper-evident audit trails for AI agents: hash-chained Runtime Records, dependency-free, verifiable by anyone.

Explore on GitHub Read Hacker News discussions

2Distinct people

3Mentions

0Explicit recommenders

85GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Tamper-evident audit trails for AI agents: hash-chained Runtime Records, dependency-free, verifiable by anyone.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2026-07-07 14:07:08 UTC to 2026-08-31 15:42:56 UTC. Weeks start Monday, UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Jul 6	2026-07-06 00:00:00 UTC	2026-07-13 00:00:00 UTC	2	1	1
Jul 13	2026-07-13 00:00:00 UTC	2026-07-20 00:00:00 UTC	0	0	0
Jul 20	2026-07-20 00:00:00 UTC	2026-07-27 00:00:00 UTC	0	0	0
Jul 27	2026-07-27 00:00:00 UTC	2026-08-03 00:00:00 UTC	0	0	0
Aug 3	2026-08-03 00:00:00 UTC	2026-08-10 00:00:00 UTC	0	0	0
Aug 10	2026-08-10 00:00:00 UTC	2026-08-17 00:00:00 UTC	0	0	0
Aug 17	2026-08-17 00:00:00 UTC	2026-08-24 00:00:00 UTC	0	0	0
Aug 24	2026-08-24 00:00:00 UTC	2026-08-31 00:00:00 UTC	0	0	0
Aug 31	2026-08-31 00:00:00 UTC	2026-09-07 00:00:00 UTC	1	0	1

What Hacker News says

3 sources

tclancy·Aug 31, 2026

Some really good policies in there, at least inasmuch as they match up to what I have been thinking about. Was hoping for more implementation but the one package for attestation/ logging looks useful: https://github.com/bkuan001/halo-record

In Agentic Trust Controls

brian_kuan·Jul 7, 2026

BTW I've added an example to the README, same setup I run on my own machine: https://github.com/bkuan001/halo-record#record-your-coding-a...

In Show HN: Halo – open-source, tamper-evident runtime evidence for AI agents

brian_kuan·Jul 7, 2026Submission

Show HN: Halo – open-source, tamper-evident runtime evidence for AI agents

Hi HN, I'm Brian, I spent the last few years at Vanta (YC W18), helping startups and enterprises become compliant and I recently started exploring what that might look like in a post-agentic world. The problem Halo solves is: when a company buys an AI agent from a vendor and gives it access to their data, they have no way to check what the agent did with that data. Vendors may have built observability dashboards and audit logs, but those are editable and partisan. SOC 2 and ISO 27001 audit a company's controls, but controls are less predictive when the software is agentic. TLDR: give an agent the same prompt 50 times, and you get 50 slightly different actions/answers - so the only thing worth auditing in a post-agentic world is what happened at runtime. Halo is an open-source project that produces agent runtime evidence. It's a small reco

Read the rest

rder that records every action an agent takes (eg. tool calls, model calls, data access, etc), and becomes a record in an append-only log. It's hash-chained, so anyone can re-verify. Run the following command to see a fictional example: uvx --from halo-record halo demo --serve Then, delete a line from one of the .jsonl files and reload, and the report will catch that it's been tampered with. To wire up your own agent, run this line of Python: agent = trace(run_my_agent, profile="my-agent", log="audit.jsonl") Then use this to generate a real report and give it to your customers: halo report audit.jsonl -o report.html Disclaimer: this proves integrity, not completeness (as a self-held chain proves nothing was edited but does NOT prove that nothing was omitted). Catching this requires a witness outside the vendor and is what I'm working on next. Halo is Apache-2.0, contains zero runtime dependencies, and is about 4,300 lines of Python with 125 tests (if you prefer TypeScript, here's that repo: https://github.com/bkuan001/halo-record-ts). Give it a try, and please let me know if you have any feedback!

37 points · Open discussion