khoj

khoj-ai/khoj

Your AI second brain. Self-hostable. Get answers from the web or your docs. Build custom agents, schedule automations, do deep research. Turn any online or local LLM into your personal, autonomous AI (gpt, claude, gemini, llama, qwen, mistral). Get started - free.

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
Aug 2, 2026
61 days ago
Ship score
35/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 36,555 → 37,532 (Aug 18 – Sep 29, 2026)
+692 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
37.6K
Forks
2.5K
Open issues
161
Watchers
181
Primary language
Python
Created
Aug 16, 2021
Owner
khoj-ai · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 110 startups in the directory ship primarily in Python.

Topics

#agent#ai#assistant#chat#chatgpt#emacs#image-generation#llama3#llamacpp#llm#obsidian#obsidian-md#offline-llm#productivity#rag#research#self-hosted#semantic-search#stt#whatsapp-ai

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 95%, hosted offering 54%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 2026-08-02This is the badge for khoj-ai/khoj, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/khoj-ai/khoj.svg)](https://ossean.com/khoj-ai/khoj)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.