Launched this week
Antelog
Stops AI coding agents from leaking or destroying your data
92 followers
Stops AI coding agents from leaking or destroying your data
92 followers
AI coding agents are amazing. Until one deletes your database, or leaks your secrets. Antelog stops the disasters before they happen, and shows you everything your AI did: every command, every website, every bit of data it sent. Works with Claude Code, Cursor and Codex. Free.
Launch Team
CotypistTab completion for your emails, Slack replies and AI prompts, in every Mac app.
Promoted
📌 Hey Product Hunt! I'm Yash, founder of Antelog.
In April, an AI agent deleted a company's entire production database in seconds. The backups went with it. The developer had only asked it to fix a small error.
That's when I realized: we're giving AI agents the keys to everything, with no brakes.
So I built Antelog.
🛑 It stops disasters. If your AI is about to:
• delete your database or backups
• wipe your files or overwrite your team's code
• show or send your passwords and keys
• send your data to a stranger because a web page tricked it
…Antelog blocks it, before it happens.
👀 It shows you everything. Every command your AI ran, every website it visited, every piece of data that left your computer. Written down, and impossible to secretly change.
🧠 Built on research. Antelog is built on LogAct, a research paper published by Meta, which records every AI action before it runs. We added the protection on top.
Works with Claude Code, Cursor, Codex and more. One install. Free.
What's the scariest thing your AI agent has ever tried to do? 👇
I'll be in the comments all day!
@yash_sarwaiya How does Antelog handle false positives without solwing down legitimate AI agent actions?
@shivam_kushwaha16 To solve this, we built three level of checkers.
The first one uses simple rules.
The second one is an AI that is very fast and careful. It stops all dangerous commands, but it also stops a few safe ones, about 3 to 4 percent. To fix that, we added a third AI. It is a little slower but smarter, so it only looks at the few commands the second one stopped, and it lets almost all the safe ones go. All of this takes less than a second at most, about 50 ms at best.
what about a python script the agent writes that reads .env, caught too?
@leoheo Yes, if it shows or sends the secrets. Antelog reads the script before it runs, not just the command. A script that prints your .env, or sends it to an outside server, gets stopped.
@yash_sarwaiya oh ok, it reads the whole script first. good to know
cool launch!! how often does it block stuff i actually wanted, like wiping a local test db on purpose
@igorblink
Thanks! Wiping a local test database won't be blocked. Antelog knows the difference: databases on your own computer with names like app_test or dev, and SQLite files, can be wiped freely. It only blocks wiping production data and backups.
We tested it on thousands of everyday commands, and it rarely blocks something you wanted. If it ever does, just run that command yourself. 🙂
blocking the rm -rf moment before it happens is huge 🙏 any plans for team policys?
@petrkovacik Thanks Petr! 🙏 Yes, we support team policies. You set them once, and every developer's computer gets them in a few minutes. You can also set rules for each person, like stopping one person's AI from running database migrations. Happy to show you if you want to try it.
As a solo dev, the audit log is the part that interests me most — blocking a delete is great, but the scarier stuff is what an agent does quietly and I only notice a week later. Is the log something you can actually scan after a session to see what files changed and what left the machine, or is it more of a raw trail you dig through once something's already gone wrong?
@jcbuilds Both, but the scan is the point. After a session you can run `antelog sent --since 24h` and get a short list of everything the agent sent off your machine: files, data, messages, pushes, and where each one went. `antelog dashboard` opens the whole session in your browser: what ran, what was blocked and why, and what left the computer.
scariest one for us wasn't even a delete. an agent did git add -A and pushed another session's half done work straight to main lol. we ended up writing our own hook rules for stuff like that, can you add project specific rules in antelog or is the list fixed?
@digi_dinos
Haha, that one hurts.
Yes, you can add your own rules! One line per rule, in plain words:
antelog rules add "git push * main"
From then on, Antelog blocks the AI from pushing to main, and you still can. For teams, admins set company rules once on the dashboard, and they apply on every developer's computer.
@yash_sarwaiya oh nice, plain words is exactly what we needed. git push * main would've saved us that day lol
@digi_dinos :) .. yes, plain words are the way to go!!
@yash_sarwaiya haha yep. good luck w the launch today 🙌
does it catch stuff that goes thru mcp tools too or only shell commands? half the time our agent hits the db via an mcp server not psql so thats where id actually worry
@bacelj
Yes, MCP tools too! Antelog checks every tool call the agent makes, not just shell commands. So if your agent sends DROP TABLE or wipes a table through a db MCP server, it's blocked the same way as through psql. The same goes for MCP tools that delete cloud db or send data outside.