omp packages

@t450/pi-chronicle0.1.0

Chronicle for Pi: standups, search, tips, cost tips, and AGENTS.md improvements from your Pi session history

t450 Published 11 days ago MIT ~238 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Did it work for you?

Result

One report per person. A new report replaces your old one.

Reports 0

No reports yet.

Readme

pi-chronicle

Chronicle for Pi: standups, search, usage tips, cost tips, and AGENTS.md suggestions drawn from your own Pi session history. It mirrors the /chronicle command of GitHub Copilot CLI.

Install

pi install npm:@t450/pi-chronicle  # from npm
pi install /path/to/pi-chronicle   # from a local checkout
pi -e /path/to/pi-chronicle        # one run

Requires Node 22.19 or newer (node:sqlite with FTS5).

Commands

Command What it does
/chronicle Pick a subcommand (interactive mode).
/chronicle standup [window] [context] Report on recent work grouped by repo, with PR status. Default window 24h.
/chronicle search <query> Full-text search over past prompts, answers and compaction summaries. Runs locally, no model call.
/chronicle tips [window] [focus] Personalized tips grounded in your prompts and tool usage. Default 7 days.
/chronicle cost-tips [window] Ranked ways to cut token spend, from a precomputed cost profile. Default 7 days.
/chronicle improve [window] Propose AGENTS.md changes for the current repo from repeated friction; asks before editing. Default 30 days.
/chronicle reindex Delete and rebuild the index.

Windows accept today, yesterday, 3d, 48h, 1 week, last 3 days. Text after the window is passed to the agent as extra context.

The extension also registers a read-only chronicle_sql tool so the agent can answer questions about past sessions on its own.

standup, tips, cost-tips and improve hand a prompt to the agent, so they need interactive or RPC mode. In pi -p, Pi exits once the command handler returns, before that turn runs. Ask in plain words instead, for example pi -p "What did I work on in the last 3 days?", and the agent will use chronicle_sql. search and reindex work in every mode.

Data

The index lives at <agent dir>/chronicle/session-store.db (normally ~/.pi/agent/chronicle/session-store.db). Every subcommand first syncs it against ~/.pi/agent/sessions, re-reading only files whose size or mtime changed. Only the active branch of each session is indexed. The index is derived data and safe to delete.

Privacy

standup, tips, cost-tips, improve and any chronicle_sql use send excerpts of your past sessions (prompts, answers, file paths, tool errors, cost figures) to your current model provider. search and reindex stay on your machine.

Development

npm run check                                  # typecheck + tests
node --experimental-strip-types scripts/smoke.ts [term]   # sync real sessions into a temp db