The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 28, 2026 5:52pm

PR Summary

Medium Risk
Touches send/dispatch, stream handoff, and rehydrate auto-send paths in useChat; mistakes could duplicate sends or drop queue edits, though behavior is covered by new store tests.

Overview
Mothership’s queued messages move from hook-local state into a sessionStorage-backed useMothershipQueueStore, keyed per chat (with a pending::<id> bucket that migrates when a new chat gets a real id). Queues survive navigation/reload within the tab; deleting a task clears that chat’s bucket.

Edit-in-place keeps queue order: editing binds a row to the composer, submit replaces the slot via replaceAt (and strips stale queuedSendHandoff), and cancel edit resumes auto-drain. The dispatcher pauses while the head is being edited, tracks dispatchingHeadId (disables edit/send-now on that row), and honors explicit removes mid-dispatch so failed sends don’t resurrect removed items. A rehydrate kick drains when history shows no active stream.

UI adds in-edit highlighting, cancel edit, and the same queue props on home and workflow copilot. 16 unit tests cover the new store.

^{Reviewed by Cursor Bugbot for commit 036bbb3. Configure here.}

Greptile Summary

This PR lifts the mothership message queue from component-local useState into a new useMothershipQueueStore (Zustand + sessionStorage), keyed by chatId, so the queue survives navigation and page reloads. It also changes edit behaviour so an edited queued message replaces in-place at its original index rather than being removed and re-appended at the tail.

• New useMothershipQueueStore (stores/mothership-queue/) provides enqueue, insertAt, replaceAt, remove, migrate, clearChat, and setEditing, all with unit tests. editing is intentionally excluded from the persisted snapshot so a reloaded tab cannot stall the drain loop.
• use-chat.ts adopts a chatKey/pendingChatKey sentinel pattern, adds dispatchingHeadId React state to gate UI affordances on the in-flight head, and introduces an auto-drain useEffect that kicks the dispatch loop on rehydrate once chatHistory confirms no active stream.
• UI and parity (queued-messages.tsx, mothership-chat.tsx, panel.tsx) wire through editingQueuedId, dispatchingHeadId, and onCancelQueueEdit for both the home chat and the workflow copilot panel.

Confidence Score: 5/5

Safe to merge; the queue persistence and edit-in-place mechanics are well-guarded and the previous-review issues are all resolved.

The core state machine — enqueue, dispatch, restore, migrate, and drain — is carefully gated with epoch checks, synchronous ref guards, and explicit kicks on every edit-resolution path. The one remaining edge case (a concurrent chat-delete racing a failing dispatch) produces a stale sessionStorage bucket that clears on tab close and cannot be re-triggered without navigating back to the deleted chat URL, so it does not affect normal usage or data integrity.

The interaction between restoreQueuedMessage in use-chat.ts and the clearChat calls in tasks.ts is worth a follow-up, but only because the queue is now persistent — the old in-memory queue would have been garbage-collected on navigation.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([User submits message]) --> B{sendingRef?}
    B -- No --> C{pendingStop?}
    C -- No --> D[startSendMessage directly]
    B -- Yes --> E{editingId set?}
    C -- Yes --> E
    E -- Yes, in queue --> F[replaceAt + setEditing null\nenqueueQueueDispatch]
    E -- No / stale --> G[enqueue to store]
    G --> H{pendingStop?}
    H -- Yes --> I[enqueueQueueDispatch send_head]
    H -- No --> J[Wait for notifyTurnEnded kick]
    D --> K([Turn ends / notifyTurnEnded])
    K --> L{queue non-empty?}
    L -- Yes --> M[enqueueQueueDispatch]
    M --> N[dispatchQueuedMessage]
    N --> O{editing head?}
    O -- Yes --> P[pause / continue loop]
    O -- No --> Q[setDispatchingHeadId\nstartSendMessage liveMsg]
    Q --> R{success?}
    R -- Yes --> S[removeQueuedMessage\nclear dispatchingHeadId]
    R -- No --> T{userRemoved?}
    T -- Yes --> U[drop / clear dispatchingHeadId]
    T -- No --> V[restoreQueuedMessage insertAt\nclear dispatchingHeadId]
    W([User cancels edit]) --> X[setEditing null\nenqueueQueueDispatch]
    Y([Page reload]) --> Z[sessionStorage rehydrate\nauto-drain useEffect]
    Z --> M
    AA([Chat deleted]) --> AB[clearChat chatId]
    AB -.->|race if dispatch in flight| V

_{Reviews (3): Last reviewed commit: "fix(mothership): honor user removal duri..." | Re-trigger Greptile}

@greptile

@cursor review

@cursor review

@greptile

@greptile

@cursor review