AI Coding Tools You Can Track with LineageLens

Coverage

LineageLens captures provenance from 11 AI coding tools — both editor assistants and agentic CLIs — via editor-level capture and a transparent local proxy. Here is exactly what is tracked for each tool, and how.

Full prompt + model capture (transparent proxy)

These tools talk to model APIs directly, so LineageLens sits as a transparent proxy at localhost:8788 and records the complete request: prompt, model version, tool metadata, and the resulting code insertion.

  • Claude Code — full prompt lineage, tool-use chains, per-insertion attribution.
  • OpenAI Codex CLI — full capture incl. agent task context.
  • Gemini CLI — full capture (adapter added in v1.5).
  • Goose — full capture of agent runs.
  • Continue — full capture for editor + agent flows.

Editor-level capture (extension)

These assistants render inside the editor, so the LineageLens VS Code extension observes accepted insertions and records the active assistant, session, and context. Full request bodies stay inside the vendor plugin; origin and acceptance are still attributed per line.

  • GitHub Copilot — per-acceptance attribution with session context.
  • Cursor — editor capture of AI insertions and Tab completions.
  • Windsurf — editor capture.
  • Codeium — editor capture.

Planned adapters

  • Aider — on the roadmap; capture via git-hook bridge.
  • Cline / Roo Code — on the roadmap.

Need a tool that isn't listed? The MCP server and adapter interface make custom agents first-class: teams have wired internal CLIs into LineageLens in an afternoon.

Start capturing provenance today

Every tier tracks all available tools — capture breadth is never paywalled. Install the free Base extension, or deploy Lite for proxy capture + dashboard in one container. Team governance and CI gates live on Plus.