AutoGen (Multi-agent, MAINTENANCE MODE)

WHENWhen evaluating LocalCommandLineCodeExecutor for any path that may receive LLM-generated code, especially when reading the class docstring sanitization claim

ACTIONTreat LocalCommandLineCodeExecutor as having ZERO input filtering. Never use it for untrusted/LLM-generated code without (a) wrapping in DockerCommandLineCodeExecutor for container isolation, OR (b) wrapping CodeExecutorAgent with an explicit approval_func (interactive prompt, hardcoded allowlist, or model_client_approval_func). Audit any existing setup of `CodeExecutorAgent(code_executor=LocalCommandLineCodeExecutor())` — this is the documented canonical example and is unsafe by default. Maintenance-mode SLA means this docstring will NOT be corrected upstream; document the gap in your own skill/wrapper.

CONSEQUENCEundefined behavior

WHENWhen choosing a CodeExecutor backend for any production deployment or any path receiving LLM-generated code

ACTIONInstantiate `DockerCommandLineCodeExecutor(work_dir='coding', image='python:3-slim')` instead of `LocalCommandLineCodeExecutor()`. Confirm Docker daemon is running before starting. Use `await code_executor.start()` / `await code_executor.stop()` (or async context manager) to manage container lifecycle. Pin the image tag explicitly to avoid silent base-image upgrades; do NOT rely on `:latest`.

CONSEQUENCEundefined behavior