You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on the latest version of the extension, or I've written my version below.
I read the README's Troubleshooting section (proxies, history retention, the AI advice feature).
What happened?
Extension wont work anymore on version 2.3.2. The status is also no longer avaliable. I even cant find where to start the UI.
The notification says "工作区专用 API 密钥无法安全迁移到单一全局 SecretStorage。请先复制并从工作区设置中移除,重新加载后在“仪表板设置 → 建议”中输入。". “Workspace-specific API keys cannot be safely migrated to a single global SecretStorage. Please copy them first, remove them from workspace settings, reload, then enter them in Dashboard Settings → Suggestions.”
Switching back to ver 2.3.0 works fine.
The configured analysis model did not return a usable analysis for this issue. The item has still been received and remains available for maintainer review.
To help with triage, please ensure the extension, VS Code, and operating-system versions plus anonymous diagnostic logs are included.
自动分析服务没有为这个问题返回可用结果。该条目已经成功收到,维护者仍可继续审阅。
为便于排查,请确认已提供扩展、VS Code、操作系统版本以及匿名诊断日志。
🤖 Posted automatically by CCU Bot — not a maintainer decision.
Thanks for the detailed report. The startup failure is caused by treating an advice API-key migration error as a fatal extension activation error. In PR #106, the usage status bar, commands, and dashboard continue to activate when a legacy workspace-scoped key cannot be migrated; AI advice remains unconfigured until the key is migrated manually.
The existing workspace key is not deleted or copied into global SecretStorage. To restore AI advice, copy the key privately, remove the legacy workspace setting, reload VS Code, and enter it under Dashboard Settings → Advice. Please do not post the key in this issue.
The fix is included in the v2.3.3 candidate and is pending PR review/merge; this issue will close when the PR merges. If the usage UI still fails in that candidate, please share the first extension-host error line with credentials and paths redacted.
Activity
github-actions commentedon Sep 14, 2026
🤖 Automated first-pass reply
The configured analysis model did not return a usable analysis for this issue. The item has still been received and remains available for maintainer review.
To help with triage, please ensure the extension, VS Code, and operating-system versions plus anonymous diagnostic logs are included.
自动分析服务没有为这个问题返回可用结果。该条目已经成功收到,维护者仍可继续审阅。
为便于排查,请确认已提供扩展、VS Code、操作系统版本以及匿名诊断日志。
🤖 Posted automatically by CCU Bot — not a maintainer decision.
Carl723000 commentedon Sep 16, 2026
Thanks for the detailed report. The startup failure is caused by treating an advice API-key migration error as a fatal extension activation error. In PR #106, the usage status bar, commands, and dashboard continue to activate when a legacy workspace-scoped key cannot be migrated; AI advice remains unconfigured until the key is migrated manually.
The existing workspace key is not deleted or copied into global SecretStorage. To restore AI advice, copy the key privately, remove the legacy workspace setting, reload VS Code, and enter it under Dashboard Settings → Advice. Please do not post the key in this issue.
The fix is included in the v2.3.3 candidate and is pending PR review/merge; this issue will close when the PR merges. If the usage UI still fails in that candidate, please share the first extension-host error line with credentials and paths redacted.
🤖 Generated with OpenAI Codex