Official issues about login, OAuth, API keys, and provider auth. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
When the Hermes Dashboard is bound to a non-loopback address with only basic_auth configured, visiting the root URL 500s because the auto-redirect calls the SSO start_login() path, which basic auth (password-only) doesn't implement.
When minimax-oauth is configured for auxiliary.title_generation, Hermes still tries to load a MINIMAX-OAUTH_API_KEY env var instead of using the existing OAuth token auth, causing title generation to fail.
In gated dashboard auth mode, clicking the Nous Portal provider login inside an already-authenticated dashboard fails before calling the backend because the frontend requires a legacy session token that is intentionally absent.
Signal group messages that pass the adapter-level filter are still rejected by _is_user_authorized because Platform.SIGNAL is missing from the platform_group_user_env_map dict used for group authorization.
The SendGrid redaction regex in agent/redact.py stops matching at the second dot, so the key-secret segment of a 3-part SendGrid API key remains unmasked in cleartext in logs and transcripts.
When the dashboard uses the built-in basic auth provider, the GET /auth/login?provider=basic redirect returns HTTP 500 instead of the login form because BasicAuthProvider.start_login() always raises NotImplementedError.
get_env_value_prefer_dotenv() returns None when get_secret() finds no match, instead of falling through to os.environ, preventing secrets injected via Bitwarden Secrets Manager from being resolved.
A non-interactive gateway run can stay stuck in MCP OAuth discovery for the full browser-callback timeout when token refresh fails, and retries then fail because the callback port is still in use. This issue is now closed.
The dashboard-auth.log file is written via plain append with no size cap or rotation, unlike other log files in the system, causing it to grow unbounded on busy dashboards.
Enabling security.redact_secrets rewrites secret-shaped substrings inside the actual command text sent to the shell or interpreter, not just in logs, corrupting commands that legitimately contain credential-like strings.
Remote dashboard sessions repeatedly expire around the refresh-token rotation window when accessed from another machine on the LAN.
The OpenAI Codex device-auth login flow reads successful JSON responses with unbounded httpx calls, with no byte cap on the response body for several auth endpoints.
The built-in Anthropic OAuth token exchange fails with HTTP 404 because Anthropic now blocks any request carrying a claude-cli/ User-Agent prefix regardless of version, confirmed by testing multiple User-Agent strings.
Cron jobs using OAuth-based providers fail with HTTP 429 when the credential pool is exhausted instead of falling back through the configured fallback_providers chain, unlike the main gateway/CLI session.
Hermes incorrectly marks all openai-codex pooled credentials as rate-limited even when one account still has quota, and running hermes auth reset openai-codex immediately restores normal operation.
Hermes currently supports Bitwarden Secrets Manager as an external secret source; the issue proposes adding Proton Pass's new AI Access Tokens as an additional secret source backend, given its read-only vault access, expiration controls, and audit logs.
Profiled Hermes workers using isolated HERMES_HOME directories can end up with split-brain OAuth state for rotating/single-use refresh tokens; the reporter proposes a separate shared HERMES_AUTH_HOME for auth storage.
Feature request to support an HTTPS OAuth redirect_uri override for MCP, since some OAuth providers (e.g. Salesforce) reject the current localhost HTTP callback format.
On a local macOS Hermes install, the xAI OAuth browser callback succeeds ("authorization received") but Hermes still throws an authorization timeout and never stores xAI credentials, a case the reporter distinguishes from documented remote/SSH callback failures.
This closed issue reported that the xai-oauth provider returned HTTP 403 at inference time for standard (non-Heavy) SuperGrok subscribers, apparently due to an xAI backend restriction rather than a Hermes-side bug.
After a Hermes update, the Kanban board fails to load with a 401 Unauthorized error via the dashboard, which the reporter suspects stems from the same update cycle that also broke Telegram pairing and introduced the 64K context minimum error.
With a valid Claude Max 20x OAuth access token, every Hermes request to the native Anthropic provider fails with HTTP 400, reporting that extra usage has been exhausted. Issue is closed as fixed.
Hermes has no working auth path for the Google Cloud Vertex AI provider, causing silent failures; the reporter built a standalone proxy handling service-account auth and proposes upstreaming it via the existing custom_providers mechanism.
OpenAI Codex OAuth works via CLI, but the Telegram gateway reports 'No Codex credentials stored' despite the same credentials being valid, in a Docker/Coolify deployment. This issue is now closed.
The set of commands requiring dangerous-action approval is currently hard-coded in tools/approval.py, so users cannot mark installation-specific or operationally-disruptive commands as approval-required without patching the source; the issue requests a configurable mechanism.
This feature proposes a credential proxy daemon that intercepts HTTP/HTTPS at the transport layer so the real credential value never exists anywhere the agent process can read it, addressing a gap left by existing env-scoping and PID-isolation mitigations.
This issue reports that Hermes Agent's gateway authorization is currently all-or-nothing, and proposes a tiered permission system (Owner/Admin/User/Guest) for messaging platforms.
Back to curated issues . School solution cards . Troubleshooting