DigUp for Customer Support

Download DigUp for Mac EmbeddingGemma 2 All roles

On-device flow Schematic: DigUp uses EmbeddingGemma 2 for Customer support local search

Original schematic — DigUp indexes local files with EmbeddingGemma 2 (llama.cpp).

Sourced snapshot (2026-10-15)

Fact	Value	Source
Model	EmbeddingGemma 2 · ~740M params · ~865 MB Q8 via llama.cpp	Google AI · DigUp README
Vector space	768-d shared multimodal space	Google AI · DigUp README
Mac / Win·Linux	0.6.1 · 0.7.0-beta.1	GitHub Releases
Stars / forks	~3,768 / ~254	GitHub API

Pain → DigUp workflow → tip

Pain	DigUp + EmbeddingGemma 2 workflow	Tip
Which runbook covers refund edge case?	Index support PDFs/md	Semantic + keyword
Call where user described error UI	Audio windows	Jump near description
Screenshot of rare settings panel	Image (+ Mac OCR)	Find by panel contents
Agent laptop privacy	Local-first DigUp	No DigUp telemetry of file contents (README)

Numbered checklist

Install DigUp; index Knowledge / Recordings allowed by policy.
Finish EmbeddingGemma 2 download (~865 MB).
Search customer phrases, not only internal IDs.
Verify before pasting into replies.
See zero-files guide if synced knowledge base is cloud-only.

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.