Reuse a prepared container for separate coding-agent tasks
At a glance
A homelab builder uses Pixels checkpoints to start coding-agent containers from a prepared environment. This workflow is listed under Coding Agents, Containers, Checkpoints.
- Agents / tools
- Pixels, Incus, Claude Code, Codex, OpenCode
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Have a local Incus installation or an accessible remote daemon. Install Pixels with mise using `mise use -g github:deevus/pixels`; alternatively, building through Go requires Go 1.25 or later. 2) Run `pixels create base --egress agent --console`. Wait for provisioning, then install the dependencies your work needs in the base container. Pixels provisions coding-agent tools; use an agent account you are authorized to access. 3) Save the prepared state with `pixels checkpoint create base --label ready`. Start a separate task environment with `pixels create task1 --from base:ready`, then enter it with `pixels console task1` to do the work. 4) After preserving any deliverables you need, remove the disposable environment with `pixels destroy task1`. Keep the base checkpoint for subsequent tasks.
Worth knowing
The Lobsters author explicitly acknowledged sandbox security limitations. A reusable container and an egress allowlist are not proof that an agent cannot escape.