fix(scheduler): Isolate scheduled dispatch context#454
Merged
Conversation
Scope dispatched agent conversation state to the dispatch record instead of the Slack destination. This lets scheduled runs that post new Slack messages start with fresh context while preserving destination-level delivery locking. Fixes GH-451 Co-Authored-By: GPT-5 Codex <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Scheduled dispatches now keep their persisted conversation, Pi transcript, artifact, and sandbox state keyed by the dispatch record instead of the Slack destination. This prevents scheduled runs that post new Slack messages from inheriting prior channel-level context while preserving destination-level delivery locking.
Dispatch Isolation
The runner now separates the Slack destination lock from dispatch-scoped conversation state, so retries and timeout resumes still reuse the same dispatch context without bleeding in channel history.
Regression Coverage
The integration test seeds destination conversation memory and verifies a scheduled dispatch starts without inherited context and writes only to its dispatch-scoped state.
Fixes #451