NousResearch/hermes-agent · error

started.error || 'OAuth failed to start'

Error message

started.error || 'OAuth failed to start'

What it means

Error "started.error || 'OAuth failed to start'" thrown in NousResearch/hermes-agent.

Source

Thrown at apps/desktop/src/lib/mcp-dashboard-oauth.ts:50

  }
}

const defaultSleep = (milliseconds: number) => new Promise<void>(resolve => window.setTimeout(resolve, milliseconds))

export async function completeMcpDesktopOAuth({
  serverName,
  start,
  status,
  openExternal,
  cancelled,
  cancel,
  sleep = defaultSleep,
  maxPollFailures = 3
}: CompleteOptions): Promise<McpOAuthFlow> {
  const started = await start(serverName)

  if (started.status === 'error') {
    throw new Error(started.error || 'OAuth failed to start')
  }

  if (!started.authorization_url) {
    throw new Error('OAuth server did not provide an authorization URL')
  }

  await openExternal(started.authorization_url)

  let pollFailures = 0

  for (;;) {
    if (cancelled?.()) {
      // Free the backend slot before rejecting; best-effort — the flow also
      // dies on its own timeout if this request is lost.
      await cancel?.(started.flow_id).catch(() => {})
      throw new McpOAuthCancelled()
    }

View on GitHub (pinned to c896c09c42)

Solutions

1. Retry starting the OAuth flow; the gateway reported a startup error.
2. Check the OAuth provider configuration (client id, redirect URL) on the gateway.
3. Review gateway logs for the underlying OAuth start failure.

When it happens

Trigger: Thrown at apps/desktop/src/lib/mcp-dashboard-oauth.ts:50 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of NousResearch/hermes-agent@c896c09c42 (2026-08-14). Data as JSON: /api/errors/8634037043b98488. Report an issue: GitHub.