Collector matrix

Most collectors tail local coding-agent logs. Nothing is injected into your application code. Lite runs collectors in-process. Cloud and Enterprise use a fleet collector that pushes to a manager.

Cloud uses the full Cloud profile (TIER_4_CLOUD) — the registry below is enabled, plus git context and traces. Enterprise still gates sources by tier.

By source

Source	Status	Enterprise	Cloud	Notes
Cursor	GA	Core+	Yes	~/.cursor/projects
Claude Code	GA	Core+	Yes	~/.claude/projects
Claude Desktop	GA	Core+	Yes	Desktop app logs — not Claude Code JSONL
Codex	GA	Core+	Yes	~/.codex/sessions
Kiro CLI / Kiro IDE	GA	Analytics+	Yes	Analytics collectors
Warp	GA	Analytics+	Yes	Platform-specific warp.sqlite
Copilot	GA	Analytics+	Yes	~/.copilot/session-state
Windsurf, Continue, Cline, Aider, OpenCode	GA	Analytics+	Yes	Registry watch paths
Claude Cowork	GA	Integration+	Yes	OTLP logs to the manager — not a log-file tailer

With platform.auto-discovery: true (Cloud enroll default), the agent probes known OS/WSL layouts and picks the path with the newest readable logs. Completely custom paths still need watch-path.

The marketing Tools page is the product-facing matrix.

Lite vs fleet

• Lite — in-process collectors for a single developer; no Docker.
• Cloud — one OS-service collector per workstation; Cloud install. Heartbeats on Collectors.
• Enterprise — one fleet agent per workstation; unsigned packages. Tier gates which sources the manager enables.

Application traces are not produced by these watchers: Cloud traces.