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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 16, 2026 6:53am

PR Summary

Medium Risk
Moderate risk due to changes in core chat input/queue editing flow (including file/context restoration) and altered PostHog session recording behavior, which could impact UX or privacy expectations if misconfigured.

Overview
Improves queued-message editing in the workspace chat by letting UserInput load a queued message (text, contexts, and file attachments) via an imperative handle, adding an ArrowUp shortcut to edit the most recent queued item, and enhancing the queued list to render mentions/truncation correctly and show attachment indicators.

Optimizes the landing experience for Core Web Vitals/accessibility by converting AuthModal/DemoRequestModal to dynamic imports across landing sections, tightening navbar session reads to use SessionContext, adding missing ARIA labels and inert usage, and updating a few footer/link alt/labels.

Updates analytics config to disable PostHog session recording by default and only start recording after a user session is identified.

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

Greptile Summary

This PR bundles two improvements: (1) a fix for the Mothership queued-message edit flow so that file attachments and context mentions are properly restored when a queued message is pulled back into the input, and (2) a set of landing-page Core Web Vitals / accessibility improvements (lazy-loading modals with next/dynamic, switching Navbar to consume SessionContext instead of calling useSession, disabling PostHog session recording by default with opt-in for authenticated users, and several a11y fixes).

The queued-message fix uses forwardRef + useImperativeHandle to expose a loadQueuedMessage imperative handle on UserInput, cleanly replacing the previous string-based editValue prop that discarded attachments and context.

Confidence Score: 5/5

Safe to merge — the queued-message attachment fix is well-architected and the landing optimisations are straightforward.

All findings are P2 (one missing typeof guard that is already inside a try/catch). No data loss, no broken paths, no security issues.

apps/sim/app/_shell/providers/session-provider.tsx — minor defensive guard missing around sessionRecordingStarted().

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant QueuedMessages
    participant MothershipChat
    participant Store as home.tsx / panel.tsx store
    participant UserInput

    User->>QueuedMessages: click ✏️ edit
    QueuedMessages->>MothershipChat: onEdit(id)
    MothershipChat->>Store: onEditQueuedMessage(id)
    Note over Store: removes message from queue,<br/>returns QueuedMessage
    Store-->>MothershipChat: QueuedMessage { content, fileAttachments, contexts }
    MothershipChat->>UserInput: userInputRef.loadQueuedMessage(msg)
    UserInput->>UserInput: setValue(msg.content)
    UserInput->>useFileAttachments: restoreAttachedFiles(msg.fileAttachments)
    UserInput->>useContextManagement: setSelectedContexts(msg.contexts)
    UserInput->>textarea: focus() + setSelectionRange(end, end)

    Note over UserInput: ArrowUp (empty input) also<br/>triggers edit of tail message

_{Reviews (1): Last reviewed commit: "improvement(landing): optimize core web ..." | Re-trigger Greptile}