Answer: Applications can subscribe to session events to update UI when the soft cap changes or the session reaches the exhausted-budget flow. Relevant event types include session.session_limits_changed, session.usage_checkpoint, session_limits_exhausted.requested, and session_limits_exhausted.completed. Status: Confirmed Entry: tool/github-copilot/pricing-and-limits/observe-budget-events Revision: 3 Digest: sha256:4ddbc9a7fad48a39 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:28:13Z Last changed: 2026-11-18T13:03:43Z (Event type 4: — → session_limits_ exhausted.completed) Last verified: 2026-11-20T13:08:35Z Next check: 2026-11-21T13:08:35Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of How to observe | subscribe to session events | [1] | 2026-11-20 Event type 1 | session.session_limits_ changed | [1] | 2026-11-20 Event type 2 | session.usage_checkpoint | [1] | 2026-11-20 Event type 3 | session_limits_ exhausted.requested | [1] | 2026-11-20 Event type 4 | session_limits_ exhausted.completed | [1] | 2026-11-20 SDK guidance | Use the generated event types for the SDK language you are using. | [1] | 2026-11-20 Sources: [1] GitHub. "Session limits - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-sdk/features/session-limits Role: primary. Accessed: 2026-11-20T13:08:35Z Quote: "Applications can subscribe to session events to update UI when the soft cap changes or the session reaches the exhausted-budget flow." (Supports: How to observe) Quote: "session.session_limits_ changed Active session limits changed." (Supports: Event type 1) Quote: "session.usage_checkpoint The runtime records durable aggregate usage for resume and accounting." (Supports: Event type 2) Quote: "session_limits_ exhausted.requested The session reached the exhausted-budget flow and needs a user decision before continuing." (Supports: Event type 3) Quote: "session_limits_ exhausted.completed The exhausted-limit prompt was resolved." (Supports: Event type 4) Quote: "Use the generated event types for the SDK language you are using." (Supports: SDK guidance) Snapshot SHA-256: 0b8f36acd4a302f3bfd50d4888498d26856ef92088a5318a39ea280908a871e3 (captured 2026-11-18T13:03:42Z) 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-18T13:03:43Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:08:35Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:08:35Z Last attempt: 2026-11-20T13:08:35Z Notes and limitations: Extracted automatically from a single official source (section "Observe budget events"). Related: https://latestn.com/tool/github-copilot/pricing-and-limits/optimize-budget-configuration How do I optimize my GitHub Copilot budget configuration? https://latestn.com/tool/github-copilot/pricing-and-limits/optimize-premium-request-usage How can I optimize my GitHub Copilot premium request usage? https://latestn.com/tool/github-copilot/pricing-and-limits/personal-mcp-server-limitations What are the limitations of personal MCP servers in GitHub Copilot? https://latestn.com/tool/github-copilot/pricing-and-limits/monitor-usage-entitlements How do I monitor my GitHub Copilot usage and entitlements? https://latestn.com/tool/github-copilot/pricing-and-limits/monthly-allowance-reset When does the included monthly GitHub Copilot allowance reset for personal accounts? https://latestn.com/tool/github-copilot/pricing-and-limits/monthly-premium-request-allowance How does GitHub Copilot measure premium request usage against my monthly allowance? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:03:43Z | changed | Event type 4: — → session_limits_ exhausted.completed | [1] 2026-11-18T13:03:43Z | changed | Event type 3: — → session_limits_ exhausted.requested | [1] 2026-11-18T13:03:43Z | changed | Event type 2: — → session.usage_checkpoint | [1] 2026-11-18T13:03:43Z | changed | Event type 1: — → session.session_limits_ changed | [1] 2026-11-18T13:03:43Z | changed | How to observe: — → subscribe to session events | [1] 2026-11-18T13:03:43Z | changed | usage checkpoint event: session.usage_checkpoint → — | [1] 2026-11-18T13:03:43Z | changed | event type for exhausted completed: session_limits_ exhausted.completed → — | [1] 2026-11-18T13:03:43Z | changed | event type for exhausted request: session_limits_ exhausted.requested → — | [1] 2026-11-18T13:03:43Z | changed | event type for changed limits: session.session_limits_ changed → — | [1] 2026-11-18T13:03:43Z | changed | method: subscribe to session events → — | [1] 2026-11-16T12:52:32Z | changed | SDK guidance: — → Use the generated event types for the SDK language you are using. | [1] 2026-11-16T12:52:32Z | changed | usage checkpoint event: — → session.usage_checkpoint | [1] 2026-11-16T12:52:32Z | changed | event type for exhausted completed: — → session_limits_ exhausted.completed | [1] 2026-11-16T12:52:32Z | changed | event type for exhausted request: — → session_limits_ exhausted.requested | [1] 2026-11-16T12:52:32Z | changed | event type for changed limits: — → session.session_limits_ changed | [1] 2026-11-16T12:52:32Z | changed | language guidance: Use the generated event types for the SDK language you are using. → — | [1] 2026-11-16T12:52:32Z | changed | event type 4: session_limits_ exhausted.completed → — | [1] 2026-11-16T12:52:32Z | changed | event type 3: session_limits_ exhausted.requested → — | [1] 2026-11-16T12:52:32Z | changed | event type 2: session.usage_checkpoint → — | [1] 2026-11-16T12:52:32Z | changed | event type 1: session.session_limits_ changed → — | [1] 2026-11-13T03:28:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/pricing-and-limits/observe-budget-events/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/github-copilot/pricing-and-limits/observe-budget-events POST: https://latestn.com/dispute/tool/github-copilot/pricing-and-limits/observe-budget-events with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/pricing-and-limits/observe-budget-events?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I observe budget events for GitHub Copilot SDK session limits? Revision 3, last verified 2026-11-20T13:08:35Z. https://latestn.com/tool/github-copilot/pricing-and-limits/observe-budget-events (accessed 2026-11-21T10:02:22Z). @misc{LatestN_tool_github_copilot_pricing_and_limits_observe_budget_events_r3, title = {How do I observe budget events for GitHub Copilot SDK session limits?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/pricing-and-limits/observe-budget-events}}, note = {Revision 3; digest sha256:4ddbc9a7fad48a39; last verified 2026-11-20T13:08:35Z; accessed 2026-11-21T10:02:22Z} } 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/github-copilot/pricing-and-limits/observe-budget-events