You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support a turn-level cutoff for Hermes transcript ingestion
#8174
Moved from #5118, opened by @mikez93 on 2026-09-15. Feature requests now live in Discussions > Ideas.
Feature request
For a multi-session Hermes SQLite store, gbrain transcripts ingest --since <time> has documented session-level semantics: only sessions newer than the cutoff are selected. The ingest core compares the cutoff with the session's last message timestamp. If a long-lived session has one turn after the cutoff, the whole session is selected and every earlier turn is rendered and imported.
That behavior matches the current help text, but it leaves no way to perform a cutover that admits only messages after a boundary. Please add an explicit opt-in turn/message cutoff while preserving the existing --since behavior for compatibility.
Synthetic reproduction
Create a synthetic Hermes store with one session and three messages:
The command shape is accepted by the current CLI. Source inspection shows that the session is eligible because its last message is newer than the cutoff, after which the untrimmed session is passed to redaction and rendering. This illustrates a missing opt-in capability, not a violation of the current --since contract.
Expected behavior
Keep --since session-level unless a deliberate breaking change is separately chosen.
Add an explicit option such as --messages-since <time> or --turns-since <time> that trims messages before redaction and rendering.
Under the new option, count a session with no remaining messages as filtered.
Include the new cutoff and its semantics in the --since last checkpoint fingerprint or define a separate checkpoint scope.
Ensure an idempotent rerun does not duplicate or restore pre-cutoff turns.
Suggested tests
existing --since behavior remains session-level
a resumed session with the new option retains only post-cutoff messages
a session entirely before the cutoff is filtered
an unchanged rerun is idempotent
the new option composes with --since last without checkpoint cross-talk
session timestamps that cannot be parsed do not advance the watermark
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Moved from #5118, opened by @mikez93 on 2026-09-15. Feature requests now live in Discussions > Ideas.
Feature request
For a multi-session Hermes SQLite store,
gbrain transcripts ingest --since <time>has documented session-level semantics: only sessions newer than the cutoff are selected. The ingest core compares the cutoff with the session's last message timestamp. If a long-lived session has one turn after the cutoff, the whole session is selected and every earlier turn is rendered and imported.That behavior matches the current help text, but it leaves no way to perform a cutover that admits only messages after a boundary. Please add an explicit opt-in turn/message cutoff while preserving the existing
--sincebehavior for compatibility.Synthetic reproduction
Create a synthetic Hermes store with one session and three messages:
2026-01-01T10:00:00Z2026-01-01T10:01:00Z2026-01-02T10:00:00ZThen run:
The command shape is accepted by the current CLI. Source inspection shows that the session is eligible because its last message is newer than the cutoff, after which the untrimmed session is passed to redaction and rendering. This illustrates a missing opt-in capability, not a violation of the current
--sincecontract.Expected behavior
--sincesession-level unless a deliberate breaking change is separately chosen.--messages-since <time>or--turns-since <time>that trims messages before redaction and rendering.--since lastcheckpoint fingerprint or define a separate checkpoint scope.Suggested tests
--sincebehavior remains session-level--since lastwithout checkpoint cross-talkAll reactions