Nous ResearchHermes Agent

Fix Copilot-ACP Connection Issues in Hermes

Resolve common Copilot-ACP authentication and model errors when using GitHub Copilot as a provider in Hermes Agent.

Copilot-ACP integration can encounter authentication issues, especially with certain auxiliary model configurations. The most common fix is changing your aux model from Qwen to MiMo or another model.

Deploy Hermes faster with FlyHermes

Managed cloud · API costs included · Skill library · Cancel anytime

Before you start:

  • Hermes Agent installed
  • GitHub CLI (gh) installed and authenticated
  • GitHub Copilot subscription active

Steps

  1. 1

    Check the error logs

    Look in ~/.hermes/logs/agent.log for 'unhandled auth_type external_process for copilot-acp' warnings

  2. 2

    Set a different aux model

    In config.yaml, set the auxiliary model to something other than Qwen — try MiMo or another stable model

  3. 3

    Verify gh auth status

    Run 'gh auth status' to ensure GitHub CLI is properly authenticated with Copilot access

  4. 4

    Update Hermes

    Run 'hermes update' — Copilot-ACP bugs are frequently patched

  5. 5

    Check provider fallback

    Ensure you have a fallback provider configured in case Copilot-ACP fails

Pro Tips

  • 💡The aux model setting at agent.auxiliary_models in config.yaml controls which model handles lightweight tasks — Qwen has been causing issues with Copilot-ACP
  • 💡Check the Hermes Discord for real-time updates on provider issues — Copilot-ACP problems are usually discussed within hours
  • 💡Having a fallback provider like OpenRouter prevents complete downtime when one provider has issues

Troubleshooting

'CopilotACPClient' object has no attribute 'responses'

This is a known bug with certain Copilot-ACP versions. Update Hermes to the latest version and change the aux model to MiMo.

Context length detection failing for Copilot models

Set model.context_length explicitly in config.yaml to override the auto-detection: model: context_length: 128000

Falling back to gh auth instead of staying on copilot-acp

Check ~/.hermes/logs/gateway.log for the specific auth failure. Often requires re-running 'gh auth login' with Copilot scope.

Related Guides