{"repo":"NousResearch/hermes-agent","public_id":"32617","display_label":"Stale encrypted_content persisting after provider or LLM switch","summary":"These members all concern stale encrypted reasoning state (`encrypted_content`) being carried over after switching providers, with one report of 400 errors on Telegram sessions and another tied to xAI OAuth fallback. One member is a fix-oriented pull request that proposes stripping that state; the titles alone do not show whether the problem is settled.","subsystem":"agent","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":2,"merged_prs":0,"attempt_prs":1},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_PARTIAL","link_density":0.4533333333333333},"fix_edges":[],"members":[{"kind":"issue","number":32617,"title":"xAI OAuth fallback after provider switch due to stale encrypted_content replay","url":null,"state":"closed"},{"kind":"issue","number":34205,"title":"[Bug]: Provider/LLM switch leaves stale encrypted_content causing 400 errors on Telegram sessions","url":null,"state":"closed"},{"kind":"pr","number":34360,"title":"fix(agent): strip stale encrypted reasoning state on provider switch (#34205)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"commit","value":"9c69204d8783a530db065136a39baca9817b7c40","number":0},{"kind":"commit","value":"91d05b982d0bc08a735a2c0b1fedccd93b7fc9cd","number":0},{"kind":"pr","value":"#31629","number":31629}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}