> For the complete documentation index, see [llms.txt](https://docs.atlas.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atlas.design/atlas-ai-studio-overview/release-notes/release-0.43.0.md).

# Release 0.43.0

Previous Version: **v0.42.0**

Connect AI tools through browser sign-in, unwrap meshes with Tripo Smart UV, preview asset rebuilds, and arrange selections from the canvas toolbar. This release also improves node search, recovery from eligible generation failures, assistant progress, and workspace plan offers. Available nodes and options depend on account and workspace access.

## Connect AI tools through browser sign-in

Where enabled, connect an MCP client by adding the Atlas server URL, signing in, choosing a workspace, and approving access. You no longer need to copy a workspace API key for that connection.

* **MCP** has its own sidebar entry, with setup guidance for Claude Code, Claude desktop/web, Cursor, VS Code, Codex, and ChatGPT. Where browser authorization is unavailable, the page provides workspace API-key setup guidance.
* Choose a maximum of **250, 500, 1,000, 2,500, or 5,000 credits per agent call**. The default is **1,000**. Each OAuth call receives its own allowance for agent work, node executions, and continuations, including work that finishes later. A call may request a smaller allowance; a later call cannot top up an earlier one.
* Workspace members can inspect connected tools, who approved them, their approval date and recent activity, credit cap, and reapproval date. The approving person or a workspace owner/admin can disconnect a tool, immediately blocking subsequent calls and downloads. Work already running may finish.
* Connections use the approving person's existing permissions and last **90 days**. The client must then be approved again; a newly issued credential replaces the previous connection. Sign-in and email verification preserve a pending approval.

The credit cap applies to each agent call, rather than the lifetime of a connection. Existing workspace API keys continue to work. Browser-authorized connections are for MCP; scripts and exported API execution still use workspace API keys.

![The MCP workspace page provides one server URL for your tools. This example uses the development environment.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FjAb6R1j4hmt5NxhPmzhw%2Fmcp-connect-tools.jpg?alt=media)

![Setup guidance for Claude Code, Cursor, VS Code, Claude desktop/web, Codex, and ChatGPT.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FjYcb805QzeRLrDxsT8n4%2Fmcp-more-clients.jpg?alt=media)

![Approve the requested workspace access and set a maximum credit allowance for each MCP agent call. The workspace name is blurred.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2Ftx6M1oHEkNN8RHX56zfZ%2Fmcp-oauth-consent.jpg?alt=media)

![Inspect connected tools, credit caps, expiry, and the Disconnect action. Personal attribution is blurred.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FWCwX2uDXgF7l83FiJjh5%2Fmcp-connected-tools.jpg?alt=media)

{% embed url="<https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FHvyqh3urNikACKiALIe4%2Fmcp-per-call-credit-cap.mp4?alt=media>" %}
Choose a per-call credit allowance before approving access. All five actual allowance settings are shown. Captured as individually rendered frames at fixed 1/30-second intervals and encoded at 30 FPS.
{% endembed %}

## Open MCP asset downloads directly

Workspace asset discovery returns private, file-specific links that can be opened directly without an Authorization header. A link can be reused for **15 minutes**.

Revoking or expiring the issuing credential, removing its owner from the workspace, or deactivating the workspace blocks further downloads even before the link expires. Existing downloads authenticated with a workspace API key in the request header remain supported.

![The Smart UV atlas preview opened directly from an MCP asset download link, without an Authorization header. The capability URL is kept out of the capture.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2F0SDNvENQCVWU5DrdwAjQ%2Fmcp-direct-asset-preview.jpg?alt=media)

## Unwrap meshes with Tripo Smart UV and Retopology v3

**UV Unfold** adds **Tripo :: Smart UV**, producing both the processed mesh and a **UV Atlas Preview** image. **Bake Textures** is enabled by default to bake existing textures onto the new layout. The Tripo option accepts GLB input up to **80,000 triangles** and **150 MiB**.

<figure><img src="https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2Fs8yqxawfJZ3oz6QDQLkQ%2Fimage.png?alt=media&amp;token=bc3358d4-7c67-4229-a81f-d226c76e33d1" alt=""><figcaption></figcaption></figure>

**Optimize Mesh → Tripo Retopology** adds **v3.0**, with **triangle or quad topology** and an optional **Smart UV** setting, off by default. New Tripo Retopology configurations select v3; v1 and v2 remain available.

Existing Tripo Retopology nodes keep their effective v2 selection and saved results. The overall default engines remain Hunyuan3D for UV Unfold and Meshy for Optimize Mesh. The editor and API/MCP-created workflows share these options.

<figure><img src="https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FEwGoVuJMoTFF1lxsNXVO%2Fimage.png?alt=media&amp;token=08e16b7d-64f4-4947-b656-7570b879f69a" alt=""><figcaption><p>Tripo model choices retain Retopology (v3), Smart (v2), and Basic (v1).</p></figcaption></figure>

<figure><img src="https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FKJ4ThR5Mpfk3XLf7PTI6%2Fimage.png?alt=media&amp;token=04eacb11-d16b-4c26-a85b-a13d433c160a" alt=""><figcaption></figcaption></figure>

## Preview what an asset rebuild will place

The asset card combines its rebuild actions into one **Rebuild** control. When multiple generation steps can be recreated, its menu offers **Rebuild node** and **Rebuild whole chain**, with node counts and a preview of the steps that will be placed and the existing files that will remain inputs. Assets with a single applicable action keep a plain Rebuild button.

The preview explains whether a missing generated input can be recreated, needs a replacement, or prevents whole-chain reconstruction. Rebuilds place nodes without running them. Availability depends on recorded generation settings, access to the source node type, and a writable project; uploaded assets remain files.

![Compare Rebuild node with Rebuild whole chain, including node counts and inputs kept as files. Rebuilt nodes stay idle until you run them.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FMqvuXd0aDNaYABA3dJkX%2Frebuild-preview.jpg?alt=media)

## Align and distribute selections from the canvas toolbar

Open **Align and distribute** in the selection toolbar to align left, center, right, top, middle, or bottom, or distribute horizontally and vertically. The menu shows shortcut hints and stays open for successive commands. Each change supports undo.

Selected frames move as complete blocks with their nodes, notes, and nested frames, including when using the existing alignment shortcuts. You can arrange loose selected nodes alongside frames. Alignment needs at least **two independent items**; distribution needs **three**. A selected frame and its contents count as one item.

The toolbar also shows blocked nodes as a compact count with an explanation on hover, alongside clearer selection counts and the existing credit estimate.

{% embed url="<https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FZIkOrwOzcAGAnMZcQlqn%2Falign-and-distribute.mp4?alt=media>" %}
Align top, distribute horizontally, then undo. Nested frames move as complete blocks. Captured at fixed intervals and encoded at 30 FPS.
{% endembed %}

## Find nodes with clearer results and keyboard controls

Node search groups results by **3D, Video, Audio, Image, Vector, Documents & data, Text, and API**, with category paths and matching synonym hints. Ranking better recognizes requests such as “image to 3d,” media synonyms, variants, and common terminology.

Use **Up/Down** to select a result and **Enter** to choose it. **Escape** or the clear button clears the query. Searches without matches show an explicit no-results message.

API input/output nodes stay out of generic media searches unless the query asks for API or endpoint functionality or directly names the node. The menu keeps a consistent screen size while zooming and fits the available viewport height.

![Search results group by media type and show variants, category paths and matching terms.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FZfhlbMGIn1hgNGYezIDx%2Fnode-search-categories.jpg?alt=media)

## Retry eligible failed image and video generations

Eligible manual generation failures show **Retry** and expandable **Details** explaining that the provider did not accept the request. Retry starts a normal new run with the current settings, subject to the usual permission, credit, and billing checks.

This action is available for recognized transient failures before submission, such as supported connection failures or rate-limit rejections. Accepted or ambiguous requests and failures with unresolved provider usage do not qualify. Editing inputs, starting another attempt, or losing execution eligibility removes the action. Repeated clicks cannot start duplicate pending retries.

Retry is a manual editor action. It does not automatically repeat failed API, scheduled, or agent runs.

## See clearer assistant execution progress

The project assistant receives the current graph structure and grouping at the start of each turn, reducing repeated discovery steps. It can start or schedule requested nodes and watch their completion in one action before continuing with the results.

Activity labels show the running or scheduled node count and the watched-node count. Existing MCP agent workflows share the orchestration improvements, with the same requirement to authorize execution.

![The assistant schedules both finishing steps, watches them together, and reports their successful results.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FVhorB2m1WP0urOWApWDJ%2Fassistant-execution-watch.jpg?alt=media)

## Find Assets and Agent at the ends of the toolbar

**Assets** moves to the far left of the editor toolbar, before the navigation path. **Agent** moves to the far right after the profile menu. Both controls have panel-specific icons and retain their existing access restrictions.

![Assets sits at the far left of the editor toolbar; Agent sits at the far right. Workspace and profile personal information is blurred.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2Fx8q3OyFkBtEUH8xD48OK%2Feditor-toolbar.jpg?alt=media)

## Inspect contextual offers for your next workspace plan

Eligible workspace owners and admins can see the next plan's offer in the credit popover, the Members invitation gate, and contextual prompts after successful generation or download activity. From an offer, inspect plans, open checkout, or confirm an eligible upgrade using the saved card.

Offers apply to eligible workspaces without an ongoing paid plan, including the zero-price card-on-file tier. Pilot and Google Cloud-billed workspaces are excluded. Prompts are frequency-limited, respect repeated dismissals, and do not interrupt a blocked-run prompt.

![Eligible workspace owners and admins see the next plan's benefits and price at the Members invitation gate.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FBstTHbX06BdTLLbhlNoE%2Fplan-offer-members.jpg?alt=media)

![The credit popover provides a contextual plan offer with links to plan details and checkout. No upgrade was purchased.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FbpI2iqsBEdf66eS6V9o4%2Fplan-offer-credits-clean.jpg?alt=media)

![A contextual offer after a successful download. The example followed two real downloads of the editor showcase asset; no billing settings were changed.](https://3654894688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR7boiMixMhR4q36Ns33Y%2Fuploads%2FjiwxJYr9J3oO23tlsVRJ%2Fplan-offer-after-download.jpg?alt=media)


---

# 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.atlas.design/atlas-ai-studio-overview/release-notes/release-0.43.0.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.
