ThinkingJuly 12, 2026
Reindexing has to be triggered, not assumed
Alex OS only re-embeds content when the CMS calls its config-refresh route — a seed script that writes straight to PostgreSQL has to call it manually.
Key takeawayAny future bulk content import needs an explicit reindex step, or newly seeded content will be invisible to the assistant even though it's live on the public site.
Content
The CMS's normal save path calls notifyContentChanged, which pokes Alex OS's /os/config/refresh route to re-pull the corpus and re-embed anything whose content hash changed. A script that inserts rows directly into PostgreSQL — like the seed scripts in this repo — bypasses that path entirely. Alex OS won't know new content exists until something calls that route, or the service restarts.