Repos, PR screenshots, stack traces in PDFs, meeting recordings — DigUp indexes meaning with EmbeddingGemma 2 on your machine. Opt in to code search with the code: prefix. Community guide — based on DigUp (MIT). Not affiliated; DigUp is not Google-official.
Enable code folders → query code: retry with backoff
Results open at the line in Cursor/VS Code/Zed
Screenshot of an error buried in Downloads
Index Screenshots + Downloads; search by what the UI showed
Mac OCR on screenshots helps exact strings too
Design PDF vs implementation drift
Index docs + code; compare meaning across modalities
Keep Spotlight for filenames; DigUp for meaning
Old Loom / mp4 of a weird bug
Video frame + audio windows (~30s) in shared 768-d space
Jump near the moment — README behavior
Numbered checklist
Install DigUp (Mac 0.6.1 or Win/Linux 0.7.0-beta.1) — first EmbeddingGemma 2 download ~865 MB.
Add project folders; enable code search in Settings for repos you want.
Wait for first-pass estimate; schedule overnight hours if fans bother you.
Query with code: for source; natural language for screenshots/PDFs/recordings.
If index stays empty on cloud sync folders, see the 0-files guide.
Why EmbeddingGemma 2 matters here
Google’s EmbeddingGemma 2 (~740M, unified 768-d multimodal space) is what DigUp runs via llama.cpp (~865 MB Q8 package). One query can rank images, PDF pages, audio windows, video frames, and optional code — see the local multimodal guide and model page. digup.run is not Google-official.
DigUp