fix: preserve agent for scheduled reminders#4
Open
kernel-oops wants to merge 1 commit into
Open
Conversation
This was referenced Jul 25, 2026
Author
|
A consolidated integration PR is now available at #5. It deliberately combines #2, #3, and #4, resolves their overlapping scheduler changes, and adds regression fixes found while stress-testing the combined lifecycle. This PR is left open for history/discussion, but the consolidated PR is the recommended merge path. |
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.
Summary
Preserve the agent that scheduled a reminder and use it when the reminder fires.
ToolContext.agentwhenreminderaddcreates a remindersession.prompt()during executionbody.agentwhen it is absentRoot cause
Reminder execution submitted only
body.parts. OpenCode therefore fell back to the configured default agent, so a reminder scheduled from one agent could unexpectedly run as another agent and inherit different permissions or behavior.Tests
Verified locally:
Relationship to #2 and #3
This PR is intentionally based directly on
mainand addresses a separate agent-selection issue. It does not depend on the cancellation-race changes in #2 or the cross-process coordination changes in #3, though overlapping scheduler/test files may require integration after another PR merges.