Docker makes Gordon generally available for container workflows

Docker made its container-focused agent Gordon generally available on May 19. The announcement says it is built into Docker Desktop 4.74 and later and the Docker CLI, where it can inspect the current container environment, propose changes, and run approved actions.

Container context is the product boundary

Gordon can read running-container logs, images, Compose files, and the working directory. Docker positions it for tasks such as diagnosing an exiting container, drafting a Dockerfile and Compose setup, or cleaning unused images. Under the hood it has shell and filesystem operations, Docker CLI access, Docker documentation, and web access.

By default, Gordon shows each shell command, file modification, and Docker operation before it runs and asks the user to approve, reject, or redirect it. Permissions reset when the session ends. Docker also allows auto-approve for trusted workflows. Enabling it changes the control boundary: the user is trusting the configured workflow instead of reviewing every individual action, so teams should check the active approval mode before relying on a per-action review point. In either mode, users need to understand which files, credentials, mounts, and networks the local Docker environment exposes.

Start with reversible jobs

A team evaluating Gordon should begin with a disposable repository and local containers. Give it a known broken Compose stack, record the evidence it uses, and compare its proposed fix with a manual diagnosis. Keep auto-approve disabled for the first evaluation, verify refusal and cancellation paths as well as successful execution, and then document any workflow for which the team chooses to enable it.

For shared development machines, document whether project directories contain production credentials or broadly privileged Docker contexts before enabling agent actions. Container cleanup also deserves care: “unused” is a local engine state, and deleting an image can affect an offline or expensive rebuild.

Gordon’s general availability brings agent assistance directly into Docker’s container workflow. Teams can judge it by a practical standard: whether it produces reviewable, reproducible changes and leaves enough evidence for another engineer to understand what happened.