Description

After upgrading to v0.14.0, Hermes crashes with a NameError when a 429 rate limit error is encountered from a provider.

Error

Error: name '_pool_may_recover_from_rate_limit' is not defined

Root Cause

agent/conversation_loop.py imports run_agent as a module at line 81:

import run_agent

But at line 2254, _pool_may_recover_from_rate_limit is called without the module prefix:

pool_may_recover = _pool_may_recover_from_rate_limit(
    agent._credential_pool,
    provider=agent.provider,
    base_url=getattr(agent, "base_url", None),
)

This causes a NameError because the function is defined in run_agent.py, not in scope of conversation_loop.py.

Fix

pool_may_recover = run_agent._pool_may_recover_from_rate_limit(
    agent._credential_pool,
    provider=agent.provider,
    base_url=getattr(agent, "base_url", None),
)

Steps to Reproduce

1. Configure a provider that hits a 429 rate limit (e.g. ollama-cloud weekly quota exhaustion)
2. Trigger a conversation — Hermes fails with NameError instead of falling back to the next provider

Environment

• Hermes v0.14.0 (2026.5.16)
• Python 3.11.15