# Workflow





<DocImage src="features/workflow/workflow-panel" alt="Workflow panel with System Setup, Run Step and Project Dependencies cards and their commands" width="1280" height="1316" />

The Workflow panel defines the commands Ideavo uses to set up, run, and build your project. It is automatically configured by the agent when you create or import a project — and fully editable at any time to match your setup.

<Cards>
  <Card title="Auto-configured" icon="<FcAutomatic style={{ filter: &#x22;grayscale(100%)&#x22; }} />" description="The agent detects your framework and pre-fills every workflow section on project creation — no manual setup needed." />

  <Card title="Fully Editable" icon="<MdEdit />" description="Override any command, add extra steps, or restructure the workflow to fit your stack at any time." />
</Cards>

## Sections [#sections]

### System Setup [#system-setup]

Commands that run once to configure the system environment — typically used for installing system-level dependencies. Click **Run Setup** to execute them manually when needed.

### Project Dependencies [#project-dependencies]

Commands to install project dependencies (e.g. `bun i`, `npm install`). These run before the dev server starts to ensure all packages are available.

### Run Step [#run-step]

Commands to start the development server. The agent pre-fills this based on your framework (e.g. `bun run dev --port 4000`). Use **+ Add Run Step** to add multiple run steps for projects with parallel services.

### Build Steps [#build-steps]

Commands to build the project for production (e.g. `bun run build`). Add additional steps with the **+** button for multi-stage build processes.

### Deploy Steps [#deploy-steps]

Commands to start the production server after a build (e.g. `bun run start`). Used when running your app outside of the dev environment.

### Environment Paths [#environment-paths]

File paths for environment variable files (e.g. `.env`). Ideavo uses these to load the correct variables at runtime. Add additional paths if your project uses multiple env files.

### Cleanup Files [#cleanup-files]

Files and directories removed before a fresh install or build (e.g. `.next`, `node_modules`). Ideavo clears these to guarantee a clean environment on each setup.

## Editing the Workflow [#editing-the-workflow]

Each section has an input field and a **+** button to add new commands. Existing commands can be edited inline — click any command to modify it directly. The agent picks up changes automatically on the next run.

<Callout type="info">
  If the agent makes changes to your project that affect the framework or
  dependencies, it may update the workflow automatically to reflect the new
  setup.
</Callout>

## FAQ [#faq]

<Accordions>
  <Accordion title="What order do workflow steps run in?">
    On startup: **Cleanup → System Setup → Project Dependencies → Run Step**.
    Build and Deploy steps only run when you trigger a build or deployment —
    they do not run automatically on dev server start.
  </Accordion>

  <Accordion title="Will manually editing the workflow break auto-detection?">
    No. Manual edits persist and take priority. The agent will only update the
    workflow if you explicitly ask it to reconfigure the project setup.
  </Accordion>

  <Accordion title="Can I add multiple run steps for different services?">
    Yes. Use **+ Add Run Step** to add commands for each service. All run steps
    execute in parallel, so you can start a frontend and a backend server at the
    same time.
  </Accordion>

  <Accordion title="What if my project uses a monorepo or custom folder structure?">
    Edit the run and build steps to point to the correct workspace or
    subdirectory (e.g. `bun run dev --filter=web`). You can also adjust
    Environment Paths to pick up env files outside the project root.
  </Accordion>
</Accordions>
