---
title: "Review and verify the setup config"
description: "Fix the setup steps or dev server command when verification fails, and run the check again."
url: https://help.modeinspect.com/en/articles/14-review-and-verify-the-setup-config
collection: "Set up your codebase"
updated: 2026-10-28
language: en
---

# Review and verify the setup config

Fix the setup steps or dev server command when verification fails, and run the check again.

When Auto-setup's recorded steps do not reproduce on a clean copy of your code, setup stops with **Verification failed** and shows you the setup config. Fix the step that broke, then verify again.

The setup config is the recipe Modeinspect replays every time it starts your codebase: the setup steps in order, the dev server command and port, and the environment variables.

**Before you start**

-   An engineer who knows how the project is run locally is the best person for this page. Use **Send to coworker** at the top to hand it over.
    

## Steps

1.  Read the banner under **Setup config**. It names the step that failed, or says that the dev server failed to start. The failed row is expanded and shows its output in red, with the exit code above it.
    
2.  Fix the step under **Setup steps**. Click a row to edit its name and command. To add a step, type the command in the field at the bottom and press `Enter`. Drag a row to reorder it, or hover it and click the bin to remove it.
    
3.  Check the **Dev Server** row. Click it to edit **Command** and **Port**. The output of the last start is shown below the fields.
    
4.  Check **Environment variables**. A variable the code reads but has no value shows **NOT SET**. The question mark next to a name shows where the code uses it. Add one with **Add variable**, or several with **Paste .env**. Values are stored as plaintext and applied when you save.
    
5.  Click **Verify Setup**. The page shows **Verifying codebase** while the steps replay on a clean copy of your code.
    

If the replay succeeds, the card reads **You're all set!** and **Create Canvas** opens your first canvas. If it fails, the setup config comes back with the new failure in the banner.

## If it does not work

-   **The same step fails again with the same output**: the command needs something the clean copy does not have, usually a file or a value. Add the missing environment variable, or add the step that creates the file before it.
    
-   **"Dev server failed to start"**: open the **Dev Server** row and compare **Command** with the script your team runs locally. For Vite projects the command needs an explicit `--port` that matches **Port**.
    
-   **Verify Setup is disabled**: there are no steps to replay. Add at least the install command.
    

## Related

-   [What happens during setup](https://help.modeinspect.com/en/articles/17-what-happens-during-setup.md)
    
-   [Answer Auto-setup's questions](https://help.modeinspect.com/en/articles/10-answer-auto-setup-questions.md)
    
-   [Add start scripts to a codebase](https://help.modeinspect.com/en/articles/13-edit-start-scripts.md)
    
-   [Edit a codebase's secrets](https://help.modeinspect.com/en/articles/12-edit-secrets.md)

## Related

- [Connect a GitHub repository](https://help.modeinspect.com/en/articles/11-connect-a-github-repository.md)
- [Upload a codebase as a zip](https://help.modeinspect.com/en/articles/16-upload-a-codebase-as-a-zip.md)
- [Start from a blank codebase](https://help.modeinspect.com/en/articles/15-start-from-a-blank-codebase.md)
- [What happens during setup](https://help.modeinspect.com/en/articles/17-what-happens-during-setup.md)
- [Answer Auto-setup's questions](https://help.modeinspect.com/en/articles/10-answer-auto-setup-s-questions.md)