Tried sponsors/abhigyanpatwari Today: GitNexus Is a Serious Codebase Map
GitNexus is gaining attention fast: +202 stars today is a strong signal for a tool that solves a painful developer problem—understanding an unfamiliar repository without manually opening hundreds of files.
The idea is refreshingly simple. Drop in a GitHub, GitLab, Azure, local repository, or ZIP file, and GitNexus builds a client-side knowledge graph directly in your browser. You get relationships between files, symbols, imports, and modules, plus a built-in Graph RAG Agent for asking codebase-level questions.
The important part: it is a zero-server code intelligence engine. Your repository can stay local instead of being uploaded to a hosted indexing service. That makes it useful for private projects, incident debugging, dependency tracing, and onboarding.
For custom agent workflows, route the AI calls through an OpenAI-compatible gateway. For example:
export OPENAI_BASE_URL="https://b-lost.com/v1"
export OPENAI_API_KEY="$B_LOST_API_KEY"
curl "$OPENAI_BASE_URL/chat/completions" \
-H "Authorization: Bearer $OPENAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "claude-fable-5",
"messages": [
{
"role": "user",
"content": "Explain the dependency path from the auth module to database writes."
}
]
}'
If your client supports Anthropic’s native API, B-Lost also exposes /v1/messages with prompt caching. That is particularly relevant for Graph RAG: repository instructions, schemas, and repeated code context can be cached, reducing latency and token cost on follow-up questions. Cache hits receive a 90% discount according to the relay documentation.
B-Lost lists 20% off official pricing, plus a 100% first-deposit bonus with a $10 minimum. Still, the real test is reliability: watch for 429s, context overflow, and whether your gateway preserves long structured prompts.
GitNexus is worth trying if “where is this symbol used?” has become your daily debugging routine.
Top comments (0)