Devcontainer Exec

Resolve the container once, then run project commands through it. Edit on the host, execute in the container when the source is bind-mounted. A .devcontainer/ directory is a cue to check the project's environment policy, not a reason to run unrelated container work.

Host: file tools, git, gh, docker. Container: install, build, test, lint, typecheck, codegen, migrations, app run.

Resolve and Verify

ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
docker ps --filter "label=devcontainer.local_folder=$ROOT" --format '{{.ID}}\t{{.Names}}'

VS Code and the devcontainer CLI set this label on the dev container, not compose sidecars. If there is no exact match, read resolution.md. Multiple matches require asking, never guessing; a shared bind mount alone does not prove identity.

Inspect the selected container: