Fix spurious check_token_telemetry failure in Smoke Cursor workflow by Copilot · Pull Request #57313 · github/gh-aw

Copilot · 2026-08-31T01:19:45Z

The check_token_telemetry job in the Smoke Cursor workflow was failing on every run because token_usage.jsonl was always empty for Cursor.

Root cause: the Cursor engine calls its own API (api2.cursor.sh) directly rather than through gh-aw's universal LLM provider proxy, so it never produces token_usage.jsonl. The telemetry check assumes proxy-routed engines and was misapplied here.
Fix: removed the shared/token-telemetry-check.md import from smoke-cursor.md, aligning it with shared/aider.md and other direct-API engines that already omit this check for the same reason.
Regenerated smoke-cursor.lock.yml via gh aw compile, which drops the now-unneeded check_token_telemetry job.

Fixes [aw] Failed jobs: Smoke Cursor #57302

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

pelikhan · 2026-08-31T01:48:43Z

@copilot reconfigure cursor.md to
Go through api-proxy

Copilot · 2026-08-31T01:59:31Z

@copilot reconfigure cursor.md to
Go through api-proxy

Looked into this before making further changes: cursor-agent (the underlying CLI) has no supported way to redirect its API calls to a custom/local base URL — it always talks directly to Cursor's own backend (api2.cursor.sh) using CURSOR_API_KEY, unlike the openai-compat CLIs (crush, deepseek-harness, aider, etc.) that discover an AWF endpoint via /reflect and point their own provider config at it.

Separately, even if cursor-agent could be redirected, the AWF api-proxy's /reflect and token-usage parsing (actions/setup/js/awf_reflect.cjs) currently only understands the github/openai/anthropic protocols — there's no Cursor-specific request/response parser.

So routing Cursor through api-proxy isn't achievable from cursor.md alone; it would need upstream support in both cursor-agent (custom endpoint) and the github/gh-aw-firewall api-proxy (Cursor protocol parsing). Given that, I've kept the fix as removing the token-telemetry-check import for now (matching the fact that this check is only valid for proxy-routed engines). Happy to file a follow-up issue against gh-aw-firewall if you'd like to track adding Cursor protocol support there.

github-actions · 2026-08-31T04:56:46Z

Great work, @Copilot! 🎉 This fix correctly addresses the root cause of the spurious check_token_telemetry failures in the Smoke Cursor workflow. The analysis is clear: Cursor's direct API routing bypasses the LLM provider proxy, so the telemetry check does not apply—just like with Aider and other direct-API engines.

The changes are focused and well-explained:

Removed the misapplied telemetry import from smoke-cursor.md
Regenerated smoke-cursor.lock.yml via gh aw compile
Aligned with the existing pattern used by similar engines

The PR looks ready for review and merge. Nice alignment with the project's workflow patterns!

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

github.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "github.com"

See Network Configuration for more information.

Generated by ✅ Contribution Check · copilot · auto · 39.6 AIC · ⌖ 7.36 AIC · ⊞ 9.3K · ◷

github-actions · 2026-08-31T06:56:44Z

Category: bug | Risk: medium | Score: 46/100 (impact 16/50, urgency 14/30, quality 16/20) | Action: defer | Batch: workflow-automation

Generated by 🔧 PR Triage Agent · copilot · mai10 · 35.4 AIC · ⌖ 2.7 AIC · ⊞ 15.2K · ◷

github-actions · 2026-08-31T06:56:48Z

Category: bug | Risk: medium | Score: 46/100 (impact 16/50, urgency 14/30, quality 16/20) | Action: defer | Batch: workflow-automation

Generated by 🔧 PR Triage Agent · copilot · mai10 · 35.4 AIC · ⌖ 2.7 AIC · ⊞ 15.2K · ◷

github-actions · 2026-09-01T12:43:53Z

Category: bug | Risk: medium | Score: 61/100 (impact 28/50, urgency 18/30, quality 15/20) | Action: fast_track | Batch: workflow-reliability

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

api.github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"

See Network Configuration for more information.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 26.5 AIC · ⌖ 2.65 AIC · ⊞ 15.2K · ◷

github-actions · 2026-09-01T12:44:08Z

Category: bug | Risk: medium | Score: 61/100 (impact 28/50, urgency 18/30, quality 15/20) | Action: fast_track | Batch: workflow-reliability

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

api.github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"

See Network Configuration for more information.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 26.5 AIC · ⌖ 2.65 AIC · ⊞ 15.2K · ◷

github-actions · 2026-09-01T18:39:58Z

Category: bug | Risk: medium | Score: 70 (impact 34/50, urgency 24/30, quality 12/20) | Action: fast_track | Batch: workflow-automation. Small workflow fix for repeated smoke-cursor failures; prioritize it because it directly affects CI reliability.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

api.github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"

See Network Configuration for more information.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 30.3 AIC · ⌖ 2.88 AIC · ⊞ 15.1K · ◷

github-actions · 2026-09-02T01:05:43Z

Generated by 🔧 PR Triage Agent · copilot · mai10 · 14.9 AIC · ⌖ 2.53 AIC · ⊞ 16.1K · ◷

github-actions · 2026-09-02T12:46:08Z

Category: bug | Risk: medium | Score: 52 (impact 20 + urgency 18 + quality 14) | Action: batch_review | Batch: workflow-automation. Workflow reliability fix with a clear root cause and successful CI.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 21.9 AIC · ⌖ 2.63 AIC · ⊞ 16.1K · ◷

github-actions · 2026-09-02T18:36:53Z

Category: bug
Risk: medium
Score: 64/100 (impact 36 + urgency 20 + quality 8)
Action: fast_track
Reason: Real workflow-reliability bug affecting Smoke Cursor; prioritize for human review despite draft status.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

api.github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"

See Network Configuration for more information.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 14.7 AIC · ⌖ 2.49 AIC · ⊞ 15.1K · ◷

github-actions · 2026-09-03T06:47:22Z

Category: bug | Risk: medium | Score: 66/100 (impact 30/50, urgency 22/30, quality 14/20)
Recommended action: fast_track | Batch: workflow-reliability
Note: Fixes a flaky workflow failure in a smoke test path; CI is passing.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 16.9 AIC · ⌖ 2.56 AIC · ⊞ 16.1K · ◷

github-actions · 2026-09-03T18:42:49Z

Category: bug | Risk: medium | Score: 61 | Action: fast_track | Batch: awf-runtime

Note: Workflow failure was active and fix is small and targeted.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 24.3 AIC · ⌖ 2.54 AIC · ⊞ 16.1K · ◷

github-actions · 2026-09-04T01:04:31Z

Workflow false-positive fix; good candidate for grouped review.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 21.1 AIC · ⌖ 2.54 AIC · ⊞ 16.1K · ◷

github-actions · 2026-09-04T12:44:44Z

Category: bug | Risk: medium | Score: 58 (impact 32 + urgency 15 + quality 11) | Action: fast_track | Batch: none

Generated by 🔧 PR Triage Agent · copilot · mai10 · 22.2 AIC · ⌖ 2.85 AIC · ⊞ 15.1K · ◷

github-actions · 2026-09-04T12:45:14Z

Category: bug | Risk: medium | Score: 58 (impact 32 + urgency 15 + quality 11) | Action: fast_track | Batch: none

Generated by 🔧 PR Triage Agent · copilot · mai10 · 22.2 AIC · ⌖ 2.85 AIC · ⊞ 15.1K · ◷

github-actions · 2026-09-04T18:37:39Z

Category: bug | Risk: medium | Score: 51 (impact 24 urgency 18 quality 9) | Action: batch_review | Batch: workflow-reliability

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

api.github.com

[!TIP]
api.github.com is blocked because GitHub API access uses the built-in GitHub tools by default. Instead of adding api.github.com to network.allowed, use tools.github.mode: gh-proxy for direct pre-authenticated GitHub CLI access without requiring network access to api.github.com:

tools:
  github:
    mode: gh-proxy

See GitHub Tools for more information on gh-proxy mode.

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.github.com"

See Network Configuration for more information.

Generated by 🔧 PR Triage Agent · copilot · mai10 · 25.2 AIC · ⌖ 2.93 AIC · ⊞ 15.1K · ◷

github-actions · 2026-09-05T01:05:23Z

Generated by 🔧 PR Triage Agent · copilot · mai10 · 24 AIC · ⌖ 2.63 AIC · ⊞ 15.1K · ◷

Initial plan

a68d391

Copilot AI assigned Copilot and pelikhan Aug 31, 2026

Copilot started work on behalf of pelikhan August 31, 2026 01:19 View session

Copilot AI linked an issue Aug 31, 2026 that may be closed by this pull request

[aw] Failed jobs: Smoke Cursor #57302

Open

Remove token-telemetry-check import from smoke-cursor.md

33cc195

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Fix failed jobs in Smoke Cursor workflow~~ Fix spurious check_token_telemetry failure in Smoke Cursor workflow Aug 31, 2026

Copilot finished work on behalf of pelikhan August 31, 2026 01:26

Copilot AI requested a review from pelikhan August 31, 2026 01:26

Copilot started work on behalf of pelikhan August 31, 2026 01:48 View session

Copilot finished work on behalf of pelikhan August 31, 2026 02:00

pelikhan added the awf label Aug 31, 2026

This was referenced Aug 31, 2026

[Contribution Check Report] Contribution Check — 2026-08-31 #57314

Closed

[pr-review] Daily PR Code Quality Review — 33361572817 #57364

Closed

github-actions Bot added pr-action:defer pr-agent:copilot pr-batch:workflow-automation pr-priority:medium pr-risk:medium pr-type:bug labels Aug 31, 2026

github-actions Bot mentioned this pull request Aug 31, 2026

[PR Triage Report] PR triage report for Copilot-authored PRs #57369

Closed

github-actions Bot added the bug Something isn't working label Aug 31, 2026

github-actions Bot mentioned this pull request Aug 31, 2026

[PR Triage Report] PR Triage Report: 2026-08-31 #57305

Closed

pelikhan mentioned this pull request Aug 31, 2026

Unknown how to setup new LLM provider github/gh-aw-firewall#7900

Closed

Copilot AI mentioned this pull request Aug 31, 2026

Add add-llm-provider skill for onboarding new LLM providers/engines github/gh-aw-firewall#7903

Merged

github-actions Bot mentioned this pull request Sep 1, 2026

[PR Triage Report] PR triage report for Copilot-authored PRs #57633

Closed

github-actions Bot added pr-batch:workflow-reliability pr-priority:high labels Sep 1, 2026

github-actions Bot mentioned this pull request Sep 1, 2026

[PR Triage Report] PR triage report - 2026-09-01 #57699

Closed

github-actions Bot added the pr-type:test label Sep 1, 2026

github-actions Bot mentioned this pull request Sep 1, 2026

[PR Triage Report] PR triage report 2026-09-01 #57750

Closed

github-actions Bot added the pr-action:batch_review label Sep 2, 2026

github-actions Bot mentioned this pull request Sep 2, 2026

[PR Triage Report] PR triage report: 6 eligible Copilot PRs #57805

Closed

github-actions Bot mentioned this pull request Sep 2, 2026

[PR Triage Report] PR triage report for Copilot-authored PRs #57939

Closed

github-actions Bot mentioned this pull request Sep 2, 2026

[PR Triage Report] PR triage report - 2026-09-02 #58000

Closed

github-actions Bot mentioned this pull request Sep 3, 2026

[PR Triage Report] PR triage report: Copilot-authored PRs for 2026-09-03 #58178

Closed

github-actions Bot added the pr-batch:awf-runtime label Sep 3, 2026

github-actions Bot mentioned this pull request Sep 3, 2026

[PR Triage Report] PR triage report: 2026-09-03 Copilot PRs #58287

Closed

github-actions Bot mentioned this pull request Sep 4, 2026

[PR Triage Report] PR triage report - 2026-09-04 #58347

Closed

github-actions Bot mentioned this pull request Sep 4, 2026

[PR Triage Report] PR triage report 2026-09-04 #58487

Closed

github-actions Bot mentioned this pull request Sep 4, 2026

[PR Triage Report] PR triage report: Copilot PRs for 2026-09-04 #58581

Closed

github-actions Bot mentioned this pull request Sep 5, 2026

[PR Triage Report] PR triage report 2026-09-05 #58681

Open

Uh oh!

Conversation

Copilot AI commented Aug 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pelikhan commented Aug 31, 2026

Uh oh!

Copilot AI commented Aug 31, 2026

Uh oh!

github-actions Bot commented Aug 31, 2026

Uh oh!

github-actions Bot commented Aug 31, 2026

Uh oh!

github-actions Bot commented Aug 31, 2026

Uh oh!

github-actions Bot commented Sep 1, 2026

Uh oh!

github-actions Bot commented Sep 1, 2026

Uh oh!

github-actions Bot commented Sep 1, 2026

Uh oh!

github-actions Bot commented Sep 2, 2026

Uh oh!

github-actions Bot commented Sep 2, 2026

Uh oh!

github-actions Bot commented Sep 2, 2026

Uh oh!

github-actions Bot commented Sep 3, 2026

Uh oh!

github-actions Bot commented Sep 3, 2026

Uh oh!

github-actions Bot commented Sep 4, 2026

Uh oh!

github-actions Bot commented Sep 4, 2026

Uh oh!

github-actions Bot commented Sep 4, 2026

Uh oh!

github-actions Bot commented Sep 4, 2026

Uh oh!

github-actions Bot commented Sep 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Aug 31, 2026 •

edited

Loading