Problem

ONBOARD_PROVIDER_AUTH_FLAGS in src/commands/onboard-provider-auth-flags.ts defines 25 auxiliary provider CLI flags (e.g., --mistral-api-key, --openrouter-api-key, --kilocode-api-key, etc.) that are:

• ✅ Registered as CLI options via the loop in src/cli/program/register.onboard.ts (lines 63-65)
• ✅ Typed in OnboardOptions (e.g., mistralApiKey?: string)
• ✅ Have credential setters in src/commands/onboard-auth.credentials.ts (e.g., setMistralApiKey())
• ❌ Never consumed during non-interactive onboarding

applyNonInteractiveRuntimeAuth() in src/commands/onboard-non-interactive/local.ts only handles the 4 runtime providers (claude, gemini, codex, opencode). The 25 auxiliary provider keys passed via CLI flags are silently ignored.

Evidence

// src/commands/onboard-non-interactive/local.ts — applyNonInteractiveRuntimeAuth
// Only processes: anthropicApiKey, geminiApiKey, codexApiKey, openaiApiKey, authToken
// Never reads: mistralApiKey, openrouterApiKey, kilocodeApiKey, etc.

Credential setters like setMistralApiKey() exist but have zero callers outside their definition module.

Proposed fix

After runtime auth is applied, iterate over ONBOARD_PROVIDER_AUTH_FLAGS and call the corresponding setter for any auxiliary key provided:

// After applyNonInteractiveRuntimeAuth:
for (const flag of ONBOARD_PROVIDER_AUTH_FLAGS) {
  const value = opts[flag.optionKey];
  if (value) {
    const setter = auxiliarySetterMap[flag.optionKey];
    if (setter) await setter(value);
  }
}

This also unblocks adding --elevenlabs-api-key for TTS credential onboarding.

Scope

Origin

This is an upstream OpenClaw pattern — the flags were scaffolded but never wired. Fixing this is a RemoteClaw improvement.

Related

• feat(auth): add ElevenLabs provider to auth profile system #403 — ElevenLabs auth provider (adds the setter, missing the flag)
• fix(tts): resolve TTS API keys through auth profile store #402 — TTS auth profile integration (consumer of ElevenLabs auth)
• feat: unified auth + multimodal AgentRuntime — implementation plan #415 — implementation plan (Phase 6)