4 docs tagged with "developer-tooling"

Why the VS Code integrated terminal is not a clean environment, how it becomes polluted, and how to detect, compare, and avoid dirty shells.

Why you should run your program in a clean external shell and let VS Code attach as a UI, instead of allowing VS Code to launch and orchestrate your runtime environment.

Running a coding agent in a container solves the trust problem by giving up the machine. If you want to keep the machine, the permission allowlist is where you make the tradeoff instead.

A language-agnostic breakdown of VS Code’s multi-process architecture, including the main subsystems and how to inspect them from the shell.