Skip to content

Commit 179ecd5

Browse files
committed
small fixes and typos
1 parent 8f805fa commit 179ecd5

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/content/changelog/agents/2025-07-21-agents-queue-email-context-update.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The latest releases of [@cloudflare/agents] (https://github.com/cloudflare/agent
1212

1313
### Lightweight .queue for fast task deferral
1414

15-
You can use .queue() to enqueue background work — ideal for tasks like processing user messages, sending notifications etc.
15+
You can use `.queue()` to enqueue background work — ideal for tasks like processing user messages, sending notifications etc.
1616

1717
```ts
1818
class MyAgent extends Agent {
@@ -30,9 +30,9 @@ class MyAgent extends Agent {
3030

3131
Want to try it yourself? Just define a method like processMessage in your agent, and you’re ready to scale.
3232

33-
### New email adaptor
33+
### New email adapter
3434

35-
Want to build an AI agent that can receive and respond to emails automatically? With the new email adaptor and onEmail lifecycle method, now you can.
35+
Want to build an AI agent that can receive and respond to emails automatically? With the new email adapter and onEmail lifecycle method, now you can.
3636

3737
```ts
3838
export class EmailAgent extends Agent {
@@ -67,11 +67,11 @@ You can find a full example [here](https://github.com/cloudflare/agents/tree/mai
6767

6868
### Automatic context wrapping for custom methods
6969

70-
Custom methods are now automatically wrapped with the agent's context, so calling `getCurrentAgent()` should work regardless of where in an agent's lifecycle it's called. Previously this would not work on RPC calls, but not just works out of the box.
70+
Custom methods are now automatically wrapped with the agent's context, so calling `getCurrentAgent()` should work regardless of where in an agent's lifecycle it's called. Previously this would not work on RPC calls, but now just works out of the box.
7171

7272
```ts
7373
export class MyAgent extends Agent {
74-
async suggestReply(ctx, { message }) {
74+
async suggestReply(message) {
7575
// getCurrentAgent() now correctly works, even when called inside an RPC method
7676
const { agent } = getCurrentAgent()!;
7777
return generateText({

0 commit comments

Comments
 (0)