Skip to main content
The GitHub connection now takes care of itself: renewals are coordinated, honest about their state, and can no longer talk themselves to death. Asking ADE for help also works the first time: the ade command sets itself up, a report can be sent whenever you want one, and the report finally contains the things support actually needs.

​
Your GitHub connection

  • The connection renews itself without breaking itself. Every part of ADE now renews the GitHub authorization through one coordinator. Before, parallel renewals could invalidate the credential, and ADE then retried the dead credential without pause until GitHub blocked the whole machine — which also blocked the re-authorize flow that would have fixed it.
  • The status tells the truth. A working connection whose short-lived token lapsed no longer says “Authorization expired”. A renewal that GitHub has paused says when it resumes, and does not ask you to re-authorize — that cannot help and used to make things worse. Only a truly dead authorization asks for a login.
  • ADE renewing is not an error. While ADE renews the authorization, screens say so in one calm sentence instead of reporting a failed check.
  • You can disconnect. The GitHub panel now has a Disconnect control. Removing the authorization previously had no button at all.
  • Recovery is fast. After you re-authorize, background GitHub features pick up the new authorization within seconds instead of waiting out a cooldown.

​
Updates

  • “Check for updates” works while an update is already staged. It used to do nothing.
  • A manual check no longer discards an update that was already downloaded.

​
Getting help

  • Send a report whenever you want. Settings now has a Send button next to Diagnostics sharing. Until now a report could only be sent from a screen that had already failed — so if something merely felt wrong, there was nothing to click.
  • Reports work with no project open. A report used to leave out ADE’s own log unless a project happened to be open, which is exactly the case where a report matters most.
  • Reports carry what was missing. The background service’s full output and its startup configuration are now included. Several problems left their only trace in files no report ever read.
  • A report that could not be saved no longer says it was. The message told you to open a file that was never written.

​
The ade terminal command

  • ADE sets up the ade command once, properly. It used to be re-run on every launch and could overwrite a copy you installed yourself; now it runs once, and never touches an ade you already have.

​
Fixes

  • Your provider configuration stays yours. ADE no longer overrides model provider settings you configured yourself.
  • ADE no longer freezes while a report is being prepared. On Windows and Linux, gathering a report could lock the window for a few seconds — usually for an automatic report nobody asked for.