{"repo":"NousResearch/hermes-agent","public_id":"132937","display_label":"Named custom provider persistence broken across ACP restarts","summary":"A bug causes named custom providers to be stored as bare 'custom' labels, leading to authentication failures when ACP sessions are restored. The members address identifying, reproducing, and fixing this persistence and session-restore issue.","subsystem":"acp","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":132937,"title":"ACP session restore fails for named custom providers (bare \"custom\" persisted, 401 on first prompt)","url":null,"state":"open"},{"kind":"pr","number":132947,"title":"fix(acp): heal the bare custom provider label on session restore","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":132954,"title":"fix(acp): restore and persist named custom providers across ACP restarts","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}