fix: make epoch mismatch messages visible and recoverable#35
Merged
Conversation
The epoch mismatch messages were addressed to the user but delivered as system context only Claude sees. Rewrote them as instructions to Claude following the NUDGE_MESSAGE pattern so the agent actually relays them. Also fixed agent-setup to update epoch fields in existing souls — previously it skipped the soul entirely if it already existed, making the suggested "re-run agent-setup" action a no-op.
11bfabb to
c03dd4c
Compare
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.

The epoch mismatch messages were addressed to the user but delivered as
system context only Claude sees. Rewrote them as instructions to Claude
following the NUDGE_MESSAGE pattern so the agent actually relays them.
Also fixed agent-setup to update epoch fields in existing souls — previously
it skipped the soul entirely if it already existed, making the suggested
"re-run agent-setup" action a no-op.