openclaw - 💡(How to fix) Fix Memory wiki claim count includes cache rows without claim IDs

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

agent-digest.json reports claimCount: 186, but claims.jsonl currently contains 186 rows of which only 172 have an id; 14 rows appear to be cache rows without claim IDs.

Root Cause

Stable claim IDs are the useful unit for references, validation, and provenance. Mixing claim IDs with cache rows makes status output harder to trust.

RAW_BUFFERClick to expand / collapse

Summary

agent-digest.json reports claimCount: 186, but claims.jsonl currently contains 186 rows of which only 172 have an id; 14 rows appear to be cache rows without claim IDs.

Observed data

After openclaw wiki compile on OpenClaw 2026.5.18:

  • .openclaw-wiki/cache/agent-digest.json reports claimCount: 186
  • .openclaw-wiki/cache/claims.jsonl contains:
    • 186 total rows
    • 172 rows with id
    • 14 rows without id

The local validator warns about these rows as cache rows, not claim IDs.

Problem

A UI/status label like 186 claims is ambiguous if the number includes non-claim cache rows. Users may assume 186 stable claim IDs exist, while only 172 rows have claim IDs.

Expected behavior

Either:

  1. count only rows with claim IDs as claims, and expose cache rows separately, or
  2. relabel the metric as claim rows and optionally show 172 claim IDs + 14 cache rows.

Why this matters

Stable claim IDs are the useful unit for references, validation, and provenance. Mixing claim IDs with cache rows makes status output harder to trust.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Either:

  1. count only rows with claim IDs as claims, and expose cache rows separately, or
  2. relabel the metric as claim rows and optionally show 172 claim IDs + 14 cache rows.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Memory wiki claim count includes cache rows without claim IDs