gigai-chronicle
an append-only, plain-text ledger of AI-assisted development, inside your own repo
v0.3.0 · 284 dl/30d on npm · 666 installs on open vsx
Git answers what changed; it has never answered what was asked. Chronicle keeps that second history — prompts, attempts, reasoning — travelling by git clone like everything else. No account, no server, no network; it never calls a model.
npm install -g gigai-chronicle
SOURCE ↗ README ↗ ISSUES ↗ RELEASES ↗ NPM ↗ VS CODE ↗ OPEN VSX ↗ MICROSITE
- chronicle why <file>
- the prompt behind each change — the question git blame can't answer
- chronicle restore <evt>
- put code back to the moment before any prompt — always safety-checkpointed
- chronicle replay <session>
- step through prompts, responses, tools and commits, interleaved
- chronicle prompt save
- keep the prompt that worked — versioned, diffable, shared by git
- chronicle knowledge
- the decisions and TODOs buried in your sessions — rule-based, model-free, each with its source line
- chronicle context <file>
- a paste-ready brief of what shaped a file — pure assembly; it never calls a model, it briefs the one you do
- chronicle doctor
- the trust anchor: log integrity, secret audit, proof nothing leaves your machine
- the VS Code extension
- sidebar history, a git-style prompt graph, and 'Why is this file like this?' in the editor
MIT — fork freely, commercially included; we want the tool to travel farther than the studio. Report via issues, propose via discussions, and if you break it, tell us how.
FORK THE SOURCE ↗REPORT AN ISSUE ↗ INDIAN-PII — THE OTHER NPM CITIZEN →THE WORKBENCH — EVERY REGISTRY LINE →