Repository navigation
A caller that knows when this sitting began can say so - #57
Merged
Merged
Conversation
With the window bounded to thirty minutes (#55) a new episode no longer opens holding last month's, but takes come back to back: episodes 8 and 9 were twenty-one minutes apart in the same room, so the default would still have handed the second one the first one's transcript - and a retake right after a failure is the normal case, not the odd one. The leg cannot know where an episode begins. The show does. So --memory-since (ISO or epoch ms) sets the line, and nothing before it is this call's. Without it, the thirty-minute window stands, so a plain `join` is unchanged. A value that does not parse is ignored rather than trusted: a bad flag must not blank the context a rejoin depends on. 115 pass, 0 fail; tsc clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
Follow-up to #55/#56. Bounding room memory to thirty minutes stops a new episode opening with last month's, but it does not stop it opening with the last take's — and a retake right after a failure is the normal case here, not the odd one:
Inside one thirty-minute window, so episode 9 would have been handed episode 8's transcript as its own memory — including a guest answer it never heard.
The leg cannot know where an episode begins; the show does.
--memory-since(ISO or epoch ms) sets the line, and nothing before it belongs to this call — used both for the memory load and for the catch-up staleness guard from #56, so the two cannot disagree.Without the flag the thirty-minute window stands, so a plain
agent-phone joinis unchanged. A value that does not parse is ignored rather than trusted: a bad flag must not blank the context a rejoin depends on ('tomorrow-ish'and'0'both fall back).bun test115 pass / 0 fail,tsc --noEmitclean.Needs the matching one-line change in offtherecord to pass the episode's
created_at; opening that next.🤖 Generated with Claude Code