feat(swift-ios): attach images pasted into the composer

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.

[saphid]

Observed problem and reproduction

Paste an image into the native SwiftUI composer with the long-press menu or Cmd-V. Before this work, image-only pasteboards did nothing because SwiftUI cannot observe paste on iOS and UITextView hides its normal Paste entry for image-only content.

The current head also covers related failures found after replacing the editor: marked-text composition could fight external SwiftUI binding changes, rich-text paste could retain attachments or styling, and asynchronous image intake could finish after the composer changed thread or project.

Cause

The composer used a SwiftUI text input with no UIKit paste(_:) hook. Image attachments entered through picker, camera, and Files paths only. Replacing the input exposed ownership gaps around focus, IME reconciliation, paste normalization, task cancellation, and context-scoped result acceptance.

Change and boundary

The composer now uses a UITextView wrapper that offers Paste for image content when the selected model accepts images. Pasted providers use the existing downscale, JPEG re-encode, thumbnail, and FeatureDraftAttachment pipeline. Text-only paste delegates to normal behavior, then restores plain composer styling.

A reconciliation state machine defers external rewrites during marked-text composition. Image intake tasks are keyed to the attachment context, cancelled on context change or disappearance, and rejected if stale. Multiple images preserve order up to the existing eight-image limit and disclose overflow.

Non-goals

No new attachment wire format, server behavior, provider-specific image list, or parallel upload path. Accompanying text from an image-bearing pasteboard is intentionally not inserted because copied images often also carry a URL. React Native mobile, web, and desktop are unchanged.

Affected areas

Affected client: SwiftUI mobile composer in both existing-thread and new-thread flows.

Platforms: iOS simulator and one physical iPhone acceptance record.

Providers: the UI gates paste on the selected model's existing image capability. No adapter changes.

Contracts/connections: existing attachment upload contracts and connection behavior are reused.

Validation

Current head: da648bbd.

• xcodebuild test -only-testing:T3CodeTests on the recorded iOS 26.5 simulator: 291 tests across 33 suites passed, ** TEST SUCCEEDED **, exit 0.
• Focused ComposerImagePasteTests, FeatureComposerPowerTests, and AttachmentPreparationTests: 22 tests across 3 suites passed, exit 0.
• Simulator with live local backend: long-press Paste created an attachment chip; repeated pastes accumulated; removal and send worked; the backend persisted the image as JPEG. Hardware Cmd-V produced the same attachment.
• Recorded physical-device acceptance: internal Test build 94.

Risks, untested paths, and known gaps

• An unresolved Cursor Bugbot thread identifies a real ordinal-collision race after failed intake. A concurrent paste or drop can reuse an ordinal still owned by the first operation. This needs code and concurrency coverage.
• Multi-image single-paste behavior is unit-tested but was not exercised on device.
• The physical iOS one-time Allow Paste prompt was not exercised.
• The branch currently conflicts with its target. It was not rebased in this sweep.
• This contribution is superseded in the personal queue by merged upstream PR feat(swift-ios): paste images from the composer's native menu #7607. No closure or code change was made here.
• Known gaps: no current-head light or dark before/after screenshots; no interaction video; no device proof for a single multi-image paste; no Allow Paste prompt proof; unresolved ordinal-collision code finding.

Evidence

No current-head screenshots or video are embedded. Earlier light-only captures predated the current editor and growth semantics, so they are intentionally not presented as proof of this head.

Owning issue and stack

Owning issue: saphid/t3code-personal#126. This PR targets the open SwiftUI parent branch and depends on #5178 landing. It is not stacked on #7345. The owning queue marks it superseded by merged #7607. Maintainer edits are enabled.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15a893d0-8737-445b-a4cc-89ced43c592c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new feature (image paste support in the composer) with significant new logic including text reconciliation, async task lifecycle management, and paste text normalization. New features with this level of new state management and behavior warrant human review. An unresolved Medium-severity finding about potential ordinal collisions also requires attention.

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

[saphid]

Current-head paste-flow proof — 36621f9

Captured on the canonical proof simulator (B0B16E05-D2DE-4243-B27B-6837D50FDFE6) from the installed Debug app built at PR head 36621f9ac6aa8867689b47533b2bc968fa25e004.

Before every screenshot and the video recording, the simulator reported Booted and the installed T3Code.debug.dylib SHA-256 exactly matched the branch artifact: 30c76d6e73fbdb58ec54129b4295e3ff32e268270f8741de2534f141ad0feda8.

Light mode

Dark mode

Paste-flow video (dark mode)

dark-paste-flow.mp4

The video shows an empty composer receiving the paste and rendering the image attachment tray. Duration: 18.47 seconds.

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Ordinal collision after failed intake

Medium Severity

completeItem frees a pending slot on failure while the in-flight operation still assigns filenames from its original firstOrdinal plus offset. A concurrent paste or drop can then plan the same ordinal, so two attachments both land as the same Image N.jpg.

Additional Locations (2)

• apps/swift-ios/Features/Chat/FeatureComposerView.swift#L550-L577
• apps/swift-ios/Features/Chat/ImageAttachmentViews.swift#L223-L235

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

[saphid]

Closing as superseded. The image-paste behavior shipped via merged #7607.

The surviving real defect—attachment ordinal collisions during failed or concurrent intake—continues as the focused lane saphid/t3code-personal#153, to be fixed as a small PR against current main.