Function persistChatMessages

apps/sim/lib/mothership/inbox/executor.ts:356–394

* Persist the user message and assistant response to the copilot chat. * This is necessary because the orchestrator doesn't persist messages — * in the interactive UI flow, the client store handles persistence. * For background execution, we write directly to the DB.

(
  chatId: string,
  userMessageId: string,
  userContent: string,
  result: OrchestratorResult,
  storedAttachments: StoredAttachment[] = []
)

 * For background execution, we write directly to the DB.
 */
async function persistChatMessages(
  chatId: string,
  userMessageId: string,
  userContent: string,
  result: OrchestratorResult,
  storedAttachments: StoredAttachment[] = []
): Promise<void> {
  try {
    const userMessage = buildPersistedUserMessage({
      id: userMessageId,
      content: userContent,
      fileAttachments: storedAttachments.length > 0 ? storedAttachments : undefined,
    })

    const assistantMessage = buildPersistedAssistantMessage(result)

    // Best-effort: the email response is the primary deliverable, so a failure
    // here is logged (in the catch below) rather than failing the task.
    await db.transaction(async (tx) => {
      const [updated] = await tx
        .update(copilotChats)
        .set({ updatedAt: new Date() })
        .where(eq(copilotChats.id, chatId))
        .returning({ model: copilotChats.model })
      if (!updated) return
      await appendCopilotChatMessages(
        chatId,
        [userMessage, assistantMessage],
        { chatModel: updated.model ?? null },
        tx
      )
    })
  } catch (err) {
    logger.error('Failed to persist chat messages', {
      chatId,
      error: getErrorMessage(err, 'Unknown error'),
    })
  }
}

function stripThinkingTags(text: string): string {
  return text