Answer: Add both the onIncident and onNote handlers to the same pagerdutyChannel() call so follow-up events reach the session already working on the incident. Status: Confirmed Entry: tool/cursor/integrations/pagerduty-single-session Revision: 1 Digest: sha256:cacad66c6c477b1c (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:38Z Last changed: 2026-11-13T03:08:38Z Last verified: 2026-11-20T12:33:14Z Next check: 2026-11-21T12:33:14Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of second handler | onNote | [1] | 2026-11-20 follow-up event types | incident.acknowledged | [1] | 2026-11-20 re-trigger behavior | A re-trigger after a resolve is a new PagerDuty incident, so it starts a new session. | [1] | 2026-11-20 dedup key field | ctx.incidentKey | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/guides/pagerduty.md". https://cursor.com/docs/agent-sdk/guides/pagerduty.md Role: primary. Accessed: 2026-11-20T12:33:14Z Quote: "onNote: (ctx, note) => {" (Supports: second handler) Quote: "const followUps = ["incident.acknowledged", "incident.reassigned", "incident.resolved"];" (Supports: follow-up event types) Quote: "A re-trigger after a resolve is a new PagerDuty incident, so it starts a new session." (Supports: re-trigger behavior) Quote: "`ctx.incidentKey` carries the alert's dedup key" (Supports: dedup key field) Snapshot SHA-256: a8324048a6d3f153209e51280e3901c4004417edc079bb4feb54def7305f4310 (captured 2026-11-13T03:08:38Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:08:38Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:33:14Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:33:14Z Last attempt: 2026-11-20T12:33:14Z Notes and limitations: Extracted automatically from a single official source (section "Follow the incident in one session"). Related: https://latestn.com/tool/cursor/integrations/prebuilt-channels What prebuilt channels does Cursor's Agent SDK provide? https://latestn.com/tool/cursor/integrations/publish-origin-app-to-marketplace How do I make my Cursor Origin app public and submit it to the App Marketplace? https://latestn.com/tool/cursor/integrations/reconnect-mcp-connections How do I reconnect account-backed MCP server actions after converting a Cursor Automation? https://latestn.com/tool/cursor/integrations/pagerduty-deliver-replies How do I make a Cursor PagerDuty agent post its replies as notes on the incident? https://latestn.com/tool/cursor/integrations/pagerduty-ignore-own-actions How do I stop a Cursor PagerDuty agent from reacting to its own actions? https://latestn.com/tool/cursor/integrations/pagerduty-investigate-new-incident How do I set up a Cursor agent to investigate new PagerDuty incidents? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:38Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/integrations/pagerduty-single-session/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-single-session POST: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-single-session with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-single-session?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I keep a Cursor PagerDuty agent following the same incident in one session? Revision 1, last verified 2026-11-20T12:33:14Z. https://latestn.com/tool/cursor/integrations/pagerduty-single-session (accessed 2026-11-21T10:00:20Z). @misc{LatestN_tool_cursor_integrations_pagerduty_single_session_r1, title = {How do I keep a Cursor PagerDuty agent following the same incident in one session?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/integrations/pagerduty-single-session}}, note = {Revision 1; digest sha256:cacad66c6c477b1c; last verified 2026-11-20T12:33:14Z; accessed 2026-11-21T10:00:20Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/integrations/pagerduty-single-session