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-rc.6
- Release status
- v0.6.0-rc.6 candidate · stable remains v0.5.1 · v0.6.0-rc.5 tagged Windows run (plus two same-artifact rechecks) ended FAIL (211/4/0/0 of 215), zero product defects, grok:E1-E3 live-backend-connectivity plus a grok version drift to 1.0.13 and an H7 digest-equality-unmeasurable gap the four PARTIAL rows · this candidate widens the verified Grok Build range to 1.0.13 and refines the H7 live-home check to per-file listing with attribution · native Windows tagged-artifact acceptance pending, macOS deferred
- 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.