> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/releases-and-environments/autosave-and-concurrent-editing.md).

# Autosave and concurrent editing

StackAI saves your working draft as you edit in Workflow Builder, Interface, and Agent Builder. You can check the saved status, review earlier versions and detailed changes, and choose how to resolve edits from another session.

## Watch the walkthrough

Follow this 8-minute guide to create a small demo, confirm its edits are saved, inspect history and changes, and handle both concurrent-edit choices.

{% embed url="<https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FpGbf9aEyo4TyRGs4yj9W%2FStackAI-Autosave-Guide-Final-Alice.mp4?alt=media&token=af91ef39-a185-467e-a1da-aa680f90a26b>" %}

Jump to **4:23** for Version History, **5:41** for granular changes, or **6:50** for concurrent-edit messages.

## What changed

| Previously                                                    | Now                                                                                  |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Workflow and interface edits required a separate Save action. | Your draft saves automatically as you edit.                                          |
| Saving and publishing were separate actions.                  | They remain separate: autosave preserves the draft; publishing makes a version live. |

Agent Builder uses the same draft-saving system. A Save button may still appear for a separate task, such as adding a description to a history entry; it saves that description.

## Check that your draft is saved

After changing a workflow instruction or interface setting, check the save indicator beside **Draft**. Hover over it to see the time of the last confirmed save and an explanation of autosave. The workflow and interface show the same saved-status experience.

![The interface save indicator shows the last confirmed save and explains autosave.](https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FoUso4U8gMce8pYg09nz5%2Fautosave-saved-timestamp.png?alt=media\&token=c197b16c-6757-445a-ad17-44dbfec5d5fd)

Wait for your latest edit to be confirmed before leaving the project. If a save error or concurrent-edit message appears, resolve it and check the saved status again.

To confirm persistence, return to the dashboard and reopen the project. Your saved workflow instructions and interface settings remain in the draft.

## Inspect version history and detailed changes

Select **Draft** to open **Version History**. The sidebar separates the current working draft from saved versions. Use an entry's options to preview a version or add a description.

Inside a version preview, inspect both **Workflow** and **Interface**. Choose **Back to current draft** when you finish. Viewing an earlier version does not replace or publish your draft.

The restore control replaces the full draft, including workflow and interface configuration. Review both before restoring.

To inspect your current edits, open the **Publish** menu and choose **Review changes**. The **Latest changes** sidebar separates the comparison into:

| Tab           | What to review                                                                                                             |
| ------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Nodes**     | Changes to workflow steps and their settings, including instructions. Removed and added lines show the old and new values. |
| **Edges**     | Changes to the connections between nodes. An unchanged connection set shows no changes.                                    |
| **Interface** | Changes to interface settings, including its name, description, and type.                                                  |

Expand unchanged lines when you need surrounding context. Reviewing changes does not publish the project.

## Resolve a concurrent-edit message

Another teammate—or another browser tab using your own account—can edit the same project. When the same part changes in another session, StackAI may show **Someone else updated this project**.

![Someone else updated this project, with Load latest version and Keep my changes choices.](https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FN8CjmjSljt3zFhSTgGvE%2Fautosave-concurrent-edit-message.png?alt=media\&token=e99cb39b-2527-4a13-bf65-07ec0b1ffa6c)

Choose the outcome you intend:

| Choice                  | What happens                                                                                                                          |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Load latest version** | Loads the latest saved draft and discards your conflicting local edits. Choose this when you want to use the other session's changes. |
| **Keep my changes**     | Saves your local changes over the conflicting saved changes. Choose this when your local edits should be kept.                        |

{% hint style="warning" %}
Review your local edits before choosing. **Load latest version** discards the conflicting local edits; **Keep my changes** can replace the other session's conflicting changes. Coordinate with your teammate when you are unsure which version to keep.
{% endhint %}

For example, if one tab changes the interface name to “Welcome Assistant, My Draft” and a second tab enters “Welcome Assistant, Other Session,” the second tab can choose **Keep my changes** to save its name. The first tab can then choose **Load latest version** to adopt “Other Session.”

Check the resulting fields, preview, and saved status after resolving the message.

## Autosave and publishing

Autosave keeps your editable draft up to date. It does not make the draft live or replace a published release.

When you publish, StackAI first saves pending draft changes. Resolve any save error or conflict before trying again, then follow the project's usual publication or approval process.

## Related resources

[Saved Changes, Versions, and Published Releases](https://docs.stackai.com/technical-reference/releases-and-environments/saved-changes-versions-and-published-releases.md)

[Project version history and diffs](https://docs.stackai.com/guides-and-quickstarts/releases-and-environments/project-version-history-and-diffs.md)


---

# 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.stackai.com/technical-reference/releases-and-environments/autosave-and-concurrent-editing.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.
