agent-trace
It provides the observability necessary to audit autonomous coding agents, allowing teams to validate agentic decisions and debug non-deterministic failures …
Local evidence and replay for coding agents: replay what happened, see what the trace could not prove, and attach safe evidence to review. Claude Code, Codex, Copilot CLI, Gemini CLI, Cursor, MCP.
- Replay the exact steps an AI coding agent took to complete a task
- Identify specific points where an agent's reasoning failed or lacked evidence
- Attach verified evidence to traces for human review of agent actions
It provides the observability necessary to audit autonomous coding agents, allowing teams to validate agentic decisions and debug non-deterministic failures through verifiable execution replays.
Engineering leaders managing autonomous agent workflows who require auditability and error reconstruction in AI-driven development cycles.
https://github.com/Siddhant-K-code/agent-trace
By Siddhant-K-code
How to Get It
claude plugins install Siddhant-K-code/agent-trace
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me replay the exact steps an AI coding agent took to complete a task
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Hacker News
- Launch HN: Laminar (YC S24) – RL-trained model that finds errors in agent traces — Hacker News · 59 pts
- Show HN: Oodle.ai – $10 per million agent traces — Hacker News · 31 pts
- Show HN: RLM-based local debugger for AI agent traces — Hacker News · 27 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 100 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 100 GitHub stars; contributors unknown; last commit 0d ago; license MIT.