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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 8, 2026 8:02pm

PR Summary

Medium Risk
Large cross-cutting rename touches routing, React Query keys, and many API/UI call sites; behavior is intended to be equivalent with wire-compat for live events, but URL and import changes warrant regression on chat CRUD, streaming, and sidebar SSE updates.

Overview
Renames the Mothership workspace task UX and code to chat: the app route moves from /workspace/:workspaceId/task/:chatId to /workspace/:workspaceId/chat/:chatId, with a permanent Next.js redirect for old links.

API and client layers swap mothership-tasks contracts and queries/tasks for mothership-chats / mothership-chats hooks (useMothershipChats, mothershipChatKeys, etc.), distinct from deployed-chat hooks to avoid React Query key clashes. Sidebar, search, home chat flow, fork, and folder selection follow the new names (useChatSelection, clearChatSelection).

Realtime status moves from lib/copilot/tasks (taskPubSub) to lib/copilot/chat-status (chatPubSub); Redis channel task:status_changed and SSE task_status are unchanged for rolling-deploy compatibility. Server deeplinks (OAuth return, inbox emails, inbox list) now use /chat/.

Wire analytics, resource type 'task', and unrelated inbox/scheduled-task features are intentionally left as-is per the PR description.

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

Greptile Summary

This is a thorough rename/refactor moving the Mothership "task" feature to "chat" across 57 files — route, hooks, contracts, store, components, and server-side URL generators — while carefully preserving backward-compatible wire values (Redis channel task:status_changed, SSE label task_status, drag discriminants, PostHog event names) for rolling-deploy safety.

• The /workspace/:workspaceId/task/:chatId → /workspace/:workspaceId/chat/:chatId permanent redirect is correctly wired in next.config.ts, and all server-generated deep-links (OAuth callback, inbox email response, inbox list) have been updated to the new path.
• The React Query cache-key family is renamed to mothership-chat-*, deliberately distinct from the existing deployed-chat family in queries/chats.ts, preventing cache-key collisions.
• The lib/copilot/tasks.ts → chat-status.ts rename uses a new _chatStatusChannel global key while keeping the same Redis channel identifier, so old and new pods interoperate cleanly during a rolling deploy.

Confidence Score: 5/5

Safe to merge — this is a purely mechanical rename with no behavior changes on any hot path.

Every renamed symbol has been updated consistently across routes, hooks, stores, contracts, and tests. Wire-level identifiers (Redis channel, SSE label, drag discriminants, analytics events) are intentionally preserved, and the permanent redirect in next.config.ts protects existing bookmarks. Type-check and test suite pass cleanly. The only finding is a cosmetic stale string in the search-modal filter key.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Old URL\n/workspace/:wid/task/:chatId"] -->|"permanent redirect\n(next.config.ts)"| B["New URL\n/workspace/:wid/chat/:chatId"]

    subgraph "React Query Cache"
        C["mothership-chat-* keys\n(mothership-chats.ts)"]
        D["chat-* keys\n(queries/chats.ts)"]
    end

    subgraph "Pub/Sub (preserved for rolling deploy)"
        E["Redis channel: task:status_changed"]
        F["SSE label: task_status"]
        E --> F
    end

    subgraph "Renamed"
        G["tasks.ts → mothership-chats.ts"]
        H["lib/copilot/tasks.ts → chat-status.ts"]
        I["use-task-events → use-mothership-chat-events"]
        J["use-task-selection → use-chat-selection"]
        K["store: selectedTasks → selectedChats"]
    end

    B --> C
    C -.->|"no collision"| D

_{Reviews (2): Last reviewed commit: "refactor(mothership-chats): use skipToke..." | Re-trigger Greptile}

@greptile

@cursor review