Restore relentless, self-healing persistence (upstream-Hermes style)#27
Merged
Conversation
Revert the conservative loop posture: the agent should push through blockers and fix root causes itself, not stop at the first failure or get hard-halted. - tool_loop_guardrails.hard_stop_enabled: true -> false (back to upstream: it keeps going; warnings stay on). Earlier I enabled the hard-stop to tame the old 405B flailing; with DeepSeek as the agent the user wants the persistent behavior back. - SOUL: replace 'try one fix then STOP and report' with resourceful persistence -- read the real error, install missing dependencies (pip/brew/npm/playwright), change tactics, and keep going until done. The one rule kept: never repeat an identical failing call -- change something every attempt and learn from the error. (So e.g. a browser tool with no backend gets the backend installed + retried, instead of looping the same call or halting.)
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.
Revert the conservative loop posture so the agent pushes through blockers and fixes root causes itself instead of stopping or getting hard-halted.
hard_stop_enabled: true -> false-- back to upstream Hermes behavior (keeps going; warnings stay on). The hard-stop was added to tame the old 405B flailing; with DeepSeek as the agent the persistent behavior is wanted back.pip/brew/npm/playwright install), change tactics, keep going until done. The one rule kept: never fire the identical failing call again -- change something each attempt and learn from the error.Concretely: a tool whose backend isn't installed (e.g.
browser_navigatewith no playwright) now gets the backend installed and retried, instead of looping the same call or hard-halting at 5.