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
Sense, code intelligence for AI agents
Your AI has your code's text, never its map. Fix that.
Your AI coding agent reads 19 files to answer "who calls this?" because it has your code's text but never its map. Sense indexes your repo once and serves your AI a symbol graph, blast radius, semantic search, and convention detection over MCP. It finishes the same task in half the tool calls and ~32% fewer tokens, with better correctness. One local Go binary. No API key, no cloud, no Python. Works with Claude Code, Cursor, Codex, and OpenCode. Free and open source.
I'm Luc, and I build with AI coding agents every day. One thing kept bugging me: every time Claude Code or Cursor needs to understand my codebase, it greps around, reads files one at a time, and pieces the structure back together from scratch. It works, but it's slow, it burns tokens, and sometimes it confidently invents a dependency that doesn't exist.
The reason is simple. Your AI has the text of your codebase. It never has the map: who calls what, what breaks if you change this, what patterns your project actually follows.
So I built Sense. It indexes your repo once and gives your AI four things over MCP: a symbol graph (callers, callees, tests, dead code), blast radius ("what breaks if I touch this?"), semantic code search, and convention detection (the patterns your codebase already follows, so AI-written code stops feeling foreign).
The part I care about most: it's not for you, it's for your AI. You install it once and forget it exists. No SaaS account, no API key, no cloud, no Python or Node runtime. One Go binary, a local SQLite index that never leaves your machine, and it works with anything that speaks MCP: Claude Code, Cursor, Codex CLI, OpenCode.
I didn't want to just claim "80% fewer tokens" like everyone does, so I built a reproducible benchmark across 6 real codebases (Discourse, Flask, Next.js, Axum, Gin, Javalin) with published methodology and raw transcripts. On a typical structural task: 19 tool calls drop to ~10, tokens drop ~32%, same correctness. Sense doesn't make the model smarter. It stops the model from wasting effort.
It's free and open source (MIT). Setup is one download and one `sense scan`.
I'd genuinely love your feedback, especially if you point it at a gnarly codebase and your AI does something noticeably better (or doesn't). I'll be here all day answering everything. Thank you for taking a look 🙏
About Sense, code intelligence for AI agents on Product Hunt
“Your AI has your code's text, never its map. Fix that.”
Sense, code intelligence for AI agents was submitted on Product Hunt and earned 13 upvotes and 1 comments, placing #44 on the daily leaderboard. Your AI coding agent reads 19 files to answer "who calls this?" because it has your code's text but never its map. Sense indexes your repo once and serves your AI a symbol graph, blast radius, semantic search, and convention detection over MCP. It finishes the same task in half the tool calls and ~32% fewer tokens, with better correctness. One local Go binary. No API key, no cloud, no Python. Works with Claude Code, Cursor, Codex, and OpenCode. Free and open source.
On the analytics side, Sense, code intelligence for AI agents competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Sense, code intelligence for AI agents performed against the three products that launched closest to it on the same day.
Who hunted Sense, code intelligence for AI agents?
Sense, code intelligence for AI agents was hunted by Luc B. Perussault Diallo. 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 Sense, code intelligence for AI agents including community comment highlights and product details, visit the product overview.
Luc B. Perussault Diallo
Hey Product Hunters 👋
I'm Luc, and I build with AI coding agents every day. One thing kept bugging me: every time Claude Code or Cursor needs to understand my codebase, it greps around, reads files one at a time, and pieces the structure back together from scratch. It works, but it's slow, it burns tokens, and sometimes it confidently invents a dependency that doesn't exist.
The reason is simple. Your AI has the text of your codebase. It never has the map: who calls what, what breaks if you change this, what patterns your project actually follows.
So I built Sense. It indexes your repo once and gives your AI four things over MCP: a symbol graph (callers, callees, tests, dead code), blast radius ("what breaks if I touch this?"), semantic code search, and convention detection (the patterns your codebase already follows, so AI-written code stops feeling foreign).
The part I care about most: it's not for you, it's for your AI. You install it once and forget it exists. No SaaS account, no API key, no cloud, no Python or Node runtime. One Go binary, a local SQLite index that never leaves your machine, and it works with anything that speaks MCP: Claude Code, Cursor, Codex CLI, OpenCode.
I didn't want to just claim "80% fewer tokens" like everyone does, so I built a reproducible benchmark across 6 real codebases (Discourse, Flask, Next.js, Axum, Gin, Javalin) with published methodology and raw transcripts. On a typical structural task: 19 tool calls drop to ~10, tokens drop ~32%, same correctness. Sense doesn't make the model smarter. It stops the model from wasting effort.
It's free and open source (MIT). Setup is one download and one `sense scan`.
I'd genuinely love your feedback, especially if you point it at a gnarly codebase and your AI does something noticeably better (or doesn't). I'll be here all day answering everything. Thank you for taking a look 🙏