ref(dispatch): route dispatches through conversation work#1059
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c1b747f. Configure here.
dcramer
force-pushed
the
codex/dispatch-conversation-work
branch
from
July 27, 2026 00:43
cf6f1cd to
8522e13
Compare
dcramer
marked this pull request as ready for review
July 27, 2026 01:08
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 and plugin dispatches now enter the same per-conversation mailbox and lease flow as interactive turns. The dispatch-specific execution loop is removed; start and resume both use the shared turn runtime while dispatch identity, execution authority, destination, source, and delivery state remain durable across serverless invocations.
The rollout keeps signed legacy callbacks enqueue-only and repairs pre-cutover records through bounded heartbeat recovery. Terminal session state now commits the semantic dispatch outcome and accepted provider message ID together, preventing retries from rerunning or misprojecting delivered work. Regression coverage exercises production routing, yield and resume, local-origin sources, delivery fencing, and legacy callback validation and recovery.
Refs #883.