khoj-ai/khoj

Prefer this fork only if its specific UI/client/deployment changes matter more than staying current. For most adopters, upstream is the safer choice because this fork is old, substantially diverged, and likely missing newer fixes and features.

Choose this fork only if its specific GitHub, UI, or workflow changes match your needs. If you want the newest Khoj features or low-maintenance adoption, upstream is the safer choice.

Prefer upstream unless you specifically want an untouched snapshot; this fork adds no visible features and is already behind current upstream.

Prefer upstream unless you specifically need this older snapshot. The fork adds no visible functionality, while it lags upstream by 127 commits, so adopters inherit upstream features only up to that point and miss recent fixes and releases.

Choose this fork if Azure/custom OpenAI backend support and local workflow tweaks matter more than staying current. Avoid it if you need active upstream maintenance, recent bug fixes, or low-effort upgrades.

Choose this fork only if you want its customized web/Obsidian behavior and are prepared to maintain a materially diverged codebase. If you want the latest upstream fixes and lowest operational risk, upstream is the safer default.

Choose this fork only if you specifically want a customized, self-maintained Khoj variant and are prepared to manage drift from upstream. If you want current upstream features, bugfixes, and lower maintenance cost, upstream is the safer choice.

Prefer this fork only if you need its custom behavior and are prepared to maintain a 597-commit-ahead, 247-commit-behind divergence. For most adopters who want a current, low-risk Khoj deployment, upstream is the safer choice.

Choose this fork only if you want a customized, self-maintained Khoj variant and are willing to absorb significant upgrade and validation work. If you want the most reliable path to current features and fixes, upstream is the better default.