See what contributes to the estimate
Combines detected agent terminals, manual sessions, open editor context, configured usage files, and locally available model metadata in one dashboard.
A VS Code-compatible observability layer for understanding what an AI coding session may see, where usage numbers come from, and which trust controls stand between a model request and your codebase.
Agent Inspector connects session visibility with privacy, scanning, and safer edit mechanics while preserving the difference between observation and inference.
Combines detected agent terminals, manual sessions, open editor context, configured usage files, and locally available model metadata in one dashboard.
Labels provider-log or manually recorded message tokens distinctly from approximate open-document context, with source diagnostics instead of false precision.
Reviews installed extension manifests and bounded source patterns for disclosed capabilities, outbound behavior, sensitive access, and configurable security findings.
Scans selected files or folders for sensitive filenames and security-relevant patterns, with path exclusions and importable custom regex rules.
Constrains AI-assisted edits to selected paths, previews the proposed change, checks generated output, stores a snapshot, and supports one-click rollback.
Applies domain allow/deny policy, configurable redaction, privacy confirmation, payload metadata, and an outbound audit trail to explicit cloud-assisted edit flows.
Confirm the target is inside the user’s selected path locks.
Apply policy, redaction, destination checks, and confirmation.
Present a diff and verify generated output before acceptance.
Keep the previous content snapshot available for rollback.
Trustworthy telemetry design, policy enforcement, privacy-aware model integration, reversible tooling, and honest degraded states.
The extension acknowledges that VS Code cannot expose private counters from other AI providers. It uses only locally visible signals and marks estimates as estimates.
Scope validation, redaction, domain policy, confirmation, diff review, output checks, snapshots, and audit events surround the explicit Safe Agent path.
Dashboard telemetry, scan summaries, policy state, scope locks, snapshots, and audit entries remain in VS Code extension state. Ollama explanations are optional and user configured.
The dashboard can open with limited support in an untrusted workspace, while filesystem scans, usage discovery, process probing, and edits require a trusted local workspace.
Install Agent Inspector from an editor marketplace, inspect the implementation, or reach out about AI developer-tooling roles.