Skip to main content
The current app exposes Cursor, Claude, and Codex under AI Analytics. Copilot is marked Coming Soon.

​
Cursor

Settings → Team → Cursor can expose an organization API key, automatic user mapping, analytics, and key update or removal. Verify suggested mappings before relying on member-level analytics.

​
Claude Code

The Claude Code setup can expose:
  • OpenTelemetry configuration
  • Anthropic admin or platform key
  • Standard API key
  • User mapping
Choose centralized OpenTelemetry when the organization operates a trace pipeline, or use a supported local CLI path for a pilot. Check for duplicate ingestion if multiple paths are enabled. Claude Code configuration showing OpenTelemetry, admin platform key, and standard API key controls

​
Codex

The Codex setup distinguishes OpenAI Platform organization usage from ChatGPT Enterprise Codex workspace analytics. Choose the source that matches how the organization buys and uses Codex, then verify user mapping.

​
Local CLI collection

Authenticate first:
Use the explicit local workflow to inspect each stage:
The combined entelligence insights --agent workflow can gather supported sessions, prepare the Agent Insights data, synchronize it, and arm the daily workflow. Use entelligence insights schedule --at 09:00 to manage the recurring time.
Exact source availability, arguments, and flags depend on the installed CLI version. Run entelligence insights --help and the relevant subcommand help before rollout.
Agent analytics can expose member-level behavior and spend. Publish an appropriate-use policy and verify uploaded fields before broad collection.

​
Verify

  • The expected source is included.
  • Test activity maps to the right member.
  • Tool and model names are plausible.
  • Unresolved users remain unresolved instead of being guessed.
  • Removing or rotating the credential behaves as expected.

​
Next step

Follow the Agent Insights rollout or review the CLI command checklist.