Management UI only displays the first 50 projects and ignores list_projects.has_more

[lvxinrong]

Version

codebase-memory-mcp 0.10.8

Platform

macOS (Apple Silicon)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

The Codebase Memory management UI only displays the first 50 indexed projects.

I currently have 86 indexed projects. The list_projects API/CLI correctly returns the following pagination metadata:

• total: 86
• offset: 0
• limit: 50
• returned: 50
• has_more: true

However, the management UI only requests and displays the first page. It does not provide pagination, a “Load more” action, or automatically request the remaining pages.

As a result, projects after the first 50 are indexed and accessible through the CLI, but they cannot be found in the management UI.

This can be verified by requesting the second page:

codebase-memory-mcp cli --json list_projects --offset 50 --limit 50 --include-details true

Expected behavior:

The management UI should either:

1. Support pagination;
2. Provide a “Load more” action; or
3. Automatically fetch subsequent pages while has_more is true.

Environment:

• codebase-memory-mcp version: 0.10.8
• Total indexed projects: 86
• Management UI port: 9749

Reproduction

The Codebase Memory management UI only displays the first 50 indexed projects.

I currently have 86 indexed projects. The list_projects API/CLI correctly returns the following pagination metadata:

• total: 86
• offset: 0
• limit: 50
• returned: 50
• has_more: true

However, the management UI only requests and displays the first page. It does not provide pagination, a “Load more” action, or automatically request the remaining pages.

As a result, projects after the first 50 are indexed and accessible through the CLI, but they cannot be found in the management UI.

This can be verified by requesting the second page:

codebase-memory-mcp cli --json list_projects --offset 50 --limit 50 --include-details true

Expected behavior:

The management UI should either:

1. Support pagination;
2. Provide a “Load more” action; or
3. Automatically fetch subsequent pages while has_more is true.

Environment:

• codebase-memory-mcp version: 0.10.8
• Total indexed projects: 86
• Management UI port: 9749

Logs

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

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 for the precise report and for including the second-page control. I checked current main: graph-ui/src/hooks/useProjects.ts calls list_projects once without an offset or limit and consumes only result.projects. It does not inspect has_more or request another page, so the 50-project ceiling is grounded in the current UI path.

I have removed the incorrect Windows label and marked this as a high-priority graph UI bug. The fix needs a bounded pagination strategy that does not create an unbounded burst of per-project schema requests. Thank you for identifying the API and UI behavior separately.

[lvxinrong]

Thanks for confirming this and for prioritizing it. The concern about avoiding an unbounded burst of per-project schema requests makes sense. A lazy-loading approach—paginating lightweight project metadata first and fetching schema/details only when a project is opened—would work well for my use case.
I encountered this while dogfooding ArchScope, an evidence-driven architecture reconnaissance plugin I’m currently building for DeepSeek Harness. It uses codebase-memory-mcp as its primary code-intelligence layer to discover and analyze complex multi-repository systems. In my current workspace that means 86 repositories, so bounded pagination and predictable behavior at this scale are especially important.
I’d be happy to test the eventual fix against this workload and share any findings. More broadly, ArchScope is becoming a fairly demanding downstream integration for codebase-memory-mcp, so I’ll keep reporting issues and feedback as I exercise more of the API.

[DeusData]

Closing as superseded together with #1819, which fixed exactly this and was approved on merit: the graph UI is being reimplemented from the ground up, and the current projects view will be replaced rather than patched. Honouring list_projects.has_more is a requirement for the new one, with this issue as the reference. Thank you for the clear report.