Connect Claude Code, Cursor, VS Code, Windsurf, JetBrains, OpenCode, Copilot, Codex, Gemini CLI, Aider, Warp, and more with the same FORG agent.
Full session lifecycle, tool call tracking, and cost per conversation for every Claude Code session.
forg connect claude-codeView docs →Track Cursor AI sessions including Cmd-K, chat, and Composer. Per-project cost attribution.
forg connect cursorView docs →Works with Copilot, Codeium, and any VS Code AI extension. Language-agnostic signal collection.
forg connect vscodeView docs →Full Windsurf Cascade session observability. Flow tracking and multi-step operation costs.
forg connect windsurfView docs →Supports IntelliJ, PyCharm, WebStorm, and all JetBrains IDEs with AI Assistant.
forg connect jetbrainsView docs →Native OpenCode hook integration for session lifecycle, task tracking, and tool use.
forg connect opencodeView docs →Lua plugin hooks for terminal-native AI coding sessions in Neovim.
forg connect neovimView docs →Track Copilot suggestion acceptance, inline completions, and Copilot Chat sessions.
forg connect copilotView docs →Open-source AI coding assistant. Works with any model via Continue's plugin architecture.
forg connect continueView docs →MCP server in ~/.codex/config.yaml for Codex CLI session telemetry.
forg connect codexView docs →MCP server integration for Google Gemini CLI sessions, model usage, and cost tracking.
forg connect gemini-cliView docs →Context injection via AGENTS.md for Aider pair-programming session visibility.
forg connect aiderView docs →MCP-powered session tracking inside Warp's AI-assisted terminal workflows.
forg connect warpView docs →MCP server for Roo Code agent workflows in VS Code — tool metadata and model telemetry.
forg connect rooView docs →MCP server for Cline's agentic VS Code workflows — tool calls, model usage, session boundaries.
forg connect clineView docs →Profile injection for PowerShell terminals so forg-mcp is available anywhere your shell starts.
forg connect powershellView docs →Every adapter follows the same lightweight protocol — three steps from tool to dashboard.
The adapter hooks into your editor, CLI, shell profile, or MCP config and captures model, latency, cost, and session context without storing prompt text.
Signals are HMAC-SHA256 signed and emitted to the FORG local agent at 127.0.0.1:6247/emit so policy checks happen locally first.
The rule engine evaluates budgets, blocks, and alerts in real time while your dashboard keeps a full session history across every connected adapter.
Run forg statusanytime to see what's connected.
Shared capabilities across all official adapters.
| Feature | All official adapters |
|---|---|
| Real-time telemetry | ✓ |
| Budget enforcement | ✓ |
| Rule triggers | ✓ |
| Session recording | ✓ |
| Cost allocation | ✓ |
Any tool that can make an HTTP POST request can emit FORG signals. The full protocol is under 100 lines to implement.
HMAC-SHA256 signed via X-FORG-Signature header. Key provisioned at adapter registration.
Install the FORG agent, connect an adapter, and watch signals appear in your dashboard — no configuration required.
forg connect claude-code