Aichronicles

toabctl2stars

Capture, search, and summarize AI coding agent (Claude Code) sessions in SQLite. Live web UI, MCP server, CLI.

1# Aichronicles

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: Apache-2.0
Last checked: 2026-10-28

Stars: 2
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Aichronicles?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Aichronicles need an API key?

No required environment variable is listed on this record.

What transport does Aichronicles use?

Aichronicles runs locally over stdio.

When was Aichronicles last checked?

Last checked 2026-10-28. Capture, search, and summarize AI coding agent (Claude Code) sessions in SQLite. Live web UI, MCP server, CLI.

From the publisher

Documentation

aichronicles

Capture your AI coding sessions, locally, with secrets scrubbed before they hit disk.

Status: work in progress.

aichronicles runs as a tiny user-mode daemon that ingests hook events from Claude Code, Gemini CLI and Codex CLI into a SQLite store, exposes the corpus as an MCP server your agent can query for context from past work, and generates structured summaries on demand.

flowchart LR
    cc[Claude Code]
    llm[(Anthropic / OpenAI<br/>HTTPS, on-demand)]

    subgraph local["Your machine — single user, local disk"]
        direction LR
        hook["aichronicles hook<br/><i>hook subprocess</i>"]
        api["aichronicles-api<br/><i>systemd --user · UDS 0600</i>"]
        db[("SQLite store<br/>raw_envelopes ▸ events ▸<br/>extractions ▸ llm_outputs")]
        mcp["aichronicles mcp-serve<br/><i>stdio</i>"]
        cli["aichronicles summarize<br/>/ reflect / propose"]
    end

    cc -- "hook fires" --> hook
    hook -- "POST /v1/ingest" --> api
    api -- "redact + verify + persist" --> db
    cc <-- "tools/call (stdio)" --> mcp
    mcp -- "GET /v1/* (UDS)" --> api
    cli -- "GET /v1/* (UDS)" --> api
    cli -.->|"egress redact ▸ tool use"| llm
    llm -.-> cli
    cli -- "POST /v1/llm-outputs" --> api

Legend. Solid arrow: data flows in this direction. Dashed arrow: optional / on-demand (only fires for summarize/reflect/propose). The local box is the trust boundary — everything inside runs as your user, on your local disk. Cylinder is persistent state.

The diagram above is the static view (where things run). For the dynamic view — what fires automatically vs. what you trigger, and what happens step-by-step inside each flow — see docs/explanation/data-flow.md.

What you get

Searchable corpus. Every prompt, tool call, and response from your Claude Code sessions, indexed by SQLite FTS5. aichronicles search 'mongodb shutdown' returns the turn where you fixed it.
Structured summaries. aichronicles summarize --session <id> produces a JSON record with topic, what-was-done, unresolved items, files touched, and links you actually referenced — annotated with what you used each one for. Cached in the store; replays for free.
Cross-session reflection. aichronicles reflect and propose read recent sessions and surface recurring task types, friction sources, and concrete capabilities (skills, CLAUDE.md rules, scripts) worth pre-building.
MCP exposure. aichronicles mcp-serve registers as an MCP server in Claude Code, so the agent can search your past sessions and pull a prior summary mid-conversation.
Edge-scrubbed. Secrets matching ~15 patterns (Anthropic/OpenAI/AWS/etc.) are redacted to <redacted:kind> markers before envelopes leave the hook subprocess. The daemon refuses unredacted envelopes as defense-in-depth.

Example: `aichronicles summarize`

Topic: feat(grass): prefer stereo version_data over GitHub tags

What was done:
  - Added stereo.go to agents/pkg/agents/grass/ with YAML structs
    for version_data/*.yaml and a lookupStereoVersion scanner.
  - Extended grass.Analyze with a variadic opts API (WithStereoDir)
    that overrides the GitHub-tag version when stereo data matches.
  - Wired the option through the manifest-gen pipeline; added a
    --stereo-dir flag to the cg agent grass CLI command.

Unresolved:
  - cg-codeowners-check still pending — awaiting human review.
  - Reconciler config struct lacks test coverage for the new field.

Key files:
  - agents/pkg/agents/grass/stereo.go
  - bots/manifest-gen/internal/agent/analyzer/analyzer.go
  - cg/pkg/commands/agent.go

Links:
  - https://github.com/chainguard-dev/customer-issues/issues/3406
    source ticket for the harbor cert work

Status

Personal-use software, single-machine. Designed for one developer running Claude Code on their own laptop or workstation. No multi-user authentication, no central server, no remote backup. The threat model is documented at docs/explanation/threat-model.md; read it before adopting if you handle anything sensitive.

Supports three source agents today: Claude Code (Anthropic), Gemini CLI (Google) and Codex CLI (OpenAI). Each writes hooks into its own settings file via aichronicles setup <agent> and ingests live through the same UDS daemon. The envelope schema, redaction layer, and MCP server are agent-agnostic; adding another agent's hook format is mostly importer work.

Live capture is available for all three. Historical backfill from on-disk transcripts covers Claude Code (import-claude) and Gemini CLI (import-gemini); Codex's rollout files are not imported yet, so Codex history starts at the moment you install its hooks.

Get started

Quick start (≤90 seconds) — install, bring up the daemon, see your first hook event captured.

Your first summary — configure an API key and generate a structured summary of one session.

Documentation

Section	What's there
Tutorials	Learn by doing
How-to guides	Recipes for specific tasks
Reference	CLI, configuration, schema, detectors (auto-generated)
Explanation	Architecture, data flow, threat model, design decisions

Building from source

git clone <repo-url> && cd aichronicles
go build ./...
go test ./...
go test -tags=integration ./integration/...

Targets the toolchain in go.mod (Go 1.26+). Five direct deps: modernc.org/sqlite (pure-Go SQLite), spf13/cobra, BurntSushi/toml, google/uuid, godbus/dbus/v5; plus the official Anthropic and OpenAI SDKs.

License

Apache-2.0 is the planned license. The LICENSE file lands in the first public-release commit; until then, the code is shared under no formal terms.

Contributing

The development practices (commit style, testing rules, idiomatic Go expectations) are in CLAUDE.md. Read it before opening a PR.

Aichronicles

toabctl2stars

Capture, search, and summarize AI coding agent (Claude Code) sessions in SQLite. Live web UI, MCP server, CLI.

Databases

Install Run on PlugMCP

GitHub

Run on PlugMCP

1# Aichronicles

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: Apache-2.0
Last checked: 2026-10-28

Stars: 2
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Aichronicles?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Aichronicles need an API key?

No required environment variable is listed on this record.

What transport does Aichronicles use?

Aichronicles runs locally over stdio.

When was Aichronicles last checked?

Last checked 2026-10-28. Capture, search, and summarize AI coding agent (Claude Code) sessions in SQLite. Live web UI, MCP server, CLI.

From the publisher

Documentation

aichronicles

Capture your AI coding sessions, locally, with secrets scrubbed before they hit disk.

Status: work in progress.

flowchart LR
    cc[Claude Code]
    llm[(Anthropic / OpenAI<br/>HTTPS, on-demand)]

    subgraph local["Your machine — single user, local disk"]
        direction LR
        hook["aichronicles hook<br/><i>hook subprocess</i>"]
        api["aichronicles-api<br/><i>systemd --user · UDS 0600</i>"]
        db[("SQLite store<br/>raw_envelopes ▸ events ▸<br/>extractions ▸ llm_outputs")]
        mcp["aichronicles mcp-serve<br/><i>stdio</i>"]
        cli["aichronicles summarize<br/>/ reflect / propose"]
    end

    cc -- "hook fires" --> hook
    hook -- "POST /v1/ingest" --> api
    api -- "redact + verify + persist" --> db
    cc <-- "tools/call (stdio)" --> mcp
    mcp -- "GET /v1/* (UDS)" --> api
    cli -- "GET /v1/* (UDS)" --> api
    cli -.->|"egress redact ▸ tool use"| llm
    llm -.-> cli
    cli -- "POST /v1/llm-outputs" --> api

What you get

Searchable corpus. Every prompt, tool call, and response from your Claude Code sessions, indexed by SQLite FTS5. aichronicles search 'mongodb shutdown' returns the turn where you fixed it.
Structured summaries. aichronicles summarize --session <id> produces a JSON record with topic, what-was-done, unresolved items, files touched, and links you actually referenced — annotated with what you used each one for. Cached in the store; replays for free.
Cross-session reflection. aichronicles reflect and propose read recent sessions and surface recurring task types, friction sources, and concrete capabilities (skills, CLAUDE.md rules, scripts) worth pre-building.
MCP exposure. aichronicles mcp-serve registers as an MCP server in Claude Code, so the agent can search your past sessions and pull a prior summary mid-conversation.
Edge-scrubbed. Secrets matching ~15 patterns (Anthropic/OpenAI/AWS/etc.) are redacted to <redacted:kind> markers before envelopes leave the hook subprocess. The daemon refuses unredacted envelopes as defense-in-depth.

Example: `aichronicles summarize`

Topic: feat(grass): prefer stereo version_data over GitHub tags

What was done:
  - Added stereo.go to agents/pkg/agents/grass/ with YAML structs
    for version_data/*.yaml and a lookupStereoVersion scanner.
  - Extended grass.Analyze with a variadic opts API (WithStereoDir)
    that overrides the GitHub-tag version when stereo data matches.
  - Wired the option through the manifest-gen pipeline; added a
    --stereo-dir flag to the cg agent grass CLI command.

Unresolved:
  - cg-codeowners-check still pending — awaiting human review.
  - Reconciler config struct lacks test coverage for the new field.

Key files:
  - agents/pkg/agents/grass/stereo.go
  - bots/manifest-gen/internal/agent/analyzer/analyzer.go
  - cg/pkg/commands/agent.go

Links:
  - https://github.com/chainguard-dev/customer-issues/issues/3406
    source ticket for the harbor cert work

Status

Get started

Quick start (≤90 seconds) — install, bring up the daemon, see your first hook event captured.

Your first summary — configure an API key and generate a structured summary of one session.

Documentation

Section	What's there
Tutorials	Learn by doing
How-to guides	Recipes for specific tasks
Reference	CLI, configuration, schema, detectors (auto-generated)
Explanation	Architecture, data flow, threat model, design decisions

Building from source

git clone <repo-url> && cd aichronicles
go build ./...
go test ./...
go test -tags=integration ./integration/...

License

Apache-2.0 is the planned license. The LICENSE file lands in the first public-release commit; until then, the code is shared under no formal terms.

Contributing

The development practices (commit style, testing rules, idiomatic Go expectations) are in CLAUDE.md. Read it before opening a PR.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Aichronicles?

Does Aichronicles need an API key?

What transport does Aichronicles use?

When was Aichronicles last checked?

Documentation

aichronicles

What you get

Example: aichronicles summarize

Status

Get started

Documentation

Building from source

License

Contributing

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Aichronicles?

Does Aichronicles need an API key?

What transport does Aichronicles use?

When was Aichronicles last checked?

Documentation

aichronicles

What you get

Example: aichronicles summarize

Status

Get started

Documentation

Building from source

License

Contributing

Example: `aichronicles summarize`

Example: `aichronicles summarize`