RepoMindRepoMind
RepoMindRepoMind

Understand your codebase without re-reading.

Find where things live. Learn how they work. With your AI agent.

A private, repo-aware AI that helps you understand your codebase - grounded in your actual files. No guessing.

  • Grounded answers only (with file + path citations)
  • Read-only GitHub access. No training on your code
  • Index once → ask questions anytime

Connect Index Ask

1

Connect GitHub

Authorize read-only access to your repository. We never write to your code.

2

Index a branch

We index your chosen branch once in the background - ready in minutes.

3

Ask questions

Chat with your repo and get answers grounded in your actual files, with citations, across all platforms.


What will you ask your codebase?


Answers you can verify

Q: Where is authentication handled?

Authentication is implemented in a middleware layer that validates JWTs on every protected route, with session management handled alongside.

Citations

  • src/auth/verifyToken.ts
  • src/middleware/authGuard.ts
  • src/auth/session.ts

Q: What triggers the background job?

A cron scheduler enqueues jobs via the task queue. Workers pick up tasks and run the processing pipeline defined in the jobs directory.

Citations

  • src/jobs/scheduler.ts
  • src/queue/worker.ts
  • src/jobs/processTask.ts

Q: How does billing work?

Stripe webhooks update subscription state in the database. The billing service exposes helpers consumed by the account settings page.

Citations

  • src/billing/stripeWebhook.ts
  • src/billing/subscriptionService.ts
  • src/api/account.ts

Q: How are permissions enforced?

A role-based access control layer checks user permissions before each protected action. Roles are defined in a central config and evaluated by a guard middleware.

Citations

  • src/auth/roles.ts
  • src/middleware/permissionGuard.ts
  • src/config/permissions.ts