Afterpaths

Name: Afterpaths
Author: burnssa

by burnssaversion 0.2.5i★ 2iRuns on your computer

Registry nameio.github.burnssa/afterpaths

Install

Overview

Description from the maker (original English)

Session memory for AI coding agents. Search past sessions, extract rules, and track what works.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 2 passedChecked from public information; code not scanned yet
UsageiVery new↓ 29/wk · ★ 2

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools
You need to fill in: ANTHROPIC_API_KEY, OPENAI_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 2 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: ANTHROPIC_API_KEY, OPENAI_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "afterpaths": {
      "command": "uvx",
      "args": [
        "afterpaths",
        "afterpaths-mcp"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add afterpaths --env ANTHROPIC_API_KEY=your-value --env OPENAI_API_KEY=your-value -- uvx afterpaths afterpaths-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "afterpaths": {
      "command": "uvx",
      "args": [
        "afterpaths",
        "afterpaths-mcp"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "afterpaths": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "afterpaths",
        "afterpaths-mcp"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

ANTHROPIC_API_KEY secret env
Anthropic API key for session summarization and rule extraction. Not required for search, list, show, or rules tools.
OPENAI_API_KEY secret env
OpenAI API key (alternative to Anthropic) for summarization.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account burnssa, which owns the repo
! Caution
Still maintained
Code last changed 7 months ago, more than 6 months ago
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 75% of the other 5739 servers in this category
Published to the registry more recently than 10% of the other 5739 servers in this category
Basic checks equal to or better than 12% of the other 5739 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Afterpaths safe?

It passed 1 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ANTHROPIC_API_KEY, OPENAI_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 7 months ago, and the latest version (0.2.5) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: REA, Netdata, Front-End Checklist

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 448.2KUpdated 16 days ago

Runs on your computer

Install

Netdata

Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.

by netdataWidely used★ 81.3KUpdated 6 days ago

Runs in the cloud

Install

Front-End Checklist

Review frontend code and live pages against 386 quality-gated web development rules.

by thedaviddiasWidely used★ 74.7KUpdated 37 days ago

Runs in the cloud

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Afterpaths

Smarter with every session, automatically.

Extract rules from what worked. Track what didn't. Find the best models for your stack.

You're running Claude Code, Cursor and Codex, but which model actually works best for your stack? What approaches lead to breakthroughs vs. expensive dead ends? How do you stop your agents from making the same mistakes?

Afterpaths gives you a single view across all your AI coding tools: compare what's working, capture discoveries as rules, and guide your agent team away from costly diversions.

What you're seeing:

`ap audit` — Overview of your sessions, models used, and rule status
`ap show 5 --raw` — Raw session transcript (the messy JSONL data, made readable)
`ap show 5` — LLM-generated summary extracting discoveries, dead ends, and decisions
`head .claude/rules/gotchas.md` — Rules automatically extracted and ready for Claude's next session

The Problem

You're managing multiple agents - retaining critical context and learning from sessions is painful:

Repeated mistakes — Your agents hit the same gotchas. Three weeks later, same dead end, same wasted tokens.
No cross-tool visibility — Is Opus actually better than Sonnet for your codebase? Is Cursor outperforming Claude Code? You're guessing.
Rules are tedious — After a costly diversion, the last thing you want is to write a CLAUDE.md rule. So you don't. And the knowledge evaporates.
Sessions vanish — Session content is obscurely logged and hard to extract. Then it's often auto-deleted after 30 days. That breakthrough architecture decision? Context gone.

Afterpaths captures sessions across tools, surfaces what's working, and generates rules automatically—so your agents learn from every session, and you retain all your rich session context.

How It Works

Your Sessions                      Afterpaths

─────────────── ────────────────────────────────────

Claude Code ──► ap log ──► Browse sessions across IDEs Cursor ap stats ──► Analytics: tokens, activity, errors Codex ap summarize──► Session summaries (what happened) ap rules ──► Rule files (what to remember) ap search ──► Find past discussions & discoveries │ ▼ .claude/rules/ · .cursor/rules/ │ ▼ Your next session is smarter

Quick Start

pip install afterpaths

Navigate to your project (rules are project-specific)

cd ~/code/your-project

Run audit to see what you have

ap audit

The audit shows your sessions across all tools, model performance, and whether you have rules set up. No API key needed.

From there, the recommended flow:

# 1. Browse sessions and find significant work

ap log

2. Summarize important sessions (requires API key)

export ANTHROPIC_API_KEY="sk-ant-..." ap summarize 1

3. Extract rules from summaries → .claude/rules/

ap rules

4. Search across past sessions

ap search "database schema" ap search "auth" --deep # also search raw transcripts

5. Track ongoing performance

ap stats ap stats --daily

Tip: ap is the short alias for afterpaths. Both work identically.

All commands support --json for structured output (e.g., ap log --json, ap show 1 --json, ap search "query" --json).

See docs/commands.md for the full command reference and recipes.

From Session to Rules

Real example: A bug causing 76 missing sessions became a rule that prevents the same mistake.

While building afterpaths, sessions for a project weren't showing up. The path (let's call it) /Users/Code/foo_bar was being decoded as /Users/Code/foo/bar. After investigation, we discovered Claude Code uses lossy path encoding—both / and _ become -.

The summary captured the discovery:

## Discoveries

Claude Code's path encoding is lossy: Project paths in ~/.claude/projects/ are encoded by replacing / with -, but underscores are ALSO converted to hyphens. Three different paths encode identically:
/Users/Code/foo_bar → -Users-Code-foo-bar
/Users/Code/foo-bar → -Users-Code-foo-bar
/Users/Code/foo/bar → -Users-Code-foo-bar

`ap rules` extracted it into `.claude/rules/gotchas.md`:

- **Claude Code lossy path encoding**: Claude Code encodes project paths by

replacing both / and _ with -, making them indistinguishable when decoding. When decoding, try underscore variants alongside hyphen variants at each greedy step, preferring longer segments (single directories) over nested paths. _Source: 91b1ffbc_

Next time Claude works on path decoding in this codebase, it already knows about the lossy encoding—no need to rediscover it.

Why Afterpaths

Without	With Afterpaths
Discover gotcha, forget to document it	`ap summarize` captures it with full context
Hit the same issue 3 weeks later	Rule in `.claude/rules/` prevents it
No idea what's working	`ap stats` shows tokens, sessions, error rates
Sessions scattered across IDEs	`ap log` unified view across Claude + Cursor
Learnings siloed per tool	Rules sync to `.claude/rules/` and `.cursor/rules/`

What Gets Extracted

Category	What it captures	Example
Dead Ends	Approaches that failed	"Don't use X because Y"
Decisions	Architectural choices	"We chose Redis over Postgres because..."
Gotchas	Non-obvious warnings	"Watch out for X when doing Y"
Patterns	Techniques that worked	"For X, use pattern Y"

Each rule includes source session references so you can trace back to the original context.

Supported Tools

Tool	Status	Location
Claude Code	✅ Ready	`~/.claude/projects/*.jsonl`
Cursor	⚠️ Partial	`~/Library/Application Support/Cursor/User/workspaceStorage/`
Codex CLI	✅ Ready	`~/.codex/`

Known Limitations

Cursor sessions: the adapter reads several known chat/composer formats from state.vscdb (including workbench.panel.aichat.view.aichat.chatdata, composer.composerData, and allComposers), but Cursor changes its storage schema often and some sessions will return Entries: 0 even when the state.vscdb file is present. When this happens, ap show --raw and the afterpaths_show_session MCP tool emit a warning rather than silently returning empty. The raw file is untouched — if you need that session, opening state.vscdb directly with sqlite3 will still work.

Tool provenance features (ap show --artifacts, commit tracing, file activity) only cover sessions whose entries the adapter can read.

MCP Server

Afterpaths includes an MCP server that puts session history directly into your agent's tool list. Instead of relying on agents to discover the CLI, the MCP server makes session search, summaries, and rules available as native tools.

# Install with MCP support

pip install afterpaths[mcp]

Add to Claude Code

claude mcp add afterpaths -- afterpaths-mcp

Or run directly

python -m afterpaths.mcp_server

Tools exposed:

Tool	Description
`afterpaths_list_sessions`	List recent sessions for context recovery
`afterpaths_show_session`	Read session summaries and transcripts
`afterpaths_show_artifacts`	Show artifacts ledger: files written/edited with provenance
`afterpaths_summarize`	Generate summaries for sessions
`afterpaths_search`	Search across past sessions (auto-escalates to transcripts on 0 summary hits)
`afterpaths_get_rules`	Get extracted rules (dead ends, decisions, etc.)

Once configured, agents can ask "have we seen this before?" or "what were the dead ends?" and get answers from your session history.

Privacy

All local — Summaries and rules stay in your project
Your API key — Uses your Anthropic/OpenAI key
Read-only — Never modifies your source code
Gitignored — .afterpaths/ excluded by default

Storage

your-project/

├── .afterpaths/ # Summaries (gitignored) │ ├── summaries/ │ └── meta.json ├── .claude/ │ └── rules/ # Generated rules (commit these!) │ ├── dead-ends.md │ ├── gotchas.md │ └── patterns.md └── src/

Hand-edited notes in rule files

Each rule file is split into a manual section (preserved across ap rules runs) and an auto section (regenerated each run):

# Gotchas: Things to Watch For

_Add project-specific notes here — preserved across ap rules runs._

Auto-generated by afterpaths distill | Updated: 2026-04-21 12:00

Sources: 3 session(s)

Rules

Some extracted rule: ... _Source: abc12345_

Put hand-curated rules or project-specific reminders between the manual:start / manual:end markers — they'll survive every ap rules run. Content *outside* those markers (and outside the recognized boilerplate) blocks the run as a safety check. Pass --force to overwrite anyway, or wrap the content in manual markers to preserve it.

If you're upgrading from an earlier version and your rule files contain only auto-generated content, markers are inserted automatically on the next ap rules run with an empty manual section — no action required.

Roadmap

Claude Code session parsing
Cursor session support
Session analytics (tokens, errors, daily trends)
LLM summarization
Automatic rule extraction
Multi-target export (Claude, Cursor)
Codex CLI support
Cross-session search (ap search)
JSON output (--json flag)
MCP server for agent integration
Semantic search across sessions
Benchmarking and productivity insights

License

MIT

*Manage your AI coding agents. Learn what works. Stop repeating mistakes.*

Afterpaths

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

REA

Netdata

Front-End Checklist

README from the maker

Afterpaths

The Problem

How It Works

Quick Start

Navigate to your project (rules are project-specific)

Run audit to see what you have

2. Summarize important sessions (requires API key)

3. Extract rules from summaries → .claude/rules/

4. Search across past sessions

5. Track ongoing performance

From Session to Rules

Why Afterpaths

What Gets Extracted

Supported Tools

Known Limitations

MCP Server

Add to Claude Code

Or run directly

Privacy

Storage

Hand-edited notes in rule files

Rules

Roadmap

License