Conversation
When a goal continuation turn failed, timed out or never started, the
Engine marked the goal Blocked. The next message from the person still
arrived with the host's Blocked status, so it ran as an ordinary
goalless turn: the goal stayed blocked on an obsolete runtime blocker
and the model's progress updates were refused ("requires an active
goal") with no way forward except a manual /goal resume.
The Engine now records whether a blocker came from the runtime
(block_goal_continuation) or was reported by the model/user
(update_goal / mark_blocked). A message from the person (ExternalUser
provenance) naming the same objective resumes a runtime-blocked goal as
a new control revision and publishes GoalUpdated plus a status line.
Reported blockers stay until an explicit resume; runtime and automated
inputs never resume anything. Known limitation: the origin is
session-local, so a restored Blocked goal still needs /goal resume.
Evidence: 150 passed, 0 failed (13,108 skipped) on the `goal` selection,
including the new engine test. With the resume hook disabled, that test
fails (0 passed, 1 failed: "the continue turn ran as a resumed goal
revision"). TUI all-target/all-feature Clippy with CI flags and fmt
passed.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
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.
No-Issue: 0.10.1 release-readiness recovery and first-call tool work, found in dogfooding; no public issue tracks it.
When a goal continuation turn failed, timed out or never started, the
Engine marked the goal Blocked. The next message from the person still
arrived with the host's Blocked status, so it ran as an ordinary
goalless turn: the goal stayed blocked on an obsolete runtime blocker
and the model's progress updates were refused ("requires an active
goal") with no way forward except a manual /goal resume.
The Engine now records whether a blocker came from the runtime
(block_goal_continuation) or was reported by the model/user
(update_goal / mark_blocked). A message from the person (ExternalUser
provenance) naming the same objective resumes a runtime-blocked goal as
a new control revision and publishes GoalUpdated plus a status line.
Reported blockers stay until an explicit resume; runtime and automated
inputs never resume anything. Known limitation: the origin is
session-local, so a restored Blocked goal still needs /goal resume.
Evidence: 150 passed, 0 failed (13,108 skipped) on the
goalselection,including the new engine test. With the resume hook disabled, that test
fails (0 passed, 1 failed: "the continue turn ran as a resumed goal
revision"). TUI all-target/all-feature Clippy with CI flags and fmt
passed.
🤖 Generated with Claude Code