> For the complete documentation index, see [llms.txt](https://cbwire.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbwire.ortusbooks.com/v2-1/wire-features/query-string.md).

# Query String

It can be useful at times to update the browser's query string when your [Wire's ](/v2-1/essentials/creating-components.md)state changes.

## Example

Let's say you are building a [Wire](/v2-1/essentials/creating-components.md) to search articles, and want the query string to reflect the current search value like so:

```
https://yourapp.com/search-articles?search=some+string
```

This way, when a user hits the back button or bookmarks the page, you can get the initial state out of the query string rather than resetting the [Wire](/v2-1/essentials/creating-components.md) every time.

You can add a `queryString` variable to your [Wires](/v2-1/essentials/creating-components.md) and CBWIRE will update the query string every time the property value changes and also update the property when the query string changes.

```javascript
component extends="cbwire.models.Component" {

    data = {
        "search": ""
    };
    
    queryString = [ "search" ];
}
```

```html
<div>
    <input wire:model="search" type="search" placeholder="Search articles...">
</div>
```


---

# 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://cbwire.ortusbooks.com/v2-1/wire-features/query-string.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.