feat(cozy-search): Use the rag-index triggers as the setup marker - #3147
Merged
Merged
Conversation
Ensuring only the triggers at startup left an instance with triggers firing on every file change and nothing to index until the assistant was opened, since the knowledge base folders come from the provisioned assistants. The triggers are now created last, so their presence means an earlier session went through the whole setup. ensureAssistantsSetup, the startup entry point, stops after that single request when both exist, and runs the whole autoprovisioning otherwise: the folders are indexed before the assistant is ever opened. useRagIndexTriggers and ensureRagIndexTriggers, published in 2.5.0 and used by no app yet, are replaced by useAssistantsSetup and ensureAssistantsSetup.
paultranvan
requested review from
JF-Cozy,
doubleface,
rezk2ll and
zatteo
as code owners
September 21, 2026 14:23
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ensuring only the triggers at startup left an instance with triggers firing on every file change and nothing to index until the assistant was opened, since the knowledge base folders come from the provisioned assistants.
The triggers are now created last, so their presence means an earlier session went through the whole setup. ensureAssistantsSetup, the startup entry point, stops after that single request when both exist, and runs the whole autoprovisioning otherwise: the folders are indexed before the assistant is ever opened.