> 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/january-12-2026.md).

# January 12

Platform Release Update

This release removes key friction points and improves reliability, significantly speeding up **app building** and enabling teams to iterate **\~6.5–7× faster**.

## **App Builder**

### **Rapid Mode (New)**

* Now there are 2 modes of building apps - Deep Thinking & Rapid.
* With Rapid mode, you can turn ideas into working prototypes and functional apps much faster.
* **Early build time reduced from 20 minutes to \~3 minutes - 85% faster.**
* What's included:
  * Currently supports frontend-only builds for rapid prototyping.
  * Backend integrations (including Supabase) are not supported yet in Rapid Mode.

### **Stability Improvements**

* Resolved recurring **502 errors**, network errors, and WebSocket connection issues.
* Reduces build interruptions by **\~80%.**

### **Improved Build Experience**

* Simplified interface with clearer build states and smoother loaders.

### **Better Version Reverts**

* Reverting an app version now restores the relevant chat context.
* Eliminates context mismatch issues and reduces rebuild recovery time.

### **Asset Handling Fixes**

* Images, logos, and other assets now update consistently across regenerated apps.

### **GitHub Management Fixes**

* Improved stability in GitHub linking and repository sync flows.
* Fewer GitHub-related disruptions during builds.

## Agent Builder

### Under-the-Hood Enhancements

* Strengthened core agent execution and reliability.
* Improves agent response consistency by **15–20%** and sets a stronger foundation for future capabilities.

> **More improvements are in progress**, with the next release bringing even more enhancements.

***

{% 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/january-12-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.