Knowledge Graph Engine for Codebases

2 points by Shourya_55 8 hours ago

Hi HN , I built a knowledge graph engine for codebase that is accessible through API . Maintaining codebase , flagging and blocking the stale files along with 78% to 99.74% token savings are some of the main features .

I will be happy to talk about the graph schema, how we stay in sync with git, and overall philosophy of me on the product ?

visit trynovaya.com to use the product !

olejorgenb 7 hours ago

How is your tool different from the other bazillion similar tools of the same category?

  • Shourya_55 4 hours ago

    Most open source tools parse the code into graph even open source tools with 100k stars do the same AST parsing only.

    We record why each change was made, written back by the agents as they work, so the graph gets better the longer you use it . You can even check out the dashboard that is always in synch with Commits and updates from GitHub and Gitlab .

    We especially flag the stale files and code and derank them in internal . So, Graph stays in synch and updated .

    Token savings are in range of 78 to 99.74 percent .

    API as a source of distribution is much more scalable and comfortable as well especially if user is actively engaging with multiple different Agents Eg you use Claude code ,codex or grok build for a single repository .

juntz 7 hours ago

Why it is accessible through API? There are many local tools, what is the differences.

  • Shourya_55 5 hours ago

    API is more distributable and scalable overall in a sense that not many local tools can .

  • Shourya_55 5 hours ago

    novaya`s platform that is app.trynovaya.com is even highly visible dashboard and maintainable for users along with in constantly in synch with Github and Gitlab updates as well . codewiki API is gateway for our 12 to 13 set of tools that basically become bridge for a indexed codebase and your coding agent . Token savings also show 78 to 99.74 percent token savings on tasks . Mission is to the close the gap between fragmented database and other aspect of codebase and Agents we use .

  • Shourya_55 4 hours ago

    API as a source of distribution is much more scalable and comfortable as well especially if user is actively engaging with multiple different Agents Eg you use Claude code ,codex or grok build for a single repository .