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
Help users (esp. on Windows) understand why a third-party provider was not
imported, and make upstream/log diagnostics easier to collect.
Provider config errors (stage 1):
- Capture JsonError/InvalidError per global config file into a ConfigError
collector instead of letting one bad file zero out the whole global config
(orElseSucceed used to swallow it); expose via Config.getErrors().
- Add optional `errors` to Provider.ListResult + ProviderConfigError schema;
provider list handler returns them. Regenerate SDK types.
- Render config errors in Settings -> Providers -> Connected providers with a
danger tag and JSON/schema reason + message. i18n across all locales.
Upstream error logging (executor.ts):
- providerMessage now includes host + requestId + original upstream body so
relay-gateway errors (e.g. HTTP 429) are attributable at a glance.
Log export diagnostics (CLI + desktop):
- New `deepagent-code debug logs` command (--since, --out) bundling the real
log dir (~/.deepagent/code/log) for CLI/WSL/headless users.
- Fix serverLogRoots() so one-click export actually collects the real log dir
(root cause of Windows users not finding logs); parameterize the time
window and let users pick a save path. Add command-palette entries + i18n.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments