Move a research task between Claude, Codex and desktop
Move the research state, not an assumption that every host behaves identically. A method can share source instructions while file access, tool permissions, dependency handling and import support differ.
Build a portable handoff
| Handoff item | Include | Keep private |
|---|---|---|
| Method | ID, package version and license | Credentials |
| Inputs | Filenames, digests and permitted copies | Unnecessary holdings/accounts |
| Scope | Cutoff, periods, unresolved questions | Unrelated personal documents |
| Output | Reports and calculation artifacts | Provider tokens |
| Evidence | Expected and actual checkpoints | Full private chat unless needed |
A handoff folder might contain input-manifest.md, question.md, reports/run-001/ and handoff.md. The last file says which work is complete, what failed and what remains to verify. Keep input and output separate from host-specific installation folders.
Worked transfer
Suppose Claude produced the fictional cash-flow comparison, and you want Codex to verify it. Transfer the same permitted inputs and evidence table. Ask Codex to recompute 92/132=69.70% and trace both original values. Similar prose is not required; identical source scope and correct arithmetic are.
For an ETF experiment, use the same confirmed rule, data digest, calendar and calculation version. Compare daily values and events, not only the rounded final return. A version change can require a new test.
For current 0.1.0 A-batch tool reproduction, S01/S02/S04/S05 all need Python 3.12 at the destination. Their teaching tools use the standard library without network or third-party Python packages. Check the actual isolated environment; if unavailable, stop tool execution and retain the incomplete status. Reading an old report without that tool is still report continuation, not reproduced execution. Host/model network use is separate.
Discovery is host-specific
Use Claude Code documentation or Codex CLI documentation. OpenAI’s skills documentation and Claude’s official guide describe their own mechanisms. Discovery in one host does not certify another.
CoTrading desktop has its own release and import mechanisms. Until the specific release is verified, use the manual continuation guide: retain files and provide permitted context through an actually available workflow. Do not copy CLI folders into an assumed desktop directory or treat a planned one-click button as supported.
Cost and privacy boundary
Free method packages do not include all host/model charges. Moving a file to a different model changes who may process it; check settings and rights again. This website does not collect your research folder. No transfer in this article starts trading or background monitoring.
Verify before calling the handoff complete
Record host versions, package version, readable inputs, successful explicit selection, actual output and any tool errors. If the destination only reads the report, describe that as report continuation, not a reproduced calculation.
FAQ
Must both hosts write identical prose?
No. Compare evidence, scope and numeric artifacts rather than wording.
Does a portable folder prove desktop import support?
No. Import support is release-specific and needs its own verification.