onward

Author: elithrar

src/content/docs/agents/concepts/communcating-with-users.mdx

@@ -1,10 +1,10 @@
 ---
-title: Self-hosting Agents
+title: Browse the web
 pcx_content_type: concept
 sidebar:
   order: 99
 ---
 
-import { MetaInfo, Render, Type, WranglerConfig } from "~/components";
+import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 
-TODO - send emails
+TODO

src/content/docs/agents/examples/ask-ai-models.mdx

@@ -1,11 +1,11 @@
 ---
-title: Asynchronous Workflows
+title: Evals
 pcx_content_type: concept
 sidebar:
   order: 15
 
 ---
 
-import { MetaInfo, Render, Type, WranglerConfig } from "~/components";
+import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 
 TODO

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

@@ -0,0 +1,81 @@
+---
+title: Manage and sync state
+pcx_content_type: concept
+sidebar:
+  order: 6
+---
+
+import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
+
+Every Agent has built-in state management capabilities, including built-in storage and synchronization between the Agent and frontend applications. State within an Agent is:
+
+* Persisted across Agent restarts: data is permanently persisted within the Agent.
+* Automatically serialized/deserialized: you can store any JSON-serializable data.
+* Immediately consistent within the Agent: read your own writes.
+* Thread-safe for concurrent updates
+
+### State management
+
+Every agent has built-in state management capabilities. You can set and update the agent's state directly using `this.state`:
+
+<TypeScriptExample>
+
+```ts
+import { Agent } from "@cloudflare/agents";
+
+export class MyAgent extends Agent {
+  // Update state in response to events
+  async incrementCounter() {
+    this.setState({
+      ...this.state,
+      counter: this.state.counter + 1,
+    });
+  }
+
+  // Handle incoming messages
+  async onMessage(message) {
+    if (message.type === "update") {
+      this.setState({
+        ...this.state,
+        ...message.data,
+      });
+    }
+  }
+
+  // Handle state updates
+  onStateUpdate(state, source: "server" | Connection) {
+    console.log("state updated", state);
+  }
+}
+```
+
+</TypeScriptExample>
+
+### Synchronizing state
+
+Clients can connect to an Agent and stay synchronized with its state using the React hooks provided as part of `@cloudflare/agents/react`:
+
+<TypeScriptExample>
+
+```ts
+
+
+```
+
+</TypeScriptExample>
+
+
+The state synchronization system:
+
+* Automatically syncs the agent's state to all connected clients
+* Handles client disconnections and reconnections gracefully
+* Provides immediate local updates
+* Supports multiple simultaneous client connections
+
+Common use cases:
+
+* Real-time collaborative features
+* Multi-window/tab synchronization
+* Live updates across multiple devices
+* Maintaining consistent UI state across clients
+* When new clients connect, they automatically receive the current state from the agent, ensuring all clients start with the latest data.

src/content/docs/agents/examples/evals.mdx

@@ -1,11 +1,11 @@
 ---
-title: Asynchronous Workflows
+title: Retrieval Augmented Generation
 pcx_content_type: concept
 sidebar:
   order: 7
 
 ---
 
-import { MetaInfo, Render, Type, WranglerConfig } from "~/components";
+import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 
 TODO

src/content/docs/agents/examples/manage-and-sync-state.mdx

@@ -6,7 +6,6 @@ sidebar:
 
 ---
 
-import { MetaInfo, Render, Type, WranglerConfig } from "~/components";
+import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 
 TODO - show how to invoke a Workflow from an Agent
-

src/content/docs/agents/examples/persist-data.mdx

@@ -1,11 +1,65 @@
 ---
-title: Persist data
+title: Schedule tasks
 pcx_content_type: concept
 sidebar:
   order: 5
 
 ---
 
-import { MetaInfo, Render, Type, WranglerConfig } from "~/components";
+import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 
-TODO
+An Agent can schedule tasks to be run in the future by calling `this.schedule(when, callback, data)`, where `when` can be a delay, a `Date`, or a cron string; callback the function name to call, and data is an object of data to pass to the function.
+
+### Scheduling tasks
+
+You can call `this.schedule` within any method on an Agent:
+
+<TypeScriptExample>
+
+```ts
+// schedule a task to run in 10 seconds
+this.schedule(10, "myTask", { message: "hello" });
+
+// schedule a task to run at a specific date
+this.schedule(new Date("2025-01-01"), "myTask", { message: "hello" });
+
+// schedule a task to run every 10 seconds
+this.schedule("*/10 * * * *", "myTask", { message: "hello" });
+
+// schedule a task to run every 10 seconds, but only on Mondays
+let task = await this.schedule("0 0 * * 1", "myTask", { message: "hello" });
+
+// cancel a scheduled task
+this.cancelSchedule(task.id);
+```
+
+</TypeScriptExample>
+
+
+### Managing scheduled tasks
+
+You can get, cancel and filter across scheduled tasks within an Agent using the scheduling API:
+
+<TypeScriptExample>
+
+```ts
+// Get a specific schedule by ID
+let task = await this.getSchedule(task.id)
+
+// Get all scheduled tasks
+let tasks = await this.getScheduledTasks();
+
+// Cancel a task by its ID
+await this.cancelSchedule(task.id);
+
+// Filter for specific tasks
+// e.g. all tasks starting in the next hour
+let tasks = this.getSchedules({ // returns an iterator
+	timeRange: {
+		start: new Date(Date.now()),
+		end: new Date(Date.now() + 60 * 60 * 1000),
+	},
+);
+```
+
+</TypeScriptExample>

src/content/docs/agents/examples/rag.mdx

@@ -1,11 +1,11 @@
 ---
-title: Send Emails
+title: Self-hosting Agents
 pcx_content_type: concept
 sidebar:
   order: 100
 
 ---
 
-import { MetaInfo, Render, Type, WranglerConfig } from "~/components";
+import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/components";
 
-TODO - send emails
+TODO