On: Show HN: Mantic.sh – A structural code search engine for AI agents

[handfuloflight]

Do you want to objectively state your criticisms instead of this handwaving dismissal?

[usefulposter → handfuloflight]

What kind of agent workflow is it called when you post a hastily vibecoded Show HN, feed glaringly obvious user feedback reports one by one into the LLM, wait for the LLM to course-correct (YOU'RE ABSOLUTELY RIGHT!), then push a coincidentally timed "bugfix" while informing the user that their feedback was addressed by said bugfix?

[handfuloflight → usefulposter]

So your complaint is what exactly? How quickly the developer is iterating and responding to market feedback?

[koakuma-chan → handfuloflight]

Where you do think all those "weights" come from? They are all hallucinated. The rest of the code is too.

[marcoaapfortes → koakuma-chan]

I think there’s a misunderstanding of mantic.sh architecture...

The “weights” as you described in Mantic.sh are not neural network weights. They’re deterministic ranking heuristics, similar to what IDE file pickers use. For example, extension weights, path depth penalties, and filename matches. You can see them directly in brain-scorer.ts (EXTENSION_WEIGHTS).

const EXTENSION_WEIGHTS: Record<string, number> = { '.ts': 20, '.tsx': 20, '.js': 15, '.jsx': 15, '.rs': 20, '.go': 20, '.py': 15, '.prisma': 15, '.graphql': 10, '.css': 5, '.json': 5, '.md': 2 };

There’s no LLM involved in the actual search or scoring, it’s a static heuristic engine, not a learned model.

I'd love to have the implementation critiqued on its merits!