Conversation
…observability Curation was effectively never firing on typical agentic sessions because afterTurns defaulted to 10 user messages — most sessions have 3-5. The counter also resets on every OpenCode restart. Additionally, the module-level lastCuratedAt timestamp leaked across sessions, causing curation on session B to skip messages created before session A's curation. - Lower afterTurns default from 10 to 3 - Make lastCuratedAt a per-session Map instead of a shared number - Add diagnostic logging: curation skip reason, activeSessions gate, empty export detection, message.updated fetch failures
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
afterTurnsdefault from 10 to 3 — curation was effectively never firing on typical agentic sessions (3-5 user messages), especially since the counter resets on every OpenCode restartlastCuratedAtper-session — the shared module-level timestamp caused cross-session leaking where curation on session A would advance the timestamp past session B's messagesactiveSessionsgate, empty export detection, andmessage.updatedfetch failures (was a silent emptycatch {})