> 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.40.0.md).
# Release 0.40.0
Previous Version: **v0.39.0**
Turn generated assets back into editable workflows, follow node runs at a glance, and review eligible subscription upgrades without leaving the canvas. These are the new features for normal users since 0.39.0; workspace owners and admins are included.
## Rebuild generated assets into editable workflows
Open a generated asset in the workspace asset picker and choose **Rebuild** to recreate the node that produced it. Recorded settings—including the resolved seed—are restored, and supported source media become connected input nodes. Text, numbers, and other settings remain on the producer. Assets generated by exported APIs and intermediate workflow steps are supported too.
{% embed url="" %}
Choose **Rebuild (recursively)** to reconstruct the available upstream generators and their connections. Shared sources and outputs from the same recorded run reuse nodes, while recorded list order and output positions are preserved.
{% embed url="" %}
The rebuilt group appears beyond your existing canvas content, selected and brought into view. You can remove the whole addition with one **Undo**. Rebuilding creates an editable graph without running nodes or spending generation credits. Running it afterward uses the usual execution and caching rules.
If some inputs or steps cannot be reconstructed, a **Cancel / Rebuild anyway** dialog explains the gaps before anything is added. Missing workspace assets leave empty inputs with replacement warnings; an available existing asset is kept as an input when its upstream step cannot be rebuilt.
Disabled actions offer **Why unavailable?**. Uploaded files, older assets without recorded generation settings, oversized settings, settings from another workspace, and unavailable nodes or options cannot be rebuilt. Settings are recorded for new executions; older assets do not receive them retroactively. Recursive rebuilding stops where an older output is ambiguous or an intermediate file has no recorded connectable output.
## Node status, timing, and credits beneath the title
Executable nodes now show a compact run-information line directly beneath the title. Settings and displayed results stay visible during a run, and editing locks from the initial **Play** click until completion.
**Preparing…** marks the start request. Once running, the line shows elapsed time and an estimated duration when one is available. A slim progress track advances toward that estimate, then becomes an activity indicator if the run takes longer. Runs without an estimate use activity throughout; reduced-motion preferences disable the animation.
Queued nodes show **Scheduled · waiting for N nodes**. Shared prerequisites count once, and the number updates as upstream work finishes. Read-only viewers see the count too, and the queue-cancellation tooltip includes it.
Credits appear alongside the status. A **Previous result** notice identifies outputs retained from before an input change or a queued or running attempt. Stop and queue-cancellation controls remain available in the node header and menu.
## Confirm eligible subscription upgrades directly on the canvas
Workspace owners and admins with an eligible monthly Stripe subscription and a card on file can review and confirm an upgrade from the credits popover or **Run blocked** card. Eligible Free/card-only subscriptions are included. **Plan & credits** uses the same terms table in its upgrade dialog.
Before confirming, review the card on file, monthly price, renewal date, today's full-month charge plus tax, applicable discounts or account credits, newly added credits, and regular credits carried over. If upgrading removes a scheduled cancellation, the confirmation says so. The confirmation button displays the amount.
Payment progress, a decline, and success are reported in place. **Plan & credits** also provides review and retry guidance for failed or pending operations.
An upgrade completed while its original **Run blocked** card is open can resume that run after the existing permission and funding checks. Closing the card during payment still reports the outcome without restarting the dismissed run.
Availability follows the existing billing permissions and upgrade eligibility. Workspaces without a subscription use Stripe Checkout; Marketplace billing and payment-recovery states keep their existing routes.
---
# 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.40.0.md?ask=&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.
