LineageLens
AI wrote it. LineageLens proves it.
LineageLens launched on May 14, 2026 with 57 votes, #738 of 20,538 launches that month and more than 95% of that year's launches.
What it does
Been deep in AI-assisted dev work and kept hitting the same wall: something breaks in AI-generated code and there's no way to answer "which prompt wrote this, which model, and what was the context?" Root cause analysis becomes guesswork. Built LineageLens to fix that. It runs a local proxy on port 8788 that sits between your AI tools and their providers. Every time an AI writes ≥4 lines into your codebase, it captures the exact prompt, the model and tool that produced it (Cursor, Claude Code)
Free, open-source tool to track AI-generated code from Copilot, Cursor, Claude Code & Gemini. See which AI wrote each line, and flag IP/license risk.
Git blame only names the human who committed the line. LineageLens shows the AI that actually wrote it, whether anyone reviewed it before it shipped, and the license, security, and IP risk it carries — across 11 AI coding tools including GitHub Copilot, Cursor, Claude Code, OpenAI Codex, and Gemini. Open source, self-hosted — zero data leaves your environment. Then lineagelens blame annotates any file line-by-line with the AI that wrote it. The flagship risk is the universal one — unreviewed AI code running in production. Knowing the exact model and prompt then pays off five more ways, roughly in order of the money attached: AI tools can regurgitate GPL/AGPL-licensed code verbatim. In a…from lineagelens.dev
Does a similar job
all alternatives →
PrompTessor2025 · promptessor.com · ▲125After countless hours of solo coding, designing, and iterating, I’m both excited and nervous to share my first-ever product: PrompTessor — now live. As someone who constantly experiments with AI tools like ChatGPT and Midjourney, I often found myself stuck in a loop of trial-and-error. The issue wasn’t always the AI — it was often the prompt itself. That observation became the starting point for PrompTessor. This tool doesn’t just optimize your prompt — it analyzes it. It gives you: - A prompt score - A breakdown of strengths and weaknesses - A fully optimized version of your prompt - And…
PromptDC - Cursor for Prompts2025 · promptdc.com · ▲17Hey HN, Since late 2021, I’ve been building apps using only AI models. Over time, I realized the real problem wasn’t how good the coding models were, but how you write and structure your prompts. When I vibe code, I make a looooot of typos or write unclear prompts. I often find myself reverting to old versions because the AI misunderstood my prompt and made incorrect changes. But in reality, it’s usually not the AI’s fault. It’s my prompt. That’s why I built PromptDC. It enhances your prompts with one click, without leaving your web-based platform or local editor. Just write your prompt in…
OriginMar 2026 · getorigin.io · ▲6We built Origin after realizing nobody on our team could answer "which AI wrote this?" when a bug appeared. Origin hooks into Claude Code, Cursor, Gemini, and Codex. Every commit gets tagged with which agent wrote it, what prompt generated it, which model, and what it cost. Run `origin blame` on any file and you see [AI] or [HU] per line — like git blame but for AI agents. All data stored in git notes. No server required, works offline, zero lock-in. CLI is open source (MIT): github.com/dolobanko/origin-cli Team dashboard: getorigin.io Would love feedback on the attribution…
- KAKeelTest – AI-driven VS Code unit test generator with bug discoveryJan 2026 · keelcode.dev · ▲30
I built this because Cursor, Claude Code and other agentic AI tools kept giving me tests that looked fine but failed when I ran them. Or worse - I'd ask the agent to run them and it would start looping: fix tests, those fail, then it starts "fixing" my code so tests pass, or just deletes assertions so they "pass". Out of that frustration I built KeelTest - a VS Code extension that generates pytest tests and executes them, got hooked and decided to push this project forward... When tests fail, it tries to figure out why: - Generation error: Attemps to fix it automatically, then tries again -…
More work this month
the category →
Endless lofi beats composed live in your browser, over pixel-art nights in Paris, Tokyo, New York, Hong Kong, Sydney, San Francisco and more. Free, no sign-up.
Work · 25d ago · loficities.com
Smooth Recorder▲257Mac screen recordings that look edited when you hit stop
Work · 19d ago · smoothrecorder.com
Work · 13d ago · readrare.com
Source: Product Hunt launch ↗
Launched alongside, May 2026
the whole month →
Parallel agents, diff reviewer, and multi-model comparisons
Dev tools · May 2026 · kilo.ai
Hey HN, Henry here from Cactus. We open-sourced Needle, a 26M parameter function-calling (tool use) model. It runs at 6000 tok/s prefill and 1200 tok/s decode on consumer devices. We were always frustrated by the little effort made towards building agentic models that run on budget phones, so we conducted investigations that led to an observation: agentic experiences are built upon tool calling, and massive models are overkill for it. Tool calling is fundamentally retrieval-and-assembly (match query to tool name, extract argument values, emit JSON), not reasoning. Cross-attention…
Life & fun · May 2026 · github.com
🌱 Private, quiet space for thinking. Simple app for .md files. - zakirullin/files.md
Dev tools · May 2026 · github.com