@cursor/bdk 0.2.24 → 0.2.26

package/docs/guides/pagerduty.md

@@ -0,0 +1,341 @@
+---
+title: "PagerDuty"
+description: "Respond to PagerDuty incidents: investigate a page, follow it through acknowledgement and resolution, and ignore your own actions."
+---
+
+# PagerDuty agents
+
+A PagerDuty agent wakes when an incident triggers, investigates it, and
+writes what it found back to the incident. `pagerdutyChannel()` receives
+PagerDuty's v3 webhooks, verifies them, and keeps every later event for
+the same incident in one session, so the agent sees an acknowledgement,
+a note, or a responder's reply in the context of the investigation it
+already started. Every setting has a default read from a well-known secret, so
+the channel needs no configuration beyond its hooks; see
+[Connect](#connect) for the variables.
+
+## Investigate a new incident
+
+When an incident triggers, the agent starts a turn with the incident's
+title, service, urgency, and link. It reads whatever the investigation
+needs, and with `deliverReplies: true` its reply is posted as a note on
+the incident, where the person on call already looks.
+
+```ts
+// bot/channels/pagerduty.ts
+import { defaultPagerDutyAuth, pagerdutyChannel } from "@cursor/bdk/channels/pagerduty";
+
+export default pagerdutyChannel({
+  deliverReplies: true,
+  onIncident: (ctx, event) => {
+    if (event.eventType !== "incident.triggered") {
+      return null;
+    }
+    return {
+      // `auth` starts a model turn running as the event's PagerDuty actor.
+      auth: defaultPagerDutyAuth(ctx),
+      message: `Investigate PagerDuty incident #${event.incident.number}: ${event.incident.title}`,
+      context: [`Service: ${event.incident.service?.summary ?? "unknown"}`],
+    };
+  },
+});
+```
+
+Reply notes are off unless you set `deliverReplies: true`, so the channel
+writes nothing to PagerDuty on its own. An agent that writes to PagerDuty
+through its own path, such as a service that audits each write, leaves it
+off and posts only what it chooses, from `events` or `ctx.pagerduty`.
+
+With `deliverReplies: true`, the channel posts each completed reply as a
+note on the session's incident, and a short note if a turn fails, using
+the `PAGERDUTY_TOKEN` secret. The note goes to the incident in the
+verified event's state, so the model never chooses which incident it
+writes to. Eval runs and agents without a token post nothing. Nothing is
+posted until the channel knows the agent's own PagerDuty user (see
+[Ignore your own actions](#ignore-your-own-actions)), because each note
+comes back as a webhook event that only the echo skip keeps from starting
+another turn. Handlers you write in `events` replace the built-in ones.
+
+Hooks also get `ctx.pagerduty`, a REST client with the channel's
+credentials, for reads and writes of their own:
+
+```ts
+onIncident: async (ctx, event) => {
+  const incident = await ctx.pagerduty.getIncident(event.incident.id);
+  // …
+},
+```
+
+Hosted, the agent also declares PagerDuty's API host and the token:
+
+```ts
+// bot/agent.ts
+import { defineAgent } from "@cursor/bdk";
+
+export default defineAgent({
+  architecture: "v2",
+  hosting: {
+    egressDomains: ["api.pagerduty.com"],
+    secretNames: ["PAGERDUTY_TOKEN"],
+  },
+});
+```
+
+## Follow the incident in one session
+
+People act on an incident while the agent investigates: someone
+acknowledges it, adds a note, pulls in a responder, or resolves it.
+Return a dispatch for those events too, and each one arrives in the
+session that is already working on the incident, with the earlier
+findings in context.
+
+```ts
+onIncident: (ctx, event) => {
+  const followUps = ["incident.acknowledged", "incident.reassigned", "incident.resolved"];
+  if (event.eventType !== "incident.triggered" && !followUps.includes(event.eventType)) {
+    return null;
+  }
+  return {
+    auth: defaultPagerDutyAuth(ctx),
+    message: `${event.eventType} by ${ctx.agent?.summary ?? "PagerDuty"}`,
+  };
+},
+onNote: (ctx, note) => {
+  return {
+    auth: defaultPagerDutyAuth(ctx),
+    message: `Note on the incident: ${note.content}`,
+  };
+},
+```
+
+Add these to the same `pagerdutyChannel()` declaration as the
+investigation handler.
+
+## Ignore your own actions
+
+PagerDuty sends the agent's own changes back as webhook events: the
+note it posted, or an acknowledgement or resolve made through its
+PagerDuty user. The channel acknowledges those events without running a
+hook or starting a turn. The same action by a person is still delivered.
+
+The channel finds the agent's user in this order, on each delivery:
+
+1. The `selfUserIds` option, when you pass one. Nothing below is used.
+2. The `PAGERDUTY_USER_ID` secret: one PagerDuty user id.
+3. The user `PAGERDUTY_TOKEN` acts as, which PagerDuty reports at
+   `GET /users/me`.
+
+When none of these names a user, echo skip is off. `bdk deploy` warns
+while neither `PAGERDUTY_USER_ID` nor `PAGERDUTY_TOKEN` is set, and the
+agent logs a warning when its token names no single user.
+
+Inference depends on the kind of token:
+
+| `PAGERDUTY_TOKEN` | Inferred user |
+| --- | --- |
+| User token REST API key | The key's own user |
+| OAuth user token (Classic User OAuth or Scoped OAuth), written as `Bearer <token>` | The user who authorized the app |
+| General access (account-level) REST API key | The user whose email is exactly `PAGERDUTY_FROM_EMAIL`, if set |
+| Scoped OAuth app token (client credentials) | The user whose email is exactly `PAGERDUTY_FROM_EMAIL`, if set |
+
+PagerDuty serves
+[`GET /users/me`](https://developer.pagerduty.com/api-reference/0b6f8b0c3e8d1-get-the-current-user)
+only to a user-level API key or a token from an OAuth flow, not to an
+account-level key. An app token
+[acts as the app](https://docs.pagerduty.com/developer/private-apps),
+not as a user. With either, the channel looks up `PAGERDUTY_FROM_EMAIL`,
+the `From` user the token writes as, through `GET /users?query=` and uses
+the one user whose email matches exactly. The inferred id is kept in the
+agent's memory for an hour per token, never in agent storage, and an
+unresolved answer is retried after five minutes. Hosted, the lookup needs
+`api.pagerduty.com` (or your `PAGERDUTY_API_BASE_URL` host) in
+`hosting.egressDomains`, the same entry write-backs need.
+
+A read-only agent with no token sets the id directly:
+
+```bash
+bdk secrets set incident-responder PAGERDUTY_USER_ID
+```
+
+`PAGERDUTY_USER_ID` holds one id because a deployment has one token
+and so acts as one PagerDuty user. To skip several users, or to keep the
+id in code, pass `selfUserIds`:
+
+```ts
+export default pagerdutyChannel({
+  selfUserIds: ["PBOT001"],
+  onIncident: (ctx) => ({ auth: defaultPagerDutyAuth(ctx) }),
+});
+```
+
+`selfUserIds: { secretName: "OTHER_NAME" }` reads one id from another
+secret and never falls back to inference.
+
+## Events
+
+Each hook receives one family of v3 events:
+
+| Hook | Events |
+| --- | --- |
+| `onIncident` | `incident.triggered`, `.acknowledged`, `.unacknowledged`, `.escalated`, `.reassigned`, `.delegated`, `.resolved`, `.reopened`, `.priority_updated`, `.incident_type.changed` |
+| `onNote` | `incident.annotated` |
+| `onResponder` | `incident.responder.added`, `incident.responder.replied` |
+| `onEvent` | Everything else, such as status updates and workflow events |
+
+Without `onIncident`, a triggered or reopened incident starts a turn and
+other lifecycle events are acknowledged. Notes, responder events, and
+the rest are acknowledged until you add their hook. Each hook returns
+one of three decisions:
+
+| Return | What happens |
+| --- | --- |
+| `{ auth }` | Start or continue a model turn as the event's actor |
+| `{ task }` | Acknowledge the webhook, then run host code that may also call `send` |
+| `null` | Skip the event |
+
+## Incident affinity
+
+Every event for one incident joins one session, keyed on the incident
+id. Lifecycle events carry the incident, and notes and responder events
+name it by reference, so all of them reach the same session.
+
+A re-trigger after a resolve is a new PagerDuty incident, so it starts a
+new session. `ctx.incidentKey` carries the dedup key of the alert that
+opened an incident (its `incident_key`, set per alert by a Datadog
+monitor, a Sentry issue, or a Grafana rule), for an agent that wants to
+recall what it found the last time the same alert fired.
+
+## Connect
+
+Create a v3 webhook subscription in PagerDuty for the services that
+should wake the agent, and point it at
+`https://<your-host>/<slug>/v1/channels/pagerduty`. Then set the
+channel's secrets on the deployment. Locally the same names are
+environment variables.
+
+| Variable | Used for | Override |
+| --- | --- | --- |
+| `PAGERDUTY_WEBHOOK_SECRET` | Verifying `X-PagerDuty-Signature`. Hosted, the platform checks it before any compute starts and answers a bad delivery with `401` | `webhookSecret: { secretName }` |
+| `PAGERDUTY_USER_ID` | Skipping the agent's own actions: its PagerDuty user id. Optional when `PAGERDUTY_TOKEN` names a user | `selfUserIds: [ids]` or `{ secretName }` |
+| `PAGERDUTY_TOKEN` | Reply notes (with `deliverReplies: true`), `ctx.pagerduty`, and inferring the agent's user: a REST API key, or an OAuth token as `Bearer <token>` | `token: { secretName }` |
+| `PAGERDUTY_FROM_EMAIL` | The `From` user PagerDuty requires for writes made with an account-level key or app token, and the user inferred for those tokens | `from: { secretName }` |
+| `PAGERDUTY_API_BASE_URL` | The REST host, such as `https://api.eu.pagerduty.com`. Defaults to `https://api.pagerduty.com` | `apiBaseUrl` |
+
+Set `token`, `from`, and `apiBaseUrl` on `pagerdutyChannel()`; they cover
+reply notes, `ctx.pagerduty`, and inference. `createPagerDutyClient()`
+takes the same options for code outside the channel.
+
+```bash
+bdk deploy --dir . --slug incident-responder
+bdk secrets set incident-responder PAGERDUTY_WEBHOOK_SECRET PAGERDUTY_TOKEN
+bdk secrets list incident-responder
+```
+
+`bdk deploy` warns until `PAGERDUTY_WEBHOOK_SECRET` is set, and until
+either `PAGERDUTY_USER_ID` or `PAGERDUTY_TOKEN` is. The next delivery
+uses a new value without another deploy.
+
+### Several subscriptions
+
+PagerDuty gives each webhook subscription its own signing secret, so an
+agent fed by several subscriptions (one per service, say) needs all of
+them. Put them in `PAGERDUTY_WEBHOOK_SECRET`, one per line:
+
+```text
+<signing secret of subscription 1>
+<signing secret of subscription 2>
+```
+
+A delivery is admitted when any `v1=` signature in its
+`X-PagerDuty-Signature` header matches any line. Each line is trimmed,
+blank lines are ignored, and a value without a line break is one secret,
+used as-is. The value holds at most 32 secrets. Past that, every delivery
+is rejected rather than checked against only some of them.
+
+Keep the list in a file, since `bdk secrets list` never shows values,
+and set it from stdin, which keeps the line breaks:
+
+```bash
+bdk secrets set incident-responder PAGERDUTY_WEBHOOK_SECRET < pagerduty-webhook-secrets.txt
+```
+
+Rotate by adding before removing. Add the new secret as a line before
+PagerDuty starts signing with it, for example before creating the
+replacement subscription. Remove the old line only once nothing signs
+with the old secret, for example after deleting the subscription it
+replaced. While both are live, a delivery signed with either secret
+verifies, including one whose header carries both signatures. Removing
+the old line first rejects those deliveries until the new one is added.
+
+The same format works for every `hmacSignatureAuth()` secret, including
+`GITHUB_WEBHOOK_SECRET` and `BITBUCKET_WEBHOOK_SECRET`. It needs
+`@cursor/bdk` 0.2.25 or later. Earlier versions check the signature again
+in the agent with the whole value as one secret, so they reject every
+delivery once the value has a second line.
+
+Only signature checks read the value as a list. Everywhere else it is
+used whole: a `sharedSecretAuth()` header compares the entire value, and
+a `${NAME}` template in an MCP connection's `headers` would put the line
+breaks into the header. Keep a list secret for webhook signing only.
+
+Until `PAGERDUTY_WEBHOOK_SECRET` is set, the route accepts only local
+traffic: loopback deliveries under `bdk dev`, nothing in production.
+
+## Test locally
+
+`bdk pagerduty replay` posts synthesized v3 deliveries for one incident
+to the running agent, in order. With `PAGERDUTY_WEBHOOK_SECRET` unset,
+`bdk dev` admits them unsigned from loopback; with it set, replay signs
+them the way PagerDuty does:
+
+```bash
+bdk dev &
+bdk pagerduty replay --events triggered,acknowledged,annotated,resolved \
+  --comment "Rolled back the 09:30 deploy."
+```
+
+The trigger comes from PagerDuty itself, and the later events come from a
+person, so each one joins the session the trigger started. Pass an
+incident id to start another session, `--dry-run` to print the bodies,
+or `--out fixtures/pagerduty` to save them as fixtures for
+[evals](../evals.md). `bdk pagerduty events` lists the channels and the
+events each accepts.
+
+To post a real delivery saved from the webhook's delivery log, sign it
+with the secret:
+
+```bash
+export PAGERDUTY_WEBHOOK_SECRET=local-test-secret
+bdk dev &
+
+body=fixtures/pagerduty/incident-triggered.json
+signature=$(openssl dgst -sha256 -hmac "$PAGERDUTY_WEBHOOK_SECRET" -hex < "$body" | awk '{print $NF}')
+curl -X POST http://127.0.0.1:3000/v1/channels/pagerduty \
+  -H 'content-type: application/json' \
+  -H "x-pagerduty-signature: v1=$signature" \
+  --data-binary @"$body"
+```
+
+Set `event.agent.id` in a saved body to the agent's own user id to see
+the delivery skipped as an echo.
+
+## Practices
+
+- Write back from host code with the incident in channel state or
+  `ctx`, never from an incident id the model produced.
+
+- Make sure the agent knows its own user before it acts on incidents, so
+  its own notes and resolves do not wake it again: a user-level token, a
+  `PAGERDUTY_FROM_EMAIL` with an account-level key, or `PAGERDUTY_USER_ID`.
+
+- Scope the webhook subscription to the services the agent responds to;
+  every delivery it sends reaches the channel.
+
+## Related
+
+- [Channels reference](../reference/channels.md): channel hooks,
+  dispatch decisions, and session behavior
+- [Webhooks and custom channels](./webhooks.md): direct webhook auth
+  and reply delivery
+- [Evals](../evals.md): turn saved PagerDuty payloads into regression
+  fixtures

package/docs/guides/slack.md

@@ -99,6 +99,47 @@ export default slackChannel({
 });
 ```
 
+### Show steps as cards or as a checklist
+
+The agent calls `post-card` to show one step of its work, such as
+"Scan the repo". Each card has an `id`, a `title`, a `status`, and
+optional `details`. When the agent calls `post-card` again with the same
+`id`, Slack updates that card. The agent uses this to move a step from
+`in_progress` to `complete`.
+
+`cards` sets how Slack draws these steps:
+
+| `cards` | What Slack shows | Use it when |
+| --- | --- | --- |
+| `{ display: "timeline" }` (default) | Each step is a separate card in the thread. | The turn has one or two short steps. |
+| `{ display: "plan" }` | All steps from one turn are in one checklist. | The turn has several steps, and readers want to see progress in one place. |
+
+This bot shows its steps as one checklist with the title "Release check":
+
+```ts
+export default slackChannel({
+  reply: {
+    mode: "agentic",
+    cards: { display: "plan", title: "Release check" },
+  },
+});
+```
+
+Know these rules for a plan:
+
+- The `title` is optional. It can have at most 256 characters.
+- You set the `title` in the channel configuration. The agent cannot
+  change the title.
+- Each turn starts a new checklist with the same title.
+- The `pending` status shows a step that has not started. Use `pending`
+  only in a plan.
+- `slackChannel` stops at startup if `cards` is not valid. For example,
+  a `title` with `display: "timeline"` stops startup.
+
+`display` is Slack's
+[`task_display_mode`](https://docs.slack.dev/reference/methods/chat.startStream/),
+and the channel sends `title` as a `plan_update` chunk.
+
 ## Wake on a channel post
 
 This example watches `#triage-alerts`, so any substantial top-level

package/docs/reference/agent-config.md

@@ -196,15 +196,35 @@ const handle = await serve("./my-agent", {
 });
 console.log(`listening on ${handle.url}`);
 // handle.callTool(...), handle.dispatchSchedule("heartbeat"),
-// handle.createReminder(...), handle.project, await handle.close()
+// handle.createReminder(...), handle.agents, await handle.close()
 ```
 
+`handle.agents` lists each mount as `slug`, `url`, and `info`. `handle.project` is the first agent's project. It is deprecated.
+
 Host settings match the documented [CLI](./cli.md) `serve` flags.
 `serve()` also accepts `discovery` (project-loading options) and
 `mode: "single" | "multi"`. Pass `apiKey` or use the same Cursor
 credential as the CLI: `CURSOR_API_KEY`, `CURSOR_API_KEY_FILE`,
 `CURSOR_SERVICE_ACCOUNT_KEY`, or `bdk login`.
 
+## Inspect a project in tests
+
+`loadProject(dir)` reads one project and does not serve it. The result is a `Project`. The only field is `info`. That object matches the `GET /v1/info` body for the project. `bdk info --json` on a project directory prints `{ agents: [{ slug, ...info }] }`. It prints the bare object only when the single mount slug is empty.
+
+```ts
+import { loadProject } from "@cursor/bdk";
+
+const project = await loadProject("./my-agent");
+console.log(project.info.name);
+console.log(project.info.tools.map((tool) => tool.name));
+```
+
+`loadProject` throws `ProjectLoadError` when discovery reports an error. Pass `{ strict: true }` to throw on a warning as well. `error.diagnostics` lists the findings. Each `path` is relative to the project directory. A path outside that directory starts with `../`. `loadProject` does not take `importModule`. `serve` still accepts `discovery.importModule` for that override.
+
+`info.local` is `{ cwd }` when the project sets a cwd. The serve banner reads `agents[].info`.
+
+`serve` accepts that `Project` or a directory path.
+
 ## Related
 
 - [Instructions](./instructions.md): the required half of a minimal

package/docs/reference/channels.md

@@ -117,11 +117,15 @@ Each handler receives the Fetch `Request` and a typed arguments object.
 | `purpose` | Use `"eval"` to mark a new session as regression traffic |
 | `dryRun` | Run read tools and stub write tools for a new session |
 | `asOf` | Freeze a new session at an ISO-8601 instant with a timezone |
+| `deliveryId` | Name this send on the session's events, at most 256 characters. Defaults to a fresh `dlv_…` ID |
 
 `send` returns a `ChannelSession`. Its `id` identifies the session,
 `continuationToken` contains its current channel key, and `isNew` says
 whether this call created it. A coalesced call also returns
-`coalesced: true`.
+`coalesced: true`. `deliveryId` names this send on the event where the
+message reaches the agent; see
+[Track which follow-up reached the agent](./sessions.md#track-which-follow-up-reached-the-agent).
+A hosted channel's `send` returns the same ID before the session exists.
 
 ## Events
 
@@ -166,7 +170,7 @@ returns `401`.
 | `loopbackOnly()` | Any loopback TCP peer, including local relays that carry forwarding headers |
 | `bearerAuth(tokenOrVerify)` | A matching bearer token, or a token accepted by the verifier |
 | `sharedSecretAuth({ header, secret })` | A header matching the named environment or deployment secret |
-| `hmacSignatureAuth({ header, secret, prefix? })` | A hex HMAC-SHA256 signature over the raw body using the named secret |
+| `hmacSignatureAuth({ header, secret, prefix?, separator? })` | A hex HMAC-SHA256 signature over the raw body using the named secret. With `separator`, any of several signatures in the header. A secret holding one value per line verifies under any of them (at most 32, `@cursor/bdk` 0.2.25 or later) |
 | `allowAll()` | Every caller as an anonymous principal |
 | `publicEndpoint()` | Every caller on this custom channel; managed hosting also exposes the route without an alias token |
 
@@ -193,6 +197,7 @@ author their own chain, and `--allow-anonymous` swaps it for
 | `@cursor/bdk/channels/github` | `githubChannel()` | GitHub and GitHub Enterprise webhooks. See [GitHub](../guides/github.md) |
 | `@cursor/bdk/channels/gitlab` | `gitlabChannel()` | GitLab.com and self-managed GitLab hooks. See [GitLab](../guides/gitlab.md) |
 | `@cursor/bdk/channels/bitbucket` | `bitbucketChannel()` | Bitbucket Cloud and Data Center hooks. See [Bitbucket](../guides/bitbucket.md) |
+| `@cursor/bdk/channels/pagerduty` | `pagerdutyChannel()` | PagerDuty v3 incident webhooks. Replies post as incident notes only with `deliverReplies: true`. See [PagerDuty](../guides/pagerduty.md) |
 | `@cursor/bdk/channels/deployments` | `deploymentsChannel()` | Deployment events filtered by source, environment, or event name |
 
 For other platforms like Discord or Teams, use the authored

package/docs/reference/cli.md

@@ -1024,6 +1024,33 @@ follow the GitHub replay contract.
 
 See [Bitbucket](../guides/bitbucket.md) for Cloud and Data Center setup.
 
+### Test PagerDuty webhooks {#pagerduty}
+
+```text
+bdk pagerduty replay [incident-id]
+  [--events a,b,c | '*'] [--comment <body>]
+  [--dir <path>] [--slug <slug>] [--channel <id>]
+  [--url <url>] [--host <host>] [--port <n>]
+  [--secret <secret>] [--dry-run] [--out <dir>] [--json]
+bdk pagerduty events [--dir <path>] [--host <host>] [--port <n>] [--json]
+```
+
+| Subcommand | Contract |
+| --- | --- |
+| `replay` | Synthesize v3 webhook bodies for one incident and post them, in order, to matching channels. The default event is `incident.triggered`; `'*'` selects every declared event replay supports. |
+| `events` | List discovered PagerDuty channel URLs and event types. |
+
+Replay supports `incident.triggered`, `.acknowledged`, `.annotated`,
+`.escalated`, `.resolved`, and `.reopened`, by full name or by action alone
+(`resolved`). It needs no PagerDuty account. The incident id defaults to
+`PREPLAY1`, and `--comment` is the note body for `annotated`. `--secret`
+defaults to `PAGERDUTY_WEBHOOK_SECRET`, signing with its first line when it
+lists several; without either the deliveries are unsigned, which `bdk dev`
+admits from loopback. `--dry-run` and `--out`
+follow the GitHub replay contract.
+
+See [PagerDuty](../guides/pagerduty.md) for channel setup.
+
 ## Environment variables
 
 Credential resolution follows this order: `--api-key`, `CURSOR_API_KEY`,

package/docs/reference/hooks.md

@@ -28,20 +28,26 @@ Author `bot/hooks/<name>.ts` with `defineHook` from
 
 ```ts
 // bot/hooks/usage.ts
+import { metrics } from "@opentelemetry/api";
 import { defineHook } from "@cursor/bdk/hooks";
 
+const meter = metrics.getMeter("acme");
+const inputTokens = meter.createCounter("acme.tokens.input");
+const outputTokens = meter.createCounter("acme.tokens.output");
+const turnFailed = meter.createCounter("acme.turn.failed");
+
 export default defineHook({
   events: {
     async "turn.completed"(event, ctx) {
       if (ctx.session.purpose === "eval" || event.data.usage === undefined) {
         return;
       }
-      const { inputTokens, outputTokens } = event.data.usage;
-      ctx.host.otel.increment("acme.tokens.input", inputTokens);
-      ctx.host.otel.increment("acme.tokens.output", outputTokens);
+      const usage = event.data.usage;
+      inputTokens.add(usage.inputTokens);
+      outputTokens.add(usage.outputTokens);
     },
     async "turn.failed"(_event, ctx) {
-      ctx.host.otel.increment("acme.turn.failed", { channel: ctx.channel.id });
+      turnFailed.add(1, { channel: ctx.channel.id });
     },
   },
 });
@@ -93,7 +99,6 @@ exported from `@cursor/bdk`.
 | `ctx.channel`                                       | `{ id, continuationToken }`. The token is `null` when the session can't take follow-ups                                                                    |
 | `ctx.host.kv`                                       | Durable JSON, shared by every session of the agent. Prefix keys with `ctx.session.id` for per-session state                                                |
 | `ctx.host.files`                                    | Durable files, bound to this session. Pass `{ scope: "deployment" }` for agent-wide files                                                                  |
-| `ctx.host.otel`                                     | Counters, histograms, and tags, attributed to this session                                                                                                 |
 | `ctx.host.mcp`, `ctx.host.github`, `ctx.host.slack` | The same shared clients tools get                                                                                                                          |
 | `ctx.host.reminders`                                | Per-session [reminders](./schedules.md#reminders), the same API tools get                                                                                  |
 | `ctx.artifacts`                                     | Session-bound [artifacts](./artifacts.md) facade: `tag` fills in `sessionId` and `turnId`                                                                  |

package/docs/reference/sessions.md

@@ -64,6 +64,51 @@ the session is already busy depends on the channel:
 Pass `admission: "coalesce"` on `send()` to opt into the Slack policy from
 other callers. Omit it (or pass `"preempt"`) to keep interrupt semantics.
 
+### Track which follow-up reached the agent
+
+Every `send()` returns a `deliveryId`. Pass your own as the `deliveryId`
+option, such as the webhook delivery ID you already hold, or omit it to
+get a fresh `dlv_…` ID. A coalesced follow-up reaches the agent in one of
+two ways, and the ID is on the event for that path:
+
+| Path | Event | Field |
+| --- | --- | --- |
+| Steered into the running turn | `nudge.delivered` | `data.deliveryId` |
+| Fell back to the next turn | That turn's `message.received` | `data.deliveryIds` |
+
+`message.received` lists every send its prompt carries, in arrival order.
+Follow-ups queued behind a busy turn drain into one turn, so the list can
+hold several IDs. A direct send that starts a turn gets a one-item list.
+
+```ts
+// In a route or channel hook: name the steer after the webhook delivery.
+await send(`Incident ${incident.id} was acknowledged.`, {
+  continuationToken: incident.id,
+  admission: "coalesce",
+  deliveryId: webhookId,
+});
+
+// In the channel's `events` map:
+const steered = new Set<string>();
+const prompted = new Set<string>();
+const events: ChannelEventHandlers = {
+  "nudge.delivered": async (event) => {
+    if (event.data.deliveryId !== undefined) {
+      steered.add(event.data.deliveryId);
+    }
+  },
+  "message.received": async (event) => {
+    for (const id of event.data.deliveryIds ?? []) {
+      prompted.add(id);
+    }
+  },
+};
+```
+
+A local Slack session can also pick up follow-ups at a tool boundary from
+its own thread store. That `nudge.delivered` has no `deliveryId`, which
+tells it apart from a steered send.
+
 `POST /v1/session/:id/stop` interrupts a turn without sending a new
 message. The stream records `turn.failed` with `status: "cancelled"`;
 the session stays a chat session and can take another follow-up. A
@@ -82,7 +127,7 @@ within one session. The `at` field is an ISO-8601 timestamp.
 | Phase | Events | What they tell you |
 | --- | --- | --- |
 | Session | `session.started`, `session.waiting`, `session.completed`, `session.failed` | Session creation, readiness, and task completion |
-| Input | `message.received` | A user message was accepted |
+| Input | `message.received`, `nudge.delivered` | A user message was accepted as a turn's prompt, or reached a running turn mid-turn. Both name the [sends they carry](#track-which-follow-up-reached-the-agent) |
 | Turn | `turn.queued`, `turn.started`, `turn.completed`, `turn.failed` | Queue position under a [`maxRunningTurns` cap](./agent-config.md#concurrency), then turn status, final result, and token usage |
 | Steps | `step.started`, `step.completed` | Model step boundaries and duration |
 | Reasoning | `reasoning.appended`, `reasoning.completed` | Streamed reasoning blocks |

package/docs/reference/tools.md

@@ -71,6 +71,7 @@ export default defineTool({
 | --- | --- |
 | `ctx.toolCallId` | The call id, matching the `actions.requested` / `action.result` stream events |
 | `ctx.session` | Read-only session info: id, channel, mode, auth |
+| `ctx.approvedBy` | For a `needsApproval` tool, the auth of whoever approved this call, in the same shape as `ctx.session.auth`. On Slack, `attributes.user_id` is the person who clicked Approve, who can differ from the person who started the thread. Unset when the call needed no approval |
 | `ctx.workspaceDir` | The session's workspace directory |
 | `ctx.stateRoot` | The agent's durable state root, shared across every session |
 | `ctx.host` | Shared host services (see below) |
@@ -81,9 +82,9 @@ export default defineTool({
 `ctx.host` carries the shared host services: `host.mcp` (authored MCP
 connections: `names()`, `listTools(name)`, `callTool(name, tool, args)`),
 `host.github` and `host.slack` (shared platform clients), `host.kv` and
-`host.files` (durable storage), `host.otel` (custom
-metrics and session tags; see [OpenTelemetry](../guides/opentelemetry.md)),
-`host.reminders` (per-session wakes, when attached).
+`host.files` (durable storage), and `host.reminders` (per-session wakes,
+when attached). Custom metrics use the
+[OpenTelemetry](../guides/opentelemetry.md) API.
 
 ### Return values