> 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.6.0.md).
# Release 0.6.0
Platform link: [https://app-tech.atlas.design](https://app-tech.atlas.design/)
* Global node outputs cache:
* Basically if you generate “a cat” with seed “42” you will have instant output, as it will now just retrieve it from the global cache ! (ofc. any change to inputs will not retrieve anything, but generate from scratch)
* API export changes (note that API export feature still needs to be enabled per-user and is disabled by default)
* Executing API won’t recalculate nodes not dependent on the API inputs, and will use the global cache feature – so calling API with same inputs twice will result in near instant results !
* API export feature now outputs “API info” JSON, which can be pasted directly to the Atlas Unreal plugin
* **IMPORTANT: no backwards compatibility of already exported APIs with previous version, you need to re-export your APIs from app-tech.atlas.design (though there is backwards compatibility for projects, only not for already exported APIs) – we also plan to maintain backwards compatibility from now on**
* Enable bunch of new nodes for managing image arrays
* Create and break image array
* concatenate image arrays
* retrieve specific images count from array by text prompt
* “Multimodal” node with array input
* image to text with array input
* Support for PDF documents input
* drag & drop a pdf
* use “Extract Document Images” and “Extract Document Text” nodes
* Extract Document Images experimentally supports (automatically) extracting separate images from raster collages
* New “Simple LLM call” node – you can now use LLMs inside our app and exported APIs. One could even use our app to build just LLM pipelines without touching images or meshes.
* Various UI improvements:
* We began a major refactoring of the UI to unify styles and behaviors across various pages and components created at different times with differing visions. Our goal is to create a solid and consistent platform UI.
* After modifying hotkeys, you may need to refresh the page for the changes to take effect.
* Make the suggestions system more concise about amount of relevant suggestions
* Numerous bugfixes
### Known issues:
* After typing a prompt, you need to click out of the text field for the run button to be clickable/enabled
* “Selection agent” panel often jumps to the center of the screen
* some PDF documents may fail image or text extraction
* global cache via API doesn’t work when API has any binary inputs (images or meshes), will be fixed in next release/patch
---
# 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.6.0.md?ask=&goal=
```
`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.