Summary

• Adds a new noteMemorySearchHealth() check to openclaw doctor that detects when memory search is enabled but no embedding provider is configured
• Uses config-only detection (no network calls) via resolveApiKeyForProvider() and local model path checks
• Displays actionable fix suggestions with specific commands for each scenario

What it checks

The new check handles 4 scenarios:

1. Memory search explicitly disabled (enabled: false) — brief info note, not a warning
2. Provider set to local but no model file found — suggests configuring local model or switching to remote
3. Specific remote provider set but no API key — names the missing env var and suggests openclaw auth add
4. Provider set to auto (default) and no provider available — generic guidance listing all fix options

Each note ends with openclaw memory status --deep as the verify command.

Why

Users expect persistent memory to work after setup, but without an embeddings provider configured, memory search silently fails. Users blame "AI forgot" when really they need to configure an embedding provider. This check surfaces the issue during openclaw doctor with specific, actionable fix guidance.

Design decisions

• Config-only, no network calls — keeps doctor fast; memory status --deep already does runtime probing
• Uses resolveApiKeyForProvider() — same resolution path as the embedding system (checks config profiles, keychain, env vars, config file), avoiding false positives from only checking env vars
• Respects intentional disable — if enabled: false, shows a brief note rather than a warning
• Follows existing patterns — structured like doctor-security.ts (builds message, calls note())

Scope

This PR addresses the openclaw doctor portion of #13027. Onboarding wizard enhancements and runtime warnings mentioned in the issue are left as future work.

Test plan

• TypeScript compilation passes (0 errors in changed files)
• Existing doctor e2e tests pass (6/6)
• Linter passes (0 warnings, 0 errors)
• Manual test: run openclaw doctor without any API keys configured — verify warning appears
• Manual test: run openclaw doctor with OPENAI_API_KEY set — verify no warning
• Manual test: set agents.defaults.memorySearch.enabled: false — verify info note appears

Closes #13027

🤖 Generated with Claude Code

Greptile Overview

Greptile Summary

Adds a new health check to openclaw doctor that detects misconfigured memory search embeddings providers and displays actionable fix suggestions. The implementation follows existing doctor check patterns, uses config-only detection (no network calls), and handles all major scenarios: explicitly disabled memory search, local models (missing files), specific remote providers (missing API keys), and auto-detection fallback. The code correctly integrates with existing auth resolution logic and provides clear, specific guidance for each failure mode.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The implementation is well-structured, follows existing patterns from other doctor checks, uses appropriate error handling (try-catch blocks), has no breaking changes, and only adds a new non-invasive health check. TypeScript compilation passes with no errors, linting passes, and the logic correctly handles all edge cases (null checks, provider mapping, file existence checks). The only issue found is a minor comment accuracy improvement.
• No files require special attention

_{Last reviewed commit: d871c04}