Environment setup

Cue turns machine setup into an executable process. The Create Local Environment wizard guides the author through eight steps, then compiles the result into a setup run that another developer can follow on a new computer.

Start from the project

Environment setup belongs with the project it prepares. Register the project in Cue first, connect it to the appropriate team, and define the IDE, terminal, folders, URLs and launch profiles that should be available after setup.

Before building the setup run, review workspace readiness on a working machine. Dependency checks help identify the tools and conditions the project expects. The same readiness view later shows what is missing on the new machine before the run begins.

Use the eight-step wizard

Open Create Local Environment and work through its eight guided steps. The wizard compiles setup activities into an executable run rather than producing another static checklist. The run can cover the core path of getting the code, restoring the project and configuring the local environment.

Describe each part so that someone who did not invent the setup can understand the expected result. Use typed checks and validations where a condition can be verified. If a script is part of the process, Cue requires explicit confirmation before it runs. This keeps automation visible to the person preparing the machine.

The result is a procedure that can be executed, inspected and safely resumed if the work is interrupted.

Reuse setup with blueprints

Blueprints are reusable templates for projects and procedures shared through a workspace. Use a project blueprint when several projects need a common starting structure. Use a procedure blueprint when the same setup shape should be adapted without recreating every step.

A blueprint is a template, while the compiled environment run is the concrete work for a machine. Keep machine-specific paths or protected values out of a shared template. Secrets stored in Cue variables are encrypted at rest locally and on the server.

Verify the finished machine

After the setup run completes, return to workspace readiness. Resolve anything still marked as missing, then use the saved run or debug profile to launch the project in its intended order. If Visual Studio is part of the profile, verify that Cue can attach as expected.

When the run exposes a missing instruction or an unnecessary manual step, improve the procedure or its blueprint. The next new hire or replacement machine then receives the corrected process.

Continue the workflow