Preserve connecting status while a turn starts#4101
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
ApprovabilityVerdict: Approved Small, focused fix to preserve 'starting' status during turn initialization rather than briefly showing 'ready'. Changes are limited to status mapping logic with clear intent and minimal risk. You can customize Macroscope's approvability policy. Learn more. |
What Changed
Preserve the connecting thread status while provider readiness arrives with a turn start still pending. The thread transitions directly to working once the turn starts instead of briefly appearing inactive.
Why
Status-grouped thread lists currently jump between sections during provider startup because readiness temporarily exposes an idle state.
Fixes #4099
Verification
Checklist
Note
Preserve "connecting" status during turn start in provider session orchestration
"starting"instead of"ready"to avoid a brief flash of the connected state before the turn begins.ProviderCommandReactor.ts,ensureSessionForThreadaccepts a newpendingTurnStartflag; theturn.starthandler passes this flag to trigger the status override.ProviderRuntimeIngestion.ts,session.state.changed,session.started, andthread.startedevents checkprojectionTurnRepository.getPendingTurnStartByThreadIdand emit"starting"instead of"ready"when a pending turn start exists.Macroscope summarized bb2e8be.