🇬🇧 English • 🇷🇺 Русский • 🇨🇳 中文
Frequently Asked Questions. Based on real development and operations experience.
llama.cpp — это встроенный провайдер для эмбеддингов и реранкинга,
который автоматически устанавливается через install.py. Он скачивает
GGUF-модели (bge-m3 Q4_K_M 417 MB и bge-reranker-v2-m3 Q4_K_M 418 MB)
и запускает llama-server.exe локально. Не требует внешних сервисов
вроде LM Studio. Потребляет 227 MB RAM вместо 1200 MB — в 5.3× меньше.
Cause: Zed wasn't restarted. window: reload is not enough.
Solution: File → Quit → reopen the project.
Logs: %LOCALAPPDATA%\Zed\extensions\mscodebase-intelligence\.codebase_indices\logs\
Cause: The installer copied files to the extension, but MCP server is already running with the old code. Solution: File → Quit → reopen the project. Only a full restart restarts MCP.
Solution: Run intel_trigger_reindex() in Agent Panel. Wait 1-5 minutes.
Track progress via intel_get_job_status(<job_id>).
Causes:
- Empty index → see above
- Embedder not running →
intel_get_runtime_status()shows "offline" - Wrong project → check
get_index_status()output
Cause: Project resolution via SQLite — if multiple projects are open in Zed,
it may pick the wrong one. Especially on Windows where ZED_WORKTREE_ROOT is unset.
Solution: Close all Zed windows, open only the needed project.
Details: investigations/ACTIVE_WORKSPACE_RESOLUTION.md
If from an older version: Fixed. After commit 05de324 (2026-07-05)
all 50 tools output readable Markdown.
Solution: Run python install.py and restart Zed.
Cause: Zed on Windows cannot register custom LSP names.
Requires a Rust/WASM adapter. settings.json is powerless.
Status: WONTFIX. MCP server works fully without LSP.
Details: investigations/LSP_WONTFIX.md
Solution: Click "Trust and Continue". Check "Trust all projects in..." Otherwise LSP won't start, MCP won't see the project.
Solution: File → Quit → reopen the project only. Auto-restart is not supported by Zed on Windows.
Cause: resolve_project_root() couldn't find the project via SQLite.
Solution: Make sure the project is open in Zed. Check LocalAPPDATA/Zed/db/0-stable/db.sqlite.
If empty — Restricted Mode may be blocking it.
Causes:
- llama.cpp or embedder not ready (check
intel_get_runtime_status()) - Index not optimized (run
intel_trigger_reindex()) limittoo high insearch_code(recommended 6-10)
Solution: Check the embedder status. If using llama.cpp:
curl http://127.0.0.1:8080/health. If using LM Studio:
Make sure an embedding model (e.g. BAAI/bge-m3) is loaded.
Normal: LanceDB uses mmap files. Windows keeps them in memory. Solution: Restart MCP to free memory (File → Quit).
Cause: PYTHONPATH doesn't point to the extension directory.
Solution: Run python install.py — it sets the correct PYTHONPATH.
Cause: Self-indexing guard — MCP protects itself from indexing its own sources. Solution: Open a different project in Zed (not the extension).
Was in older versions (before 2026-07-05): Deadlock in DebounceBatch.
Fixed. If still happening — check version (debug_runtime_passport → BUILD_ID).
Solution: File → Quit.
| Document | Description |
|---|---|
INSTALL.md |
User installation guide |
ARCHITECTURE.md |
Project architecture (10 layers) |
ZED_WINDOWS_QUIRKS.md |
Windows specifics |
HANDFOFF.md |
Development experience, architecture decisions |