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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 29, 2026 7:19pm

PR Summary

Medium Risk
Introduces new server-side write path that duplicates chat data and triggers a downstream service call; failures or incorrect validation could create orphaned/incorrect forked tasks or inconsistent copilot state.

Overview
Adds POST /api/mothership/chats/[chatId]/fork, which validates ownership/workspace access, slices the parent chat’s persisted messages up to a specified message, copies resources/config artifacts, creates a new chat titled … | Fork, and best-effort calls the copilot service to clone server-side conversation state.

Updates the Mothership chat UI to pass messageId into MessageActions and show a new fork button on assistant messages; clicking it calls a new useForkTask mutation, navigates to the new task, invalidates task lists, and emits a new PostHog task_forked event.

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

Greptile Summary

This PR adds a Fork button to every assistant message in the Mothership chat, creating a new chat branched at that message with full state copied (messages, resources, config, previewYaml, planArtifact) and copilot-service conversation state cloned best-effort. The implementation is clean and consistent with existing patterns: session-only auth, ownership + workspace-access guards, standard useMutation + onSettled invalidation, and PostHog analytics.

Confidence Score: 5/5

Safe to merge — no P0/P1 issues found; all previously flagged concerns have been resolved.

All five files follow established project conventions (auth, query patterns, component structure). Previously raised concerns about config copying, fork-of-fork title accumulation, and signal forwarding have been addressed or confirmed as intentional design decisions. No new logic errors or security issues were found.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    actor User
    participant UI as MessageActions (UI)
    participant TQ as TanStack Query (useForkTask)
    participant API as POST /api/mothership/chats/[chatId]/fork
    participant DB as copilotChats DB
    participant CS as Copilot Service
    participant PubSub as taskPubSub

    User->>UI: Clicks GitBranch (Fork) button
    UI->>TQ: mutateAsync({ chatId, upToMessageId })
    TQ->>API: POST /api/mothership/chats/[chatId]/fork
    API->>API: authenticateCopilotRequestSessionOnly()
    API->>DB: SELECT parent chat (verify ownership + type)
    DB-->>API: parent row
    API->>API: slice messages up to forkIdx
    API->>DB: INSERT forked chat row (messages, resources, config, previewYaml...)
    DB-->>API: { id, workspaceId }
    API->>CS: POST /api/chats/fork (best-effort)
    CS-->>API: 200 OK (or error, silently logged)
    API->>PubSub: publishStatusChanged({ type: 'created' })
    API->>API: captureServerEvent('task_forked')
    API-->>TQ: { success: true, id: newId }
    TQ->>TQ: onSettled → invalidateQueries(taskKeys.lists())
    TQ-->>UI: result.id
    UI->>UI: router.push(/workspace/.../task/newId)

_{Reviews (2): Last reviewed commit: "fix(fork): register task_forked PostHog ..." | Re-trigger Greptile}

@greptile

@cursor review