{"repo":"NousResearch/hermes-agent","public_id":"46856","display_label":"OpenRouter 'Provider returned error' fallback and cooldown classification","summary":"These items concern how an agent's error classifier handles OpenRouter's 'Provider returned error' message, which has no status code. One issue reports it being classified as unknown, so no rate-limit cooldown applies and fallback resets each turn; two pull requests propose classifying it as rate_limit and keeping the provider fallback on cooldown.","subsystem":"agent","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":46856,"title":"[Fallback] \"Provider returned error\" (no status code) classified as unknown → no rate-limit cooldown → fallback resets every turn","url":null,"state":"open"},{"kind":"pr","number":46858,"title":"fix(agent): classify 'Provider returned error' as rate_limit in error classifier","url":null,"state":"open","close_reason":{"refs":[{"kind":"pr","value":"#46856","number":46856}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":47354,"title":"fix(agent): keep OpenRouter provider fallback on cooldown","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}