Run, Isolate, and Act: A Minimal Primitive for Container Workflows

You’ve probably wanted to run a one-off command in a clean environment, or pipe a task into an AI tool and do something with the result—commit the changes, export a patch, run tests—without wiring up a full pipeline. dockpipe is a small open-source CLI that does exactly that: one primitive, any command, optional follow-up action. This post is a short intro to what it is, why it’s useful, and how you can use it for automation and chained workflows (including AI). What is dockpipe? dockpipe is a single primitive for running commands in disposable containers and optionally acting on the result. It’s not a workflow engine, not an AI framework, and not tied to any vendor. It’s a composable building block you plug into your own scripts and automation. The model: Spawn — Start a container from an image (default is a light dev image; you can use your own). Run — Execute whatever you pass in: a one-liner, a script, or a tool (e.g. Claude, Codex, npm test ). Act — Optionally run an action script