hermes - 💡(How to fix) Fix [BUG] unhandled auth_type oauth_minimax warning on auxiliary providers

Description

Every time a chat session starts (new conversation or /new), the errors.log shows:

WARNING agent.auxiliary_client: resolve_provider_client: unhandled auth_type oauth_minimax for minimax-oauth

This fires twice per session (once per auxiliary client initialization).

Impact

• Non-critical: chat works correctly via fallback
• Logs are polluted (145+ warnings accumulated in a few hours)
• Affects all profiles (default, finus, tikita) when using minimax-oauth

Root Cause

In agent/auxiliary_client.py, the resolve_provider_client() function handles auth_type values like bearer, api_key, oauth_openai, but has no handler for oauth_minimax:

# File: agent/auxiliary_client.py
def resolve_provider_client(provider, auth_type, ...):
    if auth_type == "bearer": ...
    elif auth_type == "api_key": ...
    elif auth_type == "oauth_openai": ...
    # ← no elif for "oauth_minimax"
    else:
        logger.warning("unhandled auth_type %r for %r", auth_type, provider)
        return None  # ← falls back, chat still works

Suggested Fix

Add a handler branch for auth_type == "oauth_minimax". The logic should mirror the oauth_openai handler since both are OAuth-based. Alternatively, extract a shared _resolve_oauth_client() helper.

Environment

• Hermes Agent: latest (NousResearch/hermes-agent)
• Profiles: default, finus, tikita
• Provider: minimax-oauth
• OS: Debian GNU/Linux 13 (trixie) VM