Back to Signal Feed
CodeTracked since May 19, 2026

Viewer Memories search now routes CJK and longer queries to backend BM25+vector

The PR replaces client-side-only `String.includes()` filtering in the Viewer Memories tab with conditional backend search routing so CJK and qualifying Latin queries are handled by `/agentmemory/search` (BM25+vector), improving match behavior for international text input.

AgentMemory Viewer Memoriesbackend search /agentmemory/searchBM25vector search

What Happened

  • The PR replaces client-side-only `String.includes()` filtering in the Viewer Memories tab with conditional backend search routing so CJK and qualifying Latin queries are handled by `/agentmemory/search` (BM25+vector), improving match behavior for international text input.
  • The PR replaces client-side-only `String.includes()` filtering in the Viewer Memories tab with conditional backend search routing so CJK and qualifying Latin queries are handled by `/agentmemory/search` (BM25+vector), improving match behavior for international text input.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Added query-routing logic that detects CJK characters and Latin query length, dispatches eligible queries to backend BM25+vector search, preserves local filtering as a graceful fallback, and uses compositionstart/compositionend guards to prevent IME text composition from being interrupted during input.

Why Track This

Why It Matters

Users typing Chinese/Japanese/Korean in the Viewer Memories search will get more consistent and useful results than before because search no longer depends only on naive local string matching, and operators gain explicit visibility into whether a query used backend or local mode; watch for backend response latency, fallback-result quality when backend calls fail, and any rise in wrong-mode routing from CJK detection edge cases.

Impact

Users typing Chinese/Japanese/Korean in the Viewer Memories search will get more consistent and useful results than before because search no longer depends only on naive local string matching, and operators gain explicit visibility into whether a query used backend or local mode; watch for backend response latency, fallback-result quality when backend calls fail, and any rise in wrong-mode routing from CJK detection edge cases.

What To Watch Next

  • Watch whether AgentMemory Viewer Memories becomes a repeated pattern.
  • Track follow-up changes around Hybrid Search.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: backend_search_latency_regression, backend_unavailable_fallback_behavior.
Open Topic TimelineOpen Technical EventOpen Original Sourcebackend_search_latency_regression / backend_unavailable_fallback_behavior / cjk_detection_false_positives / search_mode_indicator_mismatch / search_result_quality_drift_on_short_queries

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

rohitg00/agentmemory PR #536: feat(viewer): add backend-powered CJK search for Memories tab

Route CJK and long Latin queries from local filtering to `/agentmemory/search`, add IME-safe input handling, and show whether Backend (BM25+vector) or Local filter is active.