> ## Documentation Index
> Fetch the complete documentation index at: https://docs.weaveos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect your AI coding assistants to track adoption and impact

Weave connects to the AI coding tools your engineers use, including Claude Code, Cursor, GitHub Copilot, Codex, Windsurf, and Devin, and measures adoption, AI-attributed code output, and spend across people, teams, and tools. It labels tools as foreground AI, which engineers interact with directly, or background AI, which works automatically in the background, so work from autonomous agents and review bots can be told apart from work engineers do with an assistant.

For per-developer telemetry from Claude Code, Cursor, GitHub Copilot, Codex, or Grok Build, follow the [Weave plugin installation guide](/tutorials/weave-plugin-installation).

## Supported tools

### Direct integrations

These tools can be connected directly to Weave:

<CardGroup cols={2}>
  <Card title="Cline" href="/ai-tools/cline">
    OpenTelemetry integration for code generation tracking
  </Card>

  <Card title="Cursor" href="/ai-tools/cursor">
    API integration for IDE usage and code generation
  </Card>

  <Card title="Kiro" href="/ai-tools/kiro">
    S3 integration for AI IDE usage and code generation
  </Card>

  <Card title="Windsurf" href="/ai-tools/windsurf">
    API integration for IDE usage and code generation
  </Card>

  <Card title="Claude Code" href="/ai-tools/claude-code">
    Telemetry and API integration for code generation and cost
  </Card>

  <Card title="Oh My Pi" href="/ai-tools/oh-my-pi">
    OTLP integration for model, token, session, and OpenRouter cost tracking
  </Card>
</CardGroup>

**Other supported tools:**

* [Amazon Q](/ai-tools/amazon-q) (S3 integration)
* [Augment](/ai-tools/augment) (API key)
* [Codex](/ai-tools/codex) ([plugin](/tutorials/weave-plugin-installation)) — also covers direct OpenAI API usage
* [Devin](/ai-tools/devin) (Cognition Enterprise API)
* [GitHub Copilot](/ai-tools/copilot) (via GitHub integration) — [plugin](/tutorials/weave-plugin-installation) for per-developer Chat telemetry
* Firebender (API key)
* [Gemini CLI](/ai-tools/gemini-cli) (telemetry)
* [Gemini Code Assist](/ai-tools/gemini-code-assist) (BigQuery integration)
* [Grok Build](/ai-tools/grok-build-plugin) (plugin)
* [Hermes](/integrations/ingest-api) (OTLP)
* [AI Gateway](/integrations/ingest-api) (OTLP — custom model gateways, AWS Bedrock proxies)
* JetBrains (IDE Services API token)
* [OpenClaw](/integrations/ingest-api) (OTLP)
* [Pi](/ai-tools/oh-my-pi) (OTLP for usage and cost; git attribution for AI-assisted code)
* [OpenRouter](/ai-tools/openrouter) (Analytics API for usage and cost)
* [Sourcegraph](/ai-tools/sourcegraph) (CSV upload)
* Weave Router (session-matched GitAI attribution for Codex and Claude Code)

Router attribution uses GitAI's measured code contributions and matching Router
session metadata. A native session ID is stable while the client stays on the router;
turning the router off starts a new session, so a match attributes the whole GitAI session.
Unmatched or conflicting contributions keep their Codex or Claude Code label;
using `/fm` through the Router does not create a separate AI tool. Code attribution
does not change token usage or billing records.

### Auto-detected tools

These tools are automatically detected from commit metadata (no setup required):

* CodeRabbit
* Continue
* Cubic
* [Devin](/ai-tools/devin) (connect the Cognition API for ACU activity and cost)
* [Gemini Code Assist](/ai-tools/gemini-code-assist) (connect the BigQuery integration for IDE usage metrics)
* Graphite
* Greptile
* Jules
* Junie
* Nori
* OpenCode
* OpenHands
* Parameter
* [Pi](/ai-tools/git-attribution) (requires git attribution)
* Sazabi
* Warp
* Wispbit

## Foreground vs background AI

Weave categorizes AI tools into two groups:

**Foreground AI** — Tools that engineers interact with directly:

* AI Gateway, Claude Code, Cline, Codex, Copilot, Cursor IDE
* Firebender, Gemini CLI, Gemini Code Assist, Grok, Hermes Agent, Junie, Nori, OpenClaw, OpenCode, OpenRouter
* Pi, Warp, Windsurf, Augment, Auggie Interactive
* Sourcegraph, Amazon Q, Kiro, JetBrains AI Assistant
* Weave Router

**Background AI** — Tools that work automatically in the background:

* Auggie Automation, Augment Code Review
* CodeRabbit, Continue, Cubic
* Cursor Agent, Cursor Bugbot
* Devin, GitHub, Graphite
* Greptile, Jules, Junie Bot
* OpenHands, Parameter, Sazabi, Wispbit

This distinction helps you understand both active AI usage and passive AI assistance.

## What you can measure

Once connected, you can track:

* **[AI output percentage](/metrics/ai-output-percentage)** — What portion of output is AI-attributed
* **[AI LOC](/metrics/ai-code-loc)** — Lines of code written with AI assistance
* **[AI tool costs](/metrics/ai-tool-costs)** — Spending on AI tools, using provider-reported billing where available (including OpenRouter-reported cost from Oh My Pi), or estimated / seat-based otherwise
* **[AI efficiency index](/metrics/ai-efficiency-index)** — A 0 to 100 score that combines AI output, AI usage percentage, AI cost per user, and code turnover
* **AI adoption trends** — How AI usage changes over time

## Getting started

<Steps>
  <Step title="Choose your tools">
    Select which AI tools your team uses from the supported list
  </Step>

  <Step title="Connect integrations">
    Follow the setup guide for each tool (Cline, Cursor, Kiro, Windsurf, Claude
    Code, or [Oh My Pi](/ai-tools/oh-my-pi))
  </Step>

  <Step title="Wait for sync">
    Allow time for initial data sync (usually a few minutes)
  </Step>

  <Step title="View metrics">
    Access AI metrics in Reports and Overview pages
  </Step>
</Steps>

## Data privacy

Weave tracks AI usage metadata and prompt content:

* Number of AI-generated lines
* Tool usage frequency
* Cost and subscription data
* Commit metadata with AI attribution
* User prompt text (used for activity classification; system messages are excluded)

**We never access:**

* Source code content or diffs
* AI model responses
* File paths or project structure
* Individual keystroke data

## Common questions

### Which AI coding tools does Weave support?

Claude Code, Cursor, GitHub Copilot, Codex, Windsurf, Devin, Cline, Kiro, Amazon Q, Augment, Gemini CLI, Gemini Code Assist, Sourcegraph, OpenRouter, and the other tools listed under [supported tools](#supported-tools). Tools such as CodeRabbit, Greptile, Jules, and OpenHands are detected from commit metadata with no setup.

### How does Weave separate agent work from developer-assisted work?

Tools are grouped into [foreground and background AI](#foreground-vs-background-ai). Add the **Background vs. foreground AI** chart to a [custom dashboard](/features/custom-dashboards) to split AI lines of code between the two, and register internal bots as [custom AI agents](/features/custom-ai-agents) with the category that fits.

### Do I need the Weave plugin?

For many tools, no: usage and cost come through an API key, telemetry, or your code platform. The [Weave plugin](/tutorials/weave-plugin-installation) for Claude Code, Cursor, GitHub Copilot, Codex, or Grok Build adds per-developer session data that [AI skills](/reports/ai-skills) scoring uses.

### Can I compare what each tool costs with the output it produces?

Yes. [AI tool costs](/metrics/ai-tool-costs) shows spend per tool and, where the data allows, per engineer. The AI report's **Cost per output by tool** chart divides that spend by AI-attributed code output; see [AI ROI](/reports/ai-roi).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.