# Clearer refusals for agent tokens, console sign-in and uploads

6 November 2026. Agent tokens your app declines, refused console sign-ins and oversized files now say why. A notification email can also leave its unsubscribe group.

## Added

- **Email:** A notification email template can now leave its unsubscribe group. It is then sent as transactional mail: no opt-out stops it, and it carries no one-click unsubscribe header.
- **API:** To do it, send unsubscribeGroupId as null to PATCH /api/emails/templates/:id. System templates and templates of other categories keep their group.

## Improved

- **Agents:** When your app server declines to issue a token to an AI agent or another app, they now learn why. The token endpoint answers 400 invalid_grant, with your message as error_description, up to 300 characters.
- **Agents:** Before, every refusal read as 503 temporarily_unavailable, which said to try again later. An app server that cannot be reached still answers 503.
- **Console:** The console's sign-up page is now a real Create your account screen, built from the sign-in card. Before, it sent you straight on to sign in.
- **Console:** A refused console sign-in now says why and what to do next. For example, it asks you to verify your email address first, or offers Contact support for a blocked account.
- **Console:** While the console's sign-in options load, one placeholder shows, so buttons no longer appear one after another. If they fail to load, Try again fetches them in place.

## Fixed

- **Assets:** Three more size refusals now state their limit in exact bytes and carry maxBytes. They cover a file sent inline as a data: URI over 16,384 bytes (INLINE_FILE_TOO_LARGE), a collection record's file over its field's limit, and a file over your plan's per-file limit. Their status codes and error codes are unchanged.

Source: https://www.buildbase.app/changelog/clearer-refusals-for-agent-tokens-console-sign-in-and-uploads
