Plugins are telemetry, not Weave Router. Plugins observe
activity and send it to Weave; Router changes which model serves a request.
You can use either or both.
Choose a plugin
- Install the Claude Code plugin
- Install the Cursor plugin
- Install the GitHub Copilot plugin
- Install the Codex plugin
- Install the Grok Build plugin
Before you start
- For a shared install, an organization admin creates a plugin API key in Weave. Claude Code, Cursor, Copilot, Codex, and Grok Build also let any signed-in member create a personal install command that writes telemetry onto their own account. The full key is shown only once, so save the generated command or configuration securely.
- Install the plugin separately for each developer machine, unless you are using an MDM or fleet deployment described in the tool’s guide.
- Claude Code, Cursor, Codex, and Grok Build hook runtimes require Node.js 18 or later. GitHub Copilot’s native OpenTelemetry export does not require Node.js.
- Use the generated commands and configuration snippets from Weave as the source of truth for your organization and deployment environment.
Shared privacy controls
The Claude Code, Cursor, Codex, and Grok Build guides document the five content categories available to their installers: prompt bodies, agent messages, tool input/output, file paths, and git context. Each guide explains the individual flags and the--privacy-mode switch.
GitHub Copilot has one content setting, COPILOT_OTEL_CAPTURE_CONTENT, which controls content capture for Copilot Chat. The organization-wide Telemetry content retention policy is the floor for every member. Configure it under Settings → Organization → General → Telemetry content retention. Members can choose a stricter policy, but cannot override an organization restriction.
When prompt retention is off, Claude Code and Cursor hold prompt text until it is scored and then purge it. Grok Build has no hold, so Weave drops its prompt text at ingest.
After installation
Follow the verification and troubleshooting steps in the dedicated plugin guide. In general:- Run the plugin in the developer’s own user context.
- Start a new session, or restart the relevant application when the guide requires it.
- Check plugin activity and member attribution in Data.
- Review reports supported by the selected plugin, including AI skills where available. Copilot’s AI code LOC and AI output percentage require the GitHub Copilot integration.
Related guides
- AI tools overview — all supported AI tool integrations
- Connecting your data — full integration onboarding
- Claude Code — managed settings, Compliance API, and cost integrations
- Cursor — Admin API usage and spend
- GitHub Copilot — GitHub usage and billing
- Codex — Codex Analytics API and OpenAI direct API usage
