{"repo":"rajudandigam/agent-inspect","free":true,"listed":false,"github":"https://github.com/rajudandigam/agent-inspect","clone":"git clone https://github.com/rajudandigam/agent-inspect.git","description":"Local execution trees for TypeScript AI agents. agent-inspect helps you understand what happened inside an AI agent run — locally. It turns manual steps, tool calls, LLM calls, structured logs, failures, durations, and run metadata into readable execution trees you can inspect from the terminal. It is built for TypeScript/Node.js developers..","language":"TypeScript","stars":342,"topics":["observability","typescript","ai-agents","cli","debugging","devtools","evidence","jsonl","langchain","langgraph"],"license":"MIT","category":"ai-agents","readme_excerpt":"agent-inspect Local-first evidence for TypeScript AI agents See what your agent did. Catch the wrong path in CI. Keep the evidence local. AgentInspect turns TypeScript agent runs into readable execution trees, deterministic trajectory checks, and portable Evidence v2—without requiring an account, collector, or default upload. Capture once. Debug, prevent, and share from the same local trace. No account · no collector · no default upload · metadata-only by default Website · Docs · npm · GitHub Agent code rarely fails as one function call. It plans, retrieves, calls tools, invokes a model, retries, and produces side effects. Flat logs show fragments. AgentInspect keeps the run as local JSONL and gives you one evidence loop from the same trace. One trace. Three jobs. Debug — read the execution path See nested steps, tool calls, LLM calls, model and token metadata, durations, errors, and the first causal failure without sending the trace to an AgentInspect service. Use manual instrumentation, official adapters, supported standards files, or structured logs you already emit. Prevent — fail CI on the wrong trajectory Checks are deterministic and provider-free: the same trace and rules produce the same result. Start with a preset, then extend it with the expectations that matter to the workflow. A passing check exits 0 ; a rule failure exits 1 . Invalid configuration and unreadable/unsupported inputs use separate documented exit codes. Use TraceContract, suites, cohorts, Vitest/Jest","default_branch":null,"files":null,"tree":[],"storefront":"/r/rajudandigam","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/rajudandigam/agent-inspect/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}