Skip to main content

Core Concepts

Understand the key concepts behind Intentra CLI.

Events

An event is a single hook invocation from an AI tool. Each time you:

  • Send a message in Cursor chat
  • Request code completion
  • Run a Claude Code command
  • Execute a Gemini CLI prompt

...an event is captured.

Scans

A scan groups related events into a logical unit. For example:

  • A chat conversation with multiple back-and-forth messages = one scan
  • Code completion attempts while typing = one scan
  • Separate, unrelated prompts = multiple scans

Scans make it easier to understand your AI usage patterns.

Normalization

Different AI tools report data in different formats. Intentra normalizes all events to a unified schema:

ToolNative FormatNormalized
CursorinputTokens, outputTokenstokens.input, tokens.output
Claudeusage.input_tokenstokens.input, tokens.output
GeminitokenCounttokens.input, tokens.output

This allows consistent analysis across tools.

Anomaly Detection

Intentra detects anomalies that indicate billing-relevant patterns such as:

  • Retry loops - Tool retries failed actions repeatedly
  • Ignored instructions - Tool diverged from your explicit directives
  • Context waste - Excessive tokens loaded but not used
  • Duplicate work - Same task performed multiple times

Detection Methods

PlanMethodDescription
FreeHeuristicPattern-based rules (15 detection patterns)
Pro/EnterpriseAI-poweredAnalyzes context (9x better detection)

Heuristic detection uses pattern matching - fast but misses subtle issues.

AI-powered detection understands context, catching anomalies that rules miss.

Both methods detect the same anomaly types, but AI is significantly more accurate.

Cost Estimation

Intentra estimates costs based on:

  • Token counts (input + output)
  • Model pricing
  • Usage over time

Note: Estimates are approximate and may not match actual provider bills.

Core Concepts - Intentra Docs