let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify memory search auth

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-13 00:25:54 +00:00
parent 4f3bedfdb7
commit 1f3ae2346e
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/start/faq.md
View File

@@ -231,6 +231,14 @@ Clawdbot also runs a **silent pre-compaction memory flush** to remind the model
to write durable notes before auto-compaction. This only runs when the workspace
is writable (read-only sandboxes skip it). See [Memory](/concepts/memory).
### Why does memory search need an OpenAI API key if I already signed in with Codex?
Vector memory search uses **embeddings**. Codex OAuth only covers
chat/completions and does **not** grant embeddings access, so the upstream
memory indexer needs a real OpenAI API key (`OPENAI_API_KEY` or
`models.providers.openai.apiKey`). If you don’t want to set a key, switch to
`memorySearch.provider = "local"` or set `memorySearch.fallback = "none"`.
## Where things live on disk
### Where does Clawdbot store its data?