The repo chat that starts with two keys

The startup idea

The problem

A new repository is a thousand files and no map of how auth works.

Who would pay for this?

Primary

A developer opening a repository they did not write.

Secondary

Someone who will run Java, Docker, and a GitHub OAuth app locally.

Early adopter

One repo, one cited answer, and both names on the page.

How could it make money?

Possible models. Nothing here is a claim about what GitSense charges.

• The readme prints no price and no license.
• Chat and embeddings spend an OpenAI key.
• The post does not name a seat.

What would the MVP look like?

1. GitHub sign-in and one synced repo.
2. One answer that cites a file.
3. The OpenAI key line.
4. The DevPilot title next to GitSense.

How to validate the idea

• Ask five people a question they can check against a file.
• If the citation is the wrong file, the index was the product problem.
• Do not ship a paste box the readme does not have.

How to differentiate

• The unit is a repository, not a chat with no files.
• Citations are the point.
• It runs on your machine, with your keys.
• Do not become a hosted code host.

Product that inspired this idea

Nitin's post says GitSense answers "how does auth work?" on a pasted GitHub repo, with code citations. Java, Spring Boot, pgvector, and RAG. He links lookwhatibuilt.live and the repository. The readme titles the same repo DevPilot. It indexes repositories and chats with them. You need Docker, Java 21, Node.js 20 or newer, an OpenAI key, and a GitHub OAuth app. Chat is GPT-4o-mini. Embeddings are text-embedding-3-small. Sign-in is GitHub OAuth, then a repository sync. The post says paste a repo. The readme starts with a login and two keys. The readme does not print a license. This page did not index a repository.

Posted by @nitinmehra_09. Watch the original launch. No separate product site is listed unless the post itself is the source.

• code
• rag

Related startup ideas

• A fast decision before the agent moves

  Look at a screen, offer one action, and wait for a click before a slower agent takes over.

• Sign-in that belongs to the agent

  Let an agent sign in as itself, with a human owner on the record, instead of borrowing a password.

• Steer an agent without cancelling its current work

  A way to add a message to an agent’s next turn while a subagent keeps going.

• The passage, not the whole page

  Give an agent the paragraphs that answer a question, with the surrounding lines, instead of a scraped page.

• A browser inside the coding agent’s terminal

  Open a real browser from the agent session so the agent can see the page it just changed.

• A checklist the coding agent cannot hide

  A plain-language checklist beside Claude Code that pauses for an OK, says when a step is stuck, and puts the limit and the cost on the same screen.

More developer tools ideas