Upstream PR: LibreChat-AI#16632
Finding: LibreChat-AI#16632 (comment)
A follow-up queued during the first turn of a new chat stays keyed under NEW_CONVO. When the user leaves before that turn finishes and returns, the detached run is recorded under the resolved conversation id, but the reconstructed RunEnd has no startedAsNewConvo, so useQueueDrain neither migrates nor drains the NEW_CONVO queue. Behavior matches the pre-LibreChat-AI#16632 baseline (manual send), and LibreChat-AI#16632 lists new-conversation runs as a non-goal.
A fix would carry the run's new-conversation origin into DetachedRun and the reconstructed end. It needs care: after leaving to /c/new, the NEW_CONVO queue is the one the new-chat composer shows, so migrating it on return must not take items the user queued for a different new chat.
Upstream PR: LibreChat-AI#16632
Finding: LibreChat-AI#16632 (comment)
A follow-up queued during the first turn of a new chat stays keyed under
NEW_CONVO. When the user leaves before that turn finishes and returns, the detached run is recorded under the resolved conversation id, but the reconstructedRunEndhas nostartedAsNewConvo, souseQueueDrainneither migrates nor drains theNEW_CONVOqueue. Behavior matches the pre-LibreChat-AI#16632 baseline (manual send), and LibreChat-AI#16632 lists new-conversation runs as a non-goal.A fix would carry the run's new-conversation origin into
DetachedRunand the reconstructed end. It needs care: after leaving to/c/new, theNEW_CONVOqueue is the one the new-chat composer shows, so migrating it on return must not take items the user queued for a different new chat.