Chronicle

Chronicle

[](https://github.com/geekmuse/chronicle/actions/workflows/ci.yml) [](LICENSE)

Bidirectional sync for AI coding agent session history across machines, with path canonicalization and Git-backed storage.

---

[!WARNING] **ALPHA SOFTWARE - USE WITH CAUTION**

Chronicle is alpha-quality software. It directly modifies AI agent session files on your machine. Bugs in the canonicalization, merge, or materialization logic could **corrupt or permanently delete your session history**.

**Back up your existing sessions before installing or running Chronicle** (see [Before You Start](#before-you-start-back-up-your-existing-sessions) below).

Chronicle is provided as-is, with no warranty of any kind. See [LICENSE](LICENSE).

---

Overview

Chronicle synchronizes Pi and Claude Code session history across multiple machines where `$HOME` paths differ.

**Chronicle is for you if** you use AI coding agents across multiple machines with different home directory paths (e.g., `/Users/alice` on your Mac and `/home/alice` on your Linux workstation) and you want session history to follow you between them without running your own sync infrastructure.

**Chronicle is not for you if** you only work on one machine, your machines already share identical `$HOME` layouts (in which case any file sync tool will work), or you already run self-hosted sync infrastructure like Syncthing with an always-on relay node - simpler tools will serve you better.

It uses a canonicalization layer to abstract away per-machine path differences and Git as the storage and transport backend. Session files are merged using a grow-only CRDT (set-union), preserving the append-only invariant of JSONL session data. See [Storage Backends](docs/references/002-storage-backends.md) for why Git was chosen over alternatives.

Features

• **Cro