hermes - 💡(How to fix) Fix doctor falsely reports Copilot as unconfigured when gh_cli credential exists [1 pull requests]

Summary

hermes doctor reports that GitHub Copilot has no credentials / no API key configured even when the active profile is successfully using Copilot and hermes auth list copilot shows a valid gh_cli credential.

This looks like a false negative in diagnostics rather than an actual runtime auth failure.

What I observed

On Linux, after selecting GitHub Copilot as the model provider for a profile:

• hermes profile show <profile> shows the profile is using gpt-5.4 (github-copilot)
• hermes auth list copilot shows a valid credential, for example:

copilot (1 credentials):
  #1  gh auth token        api_key gh_cli ←

• the profile can still use Copilot successfully at runtime
• but hermes doctor still reports:

model.provider 'copilot' is set but no API key is configured
...
No credentials found for provider 'copilot'.

Why this seems wrong

The diagnostic appears to be checking only for an inline API key (or the wrong provider alias) and not recognizing the working gh_cli credential path.

There may also be an alias mismatch involved:

• profile/config display shows github-copilot
• hermes auth list uses copilot
• hermes doctor reports copilot

So this may be one of:

1. doctor only checks model.api_key and ignores credential-pool / gh_cli auth
2. doctor is checking the wrong provider slug/alias (copilot vs github-copilot)
3. both

Reproduction

1. Authenticate GitHub CLI / Copilot so hermes auth list copilot shows a gh_cli credential.
2. Select GitHub Copilot in hermes model.
3. Verify the profile shows a Copilot model, e.g. hermes profile show <profile>.
4. Run:

hermes auth list copilot
hermes doctor

Actual result

hermes doctor says Copilot has no credentials / no API key configured.

Expected result

If a valid Copilot credential is available through gh_cli / auth storage, hermes doctor should either:

• report Copilot as configured, or
• clearly distinguish between:
  • “no inline API key configured” and
  • “usable credential found via auth/credential pool”

Environment

• OS: Linux
• Hermes version/config generation: config reported as v23 during doctor output
• Provider: GitHub Copilot
• Credential source: gh_cli

Potential debugging hint

The mismatch between github-copilot and copilot in different commands/output paths may be the easiest place to start.