Open source

Reinstate Is Open Source Under Apache-2.0

Reinstate is fully open source under the Apache License 2.0. Its Go source, tests, security model, release automation, roadmap, and issue tracker are public, so developers can inspect the continuity layer that handles their sensitive coding-agent sessions.

Last verified: July 27, 2026
Current release: v0.1.0-rc.8
Release status: pre-1.0 release candidate
Owner: Harjot Singh Rana

Project facts

License: Apache-2.0
Language: Go
Repository: GitHub
CLI: rein or reinstate
Maintainer: Harjot Singh Rana
Contribution status: Issues and pull requests welcome

Why a continuity layer should be inspectable

Coding-agent transcripts can contain source code, design decisions, internal paths, and sensitive terminal output. Reinstate sits between those local files and remote object storage. Publishing the implementation lets users verify what adapters select, which paths are excluded, where encryption happens, and how restores avoid overwriting local history.

Open source makes independent review possible; it does not prove the absence of vulnerabilities. RC8 has not claimed a formal third-party audit, so use the documented threat model and your own risk assessment for sensitive work.

Where to inspect the implementation

Repository area	Responsibility
`cmd/reinstate`	CLI entry point
`internal/adapter`	Claude Code and Codex local session discovery and restore adapters
`internal/crypto`	age encryption and secret-input handling
`internal/pathmap`	Portable Windows ↔ macOS structural path rewriting
`internal/sync`	Push, pull, manifests, artifacts, and conflicts
`testdata`	Deterministic synthetic fixtures rather than real transcripts
`docs`	Architecture, security, compatibility, product boundaries, and runbooks

Build and test locally

The project targets Go 1.25.12 or newer. Clone the repository, then use the maintained Make targets:

make build creates bin/reinstate and the short rein alias.
make test runs the test suite.
make vet runs Go's static checks.
make verify runs the broader local verification gate.

Unit tests do not depend on live networks without fakes, and committed session fixtures must remain deterministic, synthetic, and secret-scanned.

How to contribute

Read the roadmap and product strategy so a proposal fits the continuity-layer boundary.
Open or join an issue before a large change; small, reviewable pull requests are preferred.
Add table-driven tests for Go behavior and avoid live network dependencies in unit tests.
Update user documentation and the unreleased changelog when a change affects the CLI or web experience.
Never commit real transcripts, API keys, passphrases, session credentials, or private compatibility evidence.

Start with the repository'scontribution guide and open issues.

What Apache-2.0 means here

Apache-2.0 permits use, modification, and distribution under its conditions and includes an express patent-license grant. The repository'sLICENSE file is the authoritative legal text; this page is a project overview, not legal advice.