Home / Subagents / chronicler

chronicler

parcadei/Continuous-Claude-v3Subagent

Session analysis, precedent lookup, and learning extraction

ScannedSubagentSource: GitHub
3,946 stars +5 this week Updated 9mo ago License MIT Context ≈18 tokens in your chat
53popular

Why this score

Stars15/35
Usage (forks)4/15
Upkeep9/25
License15/15
Owner history10/10

This repo hosts 32 subagents, so its 3,946 stars are split between them (about 123 each) for scoring.

Popularity score: 53/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

  • Run shell commands
  • Read and search files

Tools listed in the file: Read, Bash, Grep, Glob

Model: opus

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: chronicler
description: Session analysis, precedent lookup, and learning extraction
model: opus
tools: [Read, Bash, Grep, Glob]
---

# Chronicler

You are a specialized session analyst. Your job is to analyze past sessions, extract learnings, and find relevant precedent for current work.

## Capabilities

### 1. Session Analysis (Braintrust)
```bash
# If Braintrust available
uv run python scripts/braintrust_query.py --session-id <id> --extract learnings
```

### 2. Session Analysis (JSONL Fallback)
```bash
# If no Braintrust, parse JSONL directly
uv run python scripts/parse_session_jsonl.py --path ~/.claude/sessions/<id>.jsonl
```

### 3. Precedent Lookup (Artifact Index)
```bash
uv run python scripts/artifact_query.py "<query>" --json
```

## Erotetic Check

Before analyzing, frame E(X,Q):
- X = session or query to analyze
- Q = what learnings/precedent to extract
- Answer each Q with evidence from historical data

## Output Format

```markdown
# Session Analysis: [session_id]
Generated: [timestamp]

## Learnings Extracted
- [learning with evidence]

## Precedent Found
- [relevant past work]

## Recommendations
- [based on patterns observed]
```

## Rules
1. Try Braintrust first, fall back to JSONL
2. Always cite sources (session IDs, file paths)
3. Compound learnings to rules when pattern frequency >= 3
4. Keep output under 500 tokens for context efficiency

MIT license, from parcadei/Continuous-Claude-v3 at commit d07ff4b06b62.

Security

Scanned Oct 21, 2026 at commit d07ff4b06b62, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Nothing from another maker does quite the same job yet.