Your code's got something to say!
A few commands that make your repo talk back
Start a conversational session with your codebase. Ask questions in natural language and get instant answers with relevant code snippets. Understanding complex logic, finding implementations, or exploring unfamiliar code becomes as easy as having a conversation. The REPL stays open until you're done, maintaining full context across multiple questions.
Generate intelligent context files for all major AI coding assistants in one command. Creates .cursorrules, .windsurfrules, .clinerules, and more with deep architectural insights about your project. Your AI tools will understand your codebase structure, patterns, dependencies, and design decisions without you having to explain anything.
Keep your AI assistants synchronized with your codebase in real-time. Automatically detects file changes and regenerates context files so Cursor, Windsurf, and other tools always have up-to-date knowledge of your project. Run it in the background during development and never worry about stale context again.
See all available commands, flags, and options at a glance. Get quick documentation on usage patterns, example queries, and configuration options without leaving your terminal. Perfect for discovering advanced features or refreshing your memory on command syntax when you need it.
Everything you need to know about QuackStack
No! QuackStack generates embeddings entirely locally on your machine. Your code never leaves your computer during indexing. Only your natural language queries (like 'where is auth handled?') and small relevant code snippets are sent to the AI provider for generating conversational answers.
You need: (1) A PostgreSQL database - free options like Neon or Supabase work great, and (2) ONE API key for conversational answers (OpenAI, Claude, Gemini, DeepSeek, or Mistral). Gemini has a free tier! Embeddings are generated locally with no API calls.
First-time indexing depends on your codebase size. A typical project (1000-5000 files) takes 2-5 minutes. After that, only changed files are re-indexed, making updates nearly instant. Large monorepos may take 10-15 minutes initially.
Copilot and Cursor suggest code based on immediate context. QuackStack gives them FULL codebase understanding. It's complementary - QuackStack generates the .cursorrules file that makes Cursor smarter about YOUR specific project, patterns, and architecture.
Yes! Each project gets its own isolated namespace in the database (based on directory name). Just run 'quack' in any project folder and it automatically manages separate indexes. Switch between projects freely without conflicts.
QuackStack itself is 100% free and open source. Your only costs are: (1) AI provider API usage for conversational answers (Gemini has a free tier!), and (2) database hosting (Neon/Supabase offer free tiers). Most developers spend $0-5/month depending on usage.