A controlled handoff of decisions, sources, and open questions—not an entire conversation export.
Last reviewed:
About this guide
This guide was prepared with AI assistance using the project’s public documentation. It does not claim testing on every device or independent human review. Project publisher: AmirSina Zamanian.
Sources are listed at the end. Use the project repository to report an error or suggest a correction. Report an issue
⌕
Search runs on this device.
On this page
What belongs in a handoff?
Give the second tool the smallest set of information that enables the next decision: current goal, actual state, accepted decision, its source, and next action. Full conversation history can obscure those boundaries. Keep assumptions separate from verified facts in the context pack and mark unsupported claims for review.
Review completed changes, test results, and unfinished work. Do not turn “tests not run” into “tests passed.” After approved recording and sync, inspect the project pack in 09-Exports. The filename depends on the project identifier; do not substitute another project’s example file. Transfer only content you are authorized to send to that specific destination.
Ask the receiving tool to read only the selected pack, summarize the goal and constraints, and report conflicts with current code before making changes. If a decision conflicts with the code, neither should automatically be treated as authoritative. After reconciliation, choose one small testable action. The pack’s local path must be accessible in that environment; knowing its filename does not grant access.
Accept the handoff only when the second tool identifies the correct project, decision, and next action with a source, while leaving unanswered questions open. Record this evaluation separately from successful file copying. The current Wiki lab checks text portability and provenance; actual two-model answer quality and cost reduction remain unmeasured.