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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 8, 2026 3:25am

@BugBot review

PR Summary

Low Risk
Low risk UI-only change that adds client-side clipboard copying to rendered markdown code blocks; main risk is minor UX issues if navigator.clipboard is unavailable or denied.

Overview
Adds a reusable CopyCodeButton that copies code to the clipboard and shows a temporary success state.

Updates both chat markdown renderers (markdown-renderer.tsx and chat-content.tsx) to display this button in code block headers, and introduces a shared extractTextContent utility to reliably derive plain text from React node code content.

^{Reviewed by Cursor Bugbot for commit 6ed3bcc. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

This PR adds a reusable CopyCodeButton component and wires it into both the public chat markdown renderer (markdown-renderer.tsx) and the workspace chat content renderer (chat-content.tsx), giving users a one-click way to copy fenced code blocks.

Key findings:

• P1 — Unhandled clipboard Promise (copy-code-button.tsx): navigator.clipboard.writeText(code) is not awaited. setCopied(true) fires unconditionally, so the "✓ Copied" indicator appears even when the write fails (e.g. browser permissions denied, page not focused).
• P2 — Invisible hover state (chat-content.tsx): The CopyCodeButton receives hover:bg-[var(--surface-4)], which is the same token used by its parent container, so the hover effect produces no visible change.
• P2 — extractTextContent duplicated across two files: An identical helper is now defined independently in both markdown-renderer.tsx and chat-content.tsx. Per project guidelines, shared helpers needed by 2+ files should be extracted into a shared utils.ts.
• P2 — setTimeout not cleaned up on unmount: The timer handle is discarded; clearing it in a useEffect cleanup would prevent the state update from firing after the component unmounts.

Confidence Score: 4/5

Safe to merge after fixing the unhandled clipboard Promise, which causes a misleading success indicator on write failure.

One P1 issue: the clipboard write is not awaited, so the copy-success UI fires regardless of whether the write actually succeeded. This is a real, reproducible behaviour defect on the primary user path of the feature. The remaining findings are P2 quality/style items that do not block correctness.

apps/sim/components/ui/copy-code-button.tsx — fix async clipboard handling before merging.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant CopyCodeButton
    participant Clipboard as navigator.clipboard
    participant Timer as setTimeout

    User->>CopyCodeButton: click
    CopyCodeButton->>Clipboard: writeText(code) [Promise, not awaited]
    CopyCodeButton->>CopyCodeButton: setCopied(true) [fires immediately, regardless of result]
    CopyCodeButton->>Timer: setTimeout(setCopied(false), 2000)
    Note over Clipboard: Write may succeed or fail silently
    Timer-->>CopyCodeButton: setCopied(false) after 2s
    Note over CopyCodeButton: If component unmounts before 2s,<br/>timer fires on unmounted component

_{Reviews (1): Last reviewed commit: "Handle react node case for copy" | Re-trigger Greptile}