hermes-admin/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

fix(connectors): not_connected asks the user again in ordinary chats

Browse Source 
#130152 changed the shared settle note so not_connected read like skipped:
"do not ask about it again in this chat". That note reaches every chat, so
after a sign-in failed or expired in an ordinary chat the agent stopped
offering a retry. The loop #130152 fixed (the first task restarting its
steps and opening a second connect card) is already prevented by the
first-task skill itself ("The connect card's answer is final for this
chat", SKILL.md:69), and the setup skill never re-asks a skipped card.

Main's wording is back; the onboarding chats keep their rule through their
skills.
This commit is contained in:
alt-glitch
2026-10-07 07:13:24 +05:30
parent 8bd054eca9
commit b335ffab09
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
tools/connectors/managed.py
View File

@@ -36,10 +36,9 @@ _ACCOUNT_OUTCOME: Dict[str, Tuple[TargetState, Actor]] = {
}
NOTE = (
"Settled once. connected → use the app now. skipped or not_connected → the user moved on: do not "
"connect it again, do not ask about it again in this chat, and do not route around it; you may say "
"once that they can connect it later. A later request from the USER for that same app is not a "
"re-ask — run it."
"Settled once. connected → use the app now; skipped → the user chose Not now, do not connect it "
"or route around it; not_connected → ask the user what to do, never re-mint on your own. "
"A later request from the USER for that same app is not a re-ask — run it."
)