Answer: Use `agent-sdk session list --prod --slug ` to find a hosted session, then print its events with `agent-sdk session get --prod --slug --view events`; for a local run, pass the trace path from `agent-sdk run` to `--file`. Pair each `actions.requested` event with its `action.result` to find the call that failed. Status: Confirmed Entry: tool/cursor/troubleshooting/read-session-trace Revision: 1 Digest: sha256:22c6484cff876cf3 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:09:09Z Last changed: 2026-11-13T03:09:09Z Last verified: 2026-11-20T12:34:27Z Next check: 2026-11-21T12:34:27Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of list command | agent-sdk session list --prod --slug | [1] | 2026-11-20 get events command | agent-sdk session get --prod --slug --view events | [1] | 2026-11-20 local trace command | agent-sdk session get --file | [1] | 2026-11-20 event pairing | actions.requested | [1] | 2026-11-20 result event | action.result | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/troubleshooting.md". https://cursor.com/docs/agent-sdk/troubleshooting.md Role: primary. Accessed: 2026-11-20T12:34:27Z Quote: "agent-sdk session list --prod --slug " (Supports: list command) Quote: "agent-sdk session get --prod --slug --view events" (Supports: get events command) Quote: "agent-sdk session get --file " (Supports: local trace command) Quote: "Pair each `actions.requested` event with its `action.result`" (Supports: event pairing, result event) Snapshot SHA-256: 5a0a741e37bfaa43e1240618d0614c6e8e197c4e8b6ad35ec734f8b212855d23 (captured 2026-11-13T03:09:08Z) 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:09:09Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:34:27Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:34:27Z Last attempt: 2026-11-20T12:34:27Z Notes and limitations: Extracted automatically from a single official source (section "Read the session trace"). Related: https://latestn.com/tool/cursor/troubleshooting/retry-after-503-deploy How do I retry a Cursor Agent SDK deploy that returns 503 with Retry-After? https://latestn.com/tool/cursor/troubleshooting/rule-not-applied Why isn't my Cursor rule being applied? https://latestn.com/tool/cursor/troubleshooting/scim-sync-troubleshooting Why aren't my users or groups syncing with Cursor SCIM? https://latestn.com/tool/cursor/troubleshooting/missing-voice-chat-button Why don't I see the Start voice chat button in Cursor? https://latestn.com/tool/cursor/troubleshooting/network-troubleshooting What should I check if Cursor has network connectivity issues in my enterprise? https://latestn.com/tool/cursor/troubleshooting/proxy-vpn-http-compatibility How do I fix Cursor not working behind a proxy or VPN? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:09:09Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/troubleshooting/read-session-trace/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/troubleshooting/read-session-trace POST: https://latestn.com/dispute/tool/cursor/troubleshooting/read-session-trace with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/troubleshooting/read-session-trace?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I read the session trace to debug Cursor Agent SDK issues? Revision 1, last verified 2026-11-20T12:34:27Z. https://latestn.com/tool/cursor/troubleshooting/read-session-trace (accessed 2026-11-21T09:54:14Z). @misc{LatestN_tool_cursor_troubleshooting_read_session_trace_r1, title = {How do I read the session trace to debug Cursor Agent SDK issues?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/troubleshooting/read-session-trace}}, note = {Revision 1; digest sha256:22c6484cff876cf3; last verified 2026-11-20T12:34:27Z; accessed 2026-11-21T09:54:14Z} } 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/troubleshooting/read-session-trace