Privacy choices

This site may send the owner a minimal page-visit notice with page, browser, device type, and resolution. If you accept analytics, it can also remember an anonymous visit/session ID and collect richer engagement signals.

Read the privacy notice
AlexPersonal Operating System
Alex OS Online
Back to Signals
LinkedIn
SignalJuly 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 MySQL has to call it manually.

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 MySQL — 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.

alex-osindexingseeding
Internal Links
ThinkingRelatedForce Alex OS to reindex after a direct DB writeDiscovery and its operational guide.

Explore with Alex OS

Direct MySQL writes bypass Alex OS's reindex trigger — you have to call the refresh route yourself.

Reindexing has to be triggered, not assumed

Alex OS re-embeds content only when its `/os/config/refresh` route is called. The CMS handles this automatically via `notifyContentChanged` on every normal save. Seed scripts that write rows straight to MySQL skip that path entirely — Alex OS stays unaware of the new content until something explicitly hits that route, or the service restarts. If you're seeding data, you need to call the refresh route manually at the end of the script.