Back to Signal Feed
CodeTracked since May 19, 2026

Wire runtime-signal sidecar updates into tool-mode curate/query execution

The PR adds runtime-signal sidecar write/read updates to tool-mode workflows by introducing bump helpers and invoking them from the daemon curate path, CLI curate-session path, and tool-mode read/write executor paths so topic activity metadata is recorded on use.

runtime-signal sidecarbumpSidecarOnCurateWritebumpSidecarOnQueryReadSearchExecutor

What Happened

  • The PR adds runtime-signal sidecar write/read updates to tool-mode workflows by introducing bump helpers and invoking them from the daemon curate path, CLI curate-session path, and tool-mode read/write executor paths so topic activity metadata is recorded on use.
  • The PR adds runtime-signal sidecar write/read updates to tool-mode workflows by introducing bump helpers and invoking them from the daemon curate path, CLI curate-session path, and tool-mode read/write executor paths so topic activity metadata is recorded on use.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Implemented helper-based bumping for runtime-signal sidecar metadata and integrated it into all currently relevant tool-mode curate and query execution paths, updating write-side `updateCount`/`recency` and read-side access tracking through existing store operations while keeping behavior safe (best-effort, no-throw on missing store).

Why Track This

Why It Matters

Tool-mode operators and users will stop seeing every topic look like a brand-new, never-accessed item after activity, so runtime signal-driven ranking can now prioritize active content and avoid repeatedly surfacing stale candidates. This is achieved by adding sidecar bumps on curated writes and query reads via existing `update/delete/list` calls (including `updateCount`, `recency`, and `accessCount`), which restores the practical input needed for candidate pruning and importance decay logic; watch for any remaining tool-mode entry points that still bypass these bumps and for deployments where the sidecar store is frequently absent so signal freshness updates may be silently skipped.

Impact

Tool-mode operators and users will stop seeing every topic look like a brand-new, never-accessed item after activity, so runtime signal-driven ranking can now prioritize active content and avoid repeatedly surfacing stale candidates. This is achieved by adding sidecar bumps on curated writes and query reads via existing `update/delete/list` calls (including `updateCount`, `recency`, and `accessCount`), which restores the practical input needed for candidate pruning and importance decay logic; watch for any remaining tool-mode entry points that still bypass these bumps and for deployments where the sidecar store is frequently absent so signal freshness updates may be silently skipped.

What To Watch Next

  • Watch whether runtime-signal sidecar becomes a repeated pattern.
  • Track follow-up changes around Agentic RAG.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: uncovered_tool_mode_execution_paths, silent_noop_when_sidecar_store_missing.
Open Topic TimelineOpen Technical EventOpen Original Sourceuncovered_tool_mode_execution_paths / silent_noop_when_sidecar_store_missing / incomplete_signal_coverage_in_followup_features

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

campfirein/byterover-cli PR #677: [Tool Mode] wire runtime-signal sidecar in tool-mode curate + query paths

Adds `bumpSidecarOnCurateWrite` and `bumpSidecarOnQueryRead` helpers and wires them into tool-mode daemon/CLI curate flows plus `SearchExecutor` and `QueryExecutor`, passing `runtimeSignalStore` through construction.