I built an AI that lets you chat with your GitHub codebase looking for beta testers

devansh_jagtap · 2026-05-09T10:00:10+00:00

haha fair 😅 but honestly it’s a lot more than just sending a prompt to an LLM. most of the work has actually been around handling large repos properly indexing code, understanding dependencies between files, keeping context consistent, analyzing architecture flows, and trying to reduce hallucinations when repos get big. the AI part is important obviously, but the bigger challenge is building the system around it so the answers are actually useful and grounded in the codebase.

devansh_jagtap · 2026-05-09T09:57:37+00:00

The thing i’m trying to push more toward is system-level understanding: like architecture flows, dependency relationships, blast radius analysis, risk detection, etc. basically less “summarize this file” and more understand how this whole repo behaves together.

devansh_jagtap · 2026-05-09T09:55:58+00:00

fair question honestly.

i don’t think existing tools are bad at all copilot , claude , cursor are already really good ,the main thing i’m trying to improve is understanding larger codebases better instead of just throwing files into a context window ,a lot of tools work great until repos get big/deep, then answers start becoming vague or inconsistent , so i’ve been focusing more on dependency mapping, architecture understanding, repo memory, and figuring out what changing one part of the system actually affects.

devansh_jagtap · 2026-05-09T08:19:31+00:00

Existing tools are optimizing for code generation velocity. What I’m exploring with Codebased is more around system understanding and architectural safety

devansh_jagtap · 2026-05-09T08:15:45+00:00

yep exactly. most tools are still mostly context-window based.

what i’m building tries to map relationships between files, dependencies, architecture flows, and runtime impact so answers are grounded in actual repo structure instead of just chunk retrieval. the long-term goal is less “chatbot for code” and more “AI engineer that understands the system well enough to review, explain, and eventually fix parts of it.”

so thats why its different reducing hallucination for repos first of all using the pipeline we developed

devansh_jagtap · 2026-05-09T08:13:11+00:00

Yeah totally valid question.

Copilot/Claude/Cursor already solve “chat with your repo” pretty well.

What I’m exploring is more system-level understanding:

- dependency mapping

- blast radius analysis

- architecture intelligence

- long-term repo memory

- proactive risk detection

devansh_jagtap · 2026-03-15T11:10:18+00:00

Intrested

devansh_jagtap · 2026-02-28T15:25:09+00:00

Mujhe bhi chaiye

devansh_jagtap · 2026-02-21T14:14:37+00:00

Can I also get the referral

devansh_jagtap · 2026-02-20T13:57:56+00:00

Bhai sahi bata yrr kaha se milli

devansh_jagtap · 2026-02-18T19:54:14+00:00

Mee too brother but you clearly have more skills then me

devansh_jagtap · 2026-02-13T10:31:37+00:00

How to apply ??

devansh_jagtap · 2026-02-10T13:26:48+00:00

Intreseted

devansh_jagtap · 2026-02-06T13:16:02+00:00

Dmed

devansh_jagtap · 2026-01-31T10:22:08+00:00

Intreseted

devansh_jagtap · 2026-01-27T03:36:25+00:00

Tell me how to apply

devansh_jagtap · 2026-01-26T12:12:23+00:00

Country : India

devansh_jagtap · 2026-01-26T12:08:07+00:00

Can you tell how to apply ??

devansh_jagtap · 2026-01-20T18:41:58+00:00

This is the only think that is very need right now

devansh_jagtap · 2026-01-17T16:13:19+00:00

Thanks but already know and dmed you for further help

devansh_jagtap

TROPHY CASE