> 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/vex-nx-user-guide-1/assist/using-assist.md).

# Using Assist

Assist is a **single dock** on the lab page. Open it with **VEX-NX Assist** on the toolbar. Use **Rail** to collapse to a thin strip; use **Hide** to close; use width controls for dock size.

Assist is **not** the Terminal float workspace. Terminal Glass / click-through control consoles only.

## Requirements

Assist requires a commercial edition with **Assist LLM** enabled (Pro, Academic, Team, or Enterprise) **and** an OpenRouter API key under **Administration -> Assist LLM**. Community has no Assist agent.

## Agent

Type naturally or use chips:

| Chip     | Example                                              |
| -------- | ---------------------------------------------------- |
| Build    | Build an MPLS VPN topology with configs              |
| Configs  | Generate and apply startup configs                   |
| Fix      | Fix the route-map on R1                              |
| Capture  | Capture packets on a link (when capture is licensed) |
| Export   | Export the config pack                               |
| Validate | Validate this lab                                    |

The agent streams plan, step, diff, artifact, and confirm cards. Destructive actions ask for Confirm. Your typed goal is the source of truth; chips are starters.

## Related

* Admins: Assist LLM settings
* OpenRouter models: [OpenRouter LLM](/vex-nx-user-guide-1/assist/openrouter-llm.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 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.vex-nx.com/vex-nx-user-guide-1/assist/using-assist.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.