Afterpaths
About
Make your AI coding agents smarter with every session
Details
- Author
- burnssa
- GitHub stars
- 2
- Downloads
- 171
- Categories
- Developer Tools
Jump to
- Unified session view across all AI coding tools
- LLM-generated session summaries (discoveries, dead ends, decisions)
- Automatic rule extraction into .claude/rules/ and .cursor/rules/
- Cross-session search (ap search) with optional deep search
- Session analytics: tokens, errors, daily trends
- MCP server with 6 native tools (list, show, search, summarize, artifacts, rules)
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
AfterpathsCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install with pip install afterpaths (or pip install afterpaths[mcp] for MCP support). Navigate to your project and run ap audit to see an overview. Recommended flow: ap log to browse sessions, ap summarize <ref> (requires ANTHROPIC_API_KEY), ap rules to extract rules into .claude/rules/, ap search <query> to find past discussions, and ap stats to track performance. For the MCP server, configure it with claude mcp add afterpaths -- afterpaths-mcp or run python -m afterpaths.mcp_server. Both afterpaths and ap work identically.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"afterpaths": {
"afterpaths": {
"command": "uvx",
"args": [
"--from",
"afterpaths[mcp]",
"afterpaths-mcp"
]
}
}
}
}McpServers
{
"afterpaths": {
"command": "uvx",
"args": [
"--from",
"afterpaths[mcp]",
"afterpaths-mcp"
]
}
}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:
1. ap audit — Overview of your sessions, models used, and rule status
2. ap show 5 --raw — Raw session transcript (the messy JSONL data, made readable)
3. ap show 5 — LLM-generated summary extracting discoveries, dead ends, and decisions
4. 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
```bash
pip install afterpaths
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
