π§Ύ Local session receipts for AI coding agents
AgentRun Ledger is a local-first CLI + dashboard that records what your AI agent actually did during a session.
It captures:
- π Files changed (added / modified / deleted)
- βοΈ Commands executed (with pass/fail)
- π Human notes
- π Session scoring & risks
- π Auto-generated Markdown reports
Think of it as:
π Git + Logs + AI audit trail β all in one place
After a long session, you usually have:
- No clear audit trail
- No idea what failed silently
- No structured way to review
AgentRun Ledger fixes that by generating a deterministic, reviewable session report.
npm install
npm run build
npm run dev -- init
npm run dev -- start "demo agent session"
npm run dev -- note "Testing AgentRun Ledger."
npm run dev -- run "node -e \"console.log('hello')\""
npm run dev -- report
npm run dev -- dashboardOpen dashboard: π http://127.0.0.1:3765
What youβll see:
- Session timeline
- File changes with status badges
- Command execution logs
- Notes
- Live report preview
# AgentRun Report: demo agent session
## Summary
- Changed files: 3
- Commands logged: 2
- Passed commands: 1
- Failed commands: 1
## Review risks
- **DANGER: Failed commands exist**npm install
npm run buildnpm linkThen use anywhere:
agentrun init
agentrun start "my session"agentrun init
agentrun start "task name"
agentrun snapshot before
agentrun snapshot after
agentrun run "npm test"
agentrun note "Agent updated retry logic"
agentrun status
agentrun list
agentrun report
agentrun dashboard --port 3765AgentRun Ledger is agent-agnostic.
Use it with:
- Codex
- Gemini CLI
- Local LLMs
- Any script or automation
Just wrap actions like:
agentrun run "your command"agentrun start "implement feature X"
agentrun run "npm install"
agentrun run "npm run build"
agentrun note "Added API layer and validation"
agentrun report- Uses Git diff vs HEAD to track file changes
- Stores session data in
.agentrun/agentrun.db - Generates deterministic reports (no AI required)
- Dashboard reads local DB only
No cloud. No API keys. No tracking.
- Requires Node 24+ (uses
node:sqlite) - SQLite warning is expected (experimental feature)
- No full terminal recording (command-level only)
- Reports are heuristic-based (not AI-generated)
AgentRun Ledger includes pre-built agent recipes to standardize workflows.
These are located in:
agent-recipes/
When starting a task, explicitly instruct the agent to:
- Read the recipe file
- Follow it step-by-step
- Execute all commands via
agentrun
Before doing anything:
1. Open and read:
agent-recipes/planning-session.md
2. Follow it strictly.
3. Do not skip steps.
4. Use agentrun for:
- starting session
- logging commands
- adding notes
- generating report
Task:
Plan a RAG Regression Lab project.
Before starting:
1. Read:
agent-recipes/feature-implementation.md
2. Follow all steps exactly.
3. All commands must go through:
agentrun run "<command>"
Task:
Implement API layer for RAG system.
You were previously working on this project.
Before continuing:
1. Read:
agent-recipes/recovery-after-reset.md
2. Follow it strictly.
3. Resume from last AgentRun report.
- Always reference recipe by path
- Always say "read this file first"
- Always enforce step-by-step execution
If you donβt do this, the agent will ignore your system.
This folder contains standardized workflows for AI agents.
- planning-session.md β planning only
- feature-implementation.md β feature development
- bug-fix-session.md β debugging
- refactor-session.md β safe refactoring
- test-and-validation.md β testing
- documentation-update.md β docs work
- recovery-after-reset.md β resume sessions
Before any task:
- Select the appropriate recipe
- Read it fully
- Follow it strictly
- Use AgentRun Ledger for all actions
MIT



