Project Info
Inspiration
The hardest part of changing unfamiliar code is reconstructing the decisions accumulated across commits: what changed, which entities interacted, and why the current shape exists. File trees and blame views expose fragments, but they do not tell the feature's story.
What it does
RepoRewind is a desktop developer tool that builds a local timeline of a Git repository. Developers can search code entities, explore function interactions, inspect commits related to an entity, and rewind the map to earlier states.
How we built it
We built RepoRewind collaboratively in Codex with GPT-5.6 Sol. Codex accelerated cross-cutting work like snapshot comparison, repository analytics, and the commit deepdive. It is made with Rust and Tauri with language server support to handle various languages. Challenges and accomplishments The difficult parts were building the timeline and history of repo. Firstly we wanted to make 3D visualizations but it wasn't panning out well and was very noisy. Finally we went with tabular formats. We are proud of the final features to rewind and forward to specific commits.
What's next
Next we would deepen language-server coverage, improve the visual factor with 3D graphics and add macOS and Linux packaging.
RepoRewind
RepoRewind is a Windows desktop application that turns Dart and Kotlin Git history into a rewindable semantic graph. It analyzes repositories in a private cache, never checks out or modifies the selected working tree, and stores all indexes locally.
Download the Windows installer · OpenAI Build Week submission
MVP capabilities
- Native Git working-tree picker and explicit repository trust.
- Dart Analysis Server and checksum-pinned JetBrains Kotlin LSP runtime management.
- Current working-tree graph first, then cancellable newest-first HEAD ancestry indexing.
- Class-like entities connected by language-server call-hierarchy evidence.
- SQLite/WAL metadata with zstd checkpoints and semantic deltas.
- 3D mouse navigation, package clustering, filters, entity search, edge evidence, commit rewind, and paginated related commits.
- Windows x64 NSIS packaging through Tauri 2.
Development
Prerequisites are Node.js, the Rust MSVC toolchain, Visual Studio C++ Build Tools, and WebView2. Dart/Flutter is required to analyze Dart repositories; Kotlin can be installed from the setup screen.
npm install
npm test
npm run tauri build
Indexes and managed runtimes live under %LOCALAPPDATA%\RepoRewind. Dependency restore is permitted only after repository trust and only inside RepoRewind's materialized cache workspaces.
Architecture
The React interface calls a narrow set of Tauri commands. Rust owns Git traversal/materialization, LSP sessions, runtime installation, semantic identity and deltas, checkpoints, SQLite persistence, pagination, and background job cancellation. Historical reconstruction starts from the nearest first-parent checkpoint and applies bounded deltas; incomplete analysis remains explicitly partial.
Judge quick start
RepoRewind supports Windows x64. The fastest path is the prebuilt RepoRewind_0.1.6_x64-setup.exe attached to the GitHub release. Install it, select a local Dart or Kotlin repository with several commits, review the explicit trust prompt, start analysis, select an entity, inspect What changed and Affected code, and rewind from the commit timeline. No account or API key is required, and the selected working tree is not modified.
How Codex and GPT-5.6 were used
RepoRewind was built collaboratively in Codex with GPT-5.6 Sol. Codex accelerated repository-wide work across React, Rust, Git, SQLite, tests, and Windows packaging: diagnosing stale completed indexes using working-tree fingerprints, replacing an unscalable layout with deterministic Barnes-Hut physics in a Web Worker, and tracing Git commit descriptions end-to-end into the story-first inspector.
Human direction set the product constraints: visible connections and readable labels, scalable layout instead of hand-tuned physics, and a clear story before dense technical evidence. See the Codex/GPT-5.6 evidence plan.
Build Week materials
License
RepoRewind is available under the MIT License.
Analysis
View
Metric
No commits on this project resolved to a GitHub account.
Technology
- CSSIn code
- HTMLIn code
- ReactIn code
- RustIn code
- TypeScriptIn code
5 of 5 appear in the indexed code.
AI coding agents
- CodexConfig
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
746 KB
Source files
83
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
Trion129/RepoRewind
114 files · 1.2 MB · @ dc364c5
Structure
Interface
12 files · 11%Screens, components and styles rendered to the user.
Application logic
29 files · 25%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- Rust33%
- Markdown32%
- TypeScript29%
- CSS7%
- HTML0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 24- @tauri-apps/api
- @tauri-apps/plugin-dialog
- @tauri-apps/plugin-fs
- @tauri-apps/plugin-opener
- d3-force-3d
- lucide-react
- ngraph.forcelayout
- ngraph.graph
- react
- react-dom
- react-force-graph-3d
- three
- +12 more
src-tauri/Cargo.toml
cargo · 24- async-trait
- base64
- blake3
- chrono
- futures
- git2
- parking_lot
- reqwest
- rusqlite
- serde
- serde_json
- sha2
- tauri
- tauri-plugin-dialog
- tauri-plugin-opener
- thiserror
- tokio
- url
- +6 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.