refactor(prompts): defer cron mechanics to the scheduling-tasks skill - #3683
Merged
Conversation
The Working-across-time section restated cron CLI mechanics (invocation templates, flag behavior, schedule placement rules) that the scheduling-tasks skill also documents. The CLI copy changes across versions while the prompt copy is always in context, so agents keep trusting stale mechanics — the placement paragraph alone needed edits in three consecutive PRs (#3665 and follow-ups). The prompt now owns the durable concept: no future invocation happens unless the agent schedules it, when to create crons, proactivity, and cost. One line defers all mechanics to the skill and warns against relying on remembered flag behavior. 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>
2 tasks
…agraph The deferral change is deletion-only plus one pointer line; the opening paragraph paraphrase was scope creep. 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>
1 task
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
Working across timesection of both system prompts: theletta cron addinvocation templates, flag documentation,$AGENT_IDplumbing note, and the schedule-placement paragraph.Why
The prompt copy of cron mechanics drifts from the CLI: the placement paragraph alone needed edits in three consecutive PRs (#3665, its hotfix commit, and the pending #3682). Because the prompt copy is always in context, agents trust it over the skill even when the CLI has moved on — a stale prompt is worse than no prompt. The skill is versioned with the CLI it documents; that is the single source of truth for mechanics.
The invocation templates were deliberately not kept: an agent pattern-matching a remembered template instead of loading the skill is exactly the drift failure mode this removes.
Sequencing: lands before #3682 (stacked on this branch), which changes placement behavior again — with this merged, that PR only needs to update the skill.
Test plan
bun run checkgreen on the branch👾 Generated with Letta Code