1
My last post was about what I’m working on. We had just launched, and I was excited to hear some feedback.
Full of anticipation, I used the prefix `Launch HN` in the title and clicked Submit.
After rereading the post, I noticed the title was wrong. It said `Show HN: ... `instead of `Launch HN: ....`
I assumed I had made a mistake, so I edited the post and changed the title back to `Launch HN`.
I pressed Submit again—only for it to revert to Show HN.
After repeating this a few times, deleting the post, and submitting it again, I finally realized it wasn’t me.
It was HN.
I’m glad I learned something new about Hacker News and the etiquette today. I’ll keep going, and eventually I’ll be able to post something that someone else wants to see.
For now, I’ll just take a quick look at what’s new on HN and call it a day.
We are building Legit, an open source version control and collaboration layer for AI agents and AI native applications.
You can find the repo here https://github.com/Legit-Control/monorepo and the website here https://legitcontrol.com
Over the last years, we worked on multiple developer tools and AI driven products. As soon as we started letting agents modify real files and business critical data, one problem kept showing up. We could not reliably answer what changed, why it changed, or how to safely undo it.
Today, most AI tools either run without real guardrails or store their state in proprietary databases that are hard to inspect, audit, or migrate. Once agents start collaborating on shared data, you are often just crossing your fingers and hoping nothing goes wrong.
We noticed something interesting. Developers do not have this problem when collaborating on code, and agent like workflows took off there first. The reason is relatively simple. Git already solves coordination, history, review, and rollback.
That insight led us to build Legit. We bring Git style versioning and collaboration to AI applications and to most file formats. Every change an agent makes is tracked. Every action is inspectable, reviewable, and reversible. No hidden state. No black box history.
Legit works as a lightweight SDK that AI apps can embed anywhere the filesystem works. It handles versioning, Sync, rollback, and access control for agens. Everything lives in a repository that you can host yourself or on any Git hosting provider you already trust.
We believe the right way to scale AI collaboration is not to hide what agents do, but to let developers and users see, review, and control every change. Legit is our attempt to bring the discipline, visibility, and safety of modern developer workflows to write enabled AI applications.
Give it a spin: https://github.com/Legit-Control/monorepo and let us know your feedback, criticism, and thoughts.
What I find strange is that Hacker News feels oddly opaque. I’ve never met anyone who can clearly explain how it works in practice. Not just the rules, but the dynamics: what’s repeatable, what’s luck, and what actually matters.
By using the Kevin Bacon-number idea: I can usually get within three degrees of separation of well-known technologists like Linus Torvalds, but I can’t seem to get within three steps of someone who confidently understands how HN works.
So I’m asking sincerely: Does anyone here feel they understand Hacker News? If so, what are the real levers, and what do people consistently misunderstand?
PS: This question comes from a mix of genuine curiosity and personal frustration. I’m honestly trying to understand how HN works in practice.
But here’s the thing: in 2025 our biggest collaborators aren’t just humans, they’re AI tools. And those tools need the messy history: the failed attempts, the typos, the bad refactors. That’s the context they learn from.
When we squash everything into a perfect history, we’re deleting the very breadcrumbs that could help an agent explain a bug, trace a regression, or warn us we’re about to repeat an old mistake.
“Clean history” makes reviewers happy today. But it’s technical debt for tomorrow’s AI-assisted development
We’re building *Lix*, a change control SDK that tracks every modification in your files or apps—no matter the format. Think of it like Git, but for *any* digital file, running in your browser.
## What is Lix?
Lix is a *file-agnostic change control system* that works across different environments. It lets you: - *Track every change* made to a file or app, whether by humans or AI - -See what changed, when, and by whom** - - Integrate version tracking into your own applications via our SDK
This means *AI-generated edits* (e.g., AI-assisted writing, automated code suggestions) are no longer a black box—you can see exactly what changed and decide whether to keep or revert them.
## Why Did We Build It?
We originally built *inlang.com*, a localization solution, and realized that translators, designers, and developers all needed to track changes across different file types and platforms. Existing tools weren’t flexible enough.
As we iterated, we saw a broader need: *AI-assisted workflows and collaborative apps* require *transparent change tracking*. Whether it’s an AI rewriting text, auto-fixing code, or updating structured data, *users want to review and merge changes, just like they do with Git*.
## Try It Out
We built a few demo apps to showcase Lix: [*Markdown App*](https://lix-md.onrender.com/) – Write Markdown with AI assistance & see exactly what the AI changed. (I drafted this post in it!)
[*CSV App*](https://lix.opral.com/app/csv/?l=lTj18aPHiC93VDrpwW) – Ever had an intern mess up your cap table? Now you can track and revert every edit.
[*Fink*](https://fink2.onrender.com/) – Track and compare changes in the translated text.
## Feedback
We want to position Lix as the *change control SDK for AI-driven workflows*, but we’re still refining our messaging. Would love your thoughts on how to frame this better!
What use cases do you see where *human-AI collaboration* needs better versioning?
Any feedback, ideas, or brutal honesty is much appreciated!