> For the complete documentation index, see [llms.txt](https://help.claritylims.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.claritylims.illumina.com/instruments-and-integrations/other-release-notes/novaseq6k-file-v2.2.1-release-notes.md).

# NovaSeq 6000 File-based v2.2.1

## Version: 2.2.1 Compatibility:

* BaseSpace Clarity LIMS v4.2 or later, though not compatible with v6.0 and later
* NGS Extensions Package v5.15 or later
* BaseSpaceLIMS-AutomationWorker 0.1.0 (LIMS v4.2) or v1.0 (LIMS v5.0)

## Illumina NovaSeq Software Compatibility: NovaSeq Control Software (NVCS) v1.3.0

## Features to note for this release. Maintains integrity of sample information throughout the workflow

* Now Support S1 in addition to S2, and S4 flow cells per sample

## Known issues

There are no known issues for this release.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.claritylims.illumina.com/instruments-and-integrations/other-release-notes/novaseq6k-file-v2.2.1-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.