VS Code Adapter

The VS Code adapter connects VS Code to FORG by registering a managed FORG MCP server in your VS Code User settings. AI sessions can then be attributed without installing a separate FORG extension. There is no FORG VS Code Marketplace extension.

Prerequisites

• VS Code with MCP support (an MCP-aware AI extension configured)
• FORG CLI installed and activated
• Node.js 18+ (for the MCP server process)

Install

forg connect vscode

This registers a managed FORG MCP server entry, backed bynpx -y forg-mcp@latest, in your VS Code User settings (settings.json):

• macOS: ~/Library/Application Support/Code/User/settings.json
• Linux: ~/.config/Code/User/settings.json
• Windows: %APPDATA%\\Code\\User\\settings.json

Reload VS Code after connecting so it picks up the new MCP server. The entry is idempotent and FORG-managed, so forg uninstall removes only the FORG footprint.

What gets captured

• Tool-call metadata and session boundaries from MCP-aware AI extensions
• Model, token, and cost metadata per session
• Auto-sampled session heartbeats (every 30 s for standalone hosts)

Verification

FORG_KEYSTORE=file:// forg status
# Reload VS Code, start a new AI session, and confirm signals arrive.

Notes

• FORG registers the MCP server only; it does not ship or require a VS Code extension.
• The adapter is metadata-only — prompt and completion content stay on your machine.