You've been away for a week and want to know what happened. Or you need to find when a specific decision was made. The chronicle is your project's narrative timeline — it records what happened, when, and why.

Open the chronicle from the command palette (Cmd/Ctrl+K) by typing "Memories," then switch to the Chronicles tab.

Overview

The chronicle is different from memories. Memories store facts. The chronicle records events — what agents did, what states changed, what decisions were made, and in what order. It's a running narrative of your project's history.

kill9 synthesizes chronicle entries from session activity automatically. You don't write chronicle entries yourself. The system observes what happens and builds the timeline.

What you can do

With the chronicle, you can:

Catch up on everything that happened while you were away
Search for past events by keyword, date, or initiative
Read daily, weekly, or monthly digests summarizing project activity
Understand why a decision was made by finding the original context
Give agents access to project history so they can learn from past patterns

How it works

What the chronicle is

The chronicle is a database of timestamped events drawn from session activity. Every initiative state change, document approval, agent delegation, and significant agent action gets recorded. These raw events are synthesized into a readable narrative — not just a log of "thing happened at time," but a story of why it happened and what came next.

How it synthesizes session activity

kill9 doesn't just dump raw logs into the chronicle. It processes session activity into coherent narrative entries. When kdev implements a feature, the chronicle doesn't record "kdev edited file.ts" — it records "kdev implemented the email validation story, adding format checks to the signup form and writing six unit tests."

This synthesis happens automatically through built-in hooks. After each significant session event, the hook processes the activity and writes a chronicle entry.

Chronicle search

Search the chronicle by text, date, or initiative. Type a keyword and find every event related to it. Filter by date range to see what happened during a specific period. Filter by initiative to trace the full history of a feature.

Use search when you need to answer questions like "when did we decide to use PostgreSQL instead of MongoDB?" or "what did kdev do last Tuesday?"

Chronicle digests

Digests summarize activity over a time period:

Daily — what happened today: which agents ran, what changed, what decisions were made
Weekly — broader trends: progress across initiatives, blockers resolved, patterns emerging
Monthly — strategic view: what shipped, what stalled, what changed direction

Digests are the fastest way to catch up. Instead of reading every chat message from the past week, read the weekly digest. You'll understand what agents did, what got approved, and what's still in progress.

How chronicle context helps agents

Agents can access the chronicle too. When an agent starts working on a story, it can look at the chronicle to understand what happened before — previous decisions, failed approaches, and the broader context of the initiative.

This means an agent working on week three of a project knows what was decided in week one. It doesn't repeat failed approaches, and it can reference past decisions when making new ones.

The Memories panel Chronicle tab

The Chronicle tab in the Memories panel is your window into the chronicle. Browse entries chronologically, search by keyword, or generate a digest for a specific time period.

The tab shows the same narrative entries that agents can access, so you see exactly what context they're working with.

Tips

Read the weekly digest every Monday morning. Five minutes of reading replaces an hour of catching up in individual sessions.
Use chronicle search before asking an agent a question about past decisions. The answer might already be there.
If an agent seems to be repeating a failed approach, check the chronicle. It might not have access to the relevant entries, or the entries might be unclear.
The chronicle grows over time. Old entries remain searchable, so you can always go back and find what happened months ago.
Chronicle quality depends on session quality. Clear, descriptive agent sessions produce better chronicle entries than vague ones.

Memories — retained facts that agents use across sessions
Work — where agent activity gets recorded
Plan a feature — initiatives tracked in the chronicle
Hooks — how chronicle entries get created automatically

Chronicles