> 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.7.0.md).

# Release 0.7.0

Platform link: <https://app-tech.atlas.design/>

## API export changes: <a href="#api-export-changes" id="api-export-changes"></a>

* simple workflows with images will work now much faster as we skip unnecessary image captioning logic
* nodes which are not preceding output nodes are automatically removed from exported graph (with a warning message in the API creation UI)
* Fixed global cache with workflows reusing the same input file id (it didn’t cache previously always rerunning whole pipeline part dependent on the input images or meshes)
* API export/execution is backwards compatible with APIs exported using 0.6.0 release
* API export dialog improvements:
  * copy-able python code along bash and API info
  * button for only copying API id for fast replacement
  * fixed bug with not copy-able text on this dialog
  * fixed issue with api name not properly displaying in copied API info

## Optimization: <a href="#optimization" id="optimization"></a>

* Nodes which output images display results now 8-10 seconds faster, because now the new image is being captioned (for suggestions system) in the background.

## Text to origin <a href="#text-to-origin" id="text-to-origin"></a>

<figure><img src="/files/hYxDvPRtKmoEXCG3jAou" alt="" width="563"><figcaption></figcaption></figure>

New experimental node, allowing to set 3D origin in a desired location. It’s still a fresh feature and needs some improvements as failure cases are often.

## New models/algorithms: <a href="#new-models-algorithms" id="new-models-algorithms"></a>

* “Tile 4x” backend for upscale node - good for photos, upscales 4x without limitation, e.g. image can be 2048x2048 → will be 8192x8192. Not recommended for super high resolutions, may have some tiling artifacts
* “CGI” backend for upscale node - good for cgi, digital art, render images. Not good for photos.
  * `Maximum upscale for CGI is 3840x2160 (not applicable to a 9:16, e.g. 9:16 will be 1680x2160)`

## Automatic mesh frontalization: <a href="#automatic-mesh-frontalization" id="automatic-mesh-frontalization"></a>

<figure><img src="/files/MUGoTOqf14Q0GZRddzXT" alt="" width="480"><figcaption></figcaption></figure>

Auto transform has now 3 input booleans, previously it behaved like with only first 2 enabled always.

## Simple node arrangement: <a href="#simple-node-arrangement" id="simple-node-arrangement"></a>

* Add a simple automatic node placement cleanup, rearranging nodes to remove overlaps between them. There are 3 buttons, each is corresponding to different “strength”/ how much nodes are being moved from their initial positions.

  <figure><img src="/files/SwIPyJzYIM5Yfw4ivr9U" alt="" width="156"><figcaption></figcaption></figure>

## Other changes/fixes <a href="#other-changes-fixes" id="other-changes-fixes"></a>

* fixed project “Save and Edit” feature (issue with copied project being empty)
* added “other irrelevant text” output (as a 3rd one) for Document text extraction node
* added new simple “Math Expression” node
* fixed issue with pasting nodes pasting duplicates
* fixed issue about run button for node with required text input not updating after just typing text (required defocus)
* improved the node run button locked behavior when typing prompt
* fixed copy-paste issues

## UI changes: <a href="#ui-changes" id="ui-changes"></a>

* Nodes errors now properly display in frontend, so there shouldn’t be any “mysterious” cases of nodes just stopping running
* Projects view redesign
* vertical/horizontal UI switch
* node layout improvements


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.atlas.design/atlas-ai-studio-overview/release-notes/release-0.7.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.