headers

Author: elithrar

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

@@ -113,7 +113,7 @@ class MyAgent extends Agent<Env, State> {
 }
 ```
 
-### WebSocket connection Handling
+### WebSocket connection handling
 
 #### Connection
 
@@ -166,7 +166,7 @@ interface ConnectionContext {
 
 ### State Management
 
-#### State Management
+#### State management
 
 Methods and types for managing Agent state.
 
@@ -280,9 +280,9 @@ type Schedule<T = any> = {
 let task = await this.schedule(300, "methodToCall", { message: "data-to-send-to-method" });
 ```
 
-### SQL Database Access
+### SQL database
 
-#### SQL Query API
+#### SQL query API
 
 Execute SQL queries against the Agent's built-in SQLite database using the `this.sql` method within any method on your `Agent` class.
 
@@ -359,7 +359,7 @@ function agentFetch(
 ): Promise<Response>;
 ```
 
-### React Integration
+### React API
 
 The `agents-sdk` provides a React API for simplifying connection and routing to Agents from front-end frameworks, including React Router (Remix), Next.js, and Astro.
 
@@ -425,7 +425,7 @@ class AIChatAgent<Env = unknown> extends Agent<Env> {
 }
 ```
 
-### AI React Hooks
+### Chat Agent React API
 
 #### useAgentChat
 
@@ -471,7 +471,6 @@ To learn more about how to manage state within an Agent, refer to the documentat
 
 :::
 
-
 ### Next steps
 
 * [Build a chat Agent](/agents/getting-started/build-a-chat-agent/) using the `agents-sdk` and deploy it to Workers.

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

@@ -10,7 +10,7 @@ import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/com
 
 Learn how to call your Agents from Workers, including how to create Agents on-the-fly, address them, and route requests to specific instances of an Agent.
 
-## Calling your Agent
+### Calling your Agent
 
 Agents are created on-the-fly and can serve multiple requests concurrently. Each Agent instance is isolated from other instances, can maintain its own state, and has a unique address.
 

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

@@ -9,6 +9,8 @@ import { MetaInfo, Render, Type, WranglerConfig } from "~/components";
 
 An Agent is configured like any other Cloudflare Workers project, and uses [a wrangler configuration](/workers/wrangler/configuration/) file to define where your code is and what services (bindings) it will use.
 
+### Project structure
+
 The typical file structure for an Agent project created from `npm create cloudflare@latest agents-starter -- --template cloudflare/agents-starter` follows:
 
 ```sh
@@ -28,6 +30,8 @@ The typical file structure for an Agent project created from `npm create cloudfl
 `-- wrangler.jsonc // your Workers & Agent configuration
 ```
 
+### Example configuration
+
 Below is a minimal `wrangler.jsonc` file that defines the configuration for an Agent, including the entry point, `durable_object` namespace, and code `migrations`:
 
 <WranglerConfig>
@@ -70,3 +74,5 @@ The configuration includes:
 - A `main` field that points to the entry point of your Agent, which is typically a TypeScript (or JavaScript) file.
 - A `durable_objects` field that defines the [Durable Object namespace](/durable-objects/reference/glossary/) that your Agents will run within.
 - A `migrations` field that defines the code migrations that your Agent will use. This field is mandatory and must contain at least one migration. The `new_sqlite_classes` field is mandatory for the Agent to store state.
+
+Agents must define these fields in their `wrangler.jsonc` (or `wrangler.toml`) config file.

src/content/docs/agents/api-reference/http-sse.mdx

@@ -10,12 +10,10 @@ import { MetaInfo, Render, Type, TypeScriptExample, WranglerConfig } from "~/com
 
 The Agents SDK allows you to handle HTTP requests and has native support for [Server-Sent Events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events) (SSE). This allows you build applications that can push data to clients, avoid buffering
 
-## Handling HTTP requests
+### Handling HTTP requests
 
 Agents can handle HTTP requests using the `onRequest` method, which is called whenever an HTTP request is received by the Agent instance. The method takes a `Request` object as a parameter and returns a `Response` object.
 
-
-
 <TypeScriptExample>
 
 ```ts
@@ -99,7 +97,6 @@ export default {
 
 </TypeScriptExample>
 
-## WebSockets vs. Server-Sent Events
-
-
+### WebSockets vs. Server-Sent Events
 
+TODO

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

@@ -38,7 +38,7 @@ export class ChatAgent extends Agent {
 
 </TypeScriptExample>
 
-## Connecting clients
+### Connecting clients
 
 The Agent framework includes a useful helper package for connecting directly to your Agent (or other Agents) from a client application. Import `agents-sdk/client`, create an instance of `AgentClient` and use it to connect to an instance of your Agent:
 
@@ -66,7 +66,7 @@ connection.send(
 
 </TypeScriptExample>
 
-## React clients
+### React clients
 
 React-based applications can import `agents-sdk/react` and use the `useAgent` hook to connect to an instance of an Agent directly:
 
@@ -107,7 +107,7 @@ function AgentInterface() {
 
 The `useAgent` hook automatically handles the lifecycle of the connection, ensuring that it is properly initialized and cleaned up when the component mounts and unmounts. You can also [combine `useAgent` with `useState`](/agents/api-reference/store-and-sync-state/) to automatically synchronize state across all clients connected to your Agent.
 
-## Handling WebSocket events
+### Handling WebSocket events
 
 Define `onError` and `onClose` methods on your Agent to explicitly handle WebSocket client errors and close events. Log errors, clean up state, and/or emit metrics: