Refreshed this PR on top of current upstream v0.8.0 tip. The branch now contains only the still-needed delta: credential_pool detection for mapped providers like copilot plus curated gpt-5.4/gpt-5.4-mini entries for openai-codex.

I hit a closely related case on the gateway /model flow.

In my repro, the problem was not only Copilot model visibility, but also provider visibility when credentials existed in Hermes auth storage / credential pool but were not exported as environment variables in the current process.

What I observed:

• copilot was present in Hermes auth storage, but /model could show it incorrectly or with missing/empty model entries
• gemini was also present in auth storage, but /model did not show it at all
• the behavior depended too heavily on env-var detection during provider listing

It also looks like there is a provider-ID mismatch aspect for Copilot:

• Hermes slug: copilot
• models.dev provider id: github-copilot

So provider detection and curated model lookup can disagree unless both the Hermes slug and the mapped models.dev id are checked consistently.

A similar mapping issue may also affect Gemini / Google:

• Hermes slug: gemini
• models.dev provider id: google

In short, /model provider listing seems more reliable if it treats these as valid credential sources:

• environment variables
• auth store providers
• auth store credential_pool

And then normalizes provider slug ↔ models.dev id before duplicate suppression / curated model lookup.

I’m mentioning this because the fix here may want to cover not just Copilot model enumeration, but the broader “authenticated in Hermes but not exported in env vars” case too.

Thanks — I reproduced the broader case locally and refreshed this PR branch on top of current upstream.

Verified behavior difference against clean upstream:

• providers authenticated in Hermes auth storage but not exported as env vars can be missing from /model
• in my repro this affected not just copilot, but also gemini
• clean upstream showed only openai-codex
• local patched behavior showed copilot, gemini, and openai-codex

So I agree the fix should be framed as broader provider visibility from Hermes auth storage, not just Copilot model enumeration.

This PR still does two concrete things:

• treat credential_pool as a valid credential source for mapped providers during provider listing
• add curated gpt-5.4 / gpt-5.4-mini entries for openai-codex

It does not try to fully rewrite all slug <-> models.dev normalization paths, but it does address the verified "authenticated in Hermes, not exported in env vars" failure mode that affected both copilot and gemini in my local tests.

Quick note: GitHub Actions on this fork PR currently show action_required with 0s runtime (Tests / Nix / Docker / Supply Chain Audit), which looks like maintainer workflow approval is still needed before checks will actually run.

Verified again against current origin/main after rebasing.\n\nCurrent upstream still misses Hermes-mapped providers when credentials exist only in auth-store credential_pool and are not exported as env vars. In a local smoke test, clean upstream omitted gemini in that scenario, while the reduced patch makes gemini appear with its curated models.\n\nI also trimmed this PR to only that surviving fix. The earlier openai-codex curated-model addition is no longer included because current upstream already has that behavior.

Refreshed this branch on top of current origin/main and re-verified the behavior against clean upstream.

What I checked locally:

• clean upstream: mapped provider gemini does not appear when credentials exist only in Hermes auth-store credential_pool
• patched branch: gemini appears correctly
• real local auth-store also reproduces this difference (credential_pool currently contains gemini)

So the fix is still needed; this PR now contains only the surviving delta on top of current upstream.

This branch has been refreshed on top of current origin/main and reduced to the still-needed delta only.

Re-verified locally against clean upstream:

• clean upstream omits gemini when credentials exist only in Hermes auth-store credential_pool
• this patch makes the mapped provider appear correctly in /model

Would appreciate maintainer review when convenient.

Thanks for the careful, well-maintained contribution @jakubkrcmar! This fix has already been merged into main.

Automated hermes-sweeper review.

The credential_pool detection logic and the regression test from this PR were salvaged into main as commit 1af44a13c (fix(model_picker): detect mapped-provider auth-store credentials), which has the identical diff (+8 lines to hermes_cli/model_switch.py, +19 lines to tests/hermes_cli/test_overlay_slug_resolution.py).

• hermes_cli/model_switch.py line 1058–1065: credential_pool check is present verbatim
• tests/hermes_cli/test_overlay_slug_resolution.py line 87: test_mapped_provider_credential_pool_visibility is present verbatim
• 483 subsequent commits have landed on top of this fix

Closing as implemented on main.