> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/labs/configuration-studio.md).

# Configuration Studio

![Configuration Studio](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FcJRTXdS4u1lyyYfUzJiP%2Fve20261112v5-config-studio.png?alt=media)

## Goal

Edit running, startup, candidate, and golden configs for one or many nodes, then validate, diff, and deploy without leaving the studio.

## Open it

1. From the OS sidebar / app launcher open **Configuration Studio**, or
2. From a lab workspace use ScriptPad / config actions that deep-link into the studio for the active lab

Pick the lab in the studio header if more than one lab exists.

## What you get

| Surface           | Use it for                                                 |
| ----------------- | ---------------------------------------------------------- |
| **Node tree**     | Spines / leafs / borders / hosts grouped for multi-select  |
| **Views**         | Running, startup, candidate, golden                        |
| **Editor**        | Per-node tabs with syntax-friendly editing                 |
| **Diff**          | Candidate vs running / golden comparisons                  |
| **Validation**    | Studio checks before push                                  |
| **History**       | Restore earlier config snapshots recorded in the studio    |
| **Terminal dock** | Live CLI pull / show / push helpers on supported platforms |
| **Assist panel**  | Draft or explain config when OpenRouter is configured      |

## Recipe: pull, edit, deploy

1. Select one or more running nodes
2. Pull **running** (or open **startup** / **golden**)
3. Edit the **candidate** view
4. Run **Validation** and review **Diff**
5. Deploy / push live (confirm the dialog). Optionally verify or save as post-action when offered

Expected: candidate becomes live on the guest (or a clear error if the runtime / credentials cannot push).

## Related

* [Operate and consoles](/labs/operate-and-consoles.md) (ScriptPad / Wipe day-0)
* [Automation Studio](/labs/automation-studio.md)
* [Using Assist](/assist/using-assist.md)
* [Features](/getting-started/features.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.vex-nx.com/labs/configuration-studio.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.