motia 0.5.11-beta.120-356715 → 0.5.11-beta.120-382150

package/README.md

@@ -98,24 +98,24 @@ Backend teams juggle **fragmented runtimes** across APIs, background queues, and
 
 Motia unifies your entire backend into a **unified state**. APIs, background jobs, and AI agents become interconnected Steps with shared state and integrated observability.
 
-| **Before** | **After (Motia)** |
-|---|---|
-| Multiple deployment targets | **Single unified deployment** |
-| Fragmented observability | **End-to-end tracing** |
-| Language dependent | **JavaScript, TypeScript, Python, etc** |
-| Context-switching overhead | **Single intuitive model** |
-| Complex error handling | **Automatic retries & fault tolerance** |
+| **Before**                  | **After (Motia)**                       |
+| --------------------------- | --------------------------------------- |
+| Multiple deployment targets | **Single unified deployment**           |
+| Fragmented observability    | **End-to-end tracing**                  |
+| Language dependent          | **JavaScript, TypeScript, Python, etc** |
+| Context-switching overhead  | **Single intuitive model**              |
+| Complex error handling      | **Automatic retries & fault tolerance** |
 
 ---
 
 ## 🔧 Supported Step Types
 
-| Type | Trigger | Use Case |
-|---|---|---|
-| **`api`** | HTTP Request | Expose REST endpoints |
-| **`event`** | Emitted Topics | React to internal or external events  |
-| **`cron`** | Scheduled Time (cron) | Automate recurring jobs |
-| **`noop`** | None | Placeholder for manual/external tasks |
+| Type        | Trigger               | Use Case                              |
+| ----------- | --------------------- | ------------------------------------- |
+| **`api`**   | HTTP Request          | Expose REST endpoints                 |
+| **`event`** | Emitted Topics        | React to internal or external events  |
+| **`cron`**  | Scheduled Time (cron) | Automate recurring jobs               |
+| **`noop`**  | None                  | Placeholder for manual/external tasks |
 
 ---
 
@@ -123,9 +123,9 @@ Motia unifies your entire backend into a **unified state**. APIs, background job
 
 Motia's architecture is built around a single, powerful primitive: the **Step**. A Step is not just a trigger; it's a powerful container for your business logic. You can write anything from a simple database query to a complex AI agent interaction inside a single step. Instead of managing separate services for APIs, background workers, and scheduled tasks, you simply define how your steps are triggered.
 
--   **Need a public API?** Create an `api` step. This defines a route and handler for HTTP requests. You can build a complete REST or GraphQL API just with these steps.
--   **Need a background job or queue?** Have your `api` step `emit` an event. An `event` step subscribed to that event's topic will pick up the job and process it asynchronously. This is how you handle anything that shouldn't block the main request thread, from sending emails to complex data processing.
--   **Need to run a task on a schedule?** Use a `cron` step. It will trigger automatically based on the schedule you define.
+- **Need a public API?** Create an `api` step. This defines a route and handler for HTTP requests. You can build a complete REST or GraphQL API just with these steps.
+- **Need a background job or queue?** Have your `api` step `emit` an event. An `event` step subscribed to that event's topic will pick up the job and process it asynchronously. This is how you handle anything that shouldn't block the main request thread, from sending emails to complex data processing.
+- **Need to run a task on a schedule?** Use a `cron` step. It will trigger automatically based on the schedule you define.
 
 This model means you no longer need to glue together separate frameworks and tools. A single Motia application can replace a stack that might otherwise include **Nest.js** (for APIs), **Temporal** (for workflows), and **Celery/BullMQ** (for background jobs). It's all just steps and events.
 
@@ -173,9 +173,9 @@ Motia unifies your entire backend into a **unified state**. APIs, background job
 
 Motia's architecture is built around a single, powerful primitive: the **Step**. A Step is not just a trigger; it's a powerful container for your business logic. You can write anything from a simple database query to a complex AI agent interaction inside a single step. Instead of managing separate services for APIs, background workers, and scheduled tasks, you simply define how your steps are triggered.
 
--   **Need a public API?** Create an `api` step. This defines a route and handler for HTTP requests. You can build a complete REST or GraphQL API just with these steps.
--   **Need a background job or queue?** Have your `api` step `emit` an event. An `event` step subscribed to that event's topic will pick up the job and process it asynchronously. This is how you handle anything that shouldn't block the main request thread, from sending emails to complex data processing.
--   **Need to run a task on a schedule?** Use a `cron` step. It will trigger automatically based on the schedule you define.
+- **Need a public API?** Create an `api` step. This defines a route and handler for HTTP requests. You can build a complete REST or GraphQL API just with these steps.
+- **Need a background job or queue?** Have your `api` step `emit` an event. An `event` step subscribed to that event's topic will pick up the job and process it asynchronously. This is how you handle anything that shouldn't block the main request thread, from sending emails to complex data processing.
+- **Need to run a task on a schedule?** Use a `cron` step. It will trigger automatically based on the schedule you define.
 
 This model means you no longer need to glue together separate frameworks and tools. A single Motia application can replace a stack that might otherwise include **Nest.js** (for APIs), **Temporal** (for workflows), and **Celery/BullMQ** (for background jobs). It's all just steps and events.
 
@@ -184,24 +184,31 @@ This model means you no longer need to glue together separate frameworks and too
 The **Step** is Motia's core primitive. The following concepts are deeply integrated with Steps to help you build powerful, complex, and scalable backends:
 
 ### 🔑 Steps & Step Types
+
 Understand the three ways Steps are triggered:
+
 - **HTTP (`api`)** – Build REST/GraphQL endpoints with zero boilerplate.
 - **Events (`event`)** – React to internal or external events emitted by other steps.
 - **Cron (`cron`)** – Schedule recurring jobs with a familiar cron syntax.
 
 ### 📣 Emit & Subscribe (Event-Driven Workflows)
+
 Steps talk to each other by **emitting** and **subscribing** to topics. This decouples producers from consumers and lets you compose complex workflows with simple, declarative code.
 
 ### 🏪 State Management
+
 All steps share a unified key-value state store. Every `get`, `set`, and `delete` is automatically traced so you always know when and where your data changed.
 
 ### 📊 Structured Logging
+
 Motia provides structured, JSON logs correlated with trace IDs and step names. Search and filter your logs without regex gymnastics.
 
 ### 📡 Streams: Real-time Messaging
+
 Push live updates from long-running or asynchronous workflows to clients without polling. Perfect for dashboards, progress indicators, and interactive AI agents.
 
 ### 👁️ End-to-End Observability with Traces
+
 Every execution generates a full trace, capturing step timelines, state operations, emits, stream calls, and logs. Visualise everything in the Workbench's Traces UI and debug faster.
 
 ---
@@ -211,7 +218,9 @@ Every execution generates a full trace, capturing step timelines, state operatio
 Motia comes with a range of [powerful CLI commands](https://www.motia.dev/docs/concepts/cli) to help you manage your projects:
 
 ### `npx motia create [options]`
+
 Create a new Motia project in a fresh directory or the current one.
+
 ```sh
 npx motia create [options]
 
@@ -238,12 +247,12 @@ bun run dev  [options]
 # options:
   # -p, --port <port>     The port to run the server on (default: 3000)
   # -H, --host [host]     The host address for the server (default: localhost)
-  # -v, --verbose         Enable verbose logging
   # -d, --debug          Enable debug logging
   # -m, --mermaid        Enable mermaid diagram generation
 ```
 
 ### `npx motia build`
+
 Compiles all your steps (Node.js, Python and more) and builds a lock file based on your current project setup, which is then used by the Motia ecosystem.
 
 ```bash
@@ -256,12 +265,12 @@ motia build
 
 Write steps in your preferred language:
 
-| Language       | Status        | Example           |
-| -------------- | ------------- | ----------------- |
+| Language       | Status         | Example           |
+| -------------- | -------------- | ----------------- |
 | **JavaScript** | ✅ Stable      | `handler.step.js` |
 | **TypeScript** | ✅ Stable      | `handler.step.ts` |
 | **Python**     | ✅ Stable      | `handler.step.py` |
-| **Ruby**       | 🚧 Beta | `handler.step.rb` |
+| **Ruby**       | 🚧 Beta        | `handler.step.rb` |
 | **Go**         | 🔄 Coming Soon | `handler.step.go` |
 | **Rust**       | 🔄 Coming Soon | `handler.step.rs` |
 
@@ -276,6 +285,7 @@ motia <command> --help
 ```
 
 ### 💬 **Get Help**
+
 - **📋 Questions**: Use our [Discord community](https://discord.gg/motia)
 - **🐛 Bug Reports**: [GitHub Issues](https://github.com/MotiaDev/motia/issues)
 - **📖 Documentation**: [Official Docs](https://motia.dev/docs)
@@ -284,6 +294,7 @@ motia <command> --help
 ### 🤝 **Contributing**
 
 We welcome contributions! Whether it's:
+
 - 🐛 Bug fixes and improvements
 - ✨ New features and step types
 - 📚 Documentation and examples

package/dist/cjs/cli.js

@@ -28,27 +28,36 @@ commander_1.program
     .command('create')
     .description('Create a new motia project')
     .option('-n, --name <project name>', 'The name for your project, used to create a directory, use ./ or . to create it under the existing directory')
-    .option('-t, --template <template name>', 'The motia template name to use for your project')
+    .option('-t, --template <template name>', 'The motia template name to use for your project', 'typescript')
     .option('-c, --cursor', 'Copy .cursor folder from template')
     .option('-i, --interactive', 'Use interactive prompts to create project')
     .option('-y, --skip-confirmation', 'Skip confirmation prompt')
-    .option('-d, --skip-tutorial', 'Skip the motia tutorial', false)
+    .option('-d, --skip-tutorial [value]', 'Skip the motia tutorial (true/false)')
     .action((0, config_utils_1.handler)(async (arg, context) => {
     if (arg.name || arg.template || arg.cursor) {
         const { create } = require('./create');
-        const disableTutorial = await inquirer_1.default.prompt({
-            type: 'confirm',
-            name: 'disableTutorial',
-            message: 'Do you wish to disable the motia tutorial?',
-            default: arg.skipTutorial,
-            when: () => arg.skipTutorial === false,
-        });
+        // Handle skip-tutorial option: 'true', 'false', or prompt user
+        const skipTutorialValue = await (async () => {
+            const skipValue = String(arg.skipTutorial).toLowerCase();
+            if (skipValue === 'true')
+                return true;
+            if (skipValue === 'false')
+                return false;
+            // Prompt user when not explicitly set
+            const { disableTutorial } = await inquirer_1.default.prompt({
+                type: 'confirm',
+                name: 'disableTutorial',
+                message: 'Do you wish to disable the motia tutorial?',
+                default: false,
+            });
+            return disableTutorial;
+        })();
         await create({
             projectName: arg.name ?? '.',
-            template: arg.template ?? 'default',
+            template: arg.template,
             cursorEnabled: arg.cursor,
             context,
-            skipTutorialTemplates: disableTutorial.disableTutorial,
+            skipTutorialTemplates: skipTutorialValue,
         });
     }
     else {
@@ -185,5 +194,44 @@ docker
     await build(arg.projectName);
     process.exit(0);
 });
+const rules = commander_1.program
+    .command('rules')
+    .description('Manage Motia AI development guides (AGENTS.md, CLAUDE.md) and IDE-specific rules');
+rules
+    .command('pull')
+    .description('Install essential AI development guides (AGENTS.md, CLAUDE.md) and optional Cursor IDE rules')
+    .option('-f, --force', 'Overwrite existing files')
+    .action(async (options) => {
+    const { handleAIGuides } = require('./cursor-rules');
+    await handleAIGuides({ force: options.force });
+});
+rules
+    .command('list')
+    .description('List available AI development guides and IDE rules')
+    .action(async () => {
+    const { handleAIGuides } = require('./cursor-rules');
+    await handleAIGuides({ list: true });
+});
+rules
+    .command('show <rule-name>')
+    .description('Show content of a specific AI guide or IDE rule')
+    .action(async (ruleName) => {
+    const { handleAIGuides } = require('./cursor-rules');
+    await handleAIGuides({ show: ruleName });
+});
+rules
+    .command('remove')
+    .description('Remove AI development guides and IDE rules from your project')
+    .action(async () => {
+    const { handleAIGuides } = require('./cursor-rules');
+    await handleAIGuides({ remove: true });
+});
+rules
+    .command('version')
+    .description('Show AI development guides version')
+    .action(async () => {
+    const { handleAIGuides } = require('./cursor-rules');
+    await handleAIGuides({ version: true });
+});
 commander_1.program.version(version_1.version, '-V, --version', 'Output the current version');
 commander_1.program.parse(process.argv);

package/dist/cjs/cloud/endpoints.d.ts

@@ -0,0 +1,2 @@
+import { LockedData, MotiaServer } from '@motiadev/core';
+export declare const deployEndpoints: (server: MotiaServer, lockedData: LockedData) => void;

package/dist/cjs/cloud/endpoints.js

@@ -0,0 +1,107 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.deployEndpoints = void 0;
+const crypto_1 = require("crypto");
+const build_validation_1 = require("./build/build-validation");
+const streaming_deployment_listener_1 = require("./new-deployment/listeners/streaming-deployment-listener");
+const build_1 = require("./new-deployment/build");
+const upload_artifacts_1 = require("./new-deployment/upload-artifacts");
+const deployment_stream_1 = require("./new-deployment/streams/deployment-stream");
+const cloud_api_1 = require("./new-deployment/cloud-api");
+const deployEndpoints = (server, lockedData) => {
+    const { app } = server;
+    // Criar stream de deployment se não existir
+    const deploymentStream = lockedData.createStream({
+        filePath: '__motia.deployment',
+        hidden: true,
+        config: {
+            name: '__motia.deployment',
+            baseConfig: { storageType: 'default' },
+            schema: null,
+        },
+    })();
+    const deploymentManager = new deployment_stream_1.DeploymentStreamManager(deploymentStream);
+    app.post('/cloud/deploy/start', async (req, res) => {
+        try {
+            const { deploymentToken, deploymentId, envs } = req.body;
+            if (!deploymentToken || !deploymentId) {
+                return res.status(400).json({
+                    success: false,
+                    error: 'deploymentToken and deploymentId are required',
+                });
+            }
+            const sessionId = deploymentId || (0, crypto_1.randomUUID)();
+            await deploymentManager.startDeployment(sessionId);
+            const listener = new streaming_deployment_listener_1.StreamingDeploymentListener(sessionId, deploymentStream);
+            res.json({
+                success: true,
+                message: 'Deployment started',
+                deploymentId: sessionId,
+                streamName: 'deployment-status',
+                groupId: 'deployments',
+                itemId: sessionId,
+            });
+            setImmediate(async () => {
+                try {
+                    await listener.startBuildPhase();
+                    const builder = await (0, build_1.build)(listener);
+                    const isValid = (0, build_validation_1.buildValidation)(builder, listener);
+                    if (!isValid) {
+                        await listener.onBuildErrors(listener.getErrors());
+                        return;
+                    }
+                    await listener.completeBuildPhase();
+                    await listener.startUploadPhase();
+                    await (0, upload_artifacts_1.uploadArtifacts)(builder, deploymentToken, listener);
+                    await listener.completeUploadPhase();
+                    await listener.startDeployPhase();
+                    await cloud_api_1.cloudApi.startDeployment({
+                        deploymentToken,
+                        envVars: envs,
+                        steps: builder.stepsConfig,
+                        streams: builder.streamsConfig,
+                        routers: builder.routersConfig,
+                    });
+                }
+                catch (error) {
+                    console.error('Deployment failed:', error);
+                    // Update stream with error
+                    if (listener) {
+                        await listener.onDeployError(error.message);
+                    }
+                }
+            });
+        }
+        catch (error) {
+            console.error('Failed to start deployment:', error);
+            res.status(500).json({
+                success: false,
+                error: error.message,
+            });
+        }
+    });
+    // Get deployment status by ID
+    app.get('/cloud/deploy/status/:deploymentId', async (req, res) => {
+        try {
+            const { deploymentId } = req.params;
+            const deployment = await deploymentManager.getDeployment(deploymentId);
+            if (!deployment) {
+                return res.status(404).json({
+                    success: false,
+                    error: 'Deployment not found',
+                });
+            }
+            res.json({
+                success: true,
+                deployment,
+            });
+        }
+        catch (error) {
+            res.status(500).json({
+                success: false,
+                error: error.message,
+            });
+        }
+    });
+};
+exports.deployEndpoints = deployEndpoints;

package/dist/cjs/cloud/new-deployment/listeners/streaming-deployment-listener.d.ts

@@ -0,0 +1,45 @@
+import { Step, MotiaStream } from '@motiadev/core';
+import { Stream } from '@motiadev/core/dist/src/types-stream';
+import { BuildStepConfig } from '../../build/builder';
+import { ValidationError } from '../../build/build-validation';
+import { DeploymentListener, DeployData } from './listener.types';
+import { DeploymentData } from '../streams/deployment-stream';
+export declare class StreamingDeploymentListener implements DeploymentListener {
+    private deploymentId;
+    private errors;
+    private warnings;
+    private streamManager;
+    constructor(deploymentId: string, deploymentStream: MotiaStream<DeploymentData>);
+    private getStepType;
+    private getLanguage;
+    private updateStream;
+    getErrors(): ValidationError[];
+    onBuildStart(step: Step): void;
+    onBuildProgress(step: Step, message: string): void;
+    onBuildEnd(step: Step, size: number): void;
+    onBuildError(step: Step, error: Error): void;
+    onBuildSkip(step: Step, reason: string): void;
+    onStreamCreated(stream: Stream): void;
+    onApiRouterBuilding(language: string): void;
+    onApiRouterBuilt(language: string, size: number): void;
+    onWarning(id: string, warning: string): void;
+    onBuildWarning(warning: ValidationError): Promise<void>;
+    onBuildErrors(errors: ValidationError[]): Promise<void>;
+    stepUploadStart(stepPath: string, step: BuildStepConfig): void;
+    stepUploadProgress(stepPath: string, step: BuildStepConfig, progress: number): void;
+    stepUploadEnd(stepPath: string, step: BuildStepConfig): void;
+    stepUploadError(stepPath: string, step: BuildStepConfig): void;
+    routeUploadStart(path: string, language: string): void;
+    routeUploadProgress(path: string, language: string, progress: number): void;
+    routeUploadEnd(path: string, language: string): void;
+    routeUploadError(path: string, language: string): void;
+    onDeployStart(): void;
+    onDeployProgress(data: DeployData): void;
+    onDeployEnd(): Promise<void>;
+    onDeployError(errorMessage: string): Promise<void>;
+    startBuildPhase(): Promise<void>;
+    completeBuildPhase(): Promise<void>;
+    startUploadPhase(): Promise<void>;
+    completeUploadPhase(): Promise<void>;
+    startDeployPhase(): Promise<void>;
+}