Browse documentation

Current writer default: v4 (requires opentine 0.26+). Legacy v1/v2 files and v3 repositories remain readable. Bare tine migrate now writes a sibling file; use --dry-run for preview only. Read upgrade notes.

Docs target stable release v0.34.0.Stable vs main checked 2026-11-03

Upgrade to v0.34

Terminal
python -m pip install --upgrade "opentine==0.34.0"
tine pricing check
tine pricing show openai gpt-6.1-terra
tine rewind run.tine --json

Pricing snapshot, not guessed history

The signed catalog now has 248 cards. Missing launch/change dates create unknown historical costs; do not backfill current rates into older runs. See model additions and date gaps.

Repository edits are now supported

Since v0.33, --set and --edit-file also edit repository fork-point events. --unset removes a key or list item; PATH[+] appends to a list. The edited event stays unexecuted and its own transcript turns are removed. Edits are bound into the repository run object as fork_overrides.edit. Existing unedited forks retain their identities.

Inspect rewind recovery modes

v0.32 captures first-edit file originals for supported Claude Code and Gemini paths. Rewind can use digest-checked originals or fall back to reconstruction, reporting exact, reconstructed, or skipped. Existing artifacts do not gain originals retroactively, and originals changed by redaction are not written as though they were authentic file content.

Offline timestamps are published

v0.31 adds RFC 3161 sidecars and local-root verification. Token fetching remains external; missing roots are unavailable, and timestamps do not establish run authorship. See the timestamp guide.

Unchanged v4 boundary

Python remains 3.11–3.14. Final files and repositories default to v4 and need readers 0.26+. Bare migrate writes a sibling file; --dry-run previews only. Drafts and warned fallback cases can remain v2. The v4 transition guide covers legacy writers and migration safety.