> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/overview/chip/chip-bar.md).
# ε ChipBar
Element: A grouping for design convenience for display in the bar component. The bar component can have different background surfaces (colors) so we don't include a surface here.
Common chip bar layouts are located here and will be added to over time.
[Styleguide Link](https://zpl.io/a8DyPZQ)
* Parent: [Chiplist ](/core/components/form/chiplist.md)(Form Component), [Field - Content](/core/overview/field/field-content.md), Multiple Others
* Child: [Chip](/core/overview/chip.md)
## Properties
### Behavior
* **Fixed** - The control has a fixed width for display on the screen.
* **Scroll** - The control has an infinite horizontal scroll for its contents.
### Size
* **Base** - The default size, used in the majority of chip situations
* **Field** - When chips are presented inside of a field we use a slightly smaller size that fits within a field component.
---
# 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://able.bucca.com/core/overview/chip/chip-bar.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.
