GeezerVison

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 15, 2026 11:34pm

PR Summary

Medium Risk
Touches core chat streaming/stop behavior and client cache synchronization; regressions could surface as missing/duplicated messages or stuck queued sends. Changes are covered by new unit tests for transcript synthesis and stop-route behavior.

Overview
Chat fetch endpoints now return an effective transcript by normalizing persisted messages and synthesizing the in-flight assistant response from Redis stream snapshots (buildEffectiveChatTranscript), avoiding missing/duplicated tails while a conversation is active.

The home useChat streaming flow is refactored to write live SSE updates into the React Query chat detail cache (with a pendingMessages fallback) and introduces a sessionStorage-backed queued-send handoff so queued messages survive stop/reload/navigate scenarios without getting stuck.

Stopping a chat stream now always clears conversationId and can append a synthesized cancelled assistant message (with stable generateId IDs and stopped/complete:cancelled blocks), plus adds shared tooling for interpreting cancelled tool outcomes and expands allowed resource attachment types (incl. log/task/generic).

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

Greptile Summary

This PR fixes two related chat streaming bugs: (1) when a chat is active, the API now returns an effective transcript that splices the live Redis-backed stream snapshot into the persisted message list via buildEffectiveChatTranscript, so the client always gets an up-to-date view on refetch; and (2) the stop route now unconditionally appends a cancelled assistant message (with a synthesized { type: 'stopped' } block) regardless of whether partial content was accumulated.

A significant client-side refactor moves streaming updates from a local setMessages state into the React Query cache via a new upsertTaskChatHistory helper, aligning the server and client views. handleTaskStatusEvent also drops the now-redundant detail-query invalidation on SSE completion, relying on the finalize path instead. Finally, task, log, and generic resource types are added to the chat-post schema, fixing the "log resource left chat hanging" regression.

Confidence Score: 5/5

Safe to merge — no P0/P1 issues found across any changed file.

All findings are P2 or lower. The core logic in buildEffectiveChatTranscript, the stop-route cancelled-block synthesis, and the React Query cache migration are all verifiably correct after tracing through normalizeMessage. New test files provide solid coverage for the new modules. The handleTaskStatusEvent narrowing (list-only, workspace-scoped) is safe because the workspaceId guard in useTaskEvents ensures the function is always called with a defined string.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant C as Client (useChat)
    participant RQ as React Query Cache
    participant API as API Route
    participant Redis as Redis (stream snapshot)
    participant DB as Database

    C->>RQ: cancelQueries(detail)
    C->>RQ: upsertTaskChatHistory (optimistic user + assistant)
    C->>API: POST /api/mothership/chat (send message)
    API-->>C: SSE stream begins

    loop During streaming
        C->>RQ: upsertTaskChatHistory (flush: update assistant snapshot)
    end

    API->>Redis: write stream events
    API->>DB: persist final messages
    API-->>C: stream complete

    C->>C: finalize() → invalidateChatQueries
    C->>API: GET /api/mothership/chats/{chatId}
    API->>DB: fetch chat + conversationId
    API->>Redis: fetch streamSnapshot
    API->>API: buildEffectiveChatTranscript(messages, snapshot)
    API-->>C: effective transcript (persisted + live tail)
    C->>RQ: update cache with server response

    Note over C,RQ: SSE task_status → only list key invalidated (not detail)

_{Reviews (2): Last reviewed commit: "address comments" | Re-trigger Greptile}

bugbot run

@greptile