If a provider switch is refused
- Confirm the source is a Claude Code or Codex session and the destination is the other member of that pair.
- Wait until the current run has stopped or completed. Rudr cannot migrate a running provider process.
- Verify the destination harness is installed, enabled, authenticated, and ready for its selected model.
- Review any draft or queued-prompt confirmation before proceeding.
Other harnesses remain choices for new sessions. Disabling a harness or changing a default does not convert a retained session into a supported switch.
If the destination fails
Keep the source session and workspace intact. Inspect the source and any linked destination in the sidebar, read the latest error, and check whether the next message was actually sent. A handoff supplies bounded source context on the next message; creating the destination alone is not a completed agent run.
If submission acceptance is uncertain, review activity and file changes before sending the same instruction again. Repeated mutating requests can duplicate work. Restore or edit recovered drafts only after confirming the target folder and provider.
If context seems missing
A linked transcript and a model’s actual context are different. Long prior histories are bounded, individual events can be shortened, and missing or deleted reference sources cannot be read. State the essential decision or next action in the new message and ask the destination to verify current files.
Use previous-session references for selective context, Import for supported external histories, and context/history for qualified native operations. File restoration is separate from conversation recovery and never promises a whole-repository rollback.
For a report, include the source/destination harnesses, idle/running state, whether a linked destination exists, and sanitized errors. Preserve drafts and current Git changes while collecting diagnostics.