VS Code Extension

Open a CropsCode container in Visual Studio Code to browse files, edit code, and use the integrated terminal as if working locally.

Prerequisites

• VS Code (or VS Code Insiders) installed
• Dev Containers extension installed
• A running CropsCode container

Install the extension:

code --install-extension ms-vscode-remote.remote-containers

Configure for Podman

VS Code defaults to Docker. If your worker uses Podman, tell VS Code where to find the socket.

macOS

1. Find your Podman socket:

podman machine inspect --format '{{.ConnectionInfo.PodmanSocket.Path}}'

2. Add to VS Code settings.json:

{
  "dev.containers.dockerPath": "podman",
  "dev.containers.dockerSocketPath": "<your-socket-path>"
}

Windows

1. Ensure the Podman machine is running:

podman machine start

2. Find your pipe path:

podman machine inspect --format '{{.ConnectionInfo.PodmanPipe.Path}}'

3. Add to VS Code settings.json:

{
  "dev.containers.dockerPath": "podman",
  "dev.containers.dockerSocketPath": "<your-pipe-path>"
}

Docker Desktop

No configuration needed — VS Code detects Docker automatically.

Attach to a Container

From the UI

1. Open VS Code
2. Ctrl+Shift+P (or Cmd+Shift+P on macOS) → Dev Containers: Attach to Running Container…
3. Select your container (e.g. claude-code-terminal-github-...)
4. A new window opens connected to the container
5. Ctrl+O (or Cmd+O) to open a folder inside the container

From the command line

macOS/Linux:

code --folder-uri "vscode-remote://attached-container+$(printf '<container-id>' | xxd -p)/workspace"

Windows (PowerShell):

$hexId = -join ([System.Text.Encoding]::UTF8.GetBytes("<container-id>") | ForEach-Object { '{0:x2}' -f $_ })
code --folder-uri "vscode-remote://attached-container+$hexId/workspace"

Use podman ps or docker ps to find the container ID.

Troubleshooting

”Cannot connect to the Docker daemon”

• Podman: Make sure the machine is running — podman machine start
• Docker: Make sure Docker Desktop is running
• Verify the socket/pipe path in your VS Code settings

Container doesn’t appear in the list

• Verify the container is running: podman ps
• Check dev.containers.dockerPath is set correctly
• Check dev.containers.dockerSocketPath points to the right socket

VS Code shows “Installing server…” for a long time

First-time attachment installs the VS Code server inside the container. Subsequent connections reuse the cache and are much faster.