Attach a reference
- Open the destination Code session.
- Choose Add → Reference previous session in the composer.
- Select the source sessions in the picker and attach the selection.
- Review the attached references before sending. Describe the decision, result, or open question you want the agent to use.
- Send the next message and inspect any omission or unavailable-source notice.
The picker excludes the current session. Readable archived Code sessions can be referenced; deleted or purged sources cannot. If a session is missing, check whether it was deleted, whether you are looking at Code rather than Chat history, and whether the source remains readable.
Understand the snapshot
The reference is a bounded context snapshot, not a shared live conversation. The implementation limits narrative history to 120 events and recent history to 40 events, with individual text capped at 1,200 characters. Omission counts help explain why the destination may not have every detail visible in the source transcript.
A source workspace reference does not switch the destination’s active folder. Ask the agent to verify current files in the active workspace before relying on a historical result. If a specific decision is essential, state it directly in the new request instead of assuming it survived truncation.
Choose the appropriate continuation tool
Use a reference for selective context across existing Code sessions. Use provider continuation for an idle Claude Code/Codex linked handoff. Use Import for supported histories created outside Rudr. Native provider history and file rollback have different limits, described in context and history.