-
Notifications
You must be signed in to change notification settings - Fork 3.6k
fix(agent-harness): escalate user-actionable blockers to the user with a concrete ask (#4092) #4482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
senamakel
merged 4 commits into
tinyhumansai:main
from
senamakel:fix/GH-4092-escalate-to-user
Jul 4, 2026
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
7aeb668
fix(agent-harness): escalate user-actionable blockers to the user wit…
senamakel f20fe17
test(ci): add privacy_mode config methods to the schema-catalog golden
senamakel 2be8e99
Merge branch 'main' into pr/4482
senamakel 72ecf82
fix(agent-harness): narrow user-actionable reconnect escalation
senamakel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This broad substring also matches agent-actionable MCP errors:
mcp_clients_list_toolsreturnsserver_id=... is not connected; connect it first via mcp_clients_connect(src/openhuman/mcp_registry/ops.rs), and the tinyagents adapter turns that into a failed tool result. After repeated calls, this new branch replaces that recovery hint with “Connect it (Settings → Connections)”, even though the correct next step is for the agent to call the MCP connect tool, not for the user to reconnect a service in Settings. Please anchor this escalation to true integration/platform connection failures (or preserve errors that already name a recovery tool).Useful? React with 👍 / 👎.