> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/design-and-structure/components/chips.md).

# Chips

The Chips component displays options or selected items in a compact, visually appealing list. It supports custom styling and interactive features.

### Usage

Chips are ideal for categorizing, filtering, or inputting data. They can dynamically display options, allowing users to add new chips and interact with the component.

### Customization

#### Custom Styling

You can modify the shapes of chips to fit your application's theme.

#### Adding Options

Enable the **Allow Adding Options** checkbox to let users add new chips dynamically.

#### Actions

The Chips component supports specifying actions that can be triggered by user interactions. You can define actions for the following events:

* **Top Actions**: Actions that appear at the top of the component.
* **Bottom Actions**: Actions that appear at the bottom of the component.
* **Value Changes**: Actions that trigger when the value of the chips changes.

{% @arcade/embed flowId="6c4u9xfS1vtht34FIVQK" url="<https://app.arcade.software/share/6c4u9xfS1vtht34FIVQK>" %}

For more detailed information on implementing actions, please refer to our [Action Documentation](https://docs.jetadmin.io/user-guide/workflow/steps/actions).


---

# 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.jetadmin.io/classic-app-builder/design-and-structure/components/chips.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.