Achievements tab fails to render when token reporting is disabled

[notsalate]

Description

Summary

In the Level Up section, the Achievements tab fails to render when token reporting is temporarily disabled.

Other Level Up tabs render normally. The problem appears specifically when opening Achievements.

AI Engineer Coach: Reload Data succeeds. The parser and analyzer complete normally, so the issue appears to be in the Achievements render path, not in log parsing.

This reproduces both on my previously installed VSIX and on a fresh VSIX built from the latest main branch.

Actual behavior

When opening the Achievements tab, the UI shows:

Failed to render Level Up
Token reporting is temporarily disabled

After rebuilding from the latest main, the DevTools console shows:

app.js:14563 Uncaught (in promise) Error: Token reporting is temporarily disabled
    at app.js:14563:18

Before rebuilding from latest main, the same error appeared at a nearby generated bundle location:

app.js:14561 Uncaught (in promise) Error: Token reporting is temporarily disabled

Reload Data succeeds

The extension logs show that parsing and analyzer construction complete successfully:

parse-complete | sessions=242 workspaces=180
analyzer-built
data-ready-sent
warmUp-done

Filters tested

The issue reproduces with both:

Workspace: Current / Harness: Codex
Workspace: All / Harness: All Harnesses

Other tabs and sections

The following Level Up tabs render normally:

• Learning
• SDLC
• Share

The following dashboard sections also continue to work:

• Dashboard
• Timeline
• Coding Moments
• Output
• Patterns
• Anti-Patterns
• Skill Finder
• Context Health

Notes

The error looks like an unhandled disabled-state for token reporting. Since token reporting is intentionally disabled, the Achievements tab probably needs to catch this condition and render a fallback instead of throwing an uncaught promise rejection.

Steps to Reproduce

1. Build and install the extension from the latest main branch:

   git clone https://github.com/microsoft/ai-engineering-coach.git
   cd ai-engineering-coach
   npm ci
   npm run package
   code --install-extension (Get-ChildItem . -Filter 'ai-engineer-coach-*.vsix' | Select-Object -First 1).FullName

2. Reload VS Code.

3. Open AI Engineer Coach.

4. Confirm that the dashboard shows the token reporting notice:

   Token Usage & Burndown temporarily hidden
   These features are disabled until we can verify that reported numbers align with GitHub's billing data.
   

5. Open Level Up.

6. Open the Achievements tab.

7. Run AI Engineer Coach: Reload Data.

8. Reopen Level Up → Achievements.

Expected Behavior

The Achievements tab should render without token-dependent data, or show a graceful disabled-state fallback when token reporting is unavailable.

For example: Achievements are temporarily unavailable because token reporting is disabled.

The tab should not fail with a render error.

Extension Version

0.1.0, latest main built from source on 2026-06-22

VS Code Version

1.125.1

Operating System

Windows 11

[github-actions]

🎯 Triage report

This is a well-scoped bug report for a reproducible render failure in the Level Up → Achievements tab when token reporting is disabled. The report already narrows impact well: parsing/reload succeeds, other Level Up tabs still render, and the failure appears to come from the Achievements-specific RPC/render path.

📊 Assessment

Dimension	Value	Reasoning
Type	Bug	Clear regression/incorrect behavior with reproducible steps, expected vs actual behavior, and environment details.
Labels	bug	Existing label already matches; no additional repository label is clearly supported by the issue content.
Severity	Medium	A visible product feature is broken, but scope appears limited to the Achievements tab while the rest of the extension and other Level Up tabs continue to work.
Coding agent	Suitable	Repro is explicit, likely scope is localized, and success criteria are concrete: Achievements should render or show a graceful disabled state when token reporting is unavailable.

🔗 Similar issues

• fix: burndown e2e tests broken — stale assertions + missing feature-flag skip #109 (related) — also tracks behavior that broke when token-reporting feature flags were off; not a duplicate, but relevant because it shows another area that needed explicit disabled-state handling.

💡 Notes and suggestions

From the current code, the likely fault line is in the Achievements render path rather than the parser/analyzer path:

• src/webview/page-achievements.ts calls several RPCs via rpcAllSettled(...), but later makes direct awaited RPC calls including getConsumption.
• src/webview/panel-rpc.ts returns errorResult('Token reporting is temporarily disabled') for getConsumption when FF_TOKEN_REPORTING_ENABLED is false.
• That combination is consistent with the uncaught promise rejection reported here if Achievements does not treat disabled token reporting as an expected state.

Maintainer debugging path:

1. Reproduce with FF_TOKEN_REPORTING_ENABLED = false and open Level Up → Achievements.
2. Inspect the direct RPCs after the initial rpcAllSettled(...) block in renderAchievements.
3. Decide whether token-dependent achievements should be omitted, zeroed, or replaced by a disabled-state message when token reporting is unavailable.
4. Add a regression test for Achievements with token reporting disabled so this state is covered alongside other feature-flag-off flows.

A likely implementation shape is to make token-dependent data fetches in Achievements use the same tolerant pattern as the earlier settled RPC batch, or to gate those calls entirely and render a fallback for achievements that depend on consumption/token data.

Generated by Agentic Triage for issue #155 · 50.5 AIC · ⌖ 14.3 AIC · ⊞ 22.4K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@df35cf29fb856d1c3b8f023ed46d19126e7813bf

[notsalate]

I tested a local fix and it resolves the issue for me.

After patching src/webview/page-achievements.ts, rebuilding the VSIX, installing it with --force, and reloading VS Code, Level Up → Achievements renders successfully when token reporting is disabled.

The local fix was:

• handle the expected Token reporting is temporarily disabled error from the getConsumption RPC
• fall back to an empty modelTotals object
• mark the token-dependent Model Explorer achievement as unavailable instead of crashing the tab
• rethrow unexpected getConsumption errors

Observed after the patch:

• Achievements renders successfully
• the other Level Up tabs still render normally
• no uncaught Token reporting is temporarily disabled error appears in DevTools
• Model Explorer shows Token reporting disabled

I can share the exact diff if this direction looks acceptable.