Nodge for VS Code

Sign in with your Nodge identity directly from VS Code. Push code, check logs, check API specs, and interact with the Nodge platform directly from your editor.

Features

• Sign in with Nodge — appears in VS Code's Accounts menu, just like GitHub
• Git credentials — push and pull to git.nodge.ai using your Nodge identity
• MCP server — exposes Nodge platform tools to any MCP-aware AI assistant in your editor
• Auto-config for Claude Code — in a Nodge project the extension writes the MCP server into the workspace .mcp.json so the Claude Code CLI picks it up, no manual setup
• Commit-context capture — records the "why" behind your work (plan, todos, decisions) per commit, so it's recoverable later by SHA via the nodge_commit_context_get tool

Getting Started

1. Install the extension
2. Click the Accounts icon (bottom-left) → Sign in with Nodge
3. Your browser opens → sign in on platform.nodge.ai → done

AI Assistant Integration

The extension registers a Nodge MCP server through VS Code's native mcpServerDefinitionProvider API. Once signed in, any MCP-aware assistant in your editor (Cursor's built-in chat, GitHub Copilot, Claude Code, Continue, and others) can call Nodge platform tools.

For the Claude Code CLI, the extension also writes the MCP server into the workspace .mcp.json automatically (in Nodge projects only). No manual configuration needed either way.

Commit-Context Capture

In a Nodge project, the extension seeds a small set of Claude Code hooks into the workspace .claude/settings.json. As you work, Claude Code stages your plan, todo progress, and decisions; on push, the platform folds them into a per-commit record. Later, any agent browsing git log can recover what was happening at a commit via the nodge_commit_context_get tool.

The hooks route through the extension's local server, so your Nodge token never touches disk. The hooks block is merged into your settings — existing hooks and other settings are left untouched.

Settings