> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/design-process/edit-mode/draw.md).
# Draw
The Draw tool enables the creation of geometry by sketching directly in the scene. It supports two modes: **Draw Lines**, for precise straight-line segments, and **Hand Draw**, for freehand shapes with post-processing options. All drawing takes place on a single plane to maintain consistent alignment.
#### **Draw Lines**
* Creates straight-line drawings by placing points, automatically connecting them with straight segments.
* To generate a filled shape, the line must be closed. Enabling snapping to `End` ensures precise alignment of endpoints, making closure more accurate and efficient. \
\
#### **Hand Draw**
Enables freehand drawing with more organic shapes.
* After drawing, a menu appears with options to refine the line:
* Close the line
* Smooth the curve
* Remove sharp angles
* Increase line detail
* To fill the shape with geometry, select the line and press **`Ctrl+O` (**[Cap open boundaries](/documentation/design-process/edit-mode/cap-open-boundaries.md)`)`
{% embed url="" %}
---
# 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://help.vectary.com/documentation/design-process/edit-mode/draw.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.
