> For the complete documentation index, see [llms.txt](https://help.bioinsight.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.bioinsight.illumina.com/basespace/releases/previous-releases/2024/7.18.0.md).

# 7.18.0 - Custom Kit Deletion

#### Jan 23, 2024

#### Features

* Added the ability to delete custom library prep kits and index adapter kits from the Resources page.

#### Bugs Fixed

* Fixed an issue that prevented the transfer of projects containing NextSeq 1000/2000 and BCL Convert analysis data. Staged Rollout.
* Fixed an issue that could cause a NovaSeq X Local mode run to be incorrectly stuck in the Uploading status.
* Fixed an issue when transferring Projects that could prevent associated Biosamples from showing up for the recipient.
* Fixed a rare issue where an App launch could result in two analyses.

#### Release 7.18.1 - February 12, 2024

* Features
  * None.
* Bugs Fixed
  * A new version of the BaseSpace Downloader for Windows has been made available, that fixes network connection issues experienced by some users. A security warning about untrusted software may be shown during installation.


---

# 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://help.bioinsight.illumina.com/basespace/releases/previous-releases/2024/7.18.0.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.
