feat(cron): render scheduled reminders in TUI and expose fired events#204
Open
sailist wants to merge 2 commits into
Open
feat(cron): render scheduled reminders in TUI and expose fired events#204sailist wants to merge 2 commits into
sailist wants to merge 2 commits into
Conversation
- add CronMessageComponent for distinct cron transcript entries in TUI\n- emit cron.fired events from agent-core and expose via node-sdk\n- report cron fire times with local ISO timestamps including timezone offsets\n- render cron_job and cron_missed origins during session replay instead of skipping\n- handle warning events in CLI and session event handler
- cron-create.md: instruct model to proactively tell users how to cancel/modify reminders\n- cron-list.md: add guideline that users cannot directly manage cron tasks\n- cron-delete.md: emphasize users must ask model to cancel reminders
🦋 Changeset detectedLatest commit: 534064a The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
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.
Summary
This PR improves the cron (scheduled reminder) experience by rendering fired reminders distinctly in the TUI, exposing cron events to SDK consumers, and clarifying user-facing documentation around task management.
1. Render scheduled reminders in TUI and expose fired events
Problem: Previously, cron-fired reminders were invisible during an active session and were skipped entirely during session replay, making it impossible for users to see what reminders had fired. Additionally, SDK clients had no way to observe cron events.
What was done:
CronMessageComponentto render cron transcript entries distinctly in the TUI.cron.firedevents fromagent-coreand exposed them vianode-sdk.cron_jobandcron_missedorigins during session replay instead of skipping them.2. Clarify user documentation for cron task management
Problem: The cron tool documentation did not clearly explain that users must ask the model to cancel or modify reminders, rather than managing them directly.
What was done:
cron-create.mdto instruct the model to proactively tell users how to cancel or modify reminders.cron-list.mdto add a guideline that users cannot directly manage cron tasks.cron-delete.mdto emphasize that users must ask the model to cancel reminders.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.