> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/overview/roadmap.md).

# Product Roadmap

Which YouDesign Command versions are current, supported or retired, and what the current and next releases focus on.

YouDesign Command follows the ServiceNow release cycle and supports the current and recent ServiceNow releases. Version 26.1 is the current release. Version 26.2 continues moving the data model onto the Portfolio Element architecture.

## Release status

| Version             | Status    | ServiceNow releases                     |
| ------------------- | --------- | --------------------------------------- |
| **26.2**            | Planned   | To be announced                         |
| **26.1**            | Current   | See the ServiceNow Store listing        |
| **26.0**            | Supported | See the ServiceNow Store listing        |
| **4.8**             | Supported | Washington, Xanadu, Yokohama, Zurich    |
| **4.7**             | Supported | Vancouver, Washington, Xanadu, Yokohama |
| **4.6**             | Expiring  | Vancouver, Washington                   |
| **4.5 and earlier** | Obsolete  | Not supported                           |

{% hint style="info" %}
**Check the Store for exact compatibility**

The ServiceNow Store listing for YouDesign Command shows the ServiceNow releases each version is certified for. If it differs from this page, the Store listing is correct.
{% endhint %}

## What the current and next releases focus on

| Version  | Focus                                                                                                                                                                                                                                                 |
| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **26.1** | The portal on a phone, faster startup and faster tables and full-page views, clearer icons, titles and counts, a formal assistant tone, and accessibility work toward WCAG 2.2 level AA. See the [Release Notes](/command/overview/release-notes.md). |
| **26.2** | Completing the move of the remaining fields onto the Portfolio Element architecture.                                                                                                                                                                  |

{% hint style="warning" %}
**Plans can change**

Dates and scope of future versions are not commitments. They are confirmed in the release notes and upgrade guides when each version ships.
{% endhint %}

## Related pages

* [Upgrade from v4.8 to v26.0](/command/get-the-app/upgrade-v48-to-v260.md), the first phase of the data model alignment
* [Updating YouDesign Command](/command/get-the-app/updating.md)


---

# 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.ins-pi.com/command/overview/roadmap.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.