UI Projects page shows 0 nodes and 0 edges while project-health and MCP report a populated graph

[mklusz]

Version

codebase-memory-mcp 0.10.2

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

ui

What happened, and what did you expect?

The Projects page displays an indexed project correctly, but the summary cards show:

• Projects: 1
• Nodes: 0
• Edges: 0

The project is healthy and its graph is populated. Both the MCP tools and the UI's per-project health endpoint report non-zero node and edge counts.

Expected behavior:

The Nodes and Edges summary cards on the Projects page should display the totals for indexed projects.

Actual behavior:

The summary cards show zero even though the project is listed and its graph database contains nodes and edges.

This appears to be a UI statistics aggregation problem rather than an indexing or graph-storage failure.

Reproduction

1. Install and run codebase-memory-mcp 0.10.2 with the embedded UI enabled.

2. Index a repository successfully.

3. Confirm through MCP:

   list_projects
   → project: MY_PROJECT
   → nodes: 52062
   → edges: 238991
   

4. Confirm its indexing status:

   index_status(project="MY_PROJECT")
   → status: ready
   → nodes: 52062
   → edges: 238991
   

5. Open:

   http://localhost:9749/?tab=stats
   

6. Observe that the Projects page lists the project but displays:

   Projects: 1
   Nodes: 0
   Edges: 0
   

7. Query the UI backend directly:

   Invoke-RestMethod `
     -Uri 'http://localhost:9749/api/project-health?name=MY_PROJECT'

   Result:

   {
     "status": "healthy",
     "nodes": 52062,
     "edges": 238991,
     "size_bytes": 157417472
   }

8. Query the endpoint apparently used for the page-level status:

   Invoke-RestMethod `
     -Uri 'http://localhost:9749/api/index-status'

   Result:

   []

Diagnostic summary

There is a discrepancy between the UI and MCP results:

Source	Nodes	Edges	Result
MCP list_projects	52,062	238,991	Correct
MCP index_status	52,062	238,991	Correct
/api/project-health?name=MY_PROJECT	52,062	238,991	Correct
Projects summary cards	0	0	Incorrect
/api/index-status	—	—	Returns []

The executable serving port 9749 is the same installed daemon:

codebase-memory-mcp.exe --cbm-daemon-internal

This rules out an empty project index. The likely problem is that the summary cards derive their totals from /api/index-status, which returns only active indexing jobs—or otherwise returns an empty array—instead of aggregating indexed-project statistics.

Logs

No indexing failure is reported.

The project status is `ready`, the project root exists, and the graph database is queryable through MCP.

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

1 indexed project / 52,062 nodes / 238,991 edges / Database size: 157,417,472 bytes

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[DeusData]

Thank you @mklusz. The code confirms the exact UI defect. StatsTab totals come from get_graph_schema; useProjects() calls that tool through POST /rpc, but rpc_is_allowed_for_ui() currently permits only list_projects and get_code_snippet. The schema request is therefore rejected, the UI catches it as schema: null, and both totals become zero.

/api/index-status is only the active indexing-job list, so [] there is expected and is not the source of the totals. Routed priority/high under the UI/install epic #396. Your endpoint comparison made this root cause unambiguous.