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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 22, 2026 3:13pm

PR Summary

Low Risk
Low risk performance change that limits selected DB columns, with small risk of missing a field if other callers relied on the previous select() behavior.

Overview
Reduces DB load for the legacy copilot chat detail fetch by changing getAccessibleCopilotChat to select an explicit column projection instead of db.select().

Introduces copilotChatLegacyDetailColumns and CopilotChatLegacyDetailRow to keep returning only the fields consumed by the legacy transformChat shape (including model, planArtifact, config) while omitting heavy/unused columns like previewYaml, pinned, and lastSeenAt.

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

Greptile Summary

This PR tightens the DB projection in getAccessibleCopilotChat (the legacy copilot chat detail path) from a full SELECT * to an explicit column list that drops previewYaml (JSONB), pinned, and lastSeenAt. A new copilotChatLegacyDetailColumns constant and CopilotChatLegacyDetailRow type are added to capture the narrowed shape.

• The only production caller (app/api/copilot/chat/queries.ts) passes the result to transformChat, which consumes id, title, model, messages, planArtifact, config, conversationId, resources, createdAt, and updatedAt — all of which remain in the new projection.
• All other callers in the codebase already use the narrower getAccessibleCopilotChatAuth or getAccessibleCopilotChatWithMessages variants and are unaffected.
• CopilotChatLegacyDetailRow is a structural superset of CopilotChatDetailRow, keeping the ChatLoadResult interface and resolveOrCreateChat paths fully compatible.

Confidence Score: 5/5

Safe to merge — the narrowed projection covers every field the single production caller consumes, and unrelated callers use different function variants.

The column set in copilotChatLegacyDetailColumns was cross-checked against every field read by transformChat in queries.ts and all are present. No other call site uses getAccessibleCopilotChat directly. The new CopilotChatLegacyDetailRow type is a strict superset of CopilotChatDetailRow, so existing type boundaries remain sound.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client
    participant GET as GET /api/copilot/chat
    participant LC as lifecycle.ts
    participant DB as copilot_chats

    Client->>GET: "GET ?chatId=..."
    GET->>LC: getAccessibleCopilotChat(chatId, userId)
    LC->>DB: "SELECT id, userId, workflowId, workspaceId, type, title, messages, conversationId, resources, createdAt, updatedAt, model, planArtifact, config WHERE id=? AND userId=? LIMIT 1"
    Note over DB: Drops previewYaml, pinned, lastSeenAt
    DB-->>LC: CopilotChatLegacyDetailRow
    LC->>LC: authorizeCopilotChatRow(chat, ...)
    LC-->>GET: CopilotChatLegacyDetailRow or null
    GET->>GET: transformChat(chat)
    GET-->>Client: "{ success, chat }"

_{Reviews (1): Last reviewed commit: "perf(copilot): narrow getAccessibleCopil..." | Re-trigger Greptile}