Lightning rebuilds conversation histories from previous conversation turns, instead of using the history key returned by Apollo. This means that RAG is not re-triggered when a user navigates from one step to another. Check the impact of this (if it's just general documentation, it might not be too bad) and consider giving job_chat access to the documentation tool the planner already uses instead.
Lightning rebuilds conversation histories from previous conversation turns, instead of using the history key returned by Apollo. This means that RAG is not re-triggered when a user navigates from one step to another. Check the impact of this (if it's just general documentation, it might not be too bad) and consider giving job_chat access to the documentation tool the planner already uses instead.