Summary
dewey_reload returns "Vault reloaded successfully" immediately, but dewey_graph_overview called right after shows 0 pages, 0 blocks, 0 links. The server appears to return before the vault re-scan is complete.
Reproduction
- Verify server has content:
dewey_health() → embeddingCount: 8127, sources with pageCount > 0
- Call reload:
dewey_reload() → "Vault reloaded successfully"
- Immediately call overview:
dewey_graph_overview() → {totalPages: 0, totalBlocks: 0, totalLinks: 0}
- Subsequent calls to
list_pages, search, get_page also return empty.
Expected Behavior
Either:
dewey_reload should be synchronous — return only after the re-scan is complete and pages are available, OR
dewey_reload should return a status indicating re-scan is in progress, and dewey_graph_overview / dewey_health should reflect the "reloading" state
Impact
- After a reload, the MCP server appears empty — all read tools return no results
- No way to tell when the reload has completed
- Agents calling reload to pick up new content get worse results than before the reload
Environment
- dewey version: dev
- Backend: obsidian (default)
- Server:
dewey serve --vault . via OpenCode MCP
Summary
dewey_reloadreturns "Vault reloaded successfully" immediately, butdewey_graph_overviewcalled right after shows 0 pages, 0 blocks, 0 links. The server appears to return before the vault re-scan is complete.Reproduction
list_pages,search,get_pagealso return empty.Expected Behavior
Either:
dewey_reloadshould be synchronous — return only after the re-scan is complete and pages are available, ORdewey_reloadshould return a status indicating re-scan is in progress, anddewey_graph_overview/dewey_healthshould reflect the "reloading" stateImpact
Environment
dewey serve --vault .via OpenCode MCP