Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: unavailable · PR result: Scenario and decoded snapshot size10 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.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — This PR adds a new iOS workflow that rewinds server conversation history, copies attachments for recovery, and coordinates asynchronous command confirmation and draft restoration. Its production-side effects and cross-layer state management are substantial enough to require human review. You can add or adjust custom eligibility rules. Learn more. |
ca3fafe to
fabe2b0
Compare
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
84dfa1b to
cea8809
Compare
cea8809 to
a777440
Compare
SwiftUI could not edit an earlier prompt while keeping file changes.
Add "Edit from here" to completed user messages and "Edit last prompt" to the thread menu. The confirmation keeps workspace files unchanged. A separate conversation-revert command lets older servers reject the action safely.
Save the prompt and copied attachments before rewind deletes their server copies. Wait for a completion event after command acceptance and confirm the final history with a server read. Then append the recovered input to the existing draft. Block sends for that thread during rewind, including across navigation. Keep the selected model and workspace.
Keep captured context and pasted-text attachment sources through recovery and resend. Context links stay unchanged, while their records point to the new attachment copies. Check the combined context limit before changing history.
If the reply is lost, keep a durable recovery draft across app restart. "Recover saved prompt" restores that input locally without sending another rewind. Recovery cannot consume a backup with missing attachment files.
The central native run passed 117 tests with no failures, covering conversation rewind, root state, and draft storage. Tests include command and checkpoint boundaries, failure events, send locking, app restart recovery, context and attachment sources on resend, and missing or incomplete attachment files. CI passes. UI evidence is being collected centrally with the other SwiftUI parity changes. No real thread was used for rewind verification.
Created with Codex.