Skip to content

Chronicle Documentation

Chronicle is a local-first time machine for AI coding sessions. It imports the conversation logs your AI coding assistants already write, and maps every message to the exact state of your code at that moment — reconstructed from your project's Git history. Click any message, and travel back to the code as it was.

Everything runs on your machine. There are no LLM calls anywhere, no cloud backend, and your source logs and project repos are never written to. Chronicle observes and organizes your AI tools; it never replaces them.

Chronicle imports from six tools today — Claude Code, Codex, Cursor, OpenCode, Gemini CLI, and GitHub Copilot Chat — and unifies their sessions into a single, path-based project view.

New here? Jump to the Quickstart and reach your first time-travel moment in under five minutes.

The three pillars

Chronicle's design philosophy is Replay · Control · Secure:

  • ReplayTime Travel over any session, a deterministic Replay sandbox, Refine for distilling a session into docs or a reusable prompt, and Context Causality linking what the AI read to what it changed.
  • Control — a unified control plane for MCP services and Skills across every tool: take over existing configs, centralize them, and distribute them everywhere.
  • Secure — one-click Security Check and redaction, real-time pre-tool-use interception, and locally served, redacted share links. All parsing and storage stay on-device (see Privacy & data).

Guide

Get up and running, then explore each feature.

PageWhat it covers
InstallationHomebrew, the signed DMG, running from source, and auto-update
QuickstartYour first time-travel in under five minutes
Importing sessionsThe import wizard, all six sources, and the read-only guarantees
Time travelPlayback mode, code snapshots, diff view, and the TimberLine timeline
Search & filteringType-filter chips, ⌘F search, and the ⌘K command palette
Session insightsOverview stats, Active Duration, Cost & Usage, and the context-window bar
Refine modeDistill a session with Keep / Delete / Edit / Insert, then export
Replay modeDeterministic re-execution in an isolated sandbox
Project managementLogical projects, association, the Git pill, and sync
Context causalityHeuristic read → change linking with confidence tiers
Live streamingWatching in-progress sessions in real time
MCP HubThe aggregating MCP server, config takeover, tool policies, and the Inspector
Skills HubCentral skill storage, symlink distribution, GitHub import, and versioning
Security & sharingSecurity Check, custom rules, the pre-tool-use hook, and share links

Reference

PageWhat it covers
Keyboard shortcutsEvery shortcut, grouped by mode
CompatibilityThe six-tool support matrix and per-tool log locations
ConfigurationThe ~/.chronicle/ layout, environment variables, and config.json
Privacy & dataThe local-first guarantees and the exact outbound calls

Architecture

For contributors who want to understand and extend the codebase.

PageWhat it covers
OverviewSingle-process/single-port design, run modes, component map, and principles
Data modelThe SQLite schema, the normalized event model, and replaceSession
Parsers & ingestionThe event model in depth, plus how to add a new source
Git snapshot engineReconstructing code state from Git history
MCP & Skills internalsThe registry, the hub, Streamable HTTP, and skill distribution
Security, live & replayThe redaction engine, SSE watchers, the replay engine, and causality
API referenceEvery REST route, the SSE stream, /mcp, and /share
Desktop & packagingThe Electron shell, signing, auto-update, and the release flow

Then see Contributing for dev setup, the branch-and-PR workflow, and how changes are verified.

Project background

Chronicle was built from a detailed product requirements document; its decision log records what shipped versus what was deferred. The README carries the full feature inventory, and the CHANGELOG tracks releases.

License: Chronicle is MIT licensed.

Released under the MIT License.