> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/release-notes/2026/february-18th-2026.md).

# February 18

Platform Release Update

This release introduces key enhancements across authentication, integrations, and app builder capabilities - enabling more secure, scalable, and production-ready applications.

## Authentication Enhancements

### Mobile & WhatsApp OTP Authentication (via Twilio)

Enable secure mobile number login with OTP verification and extend message delivery to WhatsApp using Twilio - supporting OTPs as well as other transactional user communications.

## Integrations

### Email Notifications (Resend Integration)

Enable transactional email workflows within your apps using Resend. Suitable for onboarding emails, alerts, confirmations, and system notifications.

### BYOK Experience from Chat

Enhanced Bring Your Own Key (BYOK) experience directly within the chat interface. Users can securely configure and manage integration keys during the build process.

### Integration Layer for Generated Apps

Generated applications now include a structured integration layer, allowing seamless connectivity with authentication providers, messaging services, and other external systems.

## App Builder Enhancements

### Brand Guidelines – Asset Management

Brand assets can now be uploaded and managed within Brand Guidelines to ensure consistent design implementation across generated applications.

### Improved Image Reference Handling

Enhanced application of image references to improve visual alignment and brand consistency in generated outputs.

**Happy Building!**

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/ai-workbench-qore/release-notes/2026/february-18th-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.