feat(mobile): upload attachments while composing

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

What Changed

Mobile uploads images and files over HTTP as soon as they are attached to a connected environment. Composer thumbnails show progress and retry, with at most three concurrent uploads. Send reuses completed uploads and refreshes expired ones from the local copy.

Local image data and owned files stay with drafts and queued messages. Cloud sign-out saves relay drafts and the outbox under their account, then restores them before that account reconnects. This uses the existing Expo file APIs and server endpoints; no new native dependency or rebuild is needed.

Why

Mobile previously waited until Send to upload files and sent images inline. Uploading while composing removes that wait without making drafts depend on connectivity. Local copies remain available offline and survive app restarts and sign-out. Older servers keep the inline-image fallback.

UI Changes

The demo opens a saved PDF after an offline app restart, then shows the composer after reconnecting. Both attachments uploaded before Send, and their server bytes matched the originals. The idle wait is omitted.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/90e07f8e31875d08/offline-and-reconnected-demo.mp4

Before reconnecting	After reconnecting, before Send

Local PDF preview after restarting offline

Validation

• 96 focused tests pass for uploads, cancellation, retries, concurrency, draft persistence, outbox delivery, and account-specific restoration.
• Mobile typecheck and lint of changed files pass.
• iPhone 17 Pro Simulator, iOS 27: offline attachment creation, app restart, local PDF preview, and automatic upload on reconnect. Server files matched the original SHA-256 hashes.
• Cloud sign-out retention was covered by storage tests; live cloud sign-out and Android were not exercised.

Checklist

• Scope limited to mobile attachment uploads and local retention
• Explained the change and why
• Included screenshots of the offline and connected states
• Included an interaction demo

---

Note

Medium Risk
Changes span cloud auth transitions, durable draft/outbox persistence, and send-time attachment preparation; regressions could lose drafts on sign-out or block sends incorrectly, but behavior is heavily covered by new tests.

Overview
Mobile composer attachments now upload in the background while you draft, instead of waiting until Send. A global worker (hosted next to the thread outbox drain) syncs draft attachments for connected environments into a bounded queue (max three concurrent transfers), persists upload IDs back onto drafts, and survives navigation away from the composer.

UI and send gating:ComposerAttachmentStrip shows per-thumbnail progress, percentage, and tap-to-retry on failure. Thread composer, new-task flow, and thread send paths block Send/Start when online until uploads finish or failures are retried/removed; offline queuing is unchanged.

Upload pipeline:prepareTurnAttachments gains abortable HTTP uploads with progress, image upload when the server supports attachmentUploads (temp cache file from dataUrl, with inline-image fallback on older servers), reuse/re-upload of expired pending IDs for both files and images, and stamped uploadedAttachmentId on image drafts.

Cloud account lifecycle: Sign-out runs removeCloudEnvironments, which archives relay-environment drafts and queued outbox messages under the owning account before removing environments; sign-in restores them and reconciles delivered messages against the archive. Attachment file/upload cleanup respects signed-out snapshots so local bytes are not deleted prematurely.

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

Note

Add background attachment uploads to mobile composer with cloud draft preservation

• Introduces a bounded-concurrency upload queue (max 3) in composerAttachmentUploadQueue.ts that uploads images and files over HTTP when the server supports it, with per-attachment progress, abort, and retry
• Adds a long-lived worker hook useComposerAttachmentUploadWorker in composer-attachment-uploads.ts that reconciles the queue against current drafts and connection state, persists uploaded references back into drafts, and keeps previews usable during transfers
• Stamps uploadedAttachmentId/uploadEnvironmentId onto image drafts in attachmentUpload.ts and composer-image-schema.ts, enabling reuse of previously uploaded ids on the same environment and reupload when expired
• Blocks sending in use-thread-composer-state.ts, ThreadComposer.tsx, and NewTaskDraftScreen.tsx while uploads are in-progress or failed; thumbnails in ComposerAttachmentStrip.tsx show progress overlays and retry controls
• On cloud sign-out, archives drafts and queued messages per-account in use-composer-drafts.ts via archiveCloudComposerDrafts; on sign-in, restores them via restoreCloudComposerDrafts in CloudAuthProvider.tsx
• Risk: prepareTurnAttachments in attachmentUpload.ts now validates image mime types against PROVIDER_SEND_TURN_SUPPORTED_IMAGE_MIME_TYPES and throws on unsupported types; older servers without upload support continue to receive inline images, but any caller passing unsupported image types will now fail at upload time

^{Macroscope summarized 312dc46.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+13 B (+0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	−1 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+14 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	11	11	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+4 B (+0.0%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+3 B (+0.0%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	11	11	0 (0.0%)	21	✅

Baseline: 85b656f · PR result: 312dc46 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial mobile workflow for automatic background attachment uploads, offline persistence, queued-message handling, and account-specific cloud draft restoration. It also changes the default composing behavior and touches authentication lifecycle code, so the scope and side effects require human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

</antml the="" parameter="">

^{Posted via Macroscope — Effect Service Conventions}