This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Agentmetry
A local-first endpoint sensor for AI coding agents
Agentmetry is a local-first endpoint sensor for AI coding agents. It records each tool call Claude Code, Cursor, Codex and others make, in a hash-chained trail on the laptop, and can forward it to the SIEM you already run. The difference is the MCP listing. It hashes tools/list per tool and records when it moves while the config stays the same: the MCP rug pull (ATLAS AML.T0109). It stores the hash, not the text. Apache-2.0. No install needed: uvx agentmetry demo. Sees only agents with hooks.
Hi Product Hunt, I'm Ioannis, and I build Agentmetry on my own, from Greece.
It started with a simple question I could not answer: what did my coding agent actually do on my laptop today? The transcript is a conversation, not a record. My editor keeps no log. Endpoint security sees a process start a process, which is what an agent looks like when it is working fine.
So Agentmetry sits at the tool boundary. Claude Code, Cursor, Codex, Copilot and five more agents call it through their own hooks, and every tool call lands in a hash-chained trail on your machine. Fourteen sequence rules look for risky orders of events, like a credential read followed by a network upload, and label them with MITRE ATT&CK. If you run Splunk, Elastic, Google SecOps or Sentinel, it forwards there. Arguments are hashed inside the hook by default, so the trail holds fingerprints, not your secrets.
What it does not do, so you know before you install it:
- It only sees agents whose hooks are installed. A browser chat or an IDE with hooks off is invisible to it.
- Windows and Linux are tested in CI. macOS runs the test suite but is still in preview.
- It is public alpha, and Sentinel has not been run against a live workspace yet.
The detection benchmark is public: 57 cases, 0 missed, 0 false positives, and you can rerun it with agentmetry benchmark.
To try it without installing anything: uvx agentmetry demo. It replays a credential theft into a temp folder, catches it, then shows the trail failing verification after one edit.
I would love your hardest criticism, especially from anyone who runs a SOC or ships agents to a team.
About Agentmetry on Product Hunt
“A local-first endpoint sensor for AI coding agents”
Agentmetry was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #414 on the daily leaderboard. Agentmetry is a local-first endpoint sensor for AI coding agents. It records each tool call Claude Code, Cursor, Codex and others make, in a hash-chained trail on the laptop, and can forward it to the SIEM you already run. The difference is the MCP listing. It hashes tools/list per tool and records when it moves while the config stays the same: the MCP rug pull (ATLAS AML.T0109). It stores the hash, not the text. Apache-2.0. No install needed: uvx agentmetry demo. Sees only agents with hooks.
On the analytics side, Agentmetry competes within Developer Tools, Artificial Intelligence, GitHub and Security — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how Agentmetry performed against the three products that launched closest to it on the same day.
Who hunted Agentmetry?
Agentmetry was hunted by Ioannis Loutsis. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Agentmetry including community comment highlights and product details, visit the product overview.
Ioannis Loutsis
Hi Product Hunt, I'm Ioannis, and I build Agentmetry on my own, from Greece.
It started with a simple question I could not answer: what did my coding agent actually do on my laptop today? The transcript is a conversation, not a record. My editor keeps no log. Endpoint security sees a process start a process, which is what an agent looks like when it is working fine.
So Agentmetry sits at the tool boundary. Claude Code, Cursor, Codex, Copilot and five more agents call it through their own hooks, and every tool call lands in a hash-chained trail on your machine. Fourteen sequence rules look for risky orders of events, like a credential read followed by a network upload, and label them with MITRE ATT&CK. If you run Splunk, Elastic, Google SecOps or Sentinel, it forwards there. Arguments are hashed inside the hook by default, so the trail holds fingerprints, not your secrets.
What it does not do, so you know before you install it:
- It only sees agents whose hooks are installed. A browser chat or an IDE with hooks off is invisible to it.
- Windows and Linux are tested in CI. macOS runs the test suite but is still in preview.
- It is public alpha, and Sentinel has not been run against a live workspace yet.
The detection benchmark is public: 57 cases, 0 missed, 0 false positives, and you can rerun it with agentmetry benchmark.
To try it without installing anything: uvx agentmetry demo. It replays a credential theft into a temp folder, catches it, then shows the trail failing verification after one edit.
I would love your hardest criticism, especially from anyone who runs a SOC or ships agents to a team.