Answer: Set the selfUserIds option in the pagerdutyChannel configuration to the agent's own PagerDuty user ID(s), so events caused by the agent's own user are skipped. The user is resolved in order from selfUserIds, PAGERDUTY_USER_ID, or the user PAGERDUTY_TOKEN acts as. Status: Confirmed Entry: tool/cursor/integrations/pagerduty-ignore-own-actions Revision: 1 Digest: sha256:9365e8dd5e0f41c5 (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 option | selfUserIds | [1] | 2026-11-20 example user id | PBOT001 | [1] | 2026-11-20 resolution order | selfUserIds, PAGERDUTY_USER_ID | [1] | 2026-11-20 fallback env var | PAGERDUTY_USER_ID | [1] | 2026-11-20 email env var | PAGERDUTY_FROM_EMAIL | [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: "selfUserIds: ["PBOT001"]," (Supports: option, example user id) Quote: "The user comes from, in order: selfUserIds, PAGERDUTY_USER_ID," (Supports: resolution order) Quote: "A read-only agent with no token sets `PAGERDUTY_USER_ID` instead." (Supports: fallback env var) Quote: "the channel uses the user whose email matches `PAGERDUTY_FROM_EMAIL`." (Supports: email env var) 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 "Ignore your own actions"). Related: 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/cursor/integrations/pagerduty-single-session How do I keep a Cursor PagerDuty agent following the same incident in one session? https://latestn.com/tool/cursor/integrations/prebuilt-channels What prebuilt channels does Cursor's Agent SDK provide? https://latestn.com/tool/cursor/integrations/origin-mcp-transport What transport does the Cursor Origin MCP server use? https://latestn.com/tool/cursor/integrations/other-ci-systems Can I use Cursor CLI in CI systems other than GitHub Actions? 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/ 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-ignore-own-actions/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-ignore-own-actions POST: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-ignore-own-actions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/integrations/pagerduty-ignore-own-actions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I stop a Cursor PagerDuty agent from reacting to its own actions? Revision 1, last verified 2026-11-20T12:33:14Z. https://latestn.com/tool/cursor/integrations/pagerduty-ignore-own-actions (accessed 2026-11-21T10:07:58Z). @misc{LatestN_tool_cursor_integrations_pagerduty_ignore_own_actions_r1, title = {How do I stop a Cursor PagerDuty agent from reacting to its own actions?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/integrations/pagerduty-ignore-own-actions}}, note = {Revision 1; digest sha256:9365e8dd5e0f41c5; last verified 2026-11-20T12:33:14Z; accessed 2026-11-21T10:07:58Z} } 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-ignore-own-actions