Engineering notes
Blog
The Reinstate blog explains the engineering boundaries behind coding-agent continuity. Articles distinguish current stable behavior from roadmap work and link claims to the implementation, documentation, or release evidence.
- Last verified
- Current release
- v0.6.0
- Release status
- v0.6.0 stable · native Windows x64 tagged-artifact acceptance PASS (215/215 required rows, docs/testing/results/2026-09-09-windows-v060rc8.md) under the single-platform waiver (ADR 0005) · Apple Silicon macOS acceptance deferred to #403 · supersedes v0.5.1
- Owner
- Harjot Singh Rana
Latest articles
engineering · Aug 27, 2026
The transcript is not the session
Your session file survives the crash. That is not the same as being able to continue, because a session is a transcript plus the conditions it ran under.
Read article →engineering · Jul 27, 2026
Why Git Alone Does Not Sync Coding-Agent Sessions
Git preserves source history, but coding-agent continuity also depends on local conversations, tool context, vendor layouts, paths, and safe restore.
Read article →The editorial contract
Product claims are tied to a visible review date and the current release status. Current, planned, and experimental capabilities are labeled separately. Reinstate does not publish fabricated benchmarks, ratings, compatibility results, or cross-agent fidelity claims.