implement Nova chat attachments on the web side

[ishaanxgupta]

• Added attachment draft/shared types and validation in components/chat/attachments.ts.
• Added paperclip upload UI to Nova composer with file chips, size/status, remove, retry, and per-file Save / Chat only toggle.
• Wired uploads before send to /chat/attachments, then sends returned attachment references in chat message metadata.
• Preserved attachment metadata when loading threads and rendered attachment chips on user messages.
• Added attachment support from the home composer into the full chat view.
• Extended chat analytics with attachment counts.

• ensured responsiveness

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	supermemory-mcp	7095548	Jun 08 2026, 06:20 AM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	supermemory-app	7095548	Commit Preview URL Branch Preview URL	Jun 08 2026, 06:21 AM

[claude]

Claude finished @MaheshtheDev's task in 2m 21s —— View job

---

Reviewing PR #1004: Nova chat attachments

• Fetch PR diff and existing review comments
• Analyze changed files for bugs, security issues, and logic errors
• Read surrounding code for boundary issues
• Submit review with findings

Review submitted. No bugs, security issues, or logic errors found. This is a solid implementation with proper error handling, memory management, and XSS prevention. Score: 9/10.

[claude]

Overview: Implements chat attachment functionality with file uploads, draft state management, save-to-memory toggle, and attachment rendering in messages.

Issues found: None — this looks good to ship.

The implementation is solid:

• File validation checks size (50MB limit) and type before accepting
• Each attachment draft tracks its own upload state (queued → uploading → uploaded/error), enabling granular retry
• uploadAttachmentDraft correctly skips already-uploaded drafts on retry
• State is only cleared on full success (both uploads and sendMessage complete)
• Error handling preserves draft state so users can retry or remove individual failures
• React's automatic text escaping prevents XSS in filename rendering
• The canSend logic correctly blocks sending when uploads are in progress or have errors

Score: 9/10

Minor observations (not blocking):

• Attachments upload sequentially rather than in parallel — likely intentional for server load control
• handleRetryAttachment captures currentChatId at callback creation time, so if a user switches threads before clicking retry, the attachment uploads to the new thread. Edge case, but worth noting.

[claude]

Overview: Implements chat attachment functionality with file uploads, draft state management, save-to-memory toggle, and attachment rendering in messages.

Issues found: None — this looks good to ship.

The implementation is solid:

• File validation checks size (50MB limit) and type before accepting
• Each attachment draft tracks its own upload state (queued → uploading → uploaded/error), enabling granular retry
• uploadAttachmentDraft correctly skips already-uploaded drafts on retry
• State is only cleared on full success (both uploads and sendMessage complete)
• Error handling preserves draft state so users can retry or remove individual failures
• React's automatic text escaping prevents XSS in filename rendering
• The canSend logic correctly blocks sending when uploads are in progress or have errors
• Object URLs are properly cleaned up in useEffect return to prevent memory leaks

Score: 9/10

Minor observations (not blocking):

• Attachments upload sequentially rather than in parallel — likely intentional for server load control
• handleRetryAttachment captures currentChatId at callback creation time, so if a user switches threads before clicking retry, the attachment uploads to the new thread. Edge case, but worth noting.

[claude]

Overview: Implements chat attachment functionality with file uploads, draft state management, save-to-memory toggle, and attachment rendering in messages.

Issues found: None — this looks good to ship.

The implementation is solid:

• File validation checks size (50MB limit) and type before accepting
• Each attachment draft tracks its own upload state (queued → uploading → uploaded/error), enabling granular retry
• uploadAttachmentDraft correctly skips already-uploaded drafts on retry
• State is only cleared on full success (both uploads and sendMessage complete)
• Error handling preserves draft state so users can retry or remove individual failures
• React's automatic text escaping prevents XSS in filename rendering
• The canSend logic correctly blocks sending when uploads are in progress or have errors
• Object URLs are properly cleaned up in useEffect return to prevent memory leaks

Score: 9/10

Minor observations (not blocking):

• Attachments upload sequentially rather than in parallel — likely intentional for server load control
• handleRetryAttachment captures currentChatId at callback creation time, so if a user switches threads before clicking retry, the attachment uploads to the new thread. Edge case, but worth noting.

[claude]

Overview: Implements chat attachment functionality with file uploads, draft state management, save-to-memory toggle, and attachment rendering in messages.

Issues found: None — this looks good to ship.

The implementation is solid:

• File validation checks size (50MB limit) and type before accepting
• Each attachment draft tracks its own upload state (queued → uploading → uploaded/error), enabling granular retry
• uploadAttachmentDraft correctly skips already-uploaded drafts on retry
• State is only cleared on full success (both uploads and sendMessage complete)
• Error handling preserves draft state so users can retry or remove individual failures
• React's automatic text escaping prevents XSS in filename rendering
• The canSend logic correctly blocks sending when uploads are in progress or have errors
• Object URLs are properly cleaned up in useEffect return to prevent memory leaks
• Inflight upload tracking via uploadPromisesRef prevents duplicate upload requests
• Abort controllers are properly cleaned up when attachments are removed
• Discarded draft tracking ensures uploads that complete after removal are cleaned up server-side

Score: 9/10

Minor observations (not blocking):

• Attachments upload sequentially rather than in parallel — likely intentional for server load control
• handleRetryAttachment captures currentChatId at callback creation time, so if a user switches threads before clicking retry, the attachment uploads to the new thread. Edge case, but worth noting.

[claude]

Overview: Implements chat attachment functionality with file uploads, draft state management, save-to-memory toggle, and attachment rendering in messages.

Issues found: None — this looks good to ship.

The implementation is solid:

• File validation checks size (50MB limit) and type before accepting
• Each attachment draft tracks its own upload state (queued → uploading → uploaded/error), enabling granular retry
• uploadAttachmentDraft correctly skips already-uploaded drafts on retry
• State is only cleared on full success (both uploads and sendMessage complete)
• Error handling preserves draft state so users can retry or remove individual failures
• React's automatic text escaping prevents XSS in filename rendering
• The canSend logic correctly blocks sending when uploads are in progress or have errors
• Object URLs are properly cleaned up in useEffect return to prevent memory leaks
• Inflight upload tracking via uploadPromisesRef prevents duplicate upload requests
• Abort controllers are properly cleaned up when attachments are removed
• Discarded draft tracking ensures uploads that complete after removal are cleaned up server-side

Score: 9/10

Minor observations (not blocking):

• Attachments upload sequentially rather than in parallel — likely intentional for server load control
• handleRetryAttachment captures currentChatId at callback creation time, so if a user switches threads before clicking retry, the attachment uploads to the new thread. Edge case, but worth noting.

[claude]

Overview: Implements chat attachment functionality with file uploads, draft state management, save-to-memory toggle, and attachment rendering in messages.

Issues found: None — this looks good to ship.

The implementation is solid:

• File validation checks size (50MB limit) and type before accepting
• Each attachment draft tracks its own upload state (queued → uploading → uploaded/error), enabling granular retry
• uploadAttachmentDraft correctly skips already-uploaded drafts on retry
• State is only cleared on full success (both uploads and sendMessage complete)
• Error handling preserves draft state so users can retry or remove individual failures
• React's automatic text escaping prevents XSS in filename rendering
• The canSend logic correctly blocks sending when uploads are in progress or have errors
• Object URLs are properly cleaned up in useEffect return to prevent memory leaks
• Inflight upload tracking via uploadPromisesRef prevents duplicate upload requests
• Abort controllers are properly cleaned up when attachments are removed
• Discarded draft tracking ensures uploads that complete after removal are cleaned up server-side

Score: 9/10

Minor observations (not blocking):

• Attachments upload sequentially rather than in parallel — likely intentional for server load control
• handleRetryAttachment captures currentChatId at callback creation time, so if a user switches threads before clicking retry, the attachment uploads to the new thread. Edge case, but worth noting.

[MaheshtheDev]

• Grok 4.3, web sources UX, and mobile polish #1064
• implement Nova chat attachments on the web side  #1004 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Merge activity

• Jun 8, 6:17 AM UTC: MaheshtheDev added this pull request to the Graphite merge queue.
• Jun 8, 6:19 AM UTC: Merged by the Graphite merge queue.