Repository navigation
Unknown-project error lists only cloud projects and omits local ones #1809
Description
Found during live testing of main at 0276799 (2026-10-22).
Problem
With cloud credentials present, an unknown project name on write_note or recent_activity reports only cloud projects:
Project 'no-such-project' was not found in indexed cloud workspaces. Available projects:
basic-memory-7020de4e.../test-visibility, ..., demo/main, my-team-2/main.
None of the 9 local projects (main, basic-memory-testing-*) appear. A local-only user gets a list they cannot use. The call also takes 0.7-1.2s because it goes through cloud discovery.
delete_project handles the same case correctly: Project 'bm-live-does-not-exist' not found. Available projects: main, basic-memory-testing-20261008-1228, ...
Repro
- Local mode with an OAuth token or
BASIC_MEMORY_API_KEYset. recent_activity(project="no-such-project")orwrite_note(project="no-such-project", directory="x", title="x", content="x").
Source
src/basic_memory/mcp/workspace_project_index.py:408
Expected
The error lists local projects, plus cloud projects when cloud is in use. It does not say "indexed cloud workspaces" for a lookup that started from local config.
Activity
claude commentedon Oct 23, 2026
Claude finished @phernandez's task in 17s —— View job
Triage
bug,cloud)write_note,recent_activity) on the cloud project-routing pathsrc/basic_memory/mcp/workspace_project_index.py(around line 408). It is built fromindex.entries, which only holds cloud workspace projects, and the text says "indexed cloud workspaces". The fix is probably to catchWorkspaceProjectLookupMissat the caller. The caller already knows the local config, so it can merge local project names into the "Available projects" list and drop the cloud-only wording when the lookup started from local config.delete_projectalready does this correctly and can serve as a reference.I have not made any code changes, as this was triage only.