Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ChatLab/ChatLab
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: ChatLab/ChatLab
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: dev
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 13 files changed
  • 2 contributors

Commits on Jun 11, 2026

  1. fix(ai): fix stale overview and analysis caches after incremental import

    Overview cache had no self-invalidation: once written it would return
    stale lastMessageTs forever if the postImportHook failed silently.
    Analysis query cache (17 chart/stats queries) was never cleared on
    import, so charts showed stale data until the user triggered a manual
    invalidate.
    
    Add MAX(message.id) fingerprint to OverviewCache and introduce
    getValidatedOverviewCache(), which recomputes automatically when new
    messages are inserted. Update resolveOverview() in the Electron worker
    to use this instead of bare getCache().
    
    In both postImportHooks (incrementalImport, streamImport) also call
    deleteSessionCache against the query cache directory so chart data is
    fresh after every import.
    
    Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
    hellodigua and claude committed Jun 11, 2026
    Configuration menu
    Copy the full SHA
    5077cb4 View commit details
    Browse the repository at this point in the history
  2. fix(ai): clarify last_message_time is data coverage end, not group ac…

    …tivity time
    
    AI was treating last_message_time as "when the group last had activity"
    and drawing inferences like "the group has been quiet for two months,
    maybe send a message to revive it." In reality, the timestamp only
    reflects the end of imported data — the user may simply not have
    imported newer records yet.
    
    Add an inline parenthetical to the last_message_time field in all four
    locale templates, and append a dedicated usage rule in
    dataSnapshotUsageRules (zh-CN, en-US, zh-TW, ja-JP) explicitly
    prohibiting inferences about group inactivity based on this value.
    Also add the same note to formatDataSnapshotForPlanner's notes section
    in data-snapshot.ts.
    
    Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
    hellodigua and claude committed Jun 11, 2026
    Configuration menu
    Copy the full SHA
    e464c71 View commit details
    Browse the repository at this point in the history
Loading