wcgw for VS Code: Setup & Config

What you can do with wcgw in VS Code

Choose wcgw for a shared interactive agent terminal plus code-editing and checkpoint tools.

• Run compiler checks and iterate on code changes.
• Edit large files through incremental replacements.

Before you start: wcgw in VS Code

• uv / uvx available to the MCP client
• Python 3.12 for the documented launch
• WSL on Windows

The README documents this configuration for Claude Desktop. A --shell argument can select bash or zsh. Understand the unrestricted shell and file-access risks before running it.

wcgw VS Code configuration

1. Choose VS Code configuration scope

   For wcgw, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add wcgw to VS Code

   Use the wcgw entry below in servers. Keep wcgw's documented stdio connection fields and your other VS Code entries.

3. Check wcgw in VS Code

   wcgw: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "wcgw": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "wcgw@latest"
      ],
      "env": {}
    }
  }
}

wcgw tools available to VS Code

wcgw's stored tool list documents 7 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

Initialize

Look for Initialize among VS Code's agent-mode tools after starting wcgw through the MCP controls.

BashCommand

Look for BashCommand among VS Code's agent-mode tools after starting wcgw through the MCP controls.

Run shell commands or send interactive input to the terminal.

ReadFiles

Look for ReadFiles among VS Code's agent-mode tools after starting wcgw through the MCP controls.

Read one or more files into the assistant context.

WriteIfEmpty

Look for WriteIfEmpty among VS Code's agent-mode tools after starting wcgw through the MCP controls.

FileEdit

Look for FileEdit among VS Code's agent-mode tools after starting wcgw through the MCP controls.

Modify a file using search-and-replace blocks.

ReadImage

Look for ReadImage among VS Code's agent-mode tools after starting wcgw through the MCP controls.

Load an image file for inspection.

ContextSave

Look for ContextSave among VS Code's agent-mode tools after starting wcgw through the MCP controls.

wcgw: full stored tool descriptions

Troubleshooting wcgw in VS Code

• Make uvx --python (from uv, for Python tools) available in the workspace, container, or remote environment hosting wcgw. Start through VS Code's MCP controls; inspect output and trust prompts.
• wcgw uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Default mode gives unrestricted shell and filesystem access.
• Known limitation: Code-writer command lists are not enforced allow-lists.
• Known limitation: Windows requires WSL.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions