Workbench displays compiled JS files from `.motia/compiled/` directory as steps

[zbango]

Environment

Windows 11 Pro 64 bits, node v24.12.0

Steps to Reproduce

1. Start the Motia development server:

   npm run dev

2. Verify that Motia Workbench loads normally on http://localhost:3000

3. Make any modification to a step file (e.g., src/hello/hello-api.step.ts)

4. Observe that Motia generates compiled JavaScript files in src/.motia/compiled/ directory:

   • Example: src/.motia/compiled/hello/hello-api.step.js

5. Refresh the Workbench page in the browser

6. Observe that the compiled .js files are now displayed as separate steps in the Workbench UI

Expected Behavior

The Workbench should only display the original step files (.step.ts, .step.js, _step.py, etc.) and should ignore compiled files in the .motia/compiled/ directory. The compiled files should be used internally by Motia but should not appear as steps in the visual Workbench interface.

Actual Behavior

After refreshing the Workbench page, both the original step files and their compiled JavaScript counterparts from src/.motia/compiled/ are displayed as separate steps in the UI. This creates visual noise and confusion, as users see duplicate entries:

• hello-api.step.ts (original)
• hello-api.step.js (compiled version from .motia/compiled/)

Relevant Logs/Console Output

- The compiled files are generated automatically when step files are modified during development

Screenshots

Motia Version

0.17.6-beta.187

Additional Context

No response

[JuCarr]

I'm experiencing the same issue, Ubuntu 20.04, Node v22.21.1, Motia 0.17.6-beta.187.

This makes the dev mode really painful to work with as any update breaks the workflow by duplicating steps.

The hot reloading should only create the .motia folder at the root of the project.