Back to Signal Feed
CodeTracked since May 18, 2026

Add all_projects flag for cross-project MCP mem_search

This PR adds an optional `all_projects` boolean to `mem_search` so callers can request cross-project lookup, while keeping default behavior unchanged when the flag is omitted or set to false.

mem_searchall_projectsMCPhandleSearch

What Happened

  • This PR adds an optional `all_projects` boolean to `mem_search` so callers can request cross-project lookup, while keeping default behavior unchanged when the flag is omitted or set to false.
  • This PR adds an optional `all_projects` boolean to `mem_search` so callers can request cross-project lookup, while keeping default behavior unchanged when the flag is omitted or set to false.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced a concrete cross-project search path in the MCP layer by extending `mem_search` schema with `all_projects` and updating `handleSearch` to bypass project resolution when global search is requested.

Why Track This

Why It Matters

Developers and operators can now retrieve memory search hits across multiple projects with a single `mem_search` call, so cross-project workflows no longer require repeated per-project queries or manual project switching; this is especially useful for debugging and agent operations that span project boundaries. The change is implemented in MCP request parsing and handler logic, which now routes `all_projects: true` to project-agnostic lookup while preserving existing scoped behavior for `false`/unset, so the next signal to watch is whether global results stay bounded by intended access controls and whether large multi-project queries introduce response latency or result-volume surprises.

Impact

Developers and operators can now retrieve memory search hits across multiple projects with a single `mem_search` call, so cross-project workflows no longer require repeated per-project queries or manual project switching; this is especially useful for debugging and agent operations that span project boundaries. The change is implemented in MCP request parsing and handler logic, which now routes `all_projects: true` to project-agnostic lookup while preserving existing scoped behavior for `false`/unset, so the next signal to watch is whether global results stay bounded by intended access controls and whether large multi-project queries introduce response latency or result-volume surprises.

What To Watch Next

  • Watch whether mem_search becomes a repeated pattern.
  • Track follow-up changes around Agent Orchestration Platforms.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: cross_project_permission_leakage, default_scope_behavior_regression.
Open Topic TimelineOpen Technical EventOpen Original Sourcecross_project_permission_leakage / default_scope_behavior_regression / global_query_performance_regression / unexpected_large_result_sets

Supporting Evidence