Skip to main content

IDEs

Monitor IDE AI Usage

Once editors send model requests through your gateway, you can see each decision, the captured conversation, and what it cost. Each question has its own place to look:

QuestionWhere to look
Was a request allowed or blocked, and why?Runtime events
What did the conversation say?History, when capture is on
How many tokens, and what cost?Usage
Who changed configuration or access?Trail

Use a short, clearly labeled test prompt when you look for one request, so it stands out from other traffic.

Before you start​

  • A gateway from Gateway Setup for IDEs, started with --agent.
  • At least one editor that sends model requests to the gateway. An MCP-only connection sends no model requests.
  • A CLI session with events:read, from VERDICTAN_API_TOKEN or verdictan auth login.
  • For conversation content in History: a history.capture block with enabled: true and mode: raw or mode: redacted. See Runtime Configuration.

To tell editor traffic apart, run the editor gateway under its own --agent value, such as ide-gateway, and give each developer or team its own client API token. Usage can then group cost by agent and by API key.

Read recent events​

  1. Read the events from the last ten minutes while someone uses the editor:

    verdictan events tail --since 10m --json

  2. Show only blocked decisions:

    verdictan events tail --since 10m --event-type decision --verdict block --json

  3. Show one gateway:

    verdictan events tail --since 30m --gateway-id <gateway-id> --json

Each command reads one page, newest first. Run it again to see events that arrived later. Use --json: each event then shows its timestamp, verdict, and reason_code, while the text lines show - for the time, model, and policy. --verdict matches the stored value exactly, such as allow, block, redact, or escalate. The API equivalent is GET /v1/events, which requires since. See verdictan events.

Review one request​

  1. Find the event in the tail or in GET /v1/events, and read the verdict and reason code.
  2. Read the policy results, not just the verdict: a request can be allowed after a redaction.
  3. If capture is on, open History and find the session. With mode: raw or mode: redacted, it shows the content as well as the metadata.
  4. For configuration or access changes around the request, open Trail.
  5. If the request was escalated, open Inbox.

Notifications don't report ordinary IDE decisions, gateway health, configuration reloads, export completion, or budget thresholds. See Notifications.

Read IDE cost in Usage​

  1. Open Usage in the Console and set Time to your review period.
  2. Set Group by to Agent to compare the editor gateway with other agents, or to API key to compare developers.
  3. Add a filter for the editor agent.

Costs are estimates from token counts and pricing metadata; see Usage Costs and Budgets. From the CLI, run verdictan spend summary --since 30d --json.

Export evidence​

  1. For a short window, write events to a file:

    verdictan events export --since 7d --format csv > ide-events-7d.csv

  2. For a long window or a handoff to another team, use an export job:

    verdictan export-jobs create --since 30d --format csv
verdictan export-jobs list --json
verdictan export-jobs download --job-id <job-id> > ide-audit.csv

  3. Note the request IDs, escalation IDs, or incident references the export supports.

Export only the window the review needs. See verdictan export-jobs for job states and formats.

Verify​

  1. Send one request from the editor, then run verdictan events tail --since 10m --json. A new event appears with a timestamp from the moment you sent the request.
  2. If capture is on, find the session in History by request or session ID; use the time only to narrow the search.
  3. In Usage, group by Agent and check tokens and estimated cost. A tiny amount shows as <$0.01, and a blocked request may have no upstream cost.

Troubleshooting​

SymptomCauseFix
No events found.The window or filters exclude the request, or the CLI is on another regionWiden --since, drop filters, and check verdictan regions current.
The editor gets a reply but no event appearsThe endpoint, event delivery, organization, region, or time window differsCheck the editor's base URL and model. See IDE Integration Troubleshooting.
No session in Historyhistory.capture.enabled is falseSet it to true and choose a mode.
Metadata but no contenthistory.capture.mode is metadata_only, the defaultAfter a data review, set mode to redacted or raw.
A blocked request is missing from Historyhistory.capture.include_blocked is false, the defaultSet it to true. The event records the block either way.
No cost for the editor agentThe target has no pricing metadata, or the traffic used another agentCheck the target's pricing and the gateway's --agent value.
verdictan events export fails to authenticateNo API token or sessionSet VERDICTAN_API_TOKEN or run verdictan auth login.

Next steps​