fix(loop): fired tasks actually execute instead of being refused (0.7.1) - #16
Merged
Conversation
The 0.7.0 confirmation prompts told the model not to treat the task prompt as an instruction; that instruction lingered in the conversation, so when a task later fired the model refused to run it. The prohibition is now scoped to the confirmation reply only, and fixed-task fires inject an explicit "scheduled execution — perform this task now" wrapper instead of the bare prompt. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
Test plan
npm test— 150/150 通过（新增触发文本断言）🤖 Generated with Claude Code