Release 0.5.4

Last updated on October 30, 2026

Overview​

AGS CLI 0.5.4 is a patch release on top of 0.5.3. Each item below is tagged with the area it affects. All items in this release affect [General].

Most scripts keep working without changes. A script that passes a client name to ags auth login --client-id now stops before the browser step, so pass the client ID instead. A script that reads the login prompts needs the new prompt texts. To upgrade from 0.5.1 or later, run ags update --install.

Highlights​

[General] Login checks the client ID before the browser opens​

ags auth login now asks IAM about the client ID before it opens the browser. Before 0.5.4, a client name or a mistyped ID went straight to the browser. The sign-in then ended on an IAM error page, while the CLI waited for two minutes.

At the Client ID prompt, if you enter an ID that IAM does not know, the CLI prints a warning and a tip. Then the prompt asks again:

! IAM has no client with ID "my-cli".
    Tip: A client ID looks like 2c7308eb4f3d48e3b892fa0794f14a9c. It is not the client name.

After three rejected answers, the command stops with No valid client ID after 3 attempts.

The CLI checks a client ID from --client-id, AGS_CLIENT_ID, or your profile the same way. If IAM does not know that ID, the command stops with an error that names where the ID came from, for example IAM has no client with ID "my-cli" (from --client-id).

The CLI also reads the client's redirect URI from IAM. If that URI cannot lead back to this login, for example because it uses another port, the CLI prints a warning and a tip before it waits for the browser.

If the CLI cannot reach IAM for the check, it prints a warning, and the login continues as before.

[General] The first command on a new machine no longer fails​

On a new machine, the first ags command could fail with No active profile, or print Waiting for file lock on profile config for 'default'… before its own output. The error also suggested ags profile create, which you did not need. Running the same command again worked.

The cause was the CLI's telemetry, which set up the default profile at the same moment as the command. Telemetry now only reads your configuration, and the command creates the profile.

Improvements​

  • [General] The Base URL prompt shows an example: Enter Base URL (e.g. https://<studio-id>-<title-id>.prod.gamingservices.accelbyte.io):. The host of the Base URL is your game's Namespace ID: your studio ID and the game's title ID, joined by a hyphen. See Install and sign in.
  • [General] The Client ID prompt shows an example ID and says that an empty answer creates a new client: Enter Client ID (e.g. 2c7308eb4f3d48e3b892fa0794f14a9c, or leave empty to create a new one):.
  • [General] After you create a new IAM client from the login prompt, the CLI asks for its ID with its own prompt: Paste the new client's Client ID:.
  • [General] Before it opens the browser, the CLI prints the client it signs in with: Signing in with IAM client <id>.
  • [General] When the Base URL is on gamingservices.xsolla.com, telemetry goes to a separate project from AccelByte's. This applies whether the Base URL comes from AGS_BASE_URL or from your profile. Telemetry for other addresses is unchanged.

Bug fixes​

  • [General] The progress line fits the terminal width. On a terminal narrower than the line, each redraw used to leave a copy of the line on the screen. The waiting line of the login is also shorter: Waiting for browser sign-in on 127.0.0.1:8080... 120s left (Ctrl-C to cancel).
  • [General] Five libraries are updated for published security advisories: rustls, rustls-webpki, webpki-roots, tokio, and zip. Certificate checks now reject chains through the distrusted emSign intermediates.

Full release notes​

See the 0.5.4 release on GitHub for the complete list of changes.

Last updated on
On this page