# AutoPilot status update - 2

This week, I introduced a concept of a `base image` to to the AutoPilot service. A user can configure their own base image as they want, by installing all necessary tools or running builds so that the build cache exists for the worker from start.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1742615311914/ed65daa6-8de3-4f8b-8cfc-447619c6828f.png align="center")

This is the screenshot of a base image setup process. I installed nodejs and did `pnpm install`. So there’s a folder named `node_modules`. After then, I clicked `Finish Setup` button, an pressing the button creates a base docker image for the worker. It utilizes the `docker commit` command.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1742615383521/3c918e0e-82cc-4ee5-8f09-9bb4ff07b037.png align="center")

* Screenshot captured from a running instance of `pnpm dev` (using turborepo)
    

And after waiting for a while, I could use the base image in a worker. The base image does not have the AutoPilot vscode extension nor Roo Code, but the worker image has one.

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1742615477783/09386302-e289-411b-b6b9-36e267fa89ef.png align="center")

This is the screenshot of a new worker instance, from which you can find `node_modules`, Roo Code, and Dudy AutoPilot vscode extension.

---

With this change, a worker can drive a task from the start to the end by itself without an interaction. But I still need to polish lots of things, and I would be busy this weekend because of a GDG event.