GitHub Issue：Codex OAuth 场景下 memory_search 不可用的排查与临时方案

解决“已用 Codex OAuth 登录但记忆检索报缺少 API key”的问题：先确认状态，再用可替代流程保证关键记忆可读写，等待上游修复。

GITHUBDiscovered 2026-02-13Author finnbusse

Prerequisites

OpenClaw uses auth profile `provider: openai-codex` + `mode: oauth` and memory plugin is enabled.
You can run CLI status checks and edit local memory files in workspace.

Steps

Run status check first and confirm whether memory shows `enabled` but `unavailable`.
Trigger one controlled `memory_search` call and record the exact missing-provider error text.
Use file-based fallback for critical recall: write key decisions into `MEMORY.md` and date files under `memory/`.
Track upstream issue progress and remove fallback only after tool status is healthy in your environment.

Commands

openclaw status

openclaw gateway restart

# auth.profiles.openai-codex:default = { provider: "openai-codex", mode: "oauth" }

Verify

Either memory tool returns results normally, or fallback files are updated and recall continuity remains intact without data loss.

Caveats

Do not assume OAuth implies embedding provider credentials are available automatically.
Final behavior may change quickly after upstream patch release（需验证）。

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.