> For the complete documentation index, see [llms.txt](https://docs.pletor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pletor.ai/build-agents/studio/toolbar.md).
# Toolbar
### Add node
The orange **+** button opens the node picker. This is how you add building blocks to your agent.
The picker is organized into sections to help you navigate capabilities.
Use the search bar at the top to find any node by name — this is the fastest way to add nodes when you know what you need.
***
### Assets
Opens the asset gallery where you can browse, search, and manage all the visuals and files generated by your agents. From here you can drag assets directly onto the canvas, preview outputs, or download them.
You can also find all the assets generated on Pletor and use them in your work.
***
### Templates
Browse pre-built agent templates for common use cases. Templates provide a ready‑made node chain that you can use as‑is, customize to fit your workflow, or treat as learning material.
This is the fastest way to get started.
***
### Learn Pletor
Opens learning resources directly inside the Studio — tutorials, walkthroughs, and tips to help you get the most out of the platform. Useful when you're building and want guidance without leaving the canvas.
***
### Chat with AI
Opens the AI Copilot chat. Describe what you want to build and the Copilot will help you — suggesting nodes, explaining how features work, or helping you troubleshoot your agent.
***
### Other actions
#### Change Agent name
The top-left corner shows your agent's name. Click it to rename your agent. The dropdown next to the Pletor logo lets you switch between agents or navigate back to the dashboard.
#### Test run
Executes your full agent chain from left to right. Each node runs in sequence, passing its output to the next connected node. The button is greyed out until your agent has at least one runnable node connected.
You can also run individual nodes by selecting a node and clicking the **Run** button inside its configuration panel, useful for testing one step at a time.
#### Version history
Access the work history for this agent. View previous versions, either via autosave or manually saved checkpoints.
#### Save in Version History
Saves the current state of your agent. Pletor auto-saves as you work, but you can trigger a manual save here when you want to capture a specific checkpoint in your work.
A new version of your agent is also created automatically whenever you deploy an App or share it.
#### Deploy as App
Turn your Agent into an App. See more here: [Deploy Apps](/automate/apps.md).
#### Share
Share your agent with teammates or make it available publicly.
***
### Working with nodes
| Action | How |
| ----------------------- | ---------------------------------------------------------------------------------- |
| **Add a node** | Click the orange **+** button in the left toolbar, or right-click on the canvas |
| **Move a node** | Click and drag it (Select mode) |
| **Connect nodes** | Drag from an output port (right edge) to an input port (left edge) on another node |
| **Delete a connection** | Click the connection line, then press `Backspace` or `Delete` |
| **Delete a node** | Select it, then press `Backspace` or `Delete` |
| **Duplicate a node** | `Ctrl/⌘ + D` or `Ctrl/⌘ + C` then `Ctrl/⌘ + V` |
| **Open node settings** | Click on the node to expand its configuration panel |
| **Group nodes** | Select multiple nodes to organize them into visual groups on the canvas |
***
---
# 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.pletor.ai/build-agents/studio/toolbar.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.