fix config

Author: elithrar

src/content/docs/agents/api-reference/configuration.mdx

@@ -42,8 +42,11 @@ Below is a minimal `wrangler.jsonc` file that defines the configuration for an A
 	"durable_objects": {
 		"bindings": [
 			{
+				// Required:
 				"name": "MyAgent", // How your Agent is called from your Worker
 				"class_name": "MyAgent", // Must match the class name of the Agent in your code
+				// Optional: set this if the Agent is defined in another Worker script
+				"script_name": "the-other-worker"
 			},
 		],
 	},

src/content/docs/agents/concepts/workflows.mdx

@@ -3,21 +3,22 @@ title: Workflows
 pcx_content_type: concept
 sidebar:
   order: 3
-
 ---
 
 import { Render } from "~/components";
 
-### What are workflows? 
+## What are workflows?
+
 A workflow is the orchestration layer that coordinates how an agent's components work together. It defines the structured paths through which tasks are processed, tools are called, and results are managed. While agents make dynamic decisions about what to do, workflows provide the underlying framework that governs how those decisions are executed.
 
-#### Understanding Workflows in Agent Systems
+### Understanding Workflows in Agent Systems
 
 Think of a workflow like the operating procedures of a company. The company (agent) can make various decisions, but how those decisions get implemented follows established processes (workflows). For example, when you book a flight through a travel agent, they might make different decisions about which flights to recommend, but the process of actually booking the flight follows a fixed sequence of steps.
 
 Let's examine a basic agent workflow:
 
-#### Core Components of a Workflow
+### Core Components of a Workflow
+
 A workflow typically consists of several key elements:
 
 1. **Input Processing**
@@ -28,4 +29,3 @@ Workflows manage how external tools and services are accessed. They handle authe
 The workflow maintains the state of ongoing processes, tracking progress through multiple steps and ensuring consistency across operations.
 4. **Output Handling**
 Results from the agent's actions are processed according to defined rules, whether that means storing data, triggering notifications, or formatting responses.
-

src/content/docs/agents/examples/browse-the-web.mdx

@@ -21,7 +21,9 @@ interface Env {
 }
 
 export class MyAgent extends Agent<Env> {
-
+	constructor(env: Env) {
+		super(env);
+	}
 }
 ```
 
@@ -35,7 +37,7 @@ npm install @cloudflare/puppeteer --save-dev
 
 <WranglerConfig>
 
-```jsonc title=
+```jsonc
 "browser": {
     "binding": "MYBROWSER"
   },
@@ -73,7 +75,9 @@ interface Env {
 }
 
 export class MyAgent extends Agent<Env> {
-
+	constructor(env: Env) {
+		super(env);
+	}
 }
 ```
 

src/content/docs/agents/examples/run-workflows.mdx

@@ -9,3 +9,81 @@ sidebar:
 import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 
 TODO - show how to invoke a Workflow from an Agent
+
+Agents can trigger asynchronous [Workflows](/workflows/), allowing your Agent to run complex, multi-step tasks in the background. This can include post-processing files that a user has uploaded, updating the embeddings in a [vector database](/vectorize/), and/or managing long-running user-lifecycle email or SMS notification workflows.
+
+Because an Agent is just like a Worker script, it can create Workflows defined in the same project (script) as the Agent _or_ in a different project.
+
+## Trigger a Workflow
+
+<TypeScriptExample>
+
+```ts
+interface Env {
+	BROWSER: Fetcher;
+}
+
+export class MyAgent extends Agent<Env> {
+
+}
+```
+
+</TypeScriptExample>
+
+<WranglerConfig>
+
+```jsonc
+{
+	"$schema": "node_modules/wrangler/config-schema.json",
+	"name": "agents-example",
+	"main": "src/index.ts",
+	"compatibility_date": "2025-02-23",
+	"compatibility_flags": ["nodejs_compat"],
+	// Create a binding between your Agent and your Workflow
+	"workflows": [{ "name": "EMAIL_WORKFLOW", "class_name": "EmailWorkflow" }],
+	"durable_objects": {
+		"bindings": [
+			{
+				"name": "MyAgent",
+				"class_name": "MyAgent",
+			},
+		],
+	},
+	"migrations": [
+		{
+			"tag": "v1",
+			// Mandatory for the Agent to store state
+			"new_sqlite_classes": ["MyAgent"],
+		},
+	],
+	"observability": {
+		"enabled": true,
+	},
+}
+```
+
+</WranglerConfig>
+
+## Trigger a Workflow from another project
+
+You can also call a Workflow that is defined in a different Workers script from your Agent by setting the `script_name` property in the `workflows` binding of your Agent:
+
+<WranglerConfig>
+
+```jsonc
+{
+	// ...
+	"workflows": [
+		{ "name": "EMAIL_WORKFLOW",
+			"class_name": "EmailWorkflow",
+			// Set script_name to the name of the Worker that contains the EmailWorkflow definition
+			"script_name": "email-workflow-prod"
+		},
+	],
+	// ...
+}
+```
+
+</WranglerConfig>
+
+Refer to the [cross-script calls](/workflows/build/workers-api/#cross-script-calls) section of the Workflows documentation for more examples.