> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/frequently-asked-questions/how-do-i-adjust-arrow-size.md).

# How do I adjust arrow size?

If the default arrow size isn't to your liking you can use the following properties to customize the arrow size:

* `arrow-min-width`
* `arrow-min-height`
* `arrow-width`
* `arrow-height`

These properties can be used within `@settings` or within a [connection decoration rule](/guides/decorate.md#decorate-in-the-advanced-editor) in the Advanced Editor. Generally you'll want to set `arrow-min-width` and `arrow-min-height` to `0` if you're sizing arrows manually.

```scss
@settings {
  arrow-min-width: 0;
  arrow-min-height: 0;
  arrow-width: 5;
  arrow-height: 3;
}
```

{% hint style="info" %}
*NOTE: both `arrow-width` and `arrow-height` are multiplied against the connection width so take that into consideration when setting the values.*
{% endhint %}

#### Arrow offset

You can also increase the offset between the element and the connection to make the arrow more distinctive. To do so, add this code to your advanced editor:

```scss
element {
  margin: 10;
}
```

You can change the number 10 to any other number to increase/decrease the space between element and arrow.


---

# 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.kumu.io/frequently-asked-questions/how-do-i-adjust-arrow-size.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.