motia 0.17.11-beta.194-563479 → 0.17.12-beta.194

package/dist/create/templates/hello/.env

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello/README.md.txt

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
 
-A Motia project created with the starter template.
+This is a **Motia** project bootstrapped with the Motia CLI.
 
-## What is Motia?
-
-Motia is an open-source, unified backend framework that eliminates runtime fragmentation by bringing **APIs, background jobs, queueing, streaming, state, workflows, AI agents, observability, scaling, and deployment** into one unified system using a single core primitive, the **Step**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 
 ## Quick Start
 
@@ -17,67 +15,19 @@ yarn dev
 pnpm dev
 ```
 
-This starts the Motia runtime and the **Workbench** - a powerful UI for developing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-
-## Step Types
-
-Every Step has a `type` that defines how it triggers:
-
-| Type | When it runs | Use case |
-|------|--------------|----------|
-| **`api`** | HTTP request | REST APIs, webhooks |
-| **`event`** | Event emitted | Background jobs, workflows |
-| **`cron`** | Schedule | Cleanup, reports, reminders |
-
-## Development Commands
-
-```bash
-# Start Workbench and development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-
-# Start production server (without hot reload)
-npm run start
-# or
-yarn start
-# or
-pnpm start
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
 
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
+You can start editing the project by making changes to `src/hello/hello-api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
 
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
 
-## Project Structure
-
-```
-steps/              # Your Step definitions (or use src/)
-motia.config.ts     # Motia configuration
-```
+## Project Config
 
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 
 ## Learn More
 
-- [Documentation](https://motia.dev/docs) - Complete guides and API reference
-- [Quick Start Guide](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
-- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia architecture
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
+- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/hello_js/.env

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello_js/README.md.txt

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
 
-A Motia project created with the starter template.
+This is a **Motia** project bootstrapped with the Motia CLI.
 
-## What is Motia?
-
-Motia is an open-source, unified backend framework that eliminates runtime fragmentation by bringing **APIs, background jobs, queueing, streaming, state, workflows, AI agents, observability, scaling, and deployment** into one unified system using a single core primitive, the **Step**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 
 ## Quick Start
 
@@ -17,67 +15,19 @@ yarn dev
 pnpm dev
 ```
 
-This starts the Motia runtime and the **Workbench** - a powerful UI for developing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-
-## Step Types
-
-Every Step has a `type` that defines how it triggers:
-
-| Type | When it runs | Use case |
-|------|--------------|----------|
-| **`api`** | HTTP request | REST APIs, webhooks |
-| **`event`** | Event emitted | Background jobs, workflows |
-| **`cron`** | Schedule | Cleanup, reports, reminders |
-
-## Development Commands
-
-```bash
-# Start Workbench and development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-
-# Start production server (without hot reload)
-npm run start
-# or
-yarn start
-# or
-pnpm start
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
 
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
+You can start editing the project by making changes to `src/hello/hello-api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
 
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
 
-## Project Structure
-
-```
-steps/              # Your Step definitions (or use src/)
-motia.config.ts     # Motia configuration
-```
+## Project Config
 
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 
 ## Learn More
 
-- [Documentation](https://motia.dev/docs) - Complete guides and API reference
-- [Quick Start Guide](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
-- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia architecture
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
+- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/hello_multilang/.env

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello_multilang/README.md.txt

@@ -1,20 +1,8 @@
 # {{PROJECT_NAME}}
 
-A Motia project created with the **multi-language** starter template (TypeScript + Python).
+This is a **Motia** project bootstrapped with the Motia CLI.
 
-## What is Motia?
-
-Motia is an open-source, unified backend framework that eliminates runtime fragmentation by bringing **APIs, background jobs, queueing, streaming, state, workflows, AI agents, observability, scaling, and deployment** into one unified system using a single core primitive, the **Step**.
-
-## Polyglot Architecture
-
-This template demonstrates Motia's polyglot capabilities by combining:
-
-- **TypeScript**: API endpoint (`hello-api.step.ts`) - handles HTTP requests
-- **Python**: Event processor (`process_greeting_step.py`) - handles background processing
-- **JavaScript**: Logger (`log-greeting.step.js`) - handles workflow completion
-
-This shows how you can use the best language for each task while keeping everything in a single unified system.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 
 ## Quick Start
 
@@ -27,80 +15,19 @@ yarn dev
 pnpm dev
 ```
 
-This starts the Motia runtime and the **Workbench** - a powerful UI for developing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-
-## How It Works
-
-1. **TypeScript API Step** receives the HTTP request at `/hello`
-2. It emits a `process-greeting` event with the request data
-3. **Python Event Step** picks up the event, processes it, and stores the result in state
-4. Python emits a `greeting-processed` event
-5. **JavaScript Event Step** logs the completed workflow
-
-## Step Types
-
-Every Step has a `type` that defines how it triggers:
-
-| Type | When it runs | Use case |
-|------|--------------|----------|
-| **`api`** | HTTP request | REST APIs, webhooks |
-| **`event`** | Event emitted | Background jobs, workflows |
-| **`cron`** | Schedule | Cleanup, reports, reminders |
-
-## Development Commands
-
-```bash
-# Start Workbench and development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-
-# Start production server (without hot reload)
-npm run start
-# or
-yarn start
-# or
-pnpm start
-
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
 
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+You can start editing the project by making changes to `src/hello/hello-api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
 
-## Project Structure
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
 
-```
-steps/                           # Your Step definitions
-├── hello/
-│   ├── hello-api.step.ts       # TypeScript API endpoint
-│   ├── process_greeting_step.py # Python event processor
-│   └── log-greeting.step.js    # JavaScript logger
-motia.config.ts                  # Motia configuration
-requirements.txt                 # Python dependencies
-```
+## Project Config
 
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 
 ## Learn More
 
-- [Documentation](https://motia.dev/docs) - Complete guides and API reference
-- [Quick Start Guide](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
-- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia architecture
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
+- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/hello_python/.env

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+APP_NAME="Motia App"
+GREETING_PREFIX="Hello"

package/dist/create/templates/hello_python/README.md.txt

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
 
-A Motia project created with the starter template.
+This is a **Motia** project bootstrapped with the Motia CLI.
 
-## What is Motia?
-
-Motia is an open-source, unified backend framework that eliminates runtime fragmentation by bringing **APIs, background jobs, queueing, streaming, state, workflows, AI agents, observability, scaling, and deployment** into one unified system using a single core primitive, the **Step**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 
 ## Quick Start
 
@@ -17,68 +15,19 @@ yarn dev
 pnpm dev
 ```
 
-This starts the Motia runtime and the **Workbench** - a powerful UI for developing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-
-```bash
-# Test your first endpoint
-curl http://localhost:3000/hello
-```
-
-## Step Types
-
-Every Step has a `type` that defines how it triggers:
-
-| Type | When it runs | Use case |
-|------|--------------|----------|
-| **`api`** | HTTP request | REST APIs, webhooks |
-| **`event`** | Event emitted | Background jobs, workflows |
-| **`cron`** | Schedule | Cleanup, reports, reminders |
-
-## Development Commands
-
-```bash
-# Start Workbench and development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-
-# Start production server (without hot reload)
-npm run start
-# or
-yarn start
-# or
-pnpm start
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
 
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
+You can start editing the project by making changes to `src/hello/hello_api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
 
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
 
-## Project Structure
-
-```
-steps/              # Your Step definitions (or use src/)
-motia.config.ts     # Motia configuration
-requirements.txt    # Python dependencies
-```
+## Project Config
 
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required. You can write Steps in Python, TypeScript, or JavaScript, all in the same project.
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 
 ## Learn More
 
-- [Documentation](https://motia.dev/docs) - Complete guides and API reference
-- [Quick Start Guide](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
-- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia architecture
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
+- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/nodejs/.env

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+API_URL="https://xnigaj-xtnawg.motiahub.com"
+SAMPLE_EMAIL="test@test.com"

package/dist/create/templates/nodejs/README.md.txt

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
 
-A Motia tutorial project in TypeScript.
+This is a **Motia** project bootstrapped with the Motia CLI.
 
-## What is Motia?
-
-Motia is an open-source, unified backend framework that eliminates runtime fragmentation by bringing **APIs, background jobs, queueing, streaming, state, workflows, AI agents, observability, scaling, and deployment** into one unified system using a single core primitive, the **Step**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 
 ## Quick Start
 
@@ -17,76 +15,19 @@ yarn dev
 pnpm dev
 ```
 
-This starts the Motia runtime and the **Workbench** - a powerful UI for developing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-
-1. **Open the Workbench** in your browser at [`http://localhost:3000`](http://localhost:3000)
-2. **Click the `Tutorial`** button on the top right of the workbench
-3. **Complete the `Tutorial`** to get an understanding of the basics of Motia and using the Workbench
-
-## Step Types
-
-Every Step has a `type` that defines how it triggers:
-
-| Type | When it runs | Use case |
-|------|--------------|----------|
-| **`api`** | HTTP request | REST APIs, webhooks |
-| **`event`** | Event emitted | Background jobs, workflows |
-| **`cron`** | Schedule | Cleanup, reports, reminders |
-
-## Development Commands
-
-```bash
-# Start Workbench and development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-
-# Start production server (without hot reload)
-npm run start
-# or
-yarn start
-# or
-pnpm start
-
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
-
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
-
-## Project Structure
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
 
-```
-steps/              # Your Step definitions (or use src/)
-src/                # Shared services and utilities
-motia.config.ts     # Motia configuration
-```
+You can start editing the project by making changes to `src/petstore/api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
 
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required.
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
 
-## Tutorial
+## Project Config
 
-This project includes an interactive tutorial that will guide you through:
-- Understanding Steps and their types
-- Creating API endpoints
-- Building event-driven workflows
-- Using state management
-- Observing your flows in the Workbench
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 
 ## Learn More
 
-- [Documentation](https://motia.dev/docs) - Complete guides and API reference
-- [Quick Start Guide](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
-- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia architecture
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
+- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/nodejs/src/petstore/api.step.ts.txt

@@ -38,7 +38,7 @@ export const handler: Handlers['ApiTrigger'] = async (req, { logger, traceId, em
       topic: 'process-food-order',
       data: {
         quantity: foodOrder.quantity,
-        email: 'test@test.com', // sample email
+        email: process.env.SAMPLE_EMAIL || 'test@test.com',
         petId: newPetRecord.id,
       },
     })

package/dist/create/templates/nodejs/src/petstore/state-audit-cron.step.ts.txt

@@ -28,7 +28,7 @@ export const handler: Handlers['StateAuditJob'] = async ({ logger, state, emit }
       await emit({
         topic: 'notification',
         data: {
-          email: 'test@test.com',
+          email: process.env.SAMPLE_EMAIL || 'test@test.com',
           templateId: 'order-audit-warning',
           templateData: {
             orderId: item.id,

package/dist/create/templates/nodejs/src/services/pet-store.ts.txt

@@ -1,8 +1,10 @@
 import type { Order, Pet } from './types'
 
+const API_URL = process.env.API_URL || 'https://xnigaj-xtnawg.motiahub.com'
+
 export const petStoreService = {
   createPet: async (pet: Omit<Pet, 'id'>): Promise<Pet> => {
-    const response = await fetch('https://xnigaj-xtnawg.motiahub.com/pet', {
+    const response = await fetch(`${API_URL}/pet`, {
       method: 'POST',
       body: JSON.stringify({
         name: pet?.name ?? '',
@@ -14,7 +16,7 @@ export const petStoreService = {
     return response.json()
   },
   createOrder: async (order: Omit<Order, 'id' | 'complete'>): Promise<Order> => {
-    const response = await fetch('https://xnigaj-xtnawg.motiahub.com/store/order', {
+    const response = await fetch(`${API_URL}/store/order`, {
       method: 'POST',
       body: JSON.stringify({
         quantity: order?.quantity ?? 1,

package/dist/create/templates/python/.env

@@ -0,0 +1,3 @@
+# Motia automatically loads environment variables from .env files
+API_URL="https://xnigaj-xtnawg.motiahub.com"
+SAMPLE_EMAIL="test@test.com"

package/dist/create/templates/python/README.md.txt

@@ -1,10 +1,8 @@
 # {{PROJECT_NAME}}
 
-A Motia tutorial project in Python.
+This is a **Motia** project bootstrapped with the Motia CLI.
 
-## What is Motia?
-
-Motia is an open-source, unified backend framework that eliminates runtime fragmentation by bringing **APIs, background jobs, queueing, streaming, state, workflows, AI agents, observability, scaling, and deployment** into one unified system using a single core primitive, the **Step**.
+Motia lets you build APIs, background jobs, workflows, and event-driven systems in a single unified backend.
 
 ## Quick Start
 
@@ -17,77 +15,19 @@ yarn dev
 pnpm dev
 ```
 
-This starts the Motia runtime and the **Workbench** - a powerful UI for developing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
-
-1. **Open the Workbench** in your browser at [`http://localhost:3000`](http://localhost:3000)
-2. **Click the `Tutorial`** button on the top right of the workbench
-3. **Complete the `Tutorial`** to get an understanding of the basics of Motia and using the Workbench
-
-## Step Types
-
-Every Step has a `type` that defines how it triggers:
-
-| Type | When it runs | Use case |
-|------|--------------|----------|
-| **`api`** | HTTP request | REST APIs, webhooks |
-| **`event`** | Event emitted | Background jobs, workflows |
-| **`cron`** | Schedule | Cleanup, reports, reminders |
-
-## Development Commands
-
-```bash
-# Start Workbench and development server
-npm run dev
-# or
-yarn dev
-# or
-pnpm dev
-
-# Start production server (without hot reload)
-npm run start
-# or
-yarn start
-# or
-pnpm start
-
-# Generate TypeScript types from Step configs
-npm run generate-types
-# or
-yarn generate-types
-# or
-pnpm generate-types
-
-# Build project for deployment
-npm run build
-# or
-yarn build
-# or
-pnpm build
-```
-
-## Project Structure
+This starts the Motia runtime and **Workbench**. Workbench is a tool for visualizing and debugging your workflows. By default, it's available at [`http://localhost:3000`](http://localhost:3000).
 
-```
-steps/              # Your Step definitions (or use src/)
-src/                 # Shared services and utilities
-motia.config.ts      # Motia configuration
-requirements.txt     # Python dependencies
-```
+You can start editing the project by making changes to `src/petstore/api` as well as produce your own `.step.ts`, `.step.js`, or `_step.py` files within the `src/` directory.
 
-Steps are auto-discovered from your `steps/` or `src/` directories - no manual registration required. You can write Steps in Python, TypeScript, or JavaScript, all in the same project.
+Motia auto-discovers all step files and executes them as defined in each step's configuration. Learn more about the power and simplicity of steps in the [Step Docs](https://motia.dev/docs/concepts/steps).
 
-## Tutorial
+## Project Config
 
-This project includes an interactive tutorial that will guide you through:
-- Understanding Steps and their types
-- Creating API endpoints
-- Building event-driven workflows
-- Using state management
-- Observing your flows in the Workbench
+The `motia.config.ts` file is the central configuration for your Motia application. Here you can customize Express, configure Redis, add security middleware, handle file uploads, set up stream authentication, and more.
 
 ## Learn More
 
-- [Documentation](https://motia.dev/docs) - Complete guides and API reference
-- [Quick Start Guide](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
-- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia architecture
+- [Docs](https://motia.dev/docs) - Complete guides and API reference
+- [Quick Start Tutorial](https://motia.dev/docs/getting-started/quick-start) - Detailed getting started tutorial
+- [Core Concepts](https://motia.dev/docs/concepts/overview) - Learn about Steps and Motia's architecture
 - [Discord Community](https://discord.gg/motia) - Get help and connect with other developers

package/dist/create/templates/python/src/petstore/api_step.py.txt

@@ -1,3 +1,4 @@
+import os
 from pydantic import BaseModel
 from typing import Optional
 from src.services.pet_store import pet_store_service
@@ -42,7 +43,7 @@ async def handler(req, context):
             "topic": "process-food-order",
             "data": {
                 "quantity": food_order.get("quantity"),
-                "email": "test@test.com",  # sample email
+                "email": os.environ.get("SAMPLE_EMAIL", "test@test.com"),
                 "pet_id": new_pet_record.get("id"),
             },
         })

package/dist/create/templates/python/src/petstore/state_audit_cron_step.py.txt

@@ -1,3 +1,4 @@
+import os
 from datetime import datetime, timezone
 
 config = {
@@ -27,7 +28,7 @@ async def handler(context):
             await context.emit({
                 "topic": "notification",
                 "data": {
-                    "email": "test@test.com",
+                    "email": os.environ.get("SAMPLE_EMAIL", "test@test.com"),
                     "template_id": "order-audit-warning",
                     "template_data": {
                         "order_id": item.get("id"),

package/dist/create/templates/python/src/services/pet_store.py.txt

@@ -1,7 +1,10 @@
+import os
 import httpx
 from typing import Dict, Any
 from .types import Order, Pet
 
+api_url = os.environ.get("API_URL", "https://xnigaj-xtnawg.motiahub.com")
+
 class PetStoreService:
     async def create_pet(self, pet: Dict[str, Any]) -> Pet:
         pet_data = {
@@ -12,7 +15,7 @@ class PetStoreService:
         
         async with httpx.AsyncClient() as client:
             response = await client.post(
-                'https://xnigaj-xtnawg.motiahub.com/pet',
+                f"{api_url}/pet",
                 json=pet_data,
                 headers={'Content-Type': 'application/json'}
             )
@@ -28,7 +31,7 @@ class PetStoreService:
             }
             
             response = await client.post(
-                'https://xnigaj-xtnawg.motiahub.com/store/order',
+                f"{api_url}/store/order",
                 json=order_data,
                 headers={'Content-Type': 'application/json'}
             )

package/dist/create/templates/python/tutorial/petstore/api_step.py-features.json.txt

@@ -3,48 +3,48 @@
     "id": "step-configuration",
     "title": "Step Configuration",
     "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
-    "lines": ["6-29"]
+    "lines": ["7-30"]
   },
   {
     "id": "api-configuration",
     "title": "API Step",
     "description": "Definition of an API endpoint",
-    "lines": ["18", "22-23"]
+    "lines": ["19", "23-24"]
   },
   {
     "id": "request-body",
     "title": "Request body",
     "description": "Definition of the expected request body. Motia will automatically generate types based on this schema.",
-    "lines": ["6-15", "24"]
+    "lines": ["7-16", "25"]
   },
   {
     "id": "response-payload",
     "title": "Response Payload",
     "description": "Definition of the expected response payload, Motia will generate the types automatically based on this schema. This is also important to create the Open API spec later.",
-    "lines": ["4", "25-27"]
+    "lines": ["5", "26-28"]
   },
   {
     "id": "event-driven-architecture",
     "title": "Emits",
     "description": "We can define the events that this step will emit, this is how we can trigger other Motia Steps.",
-    "lines": ["28", "41-48"]
+    "lines": ["29", "42-49"]
   },
   {
     "id": "handler",
     "title": "Handler",
     "description": "The handler is the function that will be executed when the step is triggered. This one receives the request body and emits events.",
-    "lines": ["31-50"]
+    "lines": ["32-51"]
   },
   {
     "id": "logger",
     "title": "Logger",
     "description": "The logger is a utility that allows you to log messages to the console. It is available in the handler function. We encourage you to use it instead of console.log. It will automatically be tied to the trace id of the request.",
-    "lines": ["33"]
+    "lines": ["34"]
   },
   {
     "id": "http-response",
     "title": "HTTP Response",
     "description": "The handler can return a response to the client. This is how we can return a response to the client. It must comply with the responseSchema defined in the step configuration.",
-    "lines": ["50"]
+    "lines": ["51"]
   }
 ]

package/dist/create/templates/python/tutorial/petstore/state_audit_cron_step.py-features.json.txt

@@ -3,24 +3,18 @@
     "id": "step-configuration",
     "title": "Step Configuration",
     "description": "All steps should have a defined configuration, this is how you define the step's behavior and how it will be triggered.",
-    "lines": [
-      "3-10"
-    ]
+    "lines": ["4-11"]
   },
   {
     "id": "cron-configuration",
     "title": "Cron Configuration",
     "description": "Cron steps require a specific configuration structure with the 'type' field set to 'cron' and a valid cron expression.",
-    "lines": [
-      "4-5"
-    ]
+    "lines": ["5-6"]
   },
   {
     "id": "handler",
     "title": "Cron Step Handler",
     "description": "The Cron step handler only receives one argument.",
-    "lines": [
-      "12-39"
-    ]
+    "lines": ["13-40"]
   }
-]
+]

package/dist/cursor-rules/dot-files/.claude/agents/motia-developer.md

@@ -86,7 +86,7 @@ Before writing ANY Motia code, you MUST read the relevant cursor rules from `.cu
 ## Key Principles
 
 - **All guides have TypeScript, JavaScript, and Python examples**
-- **Steps can live in `/src` or `/steps`** - Motia discovers both (use `/src` for modern structure)
+- **Steps can live anywhere within `/src`** - Motia discovers them automatically
 - **Always export `config` and `handler`**
 - **List all emits in config before using them**
 - **Follow naming conventions**: `*.step.ts` (TS), `*.step.js` (JS), `*_step.py` (Python)

package/dist/cursor-rules/dot-files/.cursor/architecture/architecture.mdc

@@ -10,17 +10,13 @@ alwaysApply: true
 
 This guide covers the architecture and best practices for structuring Motia projects.
 
-**Key Takeaway**: Motia automatically discovers steps from anywhere in your project. Modern projects use `/src` for a familiar structure that works seamlessly with Domain-Driven Design.
+**Key Takeaway**: Motia automatically discovers steps from anywhere in the `/src` folder. Modern projects use `/src` for a familiar structure that works seamlessly with Domain-Driven Design.
 
 ## File Structure
 
-Motia automatically discovers step files from your project. You can organize steps in either:
+Motia automatically discovers step files from your project.
 
-- **`/src` folder** (recommended) - Familiar pattern for most developers
-- **`/steps` folder** - Traditional Motia pattern
-- Both folders simultaneously
-
-### Recommended Structure (using `/src`)
+### Recommended Structure
 
 ```
 project/
@@ -39,24 +35,7 @@ project/
 └── motia.config.ts
 ```
 
-### Alternative Structure (using `/steps`)
-
-```
-project/
-├── steps/
-│   ├── api/
-│   │   └── users.step.ts
-│   ├── events/
-│   │   └── order-processing.step.ts
-│   └── cron/
-│       └── cleanup.step.ts
-├── src/
-│   ├── services/
-│   └── utils/
-└── motia.config.ts
-```
-
-Create subfolders within your chosen directory to organize related steps into logical groups (domains, features, or flows).
+Create subfolders within your `/src` directory to organize related steps into logical groups (domains, features, or flows).
 
 **Why `/src` is recommended:**
 - Familiar to developers from other frameworks (Next.js, NestJS, etc.)
@@ -109,7 +88,7 @@ Motia encourages Domain-Driven Design (DDD) principles for maintainable, scalabl
 
 ### Folder Structure for DDD
 
-When using `/src` for steps (recommended), your structure naturally supports DDD:
+When using `/src` for steps, your structure naturally supports DDD:
 
 ```
 src/

package/dist/cursor-rules/dot-files/.cursor/rules/motia/api-steps.mdc

@@ -1,6 +1,6 @@
 ---
 description: How to create HTTP endpoints in Motia
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 # API Steps Guide
@@ -9,7 +9,7 @@ API Steps expose HTTP endpoints that can trigger workflows and emit events.
 
 ## Creating API Steps
 
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively.
 - Steps in Python should end with `_step.py`.

package/dist/cursor-rules/dot-files/.cursor/rules/motia/cron-steps.mdc

@@ -1,6 +1,6 @@
 ---
 description: Cron Steps are scheduled tasks that run based on cron expressions.
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 # Cron Steps Guide
@@ -15,7 +15,7 @@ ultimately trigger an Event Step that will handle the logic.
 
 ## Creating Cron Steps
 
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively
 - Steps in Python should end with `_step.py`

package/dist/cursor-rules/dot-files/.cursor/rules/motia/event-steps.mdc

@@ -1,6 +1,6 @@
 ---
 description: How to create background tasks in Motia
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 # Event Steps Guide
@@ -19,7 +19,7 @@ Other applicable examples are tasks that are likely to fail, examples:
 
 ## Creating Event Steps
 
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively.
 - Steps in Python should end with `_step.py`.

package/dist/cursor-rules/dot-files/.cursor/rules/motia/middlewares.mdc

@@ -1,6 +1,6 @@
 ---
 description: Middlewares are used to execute code before and after the handler is called
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py,middlewares/**/*.middleware.ts,middlewares/**/*.middleware.js,middlewares/**/*_middleware.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py,middlewares/**/*.middleware.ts,middlewares/**/*.middleware.js,middlewares/**/*_middleware.py
 alwaysApply: false
 ---
 # Middlewares Guide

package/dist/cursor-rules/dot-files/.cursor/rules/motia/motia-config.mdc

@@ -196,7 +196,7 @@ export default config({
 **Project structure:**
 ```
 project/
-├── src/              # Steps can be in /src or /steps
+├── src/              # Steps can be placed anywhere within /src
 │   └── api/
 │       └── example.step.ts
 ├── plugins/

package/dist/cursor-rules/dot-files/.cursor/rules/motia/realtime-streaming.mdc

@@ -1,6 +1,6 @@
 ---
 description: Real-time streaming
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py,steps/**/*.stream.ts,steps/**/*.stream.js,steps/**/*_stream.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py,src/**/*.stream.ts,src/**/*.stream.js,src/**/*_stream.py
 alwaysApply: false
 ---
 # Real-time Streaming
@@ -56,7 +56,7 @@ export interface StreamConfig {
 ### TypeScript Example
 
 ```typescript
-// steps/streams/chat-messages.stream.ts
+// src/streams/chat-messages.stream.ts
 import { StreamConfig } from 'motia'
 import { z } from 'zod'
 
@@ -81,7 +81,7 @@ export const config: StreamConfig = {
 #### With Pydantic (Optional)
 
 ```python
-# steps/streams/chat_messages_stream.py
+# src/streams/chat_messages_stream.py
 from pydantic import BaseModel
 
 class ChatMessage(BaseModel):
@@ -100,7 +100,7 @@ config = {
 #### Without Pydantic (Pure JSON Schema)
 
 ```python
-# steps/streams/chat_messages_stream.py
+# src/streams/chat_messages_stream.py
 
 config = {
     "name": "chatMessage",

package/dist/cursor-rules/dot-files/.cursor/rules/motia/state-management.mdc

@@ -1,6 +1,6 @@
 ---
 description: Managing state across Steps
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 

package/dist/cursor-rules/dot-files/.cursor/rules/motia/ui-steps.mdc

@@ -1,6 +1,6 @@
 ---
 description: Overriding the UI of Steps in Motia
-globs: steps/**/*.step.tsx,steps/**/*.step.jsx,steps/**/*_step.tsx,steps/**/*_step.jsx
+globs: src/**/*.step.tsx,src/**/*.step.jsx,src/**/*_step.tsx,src/**/*_step.jsx
 alwaysApply: true
 ---
 
@@ -15,7 +15,7 @@ With UI Steps, you can enhance the user experience by designing intuitive, conte
 To create a custom UI for a step, create a .tsx or .jsx file next to your step file with the same base name:
 
 ```
-steps/ 
+src/ 
 └── myStep/ 
   ├── myStep.step.ts      # Step definition
   └── myStep.step.tsx     # Visual override

package/dist/cursor-rules/dot-files/.cursor/rules/motia/virtual-steps.mdc

@@ -1,6 +1,6 @@
 ---
 description: Connecting nodes virtually and creating a smooth flow in Workbench
-globs: steps/**/*.step.ts,steps/**/*.step.js,steps/**/*_step.py
+globs: src/**/*.step.ts,src/**/*.step.js,src/**/*_step.py
 alwaysApply: false
 ---
 
@@ -15,7 +15,7 @@ or without NOOP Steps.
 
 ## Creating NOOP Steps
 
-Steps need to be created in the `steps` folder, it can be in subfolders.
+Steps need to be created in the `src` folder, it can be in subfolders.
 
 - Steps in TS and JS should end with `.step.ts` and `.step.js` respectively.
 - Steps in Python should end with `_step.py`.

package/dist/cursor-rules/dot-files/AGENTS.md

@@ -63,9 +63,9 @@ Architecture guides in `.cursor/architecture/`:
 
 ### Project Structure
 
-Motia discovers steps from both `/src` and `/steps` folders. Modern projects typically use `/src`:
+Motia discovers steps from the `/src` folder:
 
-**Recommended Structure (using `/src`):**
+**Recommended Structure:**
 ```
 project/
 ├── .cursor/rules/   # DETAILED GUIDES - Read these first!
@@ -88,19 +88,6 @@ project/
 └── types.d.ts      # Auto-generated types
 ```
 
-**Alternative Structure (using `/steps`):**
-```
-project/
-├── steps/          # Step definitions
-│   ├── api/
-│   ├── events/
-│   └── cron/
-├── src/
-│   ├── services/
-│   └── utils/
-└── motia.config.ts
-```
-
 ### Step Naming Conventions
 
 **TypeScript/JavaScript:** `my-step.step.ts` (kebab-case)  

package/dist/cursor-rules/dot-files/CLAUDE.md

@@ -48,7 +48,7 @@ All guides in `.cursor/rules/` with **TypeScript, JavaScript, and Python** examp
 
 See `AGENTS.md` in this directory for a quick overview and links to specific guides.
 
-**Important**: Motia discovers steps from both `/src` and `/steps` folders. Modern projects use `/src` for a familiar structure.
+**Important**: Motia discovers steps from the `/src` folder.
 
 ## Key Commands
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "motia",
   "description": "Build production-grade backends with a single primitive. APIs, background jobs, Queues, Workflows, and AI agents - unified in one system with built-in State management, Streaming, and Observability.",
-  "version": "0.17.11-beta.194-563479",
+  "version": "0.17.12-beta.194",
   "license": "Elastic-2.0",
   "type": "module",
   "repository": {
@@ -46,13 +46,13 @@
     "table": "^6.9.0",
     "ts-node": "^10.9.2",
     "zod": "^4.1.13",
-    "@motiadev/adapter-redis-cron": "0.17.11-beta.194-563479",
-    "@motiadev/adapter-redis-state": "0.17.11-beta.194-563479",
-    "@motiadev/adapter-bullmq-events": "0.17.11-beta.194-563479",
-    "@motiadev/stream-client-node": "0.17.11-beta.194-563479",
-    "@motiadev/core": "0.17.11-beta.194-563479",
-    "@motiadev/adapter-redis-streams": "0.17.11-beta.194-563479",
-    "@motiadev/workbench": "0.17.11-beta.194-563479"
+    "@motiadev/adapter-redis-cron": "0.17.12-beta.194",
+    "@motiadev/adapter-bullmq-events": "0.17.12-beta.194",
+    "@motiadev/adapter-redis-streams": "0.17.12-beta.194",
+    "@motiadev/adapter-redis-state": "0.17.12-beta.194",
+    "@motiadev/stream-client-node": "0.17.12-beta.194",
+    "@motiadev/workbench": "0.17.12-beta.194",
+    "@motiadev/core": "0.17.12-beta.194"
   },
   "devDependencies": {
     "@amplitude/analytics-types": "^2.9.2",