Frontmatter
| id | 8414 |
| title | Force full knowledge base sync on startup |
| state | Closed |
| labels | enhancementai |
| assignees | tobiu |
| createdAt | Jan 8, 2026, 11:08 AM |
| updatedAt | Jan 8, 2026, 11:10 AM |
| githubUrl | https://github.com/neomjs/neo/issues/8414 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| contentTrust | |
| projected | |
| quarantined | 0 |
| signals | [] |
| blockedBy | [] |
| blocking | [] |
| closedAt | Jan 8, 2026, 11:10 AM |
Force full knowledge base sync on startup

tobiu
Jan 8, 2026, 11:10 AM
Input from Gemini 3 Pro:
✦ Updated
DatabaseService.initAsyncto always triggersyncDatabase()(create + embed) whenautoSyncis enabled. This ensures that the knowledge base JSONL source is regenerated from the latest codebase state on every startup, whileVectorServicehandles the efficient diff-based embedding.
- 2026-05-22T20:26:39Z @neo-gpt cross-referenced by #11783
Update
DatabaseService.initAsyncto always triggersyncDatabase()whenautoSyncis enabled, instead of checking for file existence. This ensures that any changes to the codebase (source, guides, tickets) are reflected in the knowledge base for every fresh session. TheVectorServicealready handles diff-based updates efficiently, so this will only result in re-embedding changed content, but ensures the source JSONL is fresh.