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
Read-only MCP server for local AgentInspect TraceFacts, causal failure, and Evidence tools
2026-11-13
Bintang
—
Tool
—
Uptime
—
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.
Use --fail-on-observation failed only when the run records explicit OUTCOME events (for example the broken-agent-debugging starter). Trajectory checks do not invent outcomes from tool/LLM/run success.
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 reporters, or --evidence-on fail when the workflow needs more than one CLI check.
verify-safe is a best-effort local assessment and can report SAFE, SAFE WITH WARNINGS, UNSAFE, or UNKNOWN. bundle writes a redacted artifact and manifest; bundle verify rechecks the listed file hashes offline. “Share-checked” is not compliance certification—review the artifact before attaching it to a PR, incident, or support handoff.
First local trace
The generated demo is synthetic, keyless, and local. npm install agent-inspect does not copy repository examples; init writes them into the project.
For a fixed good/regression/PII walkthrough with stable run ids (demo-good, demo-regression, demo-pii), use the canonical keyless showcase. The richer blessed starters cover framework-specific paths.
The full API also exposes TraceFacts for bounded, logical analysis of supported traces. See programmatic trace analysis.
Where AgentInspect fits
AgentInspect owns the laptop-to-PR evidence loop. It complements hosted observability, production trace retention, and broad eval platforms rather than replacing them.
Need
Best fit
Inspect one local TypeScript agent run immediately
AgentInspect
Enforce deterministic tool/order/completion expectations in CI
AgentInspect
Attach a redacted, hash-verifiable offline artifact
AgentInspect
Monitor a production fleet with hosted dashboards and retention
Hosted observability / APM
Manage prompts, datasets, and online LLM-judge experiments
@agent-inspect/mcp-server exposes configured local evidence to an MCP client through bounded, read-only tools. It is optional and currently Preview; the core debug/check/evidence loop does not require it.
npx agent-inspect mcp configure --client cursor
Review the generated dry-run configuration and the coding-agent loop guide before enabling it.
The root package is enough for custom capture, the CLI, checks, and Evidence workflows. Install optional packages only for the integration or surface you use. agent-inspect-vscode is currently in the repository and is not presented as a published Marketplace extension.
What it is not
A maintainer-hosted SaaS or production APM replacement
Hosted trace retention, a team dashboard service, or a prompt registry
An LLM-as-judge or dataset platform by default
A replay engine, automatic remediation system, or compliance certification
Status and documentation
Current published baseline:6.31.27 · persisted schema 1.0 · Node.js >=20 · MIT.
Legacy v0.1 and v0.2 traces remain readable. Check the npm badge and changelog for the current published version.
Belum ada daftar tool. Server remote mendapatkannya setelah pemeriksaan kesehatan pertama.
FAQ
Pertanyaan
Bagaimana cara menginstal @agent Inspect/?
Salin konfigurasi stdio untuk Cursor, Claude Desktop, Claude Code, atau VS Code di halaman ini. Konfigurasi ini memakai instalasi dari penerbit, bukan proxy PlugMCP.
Apakah @agent Inspect/ memerlukan kunci API?
Tidak ada variabel lingkungan wajib yang tercantum di catatan ini.
Transport apa yang digunakan @agent Inspect/?
@agent Inspect/ berjalan secara lokal melalui stdio.
Kapan @agent Inspect/ terakhir diperiksa?
Terakhir diperiksa 2026-11-13. Read-only MCP server for local AgentInspect TraceFacts, causal failure, and Evidence tools