An AI-powered tool that lets you chat with any GitHub repository. Paste a repo link, and the assistant scrapes, indexes, and embeds the entire codebase — then answers your questions about it, returns the most relevant files, and even summarizes your team meetings.
- Paste any public GitHub repo URL
- The repo is loaded via LangChain, summarized, and embedded using pgvector
- Ask anything about the codebase — architecture, logic, specific files
- Every response includes the 5 most relevant files to your query
- Invite multiple collaborators to the same repo workspace
- Full invite system — share access with your team
- Upload meeting recordings directly to the platform
- Powered by AssemblyAI — get AI-generated summaries with chapters
- Keep your repo context and meeting notes in one place
- AI usage is powered by a token system
- Buy tokens directly in the app
- Full Stripe integration — test payments implemented end to end
| Layer | Technology |
|---|---|
| Framework | Next.js (T3 Stack) |
| Language | TypeScript |
| Auth | NextAuth.js |
| ORM | Prisma |
| Database | PostgreSQL (Neon) |
| Vector Store | pgvector |
| AI / RAG | LangChain |
| Meeting AI | AssemblyAI |
| Payments | Stripe |
| Styling | Tailwind CSS + ShadCN UI |
- Node.js 18+
- PostgreSQL database with pgvector extension enabled
- API keys for your LLM provider, AssemblyAI, and Stripe
-
Clone the repo
git clone https://github.com/dhruvv7115/github-ai-assistant cd github-ai-assistant -
Install dependencies
npm install
-
Configure environment variables
cp .env.example .env
Fill in all required values in
.env. -
Set up the database
# Enable pgvector in your Postgres instance first # Then run: npx prisma db push
-
Start the dev server
npm run dev
See .env.example for the full list of required environment variables including database, LLM, AssemblyAI, and Stripe credentials.
- User submits a GitHub repo URL
- LangChain crawls and loads all files from the repo
- Files are chunked, embedded, and stored in pgvector
- A summary of the repo is generated and saved
- On each query, relevant chunks are retrieved via similarity search
- The LLM answers using the retrieved context and returns the top 5 related files
See the T3 deployment guides for detailed instructions.