Workflow comparison
Reinstate vs. Manual Coding-Agent Session Copying
Manual copying can move any session files you can correctly identify, secure, adapt, and restore. Reinstate automates those steps for supported same-vendor Claude Code and Codex sessions, including structural path remapping, local encryption, credential exclusions, and safer restore behavior. It does not support every format or remove the need for independent backups.
- Last verified
- Current release
- v0.1.0-rc.8
- Release status
- pre-1.0 release candidate
- Owner
- Harjot Singh Rana
The practical difference
A manual workflow puts file discovery, selection, transport security, cross-platform path changes, overwrite policy, and validation in your hands. That control is useful when you know an unsupported format or need a one-off transfer. Reinstate supplies a repeatable workflow for the session layouts and versions it explicitly supports.
This page uses “manual copying” to mean a user-operated transfer of selected local session files. It does not assume a particular copy command, cloud drive, archive format, or security design.
Capability comparison
| Dimension | Reinstate v0.1.0-rc.8 | Manual session copying |
|---|---|---|
| Format scope | Tested Claude Code and Codex session layouts only | Any format the operator can correctly identify and handle |
| Discovery | Adapter discovers supported vendor-native session artifacts | Operator identifies every source file and relationship |
| macOS ↔ Windows paths | Configured canonical project IDs expand to each device's local root | Operator inspects and updates structural paths when required |
| Free-form transcript paths | Left unchanged; only known structural fields are remapped | Depends on the operator's chosen edits |
| Transport payload | Encrypted locally with age before upload to user-owned S3-compatible storage | Depends entirely on the selected archive and transport |
| Credentials | Known auth, credential, token, cache, and log paths are hard-excluded | Operator must decide what to exclude and verify the result |
| Restore preview | pull --dry-run previews the planned restore | Available only if the operator builds a preview step |
| Overwrite protection | Timestamped backups, atomic writes, and explicit conflict records | Depends on the copy tool and procedure |
| Native resume | Restores to the same vendor's native layout for its own resume command | Works if the operator reproduces a valid native layout |
| Independent backup | Still recommended, especially before v1.0 | Operator owns the complete backup and recovery design |
When manual copying can fit
- You need to move a session format Reinstate does not support.
- You fully understand the vendor's current storage layout and portability constraints.
- You want total control over selection, transport, transformation, and restore behavior.
- The transfer is rare enough that maintaining a repeatable workflow is unnecessary.
When Reinstate can fit
- You regularly continue supported Claude Code or Codex work on another device.
- Your project roots differ between macOS and Windows.
- You want selected session artifacts encrypted before they reach remote storage.
- You want adapter-aware discovery, a dry-run, backups, and explicit conflict handling.
Automation narrows the supported surface.
Reinstate does not claim that manual copying is impossible or universally unsafe. A careful operator can recreate some or all of these safeguards. The tradeoff is between manual flexibility and a tested, repeatable workflow for the formats Reinstate supports.
Evidence and verification
Sources below were reviewed on . Reinstate claims describe v0.1.0-rc.8; external workflow claims are limited to what the linked primary sources document.
- Adapter documentationSupported native layouts, project-key handling, same-vendor resume, and hard exclusions.
- Getting startedCurrent push, dry-run, pull, restore, and native resume procedure.
- Security modelage encryption, credential boundaries, timestamped backups, atomic writes, and conflict forks.
- Compatibility matrixCurrent tested agents, versions, operating systems, storage, and release limitations.
Limits of this comparison
- Manual copying is a user-defined workflow, so its security and reliability cannot be scored without inspecting the actual procedure.
- Reinstate supports only documented Claude Code and Codex session layouts in Phase 1; it is not an arbitrary file synchronization tool.
- Neither approach makes a Claude Code transcript natively resumable in Codex, or a Codex rollout natively resumable in Claude Code.