FORG includes official adapters for all major AI coding tools. Claude Code, Codex CLI, and Gemini CLI are co-primary — fully supported with dedicated docs, install paths, and signal coverage. All adapters are FORG-maintained.
FORG-maintained integrations with supported docs and install paths.
Session lifecycle, tool calls, token budgets, and cost attribution for Claude Code.
Track Cursor chat, Composer, Cmd-K, project attribution, and model usage.
VS Code extension telemetry for AI extensions, editor activity, and session signals.
Cascade session observability, chat metadata, and multi-step flow tracking.
One adapter for IntelliJ, PyCharm, WebStorm, GoLand, Rider, DataGrip, and CLion.
Native hook integration for OpenCode sessions, tasks, and tool usage.
Lua plugin telemetry for AI-assisted terminal-native workflows.
Copilot completions, Copilot Chat, seat utilization, and ROI measurement.
Open-source AI coding assistant telemetry across VS Code and JetBrains.
MCP server registration in ~/.codex/config.yaml for Codex CLI session telemetry.
MCP server registration in ~/.gemini/settings.json for Gemini CLI session tracking.
Pair-programming session telemetry for Aider workflows via AGENTS.md injection.
MCP server registration in Zed settings for AI workflow telemetry.
MCP server registration in ~/.warp/mcp_config.json for Warp terminal AI sessions.
PowerShell profile injection to expose forg-mcp as a shell function.
MCP server registration in ~/.roo/mcp_settings.json for Roo Code agent workflows.
MCP server registration for Cline agentic VS Code sessions, tool calls, and model usage.
Roadmap integrations intended to become FORG-maintained adapters.
Amazon Q usage visibility for AWS-heavy engineering teams.
Cody chat and code intelligence session metadata.
Tabnine usage telemetry for completion-heavy teams.
Supermaven completion metadata and developer workflow attribution.
Augment Code usage telemetry for enterprise codebase assistants.
Testing and code-quality assistant telemetry.
Local agent session telemetry for Goose workflows.
Any HTTP-capable AI app, CLI, IDE, or agent can emit FORG signals through the open protocol.
Emit FORG signals from Replit-based AI build sessions.
Protocol path for autonomous software-engineering agent telemetry.
Pull-request AI review events through protocol integration.
Browser-based build-agent sessions through protocol events.
App-builder AI workflow telemetry through the open protocol.
Design/build generation telemetry for v0-style workflows.
Multi-agent workflow telemetry through custom protocol events.
Graph-based agent run metadata and outcome tracking.
Agent conversation metadata for AutoGen workflows.
Internal AI agents can emit FORG signals with a signed HTTP POST.
Emit AI-job telemetry from scripts, CI pipelines, and automation.
Tool adapters observe developer workflows. Gateway providers route model requests when teams need hard enforcement, virtual keys, provider budgets, and routing analytics.
Explore GatewayIf your tool can make an HTTP request, it can emit FORG signals. Build a custom adapter or submit one to the community registry.