rewindry
v0.1.5
Published
Local, immutable checkpoints for visual history of code changes.
Maintainers
Readme
Rewindry
Local visual history for code-driven product iterations.
Rewindry records local source checkpoints as you build. When a supported local Vite preview is available, it also captures a screenshot for the finished checkpoint. Review earlier iterations in a small development timeline or the standalone viewer, inspect historical files and diffs, and copy code without changing your working tree.
Quick start
Requires Node.js 26 or newer. The verified persistent setup target is macOS on Apple silicon.
From the root of your project, run:
npx rewindry@latest setupThen start your app with its usual development command, for example:
npm run devSetup creates a baseline and starts local source capture. In a supported Vite project, it adds a reversible development-only preview integration while preserving your existing dev command. It also detects installed coding agents and merges hooks only for editions with verified integrations. Review any project-trust prompt shown by your agent; Rewindry does not bypass it.
Once the preview is running, use your app and coding tools as usual. Changed, completed turns and groups of local edits become timeline checkpoints. When the dev preview is unavailable, source history can still be reviewed without screenshots.
The preview stays clear while the timeline is closed. Press Alt+Shift+R to open or close it, move the pointer to the bottom-centre trigger to reveal it, or tap the trigger's former position on touch devices. Press Escape to close the timeline.
What you can do
- Browse a timeline of recorded source iterations and available screenshots.
- Inspect historical files and diffs, and copy their contents.
- Review Git history separately from Rewindry checkpoints.
- Continue capturing source while the dev server is stopped.
- Use the standalone viewer when the app preview is unavailable.
The timeline is read-only: it does not restore, revert, apply, or execute historical code. It is a sequence of local browser captures, not a video recording.
Commands
Run these from the project root:
| Command | Description |
| --- | --- |
| npx rewindry@latest setup --dry-run | Preview setup changes without writing files. |
| npx rewindry@latest setup | Install or refresh Rewindry for this project. Safe to rerun. |
| npx rewindry@latest status | Check source capture, workspace registration, and preview configuration. |
| npx rewindry@latest doctor | Show status plus service and capture diagnostics. |
| npx rewindry@latest viewer | Open saved history in the standalone local viewer. |
| npx rewindry@latest setup --rebind-moved | Explicitly register a project after moving its directory. |
| npx rewindry@latest uninstall | Remove this project's Rewindry integrations and service registration; keep its history. |
Compatibility
The current verified setup is macOS arm64 with Node.js 26. The verified preview combination is React 19 with Vite 8.3.4. Other operating systems, Node versions, and framework configurations are not yet verified.
Agent support is edition-specific:
| Agent edition | Current evidence | | --- | --- | | Codex CLI 0.144.4 | Real turn lifecycle and edit capture verified. A project-trust approval may be required. | | Claude Code 2.1.296 | Real turn lifecycle and consecutive edit capture verified. | | Cursor IDE 3.24.9 | Paired lifecycle hooks verified; edit-to-checkpoint capture is still unverified. | | Other editions and agents | Local source changes may be grouped by inactivity, but one checkpoint per prompt is not guaranteed. |
See the compatibility notes for the evidence and caveats behind these claims.
Local data and fidelity
Project history is stored locally in .rewindry/. Rewindry does not require an account or upload project history to a Rewindry cloud service. The history can contain source code, and screenshots can show app data, so treat the project history like other private project files.
Screenshots are fresh renders from your local development preview. Environment variables, remote data, browser storage, and an existing tab's runtime state are not reconstructed. If a screenshot cannot be tied to a stable source state, Rewindry keeps the source checkpoint and reports the visual as unavailable rather than inventing a preview.
Agent prompt boundaries are only available for tested editions. For an unverified agent or an edit without a recognised turn boundary, Rewindry can record grouped local edits, but cannot promise one checkpoint per prompt. Changes in remote or unwatched worktrees are not captured until they appear in the monitored project.
License
MIT. See LICENSE.
