hermes - 💡(How to fix) Fix Telegram /model picker makes it easy to select GitHub Copilot REST instead of Copilot ACP [1 pull requests]

Bug Description

In Telegram, the /model interactive picker exposes GitHub Copilot options in a way that can lead users to select the normal copilot provider when they intended to use copilot-acp.

On this install, selecting the visible GitHub Copilot route from Telegram switched the session to the normal REST provider and the injected model note said:

[Note: model was just switched from gpt-5.5 to gpt-5-mini via GitHub Copilot. Adjust your self-identification accordingly.]

That path then hit the known normal Copilot REST/PAT auth failure:

Personal Access Tokens are not supported for this endpoint

Manually switching with the explicit ACP provider works:

/model gpt-5-mini --provider copilot-acp

So ACP itself appears to work; the confusing/failing path is the Telegram picker/default selection of plain copilot.

Steps to Reproduce

1. Use Hermes via Telegram gateway.
2. Open the interactive model picker with /model or /models.
3. Select the GitHub Copilot option/model such as gpt-5-mini.
4. Observe the gateway note says the model switched via GitHub Copilot, not GitHub Copilot ACP.
5. Send a test message.
6. The normal REST provider may fail with Personal Access Tokens are not supported for this endpoint.
7. Switch manually with /model gpt-5-mini --provider copilot-acp.
8. The ACP path responds successfully.

Expected Behavior

If both copilot and copilot-acp are available, the Telegram picker should make the distinction very clear and route to the selected provider correctly.

Possible fixes:

• Show separate picker entries named GitHub Copilot and GitHub Copilot ACP.
• Prefer copilot-acp when the local Copilot CLI/ACP path is available and the normal Copilot REST provider is not correctly OAuth-authenticated.
• Add a warning/diagnostic when switching to plain copilot while only a normal GitHub PAT/gh token is available.
• In the confirmation note, include the provider slug as well as the friendly label, e.g. GitHub Copilot ACP (copilot-acp).

Actual Behavior

The Telegram picker path switched to plain GitHub Copilot / copilot, which is easy to confuse with ACP and reproduces the normal Copilot auth failure. Explicit --provider copilot-acp works.

Environment

• Platform: Telegram gateway
• Repo: NousResearch/hermes-agent
• Install path: /usr/local/lib/hermes-agent
• Observed after updating to current main on 2026-05-25
• Default stable provider before test: openai-codex / gpt-5.5
• Working manual route: /model gpt-5-mini --provider copilot-acp
• Failing/confusing route: Telegram picker selection showing via GitHub Copilot

Notes

No credentials, tokens, or private config values are included here. The issue is about provider selection/routing UX and diagnostics, not exposing auth material.