Skip to content

Local Assistant and GraphRag built-in - #209

Closed
gsaaad wants to merge 5 commits into
ARahim3:mainfrom
gsaaad:pr/5-parallel-index
Closed

gsaaad wants to merge 5 commits into
ARahim3:mainfrom
gsaaad:pr/5-parallel-index

Conversation

@gsaaad

@gsaaad gsaaad commented Nov 13, 2026

Copy link
Copy Markdown

Issue: # 208

What changed and why:
This adds a fully local assistant to DigUp. It uses a small language model (Qwen2.5-3B or 1.5B via llama.cpp, set up for an 8-core, 12 GB RAM CPU) behind a new digup chat-service helper and an "Ask AI" pane in the app. Answers are grounded by a deterministic GraphRAG step: indexing stores identifiers, symbols and file references in a new SQLite edges table (created with IF NOT EXISTS, so the schema version is unchanged), and Searcher.retrieveGraphContext follows them one or two hops to pull in related files without any LLM indexing cost. Cache-Augmented Generation saves the model's state for pinned files to disk, so follow-up questions skip re-reading the context on CPU, and an optional JSONL logger with a secret scrubber lets users export SFT/DPO data and hot-load a LoRA adapter. Everything stays on the user's machine and the model download is optional, so first-run indexing is unaffected.

Tests run: cargo test in shell/src-tauri: 18 tests for this feature passed (the Rust dataset, GraphRAG and CAG tests). swift test was not run (no Swift toolchain on my Windows machine), so GraphRAGTests.swift is untested.

If search results change: base search is unchanged; GraphRAG only adds context for chat. No before/after evals.

@gsaaad gsaaad closed this Nov 13, 2026
@gsaaad

gsaaad commented Nov 13, 2026

Copy link
Copy Markdown
Author

wrong PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant